ERPClimb logoERPClimb

SAP MM / P2P Material Master Interview Questions

Material Master comes up in SAP MM / P2P interviews because it is one of the few areas where an interviewer can tell, in two questions, whether you have worked with the process or only read about it.

This page carries 22 reviewed SAP MM / P2P material master interview questions, each with a complete written answer and no sign-in required. The set breaks down into 3 foundational, 13 mid-level and 6 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.

The fastest way to use this page is to read the question, answer it yourself, and only then read the answer. The gap between your version and the written one is your actual revision list for material master.

22 Material Master questions with answers

easyMaterial Master

1. What is the difference between internal and external number range assignment for material master records, and where is this controlled in configuration?

Internal number ranges let the system auto-generate the next available material number sequentially from a defined numeric interval when a material is created, guaranteeing uniqueness without user input. External ranges require the user to key in a material number, typically alphanumeric, matching legacy or meaningful numbering conventions, with the system only validating that it falls within the assigned interval and is not a duplicate. Number ranges are maintained via MMNR and linked to material types in OMS2.
easyMaterial Master

2. What is the purpose of the classification system (class types, characteristics) in material master data, and how does it differ functionally from assigning a material group?

Classification (via class types like 001 for materials, characteristics and values in CT04/CL02) enables flexible, multi-dimensional attribute-based search, variant configuration, and batch classification beyond the single-field material group. Material group is a simple, fixed attribute used mainly for reporting, purchasing statistics, and account determination grouping. Classification supports complex searches (e.g., find all steel bolts with diameter 10mm and length 50mm) and integrates with variant configuration, batch determination, and QM inspection characteristics, which material group cannot support.
easyMaterial Master

3. What is the significance of the material type and how does it drive valuation level settings such as movement type restrictions and account determination?

Material type (e.g., ROH, FERT, HAWA) controls number range, allowed views, price control default, quantity/value updating, and which account category reference is used for automatic account determination. It also restricts valuation class choices, which movement types are permitted, and whether valuation is possible only at plant level or optionally at company code level depending on configuration in OMS2.
mediumMaterial Master

4. How does the classification system (class and characteristics) integrate with material type configuration to support material master governance in a multi-category enterprise?

Classification assigns materials to classes with characteristics (e.g., dimensions, hazard codes, category attributes) independent of material type, but material type determines which classification class types are relevant via the classification view field selection. Configuration links class types (like Class Type 001 for materials) to material types through the classification view activation, enabling search, variant configuration, and batch classification while material type still governs number ranges, valuation, and account determination separately.
mediumMaterial Master

5. Your client is migrating from ECC to S/4HANA Public Cloud with Ariba integration for indirect procurement. The material master no longer supports certain legacy fields used by their custom pricing logic. How would you approach reconciling material master simplifications with Ariba catalog and contract data?

First identify which legacy MM fields were deprecated or moved (e.g., certain valuation or MRP fields consolidated in S/4HANA simplification). Map Ariba catalog attributes and contract pricing conditions to the new field structure, using Ariba's Cloud Integration Gateway (CIG) for master data replication. Validate pricing logic against condition records in S/4HANA rather than custom Z-fields, since Public Cloud restricts core modifications; adapt via BAdIs or extensibility where allowed.
mediumMaterial Master

6. A business wants to introduce a new material type for 'non-stock service items' that should never carry inventory value but still needs purchasing master data (info records, source lists). How would you design this material type and what governance controls would you apply?

Create a new material type (copying a similar non-valuated type) with quantity and value updating turned off so no stock account postings occur, while enabling purchasing views so info records and source lists can be maintained. Restrict allowed item categories in purchasing documents to non-stock/service-relevant ones, and control number ranges and field selection to prevent inventory-relevant fields from being populated. Governance should include a material creation workflow enforcing this material type only for non-stock services and periodic audits to prevent misuse for actual inventory items.
mediumMaterial Master

7. Walk through how cross-plant and plant-specific material status settings support a material lifecycle governance process such as phasing out an obsolete material, and what functional restrictions each status type enforces.

Cross-plant material status (MARA-MSTAE) applies globally across all plants and, per configuration in OMS4, can issue a warning or error message that restricts functions like purchasing, MRP, or goods movements everywhere. Plant-specific status (MARC-MMSTA) allows different restriction levels per plant, so a material can be blocked for procurement at one plant while still transacting normally elsewhere. Lifecycle governance typically applies status changes with a validity date to stage phase-out gradually, first as a warning, then as a hard block once stock is depleted.
mediumMaterial Master

8. How does field selection control which material master fields are mandatory, optional, display-only or hidden, and what governs this at the material type and plant level?

Field selection uses field selection groups assigned to individual fields, and these groups are linked to combinations of material type, industry sector, transaction (create/change/display) and plant via field selection strings maintained in customizing, commonly through OMS9. The system combines the most restrictive setting across influencing factors, so if a field is optional at material type level but suppressed for a specific plant or transaction, the stricter rule wins. This lets one material type present different mandatory fields for procurement versus production views.
mediumMaterial Master

9. A buyer creates a manufacturer part number (MPN) material to procure a component from an approved manufacturer, but the purchase order cannot display the manufacturer part field and instead processes against the internal material number only. What is the likely root cause and how do you resolve it?

MPN functionality must be explicitly enabled at the material type level and requires linked manufacturer master data; if the material type used was not configured with the MPN indicator, or the manufacturer part master and the link between the internal material and the manufacturer part number were never created, the MPN fields will not surface on the PO. Resolution is to verify the MPN indicator is set for the material type in configuration, create the manufacturer master record, establish the internal-material-to-MPN link on the material master's manufacturer data screen, and confirm the purchasing info record references the correct manufacturer part.
mediumMaterial Master

10. How are number ranges assigned to material types in configuration, and what are the implications of grouping multiple material types under a shared number range?

In OMSL/material type config, each material type is linked to a number range interval (internal or external) and an assignment table controlling whether the material type uses its own range or shares one with others. Sharing a number range across material types simplifies number administration but removes the ability to identify material category from the number series alone, increases risk of range exhaustion affecting multiple types simultaneously, and complicates migration or archiving strategies that rely on number-based segregation. Dedicated ranges per type support easier reporting and lifecycle management but increase administrative overhead.
mediumMaterial Master

11. A pharma company activates batch management on an existing material with open stock across multiple plants. What integration impacts occur across inventory, quality, and FI valuation?

Activating batch management is only possible when stock is zero across all plants and storage locations, since batch-managed and non-batch stock cannot coexist for the same material. All existing stock must be cleared (physically or via posting) before activation. Once active, each batch becomes a separate valuation/inventory unit for quality inspection lot linkage, expiry date tracking, and can have its own valuation if split valuation by batch is also configured, affecting inventory reporting and FI stock account postings at batch granularity.
mediumMaterial Master

12. During a material master governance rollout, the business wants classification characteristics (e.g., a hazardous-material tag) to influence which account groups and downstream GL valuation classes can be assigned during material creation, distinct from standard material-type-driven field selection. As the functional lead, how would classification integrate with this governance model, and where does it fall short compared to account-group-based controls?

Classification via class types and characteristics can tag materials with attributes like hazardous status for reporting, search, and downstream process triggers, but it does not natively restrict account group or valuation class assignment during creation—that control belongs to material type and account group field selection. I would use classification for informational tagging and validation workflows, while enforcing actual account group and GL determination rules through material type configuration and custom checks, since classification alone cannot enforce mandatory field behavior at creation.
mediumMaterial Master

13. A material's purchasing view was maintained correctly for Plant A but a buyer at Plant B cannot create a purchase order because the material's plant-level purchasing data is missing. What is the likely root cause and how do you resolve it?

Material master data such as purchasing view, MRP view and valuation data is plant-specific and must be explicitly extended per plant using MM01 extend-material or a mass extension tool; creating the material only at Plant A does not automatically make it procurable at Plant B. The fix is to extend the material to Plant B with the required views populated, ensuring purchasing group, valuation class and other mandatory plant-level fields are maintained, then verify info records or source lists if sourcing is restricted.
mediumMaterial Master

14. A global rollout uses one material master field selection group across all plants, but a regional business unit now requires the 'country of origin' field to be mandatory only for materials manufactured in their plants, while other regions want it optional. How would you resolve this without breaking the global template?

Field selection at the material type level is global, but plant-specific field selection can be refined using the plant-specific material status or by leveraging user exits/BAdIs for conditional mandatory checks, since standard field selection groups don't natively differentiate by plant for a single field across material types. The practical approach is to use a custom check (e.g., MM06 field selection reference key tied to plant, or a validation via BAdI MD_MAINTAIN or similar) rather than forcing a global mandatory setting that would break other regions' processes.
mediumMaterial Master

15. A procurement team complains that a newly created material cannot be used on a purchase order for a specific plant even though it exists in the material master. What material master view and organizational-level checks would you investigate first?

I would first check whether the purchasing view exists at all, since it's required for PO creation, and then verify the material has been extended to the specific plant with the plant-level purchasing/MRP views maintained, not just the client-level basic data. I'd also check whether the material is extended to the relevant purchasing organization data if plant-specific purchasing org data is required, and confirm no material status (deletion flag or cross-plant material status) is blocking procurement for that plant.
mediumMaterial Master

16. A retail organization implementing S/4HANA needs both traditional stock-managed materials and listed retail articles sold across stores. How should material type selection and governance differ for these two categories?

Traditional stock-managed materials typically use standard material types such as finished goods or trading goods with quantity and value updates driven by movement type postings, while retail articles are governed through retail-specific listing and assortment processes that control which stores can sell an article, often layered on top of the base material type rather than replacing it. Governance should separate material type selection, which drives valuation and procurement behavior, from listing/assortment configuration, which drives store-level sales authorization, so that a material can be centrally created once but only become sellable at listed stores after assortment activation.
hardMaterial Master

17. Users at a new storage location cannot see the quality management view fields when creating a material master record, even though other storage locations at the same plant show these fields. What is the likely cause and how would you troubleshoot it?

Field selection at storage location level isn't typically what controls QM view visibility; the QM view is controlled by material type field selection and the QM procurement/inspection setup relevance flags in the material master, plus the plant's QM active indicator. Likely cause: the plant's QM view activation flag isn't set for this storage location scenario, or the field selection group for that material type/plant combination excludes QM fields, or the user's field selection reference (via industry sector) differs. Troubleshoot via field selection config and checking if QM is active at plant level for that material type.
hardMaterial Master

18. Purchase order creation is being blocked for a material at one plant with an error referencing plant-specific material status, while the same material transacts normally at other plants. How would you diagnose and resolve this?

Plant-specific material status is maintained in the MRP/purchasing view per plant and can restrict purchasing, production or sales at that plant only, independent of the cross-plant status maintained at basic data level. Diagnosis involves checking the plant-specific status field and its configured effect (warning or error) for the relevant procurement transaction, then confirming with the material planner whether the block is intentional, such as phase-out or discontinuation, before changing it. Because valuation level in most implementations is plant, status and valuation logic both operate independently per plant.
hardMaterial Master

19. A global manufacturer needs different base units of measure conversion behavior for a material sold in each (base UoM) but purchased in kg and produced in liters, with a temperature-dependent density conversion. How should this be architected in the material master?

Base unit of measure remains fixed at material creation (each) and cannot practically change later; purchasing uses order unit (kg) with a fixed conversion factor maintained in the material master or purchasing info record, while production uses alternative units (liters) via unit-of-measure conversion tables. For temperature-dependent density, standard fixed UoM conversion is insufficient since it assumes constant ratios; this typically requires batch-specific classification characteristics or a custom conversion logic in production/quality, as SAP's standard EAN/UoM conversion is static, not dynamic.
hardMaterial Master

20. During supplier master governance harmonization for a merger, two legacy systems used different material type strategies: one used a single generic material type for all purchased items, the other used granular material types per category. As architect, how do you decide the target material type strategy and what factors drive that decision?

I would evaluate what each material type controls: number range, valuation update, price control default, quantity/value update, and permissible views, then determine how much differentiation the business genuinely needs for inventory valuation, procurement control, and reporting. Overly granular material types create maintenance overhead and inconsistent number ranges, while a single generic type limits control over valuation and view defaults. The target design should balance reporting granularity needs, valuation control requirements and long-term maintainability, often landing on a moderate set of material types aligned to procurement and valuation behavior, not category taxonomy.
hardMaterial Master

21. Post go-live, Ariba-sourced material master data fails intermittently to sync into S/4HANA via MDG, with some materials created with missing plant-level views. How would you troubleshoot this integration issue?

First check the MDG change request status and workflow logs for failed steps, then review the Ariba-to-MDG integration monitor for message-level errors such as missing mandatory fields or mapping failures. Verify that plant/storage location extension steps are triggered correctly in the MDG process, since incomplete replication often stems from asynchronous extension requests not completing before consumption. Correlate with PI/CPI message logs and reprocess failed IDocs or messages after correcting source data.
hardMaterial Master

22. You are designing the enterprise structure for a global manufacturer where multiple internal plants source the same physical component from different manufacturers under different manufacturer part numbers. How should MPN materials and info records be architected?

Design should use manufacturer part number functionality so a single internal material number can be linked to multiple manufacturer-specific part numbers, each represented as its own MPN material record tied to a manufacturer master record, avoiding proliferation of unrelated internal material numbers for functionally identical parts. Purchasing info records are then created against the MPN material and vendor combination, allowing sourcing and pricing to remain manufacturer-specific while inventory, MRP and BOM references stay consolidated at the internal material level, simplifying cross-plant reporting and avoiding duplicate stock segmentation.

Related topics

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

Next practice step

Practice with Interview AITake a mock test