SAP Applications

How to Design the MRP4 View in SAP S/4HANA Private Edition for Manufacturing and MRP by Location

How to Design the MRP4 View in SAP S/4HANA Private Edition for Manufacturing and MRP by Location

Introduction

In SAP S/4HANA Private Edition, the MRP4 view of the material master is the fine‑tuning dial that controls manufacturing logic and MRP behavior by location. It builds on the overall planning framework defined in MRP1–MRP3 and translates it into executable rules on how BOMs, production versions, and requirements are handled in daily operations.

This article organizes the key MRP4 fields and explains where they matter most in real‑life manufacturing scenarios, especially in automotive and discrete industries.


What is the role of the MRP4 view?

While MRP1–MRP3 define the overall planning strategy, lot sizing, and basic MRP parameters, the MRP4 view refines how these settings are applied to manufacturing execution. In practice, it is the tab where you decide:

  • How BOMs and production versions are selected (including alternative BOMs)
  • How individual versus collective requirements are handled
  • How production versions (BOM + routing combinations) are controlled
  • How component scrap and discontinuation parts are treated
  • How storage location MRP, MRP areas, and repetitive manufacturing are integrated

Because these decisions directly affect how production orders and dependent requirements are created and planned, the MRP4 view should be designed jointly by PP, MM, and production control teams, ideally as part of an integrated manufacturing governance model.sites.


1. Selection Method: which BOM or production version is used

The Selection Method in the MRP4 view determines how MRP chooses an alternative BOM or production version when creating planned and production orders.

Typical patterns include:

  • Selection by order quantity
    Useful when you want to switch between alternative BOMs by lot‑size range. For example, you can let the system automatically pick a simplified BOM for prototype or pilot lots, and the standard BOM for high‑volume production.
  • Selection only by production version
    In this case, a valid production version is mandatory. If no valid production version can be found, production or process orders cannot be created. This is widely used by companies that want to strictly control which BOM and routing combinations are allowed in production.help.

In S/4HANA, production versions are essentially mandatory for MRP and order creation, and many projects adopt “selection by production version” as the standard. A robust design pattern is to manage production versions by prototype vs. series production, plant, or line, and then use the Selection Method to prevent users from accidentally using the wrong BOM or routing.


2. Individual / Collective Requirements: how far you trace demand

The Individual/Collective Requirements indicator defines how dependent requirements for lower‑level components are represented in planning.

  • Individual requirements
    Dependent requirements are kept separately per higher‑level demand, such as a sales order or a specific planned independent requirement. This is effective when you need strong traceability or want to manage cost and supply per customer order or project.
  • Collective requirements
    Dependent requirements from multiple demands are grouped together. This is appropriate in high‑volume or repetitive manufacturing scenarios, where tracking every single demand separately is unnecessary and even counterproductive.

When designing this setting, consider two questions: how far do you need to trace demand for business and quality purposes, and at what granularity do planners want to see stock and requirements on their MRP lists.


3. Production Version: the official BOM + routing combination

A production version in S/4HANA bundles several elements into one “official recipe”:

  • The BOM to be used (including which alternative BOM)
  • The routing or master recipe
  • The validity period
  • The lot‑size range

In the MRP4 view, these production versions are linked to MRP logic so that the system can decide which version to use for which date and lot size during planning and order creation.learning.

In S/4HANA, production versions are effectively mandatory for MRP, planned order generation, and production order creation. This is also the foundation for PP/DS and advanced planning integration.

Design tips:

  • Structure production versions by actual shop‑floor perspectives: prototype vs. mass production, plant, line, or key equipment.
  • Combine this with the Selection Method so that users cannot freely pick arbitrary BOM–routing combinations; only predefined production versions should be allowed.help.

4. BOM explosion, component scrap, and discontinuation

The MRP4 view also includes settings related to BOM explosion behavior, component scrap, and discontinued materials.

  • BOM explosion
    You can control which BOM usages or specific BOMs are considered in MRP, and how alternative BOMs are selected. This ensures that planning follows the same rules as manufacturing and engineering.
  • Component scrap
    To reflect yield loss in assembly, you can add a scrap factor so that MRP plans a higher input quantity than the theoretical requirement. This must be aligned with your overall design philosophy on where to absorb margins: in BOM quantities, lead times, or safety buffers.
  • Discontinuation (follow‑up materials)
    Discontinuation settings control how MRP switches from an old component to a new one, and how remaining stock of the old part is consumed. This is closely tied to your policy for inventory run‑down and overlap between old and new parts.

In automotive and complex manufacturing environments, part number changes are frequent. Standardizing how you use discontinuation fields and BOM management rules in MRP4 greatly stabilizes operations during engineering changes.sites.


5. Storage location MRP, MRP areas, and repetitive manufacturing

Finally, the MRP4 view plays a key role in connecting repetitive manufacturing with MRP by location.

  • Storage location MRP and MRP areas
    In S/4HANA, MRP plans at plant and MRP area level. Storage location MRP behavior is modeled using MRP areas and MRP types. You can, for example, exclude certain locations from MRP or plan consignment and line‑side stocks separately using appropriate MRP types and MRP area assignments.
  • Repetitive manufacturing
    For materials with high volume, stable demand, and line‑based production, you can configure repetitive manufacturing in the MRP4 view, including rate‑based planning, backflushing, and line‑specific planning parameters. These settings assume that planning is performed on a rate basis rather than on individual order quantities.

For line production of automotive components or similar products, the combination of MRP4 repetitive manufacturing settings and MRP area design largely determines how accurately you can manage inventory and planning per production line.


Design considerations for S/4HANA Private Edition

In SAP S/4HANA Private Edition, the basic MRP4 concepts remain consistent with ECC, but several aspects become more critical:

  • Production‑version‑centric BOM and routing management, as production versions are required for MRP and provide the basis for PP/DS and advanced planning.help.sap+3
  • Use of MRP areas and storage location‑related MRP settings to realize line‑side and intra‑plant location planning strategies.
  • Clear separation of MRP4 settings for high‑volume repetitive materials versus low‑volume, high‑mix items, so that each scenario uses an appropriate planning model.

However, there is no fully exhaustive, public list of “S/4HANA Private Edition‑only MRP4 fields” that is reliable for every release. In real projects, it is recommended to cross‑check the current field set using Fiori apps for the material master, IMG configuration, and the latest SAP Help, to ensure that you design based on the fields actually available in your system version.learning.


Key points to remember when designing the MRP4 view

When you design the MRP4 view in S/4HANA Private Edition, it is useful to think of it as the final adjustment layer for manufacturing logic and location‑based planning:

  • Treat MRP4 as the last‑mile fine‑tuning layer that connects planning strategy to concrete manufacturing behavior.
  • Use Selection Method together with Production Versions to strictly control which BOM + routing combinations are officially allowed.
  • Decide the Individual/Collective Requirements setting based on how granularly you need to trace demand and how planners want to see stock and requirements.
  • Standardize BOM explosion, component scrap, and discontinuation settings as part of your material lifecycle and engineering‑change processes.
  • Design storage location MRP, MRP areas, and repetitive manufacturing parameters together with your intra‑plant location and line strategy.

Here is the SAP Fundamentals Series.

SAP Implementation & Projects – Insight Arc | SAP, Enterprise Architecture & Supply Chain Strategy


Reference Links


Disclaimer

Parts of this article were developed with reference to generative AI suggestions and were reviewed, refined, and supplemented based on the author’s professional expertise and judgment.


Back to Top

REI

Recent Posts

Is TOGAF Really “Too Heavy” for SAP Programs? Designing SAP Architecture with the Right EA Intensity Using DPBoK’s Four Contexts

This article reframes TOGAF as a scalable EA service for SAP programs, using DPBoK’s four…

19 hours ago

Why SAP Programs Need TOGAF® from a PM Perspective

A global SAP template will not remain sustainable by agile delivery alone. This article explains…

2 days ago

The True Power of Enterprise Architecture in Driving Successful SAP Implementations

A deep dive into how Enterprise Architecture (EA) empowers SAP success through TOGAF’s four key…

4 days ago

A Must‑Read for Digital Transformation Practitioners: What Is DPBoK and How Does It Differ from TOGAF® Enterprise Architecture?

The Digital Practitioner Body of Knowledge (DPBoK) is a practical standard for planning, building, operating,…

5 days ago

TOGAF® Agile × Product Management: Shifting Manufacturing from Projects to Continuous Value Creation

Why should manufacturing companies shift from one-time system projects to continuously evolving products? This article…

6 days ago

TOGAF® Agile Architecture in Practice: Understanding Landscape and the Three-Layer Model (Strategy, Segment, Capability)

A practical guide to TOGAF Agile Architecture using the three-layer model. Learn how to connect…

7 days ago