How To Fix PRCG_CNDNRECORD_API065 - Condition type ô&1ö not included in pricing procedure ô&2ö

PRCG_CNDNRECORD_API065 - Overview

• Message type: E = Error

• Message class: PRCG_CNDNRECORD_API - Messages for the Condition Read API

• Message number: 065

• Message text: Condition type ô&1ö not included in pricing procedure ô&2ö

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 PRCG_CNDNRECORD_API065 - Condition type ô&1ö not included in pricing procedure ô&2ö ?

  The SAP error message PRCG_CNDNRECORD_API065 indicates that a specific condition type (represented by &1) is not included in the pricing procedure (represented by &2). This error typically occurs during the pricing determination process in sales documents, purchase orders, or other transactions where pricing is calculated based on defined conditions.
  
  Cause:
  
  Missing Condition Type: The specified condition type is not defined in the pricing procedure that is being used for the transaction.
  Incorrect Configuration: The pricing procedure may not be correctly configured to include all necessary condition types for the specific transaction type or sales area.
  Transaction Type Mismatch: The transaction type being processed may not be compatible with the pricing procedure that is currently assigned.
  
  
  Solution:
  
  
  Check Pricing Procedure Configuration:
  
  Go to the transaction code V/08 (for sales) or V/06 (for purchasing) to view and edit the pricing procedure.
  Ensure that the condition type &1 is included in the pricing procedure &2.
  If it is not included, you can