How To Fix EEDMSET102 - Mode &1 of settlement run not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: EEDMSET - Messages for Settlement

• Message number: 102

• Message text: Mode &1 of settlement run 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 EEDMSET102 - Mode &1 of settlement run not permitted ?

  The SAP error message EEDMSET102 indicates that the mode of the settlement run specified is not permitted. This error typically occurs in the context of the settlement process in SAP, particularly when dealing with internal orders, projects, or other cost objects.
  Cause:
  The error can be caused by several factors, including:
  
  Incorrect Settlement Mode: The specified settlement mode (e.g., periodic, final, etc.) may not be allowed for the particular cost object or configuration.
  Configuration Issues: The settings in the controlling area or the specific order type may not allow for the selected settlement mode.
  Status of the Cost Object: The cost object (e.g., internal order, project) may be in a status that does not permit the selected settlement mode.
  Authorization Issues: The user may not have the necessary authorizations to perform the settlement in the specified mode.
  
  Solution:
  To resolve the error, consider the following steps:
  
  
  Check Settlement Mode: Verify that the settlement mode you are trying to use is valid for the cost object. You can do this by checking the configuration settings in the SAP system.
  
  
  Review Configuration: 
  
  Go to the configuration settings for the controlling area and the specific order type to ensure that the selected settlement mode is permitted.
  Check the settings in transaction OKO7 (for internal orders) or CJ20N (for projects) to see if the settlement profile allows the mode you are trying to use.
  
  
  
  Check Cost Object Status: Ensure that the cost object is in a status that allows for the settlement run. For example, if the order is closed or has been flagged for deletion, it may not allow settlement.
  
  
  User Authorizations: Ensure that the user executing the settlement has the necessary authorizations. You may need to consult with your SAP security team to verify this.
  
  
  Consult Documentation: Review the SAP documentation or help files related to settlement runs for additional insights on permitted modes and configurations.
  
  
  Testing: If changes are made to the configuration or status of the cost object, perform a test settlement run to confirm that the issue has been resolved.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KO88 (for order settlement) or CJ88 (for project settlement).
  SAP Notes: Check for any SAP Notes related to this error message for additional guidance or patches that may address known issues.
  Community Forums: Consider searching or posting in SAP community forums for insights from other users who may have encountered the same issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.