Most manufacturers scope their SAP S/4HANA migration as a finance and IT project. That is a mistake with a specific, predictable cost: production planning is one of the modules SAP rebuilt at the logic level, not just the database level, and teams that treat SAP S/4HANA production planning as a like-for-like move discover the gaps during user acceptance testing, when fixing them is expensive and the go-live date is already fixed.

Bottom line: SAP S/4HANA production planning is not the same system running faster. Planning horizons, source-of-supply logic, and the relationship between MRP and detailed scheduling all change. If your project plan does not account for that, you are not planning a migration. You are planning a surprise.

This piece maps the specific changes to SAP S/4HANA production planning that affect a manufacturing plant's day-to-day operation, and what each one means for how you scope the project.

Why Production Planning Isn't a "Lift and Shift" Module

Bottom line: Finance and basis teams can largely map ECC processes onto SAP S/4HANA one-to-one. Production planning teams cannot, because SAP redesigned how the planning engine itself works.

In SAP ECC, material requirements planning ran as a batch job, capacity planning was a separate exercise, and detailed scheduling lived in a bolt-on system (APO/PP/DS) connected through scheduled data transfers. Under SAP S/4HANA production planning, that architecture is gone. Planning runs in-memory, production versions become mandatory master data, and the detailed scheduling engine sits inside the same digital core as MRP.

None of this is cosmetic. Each change touches master data, planner workflow, and system configuration that a manufacturing plant has often run unchanged for a decade. A CIO or VP of Manufacturing IT scoping SAP S/4HANA production planning needs to treat it as a functional redesign with a technical migration attached, not the reverse.

The sections below walk through the specific changes that matter for project scope, in the order a planning team is likely to hit them.

MRP Live Replaces the Overnight Batch Run

Bottom line: SAP S/4HANA production planning replaces the ECC batch MRP run with MRP Live, an in-memory planning engine that changes both the speed and the scope of every planning cycle.

In SAP ECC, MRP typically ran overnight, in a batch window, using transaction codes such as MD01, MD02, and MD03. Planners waited for non-peak hours because the calculation load could not run alongside daily operations without slowing the system down.

SAP S/4HANA production planning runs this differently. MRP Live (transaction MD01N) processes the planning run in-memory, which SAP designed to run during normal operating hours rather than only overnight. It also removed a planning-horizon shortcut used in ECC: the NETPL processing key, which limited how far out the system calculated demand to keep batch runtimes manageable. Under SAP S/4HANA production planning, MRP Live plans across the full horizon by default.

For a plant that has spent years tuning its overnight batch window, this is a genuine operational change, not a performance upgrade. Planners need to understand what a full-horizon, more frequent planning run means for how often plans shift and how the team reacts to those shifts. This is also one of the areas where legacy custom reports and interfaces built against the old MRP transactions may need rework, since SAP S/4HANA production planning is built around the newer engine even though classic transaction codes remain technically available.

Production Versions Are No Longer Optional

Bottom line: SAP S/4HANA production planning requires a production version for every material that MRP or a production order needs to source, and materials without one become unplannable.

In SAP ECC, production versions existed but were frequently left unmaintained. A material could still be planned and produced through a bill of material and routing combination without one, particularly in older, brownfield landscapes where master data hygiene was never enforced.

That option does not exist in SAP S/4HANA production planning. Production versions are the only valid source of supply for MRP planned-order creation and production-order creation. If a material's bill of material or routing alternative is not tied to a maintained production version, the system cannot source it, and the material effectively falls out of automated planning.

For a plant with years of ECC master data, this is one of the highest-risk items in a migration. A manufacturing IT leader should expect a dedicated data-quality workstream focused on production version maintenance before cutover, not as a cleanup task discovered afterward. SAP provides a note-driven path for this (SAP Note 2655077 addresses automatic production version creation during migration), but automatic creation does not guarantee correctness for every material, and a manual review is still the responsible approach for critical production lines.

Classic MRP and PP/DS Are No Longer Two Separate Systems

Bottom line: SAP S/4HANA production planning integrates capacity-constrained detailed scheduling into the core planning engine, removing the data-transfer step that ECC required between MRP and APO.

In SAP ECC, material requirements planning and detailed capacity scheduling were strictly separated. Getting a feasible, capacity-aware plan meant running MRP first under an assumption of infinite capacity, then running a separate detailed scheduling step in APO/PP/DS, connected through the Core Interface (CIF). Any change on one side required a data transfer to reach the other, and even viewing a production scheduling board meant enabling PP/DS and running a CIF transfer.

Under SAP S/4HANA production planning, PP/DS runs inside the same digital core as classic MRP, and MRP Live's planning logic is integrated with it rather than fully separated from it. That means the constant CIF synchronization ECC required between the two systems is no longer the operating model.

This matters for two groups on a migration project. Planners who currently work across two systems and two master-data sets need a workflow that assumes a single integrated environment. And any team that built custom interfaces or reports around the old CIF-based data flow needs to re-evaluate them, since the underlying integration pattern in SAP S/4HANA production planning is different by design, not by configuration choice.

Storage-Location Planning Moves to the MRP Area Level

Bottom line: SAP S/4HANA production planning moves storage-location-level planning control up to the MRP area, which changes how a plant excludes scrap locations or plans subcontractor stock separately.

In SAP ECC, a storage location could be excluded from MRP entirely, which plants commonly used for scrap or rejection locations, or planned separately, which was common for subcontractor stock. That control lived at the storage-location level in the material master.

SAP S/4HANA production planning moves that control to the MRP area level instead. The functional intent is similar - plants still need to exclude or separately plan certain locations - but the configuration point has changed, and MRP area setup becomes a required step rather than an optional refinement.

For manufacturing IT teams, this is a smaller item than production versions or MRP Live, but it is a common point where a migration project underestimates configuration effort, because it looks like a minor field-level change until a team discovers mid-cutover that a subcontractor or scrap process no longer plans the way it used to.

What This Means for Your Migration Project Plan

Bottom line: Every functional change above becomes a scoping item, and manufacturing plants that treat SAP S/4HANA production planning as a technical conversion tend to discover these items later and at higher cost than plants that scope them upfront.

Put together, four items belong on a manufacturing IT leader's SAP S/4HANA production planning workstream before cutover:

  • A production version audit and cleanup, since incomplete master data here directly blocks MRP from sourcing a material.
  • A review of how MRP Live's full-horizon, in-memory planning changes planning cadence and planner response, not just system performance.
  • An assessment of any custom reports, interfaces, or workflows built around the old CIF-based MRP-to-PP/DS data flow.
  • MRP area configuration for any storage location currently excluded or separately planned.

None of this replaces a broader migration plan covering finance, basis, and change management. It is the manufacturing-specific layer that a generic SAP S/4HANA migration plan tends to underweight, because production planning changes do not show up the way a finance close-cycle change does. They show up on the shop floor, during the first planning run after go-live.

ITChamps works with manufacturing IT leaders on this exact scoping problem as part of its SAP S/4HANA Migration and SAP AMS practices, starting from a production planning readiness assessment rather than a generic migration checklist. For a plant preparing for its own SAP S/4HANA production planning transition, that assessment is the practical next step, before the project timeline is fixed and before the production version cleanup becomes a cutover-weekend fire drill.

Frequently Asked Questions

Does SAP S/4HANA production planning use the same transaction codes as ECC?

Some classic transaction codes, such as MD01, MD02, and MD03, remain technically available, but SAP S/4HANA production planning is built around MRP Live (MD01N) as the recommended engine, and planning behavior differs between the two even when the classic codes still work.

Do we need to redo all of our production versions before migrating?

Every material that MRP or a production order needs to source requires a maintained production version under SAP S/4HANA production planning. SAP provides a migration note for automatic production version creation, but a manual review of critical materials is still advisable, since automatic creation does not verify correctness for every case.

Does SAP S/4HANA production planning eliminate the need for PP/DS as a separate license or module?

No. PP/DS remains a distinct capability with its own licensing consideration, but under SAP S/4HANA production planning it runs inside the same digital core as classic MRP, removing the CIF-based data transfer that ECC required between the two.

How long does a production planning-specific migration workstream typically take?

Timelines vary by the state of a plant's existing master data, the complexity of its custom interfaces, and its production version coverage, so ITChamps does not publish a general timeline. A readiness assessment is the appropriate way to scope a timeline for a specific plant's environment.

Should production planning be scoped as part of the main migration project or as a separate initiative?

It should be a distinct workstream within the main SAP S/4HANA migration project, since production version cleanup, MRP Live behavior changes, and PP/DS integration each require input from planning and shop-floor teams that a finance- or basis-led project team may not otherwise engage early enough.