FICO Material Ledger Part 2: The Actual Costing Run Step by Step
Full lesson currently free to read · AI practice limits apply separately
Run actual costing at period end with the costing cockpit: selection, determining the sequence, single- and multi-level price determination, revaluation of consumption, and posting closing entries — and what each step means for inventory and COGS.
Visual overview
Explanation
📌 KEY POINTS
✅ The actual costing run is managed in the costing cockpit (CKMLCP) for a set of plants and a period.
✅ Single-level determination assigns each material's own price differences; multi-level rolls them up to finished goods.
✅ The periodic unit price (PUP) is calculated per material and period.
✅ Post closing revalues ending inventory and distributes differences to consumption and COGS.
⚠️ Running post closing before reviewing errors locks in wrong prices for the period.
━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 explained the concepts. Part 2 executes the run.
━━━━━━━━━━━━━━━━━━━━
▶ 1. PREPARATION
Before the run, the period's logistics and invoice postings must be complete, open purchase orders with goods receipts understood, and production orders technically completed or settled as required. Actual costing reflects posted data only, so a late invoice will move into the next period.
━━━━━━━━━━━━━━━━━━━━
▶ 2. SELECTION AND SEQUENCE
In the costing cockpit, a costing run covers selected plants and a period. Selection collects materials; determining the sequence builds the order of processing from raw materials up through semi-finished and finished goods, including cyclic relationships where materials consume each other.
━━━━━━━━━━━━━━━━━━━━
▶ 3. PRICE DETERMINATION
Single-level price determination calculates a periodic unit price from each material's own receipts and differences. Multi-level price determination then passes differences from consumed materials to the materials and orders that consumed them, so finished goods carry the actual cost of their components.
━━━━━━━━━━━━━━━━━━━━
▶ 4. POST CLOSING
Post closing revalues the ending inventory at the actual price — either through price differences remaining on inventory or by changing the price for the next period, depending on settings — and posts the differences on consumption to COGS or other consuming objects. Closing postings can be reversed if the run must be repeated.
━━━━━━━━━━━━━━━━━━━━
▶ 5. REVIEW AND SIGN-OFF
Review the run's materials with errors or unusual price changes, the not-distributed and not-allocated differences, and the effect on COGS by product line. Controlling signs off before the period is closed in the Material Ledger.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Create a costing run for one plant and period in CKMLCP.
- Execute selection, sequence and single-level determination.
- Execute multi-level determination and review errors.
- Run post closing in test and review postings.
✅ CHECKPOINT: the run completes with errors reviewed and closing postings explained.
How the SAP process fits together
SAP PROCESS EXPLORER · Finance: post to report
ERPClimb.comMaterial Ledger and Actual Costing — process breakdown
Topic-specific conceptual flow: how key objects and decisions fit together. SAP configurations and exceptional cases can follow different paths.
Selected process stage
Record
Material Ledger keeps values in several currencies and valuations
What this specific lesson teaches
Run actual costing at period end with the costing cockpit: selection, determining the sequence, single- and multi-level price determination, revaluation of consumption, and posting closing entries — and what each step means for inventory and COGS.
Key lesson principle: The actual costing run is managed in the costing cockpit (CKMLCP) for a set of plants and a period.
Representative SAP learning flow, not a guarantee of system runtime sequence in every scenario. The chapter-specific facts come from the published lesson text.
Real project scenario
A company ran post closing on day three of the close without reviewing the cockpit's error list. Several materials with missing invoices got distorted periodic prices, and COGS for one product line jumped. The run was reversed, invoices posted and the run repeated; the checklist now requires error review before post closing.
Common mistakes
- Running post closing without reviewing errors.
- Late invoices and unsettled orders before the run.
- Ignoring not-distributed differences.
- No controlling sign-off.
Best practices
- Pre-run checklist for postings and settlements.
- Error review before post closing.
- Analyse not-distributed differences.
- Sign-off before closing the period.
Interview angle
Interviewers ask for the steps of the actual costing run in the costing cockpit and what single-level, multi-level price determination and post closing each do.
Frequently asked questions
What are the main steps of an actual costing run?
Selection of materials, determining the sequence from raw materials up to finished goods, single-level price determination, multi-level price determination that passes differences to consuming materials, and post closing.
What does post closing do in the Material Ledger?
It revalues ending inventory at the actual price — through differences left on inventory or a price change for the next period, depending on settings — and posts differences on consumption to COGS or other consuming objects. Closing postings can be reversed if the run must be repeated.
Why does a late invoice move to the next period in actual costing?
Actual costing reflects posted data only. Logistics and invoice postings must be complete before the run, otherwise the differences arrive in the following period.
Practice this lesson
Quick check
0 of 3 questions attempted
1. Which transaction is used for the actual costing cockpit?
2. What does multi-level price determination do?
3. When should post closing be executed?
Check before use: lesson examples are educational, not a guarantee of correctness for your SAP edition or release. Sample code has not been executed on your SAP system. Confirm API availability, syntax, authorizations and business impact in an approved development or test environment.