How To Fix /ACCGO/CCK_TOLERANCE136 - Tolerance schedule &1 saved

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CCK_TOLERANCE -

• Message number: 136

• Message text: Tolerance schedule &1 saved

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 /ACCGO/CCK_TOLERANCE136 - Tolerance schedule &1 saved ?

  The SAP error message /ACCGO/CCK_TOLERANCE136 typically relates to issues with tolerance schedules in the context of the SAP Controlling (CO) module, particularly in the area of cost center accounting or internal orders. This message indicates that a tolerance schedule has been saved, but there may be issues or warnings associated with it.
  Cause:
  
  Configuration Issues: The tolerance schedule may not be configured correctly. This could involve incorrect settings for tolerances in the controlling area or for specific cost centers or internal orders.
  Data Inconsistencies: There may be inconsistencies in the data being processed, such as missing or incorrect entries in the relevant master data.
  Authorization Issues: The user may not have the necessary authorizations to create or modify tolerance schedules.
  System Errors: There could be temporary system errors or issues with the SAP environment that are causing the message to appear.
  
  Solution:
  
  
  Check Configuration: Review the configuration settings for tolerance schedules in the SAP system. Ensure that all necessary parameters are set correctly.
  
  Navigate to the relevant configuration path in SPRO (SAP Project Reference Object) and verify the settings for tolerance management.
  
  
  
  Review Master Data: Ensure that all relevant master data (cost centers, internal orders, etc.) is complete and accurate. Check for any missing or incorrect entries that could affect the tolerance schedule.
  
  
  Authorization Check: Verify that the user has the necessary authorizations to create or modify tolerance schedules. This can be done by checking the user's roles and authorizations in the SAP system.
  
  
  Consult Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  
  Testing: If changes are made, test the tolerance schedule creation or modification process again to ensure that the issue is resolved.
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional guidance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  KP26: Change Plan/Actual Distribution
  KSB1: Cost Centers: Actual Line Items
  KSV5: Display Tolerance Schedule
  
  
  Documentation: Review SAP documentation related to tolerance management in the CO module for a deeper understanding of how tolerances are managed and configured.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the error message and implement a solution.