S/4HANA changeObjectMaterial Ledger is mandatory for inventory valuationModuleMM_P2P

Material Ledger Becomes Mandatory in S/4HANA

In S/4HANA the material ledger is technically active in every client, regardless of whether a customer wants actual costing. Inventory valuation data, including parallel currency and valuation views, is now stored and maintained through material ledger tables rather than as an optional add-on layered over MBEW, and period closing for materials must complete before financial period close.

This page covers what changes when the material ledger moves from an optional ECC add-on to a mandatory, always-on component of inventory valuation in S/4HANA. It focuses on what breaks in custom code, closing schedules and authorizations, and what has to be decided before conversion rather than cleaned up after.

Published 16 Sept 2026· 1,104 words

Classic ECC behaviour

In ECC the material ledger was a separately licensed and separately activated component. Most customers ran inventory valuation with a single local currency, price control set to standard (S) or moving average (V) in the material master accounting view, and variances posted through price difference accounts at goods receipt or invoice receipt. Companies that needed parallel currencies or actual costing (weighted average actual price rolled up through the cost component split) activated the material ledger deliberately, usually per plant or per valuation area, and accepted the extra period-end step of running the actual costing cockpit closing. A large share of ECC installations, particularly smaller or single-currency subsidiaries, never activated it at all. Valuation data for those systems lived entirely in the classic tables (MBEW at plant level, EBEW/QBEW for special stocks), with no parallel currency views and no actual costing settlement step. Custom reports and interfaces built against those tables assumed one currency and one valuation figure per material per period.

S/4HANA behaviour

In S/4HANA the material ledger is technically switched on in every system from the start; there is no toggle to run without it. Every material carries valuation in up to three currency and valuation types, and the ledger tables become the system of record for those views, alongside the classic tables which continue to be populated for compatibility. Actual costing itself (the weighted average price and multi-level cost roll-up) remains a business decision that a customer can leave inactive, but the underlying multi-currency ledger structure and the material ledger period-closing framework are always present and always used for standard valuation, not just for actual costing customers. This means every S/4HANA conversion inherits material ledger period closing as a mandatory step in the month-end sequence, even for organizations that only ever ran standard or moving average price in a single currency in ECC. Reporting and analytics built on the newer CDS-based inventory valuation views read from the material ledger structures rather than assuming a single-currency MBEW figure.

Project impact

The change reaches further than the finance close team.

  • Custom ABAP reports and interfaces that read valuation price or stock value fields directly from classic tables may compile and run but return incomplete or single-currency data once parallel currencies are populated only through the material ledger structures.
  • Month-end closing schedules gain a hard new dependency: the material ledger period must be closed for a plant before the corresponding financial period can close cleanly, which changes the sequencing FI and MM close teams have followed for years.
  • Authorization roles built for classic MM and FI closing staff often omit material ledger transactions entirely, because in ECC only a small actual-costing team ever touched them; those roles now need extending to whoever runs the standard month-end.
  • Goods movement volume that never noticed a performance cost in ECC can show a measurable slowdown once every movement also posts through the material ledger, which becomes visible only at production transaction volume, not in a sandbox with a handful of test postings.
  • Teams that never ran actual costing assume nothing has changed for them and skip material ledger training, then discover during the first live close that a required closing activity now sits between goods movement cutoff and financial period close.

Migration actions

Currency and valuation type configuration is the item that must be settled before conversion, not after; it defines structural properties of the material ledger that are difficult or impossible to change once transactional history has accumulated in S/4HANA.

  • Gate: decide and configure the currencies and valuation types the material ledger will carry for each valuation area before the technical conversion, since this is organizational-structure-level configuration rather than a parameter that can be revisited casually afterward.
  • Gate: run the available ECC-side consistency checks against existing material ledger and classic valuation data before cutover and resolve any mismatches; unresolved inconsistencies convert into S/4HANA and surface later as unexplained valuation differences.
  • Clean up open price differences, work in process, and any parked or incomplete costing runs in ECC before cutover so the ledger starts on a settled base.
  • Decide, plant by plant, whether historical periods need material ledger data reconstructed or whether the ledger simply starts fresh from the conversion cutover date.
  • Rebuild or extend custom reports and interfaces to pull valuation figures from material ledger sources rather than assuming a single-currency classic table value.
  • Extend authorization roles for FI and MM closing staff to cover material ledger period closing transactions.
  • Run a full month-end closing rehearsal with production-like volumes before go-live, specifically to expose the new sequencing dependency and any performance effect on goods movements.

Whose problem this is

This is a joint functional decision with a technical execution tail. Controlling and finance own the currency and valuation type design because it drives cost accounting and group reporting; MM owns the impact on goods movement processes and master data; Basis is not deciding activation, since it is automatic, but does own sizing and performance testing at volume. The close decision-maker should be the controlling lead, not the technical team.

Common pitfalls

The most common misjudgment is treating this as relevant only to companies that plan to use actual costing.

  • Assuming that leaving actual costing switched off means nothing else changes; the multi-currency ledger and its period closing step run regardless of the actual costing setting.
  • Testing period close in a sandbox with a handful of materials and no real volume, then finding the material ledger closing step takes materially longer and blocks financial close on production data.
  • Discovering the mismatch between classic table values and material ledger currency fields only at the first live month end, after custom reports have already been signed off in test with incomplete but plausible-looking numbers.
  • Missing the new closing sequence dependency and letting business users post financial period-close activities before the material ledger period is closed, which then requires a rework of postings.
  • Attempting to disable or bypass parallel currency population after go-live to save processing time; this is not a supported downgrade path and tends to create data inconsistency rather than solving a performance problem.

Related SAP objects

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

Source: ERPClimb — https://erpclimb.com/sap-s4hana-changes/material-ledger-is-mandatory-for-inventory-valuationERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.