How To Fix WS383 - Error in calculation schema &, different gross values exist

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 383

• Message text: Error in calculation schema &, different gross values exist

What causes this issue?

The gross value you entered and the value determined in price
determination are not the same.

System Response

Correct the settings of schema &V1& in Customizing.

How to fix this error?

Check whether the condition types have been added and this has changed
how subtotals are determined. Ensure that the gross value is only made
up of conditions that reflect the net value and of tax conditions.

Procedure for System Administrators

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 WS383 - Error in calculation schema &, different gross values exist ?

  The SAP error message:
  WS383 Error in calculation schema &, different gross values exist
  
  Cause:
  This error occurs during the pricing or billing process when the calculation schema (pricing procedure) results in inconsistent or conflicting gross values for the same item or condition. Essentially, the system detects that multiple gross values are being calculated for the same item or condition, which should not happen because the gross value must be unique and consistent.
  Common causes include:
  
  Incorrect or conflicting condition records/prices in the pricing procedure.
  Multiple condition types affecting the same base value but calculated differently.
  Custom pricing routines or user exits that produce inconsistent results.
  Rounding differences or currency conversion issues leading to different gross values.
  Incorrect configuration in the calculation schema (pricing procedure), such as condition types with overlapping or conflicting calculation rules.
  
  
  Solution:
  To resolve the WS383 error, follow these steps:
  
  
  Check the Pricing Procedure:
  
  Review the calculation schema assigned to the document.
  Verify that condition types are correctly defined and do not overlap or conflict.
  Ensure that no condition types are causing multiple gross values for the same item.
  
  
  
  Analyze Condition Records:
  
  Check the condition records for the involved condition types.
  Look for duplicate or conflicting condition records that might cause different gross values.
  
  
  
  Review Custom Pricing Routines:
  
  If user exits or custom routines (e.g., USEREXIT_PRICING_PREPARE_TKOMK, USEREXIT_PRICING_CALC_TKOMP) are implemented, debug them to ensure they do not produce inconsistent gross values.
  
  
  
  Check for Rounding or Currency Issues:
  
  Verify that rounding rules are consistent.
  Check currency conversion settings if multiple currencies are involved.
  
  
  
  Debug the Pricing Procedure:
  
  Use transaction VK13 to display the pricing procedure.
  Use transaction VA02 or VF02 to reproduce the error and debug the pricing calculation.
  Use the pricing analysis tool (e.g., pricing log) to identify where the conflicting gross values arise.
  
  
  
  Adjust Configuration:
  
  Correct any inconsistencies in the pricing procedure.
  Remove or adjust conflicting condition types.
  Ensure that the calculation schema logic leads to a single gross value per item.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VA01/VA02 - Sales order creation/change (where pricing is calculated)
  VF01/VF02 - Billing document creation/change
  VK11/VK12/VK13 - Condition records maintenance/display
  V/08 - Pricing procedure configuration
  
  
  
  SAP Notes:
  
  Check SAP OSS notes for WS383 or related pricing errors for any known bugs or patches.
  
  
  
  SAP Help:
  
  SAP Help Portal documentation on pricing procedures and condition technique.
  
  
  
  
  Summary:
  The WS383 error indicates conflicting gross values in the pricing calculation schema. The root cause is usually configuration or data inconsistencies in the pricing procedure or condition records. Careful review and correction of the pricing procedure, condition records, and any custom pricing logic will resolve the issue. Debugging the pricing process helps pinpoint the exact cause of the conflict.