How To Fix EEDMSET173 - Settlement document &1 does not have a settlement run

SAP Error Message - Details

• Message type: E = Error

• Message class: EEDMSET - Messages for Settlement

• Message number: 173

• Message text: Settlement document &1 does not have a settlement run

What causes this issue?

Settlement document &V1& does not have a settlement run. This is not
permitted.

System Response

INCLUDE ISU_VERARB OBJECT DOKU ID TX

How to fix this error?

There is an inconsistency in the database.
INCLUDE NA_SYSADMIN1 OBJECT DOKU ID TX

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EEDMSET173 - Settlement document &1 does not have a settlement run ?

  The SAP error message EEDMSET173 indicates that a settlement document does not have an associated settlement run. This typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with internal orders, projects, or other cost objects that require settlement.
  Cause:
  
  Missing Settlement Run: The most common cause is that the settlement document you are trying to process has not been included in a settlement run. This can happen if the settlement run was not executed or if the document was created after the last settlement run.
  Incorrect Configuration: There may be configuration issues in the settlement profile or the settings for the cost object that prevent the settlement from being processed correctly.
  Timing Issues: If the settlement document was created after the settlement period has been closed, it may not be included in the current settlement run.
  Data Inconsistencies: There may be inconsistencies in the data that prevent the system from recognizing the settlement document.
  
  Solution:
  
  Execute a Settlement Run: Check if a settlement run has been executed for the relevant period. If not, execute a settlement run for the cost object in question.
  
  Go to the transaction code KOB1 (for internal orders) or CJ88 (for projects) to perform the settlement.
  
  
  Check Settlement Profile: Ensure that the settlement profile assigned to the cost object is correctly configured and allows for the settlement of the document.
  Review Document Creation Date: Verify the creation date of the settlement document. If it was created after the last settlement run, you may need to include it in the next run.
  Check for Errors: Look for any error messages or logs that might indicate issues with the settlement process. You can use transaction KOB2 to analyze the settlement documents.
  Consult Documentation: Review SAP documentation or consult with your SAP support team for specific configurations related to your organization's setup.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  KOB1: Display Actual Line Items for Orders
  KOB2: Display Settled Orders
  CJ88: Settle Project
  KSU5: Execute Settlement
  
  
  SAP Notes: Check for any SAP Notes related to this error message for additional guidance or patches that may resolve the issue.
  User Authorization: Ensure that you have the necessary authorizations to execute settlement runs and access the relevant documents.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or consult with an SAP expert for further troubleshooting.