How To Fix WV388 - Condition types for SP calc. control missing in calc. schema for pricing

WV388 - Overview

• Message type: E = Error

• Message class: WV - Messages about Sales Price Calculation

• Message number: 388

• Message text: Condition types for SP calc. control missing in calc. schema for pricing

What causes this issue?

In the overview screen for pricing, you can make Customizing settings
to determine the condition type that the standard
<DS:GLOS.3526BC8AAFAB52B9E10000009B38F974>sales price</> and the
promotion price are saved to. For the current item, these are condition
types &V1& and &V2&. Checks on calculation schema &V3& for price
determination found that the schema does not contain these condition
types.

System Response

No sales conditions could be determined for the current item.

How to fix this error?

Check in Customizing for Pricing under
<DS:SIMG.W_ZF_VK_0380.SIMG_OKAL>Control Data for Pricing Table and Data
Backup</>, that condition types &V1& and &V2& are correct for the sales
prices. When doing this, take into account the relevant
<DS:DE.VKALS>sales price calculation schema</> you used.
Alternatively, check calculation schema &V3& for price determination
(definition of the calculation schema for price determination) under
<DS:SIMG.SIMG_CFMENUOLSDFP4>Define and Assign Pricing Procedures</> in
Customizing for Sales and Distribution.
When defining a pricing procedure, note the particular features for the
key fields "Document schema" and "Customer schema" in the Retail
environment (see online documentation for Pricing).
INCLUDE ISR_CUSTOMIZING

Error message extract from SAP system. Copyright SAP SE.

WV388 - Details

• The SAP error message WV388 indicates that there are missing condition types for the special pricing calculation control in the pricing schema. This typically occurs when the pricing procedure does not have the necessary condition types defined for the specific calculation control that is being used.
  
  Cause:
  
  Missing Condition Types: The pricing procedure may not have the required condition types defined for the special pricing calculation.
  Incorrect Configuration: The pricing procedure may not be correctly configured to include the necessary condition types for the specific scenario.
  Custom Pricing Procedures: If you are using a custom pricing procedure, it may not have been set up correctly to handle the special pricing conditions.
  Changes in Configuration: Recent changes in the pricing configuration might have led to the removal or misconfiguration of condition types.
  
  
  Solution:
  
  
  Check Pricing Procedure:
  
  Go to the transaction code V/08 to view and edit pricing procedures.
  Identify the pricing procedure being used for the transaction and check if