MM / P2Parchitect

MM Valuation Part 4: Enterprise Valuation Strategy, Governance and S/4HANA

Key takeaway

Design valuation for an enterprise: valuation level and valuation areas, price control policy by material type, material ledger currencies and valuations (legal, group, profit center), actual costing decision, valuation class design, migration of stock values and governance of prices.

Explanation

📌 KEY POINTS
✅ Policy first: price control by material type, valuation class structure, price change authority.
✅ Material ledger currencies (company code, group, others) and parallel valuations support group and transfer pricing reporting.
✅ Actual costing is a business decision (effort vs accuracy).
✅ Stock migration must reconcile quantities and values with finance.
⚠️ Inconsistent valuation designs across plants make group reporting and transfer pricing hard.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 3 covered edge cases. Now strategy.

━━━━━━━━━━━━━━━━━━━━
▶ 1. POLICY

Price control per material type; valuation classes per balance sheet structure.

━━━━━━━━━━━━━━━━━━━━
▶ 2. MATERIAL LEDGER DESIGN

Currencies and valuation views; group/profit center valuation if needed.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ACTUAL COSTING

Benefits, effort, closing impact.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MIGRATION

Stock quantities and values; reconciliation; price consistency.

━━━━━━━━━━━━━━━━━━━━
▶ 5. GOVERNANCE

Price change approvals, periodic review, KPIs (PRD, revaluations).

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Define valuation policy with finance.
Design ML currencies/valuations.
Plan migration and reconciliation.
Set governance.

✅ CHECKPOINT: every plant follows the same valuation policy and reconciles to finance.

Code example

ABAP Code

===== STEP 1: policy example =====FERT/HALB: S (cost estimates) | ROH: S or V per category | HAWA: V | NLAG: non-valuated ===== STEP 2: ML design =====Currencies: company code (local), group currency, optional additional | parallel valuation: group/profit center (if needed) ===== STEP 3: migration =====Stock load per valuation area → value reconciliation with GL → price checks

Real project scenario

A multinational chemicals company undergoing an ECC consolidation found each plant used different price control for the same materials, making transfer pricing and group reporting inconsistent. A global valuation policy, harmonized valuation classes and group currency in the material ledger resolved it during migration.

Common mistakes

Plant-by-plant policies.
Ignoring group currency needs.
Migrating values without reconciliation.
Actual costing without closing capacity.
No price governance.

Best practices

Define global policy.
Design ML currencies with finance.
Reconcile migrations.
Decide actual costing deliberately.
Govern price changes.

Interview angle

Questions: "How would you design valuation for a global company?", "What does material ledger add?", "How do you migrate stock values?"
Strong answer: policy, ML currencies/valuations, actual costing decision, migration reconciliation, governance.

Practice this lesson

Quick check

1. Why define a group-wide valuation policy?

2. What must be reconciled when migrating inventory to S/4HANA?

3. What does the material ledger provide in S/4HANA valuation?

Interview questions

1. During period-end close with Material Ledger active, finance flags that price differences from multiple procurement transactions are not settling correctly into the actual costing run. Which Material Ledger transaction key areas and closing steps would you review?

Answer it in your own words first, then compare.

2. During period-end close, Finance reports that stock revaluation postings hit an unexpected GL account for a specific material group. How would you investigate whether this is an OBYC valuation class misconfiguration or a Material Ledger issue?