A discrete manufacturer is a company that produces distinct, countable items. Auto components, electronic assemblies, consumer durables, machinery, packaged industrial products.
SAP S/4HANA for discrete manufacturing is the way for bigger transition. For these businesses, the most significant change in moving from SAP ECC, the older generation of SAP, to SAP S/4HANA, the modern generation, takes place on the shop floor and at the planner’s desk. It is here that the daily rhythm of work shifts. Material planning behaves differently. Production scheduling is no longer a separate exercise from material requirements planning. The information available to a shift supervisor changes from end-of-day reports to live data.
If you are a CIO, IT director, or head of manufacturing evaluating this move, the operational changes described in this article will determine whether your S/4HANA program creates value or simply replaces one system with another.
Why this transition matters now
Two pressures are arriving together.
The first is a deadline. Mainstream maintenance for SAP ECC ends on 31 December 2027. After this date, customers who remain on ECC face higher maintenance costs and reduced support. A typical S/4HANA migration takes between eighteen and thirty-six months. Any organisation that has not begun a serious assessment by mid-2026 is already choosing between a hurried migration and the financial penalty of extended support.
The second is opportunity. India’s Production Linked Incentive scheme, known as the PLI scheme, has approved 806 applications across fourteen sectors with a total incentive outlay of ₹1.97 lakh crore. Committed investments stand at ₹1.76 lakh crore. The scheme is funding new factories and capacity expansions in electronics, auto components, white goods, advanced chemistry cells, specialty steel, and pharmaceuticals. Each of these is discrete manufacturing, and each requires an enterprise system capable of running new lines at full design throughput from the start.
A respected industry study by Horváth in 2025 found that only eight percent of S/4HANA migrations are completed on schedule, and more than sixty percent run over budget. A meaningful share of that overrun comes from manufacturers who treated the move as a technology upgrade and discovered, after going live, that their production planners and shop floor teams were operating in a new model nobody had prepared them for.
Three changes deserve close attention when it comes to SAP S/4HANA for discrete manufacturing
They concern material requirements planning, production scheduling, and shop floor execution.
Material requirements planning from overnight batch to on-demand
Material Requirements Planning, abbreviated as MRP, is the calculation that decides what to procure or manufacture, in what quantity, and by when, in order to meet customer demand. It is one of the most important calculations in any manufacturing business.
In the older SAP ECC system, MRP runs as a long overnight batch process. For a manufacturer with fifty thousand or more active material codes, the calculation can take several hours. Production planners arrive in the morning, review the resulting recommendations, and respond to issues. If a customer urgency arises during the day, or a supplier flags a shortage, the planner cannot easily re-run MRP and see the consequences. They must wait until the next overnight cycle.
In SAP S/4HANA, a redesigned version of this calculation called MRP Live operates very differently. The work is performed inside the underlying SAP HANA database, which holds data in computer memory rather than on disk and processes calculations in parallel. SAP and consulting practices have documented performance improvements of up to ten times faster than the older method. A run that used to take hours can complete in minutes.
The practical consequence is straightforward. A planner can now run material requirements planning during the working day, for a single product family or an entire plant, and see the result before the next coffee break. Planning becomes responsive to events as they occur, rather than tied to a fixed overnight cycle.
Two trade-offs deserve mention. First, certain custom programs that organisations wrote on top of MRP in ECC do not work with MRP Live. Materials affected by such custom logic fall back to the slower classic method. Second, the discipline of keeping master data accurate, the records that describe materials, suppliers, lead times, and so on, becomes more important than ever. The faster the calculation, the more clearly poor data shows up in the result.
Production scheduling: planning and feasibility merge
In SAP ECC, material requirements planning and detailed production scheduling are two separate activities. MRP produces a plan that assumes unlimited capacity. The detailed scheduler then takes this plan and reconciles it against the reality of available machines, operator shifts, tooling, and changeover times. Discrepancies between what the plan asks for and what the shop floor can deliver are routine. The scheduler spends much of the day adjusting, splitting, and resequencing.
SAP S/4HANA includes a module called Production Planning and Detailed Scheduling, abbreviated as PP-DS, which is integrated into the core system. PP-DS evaluates capacity, machine availability, setup times, sequencing, and material availability together. The plan it produces is feasible from the start.
For a manufacturer running, for example, a stamping shop with multiple presses and a wide variety of part numbers, this changes the working day in concrete ways. The plan a scheduler receives in the morning can already be honoured. Setup times can be optimised by sequencing similar products together, which directly reduces changeover hours on lines with high product mix. Coordination across plants and across stages of production smooths the flow rather than fixing problems at each handover.
The honest part of the conversation is what PP-DS requires to work well. It needs accurate manufacturing routings, current cycle times, properly maintained setup matrices, and reliable data on labour and tool capacity. Many manufacturers carry routing data in their ECC system that has not been reviewed in years. Activating PP-DS without first cleaning up this master data produces a faster way to schedule an inaccurate plan, which is not a useful outcome. The technical activation is the easier part. The data preparation is where the real work lies.
Shop floor execution: the gap between data and decision narrows
The improvements in planning and scheduling translate into changes at the shop floor terminal as well.
In SAP S/4HANA, when a production order is released, the check on material availability happens against live inventory rather than yesterday’s snapshot. When an operator confirms a production step or records component consumption, the data is reflected immediately and is available to the next planning calculation. Quality holds, maintenance downtime, and production status all sit on the same data layer. The overnight reconciliation processes that used to rebuild consistency between modules are no longer required.
Modern, web-based dashboards designed for tablets and mobile devices, built on SAP’s Fiori user experience, replace the printed daily plan that used to be hours out of date by the start of the second shift.
For a manufacturer that has invested in new capacity under the PLI scheme, this layer determines whether the new line operates at its design throughput or significantly below it. Two new presses do not produce twice the output if the data round-trip from the floor to the planner and back still takes half a day. The S/4HANA architecture removes that delay. However, this benefit is only realised if execution practices are redesigned alongside the system.
The trade-offs that deserve honest acknowledgement
Three considerations are often left out of the standard project brochure.
The discipline of keeping master data accurate becomes a daily responsibility, not a periodic IT cleanup task. Materials with outdated routings, missing alternate resources, or absent setup matrices either fall back to the slower planning method or generate plans the system cannot honour.
Custom programs from the ECC era must be reviewed and, in many cases, rewritten in line with SAP’s recommended approach, often called Clean Core. The promised performance gains from MRP Live and the planning quality of PP-DS depend on this review being treated as a serious workstream, not a footnote.
Training for production planners, schedulers, and shop floor users requires planned investment. The visual interfaces in S/4HANA differ from the screens in ECC, and the underlying logic of working with the new system is different in places. This is a real workload, not an afterthought.
The choice of migration approach, whether to convert the existing ECC system or to implement S/4HANA as a fresh installation, also affects how much of this can be addressed during the project versus afterwards. For PLI-driven capacity programmes operating against the ECC end-of-maintenance deadline, this decision deserves more strategic attention than it often receives.
Practical guidance
If your organisation is evaluating SAP S/4HANA, treat the shop floor and the planning function as a primary scope of the project, not a secondary stream. Conduct an operating model assessment alongside the technical readiness check. Size the master data work realistically. Plan for production planner and scheduler training in the first year of operation.
If you are assessing S/4HANA for a discrete manufacturing operation, or experiencing shop floor performance gaps after a recent go-live?