How To Fix FTVV_MESSAGES379 - Dunning block not stored in table TZPAB

FTVV_MESSAGES379 - Overview

• Message type: E = Error

• Message class: FTVV_MESSAGES - Reporting Financial Assets Management

• Message number: 379

• Message text: Dunning block not stored in table TZPAB

What causes this issue?

You need to define a dunning block in table TZPAB because the settings
for this product type stipulate that postings are to be made with a
customer account in FI. ( TZPAB-SBUHAL = '3').
This dunning block is needed for payments to a third party . It
prevents these items being dunned to a customer account.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Define a dunning block.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FTVV_MESSAGES379 - Dunning block not stored in table TZPAB ?

  The SAP error message FTVV_MESSAGES379 indicates that there is an issue with the dunning block not being stored in the table TZPAB. This table is used to manage dunning information in the SAP system, and the error typically arises when there is an inconsistency or a missing entry related to dunning blocks.
  
  Cause:
  
  Missing Configuration: The dunning block may not be properly configured in the system.
  Data Inconsistency: There may be inconsistencies in the data that prevent the dunning block from being saved.
  Authorization Issues: The user may not have the necessary authorizations to create or modify entries in the TZPAB table.
  System Bugs: There could be a bug in the SAP version you are using that affects the handling of dunning blocks.
  
  
  Solution:
  
  
  Check Configuration:
  
  Ensure that the dunning procedure and dunning blocks are correctly configured in the system. You can check this in the SPRO transaction under Financial Accounting (FI) -> Accounts Receivable and Accounts Payable