Executive summary
The subject should not be treated as an isolated technical point. It must be read as an industrial transformation challenge: decision quality, operational robustness, operational support capacity and measurable value creation.
The difference between a standard approach and a rigorous approach is the depth of the diagnosis. It is not enough to identify what is malfunctioning. It is necessary to understand why the organization has allowed this dysfunction to settle, what decisions have not been taken, which indicators have masked the problem and what governance will prevent its reappearance.
Industrial digital performance does not come from the stacking of tools. It comes from the alignment between processes, data, responsibilities, systems and management routines.
The principle: MRP does not create truth; it amplifies the data and rules it receives
In many industry organizations, the MRP is seen as a tool that “should come out with the right plan.” This expectation is dangerous. SAP PP does not guess supplier reliability, commercial decisions, shop floor practices, or Excel workarounds. The MRP applies calculation rules from a repository and a inventory state. When the result seems inconsistent, the first reflex should not be to challenge SAP, but to question the quality of the operating model that SAP is supposed to represent.
An unstable MRP often reveals a debt of governance: materials created too quickly, deadlines never reviewed, inherited batch sizes, safety stock decided by prudence, bills of materials updated in emergency, misaligned manufacturing versions, undifferentiated supply strategies. The tool then becomes the mirror of an organization that has not formalized its steering rules.
Differentiating vision is to treat MRP not as a planning transaction, but as an industrial nervous system. Its reliability depends on the quality of the sensors, the reaction rules and the management routines. Without this discipline, the MRP produces noise. With it, it becomes an engine of prioritization, reduction of emergencies and control of the BFR.
Symptoms of an MRP that is no longer controllable
The most visible symptom is the excess of exceptions: announced shortages, proposals for advancement, theoretical delays, orders to be replanned, recurring MRP messages. But the real problem is not the volume of alerts. The real problem is the inability of planners to distinguish critical signals from mechanical signals.
In an SAP PP environment, an uncontrolled MRP typically produces four operational effects. First, planners switch to a daily emergency hunt. Then, supplies multiply the raises and the security orders. Then production loses confidence in the plan and favors local decisions. Finally, inventory increase without removing breakage, because the inventory is positioned in the wrong place or on the wrong items.
| Symptoms observed | probable cause | Question of diagnosis |
|---|---|---|
| Recurrent MRP exceptions on the same materials | Item parameters not aligned with the reality of consumption or sourcing | Have these materials been the subject of an ABC/XYZ journal or are they managed by inheritance? |
| Very volatile planned orders from one run to another | Unstable demand, short horizon, unsuited batch size or lack of firming | Does nervousness come from demand, configuration or planning policy? |
| Ruptures despite high inventory level | Poor inventory positioning, false bills of materials, underrated deadlines | Does the inventory really protect the critical constraints of the flow? |
| Production plan contested by the shop floor | non-representative standard routings, capabilities or time | Do SAP times reflect actionable capacity or theoretical capability? |
The SAP PP fields that truly affect reliability
Rely does not involve auditing all the fields in the article sheet. It consists in identifying fields that have a direct impact on purchase, manufacturing and transfer proposals. Critical fields vary by context, but some SAP PP areas are systematically returning.
On purchased items, supply times, quality reception times, batch sizes, order minimums, sources of supply and quotas directly influence the ability to cover demand. On semi-finished and manufactured products, manufacturing times, routings, manufacturing versions, scheduling keys, workstations and availability components structure the feasibility of the plan.
The classic trap is to treat these parameters as static data. In reality, they are piloting decisions. A vendor delay that goes from 20 to 45 days without SAP update immediately degrades the MRP signal. A historically fixed batch size can generate excess inventory or shortages. A security inventory defined “in hand” can mask a variability that the organization should reduce rather than compensate for.
| SAP object | Points of vigilance | Risk if not controlled |
|---|---|---|
| Factsheet article / views MRP | Type MRP, planner, MRP group, batch-sizing, security inventory, lead time, horizon, strategy | Inconsistent proposals, excessive exceptions, manual decisions |
| Nomenclature | Validity, quantity component, unit, alternative, status, ghost component | Incorrect requirements, missing components, incorrect consumption |
| Routing and work centre | Time, capacity, calendar, control key, queue, setting | Unrealistic theoretical dates, capacity overload, non-executable orders |
| Manufacturing version | Alignment article, BOM, routing, validity, batch-size | Planning on a different version of the actual execution |
| Sources of supply | Source list, quota arrangement, contracts, purchasing info records, special procurement keys | Need assigned to the wrong supplier or the wrong flow |
Segmenting materials: the mistake is to manage the entire portfolio using the same logic
A factory that applies the same MRP policy to a stable consumable, an imported critical component, a constrained semi-finished and a volatile finished product mechanically creates instability. Segmentation is therefore a major lever. It makes it possible to decide which items must be finely planned, which can be driven by threshold, which require a protective inventory and which must be worked in product design or sourcing.
An ABC/XYZ matrix is often a good starting point, but it must be supplemented by industrial criteria: quality criticality, supplier time, substitutability, capacity constraint, scrap rate, lifespan, regulatory risk, customer exposure. Segmentation should not be PowerPoint scanning; it must translate into SAP rules and piloting routines.
| Material family | Recommended policy | SAP Translation / Governance |
|---|---|---|
| Long-lead-time materials | Upstream security, supplier review, inventory or explicit target coverage | Monthly lead-time review, calculated security inventory, real consumption alerts |
| High-value, volatile materials | S&OP decision, firming, commercial validation of peaks | Planning time fence, MPS review, targeted management exception |
| Low-value, stable materials | Maximum automation, simple rules, low planner workload | Adapted batch-sizing, thresholds, planner by family |
| Semi-finished constrained | Capacity control, limited buffer inventory, synchronization scheduling | Robust manufacturing versions, up-to-date routings, actionable capacity data |
Anonymised case study: a plant with inventory but no availability
In a context of process production, the site had a level of global inventory considered comfortable. However, the planners reported weekly component shortages and emergency planning changes. The initial analysis showed an apparent contradiction: the average coverage seemed high, but some blocking materials were chronically out of stock.
The diagnosis showed three root causes. First, safety stock were concentrated on historical families and not on the real items being constrained. Second, the actual supplier lead times had drifted after a change in sourcing, without a systematic update of the material masters. Third, the bills of materials of several products had been corrected locally in preparation files but not always in SAP.
The answer was not just a data cleaning. It has combined segmentation materials, review of supplier lead times, validation circuit of bills of materials, exceptional indicators MRP by cause, and monthly ritual between supply chain, methods, purchases and production. The expected result in this type of approach is not only a decrease in the number of anomalies. It is a reduction in the manual steering load and a better credibility of the industrial plan.
Establish a pragmatic MRP control tower
Sustainable reliability goes through an MRP control tower adapted to the size of the organization. It’s not about creating a heavy tool, but a shared reading of critical signals. The logic must be root cause oriented: how many exceptions come from the data, the request, the supplier, the capacity, the execution or the configuration?
Useful indicators are not always those that are spontaneously followed. The total number of exceptions is less interesting than the recurrence of the exceptions on the same families. Average inventory coverage is less useful than coverage on critical items. The overall service level can mask shortages on strategic products.
Six-week reliability roadmap
An effective approach can start quickly, provided you focus the effort on the most sensitive flows and materials. The objective is not to correct everything, but to objectify the causes and to install a piloting discipline.
- Week 1 : scoping of critical families. Identify priority flows, high-impact materials, major pain points and business leaders.
- Week 2 : analysis of exceptions and volatility. Rank MRP messages, measure their recurrence, isolate false positives and real emergencies.
- Week 3 : targeted audit of parameters. Compare SAP critical fields to shop floor practices, suppliers, methods and production.
- Week 4 : pilot correction. Update a limited scope, test effects on run MRP, adjust rules.
- Week 5 : data governance. Define creation circuits, modification, validation, control, and review frequency.
- Week 6 : controlled rollout. Extend by families, formalize indicators, integrate routines into operational management.
Decision checklist
- Segment items according to value, variability, criticality, time and substitutability.
- Compare SAP deadlines to the actual observed vendor and internal deadlines.
- Auditer BOM, routings and manufacturing versions on families generating the most exceptions.
- Measure the nervousness of the plan, not just the volume of exceptions.
- Create a register of MRP configuration decisions with business owner.
- Set up a monthly review MRP / master data oriented root causes.
Operational conclusion
A reliable MRP is not the result of a successful initial setting. This is the result of continuous industrial discipline. The difference between an MRP suffered and a piloted MRP is played in the ability to link data, processes, suppliers, capabilities, inventory and business decisions.
The Fenlynks posture consists in making the MRP a decision asset: less noise, less urgency, more prioritization and better credibility between supply chain, production and industrial management.
Fenlynks provides scoping, rapid audits, business project support (AMOA), project governance, testing assurance, SAP/MES roadmaps, change management and post-go-live stabilisation.