The Fiori classification shift

SAP S/4HANA replaces the SAP GUI as the default user interface with the Fiori launchpad. Fiori is role-based, tile-driven, and presents only the apps a user is entitled to use. The shift is presented as a usability improvement; it has a licensing consequence that buyer-side teams underestimate. The Fiori tile assignment, the embedded-analytics access, and the BTP-extension entitlement all change the authorisation footprint of the average user. The classification consequence is that some users move up the classification ladder (more entitlement than they had in ECC), and some users move down (the GUI muscle-memory that justified Professional classification is no longer there). This article walks through the directional shifts, the measurement consequence, and the optimisation opportunity. It is one of the patterns underneath our S/4HANA migration compliance service.

The directional shift

The directional shift is not uniform. Three sub-populations move in three directions. Power users who used a wide range of transactions in ECC and now use a tighter, role-curated Fiori set typically reduce their authorisation footprint and qualify for a lower classification. Functional users who used a few transactions in ECC and now use a wider set of Fiori tiles plus embedded analytics may increase their footprint and require a higher classification. Casual users who occasionally used SAP GUI for a single task and are now persistent Fiori launchpad users may move from Employee to Professional simply because the launchpad pattern is more comprehensive than the prior transaction-specific pattern.

The aggregate directional effect varies by estate. Estates that re-engineer their role design at migration typically reduce total Professional-equivalent licensing by ten to eighteen per cent. Estates that lift-and-shift their ECC role design into S/4HANA see classification inflation of three to six per cent because the Fiori tiles assigned by the lifted role exceed what the user actually needs. The S/4HANA topic page covers the architectural frame.

What SAP measures

SAP's measurement of S/4HANA users continues to use the USMM mechanism and the classification rules. The classification rules are interpreted against the Fiori-era authorisation set. Specific transactions that previously triggered Professional classification (FBL3N, ME21N, VA01) still trigger it when reached through Fiori; the trigger is the authorisation, not the launching interface. The change is that the Fiori catalogue assigns broader authorisation by default than the equivalent ECC role would have done, and the broader authorisation triggers broader classification.

The measurement consequence is that Fiori-catalogue assignment becomes a classification decision. Assigning a wide catalogue to a user who needs a narrow subset inflates the classification. Assigning a tight catalogue mirrors the user's actual need and contains the classification. The role-mining article covers the targeted-catalogue methodology.

The embedded-analytics question

S/4HANA includes embedded analytics — CDS-view-driven dashboards, KPI tiles, smart-business apps — that present analytical content inside the operational launchpad. The classification question is whether embedded-analytics access constitutes a Professional-level entitlement. SAP's general position is that read-only analytical access to operational data does not by itself trigger Professional classification, but that interactive analytical access (drill-through to operational data, modification of analytical artefacts, publication of analytical content) does.

The drill-through trap

The most common trap is the drill-through pattern: an embedded-analytics tile that drills through to the underlying transaction, exposing the operational document. A user with the tile but without the operational authorisation cannot drill through. A user with the tile and with the operational authorisation drills through, and the drill-through transaction triggers the higher classification. Buyer-side teams that intend the analytics tile as read-only should restrict the drill-through authorisation to avoid the inflation.

The BTP dimension

S/4HANA users may have BTP entitlement for extension applications, side-by-side extensions, and integration applications. The BTP entitlement is licensed separately from the named-user licence and does not in itself trigger named-user classification inflation. However, where the BTP extension acts as a front-end to S/4HANA functionality, the back-end access through the extension does trigger classification. The position is that the extension does not licence the back-end; the back-end licences the back-end. The BTP credits article covers the BTP licensing dimension.

The role-redesign opportunity

The migration window is the natural moment to redesign roles. The S/4HANA role design starts from the Fiori catalogue rather than from the ECC transaction set, and the catalogue selection is a fresh decision. The recommended pattern is to build the role catalogue from the user's actual workflow rather than from the historical authorisation set. The workflow analysis is conducted with the business unit; the historical authorisation set is the safety-net check that ensures no operational function is lost.

The outcome of the role redesign is twofold. First, the classification distribution shifts down: more users sit in Employee or Self-Service classifications, fewer in Professional. Second, the audit-defence position improves: the role design is current, deliberate, and defensible against the auditor's challenge that the role is more permissive than the user needs.

The measurement sequence

The first S/4HANA USMM run after migration is the new baseline. The pre-migration ECC measurement is no longer comparable: the user population is the same but the authorisation footprint has changed, and the classification distribution has changed with it. The buyer-side preparation includes a fresh classification review against the post-migration authorisation, a fresh reconciliation against the HR population, and a fresh dormancy review against the post-migration logon data. The USMM run preparation article covers the mechanics.

The white-paper reference

Our S/4HANA migration licence-risks white paper sets out the full Fiori-shift methodology and the role-redesign sequence. The pharma migration case file documents the outcome on a 15,000-user estate.

Where to start

Start with the Fiori catalogue inventory and the workflow analysis for the top three user roles by population. The exercise is two-to-three weeks and produces both the optimisation thesis and the role-redesign blueprint. Build the broader programme from the proof point.