How To Fix CRMS4_SOM_PROD_BO109 - Condition type '&1' does not exist or is not valid

CRMS4_SOM_PROD_BO109 - Overview

• Message type: E = Error

• Message class: CRMS4_SOM_PROD_BO - Messages for BO Subscription Product Specification

• Message number: 109

• Message text: Condition type '&1' does not exist or is not valid

What causes this issue?

This condition type is not valid. Please check the entered value, if:
1. The condition type is the already maintained in the SD Pricing
Customizing Transaction: Define Condition Type
2. The condition type is maintained in the SOM Customizing Transaction:
Price Conditions for the Distribution to SAP CC
3. The condition type is specified for the use in the variant
configuration, which is indicated by the indicator ?Used for Variant
Configuration? in the SD Pricing Customizing Transaction: Define
Condition Type. In case the condition type is determined for the use in
the variant configuration, the value of the field ?Determined By? must
be set to ?Variant Condition Key Alias?. Specific Variant Condition Keys
must then exist in the variant configuration model of the used
subscription product

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CRMS4_SOM_PROD_BO109 - Details

• The SAP error message CRMS4_SOM_PROD_BO109 indicates that a specific condition type (represented by &1) does not exist or is not valid in the context of the SAP system you are working with. This error typically arises in the context of pricing or condition records in the SAP CRM (Customer Relationship Management) module, particularly when dealing with sales orders or service orders.
  Causes:
  
  Non-existent Condition Type: The condition type specified in the error message may not have been created in the system.
  Incorrect Configuration: The condition type may not be properly configured or activated in the pricing procedure.
  Missing Authorization: The user may not have the necessary authorizations to access the condition type.
  Incorrect Usage: The condition type may not be applicable in the context where it is being used (e.g., in a specific pricing procedure).
  Transport Issues: If the condition type was recently transported from another system, it may not have been properly imported or activated.
  
  Solutions:
  
  
  Check