How To Fix VC2HL_BO023 - Pricing set to 'on request', because Configurator is set 'on request'

SAP Error Message - Details

• Message type: E = Error

• Message class: VC2HL_BO -

• Message number: 023

• Message text: Pricing set to 'on request', because Configurator is set 'on request'

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 VC2HL_BO023 - Pricing set to 'on request', because Configurator is set 'on request' ?

  The SAP error message VC2HL_BO023 indicates that the pricing for a configurable product is set to "on request" because the configurator is also set to "on request." This typically occurs in the context of SAP Variant Configuration (VC), where the pricing of a configurable material is dependent on the configuration selected by the user.
  Cause:
  
  Configurator Settings: The configurator for the material is set to "on request," which means that the pricing cannot be determined automatically and requires manual intervention or approval.
  Pricing Procedure: The pricing procedure for the configurable material may not be set up to handle automatic pricing for certain configurations.
  Missing Pricing Conditions: There may be missing or incomplete pricing conditions in the pricing procedure that prevent the system from calculating a price.
  Sales Document Type: The sales document type being used may not support automatic pricing for configurable materials.
  
  Solution:
  
  Review Configurator Settings: Check the configuration settings for the material in the SAP system. Ensure that the configurator is set up correctly and that it allows for automatic pricing if that is the desired behavior.
  Adjust Pricing Procedure: Review the pricing procedure assigned to the material. Ensure that it includes the necessary pricing conditions for the configurations being used.
  Define Pricing Conditions: If there are missing pricing conditions, define them in the pricing procedure. This may involve creating new condition records or adjusting existing ones.
  Sales Document Type Configuration: Ensure that the sales document type being used is configured to allow for automatic pricing. This may involve checking the settings in the sales document type configuration.
  Consult Documentation: Refer to SAP documentation or help resources for more detailed guidance on configuring pricing for variant configuration.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional guidance on pricing in variant configuration.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  CU50 (Configuration Profile)
  VK11 (Create Condition)
  VK12 (Change Condition)
  VK13 (Display Condition)
  
  
  Training and Support: If you are unsure about making changes, consider reaching out to your SAP support team or consulting with an SAP expert who specializes in variant configuration and pricing.
  
  By addressing the underlying causes and following the suggested solutions, you should be able to resolve the VC2HL_BO023 error and enable proper pricing for your configurable products.