How To Fix 67425 - Dunning summarization for borrower; partner number was not found

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 425

• Message text: Dunning summarization for borrower; partner number was not found

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 67425 - Dunning summarization for borrower; partner number was not found ?

  The SAP error message 67425, which states "Dunning summarization for borrower; partner number was not found," typically occurs in the context of the dunning process in SAP Financial Accounting (FI). This error indicates that the system is unable to find a partner number (usually a customer or vendor) that is required for the dunning process.
  Cause:
  
  Missing Partner Data: The partner number (customer or vendor) may not exist in the system or may not be correctly assigned to the relevant dunning area.
  Incorrect Configuration: The dunning configuration may not be set up correctly, leading to issues in identifying the partner number.
  Data Inconsistency: There may be inconsistencies in the master data, such as missing or incorrect entries in the customer/vendor master records.
  Dunning Area Issues: The dunning area may not be properly defined or linked to the partner number.
  
  Solution:
  
  
  Check Partner Number: Verify that the partner number exists in the system. You can do this by checking the customer or vendor master data.
  
  Use transaction codes like FD03 (Display Customer) or FK03 (Display Vendor) to check if the partner number is valid.
  
  
  
  Review Dunning Configuration: Ensure that the dunning configuration is correctly set up. This includes checking the dunning areas and ensuring they are properly assigned to the relevant partner numbers.
  
  Use transaction code OBPM1 to review dunning areas and their settings.
  
  
  
  Correct Master Data: If the partner number is missing or incorrect, you may need to create or update the customer/vendor master data.
  
  Use transaction codes FD01 (Create Customer) or FK01 (Create Vendor) to add new entries if necessary.
  
  
  
  Run Dunning Program Again: After making the necessary corrections, try running the dunning program again to see if the error persists.
  
  Use transaction code F150 to execute the dunning run.
  
  
  
  Check for Authorizations: Ensure that you have the necessary authorizations to access and modify the relevant data.
  
  
  Related Information:
  
  Dunning Process: Dunning is a process used to remind customers of overdue payments. It involves sending out dunning letters or notifications based on the payment terms and overdue amounts.
  SAP Documentation: Refer to SAP Help documentation for detailed information on dunning configuration and processes.
  Transaction Codes: Familiarize yourself with relevant transaction codes for managing customer/vendor data and dunning processes, such as F150, FD01, FD03, FK01, and FK03.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any known issues related to this error message.