How To Fix EEDMSET164 - Error occurred while starting settlement job &1 &2

SAP Error Message - Details

• Message type: E = Error

• Message class: EEDMSET - Messages for Settlement

• Message number: 164

• Message text: Error occurred while starting settlement job &1 &2

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 EEDMSET164 - Error occurred while starting settlement job &1 &2 ?

  The SAP error message EEDMSET164, which states "Error occurred while starting settlement job &1 &2," typically occurs in the context of the settlement process in SAP, particularly in modules like SAP Project System (PS) or SAP Controlling (CO). This error can arise due to various reasons, and understanding the cause is crucial for finding a solution.
  Possible Causes:
  
  Configuration Issues: Incorrect configuration settings in the settlement profile or settlement rules can lead to this error.
  Missing Authorizations: The user executing the settlement job may lack the necessary authorizations to perform the action.
  Data Issues: Incomplete or inconsistent data in the relevant master data or transaction data can prevent the settlement job from starting.
  Job Scheduling Conflicts: If there are other jobs scheduled at the same time, it may lead to conflicts that prevent the settlement job from starting.
  System Performance: High system load or performance issues can also cause jobs to fail to start.
  
  Solutions:
  
  Check Configuration: Review the settlement profile and rules to ensure they are correctly configured. Make sure that all necessary parameters are set up properly.
  Verify Authorizations: Ensure that the user has the required authorizations to execute the settlement job. You can check this in transaction SU53 or by consulting with your security team.
  Data Validation: Check the relevant master and transaction data for completeness and consistency. Look for any missing or incorrect entries that could be causing the issue.
  Job Monitoring: Use transaction SM37 to monitor job logs and check for any other jobs that might be conflicting with the settlement job. If necessary, reschedule jobs to avoid conflicts.
  System Performance: If the system is under heavy load, consider running the job during off-peak hours or optimizing system performance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  CJ88: Settle Project
  CJI3: Display Actual Cost Line Items
  SM37: Job Monitoring
  
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Logs and Traces: Review application logs (transaction SLG1) for more detailed error messages that can provide insights into the root cause.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or technical team for further investigation, as they can provide deeper insights into system-level issues.