How To Fix >6113 - No entry found in correspondence dunning history

SAP Error Message - Details

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 113

• Message text: No entry found in correspondence dunning history

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 >6113 - No entry found in correspondence dunning history ?

  The SAP error message "6113 No entry found in correspondence dunning history" typically occurs when you are trying to access dunning history for a customer or vendor, but there are no records available in the dunning history table for that particular entity. This can happen for several reasons:
  Causes:
  
  No Dunning Process Executed: The customer or vendor may not have been subjected to any dunning process, meaning no dunning letters have been generated.
  Dunning History Cleared: The dunning history may have been cleared or archived, leading to the absence of records.
  Incorrect Selection Criteria: The selection criteria used to retrieve the dunning history may be incorrect, such as the wrong customer number, company code, or date range.
  Data Not Yet Processed: If the dunning process was recently run, the data may not yet be available in the history due to processing delays.
  
  Solutions:
  
  Check Dunning Process: Verify if the dunning process has been executed for the customer/vendor in question. You can do this by checking the dunning run logs.
  Review Selection Criteria: Ensure that the selection criteria you are using to view the dunning history are correct. Double-check the customer/vendor number, company code, and date range.
  Run Dunning Program: If no dunning letters have been generated, you may need to run the dunning program (transaction code F150) to create dunning notices for the relevant customers or vendors.
  Check Dunning History Table: You can check the dunning history table (usually DUNH for dunning history) directly in the database to see if any entries exist for the customer/vendor.
  Consult with IT or SAP Support: If you suspect that the dunning history has been cleared or archived, consult with your IT department or SAP support team to understand the data retention policies and whether the data can be restored.
  
  Related Information:
  
  Dunning Process: The dunning process in SAP is used to remind customers of overdue payments. It involves generating dunning letters based on the payment terms and overdue amounts.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  F150: Dunning
  FBL1N: Vendor Line Item Display
  FBL5N: Customer Line Item Display
  
  
  Dunning Configuration: Review the dunning configuration settings in your SAP system to ensure they are set up correctly for the relevant customers or vendors.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.