How To Fix 88164 - No condition type assigned to combination &1/&2

SAP Error Message - Details

• Message type: E = Error

• Message class: 88 - REA Processing

• Message number: 164

• Message text: No condition type assigned to combination &1/&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 88164 - No condition type assigned to combination &1/&2 ?

  The SAP error message 88164, "No condition type assigned to combination &1/&2," typically occurs in the context of pricing in SAP, particularly when working with sales documents, purchase orders, or other transactions that involve condition records.
  Cause:
  This error indicates that the system is unable to find a valid condition type for the specified combination of key fields (represented by &1 and &2). The key fields usually refer to specific criteria such as:
  
  &1: This could be a combination of fields like material number, customer number, or other relevant identifiers.
  &2: This could refer to the pricing procedure or other relevant criteria.
  
  The absence of a condition type means that the pricing procedure cannot determine how to calculate the price for the transaction, leading to this error.
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the condition records for the relevant condition type are maintained.
  Ensure that there are condition records for the combination of the key fields that are causing the error.
  
  
  
  Verify Pricing Procedure:
  
  Check the pricing procedure assigned to the sales document or purchase order. You can do this by navigating to the relevant configuration settings in SPRO (SAP Project Reference Object).
  Ensure that the pricing procedure is correctly configured to include the necessary condition types.
  
  
  
  Maintain Condition Types:
  
  If the condition type is missing, you may need to create or maintain it. Use transaction V/06 to maintain condition types and ensure they are assigned to the relevant pricing procedure.
  
  
  
  Check Access Sequence:
  
  Verify the access sequence for the condition type. The access sequence determines how the system searches for condition records. Ensure that the access sequence is correctly set up to include the necessary fields.
  
  
  
  Review Master Data:
  
  Ensure that the master data (like customer master, material master, etc.) is correctly maintained and that the relevant fields are populated.
  
  
  
  Consult Documentation:
  
  If you are unsure about the configuration or the specific condition types, refer to SAP documentation or consult with your SAP functional consultant.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK11, VK12: For creating and changing condition records.
  V/06: For maintaining condition types.
  SPRO: For accessing configuration settings.
  
  
  
  Pricing Procedure: Understand how pricing procedures work in SAP, including how they are assigned to sales documents and how condition types are processed.
  
  
  Access Sequences: Familiarize yourself with how access sequences are defined and how they impact the retrieval of condition records.
  
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary changes to resolve it. If the issue persists, consider reaching out to your SAP support team for further assistance.