How To Fix EEDMSET128 - No lines from previous settlement runs found

SAP Error Message - Details

• Message type: E = Error

• Message class: EEDMSET - Messages for Settlement

• Message number: 128

• Message text: No lines from previous settlement runs 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 EEDMSET128 - No lines from previous settlement runs found ?

  The SAP error message EEDMSET128: No lines from previous settlement runs found typically occurs in the context of settlement processing in SAP, particularly when dealing with projects, internal orders, or other cost objects. This error indicates that the system could not find any settlement data from previous runs, which is necessary for the current settlement process.
  Causes:
  
  
  No Previous Settlement Runs: The most common cause is that there have been no prior settlement runs for the specified cost object. If the cost object has not been settled before, there will be no lines to retrieve.
  
  
  Incorrect Selection Criteria: The selection criteria used for the settlement run may not match any existing records. This could be due to incorrect dates, cost object types, or other parameters.
  
  
  Data Deletion: Previous settlement data may have been deleted or archived, making it unavailable for the current run.
  
  
  Configuration Issues: There may be configuration issues in the settlement settings that prevent the system from recognizing previous settlements.
  
  
  Authorization Issues: Lack of proper authorizations may prevent the user from accessing the necessary data.
  
  
  Solutions:
  
  
  Check Previous Settlements: Verify if there have been any previous settlement runs for the cost object in question. You can do this by checking the settlement history in the relevant transaction (e.g., KO88 for orders, CJ88 for projects).
  
  
  Review Selection Criteria: Ensure that the selection criteria used for the settlement run are correct. Check the date ranges, cost object types, and any other filters applied.
  
  
  Run Initial Settlement: If there have been no previous settlements, you may need to perform an initial settlement for the cost object. This can be done using the appropriate transaction code (e.g., KO88 for internal orders).
  
  
  Check Configuration: Review the configuration settings for the settlement process to ensure that everything is set up correctly. This may involve checking the controlling area settings, settlement profiles, and other related configurations.
  
  
  Consult with IT Support: If the issue persists, it may be beneficial to consult with your SAP support team or IT department to investigate further, especially if there are concerns about data deletion or system configuration.
  
  
  Authorization Check: Ensure that you have the necessary authorizations to access the settlement data. If not, contact your system administrator to obtain the required permissions.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KO88 (Order Settlement), CJ88 (Project Settlement), and KOB1 (Order Line Items).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation on settlement processes for more detailed guidance on how to handle settlements and troubleshoot related issues.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.