Skip to content

170 practical guides on SAP, cybersecurity and AI, $9.99 each. Shop all books ›

0

Blog›SAP

How SAP Authorizations Change from SAP ERP to SAP S/4HANA

Moving from SAP ERP to S/4HANA changes transactions, the business partner, Fiori access and SU24 defaults. Here is what changes in roles and how to convert them.

On the first morning after an S/4HANA conversion, the service desk queue fills with the same kind of ticket: “transaction not found”, “app tile missing”, “no authorization”. The business processes look the same as last week, but the roles behind them were built for a different system. Knowing what changes in authorizations between SAP ERP and S/4HANA is how security teams avoid that morning.

When you move from SAP ERP (ECC) to SAP S/4HANA, roles change in five places: obsolete and replaced transactions, the business partner replacing customer and supplier maintenance, a simplified data model, SAP Fiori apps with their own catalogs and services, and new SU24 authorization defaults. Roles that ignore any of these break on day one or quietly give more access than intended.

In one sentence: S/4HANA changes the transactions, objects, apps and default authorizations behind every role, so ERP roles need conversion work, and often a partial redesign, before go-live.

Key takeaways

  • Some ERP transactions are gone or redirected; customer and supplier maintenance moves to BP.
  • Business partner access adds objects such as B_BUPA_RLT on top of the customer and supplier objects.
  • Fiori apps need catalogs, OData service authorizations and back-end authorizations.
  • SU24 defaults change with the release, so SU25 post-processing is required.
  • Choose technical conversion, redesign or partial redesign early; most projects end up with a partial redesign.

What changes in authorizations from SAP ERP to S/4HANA?

Change What it means for roles
Obsolete and replaced transactions Some ECC transactions no longer exist or lead to new ones; roles must contain the replacements
Business partner Customers and suppliers are maintained as business partners with BP, using objects such as B_BUPA_RLT and B_BUPA_GRP alongside the customer and supplier objects
Simplified data model Finance and logistics are simplified, for example with the universal journal, which changes some checks
SAP Fiori Apps need business catalogs, spaces and pages, OData service authorizations and back-end authorizations
New SU24 data SAP’s default authorization proposals change with the release, and roles built from them need updating
Development protection SAP Note 2309060 describes the move from SSCR object keys to S_DEVELOP protection for development access

Why does the business partner matter so much for security?

In ECC, someone who displayed customers with FD03 and someone who changed supplier bank details with XK02 used different transactions with different objects. In S/4HANA, both work through BP. If you give a user BP with broad business partner roles and activities, they may see or change far more than before, including bank data they never had access to.

Control business partner access with the business partner role and group objects, and keep the customer and supplier objects for company code and account group restrictions. Then update every SoD rule set function that used to list XK01, XK02, FD01 or FD02 so it covers BP and the matching Fiori apps.

How do Fiori apps change role design?

A transaction in a role is one menu entry plus its authorizations. A Fiori app needs three layers:

  1. Front-end access: a business catalog and the spaces and pages that show the tile on the launchpad.
  2. Service access: start authorization for the app’s OData service, checked with S_SERVICE.
  3. Back-end authorizations: the same business objects as the transaction, such as company code or plant checks.

Fiori content doesn’t map one to one to transactions, so a Fiori-first project usually needs new roles. The SAP Fiori apps reference library lists each app’s catalog, SAP business role and services, and for many apps which ECC transactions they replace.

What is SU25 and why do you need it?

SU24 holds SAP’s authorization proposals for each transaction, app and service. A new release brings new proposals. SU25 is the post-processing tool that compares SAP’s new defaults with your customized SU24 data and updates your roles. Two practical points:

  • Read SAP Note 440231 (SU25 FAQ) and Note 1539556 (SU24 FAQ, with a section on S/4HANA conversion) before the first run. Some options are hard to undo.
  • SU25 step 2d shows transactions SAP replaced with others. Table PRGN_CORR2 holds replacement data too, and some experts recommend checking it because step 2d doesn’t show every change.

Where do you find out what changed for your system?

Source What it gives you
Simplification Item Catalog Each functional change, such as the business partner, with related SAP Notes
SAP Readiness Check Which simplification items apply to your system
Fiori apps reference library Apps, catalogs, services and the transactions they replace
SU25 step 2d and PRGN_CORR2 Replaced transactions in the target release
SAP Note 1946054 Transaction comparison between S/4HANA Finance and ERP
Usage data from production Which transactions people actually use, so you only map what matters

No single source is complete for authorization purposes. Combine them, record what you checked, and confirm with traces in the converted test system.

Technical conversion, redesign or partial redesign?

Approach Strength Weakness
Technical conversion: keep roles, replace transactions, run SU25 Fast, little business effort Carries old excess access and SoD conflicts into S/4HANA
Redesign: build new task-based roles with Fiori and SoD rules from the start Clean result, closes audit findings Needs more time and process owner involvement
Partial redesign: convert most roles, redesign high-risk areas Balances effort and risk Needs clear rules for which areas get which treatment

Clean roles with maintained SU24 data favour conversion. Sprawling, manually built roles, open audit findings or a Fiori-first plan favour redesign. Decide early and write it into the project charter, because analysis, build and testing all depend on it.

How do you run the role work in a conversion project?

  1. Analyze: collect roles, assignments and usage; review Readiness Check results and simplification items.
  2. Map: for each used transaction, decide the replacement: same transaction, another transaction, a Fiori app or nothing.
  3. Build: clean SU24, run SU25, update or create roles in PFCG, add Fiori catalogs.
  4. Test: business users test their future roles with real process scripts; run SoD analysis on the new roles.
  5. Cut over: transport roles, assign users, remove project access and support the first weeks.

SAP’s conversion guide includes a step to prepare the conversion of authorizations and a separate step for Fiori enablement. Start both early, in parallel with technical preparation.

Frequently asked questions

Do ECC roles work in S/4HANA after a conversion?

They still exist, but users find missing transactions, invisible apps and authorization errors, and some roles may grant more access than intended. Roles need conversion work before go-live.

Which transaction replaces XK02 and FD02 in S/4HANA?

Supplier and customer maintenance moves to the business partner transaction BP and related Fiori apps, so roles and SoD rules must include BP.

What does SU25 do in an S/4HANA conversion?

SU25 compares SAP’s new authorization defaults with your customized SU24 data and helps update roles. Read SAP Notes 440231 and 1539556 before running it.

Do Fiori apps need extra authorizations?

Yes. A Fiori app needs a business catalog for the tile, S_SERVICE authorization for its OData service, and the usual back-end authorizations for the business data.

The bottom line

Moving from SAP ERP to S/4HANA changes transactions, the business partner, Fiori access and SU24 defaults all at once. Map what users really use, run SU25 carefully, build Fiori access in three layers and update your SoD rules for BP. For background, read what S/4HANA is and how SAP roles work.

Sources: SAP Note 440231: SU25 FAQ; SAP Note 1539556: SU24 FAQ; SAP Fiori apps reference library; SAP Learning: Authorization concept for SAP S/4HANA.

Go deeper with these books