sap-mm

SAP Materials Management (MM) Skill

0. Environment Intake and Safety Contract

Before diagnosing or recommending an MM action, collect:

• Release: ECC 6.0 EhP or S/4HANA release year
• Deployment: On-Premise, RISE/Private Cloud, or Public Cloud
• Industry/process: manufacturing, retail, project procurement, services, or regulated industry
• Scope keys: user-provided purchasing organization, plant, storage location, PO, and material
• Evidence: exact message class/number, T-code or Fiori app, timestamp, last normal document
• Control state: posting period, approval status, GR-based IV flag, and whether QM/batch/serial control applies

Never invent company codes, G/L accounts, cost centers, plants, purchasing organizations, or tolerance values. If environment context is missing, ask up to four grouped questions and still provide clearly labelled provisional read-only checks. Configuration changes require a Transport Request (TR), a representative test in DEV/QA, UAT evidence, and a rollback plan. Never edit production tables with SE16N.

1. Procurement Cycle

PR (ME51N) → RFQ (ME41) → Quotation (ME47) → PO (ME21N)
→ GR (MIGO 101) → IV (MIRO) → Payment (F110)

Shortcut flows:

• Without RFQ: PR → PO (ME58 — auto-convert PR to PO)
• Consignment: PO item cat K → GR → settlement (MRKO)
• Subcontracting: PO item cat L → GI components → GR finished

---

2. Purchase Order Issues

Account assignment errors

• Category K (cost center): cost center must exist and be active
• Category A (asset): asset master must exist, depreciation area active
• Category F (internal order): order must be in Released status
• Category P (project/WBS): WBS element must be open for costs

Tolerance check (MIRO)

• OMR6 → tolerance keys: BD (amount) / VP (moving avg price variance) / PP (price)
• Tolerance = percentage + absolute amount — both must be within limits

GR-based invoice verification

• PO item → Invoice tab → GR-Based IV flag = X
• With flag: MIRO only possible after GR; invoice quantity = GR quantity