Lesson 2 of 5
Single cost estimates
9 min
Listen to this lesson
Before you cost hundreds of materials, you cost one. A single material cost estimate with quantity structure is how controllers check a new product, investigate a strange result or show an auditor how a standard was built. In SAP GUI the classic transaction is CK11N (create) and CK13N (display).
Creating the estimate
- HeaderMaterial CMC-ALT-100, plant 1710, costing variant for standard costs
- DatesCosting date from the first day of the new period; quantity structure and valuation dates
- Quantity structureSystem selects the production version, BOM and routing valid on that date
- CostingComponents, activities and overhead valued; lower levels costed first
- ResultCosting log, itemization and cost component view
The estimate is multilevel: if a component is itself produced in-house, it is costed first and its result is used as the component's price. CMC-RTR-200 is purchased, so its price comes from the valuation strategy. Each estimate gets a status; a new estimate without errors has status KA ("costed without errors"), while errors leave it in an error status. SAP's course notes that marking later moves it to VO and release to FR.
Reading the itemization
The itemization shows where each dollar came from: one line per component, activity and overhead. Contoso's Detroit estimate for one alternator looks like this:
| Item | Type | Quantity | Price | Value (USD) |
|---|---|---|---|---|
| CMC-RTR-200 rotor | Material (purchased) | 1 pc | 40.00 | 40.00 |
| Stator, housing, regulator, small parts | Materials (purchased) | per BOM | — | 40.00 |
| Material overhead | Overhead (10% of material) | — | — | 8.00 |
| Assembly labor | Activity, labor hours | 0.5 h | 52.00 / h | 26.00 |
| Test and assembly machine | Activity, machine hours | 0.25 h | 96.00 / h | 24.00 |
| Production overhead | Overhead (24% of labor and machine) | — | — | 12.00 |
| Total | 150.00 |
Itemization of the Detroit standard cost estimate for CMC-ALT-100 (illustrative values).
The cost component view
The same total, grouped differently, is the cost component split: material, material overhead, labor, machine, production overhead. Itemization answers "which item?"; the cost component view answers "what kind of cost?". Lesson 4 explains why this second view matters long after the estimate is released.
| View | Answers | Typical use |
|---|---|---|
| Itemization | Which component, activity or overhead line caused the cost | Investigating a change, explaining a number to engineering |
| Cost component split | What kind of cost: material, labor, machine, overhead | Margin analysis, variance analysis, comparing plants |
| Costing log | What went wrong or was assumed during costing | Finding missing prices, missing routings, invalid dates |
| Task | SAP GUI | SAP Fiori |
|---|---|---|
| Create or display a single estimate with quantity structure | CK11N / CK13N | No full Fiori equivalent; the GUI transactions remain the tool in Private Edition |
| Mark and release a single material's estimate | CK24 (price update) | Release through a costing run in the Fiori app |
| Costing runs: select, cost, analyze, mark, release | CK40N | Manage Costing Runs – Estimated Costs (F1865), with filters and step scheduling across runs |
| Price history and price change documents | CKM3 (material price analysis) | Material ledger analytics apps, depending on release |
Where product cost planning work is done in SAP S/4HANA 2025 Private Edition (verify app availability for your release and roles).
The costing log
Always read the costing log, even when the status is fine. Warnings reveal assumptions: a component with no planned price that fell back to the moving average, a routing operation without an activity price, a production version that was chosen because the preferred one was invalid. A clean status with an ugly log is a standard you will explain to auditors later.
Dates decide which data is used
A single estimate has three dates that matter. The costing date says from when the result is valid; for a standard cost estimate it is the first day of a period, typically the first day of the next fiscal year for an annual update. The quantity structure date decides which BOM and routing versions are read, and the valuation date decides which prices are read. When engineering changes the BOM with effect from March, an estimate with a January quantity structure date will not see the change. Many "wrong" estimates are correct calculations on the wrong date, so record all three dates in every test case.
What would you do?
A new estimate for CMC-ALT-100 in plant 1720 comes out at USD 128 instead of the expected USD 156, status costed without errors. What should Priya look at first?
- CK11N creates and CK13N displays a single material cost estimate with quantity structure.
- Lower-level in-house components are costed first; purchased components are priced by strategy.
- Read the itemization (which item), the cost component view (what kind of cost) and the costing log (what went wrong).
- A plausible-looking status does not prove a plausible value; compare with expectations.
Check your understanding · not graded
Lesson check
1. Which view of a cost estimate shows one line per component and activity?
2. Which status does a newly created error-free standard cost estimate typically have?
3. Why read the costing log even when the status is fine?
4. Which SAP GUI transaction marks and releases the standard estimate of a single material outside a costing run?