How To Fix EARC368 - Stop: The commit counter defined in Customizing is not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: EARC - IS-U: Archiving

• Message number: 368

• Message text: Stop: The commit counter defined in Customizing 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 EARC368 - Stop: The commit counter defined in Customizing is not permitted ?

  The SAP error message EARC368 indicates that there is an issue with the commit counter defined in the system's Customizing settings. This error typically arises in the context of the SAP system's data processing, particularly when dealing with batch input sessions or data transfers.
  Cause:
  The error message "EARC368 Stop: The commit counter defined in Customizing is not permitted" usually occurs due to one of the following reasons:
  
  Invalid Commit Counter Configuration: The commit counter set in the Customizing settings is either too high or not within the acceptable range defined by the system.
  System Settings: The system may have specific settings that restrict the commit counter to a certain value, and the current configuration exceeds this limit.
  Transport Issues: If the system has recently undergone a transport of changes, the commit counter settings may not have been properly updated or synchronized.
  
  Solution:
  To resolve the EARC368 error, you can take the following steps:
  
  
  Check Customizing Settings:
  
  Navigate to the relevant Customizing transaction (usually SPRO).
  Look for the settings related to the commit counter, which can typically be found under the relevant application area (e.g., Logistics, Financials).
  Ensure that the commit counter is set to a valid value that is permitted by the system.
  
  
  
  Adjust the Commit Counter:
  
  If the commit counter is set too high, reduce it to a value that is acceptable. The typical range is often between 1 and 999, but this can vary based on specific configurations.
  Save the changes and re-test the process that triggered the error.
  
  
  
  Review System Documentation:
  
  Consult the SAP documentation or help files for your specific version to understand the acceptable ranges and configurations for the commit counter.
  
  
  
  Check for Transport Issues:
  
  If the issue arose after a transport, verify that all relevant changes were successfully imported and that there are no inconsistencies in the system settings.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional guidance.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SPRO for Customizing and SE11 for data dictionary checks.
  Batch Input Sessions: Understand how batch input sessions work in SAP, as this error often relates to data uploads or processing.
  System Logs: Check system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  
  By following these steps, you should be able to identify and resolve the cause of the EARC368 error in your SAP system.