SAP Product Costing FAQs: Costing Runs & Reports | ERPCorp
SAP Controlling Conference attendees participating in a presentation

Search Posts

SAP Product Cost Controlling FAQs: Costing Runs and Reports

Hits: 14806

By John Jordan

100 Things You Should Know About Controlling with SAP, second edition, by John JordanSAP Product Cost Controlling troubleshooting often starts with two questions: why did a costing run reuse an existing cost estimate, and why do detailed CO reports show unexpected values? This article explains both issues and points you to the relevant SAP Notes.

This is Tip 100 from 100 Things You Should Know About Controlling with SAP, second edition, by John Jordan. The examples describe classic SAP ERP Controlling behavior; check the applicable SAP Note and your system release before applying the guidance.

 

Table of Contents

How to Find the Relevant SAP Notes

SAP Notes and Knowledge Base Articles provide troubleshooting guidance, explanations of system behavior, and corrections. These resources were historically referred to as OSS Notes.

Open SAP Note 552486: FAQ Product Cost Controlling in SAP for Me with an authorized SAP account. Also review SAP Note 28145: Using Technical Inspection Report RKACSHOW for the reporting analysis described below. Full note content requires the appropriate SAP access.

The two FAQs below summarize the examples in the original book tip. For a broader overview, see our SAP Product Cost Controlling in S/4HANA guide.

Why Is an Existing Cost Estimate Transferred?

Question: Why does the costing run transfer an existing cost estimate even though Always Recost Material is selected in the selection step?

Answer: In the scenario described in the original tip, a cost estimate already exists for the same material and period with the same costing type, costing variant, and costing version. This situation can occur when you create multiple costing runs in the same period.

A different costing run name does not by itself create a different costing version. SAP documents that the costing version distinguishes cost estimates for the same material. When separate estimates are required, review whether a different costing version is appropriate for your process.

Before rerunning costing, compare the existing estimate’s key with the new run’s settings and review the transfer control and processing log. Confirm the applicable behavior in SAP Note 552486 rather than relying on the checkbox alone.

Why Do Detailed CO Reports Show Unexpected Results?

Question: Why does a detailed Controlling report appear to display incorrect results?

Answer: The report may be displaying the data stored for the selected object correctly. The next step is to distinguish an issue in report selection or presentation from an issue in the underlying data.

For classic CO analysis, SAP identifies RKACSHOW as a tool for examining the relevant CO tables for an object, including plan, actual, and target costs, work in process, and variances. Where available and authorized, execute report RKACSHOW through SE38 or transaction RKACSHOW, and select the object you want to analyze.

  1. Confirm the cost object, fiscal year, period, and version used in the report.
  2. Run RKACSHOW for the same object and restrict the selection to the relevant data.
  3. Compare the stored values with the detailed report to narrow down the source of the discrepancy.
  4. Follow SAP Note 28145 for the report’s selection options and interpretation.

RKACSHOW is a diagnostic tool. Its availability and relevance depend on your SAP release and deployment; use the supported analysis tools for your environment.

Conclusion

When costing or reporting results are unexpected, start with the identifying keys and stored data. Review the costing version and transfer settings for reused cost estimates, and compare report results with the underlying CO data before deciding where the problem lies.

Get Help with SAP Product Costing

ERPCorp helps teams investigate costing run behavior, review configuration, and resolve manufacturing cost and Controlling reporting issues.

Explore ERPCorp SAP Consulting Services →

Explore More SAP Controlling Tips

Continue with Controlling with SAP at SAP PRESS, or browse ERPCorp’s SAP books for Product Costing and production variance analysis guides.

Learn from SAP Finance and Controlling Experts

Explore ERPCorp membership for conference session recordings and technical learning resources.

Explore ERPCorp Membership →

Glossary

Costing Run

A collective process for calculating, analyzing, and updating cost estimates for multiple materials.

Costing Type

A component of the costing variant that controls the purpose and behavior of a cost estimate.

Costing Variant

A group of control settings used to calculate a cost estimate.

Costing Version

A key that distinguishes cost estimates for the same material.

OSS Note

A historical term commonly used for an SAP Note.

RKACSHOW

A technical analysis report for inspecting data in relevant CO tables for a selected object.

SAP Note

An SAP support document describing system behavior, troubleshooting guidance, or a correction.

Reference Materials