How To Fix VY141 - Condition type &3: Access seq. &1 and calculation base &2 inconsistent

VY141 - Overview

• Message type: E = Error

• Message class: VY - Messages for freight processing

• Message number: 141

• Message text: Condition type &3: Access seq. &1 and calculation base &2 inconsistent

What causes this issue?

The condition tables stored in the <DS:DE.KOZGF>access sequence</> &V1&
contain fields that are not known if <DS:DE.BERGL>calculation base</>
&V2& is used.
Example:
A condition table stored in the access sequence "DIEN" contains a field
MATNR (Material). If you use the calculation base A (delivery),
however, this field is not known. The access sequence "DIEN" and the
calculation base A2, therefore, do not match.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VY141 - Condition type &3: Access seq. &1 and calculation base &2 inconsistent ?

  The SAP error message VY141 indicates that there is an inconsistency in the configuration of a condition type in the pricing procedure. Specifically, it points to an issue with the access sequence and the calculation base associated with that condition type.
  
  Cause:
  
  
  Inconsistent Configuration: The error typically arises when the access sequence defined for a condition type does not match the expected calculation base. This can happen if:
  
  The access sequence is not properly defined or is missing.
  The condition type is not correctly assigned to the pricing procedure.
  The calculation base for the condition type is not compatible with the access sequence.
  
  
  
  Missing or Incorrect Data: If the condition records for the condition type are not maintained correctly, or if there are missing entries in the access sequence, this can lead to inconsistencies.
  
  
  
  Solution:
  
  
  Check Condition Type Configuration:
  
  Go to the transaction code V/06 (for condition types) and check the configuration of the condition type that is causing