How To Fix WV187 - No pricing control exists for key &1 &2

WV187 - Overview

• Message type: E = Error

• Message class: WV - Messages about Sales Price Calculation

• Message number: 187

• Message text: No pricing control exists for key &1 &2

What causes this issue?

There is no entry in sales price calculation control for the key:
calculation schema &V1& and list field &V2&. This entry has to exist
for the basic purchase price to be saved.

System Response

If purchase price conditions are to be created via the sales price
calculation function (in follow-on processing for a promotion, for
example) no prices will be calculated for the current item.
If prices are being calculated for plant groups, the system will be
unable to save the basic purchase price for any of the plants that
belong to the distribution chain of the reference plant.

How to fix this error?

Check your Customizing settings.
Enter the control parameters you require for the above key in the
<DS:SIMG.W_ZF_VK_0380.SIMG_OKAL>Sales price calculation control</>
section of Customizing for Pricing, making sure that condition tables
suitable for saving at the relevant pricing levels are maintained in
Customizing for the condition types you have entered in the fields
'Condition type' and (if appropriate) 'Promotion condition type'.
Alternatively, check that you have the correct calculation schema.
INCLUDE ISR_CUSTOMIZING

Error message extract from SAP system. Copyright SAP SE.

WV187 - Details

• The SAP error message WV187 "No pricing control exists for key &1 &2" typically occurs in the context of pricing and billing in SAP, particularly when dealing with condition records in the pricing procedure. This error indicates that the system cannot find a valid pricing control record for the specified key, which usually consists of a combination of the condition type and the relevant key fields (like material, customer, etc.).
  Causes:
  
  Missing Condition Records: The most common cause is that there are no condition records defined for the specified condition type in the pricing procedure.
  Incorrect Configuration: The pricing procedure may not be correctly configured to include the necessary condition types or keys.
  Data Inconsistencies: There may be inconsistencies in the master data (like customer or material master) that prevent the system from finding the appropriate pricing records.
  Condition Exclusion: The condition type may be excluded from the pricing procedure for the specific transaction or