How To Fix 9J679 - Error whilst saving settlement run identification data

SAP Error Message - Details

• Message type: E = Error

• Message class: 9J -

• Message number: 679

• Message text: Error whilst saving settlement run identification data

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 9J679 - Error whilst saving settlement run identification data ?

  The SAP error message 9J679, which indicates an error while saving settlement run identification data, typically arises in the context of the settlement process in SAP, particularly in modules like SAP Controlling (CO) or Project System (PS). Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  Data Inconsistency: There may be inconsistencies in the data being processed, such as missing or incorrect entries in the settlement run identification data.
  Authorization Issues: The user may not have the necessary authorizations to perform the settlement run.
  Configuration Issues: Incorrect configuration settings in the settlement profile or related settings can lead to this error.
  Technical Issues: There could be underlying technical issues, such as database locks or system performance problems.
  Missing Master Data: Required master data (like cost centers, internal orders, etc.) may be missing or incorrectly set up.
  
  Solutions:
  
  Check Data Consistency: Review the data being processed in the settlement run. Ensure that all required fields are filled out correctly and that there are no inconsistencies.
  Review Authorizations: Verify that the user executing the settlement run has the necessary authorizations. This can be checked in transaction SU53 or by consulting with your security team.
  Configuration Review: Check the configuration settings for the settlement profile and ensure they are set up correctly. This can be done in transaction SPRO.
  System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
  Database Locks: Investigate if there are any database locks that might be preventing the saving of the settlement run. You can use transaction SM12 to check for locks.
  Consult SAP Notes: Look for relevant SAP Notes that might address this specific error. You can search for notes in the SAP Support Portal.
  Technical Support: If the issue persists, consider reaching out to your SAP Basis team or SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  KKA2: For executing settlement runs.
  KSB1: For displaying cost center reports.
  S_ALR_87013611: For settlement reports.
  
  
  Documentation: Review SAP documentation related to settlement processes in CO or PS for best practices and troubleshooting tips.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the 9J679 error and implement a suitable solution.