S/4HANA changeObjectInventory valuation and the actual costing run on S/4HANAModuleFI_FICO

Material Ledger Becomes Mandatory in S/4HANA

In ECC the material ledger was optional and most customers ran standard price control without it. On S/4HANA the material ledger is always active and cannot be switched off, because inventory valuation is now tied into the universal journal. The periodic actual costing run, formerly an optional multi-level costing exercise, becomes a structural part of every period close.

This page covers the shift from optional material ledger activation in ECC to mandatory, always-on material ledger in S/4HANA, and what that does to the periodic actual costing run. It focuses on what breaks in reporting, interfaces, and period close scheduling when a system that never ran actual costing suddenly has to.

Published 16 Sept 2026· 1,116 words

Classic ECC behaviour

In ECC, price control on the material master was almost always set to standard price (S), with actual costing and the material ledger treated as an optional add-on requiring separate activation per valuation area and per company code. Many customers never turned it on. Without it, goods movements posted at standard price, and any variance between standard and actual purchase or production cost landed in price difference accounts on the P&L, never unwound at a material level. Where the material ledger was activated, the periodic actual costing run (commonly run through CKMLCP) calculated a weighted average actual cost per material at period end, using single- or multi-level price determination that rolled cost variances down through the production structure to consuming materials. This run was a distinct, schedulable closing step that controlling teams either ran diligently every period or, in practice, let lapse for months at a time with no immediate consequence because nothing downstream depended on it structurally.

S/4HANA behaviour

Material ledger is active in every S/4HANA system from the start and cannot be deactivated, because inventory valuation data is now part of the universal journal rather than a separate parallel structure bolted onto it. This is true even for clients that intend to keep pure standard price control with no multi-currency or multi-valuation requirement; the ledger runs underneath regardless. The periodic actual costing run still exists as a distinct activity, still using the same underlying logic of multi-level price determination and cost roll-up, but it now feeds figures directly into the universal journal rather than into a side ledger that finance could largely ignore. Parallel valuation views (legal, group, profit centre) that used to require bespoke costing logic are now natively supported through material ledger currency and valuation types. For a system converting from an ECC configuration that never activated material ledger, this means running actual costing for the first time in production, sizing it, scheduling it, and building the controlling team's competence to interpret its output, none of which existed before.

Project impact

The practical damage is concentrated in three places: period-end scheduling, reporting built on old assumptions, and authorisations for teams that never touched this area before.

Custom reports and reconciliation checks that assume static standard price valuation start showing unexplained deltas once actual costing populates additional valuation figures into the same postings.
Interfaces or extracts reading legacy material ledger period and currency tables can break or silently return incomplete data if they were built against structures that assumed the ledger was optional or inactive.
Controlling teams that never scheduled a costing run now have a mandatory batch job in the close calendar; a missed or failed run blocks downstream settlement and leaves work-in-process and variance figures in an inconsistent state for the period.
Authorisation roles for finance and controlling users need the relevant costing transactions added; teams that historically had no need for them are locked out the first time they need to investigate a failed run.
Data volumes rise because every material now carries multi-currency and multi-valuation entries per period, which changes the runtime profile of the closing job and any downstream extracts.
Month-end close windows extend because settlement and allocation steps that used to run independently of costing now have a hard dependency on the actual costing run completing first.

Migration actions

The first action is not optional cleanup, it is a pre-conversion gate: establish whether material ledger is active in the source ECC system and at what valuation area scope, because if it is not active, activation and the associated design decisions have to happen as part of the conversion project, not after go-live.

Run the standard readiness checks against the source system to confirm material ledger status and flag any valuation areas not yet covered.
Decide the parallel valuation approach (currency types, valuation views such as legal, group, profit centre) before conversion; this configuration is expensive to change once live data has accumulated against it.
For systems activating material ledger for the first time, plan the historical data conversion and opening balance build for existing inventory, since actual cost figures cannot simply appear retroactively.
Test the actual costing run against production-representative volumes, not a sample dataset, to size the batch window realistically.
Rebuild the period-end schedule so the costing run sits as a hard predecessor to settlement and allocation steps.
Audit custom reports, interfaces, and extracts that touch inventory valuation and rework anything built against the assumption of a static standard price with no material ledger underneath.
Update authorisation roles for controlling and finance users who will now need to run, monitor, and troubleshoot the costing job.
Train the controlling team on interpreting multi-level price determination output, since many will be seeing it in a live environment for the first time.

Whose problem this is

The valuation approach and parallel currency/valuation type design is a controlling and finance decision, owned by the finance lead, because it cannot be easily reversed once postings accumulate against it. Sizing the batch job, adjusting interfaces, and fixing broken extracts is technical work owned by the conversion team, but it only starts once finance has fixed the design.

Common pitfalls

The most common late discovery is a project team assuming that because the business never used actual costing in ECC, the topic does not apply to their conversion; it applies regardless, because the ledger runs underneath every S/4HANA system whether or not anyone asked for it.

Testing the costing run against a handful of materials passes cleanly, then the production run against the full material master exceeds the available batch window and pushes the entire close out.
Activating material ledger with a valuation area scope that omits plants added later requires a rework of the setup rather than a simple extension.
Interfaces built against classic price-difference postings keep running without error but silently stop reflecting the true actual cost movement, and nobody notices until a reconciliation months later.
Once currency types and valuation views are fixed at activation, changing them later is close to a re-implementation, not a configuration tweak, which teams discover only when the business asks for an additional valuation view post go-live.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-s4hana-changes/inventory-valuation-and-the-actual-costing-run-on-s-4hanaERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.