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

SAP Error Message - Details

• 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 (VA01/VA02/VA03).
  During billing document creation or update.
  When condition records are updated or recalculated.
  When condition records are copied or changed in the KONV table.
  
  
  Solution:
  
  
  Check Condition Records:
  
  Verify the condition records for the condition type involved.
  Ensure that condition records are correctly maintained and not partially active/inactive in a way that causes weighting conflicts.
  Use transaction VK13 to display condition records and check their validity and status.
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure for any custom routines or condition types that might cause weighting conflicts.
  Ensure that condition types that are mutually exclusive are not combined incorrectly.
  
  
  
  Analyze Custom Pricing Routines:
  
  If custom user exits or BAdIs are used (e.g., USEREXIT_PRICING_PREPARE_TKOMK, USEREXIT_PRICING_PREPARE_TKOMP), check if they manipulate condition records or weighting incorrectly.
  Debug the pricing routine to see where the weighting conflict arises.
  
  
  
  Check KONV Table Entries:
  
  Use SE16/SE16N to check the KONV table entries for the sales document.
  Look for condition records with inconsistent active/inactive flags or weighting shares.
  
  
  
  SAP Notes and Patches:
  
  Search for relevant SAP Notes that address this error message.
  Apply any recommended patches or corrections.
  
  
  
  Recreate or Adjust Condition Records:
  
  If condition records are corrupted or inconsistent, consider deleting and recreating them.
  Ensure that condition records are properly maintained with correct validity periods and status.
  
  
  
  
  Related Information:
  
  KONV Table: Stores condition records for pricing in sales documents.
  Condition Records: Define prices, discounts, surcharges, taxes, etc.
  Condition Types: Define the nature of the condition (e.g., PR00 for price, K004 for material discount).
  Weighting: Some pricing scenarios use weighting to distribute condition values proportionally.
  Inactive/Active Flags: Condition records can be active or inactive based on validity dates or manual settings.
  Transaction Codes:  
  
  VA01/VA02/VA03 - Create/Change/Display Sales Order  
  VF01/VF02/VF03 - Create/Change/Display Billing Document  
  VK13 - Display Condition Records  
  SE16/SE16N - Data Browser for tables like KONV
  
  
  
  
  Summary:
  The VH608 error indicates a conflict in updating condition records in the KONV table due to inconsistent weighting between active and inactive condition records. The solution involves verifying and correcting condition records, reviewing pricing procedures and custom routines, and ensuring consistent condition record maintenance.
  
  If you provide the exact scenario or document type where this error occurs, I can help you with more specific troubleshooting steps.