Picture this: it is migration weekend. The cutover window is live, your team has been running parallel systems for weeks, and then the first MRP run in S/4HANA fails. The shop floor goes dark. Procurement cannot release purchase orders. Production schedulers are staring at blank screens. By Monday morning, a single failed MRP execution has cost the business more than the entire migration budget.
This is not a hypothetical. It is the outcome that VP-level manufacturing IT leaders describe when asked what keeps them up at night before an S/4HANA migration.
The 2027 end of mainstream maintenance for SAP ECC is a fixed deadline. There is no extension on the roadmap. But for manufacturing organizations running complex, deeply customized production planning landscapes, the real challenge is not whether to migrate - it is how to do it without halting the factory floor. The stakes are highest inside the PP, MRP, and PP/DS layers of your SAP system, where years of custom ABAP logic are woven directly into operational continuity.
This guide is a technical mapping of exactly what changes, what breaks, and what needs reconfiguration when manufacturing modules make the move to S/4HANA - written for the people accountable for factory-floor uptime, not IT project management.
The 2026 Mandate: Why S/4HANA for Manufacturing is Non-Negotiable
SAP ECC mainstream maintenance ends in 2027, and manufacturing organizations that have not begun their S/4HANA transition by mid-2026 are running out of runway to execute safely.
SAP extended its original 2025 deadline once. It has stated publicly that 2027 is firm. For manufacturing operations, this carries a specific operational risk that generic IT migrations do not: production systems cannot be taken offline for extended periods, and manufacturing landscapes carry the highest density of custom ABAP code of any SAP module area.
According to Gartner research, more than 70% of large enterprises running SAP ECC have not yet completed their S/4HANA migration as of 2024. Among discrete and process manufacturers, the complexity of custom shop-floor integrations and MRP logic is the most frequently cited reason for delay. IDC data from 2024 shows that unplanned manufacturing downtime costs industrial companies an average of $125,000 per hour - a figure that frames the cost of a failed migration execution with clarity.
The urgency is not just about software support. Staying on ECC past 2027 means operating on an unsupported platform, absorbing the cost of SAP's extended maintenance program (at a significant premium), and falling behind on capabilities that your supply chain partners, customers, and competitors are already using.
For manufacturing IT leaders, 2026 is not the year to finalize a business case. It is the year to be deep into technical remediation and testing.
MRP After Migration: The Shift to MRP Live
MRP Live, the S/4HANA replacement for ECC's classic MRP engine, processes planning runs orders of magnitude faster - but it runs natively on the HANA in-memory database, which means any custom ABAP code touching the MRP execution stack must be assessed and remediated before go-live.
What is MRP Live and How Does It Differ from ECC MRP?
In ECC, Materials Requirements Planning runs as a sequential, batch-based process. The classic MRP engine reads through material master data, open orders, stock levels, and planned requirements in a structured sequence, writing results back to the database as it progresses. For large manufacturing plants with complex bills of materials and thousands of SKUs, a full MRP run could take hours.
MRP Live is S/4HANA's redesigned planning engine. Instead of sequential database reads and writes, MRP Live loads relevant planning data into HANA's in-memory layer at the start of the run, processes the entire planning sequence in memory, and writes results back in a single commit. The architecture eliminates the iterative database I/O that made classic MRP slow.
The practical result: MRP runs that took four to six hours in ECC can complete in under thirty minutes in S/4HANA environments with comparable data volumes. For manufacturing organizations running multiple MRP variants - make-to-stock, make-to-order, and kanban - across multiple plants, this is a material operational gain.
But the architectural shift creates an immediate compatibility problem. Classic MRP in ECC exposed a series of user exits and Business Add-Ins (BAdIs) that manufacturers used to inject custom logic - specialized lot-sizing routines, plant-specific sourcing hierarchies, exception message filters tied to legacy shop-floor systems. MRP Live does not support those same exit points. The BAdI framework is different. The HANA-optimized code paths are different. And the classic function modules that underpinned many Z-programs simply do not exist in the same form in S/4HANA.
This is the first place migrations break.
The Custom Code Hurdle: Remediating Z-Programs for MRP Live
Custom code remediation is the highest-risk workstream in any manufacturing S/4HANA migration - and the one most frequently underestimated in project scoping.
The remediation process follows a defined sequence. First, SAP's Custom Code Migration Cockpit (or a partner-led equivalent) scans the ECC system for all ABAP objects that reference MRP-related function modules, tables, and BAdIs flagged as unavailable or changed in S/4HANA. This produces a prioritized list of Z-programs and enhancements that require action.
From there, each object must be classified. Some custom logic can be retired entirely - the underlying business requirement is now handled by standard S/4HANA functionality. Some logic must be rewritten to use the new BAdI framework that MRP Live supports. Some objects flag as "use with caution" - technically functional, but running outside the HANA-optimized code path, which degrades performance and reintroduces the bottlenecks MRP Live was designed to eliminate.
The critical decision at each object is not just "does this code run?" but "does this code run correctly at HANA speed without generating planning errors that propagate to the shop floor?"
Manufacturing organizations with ten or more years of ECC customization typically surface between 200 and 600 custom objects in the MRP-adjacent space alone. Remediating and retesting each one is not a sprint. It is a structured workstream that needs to begin well before the migration project's technical cutover phase.
Actual MRP run-time improvements vary based on landscape complexity, data volume, and the extent of custom code remediation completed prior to go-live.
Production Planning (PP) and Embedded PP/DS in S/4HANA
S/4HANA restructures production planning by embedding Advanced Planning and Scheduling (PP/DS) directly into the core system - eliminating the ECC-era need for a separate APO system, but also requiring deliberate activation and configuration to replace the functionality manufacturers relied on APO to deliver.
Unifying PP and PP/DS on the HANA Database
In ECC, manufacturers requiring detailed finite-capacity scheduling or constraint-based production optimization ran SAP APO (Advanced Planning and Optimization) as a separate system alongside ECC. APO communicated with ECC via the Core Interface (CIF) - a data exchange layer that was notoriously sensitive to timing, data quality, and configuration. APO failures cascaded into ECC, and keeping the two systems in sync was a persistent operational burden.
S/4HANA changes this architecture entirely. PP/DS - the production planning and detailed scheduling component formerly housed in APO - is embedded directly inside S/4HANA, running on the same HANA database as the rest of the system. There is no separate APO installation, no CIF to maintain, and no synchronization delays.
The unified data model means that production orders, capacity requirements, material movements, and scheduling results all live in the same in-memory layer. Planners working in the S/4HANA production planning cockpit are looking at live data, not a snapshot that is minutes or hours old.
For manufacturers who used APO: the embedded PP/DS must be explicitly activated in S/4HANA. It does not come live by default. Activation requires configuration of the PP/DS optimizer settings, definition of planning-relevant products and resources, and - critically - the migration of any custom heuristics or optimization profiles that existed in the legacy APO environment.
For manufacturers who did not use APO: embedded PP/DS is now accessible at no additional license cost within the S/4HANA suite. This represents a genuine architectural upgrade - finite scheduling capabilities that previously required a separate system and separate implementation are now within reach through configuration.
Impact on Shop-Floor Connectivity and Integration
The consolidation of PP and PP/DS onto a single HANA platform affects more than planning logic - it changes how production orders and scheduling results reach the shop floor.
In ECC landscapes, shop-floor execution systems (MES, SCADA, third-party scheduling tools) typically connected to ECC via IDocs, BAPIs, or custom RFC calls. Many of these integration patterns remain valid in S/4HANA. However, the data structures underlying production orders and capacity requirements have changed in S/4HANA, and any MES integration that reads directly from ECC-specific database tables - rather than from standard API surfaces - will require redesign.
The Manufacturing Execution integration framework in S/4HANA uses the Production Integration and Backflush (PIF) module and, in more modern implementations, SAP's Digital Manufacturing (DM) suite. Organizations with SAP ME or custom MES connectors need to validate each integration point against the S/4HANA data model before go-live, not after.
Shop-floor downtime during cutover is the outcome that manufacturing IT leaders most want to avoid. The integration validation workstream is where that risk is controlled or ignored.
The Hidden Risk: Manufacturing Custom Code Remediation
Manufacturing SAP landscapes carry more custom ABAP code than almost any other industry vertical. That code density is not a sign of poor architecture - it reflects real operational complexity. But it is the single biggest variable in determining whether your S/4HANA migration succeeds on schedule.
Discrete manufacturers building complex, configurable products often have custom lot-sizing logic tied to production line constraints that SAP's standard MRP algorithms do not accommodate. Process manufacturers in chemicals or food and beverage frequently have custom batch classification, shelf-life management, or regulatory-compliance exits built directly into production order processing. Automotive suppliers often run custom scheduling prioritization tied to customer-specific delivery sequences.
None of this code is unnecessary. All of it requires assessment before it can be cleared for S/4HANA.
The remediation lifecycle has four phases:
- Discovery: Automated scanning of the ECC custom code base using the SAP Readiness Check and the Custom Code Migration Cockpit, producing a prioritized object list with S/4HANA compatibility ratings.
- Classification: Each flagged object is reviewed by ABAP and functional consultants with S/4HANA manufacturing expertise. The classification result - retire, rewrite, refactor, or accept with performance caveat - determines the remediation path.
- Remediation and unit testing: Custom objects are rewritten or refactored to align with S/4HANA's supported extension framework. Each object is unit-tested in an S/4HANA sandbox environment, specifically under MRP Live execution conditions.
- Integration and regression testing: Remediated objects are tested end-to-end in an S/4HANA environment with production-representative data volumes. MRP runs are executed and results are validated against ECC baseline outputs. Shop-floor integration messages are traced to confirm data integrity.
The mistake organizations make is treating custom code remediation as a task to begin after functional configuration is complete. It is a parallel workstream that must start at project initiation. Code discovered late in the project creates scope pressure that forces either timeline extension or risk acceptance - and in manufacturing, accepted risk often means production disruption.
How ITChamps Secures Your Factory Floor Migration
ITChamps brings SAP Gold Partner credentials, a proprietary readiness framework, and a track record of manufacturing-specific S/4HANA migrations to organizations that cannot afford to learn by failing.
The manufacturing migration challenge is not generic. A consultancy that excels at financial module migrations may lack the production planning depth to identify a custom MRP heuristic that will break MRP Live execution. The vertical expertise required to assess a discrete manufacturer's scheduling customizations is different from what it takes to migrate a process manufacturer's batch management exits.
ITChamps' proprietary S/4HANA Readiness Framework identifies custom code remediation needs 30% faster than standard assessment approaches, giving manufacturing IT teams earlier visibility into their true migration scope - before commitments to timelines and budgets are finalized. As an SAP Gold Partner, ITChamps has executed over 50 successful S/4HANA transitions across India, the UK, and globally, with a specific delivery focus on manufacturing-sector clients navigating complex PP, MRP, and PP/DS landscapes.
The engagement model is built around manufacturing operational reality. Cutovers are planned around production calendars. Testing cycles are structured to validate MRP Live outputs against ECC baseline runs. Shop-floor integration points are catalogued and validated before any technical switch is thrown.
For organizations at the stage of defining their migration scope, ITChamps offers a Manufacturing S/4HANA Readiness Assessment - a structured technical engagement that maps your custom code exposure, validates your PP and MRP architecture against S/4HANA requirements, and produces a remediation roadmap with realistic timelines tied to your specific landscape complexity.
The assessment is the inflection point between a migration plan that looks credible on a slide and one that holds up under the technical scrutiny of a factory-floor go-live.
Book a Manufacturing S/4HANA Readiness Assessment with ITChamps →
Frequently Asked Questions
Does MRP Live in S/4HANA replace all classic MRP functionality from ECC?
MRP Live replaces the classic MRP engine (MDBT transaction) as the primary planning run mechanism in S/4HANA. Standard MRP types (MRP, consumption-based planning, reorder point planning) are supported. However, MRP Live does not support the same user exits and BAdIs that were available in classic ECC MRP. Any custom logic injected through those legacy exit points must be assessed and remapped to the new S/4HANA extension framework before the system can execute MRP Live correctly. Classic MRP is still available in S/4HANA as a fallback option, but SAP's direction is MRP Live, and running classic MRP in S/4HANA foregoes the primary performance and architecture benefits of the migration.
Do we need a separate SAP APO system after migrating to S/4HANA?
No. PP/DS - the Advanced Planning and Scheduling capability that was previously delivered through SAP APO - is embedded directly within S/4HANA and runs on the same HANA database. Organizations that relied on APO for finite scheduling, constraint-based planning, or detailed capacity optimization can access equivalent capabilities through embedded PP/DS without maintaining a separate APO installation or the Core Interface (CIF) that synchronized data between ECC and APO. Organizations migrating from APO will need to migrate their custom heuristics, optimization profiles, and planning configurations into the embedded PP/DS environment as part of the project.
How long does custom code remediation take for a manufacturing SAP landscape?
Remediation timelines depend directly on the volume and complexity of custom ABAP objects in the ECC landscape. Manufacturing organizations with a decade or more of customization typically surface between 200 and 600 custom objects requiring assessment in the PP, MRP, and shop-floor integration areas alone. A structured remediation workstream - covering discovery, classification, rewrite, and testing - generally runs in parallel with the broader migration project over a period of six to eighteen months, depending on landscape complexity. Migration timelines and MRP Live compatibility depend on the volume of custom code in the legacy ECC system; there is no universal timeline. The correct approach is to conduct a formal readiness assessment before committing to a go-live date.
What happens to shop-floor MES integrations when migrating from ECC to S/4HANA?
Integration patterns that use SAP standard APIs - BAPIs, standard IDocs, and RFC-enabled function modules - generally remain valid in S/4HANA, though specific data structures underlying production orders and capacity requirements have changed. Integrations that read directly from ECC-specific database tables (Z-tables or ECC-era transparent tables) require redesign, because many of those tables are restructured or eliminated in the S/4HANA data model. Organizations should catalogue every MES and shop-floor integration point early in the project, map each one to its S/4HANA equivalent, and complete integration testing with production-representative message volumes before go-live.
What is the SAP ECC end-of-maintenance deadline for manufacturing organizations?
SAP has set 2027 as the end of mainstream maintenance for SAP ECC. After this date, organizations remaining on ECC must either operate on an unsupported platform or enroll in SAP's Extended Maintenance program at an additional cost premium. SAP has stated that 2027 is a firm deadline. For manufacturing organizations with complex migration workstreams, beginning technical remediation and testing in 2025 or 2026 is necessary to allow sufficient time for a safe, validated cutover before the deadline.
SAP, SAP S/4HANA, SAP ECC, SAP APO, and SAP HANA are trademarks or registered trademarks of SAP SE in Germany and other countries. All other product and company names mentioned are used for identification purposes only and may be trademarks of their respective owners.
Actual MRP run-time improvements and total cost of ownership savings vary based on landscape complexity, data volume, and the extent of custom code remediation completed prior to go-live. Migration timelines and MRP Live compatibility depend on the volume and complexity of custom code in the legacy ECC system. No guaranteed timelines or ROI outcomes are implied by any content in this article.
ITChamps' S/4HANA Readiness Framework speed claim is based on internal benchmarking against standard SAP Readiness Check workflows. Results may vary.