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

SAP Error Message - Details

• Message type: E = Error

• Message class: 67 - Loans Messages - Financial Assets Management

• Message number: 379

• Message text: Dunning block not stored in table TZPAB

What causes this issue?

A dunning block has to be entered in table TZPAB since postings should
be made using a customer in FI for this product type
(i.e. TZPAB-SBUHAL = '3').
This dunning block is required for payments to third-parties so that
these items are not dunned in the 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?

Enter the dunning block.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

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

  The SAP error message 67379, which states "Dunning block not stored in table TZPAB," typically occurs in the context of the dunning process in SAP. This error indicates that the system is unable to find or store the dunning block information in the relevant table (TZPAB), which is used to manage dunning blocks for customers.
  Cause:
  
  Missing Configuration: The dunning block may not be properly configured in the system. This could be due to missing entries in the configuration tables.
  Data Inconsistency: There may be inconsistencies in the data related to dunning blocks, such as missing or incorrect entries in the relevant tables.
  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 or issue in the specific version of SAP being used that affects the dunning process.
  
  Solution:
  
  
  Check Configuration: Verify the configuration settings for dunning blocks in the SAP system. Ensure that all necessary entries are present in the relevant configuration tables.
  
  Transaction Code: OBD2 (for dunning area configuration)
  Transaction Code: OBD3 (for dunning procedure configuration)
  
  
  
  Review Data: Check the data in the TZPAB table to ensure that there are no inconsistencies or missing entries. You can use transaction code SE16 or SE11 to view the table contents.
  
  
  Authorization Check: Ensure that the user has the necessary authorizations to perform dunning activities. This can be checked in the user roles and profiles.
  
  
  Debugging: If the issue persists, consider debugging the dunning process to identify where the error occurs. This may require the assistance of a technical consultant.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve the issue.
  
  
  Consult Documentation: Review the SAP documentation related to dunning processes for any additional insights or troubleshooting steps.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning) and F110 (Automatic Payment Transactions) as they may be involved in the dunning process.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Support: If the issue cannot be resolved internally, consider reaching out to SAP Support for assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.