How To Fix CKBK016 - Price could not be determined from purchasing info record &1

SAP Error Message - Details

• Message type: E = Error

• Message class: CKBK - Messages of the Valuation Functions

• Message number: 016

• Message text: Price could not be determined from purchasing info record &1

What causes this issue?

You were unable to determine a price at valuation date &v3& from
<DS:GLOS.3526BFD2AFAB52B9E10000009B38F974>Purchasing information record
</> &v1& with <DS:GLOS.3526BFD3AFAB52B9E10000009B38F974>Purchasing
organization</> &v2&.

System Response

To the extent that this is possible, the valuation is carried out using
the next valuation strategy.

How to fix this error?

Check the purchasing information record (<DS:TRAN.ME13>Display
information record</>). In particular check whether there is a valid
price as at &v3&.
Check the <DS:GLOS.3526B752AFAB52B9E10000009B38F974>Valuation variant
</> and change the valuation strategy there as appropriate.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CKBK016 - Price could not be determined from purchasing info record &1 ?

  The SAP error message CKBK016, which states "Price could not be determined from purchasing info record &1," typically occurs when the system is unable to find a valid price for a material in the purchasing info record (PIR) during a procurement process. This can happen in various scenarios, such as when creating a purchase order or a purchase requisition.
  Causes:
  
  Missing Info Record: There is no purchasing info record for the material and vendor combination.
  Invalid Info Record: The purchasing info record exists but is not valid for the specific conditions (e.g., validity period, plant, or purchasing organization).
  Price Conditions: The price conditions in the info record may not be set up correctly or may be missing.
  Material Master Data: The material master data may not be set up correctly, leading to issues in determining the price.
  Vendor Master Data: The vendor master data may not be correctly linked to the purchasing info record.
  Purchasing Organization: The purchasing organization may not be correctly assigned or may not have the necessary authorizations.
  
  Solutions:
  
  
  Check Purchasing Info Record:
  
  Go to the transaction code ME13 (Display Purchasing Info Record) and check if the info record exists for the specific material and vendor.
  Ensure that the info record is valid for the relevant purchasing organization and plant.
  
  
  
  Validate Info Record Conditions:
  
  Ensure that the price conditions are correctly maintained in the info record. Check for any missing or incorrect entries.
  
  
  
  Review Material Master Data:
  
  Use transaction code MM03 (Display Material) to check the material master data. Ensure that the material is set up correctly and is assigned to the appropriate purchasing group.
  
  
  
  Check Vendor Master Data:
  
  Use transaction code XK03 (Display Vendor) to verify that the vendor is correctly set up and linked to the purchasing info record.
  
  
  
  Check Validity Period:
  
  Ensure that the validity period of the purchasing info record covers the date of the transaction you are trying to execute.
  
  
  
  Consult with Purchasing Team:
  
  If you are unable to resolve the issue, consult with your purchasing team or SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  ME13: Display Purchasing Info Record
  MM03: Display Material Master
  XK03: Display Vendor
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  Documentation: Review SAP documentation for purchasing processes and info records to ensure compliance with best practices.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.