Tags

, , , ,

Master Data & Configuration (with MRP Areas per Vendor)

This playbook turns the “why” from a previous blog: “SAP MM: S/4HANA Subcontracting, Simplified…” into a concrete how-to. It focuses on building a clean, scalable design where each subcontractor has its own MRP Area, planning is segmented by vendor, and you only override parameters where behavior must differ from the plant default.

Objectives & Scope

Objectives

  • Segment planning by subcontractor using MRP Areas.
  • Keep plant-level master data as the default; override only where needed at the MRP Area.
  • Ensure smooth execution of the classical subcontracting flow (541 issue → 101 GR → 543 backflush) with clear pegging and faster MRP.

In scope

  • MRP Area configuration & governance
  • Material master setup (finished/semi-finished + components)
  • Purchasing master data for subcontracting
  • Planning parameters & when to override
  • Execution controls, monitoring, and troubleshooting

Key Design Decisions (make these first)

  1. Standardize on “one MRP Area per subcontractor” in each plant where they operate. No partial adoption.
  2. Minimal overrides: Plant views are the baseline; only create MRP-Area-specific parameters for genuine differences (lot size, safety, lead time).
  3. Ownership: Assign a planner per MRP Area (vendor) for accountability and faster exception handling.
  4. Staging strategy: Agree how/when components are issued (541) and how reversals/excess are handled (542/544).
  5. Source control: Decide whether to use Source Lists/Quota to split demand across multiple subcontractors.

Configuration (SPRO) – the essential bits

Note: Naming and paths may vary slightly by release; follow your S/4 customizing structure.

A. MRP Areas:

  • Define MRP Areas for each subcontractor under the plant and assign the vendor.
    Outcome: You get a discrete planning segment for “stock at vendor” and its requirements/supply.
  • Governance: Create a naming convention (e.g., PLT1-VEND12345) and a short description including plant, vendor name, and city.
  • SPRO > Production > MRP > Master data > MRP Areas > Define MRP Areas for Subcontractor

B. Special Procurement (optional, when you need distinct behavior)

  • If you require a distinct special procurement (e.g., to influence planning proposals for the subcontracted assembly or staging logic), define it and assign only in the MRP Area (not globally).
  • Keep it simple: If standard subcontracting behavior suffices, don’t invent extra special-procurement keys.
  • SPRO > Production > Material Requirement Planning > Master data > Define special procurement type

C. Movement Types (reference)

  • Ensure standard movement types are available and not customized in ways that break integration:
    • 541: GI to subcontractor (to special stock at vendor)
    • 543: Consumption at GR of finished assembly (auto backflush)
    • 542/544: Returns/reversals
  • If you use HU/packing, confirm settings support 541 staging.

D. Number Ranges / Account Determination (reference)

  • Nothing unique to MRP Areas here, but verify account assignment for 543 consumption and price differences (Material Ledger, if active).

Master Data Setup

A. Business Partner (Vendor)

  • Maintain vendor as BP with purchasing view.
  • Link the BP to the MRP Area definition so planning pegs correctly to that subcontractor.

B. Finished/Semi-Finished Material to be Subcontracted

  • Procurement: External procurement (purchasing view complete).
  • BOM: Maintain a valid BOM on the PO material (this is essential; MRP and 543 rely on it).
  • MRP views (Plant level): Use your standard defaults (MRP Type PD or strategy you normally use, lot-sizing, lead times, planning time fence, etc.).
  • MRP Area view (Subcontractor):
    • Create the MRP Area extension for each subcontractor you intend to use.
    • Override only when truly needed (examples below).

C. Components (materials you provide to the vendor)

  • Regular component materials (ROH/SFG) with plant-level MRP as usual.
  • Ensure each component is extended to the subcontractor MRP Area (so its requirements/supply proposals can appear there).
  • Storage locations & stock determination should support 541 staging.

D. Purchasing Master Data

  • Info Record (Subcontracting) for the finished/semi-finished material: pricing, lead times, conditions.
  • Source List (recommended) to lock the subcontractor as the source for the plant/periods required.
  • Quota Arrangement (optional) to split volumes across multiple subcontractors while keeping MRP segments clean.
  • Outline Agreement / Scheduling Agreement (optional) if you run repetitive cycles; align validity dates and release strategy.

E. Quality & WM/EWM (if applicable)

  • QM: Decide if GR is to inspection (101 to Q) vs unrestricted; reflect in PIR or material settings.
  • WM/EWM: Align 541 staging/packing, HU, and any EWM delivery-based processes; ensure they don’t mask special stock at vendor visibility.

Planning Parameters — what stays plant vs. what to override in MRP Area

Keep at Plant (default)

  • MRP Type, strategy group, primary lot-sizing policy, basic lead times, planning time fence.
  • Safety policies that reflect your overall company standard.

Override in MRP Area (only if needed)

  • Lot size / rounding: Vendor insists on fixed lots of 200? Set FX = 200 in the subcontractor MRP Area only.
  • Safety/capacity buffer: Unreliable vendor supply? Add area-level safety stock to protect that segment without inflating plant stock.
  • Lead times: Vendor-specific planned delivery time or GR processing time that differs from plant default.
  • Special procurement nuance: Only if you must change the way proposals are created for that area.

Golden rule: Less is more. Don’t clone all plant parameters into every MRP Area—only differences.

Execution Flow (what users actually do)

  1. MRP Live runs at the plant consider subcontractor MRP Areas automatically (when they exist).
  2. Planner reviews MD04 (or Fiori coverage) by MRP Area:
    • Sees component dependent requirements pegged to Vendor MRP Area.
    • Converts proposals (PR → PO) for the subcontracted assembly as needed.
  3. Component staging:
    • Warehouse issues components 541 to vendor (creating special stock at vendor).
    • Use picking/packing processes consistent with WM/EWM design.
  4. GR of finished assembly (101):
    • System performs 543 consumption of components at vendor stock.
    • Discrepancies handled by 542/544 as needed (excess/shortage returns, reversals).
  5. Monitoring:
    • MD04 by MRP Area for exception messages you can act on.
    • ME2O / MBLB to monitor subcontractor stock and components “at vendor”.

Data Quality & Governance Checklist

  • BOM on the subcontracted material is complete and current (units, scrap, alt items).
  • All materials extended to relevant MRP Areas (both assembly and components).
  • Info Record has the right subcontracting category, prices/conditions, and lead times.
  • Source List validity dates cover planning horizon; MRP-relevant flag set where needed.
  • Quota Arrangement splits match reality (if used).
  • Movement types unmodified in ways that break 541/543.
  • Planner ownership documented per MRP Area/vendor.

Testing & Cutover (fast track)

Unit Test

  • Create dependent demand; run MRP.
  • Verify component requirements appear in Vendor MRP Area (not the plant).
  • Convert PR to PO (item cat L); verify BOM explosion on PO.
  • Post 541; check special stock at vendor.
  • Post 101; check 543 consumption exactness and pegging.

Integration Test

  • Include pricing, tax, valuation, and ML if active.
  • Include WM/EWM staging scenarios, HU where applicable.
  • Include returns/excess scenarios (542/544).

Cutover

  • Create all MRP Areas and extend materials before first S/4 MRP run.
  • Lock down Source Lists/Quota to prevent sourcing drift.
  • Train planners to always filter by MRP Area in MD04/Fiori.

Monitoring & Reports (day 2 operations)

  • MD04: Always select the MRP Area scope to avoid plant noise.
  • ME2O: Subcontracting – monitor components at vendor, shortages, and open POs.
  • MBLB: Stock at subcontractor (special stock at vendor).
  • MB51 / Material Documents: Filter by 541/543/542/544 for audits and discrepancy analysis.
  • Exception messages: Treat them inside the MRP Area first; escalate only if systemic.

Troubleshooting Guide

  • Component not consumed at GR (543 missing)
    • Check PO item is subcontracting (L) and BOM explosion occurred.
    • Confirm component existed in special stock at vendor (541) and is in the BOM unit.
  • Negative or unexpected special stock at vendor
    • Review 541 timing/quantity vs GR; validate BOM qty/scrap and backflush settings.
  • Requirements show in plant instead of vendor area
    • Material not extended to MRP Area, or MRP Area missing/incorrect.
    • Sourcing (Source List/Quota) pointing to a different vendor than the area used.
  • Excess components at vendor
    • Process 542 returns; adjust BOM or staging policy; revisit lot sizing in area to reduce over-issues.
  • Messy exception list
    • Planner is reviewing plant instead of MRP Area; retrain and adjust defaults.

Minimal Parameter Playbook

  • Plant-level (default)
    • MRP Type = PD
    • Lot Size = your standard (e.g., EX or FX where appropriate)
    • Planning Time Fence = standard
    • Lead Times = standard
  • MRP Area (subcontractor) — only set if different
    • Lot Size = FX (e.g., 200)
    • Safety Stock = N days of coverage (e.g., 3–5)
    • Planned Delivery Time = vendor-specific (e.g., +5d vs plant default)
    • Special Procurement = only if your design truly needs it

Final Takeaway

Make MRP Areas per subcontractor your standard, keep plant parameters as the default, and only override where the vendor’s behavior truly differs. With that discipline, S/4’s subcontracting becomes simpler to plan, faster to run, and easier to control—exactly what the “simplified” approach is meant to deliver.

The author, Ray Hornbrook, has many years of SAP functional and technical experience.  Ray started his career in SAP as a MM/PP Subject Matter Expert (SME) for a SAP implementation and is now a Senior Level SAP Consultant.  Since Ray has worked both sides of SAP, business end user and IT professional, he is able to communicate effectively with both IT and Business team members. Having a background as an SAP business end user has helped Ray greatly in his consulting career.  The business background helps him better communicate with the business members of the team.  As well as helping bridge gaps in communication between the IT and Business team members.

To find out more about Ray Hornbrook please check out his LinkedIn profile by clicking HERE.

End of document – www.portsap.com