How To Fix VT579 - Calculation type or scale basis is not defined for condition class

VT579 - Overview

• Message type: E = Error

• Message class: VT - Vertriebstabellen

• Message number: 579

• Message text: Calculation type or scale basis is not defined for condition class

What causes this issue?

Not all condition classes (for example, C subsequent settlement, bonus)
support all calculation types and scale base typte (scale types).
Example: The calculation type G (formula) is not supported for
condition class C.

System Response

The entry is not allowed.

How to fix this error?

Correct the entry.

Procedure for System Administrators

The following applies to subsequent settlement:
Allowed calculation types
A - percental, e.g. 3%
B - fixed amount, e.g. 100 EUR
C - quantity, e.g.1 EUR per piece
D - gross weight, e.g. 1 EUR per ton
E - net weight, e.g. 1 EUR per kg
F - volumes, e.g. 1 EUR per liter
L - points (only allowed in purchasing), e.g. 0.01 EUR per 1 point
By choosing one of the calculation types D, E, F, or L, you tell the
system that, if necessary, it can convert units without the material.
Currently, for subsequent settlement, the material is not seen as a
data retention level. For example, it is no longer possible to carry
out a conversion of bottles in crates in settlement. For this, the
material must be known, i.e. whether the material is bottles of beer or
mineral water. For a condition of 3% on all drinks, conversion is no
longer possible.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VT579 - Calculation type or scale basis is not defined for condition class ?

  The SAP error message VT579, which states "Calculation type or scale basis is not defined for condition class," typically occurs in the context of pricing conditions in SAP, particularly when working with condition records in the pricing procedure.
  
  Cause:
  This error usually arises due to one of the following reasons:
  
  
  Missing Configuration: The calculation type or scale basis for a specific condition class has not been defined in the pricing procedure. This can happen if the condition type is not properly configured in the system.
  
  
  Incorrect Condition Type: The condition type being used may not be appropriate for the pricing procedure or may not have the necessary settings.
  
  
  Condition Class Issues: The condition class associated with the condition type may not have the required calculation type or scale basis defined.
  
  
  Custom Development: If there are custom developments or modifications in the pricing procedure, they may not align with the standard configuration, leading to this error.
  
  
  
  Solution:
  To resolve