ERPClimb logoERPClimb

SAP MM / P2P Valuation Interview Questions

Interviewers use valuation to test depth rather than coverage: the follow-up question is almost always "why does the system behave that way?", and that is where prepared answers usually run out.

Valuation in SAP MM determines how materials are financially valued and how inventory postings hit the general ledger. This topic covers the business purpose of valuation, valuation area/level, price control (standard vs moving average), valuation class linkage to accounts, and how these settings drive accounting integration across ECC and S/4HANA.

This page carries 39 reviewed SAP MM / P2P valuation interview questions, each with a complete written answer and no sign-in required. The set breaks down into 7 foundational, 18 mid-level and 14 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

If you can handle every question here without hesitating, valuation is unlikely to be what costs you an SAP MM / P2P interview — and the same reasoning pattern transfers to the neighbouring topics linked at the bottom of this page.

39 Valuation questions with answers

easyValuation

1. What is split valuation in the material master, and what business scenario would justify enabling it for a material?

Split valuation allows a single material to be valuated at sub-levels (valuation types) within a plant instead of one plant-level price, using valuation category settings in the accounting view. It's justified when stock of the same material comes from different sources needing separate accounting treatment, such as in-house produced vs externally procured batches, or domestic vs imported stock with different customs costs, while keeping one material number for logistics simplicity.
easyValuation

2. What does the valuation level (plant vs company code) determine in the material master, and why is plant-level valuation the standard recommendation?

Valuation level defines at what organizational granularity the material's price and stock value are maintained. Company-code level maintains one valuation across all plants; plant level maintains separate valuation per plant, enabling different prices, standard costs, and account determination per plant. Plant-level is standard because it supports plant-specific costing, transfer pricing, and split valuation, and is mandatory once material ledger or parallel valuation is used.
easyValuation

3. What is the fundamental difference between price control 'S' (Standard Price) and price control 'V' (Moving Average Price) for a material master, and how does each affect goods movement postings?

With Standard Price (S), the material is always valued at a fixed price maintained in the material master; any deviation between PO/invoice price and standard price posts to a price difference account rather than adjusting stock value. With Moving Average Price (V), the stock value is recalculated with each goods receipt or invoice, so price variances are absorbed into stock value as long as sufficient stock quantity exists to cover the difference.
easyValuation

4. Where is the valuation level (plant vs company code) defined in configuration, and what are the operational consequences if a business tries to change this setting after materials and stock already exist in the productive system?

Valuation level is defined in customizing under Enterprise Structure > Logistics-General > Define Valuation Level (transaction OX14), and it is a client-wide setting, not per plant or company code. Once materials, stock, and transactional documents exist, changing it requires all stock across all plants/company codes to be reduced to zero and no open purchasing/inventory documents, making it practically irreversible in a live system without a major cleanup or system rebuild.
easyValuation

5. What is actual costing in the SAP Material Ledger, and how does it differ conceptually from standard cost estimates used for inventory valuation?

Actual costing calculates a periodic weighted-average price based on all actual price and quantity variances recorded during the period, including purchase price variances, exchange rate differences, and production variances, then revalues inventory and cost of goods sold accordingly. Standard cost is a predetermined price set before the period that stays fixed until manually recalculated. Actual costing is executed via CKMLCP after period activities close, producing a periodic unit price that reflects true consumption cost.
easyValuation

6. How does SAP value special stocks such as vendor consignment or subcontracting stock during period-end close, and how does account determination differ from standard own stock?

Vendor consignment stock is not company-owned until consumption, so it carries no value in own inventory accounts and is tracked with quantity only using the special stock indicator K; no GL posting occurs at goods receipt. Subcontracting stock (indicator O) is valued as company stock at the subcontractor location. Account determination uses the same OBYC transaction keys (BSX, WRX) but special stock indicators route postings to separate stock accounts and enable segregated reporting via MB5B or MMBE by special stock category.
easyValuation

7. What is split valuation in SAP Materials Management, and why would a company use it for a single material master record?

Split valuation allows a single material to carry multiple valuation types, each with its own valuation category (e.g., batch, procurement type, or origin), stock quantities, and moving/standard prices. It is used when the same material number represents stock with different costs or quality, such as in-house produced versus externally procured, or different vendor batches, so each valuation type can be separately valued and posted to different valuation classes/GL accounts if needed.
mediumValuation

8. 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?

First check the material master accounting view for the valuation class and confirm it matches the intended group. Then review OBYC for the relevant transaction key (typically BSX or UMB for revaluation) mapped against that valuation class and account modifier to see which GL account is assigned. If the mapping is correct, check whether Material Ledger settlement (CKMLCP) posted the revaluation using a different account via a price-difference transaction key, which would point to an ML configuration issue rather than OBYC.
mediumValuation

9. Walk through the standard sequence of activities required to close a period for materials managed with the Material Ledger, and explain why the sequence matters.

Before closing, ensure all goods movements and invoices for the period are posted, then run the periodic price determination step which processes single-level and multi-level price differences, revaluates consumption, and calculates the periodic unit price. This must run after all preliminary valuations settle but before the next period opens for postings, because once the period is closed the actual costing run locks price and quantity data for that period, and premature closing can leave unsettled price differences.
mediumValuation

10. Does the Material Ledger provide built-in inventory aging functionality, and how would you typically configure or extend the system to support slow-moving/aging stock reporting for financial close purposes?

The Material Ledger itself does not natively track aging; it manages periodic valuation, price differences, and multiple currencies/valuations per material. Aging analysis requires combining MM data (goods movement dates, stock coverage) with custom or standard reports like MB5B, RM07MLBS, or S/4HANA embedded analytics on ACDOCA/MATDOC. For provisioning, finance often builds a range-based valuation adjustment using LIS or custom ABAP logic referencing last movement date per batch/material.
mediumValuation

11. A company uses batch management for a raw material and later discovers that different batches were valued inconsistently in the Material Ledger, causing distorted actual costing results. What integration factors between batch management and Material Ledger would you examine?

I would check whether batch-specific valuation was activated appropriately for the material, since without it all batches share one valuation record while ML actual costing still aggregates at material/plant level unless split valuation is configured. I'd review whether goods movements posted different batches under inconsistent valuation types or price control settings, and verify Material Ledger settlement runs correctly picked up all batch-related postings without gaps caused by missing periodic unit price updates.
mediumValuation

12. A plant using moving average price shows large swings in inventory value each period due to sequential goods receipts at fluctuating purchase prices. How would activating Material Ledger with actual costing help stabilize reporting without changing price control?

Material Ledger can run in parallel with moving average price control, recording all price and quantity variances at transaction level in the ledger even while MAP continues to update the standard material master price field. At period close, the actual costing run (CKMLCP) calculates a periodic unit price reflecting true weighted average costs including delivery and invoice variances, which can be used for management reporting or multi-currency/multi-valuation views without altering the legal moving average price used for real-time postings.
mediumValuation

13. How are batch and serial number valuation postings integrated with FI-GL, and what transaction keys are relevant when batch stock movements trigger financial postings?

Batch and serial numbers themselves do not have separate transaction keys; valuation still runs at material/valuation-class level via standard keys like BSX (stock account), WRX (GR/IR clearing), and PRD (price differences). Batches carry their own valuation only when split valuation is active, in which case the valuation type (per batch) determines the valuation class and thus account determination, while serial numbers remain purely for identification with no independent GL impact.
mediumValuation

14. A material is being valuated at plant level, but the business wants two different valuation methods for the same material within the same plant based on batch origin. How can this be achieved within the valuation area/material master framework?

This requires split valuation, activated via the material master's accounting view where the valuation category is set (e.g., to allow batch-based or procurement-type-based valuation types) and configured in customizing to enable split valuation globally and define valuation types. Since valuation area equals plant (in plant-level valuation), split valuation lets a single material within one valuation area carry multiple valuation records distinguished by valuation type, each with its own moving average or standard price and separate stock account determination if needed.
mediumValuation

15. What Material Ledger master data and configuration settings must be verified to ensure shelf-life expiration write-offs are correctly valued during period-end close, and how does this differ for a standard-price material versus a Material Ledger actual costing material?

You must confirm the material master has shelf-life expiration date tracking active in the plant/storage location view, and that Material Ledger is activated with the correct currency types and valuation area assigned for the plant. For standard-price materials, the write-off posts at standard price with any variance to a price difference account; for actual costing materials, the write-off value can be affected by the periodic unit price once the costing run settles, so timing of the write-off relative to CKMLCP execution matters to avoid distorted actual cost results.
mediumValuation

16. At month-end, a goods receipt posted against a purchase order posts an unexpectedly large amount to a price difference account instead of the inventory account. What is the likely cause and how would you trace it using transaction keys?

This typically occurs when the material is standard-price valuated and the GR value differs materially from the standard price, or the material is moving-average valuated but stock coverage is insufficient (negative/zero stock) forcing the excess to post to the price difference transaction key (PRD) rather than fully debiting inventory (BSX). Trace by reviewing the goods receipt accounting document in MIGO/MB03, checking OBYC assignments for BSX and PRD under the material's valuation class, and confirming the material price control indicator (S vs V) and available stock quantity at posting time.
mediumValuation

17. A goods movement using a custom Z movement type copied from standard 601 is failing to update the Material Ledger quantity ledger correctly, though the accounting document posts fine. What would you check first?

I would check whether the custom movement type retained the correct quantity update and value string assignment linked to the original movement type, since ML quantity ledger updates depend on movement type category and value string configuration, not just the accounting posting. I would verify in customizing that the Z movement type is properly flagged for stock-relevant quantity updates and that no field selection or reversal indicator differences from 601 are blocking correct ML ledger entries.
mediumValuation

18. In an S/4HANA system with Material Ledger active in the background for all materials, how does the periodic actual costing run interact with standard inventory management movements to derive actual costs, and what data does this rely on?

Material Ledger passively records every goods movement's quantity and value in ML tables during the period, capturing price and exchange rate differences alongside standard cost movements from MM. At period close, the actual costing run (CKMLCP or the Actual Costing app) settles these differences across the consumption chain, calculating a periodic unit price or actual price that redistributes variances to consumption and closing stock. This relies on complete, correctly categorized movement data in MSEG/ACDOCA and consistent valuation class assignment throughout the period.
mediumValuation

19. A plant reports that slow-moving raw materials are consistently valued at unrealistically high standard costs despite low turnover, and finance suspects transaction key GBB is misconfigured. How would you investigate the inventory aging valuation issue?

I would first check whether standard cost estimates were re-run periodically to reflect current usage patterns, since aging materials often keep outdated standard costs. Then review transaction key GBB account modifier assignments (e.g., VBR, AUF) for the valuation class to confirm postings route correctly. I would also verify if a slow-moving provision process exists separately from standard costing, since GBB governs GL posting logic, not valuation methodology, so aging itself is usually a costing run or provision issue, not a transaction key misconfiguration.
mediumValuation

20. A material valued at moving average price receives a large purchase order quantity at a significantly higher price than existing stock. The requester asks why the material's valuation price barely moved despite the price difference. How would you investigate and explain this?

I would check the stock quantity at time of receipt versus the incoming quantity in MBEW; if existing stock quantity is large relative to the new receipt, the weighted average shifts only slightly. I would also verify whether the receipt price matches the PO net price including delivery costs, and check for prior price differences already absorbed. If stock was near zero before receipt, the average should have moved close to the new price, so a small movement despite low prior stock could indicate a valuation update issue or split posting.
mediumValuation

21. A material is procured from two sources: one batch from a domestic vendor at standard price and another imported batch requiring customs duty valuation, and management wants separate inventory valuation for each without creating two material codes. What master data solution addresses this?

Split valuation should be activated for the material, configuring valuation categories (e.g., procurement origin) with valuation types such as 'domestic' and 'imported'. Each valuation type gets its own valuation record (accounting view) with separate moving average or standard price, while remaining a single material number for MRP, sales, and reporting purposes. Stock is still tracked separately by valuation type, and goods movements must specify the valuation type at posting.
mediumValuation

22. When configuring automatic PO creation for materials tied to Material Ledger activation, what basic ML settings must be verified before physical inventory counts can reliably reflect valuation-relevant data?

Before relying on automatic PO-driven stock movements for physical inventory, verify that Material Ledger is activated at company code level, the material ledger currency types and valuation area assignment are correctly configured, and periodic price determination status is closed for prior periods. Also confirm valuation classes and account determination are consistent, since ML activation changes how price differences and inventory postings are captured, affecting inventory count valuation reconciliation.
mediumValuation

23. 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?

I would review the price determination structure to confirm the material is set to actual costing (procedure 3) with the correct price determination control, then check that all relevant transaction keys (PRD for price differences, KDM for exchange rate differences, and similar ML-specific keys) are properly linked to accounts in OBYC. I would verify the closing sequence in the actual costing cockpit was executed in order (single-level then multilevel price determination) and confirm no periods were skipped, since ML settlement depends on cumulative price differences being carried forward correctly.
mediumValuation

24. A warehouse team reports that stock values in the Material Ledger differ from the accounting view in the material master for a material with multiple procurement sources. What could be causing this and how would you validate it?

This typically happens because the Material Ledger tracks price differences in additional currencies and, under actual costing, accumulates variances that haven't yet been settled into the standard price via periodic closing. I'd check whether actual costing run (CKMLCP or equivalent) has completed for the period, review the material's price determination setting (2 vs 3), and compare ML price history against MBEW to confirm whether unsettled variances explain the discrepancy.
mediumValuation

25. What Material Ledger configuration must be active for a goods issue movement type to correctly update the ML quantity and value ledgers, and how does the resulting posting differ from a plant where Material Ledger is not activated?

The plant must have Material Ledger activated with a valid ML type and currency/valuation type assigned, and the material must be ML-relevant with actual costing settings maintained if periodic unit price is used. With ML active, the goods issue updates both the quantity ledger and value ledger in the material's transaction currencies, feeding later actual costing runs. Without ML, the goods issue only updates the accounting document and material master moving average or standard price, with no parallel actual cost accumulation.
hardValuation

26. In a cycle-counting environment spanning multiple valuation classes, how should valuation class assignment be governed to ensure period-end inventory close produces accurate GL postings for count differences?

Valuation class must be consistently assigned per material type/plant combination in the material master accounting view, and mapped in OBYC to specific inventory and difference accounts. For cycle counting, materials should not change valuation class mid-cycle without a valuation-relevant transfer posting, since differences post based on the valuation class active at posting time. Governance requires change-control on valuation class updates, reconciliation of count-difference accounts by valuation class during close, and validation that account assignments in OBYC remain synchronized across plants using the same valuation area.
hardValuation

27. A global manufacturer wants to split-valuate a material by procurement source—domestic vendor supply versus imported supply—while keeping a single material number across plants. As architect, how would you design the split valuation configuration, and what governance controls are needed on purchasing info records and vendor assignments to keep valuation types consistent?

Define a valuation category (e.g., procurement origin) with valuation types such as DOM and IMP, activate split valuation on the material's accounting view, and maintain separate MBEW valuation records per type with distinct price control and GL account determination. Tie each valuation type to specific vendor purchasing info records and source list entries so POs automatically inherit the correct type. Governance must enforce that info record maintenance and vendor onboarding tag suppliers to the correct origin, preventing manual valuation type selection errors at PO creation.
hardValuation

28. A material was switched mid-year from price control V (moving average) to S (standard), and now every goods receipt posts unexpectedly large amounts to the price difference account. What is causing this and how would you address it?

Once switched to standard price, any purchase order or invoice value differing from the fixed standard price posts the variance to the price difference account (PRD) instead of adjusting inventory value, which is expected behavior for price control S but often surprises teams used to V, where variances adjusted the moving average directly. I would review whether the standard price was set appropriately reflecting current costs, and if the switch was justified, educate finance on PRD account behavior; if not justified, revert with proper MR21/CKMLCP handling to avoid ongoing distortion.
hardValuation

29. After running the actual costing run for a plant, physical inventory adjustments posted mid-period are showing unexpected variances against the actual cost calculated. How would you analyze and explain this to the finance controller?

I would explain that actual costing accumulates price and quantity variances throughout the period in the Material Ledger, and physical inventory adjustments posted before period closing are valued at the current standard or moving price at posting time, not the final actual cost, which is only determined during the closing run. The variance the controller sees is the difference between the interim valuation used at the time of the physical inventory posting and the settled actual cost after multilevel price determination absorbs all period variances, which is expected behavior, not an error.
hardValuation

30. A vendor return delivery (movement type 122) for a material whose valuation class was changed mid-year posts to a different stock and price-difference account combination than the original goods receipt used. Finance flags a GL mismatch between the original GR posting and the return. As the architect, how would you diagnose and correct this?

First confirm the material's current valuation class in the material master versus the valuation class active at the time of the original GR by checking the material's change history and MM03. Movement type 122 uses the current valuation class for BSX/PRD determination, not the historical one, so a mid-year class change causes the return to hit a different account. Reconcile by checking if standard price changed too; if so, price differences on return are expected and should be documented, not treated as an error. Prevent recurrence by controlling valuation class changes via change management and testing account impact before go-live.
hardValuation

31. Finance reports that during month-end close, the inventory valuation in the Universal Journal for a batch-managed material does not reconcile with the total stock value shown in stock overview, even though quantities match exactly. As the architect leading root-cause analysis, what batch valuation and configuration areas would you investigate?

I would first confirm whether split valuation is active with batch as valuation type, then check MBEW/valuation type records per batch for inconsistent price control (standard vs moving average) or differing valuation classes. I'd review recent transfer postings, batch splits/merges, and price changes (MR21) applied inconsistently across batches, plus check for goods movements posted with wrong valuation type overriding batch default. Finally, verify ACDOCA line items against BSEG/MBEW to isolate the delta transaction.
hardValuation

32. Explain how split valuation is configured for a material and describe the impact on movement type postings when the same material number is procured from two different valuation types (e.g., in-house produced vs externally procured).

Split valuation is activated via valuation category in the material master, allowing multiple valuation types (each with its own price control, price, and stock value) under one material number. Each valuation type behaves like a separate valuation unit with its own MBEW record, so goods movements must specify the valuation type explicitly; movement types post to the specific valuation type's stock account based on its own valuation class, enabling different accounting treatment for in-house versus externally procured stock.
hardValuation

33. During a supplier master governance redesign, the client wants stock at some storage locations valued separately from other locations within the same plant. How do you address this using standard SAP configuration, and what are the constraints?

Standard SAP valuation is defined at the valuation area level, and valuation area is normally set to plant level, meaning all storage locations under a plant share one valuation. If storage-location-level valuation is genuinely required, this typically demands a different plant structure or split into separate plants representing those locations, since storage location as a separate valuation level is not the standard design in most implementations. I would challenge the requirement and propose splitting into distinct plants with proper storage locations, or use split valuation for material-level differences.
hardValuation

34. What are the financial risks of enabling negative stock for a valuated material, and what configuration and process controls mitigate valuation distortion?

Negative stock allows goods issue before the corresponding receipt is posted, useful for parallel warehouse processes, but it can distort moving average price because the system may calculate MAP using an incomplete or negative quantity base, leading to unrealistic valuations once the offsetting receipt arrives. Mitigation includes restricting negative stock to specific storage locations or movement types via OMJ1, enforcing tight time windows for goods receipt, and monitoring valuation class postings closely during month-end to catch abnormal price jumps before they hit financial statements.
hardValuation

35. Explain the end-to-end process flow for calculating and settling actual costs in Material Ledger, including how movement types feed into the actual costing cube across multiple production levels.

Throughout the period, every goods movement (301, 261, 101, etc.) is recorded in the Material Ledger with quantity and value at the transaction currency and valuation view level, populating the ML document tables. At period close, CKMLCP performs price determination bottom-up across BOM levels: it calculates single-level price differences, then multi-level settlement cascades these through consuming materials level by level, finally computing the periodic actual price and posting revaluation documents to inventory and consumption accounts.
hardValuation

36. From a process design standpoint, what are the operational and financial trade-offs between standard price (S) and moving average price (V) control, and how does this decision affect movement type postings over time?

Standard price (S) fixes valuation at a planned/standard cost, posting all purchase and production variances to price difference accounts, giving stable inventory values ideal for standard costing environments and variance analysis. Moving average price (V) recalculates valuation with every goods movement, absorbing price fluctuations directly into stock value, which simplifies reconciliation but can distort inventory value during volatile purchasing or when stock quantities are low, since large receipts or returns swing the average significantly.
hardValuation

37. During period-end close, a stock transfer between two plants with different valuation classes results in a large price difference posting that finance did not expect. As the architect, how do you diagnose whether this is a design flaw or a legitimate valuation difference?

I would first confirm whether the transfer used a two-step (351/641) or one-step movement, and check if the receiving plant's valuation class and price control (standard vs moving average) differ from the sending plant, since transfers post at the sending plant's value and any receiving valuation difference goes to price difference accounts (transaction key UMB or PRD). I'd review whether this is expected due to differing standard costs by plant, or a design flaw such as missing intercompany pricing logic or incorrect valuation class mapping causing systematic mismatches every period.
hardValuation

38. A global manufacturer is deciding between company-code-level and plant-level material valuation. Walk through the implications of this decision on the enterprise structure and downstream inventory accounting.

Plant-level valuation allows different valuation prices/accounts per plant even within the same company code, essential when plants have different cost structures, tax jurisdictions, or local statutory requirements. Company-code-level valuation forces one valuation area per company code, limiting flexibility if plants need distinct standard costs. Most large multi-plant organizations use plant-level valuation; it's set once at client level via the valuation area configuration and cannot easily be changed after go-live without significant data migration effort.
hardValuation

39. A global enterprise is deciding between plant-level and company-code-level valuation for a new business unit with highly volatile intercompany material transfers. What are the architectural trade-offs, and which valuation level would you recommend?

Plant-level valuation allows different valuation prices per plant for the same material, which is essential when intercompany transfers or local market prices vary significantly; it's the SAP-recommended and most flexible approach, supporting split valuation and plant-specific costing. Company-code-level valuation forces a single price across all plants in that company code, simplifying reporting but eliminating plant-specific cost visibility. For volatile intercompany transfers, plant-level valuation is recommended since it supports accurate stock valuation and transfer pricing per location.

Related lesson

Configuring Valuation Area, Valuation Class and Price Control

Related topics

Invoice VerificationAutomatic Account DeterminationService ProcurementSupplier and Business PartnerSource DeterminationS/4HANA MM Transformation, Ariba, Migration, Public Cloud and ArchitectureMaterial MasterPurchase OrderRelease StrategyFlexible WorkflowPhysical InventoryGoods Receipt and Goods Issue

Next practice step

Practice with Interview AITake a mock test