How To Fix /SAPCND/GENERATOR156 - Generation of scale table table type &1 was started

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/GENERATOR -

• Message number: 156

• Message text: Generation of scale table table type &1 was started

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 /SAPCND/GENERATOR156 - Generation of scale table table type &1 was started ?

  The SAP error message /SAPCND/GENERATOR156 typically indicates that there is an issue related to the generation of a scale table in the SAP system. This message is part of the SAP Condition Management (CND) framework, which is used for managing pricing and conditions in various SAP modules.
  Cause:
  The error message /SAPCND/GENERATOR156 can occur due to several reasons, including:
  
  Missing or Incomplete Data: The scale table may not have all the necessary data or configuration settings required for its generation.
  Authorization Issues: The user attempting to generate the scale table may not have the necessary authorizations to perform this action.
  System Configuration Issues: There may be issues with the configuration of the condition types or the related tables in the SAP system.
  Database Locking: The database may be locked or busy, preventing the generation process from completing.
  Technical Errors: There could be underlying technical issues, such as problems with the ABAP code or database inconsistencies.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  Check Data Completeness: Ensure that all necessary data for the scale table is present and correctly configured. Review the condition records and ensure they are complete.
  Review Authorizations: Verify that the user has the necessary authorizations to generate the scale table. You may need to consult with your SAP security team.
  Check Configuration: Review the configuration settings for the condition types and ensure they are set up correctly. This may involve checking the relevant customizing settings in the SAP system.
  Database Status: Check the status of the database to ensure it is not locked or busy. You may need to consult with your database administrator if there are issues.
  Review Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Re-run the Generation: After addressing any identified issues, try to re-run the generation of the scale table.
  Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as VK11 (Create Condition) or VK12 (Change Condition) to manage condition records.
  SAP Help Documentation: Refer to the official SAP Help documentation for more detailed information on condition management and scale tables.
  SAP Community: Consider searching or posting in the SAP Community forums for additional insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.