How To Fix EEDMSET129 - Status &1 of settlement run is not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: EEDMSET - Messages for Settlement

• Message number: 129

• Message text: Status &1 of settlement run is not permitted

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 EEDMSET129 - Status &1 of settlement run is not permitted ?

  The SAP error message EEDMSET129, which states "Status &1 of settlement run is not permitted," typically occurs in the context of settlement runs in SAP, particularly in the area of Project System (PS) or other modules that involve settlement processes. This error indicates that the status of the settlement run you are trying to execute is not valid for the operation you are attempting.
  Causes:
  
  Incorrect Status: The settlement run you are trying to process may have a status that does not allow further actions. For example, if the settlement run has already been completed or canceled, you cannot reprocess it.
  Authorization Issues: The user may not have the necessary authorizations to perform the settlement operation on the specified run.
  Configuration Issues: There may be configuration settings in the system that restrict certain statuses from being processed.
  Data Integrity Issues: There could be inconsistencies or issues with the data related to the settlement run, such as missing or incorrect entries.
  
  Solutions:
  
  Check Settlement Run Status: Review the status of the settlement run in question. You can do this by navigating to the relevant transaction (e.g., CJ88 for project settlements) and checking the status. If the status is not appropriate for further processing, you may need to create a new settlement run.
  Review Authorizations: Ensure that the user executing the settlement has the necessary authorizations. You may need to consult with your SAP security team to verify and adjust user roles if necessary.
  Consult Configuration: Check the configuration settings related to settlement runs in your SAP system. This may involve reviewing the settings in the Project System or other relevant modules to ensure that they allow the desired operations.
  Data Consistency Check: Perform a data consistency check to ensure that all necessary data for the settlement run is complete and correct. This may involve running specific reports or transactions to identify and resolve any data issues.
  Consult Documentation: Refer to SAP documentation or notes related to the specific error message for additional insights or updates that may address the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ88 (Project Settlement), CJ02 (Change Project), and others that may be involved in the settlement process.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search the SAP Support Portal for specific notes that may provide additional context or solutions.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the issue persists after trying the above solutions, it may be beneficial to involve your SAP support team or consult with an SAP expert for further assistance.