How To Fix WTYMP036 - Pricing error: condition &1 was not added

WTYMP036 - Overview

• Message type: E = Error

• Message class: WTYMP - Warranty Mass Change

• Message number: 036

• Message text: Pricing error: condition &1 was not added

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 WTYMP036 - Pricing error: condition &1 was not added ?

  The SAP error message WTYMP036, which states "Pricing error: condition &1 was not added," typically occurs during the pricing determination process in sales documents, such as sales orders or quotations. This error indicates that a specific pricing condition (denoted by &1) could not be applied or added to the pricing procedure for the transaction.
  Causes:
  
  
  Missing Condition Records: The condition type referenced in the error message may not have any valid condition records in the system for the specific combination of key fields (e.g., customer, material, sales area).
  
  
  Incorrect Pricing Procedure: The pricing procedure assigned to the sales document may not include the condition type in question, or the condition type may be set up incorrectly.
  
  
  Condition Exclusion: The condition type may be excluded from the pricing procedure due to configuration settings or specific conditions that prevent it from being applied.
  
  
  Master Data Issues: There may be issues with the master data, such as customer