How To Fix CK736 - No cost estimate found for procurement alternative

CK736 - Overview

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 736

• Message text: No cost estimate found for procurement alternative

What causes this issue?

For material/plant &v1&, no cost estimate could be found for the
<DS:GLOS.352A616EC1035CD5E10000009B38F974>procurement alternative</>
with <DS:GLOS.3526C38DAFAB52B9E10000009B38F974>production version</>
&v2&.
There are various possible causes for this, as follows:
You have not created a procurement alternative for production version
&V2&.
Example:
At the beginning of the year, you create a
<DS:GLOS.3526B72EAFAB52B9E10000009B38F974>mixed cost estimate</> with
procurement alternatives A und B. Procurement alternative A includes
production version 1, while procurement alternative B includes
production version 2. During the fiscal year, you enter production
version 3, for which you create a
<DS:GLOS.3526B6F2AFAB52B9E10000009B38F974>product cost collector</>.
When calculating actual costs at period-end closing in Cost Object
Controlling, the system attempts to access the cost estimate for the
procurement alternative. However, there is no procurement alternative
containing production version 3.
A cost estimate was not created for production version &V2&. The reason
for this is that the lot size range entered in the production version
does not agree with the lot size entered in the procurement
alternative.
Example:
The ratio between procurement alternative A and procurement alternative
B in a mixed cost estimate for material X should be 1:9.
Procurement alternative A contains production version 1.
A lot size range of 100 - 1000 has been entered for production version
1. No lot size has been entered in the procurement alternative.
Procurement alternative A contains production version 2.
A lot size range of 1 - 100 has been entered for production version 2.
No lot size has been entered in the procurement alternative.
You create a mixed cost estimate for the material with a lot size of 1.
The system costs production version 2. Production version 1 is not
costed, because the lot size range of the production version does not
correspond to the costing lot size of the procurement alternative.
Therefore, procurement alternative A has a cost estimate that is based
on production version 2.
This would also occur if a lot size of 500 were entered in procurement
alternative A, and the costing lot size of the procurement alternative
were 100.

System Response

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

How to fix this error?

Check to see whether a cost estimate already exists for the procurement
alternative.
Check the lot sizes in the production version and in the procurement
alternative.
If necessary, create a procurement alternative and/or a cost estimate
for the procurement alternative.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CK736 - No cost estimate found for procurement alternative ?

  The SAP error message CK736 "No cost estimate found for procurement alternative" typically occurs in the context of cost estimation for materials in SAP. This error indicates that the system could not find a valid cost estimate for the specified procurement alternative of a material. Here are the potential causes, solutions, and related information for this error:
  Causes:
  
  Missing Cost Estimate: There may not be a cost estimate created for the material in the specified valuation area or plant.
  Incorrect Procurement Alternative: The procurement alternative specified may not be valid or may not have an associated cost estimate.
  Costing Variant Issues: The costing variant used may not be set up correctly or may not be applicable for the material.
  Valuation Class Issues: The valuation class assigned to the material may not be linked to a valid cost estimate.
  Data Inconsistencies: There may be inconsistencies in the master data related to the material, such as missing or