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


SAP Error Message - Details

  • 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

  • Show details Hide details
  • 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.


Smart SAP Assistant

  • What is the cause and solution for SAP error message CRMS4_SOM_PROD_BO109 - Condition type '&1' does not exist or is not valid ?

    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:

    1. Non-existent Condition Type: The condition type specified in the error message may not have been created in the system.
    2. Incorrect Configuration: The condition type may not be properly configured or activated in the pricing procedure.
    3. Missing Authorization: The user may not have the necessary authorizations to access the condition type.
    4. Incorrect Usage: The condition type may not be applicable in the context where it is being used (e.g., in a specific pricing procedure).
    5. Transport Issues: If the condition type was recently transported from another system, it may not have been properly imported or activated.

    Solutions:

    1. Check Condition Type:

      • Go to the transaction code V/06 (for condition types) and verify if the condition type exists.
      • If it does not exist, you may need to create it or check with your configuration team.
    2. Review Pricing Procedure:

      • Use transaction code V/08 to check the pricing procedure assigned to the relevant sales document type.
      • Ensure that the condition type is included in the pricing procedure and is correctly configured.
    3. Authorization Check:

      • Ensure that the user has the necessary authorizations to access and use the condition type. This may involve checking roles and authorizations in transaction PFCG.
    4. Consult Configuration Documentation:

      • Review any documentation related to the configuration of pricing and condition types to ensure that everything is set up correctly.
    5. Transport Management:

      • If the condition type was recently transported, check the transport logs to ensure that it was successfully imported and activated in the target system.
    6. Debugging:

      • If the issue persists, consider debugging the process to identify where the condition type is being called and why it is not recognized.

    Related Information:

    • Transaction Codes:
      • V/06: Maintain Condition Types
      • V/08: Maintain Pricing Procedures
      • V/02: Change Condition Records
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
    • Documentation: Review SAP Help documentation for detailed information on pricing and condition types in SAP CRM.

    If the issue continues after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant