Do you have any question about this error?
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
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.
When you save in Sales Price Calculation, the system is unable to
generate any condition records for condition type &V1&.
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
- No main condition exists for supplementary condition &1 ?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 the specific conditions.
Solution:
- Check Main Conditions: Verify that the main condition (e.g., base price) exists for the item in question. You can do this by checking the pricing details in the sales document.
- Review Condition Records: Ensure that the condition records for both the main and supplementary conditions are correctly maintained in the system. You can do this using transaction codes like
VK11
(Create Condition) orVK12
(Change Condition).- Adjust Pricing Procedure: If necessary, review and adjust the pricing procedure configuration in the customizing settings (transaction code
SPRO
). Ensure that the supplementary condition is correctly linked to its main condition.- Document Type Configuration: Check the configuration of the document type being used to ensure it supports the pricing conditions you are trying to apply.
- Consult SAP Notes: Look for any relevant SAP Notes that might address this specific error or provide additional guidance.
Related Information:
VK31
(Maintain Condition Records), V/08
(Pricing Procedure), and V/06
(Condition Types) for managing pricing conditions.If you continue to experience issues after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in pricing and sales processes.
Get instant SAP help. Start your 7-day free trial now.
WV405
Standard condition type and promotion condition type are identical
What causes this issue? You have defined the same condition type to update both standard sales prices and promotion sales prices. This can cause prob...
WV404
No condition type has been maintained for updating promotion prices
What causes this issue? You have maintained a standard condition type, but you have not yet maintained a condition type for updating promotion prices...
WV407
There is more than one main condition 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 c...
WV408
Condition type &1 is used in more than one place in schema &2
What causes this issue? In the control data for sales price calculation schema &V2&, condition type &V1& is assigned to more than one...
Click on this link to search all SAP messages.