How To Fix PRC_PRI801 - Pricing error: Mandatory condition &1 (&2) is missing

PRC_PRI801 - Overview

• Message type: E = Error

• Message class: PRC_PRI - Messages for Pricing Engine

• Message number: 801

• Message text: Pricing error: Mandatory condition &1 (&2) is missing

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 PRC_PRI801 - Pricing error: Mandatory condition &1 (&2) is missing ?

  The SAP error message PRC_PRI801 indicates that there is a mandatory pricing condition that is missing in the pricing procedure for a transaction. This error typically occurs during the pricing determination process in sales and distribution (SD) or materials management (MM) modules when the system expects a specific condition type to be present but cannot find it.
  
  Cause:
  
  Missing Condition Record: The required condition type (e.g., discounts, surcharges, taxes) has not been maintained in the condition records.
  Incorrect Pricing Procedure: The pricing procedure assigned to the document may not include the necessary condition types.
  Condition Exclusion: The condition type may be excluded from the pricing procedure due to configuration settings.
  Master Data Issues: The master data (customer, material, etc.) may not have the necessary pricing information set up.
  Document Type Configuration: The document type being used may not be configured to use the required pricing conditions.
  
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or