CK13N — Display Material Cost Estimate
CK13N is used to display a material cost estimate with itemization and cost component split without recalculating it. It is most useful when explaining standard cost, comparing costing runs or tracing which BOM, routing and prices contributed to cost. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains CK13N — Display Material Cost Estimate — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 609 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
display a material cost estimate with itemization and cost component split without recalculating it. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
CK13N is typically used when explaining standard cost, comparing costing runs or tracing which BOM, routing and prices contributed to cost. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Open the exact estimate by material/plant and costing date.
- Review status and costing variant.
- Drill into itemization for material/activity inputs.
- Compare component split with the accounting question.
- Cross-check master-data changes made after the estimate date.
Key data objects
These are the fields and business objects that usually explain the result in CK13N. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- material and plant — verify the exact value, validity/date context and source of derivation.
- costing version/date — verify the exact value, validity/date context and source of derivation.
- itemization — verify the exact value, validity/date context and source of derivation.
- cost component split — verify the exact value, validity/date context and source of derivation.
- quantity structure — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
CK13N remains a common product-cost analysis transaction in S/4HANA. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Comparing estimates from different dates/variants as if they were identical. Reconcile the exact document and period before making a configuration change.
- Reading current BOM/routing as if it necessarily matches the historical cost estimate. Reconcile the exact document and period before making a configuration change.
- Looking only at total cost and missing the component causing variance. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is Finance/Controlling, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ck13nERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.