How To Fix SPE213 - Condition & is not allowed as header condition

SPE213 - Overview

• Message type: E = Error

• Message class: SPE -

• Message number: 213

• Message text: Condition & is not allowed as header condition

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SPE213 - Condition & is not allowed as header condition ?

  The SAP error message SPE213 ("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. This error indicates that a specific condition type is being incorrectly assigned or used as a header condition when it is not allowed to be used in that context.
  
  Cause:
  
  Incorrect Condition Type Assignment: The condition type that is causing the error is not configured to be used as a header condition in the pricing procedure.
  Pricing Procedure Configuration: The pricing procedure may not be set up correctly to allow certain condition types at the header level.
  Document Type Settings: The document type being used may not support the condition type in question as a header condition.
  Condition Records: There may be condition records that are incorrectly set up or missing for the condition