How To Fix EB135 - Could not read dunning history

SAP Error Message - Details

• Message type: E = Error

• Message class: EB - IS-U invoicing

• Message number: 135

• Message text: Could not read 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 EB135 - Could not read dunning history ?

  The SAP error message EB135, which states "Could not read dunning history," typically occurs in the context of the dunning process, which is used for managing overdue customer accounts and sending reminders for outstanding payments. This error can arise due to various reasons, and here are some common causes, potential solutions, and related information:
  Causes:
  
  
  Missing Dunning Data: The dunning history for the customer or document may not exist in the system. This can happen if dunning has not been executed for the customer or if the data has been archived or deleted.
  
  
  Authorization Issues: The user may not have the necessary authorizations to access the dunning history data.
  
  
  Data Consistency Issues: There may be inconsistencies in the database or issues with the underlying data model that prevent the system from retrieving the dunning history.
  
  
  Technical Issues: There could be technical problems such as database connectivity issues or problems with the SAP application server.
  
  
  Configuration Issues: Incorrect configuration settings in the dunning procedure or related settings may lead to this error.
  
  
  Solutions:
  
  
  Check Dunning Data: Verify if the dunning history exists for the specific customer or document. You can do this by checking the dunning logs or running the dunning program again.
  
  
  User Authorizations: Ensure that the user has the appropriate authorizations to access dunning history. This can be checked in the user roles and profiles.
  
  
  Database Consistency Check: Perform a consistency check on the database to identify and resolve any inconsistencies. This may involve running specific SAP transactions or reports.
  
  
  Technical Support: If the issue persists, consider reaching out to your SAP Basis team or technical support to investigate any underlying technical issues.
  
  
  Review Configuration: Check the configuration settings for the dunning procedure in the SAP system. Ensure that all necessary settings are correctly configured.
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message. There may be patches or updates available that resolve known issues.
  
  
  Related Information:
  
  
  Dunning Process: Understanding the dunning process in SAP can help in troubleshooting. Familiarize yourself with the dunning procedure configuration and how it interacts with customer accounts.
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning) and FBL5N (Customer Line Item Display) to analyze customer accounts and dunning history.
  
  
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  
  If the problem continues after trying the above solutions, it may be beneficial to escalate the issue to your SAP support team for further investigation.