How To Fix EEDMSET105 - Settlement run &1 for settlement document &2 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: EEDMSET - Messages for Settlement

• Message number: 105

• Message text: Settlement run &1 for settlement document &2 does not exist

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 EEDMSET105 - Settlement run &1 for settlement document &2 does not exist ?

  The SAP error message EEDMSET105 indicates that a settlement run for a specific settlement document does not exist. This error typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with settlement processes for internal orders, projects, or other cost objects.
  Cause:
  
  Settlement Run Not Executed: The most common cause is that the settlement run for the specified document has not been executed yet. This could be due to oversight or scheduling issues.
  Incorrect Document Number: The document number provided in the error message may be incorrect or does not correspond to an existing settlement document.
  Data Deletion: The settlement document may have been deleted or archived, making it unavailable for the current operation.
  Authorization Issues: There may be authorization issues preventing the user from accessing the settlement document.
  Configuration Issues: There could be configuration issues in the settlement settings that prevent the creation of the settlement document.
  
  Solution:
  
  Check Settlement Run: Verify if the settlement run has been executed for the specified document. If not, execute the settlement run for the relevant cost object.
  Verify Document Number: Double-check the document number provided in the error message to ensure it is correct and corresponds to an existing settlement document.
  Review Deletion/Archiving: Check if the settlement document has been deleted or archived. If it has been archived, you may need to restore it or check the archive settings.
  Authorization Check: Ensure that the user has the necessary authorizations to access the settlement document. Consult with your SAP security team if needed.
  Configuration Review: Review the configuration settings related to the settlement process in the SAP system. Ensure that all necessary settings are correctly configured.
  Consult Logs: Check the application logs for any additional error messages or warnings that may provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like KSU5 (for settlement) or KOB1 (for displaying order documents) to investigate further.
  SAP Notes: Look for relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Refer to SAP documentation on settlement processes for internal orders or projects to understand the expected workflow and requirements.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.