How To Fix WOST_WSSO_TOOLS010 - Condition type &1 is not contained in pricing procedure &2.

SAP Error Message - Details

• Message type: E = Error

• Message class: WOST_WSSO_TOOLS - Message class for tools

• Message number: 010

• Message text: Condition type &1 is not contained in pricing procedure &2.

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 WOST_WSSO_TOOLS010 - Condition type &1 is not contained in pricing procedure &2. ?

  The SAP error message WOST_WSSO_TOOLS010 indicates that a specific condition type (denoted as &1) is not included in the pricing procedure (denoted as &2) that is being used in the transaction. This error typically arises during the pricing determination process in sales and distribution (SD) or other modules where pricing is relevant.
  Cause:
  
  Missing Condition Type: The condition type specified in the error message is not defined in the pricing procedure that is currently assigned to the sales document or transaction.
  Incorrect Configuration: The pricing procedure may not be configured correctly to include all necessary condition types for the specific transaction.
  Transaction Type Mismatch: The transaction type being used may not be compatible with the pricing procedure that is assigned, leading to the absence of the required condition type.
  
  Solution:
  
  
  Check Pricing Procedure Assignment:
  
  Go to the configuration settings in SAP (Transaction code: SPRO).
  Navigate to Sales and Distribution > Basic Functions > Pricing > Pricing Control.
  Verify that the correct pricing procedure is assigned to the relevant sales document type.
  
  
  
  Modify Pricing Procedure:
  
  If the condition type is indeed missing from the pricing procedure, you can add it:
  
  Go to Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Pricing Procedures.
  Select the relevant pricing procedure and add the missing condition type to it.
  
  
  
  
  
  Review Condition Records:
  
  Ensure that condition records for the missing condition type are maintained. You can check this using transaction codes like VK11 (Create Condition) or VK12 (Change Condition).
  
  
  
  Check Transaction Type:
  
  Ensure that the transaction type being used is compatible with the pricing procedure. You can check this in the configuration settings under Sales and Distribution > Sales > Sales Document > Define Sales Document Types.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to see if the error persists.
  
  
  
  Related Information:
  
  Condition Types: These are used in pricing to determine how prices are calculated. Common examples include discounts, surcharges, and taxes.
  Pricing Procedures: These define the sequence in which condition types are processed and how they interact with each other.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as V/08 (Maintain Pricing Procedures) and V/06 (Maintain Condition Types) for further configuration.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in SD pricing.