How To Fix CPE_ERP019 - Requested combination of reference condition data not found

SAP Error Message - Details

• Message type: E = Error

• Message class: CPE_ERP - CPE - Messages for ERP

• Message number: 019

• Message text: Requested combination of reference condition data not found

What causes this issue?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

An error occurred during commodity formula evaluation. For at least one
of the requested reference condition data of item &V1&, the system could
not find any record.

How to fix this error?

Check that the entered combination of document number, item number and
condition type for the reference condition data are correct:
&V2& &V3&
If you refer to conditions from other documents, the system reads from
table of the conditions (PRCD_ELEMENTS) and the entry must exist there.
If you refer to conditions from this document, the system reads the
internal representation and the entry must be available in this
document.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CPE_ERP019 - Requested combination of reference condition data not found ?

  The SAP error message CPE_ERP019 ("Requested combination of reference condition data not found") typically occurs in the context of condition records in SAP, particularly when dealing with pricing, discounts, or other condition-based functionalities in the SAP ERP system. This error indicates that the system is unable to find the specific combination of condition data that is required for processing a transaction.
  Causes:
  
  Missing Condition Records: The most common cause is that the required condition records for the specific combination of key fields (like customer, material, pricing type, etc.) do not exist in the system.
  Incorrect Key Combinations: The key fields used in the transaction may not match any existing condition records. This can happen if there are typos or if the wrong values are being used.
  Data Inconsistencies: There may be inconsistencies in the master data (like customer or material master) that prevent the system from finding the correct condition records.
  Condition Type Configuration: The condition type may not be properly configured or activated in the system.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access certain condition records.
  
  Solutions:
  
  Check Condition Records: Use transaction codes like VK11 (Create Condition), VK12 (Change Condition), or VK13 (Display Condition) to check if the required condition records exist for the specific combination of keys.
  Verify Key Combinations: Ensure that the key fields used in the transaction match the key fields defined in the condition records. This includes checking customer numbers, material numbers, and any other relevant fields.
  Review Master Data: Check the master data for any inconsistencies or errors that might affect the condition records. Ensure that the customer and material data are correctly maintained.
  Check Configuration: Review the configuration of the condition types in the pricing procedure to ensure they are set up correctly and are active.
  Consult with SAP Support: If the issue persists, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any known issues related to this error message.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13, and others related to pricing and conditions.
  SAP Documentation: Refer to SAP Help documentation for detailed information on condition records and pricing procedures.
  SAP Notes: Search for specific SAP Notes related to the error message CPE_ERP019 for any patches or updates that may address the issue.
  User Authorizations: Ensure that the user has the necessary authorizations to view and manage condition records.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.