How To Fix /SAPCND/GENERATOR123 - Customizing error: Application &1 /Usage &2 not maintained.

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/GENERATOR -

• Message number: 123

• Message text: Customizing error: Application &1 /Usage &2 not maintained.

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/GENERATOR123 - Customizing error: Application &1 /Usage &2 not maintained. ?

  The SAP error message /SAPCND/GENERATOR123 indicates a customizing error related to the application and usage not being maintained in the system. This error typically arises in the context of condition management, where certain configurations or settings are required for the application and usage specified in the error message.
  Cause:
  The error occurs when:
  
  The application (&1) and usage (&2) specified in the error message are not properly configured in the system.
  There may be missing entries in the customizing tables that define the relationship between applications and usages.
  The necessary condition types or access sequences are not defined for the specified application and usage.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Customizing Settings:
  
  Go to the SAP Customizing Implementation Guide (IMG) and navigate to the relevant section for condition management.
  Ensure that the application and usage specified in the error message are maintained correctly.
  
  
  
  Maintain Application and Usage:
  
  Use transaction code SPRO to access the IMG.
  Navigate to the relevant path for maintaining applications and usages. This is usually found under:
  
  Sales and Distribution (SD) -> Basic Functions -> Pricing -> Pricing Control -> Define Application and Usage.
  
  
  Ensure that the application and usage are defined and that all necessary settings are in place.
  
  
  
  Check Condition Types:
  
  Verify that the condition types related to the application and usage are defined and active.
  Ensure that the access sequences for these condition types are also properly configured.
  
  
  
  Transport Requests:
  
  If the settings were recently changed or transported from another system, ensure that the transport requests were successful and that all necessary objects were included.
  
  
  
  Testing:
  
  After making the necessary changes, test the functionality to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SPRO: Access the SAP Customizing Implementation Guide.
  SE11: Data Dictionary to check the relevant tables.
  SE16: Data Browser to view entries in customizing tables.
  
  
  
  Tables to Check:
  
  T681: Pricing condition types.
  T685: Application and usage settings.
  T684: Access sequences.
  
  
  
  Documentation:
  
  Refer to SAP Help documentation for detailed information on condition management and customizing settings.
  
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation, as there may be additional underlying issues affecting the configuration.