Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: V1 - Verkaufsbelegbearbeitung
Message number: 213
Message text: Condition & is not allowed as header condition
The condition cannot be entered at header level because it is not
marked in <GL:customizing>Customizing</> as being a header condition.
Delete the condition entered from the document header, or mark the
condition as a header condition (in the detail screen of the
<GL:condition_type>condition type</> in Customizing), if necessary.
INCLUDE 'NA_SYSAD3' OBJECT DOKU ID TX LANGUAGE E
Error message extract from SAP system. Copyright SAP SE.
V1213
- Condition & is not allowed as header condition ?The SAP error message V1213, which states "Condition & is not allowed as header condition," typically occurs in the context of pricing in sales documents (like sales orders or quotations) when there is an issue with the conditions defined in the pricing procedure.
Cause:
- Incorrect Condition Type: The condition type being used is not allowed to be set at the header level. In SAP, certain condition types are defined to be applicable only at the item level, while others can be applied at the header level.
- Pricing Procedure Configuration: The pricing procedure may not be configured correctly to allow the specific condition type at the header level.
- Document Type Settings: The document type settings may restrict certain conditions from being applied at the header level.
- Condition Records: There may be missing or incorrect condition records for the condition type in question.
Solution:
- Check Condition Type: Verify the condition type that is causing the error. Ensure that it is intended to be used at the header level. You can do this by checking the configuration in the pricing procedure.
- Review Pricing Procedure: Go to the configuration of the pricing procedure (Transaction code: SPRO) and check the settings for the condition type. Ensure that it is allowed at the header level if that is your intention.
- Adjust Document Type Settings: Check the settings for the document type you are using. Ensure that it allows the condition type to be applied at the header level.
- Condition Records: Ensure that the necessary condition records for the condition type are maintained correctly. You can check this using transaction codes like VK11 (Create Condition) or VK12 (Change Condition).
- Consult Documentation: If you are unsure about the configuration, refer to SAP documentation or consult with your SAP functional consultant to understand the implications of the condition types and their allowed levels.
Related Information:
If the issue persists after checking these areas, it may be beneficial to engage with your SAP support team or a consultant who can provide deeper insights into your specific configuration and business processes.
Get instant SAP help. Sign up for our Free Essentials Plan.
V1212
No pricing procedure could be determined
What causes this issue? The appropriate pricing procedure could not be determined because no entry with keys '&V1&' '&V2&a...
V1211
New valuation carried out for the document
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
V1214
Condition & is not allowed as item condition
What causes this issue? The condition cannot be entered at item level because it is not marked in <GL:customizing>Customizing</> as being...
V1215
Requirements are not fulfilled for condition &1
What causes this issue? The requirements have not been fulfilled for <DS:GLOS.5CF3FCDB46F61EE493A965DC5E0E023C>condition</> &V1&....
Click on this link to search all SAP messages.