How To Fix WV406 - No main condition exists for supplementary condition &1

WV406 - Overview

• Message type: E = Error

• Message class: WV - Messages about Sales Price Calculation

• Message number: 406

• Message text: No main condition exists for supplementary condition &1

What causes this issue?

Condition type &V1& does not have its own access sequence, which means
that it should be updated as a supplementary condition relating to a
main condition. The control parameters for sales price calculation
schema &V2& do not contain a condition type that could be used as a
main condition, however.

System Response

When you save in Sales Price Calculation, the system is unable to
generate any condition records for condition type &V1&.

How to fix this error?

Check the control data for sales price calculation schema &V2& and find
all the condition types with access sequences. These are the condition
types that can be used as main conditions.
If you would like condition type &V1& to be updated as a supplementary
condition relating to one of these main conditions, enter condition
type &V1& in the supplementary calculation schema for the relevant main
condition (Customizing for price determination).

Error message extract from SAP system. Copyright SAP SE.

WV406 - Details

• The SAP error message WV406 "No main condition exists for supplementary condition &1" typically occurs in the context of pricing and conditions in sales documents, such as sales orders or quotations. This error indicates that a supplementary condition (like a discount or surcharge) is being referenced, but there is no corresponding main condition (like the base price) that it can be applied to.
  
  Cause:
  
  Missing Main Condition: The primary reason for this error is that the main condition, which the supplementary condition is supposed to modify or complement, does not exist in the pricing procedure for the document.
  Incorrect Condition Records: There may be issues with the condition records in the pricing procedure, such as missing or incorrectly configured records.
  Pricing Procedure Configuration: The pricing procedure may not be set up correctly to allow for the supplementary condition to be applied.
  Document Type Issues: The document type being used may not be configured to support