How To Fix VH608 - KONV: CondRecs with update -->(inactive/active) weighted with KONV share

VH608 - Overview

• Message type: E = Error

• Message class: VH - SD pricing

• Message number: 608

• Message text: KONV: CondRecs with update -->(inactive/active) weighted with KONV share

Please read the information in
<DS:NA.VH607>Inactive conditions with update</>
Determining this weighted ratio
Determining the maximum is carried out per condition. The ratio is
weighted with the percentage share of the frequency with with the
condition occurs in PRCD_ELEMENTS.
Example:
Condition type: TEST
PRCD_ELEMENTS entries: total (all conditions) 100 000
only for condition type TEST 10 000
of which inactive 5 000
Thus:
% of TEST in PRCD_ELEMENTS = 10 %
% of inactive / active in TEST = 50 %
==> value ratio = 0,1 * 0,5 = 0,05
or in % = 5

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VH608 - KONV: CondRecs with update -->(inactive/active) weighted with KONV share ?

  Certainly! Here's a detailed explanation of the SAP error message:
  
  SAP Error Message:
  VH608 KONV: CondRecs with update -->(inactive/active) weighted with KONV share
  
  
  Cause:
  This error occurs during the pricing condition update process in sales documents (e.g., sales orders, billing documents) when the system tries to update condition records (CondRecs) in the KONV table, but encounters a conflict related to the weighting of condition records that are either active or inactive.
  More specifically:
  
  The system attempts to update condition records that have been flagged as either active or inactive.
  These condition records are weighted based on their share in the KONV table.
  The inconsistency or conflict arises because the system expects a consistent weighting scheme for condition records during update, but finds that inactive and active condition records are mixed or weighted incorrectly.
  This can happen due to incorrect condition record maintenance, custom pricing routines, or inconsistencies in condition types or access sequences.
  
  
  When does it occur?
  
  During sales document pricing