MRP solutions for material timing challenges

SAP HANA: Understanding MRP Live in SAP S/4HANA In today’s fast-moving supply chain environment, businesses need faster and more intelligent planning capabilities. This is where MRP Live in SAP S/4HANA becomes a game changer. MRP Live is one of the most important innovations introduced with SAP S/4HANA, leveraging the power of the SAP HANA in-memory database to perform Material Requirements Planning (MRP) significantly faster than classical MRP. What is MRP Live? MRP Live is the modern version of Material Requirements Planning that runs directly on the SAP HANA database. Unlike classical MRP, which processes data through the application server and often requires long batch jobs, MRP Live executes planning logic directly in the database layer. This means: ▪️ Faster planning runs ▪️ Real-time material shortage visibility ▪️ Better performance for large data volumes ▪️ More frequent planning cycles SAP introduced MRP Live primarily through transaction MD01N and equivalent Fiori apps. Why MRP Live is Important Traditional MRP in legacy SAP ERP systems could take hours to complete, especially for companies with: ▪️ Thousands of materials ▪️ Multiple plants ▪️ Complex BOM structures ▪️ High transaction volumes With SAP HANA’s in-memory processing, MRP Live drastically reduces runtime. Key Benefits of MRP Live 1. High-Speed Processing The biggest advantage is performance. Because calculations happen directly in the HANA database, MRP Live minimizes data transfer between the database and application server. This significantly reduces execution time. 2. Real-Time Planning Businesses can perform planning more frequently. This allows supply chain teams to quickly react to: ▪️ new customer orders ▪️ inventory changes ▪️ purchase delays ▪️ production issues This leads to more agile operations. 3. Multilevel BOM Planning MRP Live supports planning across multilevel BOM structures. It automatically plans: ▪️ finished goods ▪️ semi-finished materials ▪️ raw materials ▪️ components based on low-level codes, ensuring dependent requirements are calculated in the correct sequence. 4. Better User Experience with Fiori SAP provides modern Fiori apps for MRP monitoring and execution. This improves usability compared to traditional SAP GUI transactions. Common apps include: ▪️ Monitor Material Coverage ▪️ Manage Material Coverage ▪️ Schedule MRP Runs

From Forecast-Driven to Demand-Driven: The Power of DDMRP In today’s volatile markets, traditional MRP systems struggle to keep pace with fluctuating demand and long lead times. That is where Demand Driven Material Requirements Planning (DDMRP) steps in — a modern planning and execution methodology designed to protect flow and enhance responsiveness across the supply chain. What is DDMRP? DDMRP is an innovative approach that integrates the best of MRP, Lean, and Theory of Constraints (TOC). It focuses on decoupling points, dynamic buffers, and real demand signals rather than relying solely on forecasts. The goal? To align material flow with actual customer needs while reducing inventory volatility and improving service levels. The 5 Components of DDMRP (as shown in the image): 1️⃣ Strategic Inventory Positioning – Identify where to hold inventory within the supply chain to maximize responsiveness and minimize lead time. 2️⃣ Buffer Profiles and Levels – Establish inventory buffers (red/yellow/green zones) for different items based on demand variability and lead time. 3️⃣ Dynamic Adjustments – Continuously adapt buffer sizes based on real-time changes in demand, seasonality, and lead times. 4️⃣ Demand Driven Planning – Plan and execute replenishment based on actual consumption signals rather than forecasts. 5️⃣ Visible and Collaborative Execution – Use real-time visibility and shared information across functions to act proactively and maintain smooth material flow. Each step moves from Strategic → Tactical → Operational, ensuring agility at every level. MRP vs. DDMRP (Key Differences) 1️⃣ Driver → MRP: Forecast-driven → DDMRP: Actual demand-driven 2️⃣ Planning Logic → MRP: Push-based → DDMRP: Pull-based 3️⃣ Inventory Focus → MRP: Centralized, high levels → DDMRP: Strategically positioned buffers 4️⃣ Response Time → MRP: Slow, reactive → DDMRP: Fast, adaptive 5️⃣ Visibility → MRP: Departmental silos → DDMRP: Cross-functional collaboration collaboration 🏭 Real-Life Example In one of my projects within a manufacturing facility, we transitioned from traditional MRP to DDMRP. Before: Production orders were based on forecasts that often missed actual sales trends, leading to overstocked components and stockouts of key items. After implementing DDMRP: → Inventory dropped by 25% → Service level improved from 85% to 98% → Planners shifted focus from firefighting to proactive flow management The visibility and responsiveness achieved were game-changing. 💡 Conclusion DDMRP is not just a system tweak — it is a mindset shift toward aligning supply chains with real demand. By positioning, protecting, and pulling strategically, organizations can achieve higher agility and reliability in an unpredictable world. 👉 Have you implemented DDMRP in your organization? I would love to hear your experience and how it reshaped your planning process.

🔧 SAP MRP in Manufacturing — What They Don't Tell You Before Go-Live After years of SAP implementations in manufacturing environments, here's my honest take: MRP is not an IT project. It's a business transformation. When it works, it's magic — reactive firefighting becomes proactive, data-driven execution. When it fails, it's almost never the system. It's the data, the process, or the people. What SAP MRP actually does: It connects Sales → Planning → Procurement → Production → Inventory into one integrated flow — ensuring the right material, at the right quantity, at the right time. The real foundation? Master data. Your MRP output is only as good as your input: * Material Master (MRP views) * Bill of Materials * Routings & Work Centers * Lead Times & Lot Sizes Garbage in = garbage out. Every time. Why most implementations struggle: ❌ Unrealistic lead times ❌ No clear MRP controller ownership ❌ Cross-functional teams not aligned ❌ Users who don't understand the logic behind the run ❌ Treating exception messages as noise instead of signals What the successful ones do differently: ✅ Master data governance as a discipline, not a one-time fix ✅ Clear planning ownership per material/plant ✅ Procurement, production & warehouse aligned on the same logic ✅ Regular review of MD04 & exception messages ✅ Continuous improvement after go-live — not just at cutover The business impact when it's done right: → Higher service levels → Lower inventory costs → Stable, predictable production → Better supplier collaboration → Full end-to-end supply chain visibility MRP becomes the heartbeat of manufacturing planning. The companies that master it don't just run SAP better — they run their business better. Qu'est-ce qui a été le plus grand défi MRP dans votre expérience ? 👇 #SAP #MRP #SAPPP #SAPMM #SAPSD #SAPConsulting #SAPImplementation #SAPERP #SAPS4HANA #S4HANA #SupplyChain #SupplyChainManagement #SupplyChainOptimization #SupplyChainDigitalization #SupplyChainLeadership #Manufacturing #ManufacturingExcellence #ManufacturingOperations #SmartManufacturing #LeanManufacturing #ERP #ERPImplementation #ERPConsulting #DigitalTransformation #Industry40 #OperationalExcellence #ProcessImprovement #ProcurementStrategy #InventoryManagement #ProductionPlanning #DemandPlanning #MasterData #DataGovernance #BusinessTransformation #ProjectManagement #ChangeManagement #EnterpriseArchitecture #Logistics #Operations #Consulting

BOM–Master Schedule Alignment: The “Tiny” Miss That Triggers Big Delays The worst production delays often don’t come from big crises, they come from small mismatches between the Bill of Materials (BOM) and the Master Schedule. In recent work, tightening that link alone contributed to a 10% reduction in production delays and made order execution far more predictable. Here’s how that played out behind the scenes: - The BOM was treated as the single source of truth for materials, components, and quantities required for every finished good, while the Master Schedule translated demand into a time‑phased production plan. When those two were out of sync, MRP planned the wrong items, at the wrong levels, or at the wrong time showing up as missing parts, emergency expedites, and overtime on the shop floor. -Alignment started with verifying BOM accuracy and structure so every scheduled SKU had a complete, current component list before MRP ran. The Master Schedule was then explicitly linked to validated BOMs and realistic lead times, so planned orders reflected true material and capacity needs. -Exceptions like recurring shortages and frequent reschedules were monitored and fed back into BOM maintenance and scheduling rules, turning firefighting into continuous feedback. ERP planning tools were used to simulate schedule changes and check material availability ahead of freeze periods, reducing last‑minute surprises. By treating BOM governance and Master Scheduling as one integrated discipline, not two separate tasks, production became more predictable, delays dropped, and planners were finally able to shift their time from expediting to continuous improvement. What about you: where do you see the biggest BOM–schedule disconnects in your plant? #ProductionScheduling #MRP #SupplyChainExecution #ManufacturingPlanning

A consumer goods company spent 30 days trying to fix one SAP planning behaviour. Their MRP run was generating purchase requisitions for materials that already had usable alternates in stock. The system wasn't really counting wrong, it just didn't know to check the alternate group before raising a PR. Procurement was chasing requisitions that shouldn't have existed, planners were manually overriding outputs to compensate, and trust in the planning run was gone. _ _ This is how we approached this with Dodge AI: 👉 Two paths, one session: Plan Mode laid out MPN MRP Sets using standard SAP pooling logic, and a BAdI-driven MRP enhancement that made the planning run priority-aware across alternate material groups. The customer chose the BAdI path because their requirement depended on sequence, consume Priority 1 first, then alternates in order, generate a PR only if the entire alternate group was short. This was something which Pooling couldn't handle. 👉 Decision to build in one flow: Business substitution policy was formalized into implementable rules, BAdI enhancement code was written for MRP Live, and a Z-table was designed so the business could maintain alternate groups and priority order themselves without touching the codebase. 👉 Solution live in SAP: What the team couldn't land in a month, they shipped off the back of one Plan Mode session, deployed in SAP S/4HANA and resolved. _ _ At Dodge AI, we are reimagining how enterprise systems are built and maintained, and problems like this one are exactly where that starts. Excited to keep building 🚀