How To Fix CACS_CONDITIONS213 - Only scale basis 'C' or 'B' allowed

CACS_CONDITIONS213 - Overview

• Message type: E = Error

• Message class: CACS_CONDITIONS - Comn: Condition Technique Messages

• Message number: 213

• Message text: Only scale basis 'C' or 'B' allowed

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 CACS_CONDITIONS213 - Only scale basis 'C' or 'B' allowed ?

  The SAP error message CACS_CONDITIONS213 indicates that there is an issue with the scale basis defined in the condition records for a pricing procedure in SAP Convergent Charging (SAP CACS). Specifically, the error states that only scale basis 'C' (for cumulative) or 'B' (for non-cumulative) is allowed, and the current configuration is not compliant with this requirement.
  
  Cause:
  
  Incorrect Scale Basis: The scale basis defined in the condition record is set to a value other than 'C' or 'B'. This could happen due to manual entry errors or incorrect configuration in the pricing procedure.
  
  Configuration Issues: The pricing procedure or condition type may not be set up correctly to handle the expected scale basis.
  Data Migration Issues: If data was migrated from another system or manually uploaded, it may contain invalid scale basis values.
  
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the condition records related to the pricing procedure in question.
  Verify the scale basis field and ensure it