By John Jordan
SAP Note 552486 covers frequently asked questions about Product Cost Controlling (CO-PC). This article focuses on two troubleshooting questions from Tip 100 of 100 Things You Should Know About Controlling with SAP, second edition.
Learn what to check when a costing run in CK40N reuses a cost estimate and how to investigate unexpected results in a Cost Object Controlling report using RKACSHOW.
Why Does CK40N Reuse a Cost Estimate?
A costing run can transfer an existing estimate even when Always Recost Material is selected. As Tip 100 explains, one cause is an estimate that already exists under the same key, such as for the same material, period, costing type, costing variant, and costing version. This can occur when you run costing more than once in the same period.
- In CK13N, check whether a matching estimate already exists. Compare the material, plant, costing date or period, costing variant, and version with the settings in your run.
- Review the costing run log and the transfer control assigned to your costing variant to see where existing costing data can be reused.
- If you need a separate comparison estimate, test a different costing version in a controlled run and verify the result before marking or releasing a standard cost estimate.
How Do You Investigate Unexpected CO Report Results?
Start with the same controlling object, period, currency, and value type in both reports. For example, a report showing target costs will differ from one showing actual costs even for the same production order.
Where available and authorized in SAP GUI, run RKACSHOW directly or via SE38 and select the controlling object you want to investigate. The report lets you inspect underlying CO data for that object, including plan, actual, and target costs, work in process, results analysis, and variances. See SAP Note 28145 and SAP’s Cost Object Controlling supportability tools.
Where to Find SAP Note 552486
Open SAP Note 552486 in SAP for Me or search for the note number in the Knowledge area of SAP for Me. Sign in with an SAP support account that has access to the note. Tip 100 describes classic SAP GUI workflows. Check the note’s applicability and transaction availability for your release and deployment.