MM_P2Pbeginner
MM Foundation, Enterprise Structure and Master Data
More overview details for this topic are coming soon.
Interview questions covered
- After a purchasing organization restructuring, buyers report that certain fields (e.g., incoterms, payment terms) are unexpectedly becoming mandatory or hidden in specific purchasing document types, but only for one purchasing organization. How would you diagnose and resolve this?
- Why is master data quality (material master, vendor master, purchasing info records) considered a foundational control point in a Procure-to-Pay implementation, rather than just a data-entry concern?
- A global template design assigns one purchasing group per commodity category, but regional business units insist on local purchasing group ownership by geography. How would you architect the purchasing group structure to balance global template governance with local operational needs?
- In an SAP Retail-enabled client, what is the significance of assigning a site (store or DC) to a merchandise category hierarchy, and how does this differ from a standard plant setup in classic MM?
- Explain how account groups govern field selection and number ranges for material master and Business Partner supplier records, and where these controls are configured.
Related topics
MM_P2P
S/4HANA MM Transformation, Ariba, Migration, Public Cloud and Architecture
MM_P2P
Invoice Verification, GR/IR, Integration and Production Support
MM_P2P
Procurement and End-to-End Procure-to-Pay
MM_P2P
Inventory Management, Valuation, Material Ledger and Account Determination
MM_P2P
Enterprise Structure
MM_P2P
Material Master