What happens to SAP GUI transactions and custom reports when you move to S/4HANA and Fiori?

The UI is not the migration. But every Z-transaction behind it is a decision you have to make on purpose.

By Chris Benson — 30 years in SAP SD5 min read

The short answer

Most SAP GUI transactions keep working after an ECC to S/4HANA conversion, because SAP GUI remains supported. Fiori is the strategic user experience, though, and S/4HANA moves many standard transactions into Fiori apps while a few are deprecated or replaced. Custom Z-transactions and Z-reports are the real exposure: each one either still runs, runs but reads data in a new structure, or breaks because it touched a table that no longer exists. The practical approach is to inventory every custom transaction by actual usage, decide retire, keep in GUI, or rebuild as a Fiori app on the clean-core extensibility model, and only then size the Fiori work.

Does SAP GUI go away in S/4HANA?

No. SAP GUI is still supported for S/4HANA, and many classic transactions continue to run after a system conversion. That is why a UI cutover is not what makes migrations hard. SAP's direction, however, is Fiori: new capability and simplified processes are delivered as Fiori apps, and some legacy transactions are marked obsolete in SAP's simplification list.

So the useful framing is not GUI versus Fiori. It is which of your transactions are standard, which are custom, and which of those still earn their keep.

Why custom Z-transactions are the real exposure

Standard transactions are SAP's problem; SAP publishes what changes. A Z-transaction or Z-report is yours. After conversion, each custom object falls into one of three buckets: it runs unchanged, it runs but returns different results because the underlying data model changed (the universal journal and the business partner model are typical causes), or it fails outright because it reads a table or calls a function that was replaced.

You find out which bucket applies with static checks such as ABAP Test Cockpit against the S/4HANA readiness rules, combined with usage data from the ECC system. Neither alone is enough.

How to decide: retire, keep in GUI, or rebuild in Fiori

Usage data is the fastest filter. Many estates carry a large share of custom reports nobody has run in a year or more. Those are retirement candidates, not rebuild candidates. Do not spend Fiori effort on a report with no users.

For what remains, ask whether S/4HANA now does the job as standard, whether the transaction can stay in SAP GUI at low cost, or whether the business wants a modern interface. Only the last group justifies a Fiori build.

  • Retire: no meaningful usage, or replaced by a standard Fiori app or embedded analytics.
  • Keep in GUI: stable, low-change, internal power-user transactions that pass the readiness checks.
  • Rebuild: high-volume or cross-functional processes where the interface itself is costing the business time.

Where clean core fits

If you rebuild, build it on the extensibility model SAP recommends for a clean core: in-app key-user extensibility where it is enough, and side-by-side extensions for anything larger, rather than modifying standard objects. The objective is that the next upgrade does not turn today's Fiori app into tomorrow's migration problem.

On a reference estate, a live ECC system we analyzed, a meaningful share of custom objects turned out to be re-implementations of what S/4HANA now does as standard. That figure is specific to that estate; a customer's numbers come from reading their own system.

Frequently asked

Do we have to move every user to Fiori at go-live?

No. SAP GUI remains supported, so a phased approach is valid. Many programs move high-volume roles to Fiori first and leave stable power-user transactions in GUI until there is a business reason to change them.

How do we find which Z-reports are safe to retire?

Combine usage statistics from your ECC system with a static code check against S/4HANA readiness rules. Objects with no recent usage are retirement candidates; objects that are used and flagged need a retire, fix, or rebuild decision with a business owner.

Does Fiori adoption change our authorization model?

Yes, it usually does. Fiori apps are exposed through catalogs, groups, and spaces, so roles built around GUI transactions typically need rework. Plan authorization redesign alongside the UI decisions rather than after them.

See your own Clean Core Score.

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

Keep reading