How To Fix W_CB200 - Condition type &1 is not contained in calculation schema &2

SAP Error Message - Details

• Message type: E = Error

• Message class: W_CB -

• Message number: 200

• Message text: Condition type &1 is not contained in calculation schema &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 W_CB200 - Condition type &1 is not contained in calculation schema &2 ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  W_CB200 Condition type &1 is not contained in calculation schema &2
  
  Meaning / Cause:
  This warning message occurs during pricing or condition processing in SAP Sales and Distribution (SD) or Materials Management (MM) when the system tries to apply a condition type that is not defined in the assigned calculation schema.
  
  Condition type &1: The specific condition type (e.g., PR00, K004, etc.) that the system attempted to process.
  Calculation schema &2: The pricing procedure or calculation schema assigned to the document or transaction.
  
  The system expects all condition types used in pricing to be part of the calculation schema. If a condition type is missing from the schema, the system cannot process it properly, leading to this warning.
  
  Common Causes:
  
  Condition type missing in pricing procedure: The condition type is not included in the pricing procedure assigned to the sales document or purchasing document.
  Incorrect pricing procedure assignment: The pricing procedure assigned to the document does not match the expected one that contains the condition type.
  Custom condition type not maintained: A custom or newly created condition type has not been added to the calculation schema.
  Incorrect access sequence or condition record: Sometimes, condition records exist for a condition type that is not part of the pricing procedure.
  Copying or referencing errors: When copying pricing procedures or calculation schemas, some condition types might be omitted.
  
  
  Solution / How to Fix:
  
  
  Check the pricing procedure / calculation schema:
  
  Go to transaction V/08 (for SD pricing procedures) or OMWN (for MM calculation schemas).
  Verify that the condition type &1 is included in the calculation schema &2.
  
  
  
  Add the missing condition type:
  
  If the condition type is missing, add it to the calculation schema at the appropriate step.
  Maintain the correct condition class, calculation type, and other relevant details.
  
  
  
  Verify pricing procedure assignment:
  
  Check the assignment of pricing procedure to sales document type, customer, or material (via V/08, V/07, or OVKK).
  Ensure the correct pricing procedure is assigned that contains the condition type.
  
  
  
  Check condition records:
  
  Use VK13 to check if condition records exist for the condition type.
  If condition records exist but the condition type is not in the pricing procedure, either remove the records or add the condition type to the procedure.
  
  
  
  Test the pricing:
  
  After changes, test the pricing in the sales order or purchasing document to confirm the warning no longer appears.
  
  
  
  
  Additional Information:
  
  This message is a warning (W_), not an error, so the system may still process the document but the pricing might be incomplete or incorrect.
  It is important to maintain consistency between condition types and pricing procedures to ensure accurate pricing.
  In MM, similar issues can occur with calculation schemas for invoice verification or purchase orders.
  Always transport changes in pricing procedures carefully between systems (DEV ? QAS ? PRD).
  
  
  Summary Table:
  
  
  
  Aspect
  Details
  
  
  
  
  Message ID
  W_CB200
  
  
  Message Text
  Condition type &1 is not contained in calculation schema &2
  
  
  Module
  SD Pricing / MM Pricing
  
  
  Cause
  Condition type missing in calculation schema
  
  
  Solution
  Add condition type to calculation schema or correct pricing procedure assignment
  
  
  Transactions to check
  V/08, OMWN, VK13
  
  
  
  
  If you need help with specific transaction codes or configuration steps, feel free to ask!