How To Fix CK468 - No price could be determined for subcontracting

SAP Error Message - Details

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 468

• Message text: No price could be determined for subcontracting

What causes this issue?

The system could not calculate a price for the subcontracting because
none of the valuation strategies in valuation variant &v1& was
successful.

System Response

If the system issues a <ZH>warning message</> or an <ZH>information
message</>, the costing item is used in the cost estimate with a zero
value.
If the system issues an <ZH>error message</>, it sets the status "KF"
(costed with errors).
If the system issues a <ZH>termination message</>, the cost estimate
cannot be processed.

How to fix this error?

If you have authorization for Customizing, check the valuation strategy
for subcontracting in valuation variant &v1&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CK468 - No price could be determined for subcontracting ?

  The SAP error message CK468 ("No price could be determined for subcontracting") typically occurs in the context of material valuation and costing, particularly when dealing with subcontracting processes. This error indicates that the system is unable to determine a valid price for a subcontracted item during the costing run or when trying to create a purchase order for a subcontracting scenario.
  Causes:
  
  
  Missing Price Conditions: The pricing conditions for the subcontracting item may not be maintained in the system. This can happen if the condition records for the relevant pricing procedure are not set up correctly.
  
  
  Incorrect Material Master Data: The material master data for the subcontracted item may be incomplete or incorrect. This includes missing valuation class or price control indicators.
  
  
  Missing Info Records: If there are no purchasing info records for the vendor and material combination, the system will not be able to determine the price.
  
  
  Incorrect Configuration: The configuration settings for the pricing procedure or the valuation area may not be set up correctly, leading to issues in price determination.
  
  
  Currency Issues: If there are discrepancies in currency settings between the vendor, material, and company code, it may lead to price determination issues.
  
  
  Solutions:
  
  
  Check Condition Records: Ensure that the necessary condition records for the pricing procedure are maintained. You can do this using transaction codes like VK11 (Create Condition) or VK12 (Change Condition).
  
  
  Review Material Master Data: Verify that the material master data is complete and correct. Check the valuation class, price control (standard price or moving average), and other relevant fields.
  
  
  Maintain Info Records: Create or update the purchasing info records for the vendor and material combination using transaction code ME11 (Create Info Record) or ME12 (Change Info Record).
  
  
  Check Configuration: Review the configuration settings for the pricing procedure in the customizing settings (transaction code SPRO). Ensure that the pricing procedure is correctly assigned to the relevant purchasing organization and that all necessary conditions are included.
  
  
  Currency Settings: Ensure that the currency settings for the vendor, material, and company code are consistent. Check the currency type in the material master and vendor master records.
  
  
  Costing Run: If the error occurs during a costing run, ensure that all necessary data is available and that the costing variant is correctly configured.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME11, ME12, VK11, VK12, CK11N (Create Cost Estimate), and CK40N (Costing Run).
  Documentation: Refer to SAP documentation or help files for detailed information on pricing procedures and subcontracting processes.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  By following these steps, you should be able to identify the root cause of the CK468 error and implement the necessary solutions to resolve it.