CK11N — Create Material Cost Estimate
CK11N is used to calculate a material cost estimate using quantity structure, valuation strategy and costing variant. It is most useful when standard cost, simulation or product-cost analysis needs a new estimate for a material/plant. 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 CK11N — Create 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· 611 words
Esta página ainda não está disponível em português.
Purpose
calculate a material cost estimate using quantity structure, valuation strategy and costing variant. 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
CK11N is typically used when standard cost, simulation or product-cost analysis needs a new estimate for a material/plant. 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
- Confirm material, plant and costing variant.
- Check costing and valuation dates.
- Run the estimate and review quantity structure explosion.
- Analyze missing prices, activities or BOM/routing errors.
- Save only an explainable estimate and compare with prior cost.
Key data objects
These are the fields and business objects that usually explain the result in CK11N. 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 variant — verify the exact value, validity/date context and source of derivation.
- costing date — verify the exact value, validity/date context and source of derivation.
- BOM/routing quantity structure — 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.
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
CK11N remains important for product costing in S/4HANA, while Material Ledger and Universal Journal provide the broader actual-costing/accounting context. 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
- Accepting a successful cost estimate without reviewing warnings. Reconcile the exact document and period before making a configuration change.
- Using the wrong costing date and picking stale prices. Reconcile the exact document and period before making a configuration change.
- Fixing a costing error by manually overriding values instead of correcting master data. 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/ck11nERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.