What happens to SAP modifications (SPAU/SPDD) in an S/4HANA conversion?

Modifications are the custom code that fights SAP. Count them early, because each one is a decision you will otherwise make under deadline.

By Chris Benson — 30 years in SAP SD5 min read

The short answer

In an ECC to S/4HANA system conversion, every modification to SAP standard objects has to be reconciled against the new SAP code. Dictionary modifications are adjusted in transaction SPDD and repository modifications in SPAU, and each one forces a decision: reset to SAP standard, keep and merge by hand, or redesign. Modifications are different from enhancements and user exits, which live in SAP-provided extension points and usually carry over with far less rework. The cheapest modification is the one you retire before the conversion starts, which is why a modification inventory belongs in the fit-to-standard phase, not in the cutover weekend.

What is the difference between a modification and an enhancement?

A modification changes an SAP-delivered object directly: a standard program, a function module, a data dictionary element. SAP records the change, and from then on your version and SAP's version of that object diverge. An enhancement or user exit uses a place SAP deliberately left open for customers, such as a BAdI, a customer exit, or an append structure, so SAP's own object stays untouched.

That distinction decides how painful a conversion is. Enhancements are still subject to simplification checks, but they are separate objects you own. Modifications sit inside code SAP is replacing, so they collide with every change SAP ships.

What do SPDD and SPAU actually do?

During the conversion, the SAP tooling detects objects you modified that SAP also changed in the target release. SPDD is the modification adjustment for dictionary objects and runs early, because later phases depend on a consistent dictionary. SPAU covers repository objects such as programs, function modules and screens, and runs after the new release is in place.

Each flagged object lands in a worklist. For every entry someone has to choose: reset to the SAP original and lose the customization, adopt your version and merge in SAP's changes, or take SAP's version and rebuild the requirement another way. Large worklists are where schedules slip, because each entry needs a person who understands the business reason for the change.

Why does the worklist surprise people?

Teams often size the conversion from the number of custom Z objects, which sit outside SPAU, and underestimate the modified standard objects, which do not. Modifications made years ago by people who have left are the hardest, because the original requirement was never written down.

The first pass is therefore detective work, not engineering. For each modification you need the business rule it implements and whether S/4HANA now delivers that rule as standard.

  • Reset candidates: the requirement is now covered by standard S/4HANA functionality, so the modification can be dropped.
  • Move-to-extension candidates: the logic is still needed but can be re-implemented in a BAdI or in side-by-side extensibility, which is the clean core direction.
  • Genuine keep-and-merge: rare, expensive, and worth a documented reason because it reintroduces the upgrade burden on every future release.

How do you reduce the SPAU burden before conversion?

Start with usage data. Code that nobody executes is the easiest decision; running the system's usage and ATC analysis early shows which modified objects are dead weight. In our reference estate, a live ECC system we analysed, a large share of custom objects turned out to be retire candidates once the business rule was traced; a customer's numbers come from their own system, not from ours.

Then classify each modification by the rule it carries, route the survivors to extension points, and write the acceptance test before touching the code. That order turns SPAU from a discovery exercise into confirmation of decisions already made. Any configuration or transport changes that follow should still be drafted for your change board to approve in development systems, never applied automatically.

Frequently asked

Are user exits and BAdI implementations handled in SPAU?

Generally no. SPAU deals with modified SAP standard objects. Enhancements and user exits are separate customer objects, though they can still be affected by simplification items and need their own checks, which is why a full custom code inventory covers both.

Can we skip SPAU adjustments by resetting everything to SAP standard?

You can reset many objects, but resetting discards the customization, so it is only safe where the business requirement is covered by standard S/4HANA or has been retired. Resetting blindly can silently remove a pricing rule, a validation or a control that finance or compliance relies on.

Do modifications conflict with a clean core strategy?

Yes. A clean core means keeping SAP standard objects unmodified and placing differentiating logic in supported extension points. Every modification you keep is a deliberate exception that must be re-adjusted on each future SAP release, so most organizations treat modifications as the first thing to eliminate.

See your own Clean Core Score.

Run the free S/4 readiness scan in under a minute — no system access required.

Keep reading