With key user adaptation, you can change the user interface of SAP Fiori apps directly in the Fiori launchpad — intuitively and without having to write new code. The changes are upgrade-safe adaptations to SAP Fiori apps. Key users can open the UI Adaptation mode for a Fiori app directly from their user menu in the Fiori launchpad (menu entry Adapt UI).
A key user is a business expert who is authorized to make changes on behalf of other users — for example a team member who is interested in technology. The goal of key user extensibility is to empower business users to be able to adapt their working environment to suit their needs, without having to rely on system administrators.
What can key users change with key user adaptation?
Key users can perform the following changes in Fiori apps based on SAP Fiori elements:
Hide/show the information that shall be visible in the object page headerHide/show tabs, sections, tables, or action buttons on the object pageDefine the fields visible in forms on the object pageSet the configuration for tables (select all, selection mode, thresholds, view settings, export, etc.)Set the configuration for the filter bar (clear button, usage of the semantic date range control)Set the configuration for the complete list report / object page (variant management, initial load)Change Text Arrangement (ID only, Text first, Text last, Text only)Change Labels (global label changes)Rename (only for a dedicated field – applies only locally to a form field)Define the fields visible in the mass edit dialog. In the key user adaptation mode, all fields except static read-only fields are available.And more
The scope was continuously enhanced. The bold items above are extremely powerful new features available since S/4HANA Cloud Public Edition 2508 / S/4HANA Cloud Private Edition 2025 / On-Premise 2025. They are described in detail in the following sections.
New feature: configuration for tables
The Configuration functionality is available in key user adaptation mode when the context menu entry Configuration is selected on a table, on the filter bar, or on page level. The context menu on a table contains — for example in Fiori elements V4 — the following entries:
Among other things, the following settings can be configured here:
Enable Table Export — configures whether the Export button is displayed in the table.Frozen Column Count — configures the count of columns that are always visible when scrolling horizontally.Personalization — configures whether the table personalization settings are enabled. To configure the listed settings individually, choose Own Settings.Row Count — configures the number of rows to be displayed in the table.Width Including Column Header — configures whether the column header label is considered when calculating the column width.Enable Select All — configures whether the Select All option is displayed in the table.Selection Limit — configures the maximum limit of the number of rows that can be selected at once (e.g., by using Select All).Threshold — determines the maximum number of entries loaded when the application is started. Scroll Threshold determines the maximum number loaded during scrolling if new entries need to be fetched. Increasing these settings will lead to an increased initial load time but deliver a smoother scroll experience.
Note: Not all settings listed above are available for all table types and page types. Furthermore, there are differences between Fiori elements V2 and Fiori elements V4 (Fiori elements V2 offers fewer settings).
Example – List Report Grid Table in Fiori elements V4:
New feature: configuration for the filter bar
The Configuration context menu entry on the filter bar opens settings for the filter bar. Among other things, the following settings can be configured here:
Display Clear Button — configures whether the Clear button is displayed in the filter bar.Enable Semantic Date Range menu options — configures that single date range filters offer semantic operators (like “Today”, “This Month”, “Last Year”).
Example – List Report Filter Bar in Fiori elements V4:
New feature: configuration for the complete list report / object page
The Configuration context menu entry at page level opens settings for the entire List Report or Object Page. Among other things, the following settings can be configured here:
Variant Management (Table Variant Management) — configures how variant management is used on the List Report page or in tables on the Object Page.Initial Load — configures how data is loaded initially when the app is opened.
Example – List Report in Fiori elements V4:
New feature: change text arrangement
The Change Text Arrangement functionality is available in key user adaptation mode when the context menu entry Change Text Arrangement is selected on a table, on the filter bar, or on a form.
This powerful new functionality allows changing centrally the text arrangement for all relevant fields in a Fiori app. A key user can decide for each field whether it shall be shown as:
Option
Example (Company Code “0001” / “SAP AG”)
ID only
0001
Text only
SAP AG
Text first
SAP AG (0001)
Text last
0001 (SAP AG)
Note: These changes are independent of specific controls. You change the text arrangement for the underlying OData property. If a specific field or control does not use the text arrangement from the OData property, the changes will not be applied to that control.
New feature: change labels
The Change Labels functionality is available in key user adaptation mode when the context menu entry Change Labels is selected on a table, on the filter bar, or on a form.
This allows changing the labels centrally for all relevant fields in a Fiori app: if an identical label is available in the filter bar, in tables, forms, and charts of a Fiori application, then all places are changed consistently. This is the key difference from the existing Rename feature, which only applies locally to a form field.
Example: You can consistently change the text “Material” to “Product” across your entire Fiori app.
Note: These changes are independent of specific controls. You change the label for the underlying OData property. If a specific field or control does not use the text from the OData property, the changes will not be applied to that control.
Need more complex changes? Seamless Transition from Key User to Developer Extensibility.
If you need to make more complex changes — for example, adding fragments to visualize data as a chart, changing a responsive table to a grid table, or making the app available to different business roles, user groups, organizational units, and countries — you can extend an application by creating an SAPUI5 Adaptation Project (developer adaptation).
When creating an SAPUI5 Adaptation Project, you can select the brand-new option Import Key User Changes (available since S/4HANA Cloud Public Edition 2602; not yet available for S/4HANA Private Cloud / On-Premise) to import all key user changes made so far. This means key user changes will not be lost — they become part of the new SAPUI5 Adaptation Project.
For an introduction to Adaptation Projects, see Work with SAPUI5 Adaptation Projects to Make Changes and Extend the Source Code of an Application Variant of an SAP Fiori Application in SAP S/4HANA Cloud Public Edition.
For more detailed information, see Extending SAP Fiori Applications.
Prerequisites
Public Cloud:
The IAM app F6184_TRAN provides the relevant authorizations. It is included in the business catalogs SAP_CORE_BC_EXT_FLX_CUS_PC and SAP_CORE_BC_EXT_FLX_PC (see Adapting SAP Fiori UIs at Runtime – Key User Adaptation).
Private Cloud / On-Premise:
Your administrator assigned you to the authorization role SAP_UI_FLEX_KEY_USER (see Enabling Key User Adaptation).
General requirements:
You run your SAPUI5 app on a desktop computer or laptop.Your app is enabled for key user adaptation.A minimum screen size of 800×600 is required for key user adaptation. Anything smaller can affect the toolbar elements, causing them to overlap.
Tips for Key User Adaptation for Fiori Apps in SAP S/4HANA
Where do I make Key User changes?
Key users typically make changes in the Development environment.
How do I transport Key User changes?
Active changes must be published to make them ready for transport.To publish your changes for transport, you must be assigned a transport request by your technical team.Your technical team manages the transports through to your Production environment.
Key takeaways
Key User Adaptation lets you make common changes to SAP Fiori apps directly in the Fiori Launchpad — no developer knowledge required.Key User Adaptation is now extremely powerful with new options for:Configuring important UI elements (tables, filter bar, complete list report / object page)Changing the text arrangement of fieldsChanging labels globally across an entire Fiori appChanges are made in the Development environment and published for transport.Published changes can be transported to other environments by your technical team.Key User Adaptation changes can be imported when creating an SAPUI5 Adaptation Project for more complex changes (S/4HANA Public Cloud 2602+). This allows a seamless transition from key user to developer extensibility.
Where can I learn more about Key User Adaptation for Fiori Apps in SAP S/4HANA?
SAP Help – Key User Adaptation (S/4HANA Cloud Public Edition): Adapting SAP Fiori UIs at Runtime – Key User AdaptationSAP Help – Key User Adaptation (S/4HANA Cloud Private Edition and On-Premise): Adapting SAP Fiori UIs at Runtime – Key User AdaptationSAP Learning – Tutorials: Key User Adaptation for SAPUI5 ApplicationsSAP Help – SAP Fiori elements V4: Extending Delivered Apps With Key User AdaptationSAP Help – SAP Fiori elements V2: Adapting the UI
With key user adaptation, you can change the user interface of SAP Fiori apps directly in the Fiori launchpad — intuitively and without having to write new code. The changes are upgrade-safe adaptations to SAP Fiori apps. Key users can open the UI Adaptation mode for a Fiori app directly from their user menu in the Fiori launchpad (menu entry Adapt UI).A key user is a business expert who is authorized to make changes on behalf of other users — for example a team member who is interested in technology. The goal of key user extensibility is to empower business users to be able to adapt their working environment to suit their needs, without having to rely on system administrators. What can key users change with key user adaptation?Key users can perform the following changes in Fiori apps based on SAP Fiori elements:Hide/show the information that shall be visible in the object page headerHide/show tabs, sections, tables, or action buttons on the object pageDefine the fields visible in forms on the object pageSet the configuration for tables (select all, selection mode, thresholds, view settings, export, etc.)Set the configuration for the filter bar (clear button, usage of the semantic date range control)Set the configuration for the complete list report / object page (variant management, initial load)Change Text Arrangement (ID only, Text first, Text last, Text only)Change Labels (global label changes)Rename (only for a dedicated field – applies only locally to a form field)Define the fields visible in the mass edit dialog. In the key user adaptation mode, all fields except static read-only fields are available.And moreThe scope was continuously enhanced. The bold items above are extremely powerful new features available since S/4HANA Cloud Public Edition 2508 / S/4HANA Cloud Private Edition 2025 / On-Premise 2025. They are described in detail in the following sections. New feature: configuration for tablesThe Configuration functionality is available in key user adaptation mode when the context menu entry Configuration is selected on a table, on the filter bar, or on page level. The context menu on a table contains — for example in Fiori elements V4 — the following entries: Among other things, the following settings can be configured here:Enable Table Export — configures whether the Export button is displayed in the table.Frozen Column Count — configures the count of columns that are always visible when scrolling horizontally.Personalization — configures whether the table personalization settings are enabled. To configure the listed settings individually, choose Own Settings.Row Count — configures the number of rows to be displayed in the table.Width Including Column Header — configures whether the column header label is considered when calculating the column width.Enable Select All — configures whether the Select All option is displayed in the table.Selection Limit — configures the maximum limit of the number of rows that can be selected at once (e.g., by using Select All).Threshold — determines the maximum number of entries loaded when the application is started. Scroll Threshold determines the maximum number loaded during scrolling if new entries need to be fetched. Increasing these settings will lead to an increased initial load time but deliver a smoother scroll experience.Note: Not all settings listed above are available for all table types and page types. Furthermore, there are differences between Fiori elements V2 and Fiori elements V4 (Fiori elements V2 offers fewer settings).Example – List Report Grid Table in Fiori elements V4: New feature: configuration for the filter barThe Configuration context menu entry on the filter bar opens settings for the filter bar. Among other things, the following settings can be configured here:Display Clear Button — configures whether the Clear button is displayed in the filter bar.Enable Semantic Date Range menu options — configures that single date range filters offer semantic operators (like “Today”, “This Month”, “Last Year”).Example – List Report Filter Bar in Fiori elements V4: New feature: configuration for the complete list report / object pageThe Configuration context menu entry at page level opens settings for the entire List Report or Object Page. Among other things, the following settings can be configured here:Variant Management (Table Variant Management) — configures how variant management is used on the List Report page or in tables on the Object Page.Initial Load — configures how data is loaded initially when the app is opened.Example – List Report in Fiori elements V4: New feature: change text arrangementThe Change Text Arrangement functionality is available in key user adaptation mode when the context menu entry Change Text Arrangement is selected on a table, on the filter bar, or on a form.This powerful new functionality allows changing centrally the text arrangement for all relevant fields in a Fiori app. A key user can decide for each field whether it shall be shown as:OptionExample (Company Code “0001” / “SAP AG”)ID only0001Text onlySAP AGText firstSAP AG (0001)Text last0001 (SAP AG)Note: These changes are independent of specific controls. You change the text arrangement for the underlying OData property. If a specific field or control does not use the text arrangement from the OData property, the changes will not be applied to that control. New feature: change labelsThe Change Labels functionality is available in key user adaptation mode when the context menu entry Change Labels is selected on a table, on the filter bar, or on a form.This allows changing the labels centrally for all relevant fields in a Fiori app: if an identical label is available in the filter bar, in tables, forms, and charts of a Fiori application, then all places are changed consistently. This is the key difference from the existing Rename feature, which only applies locally to a form field.Example: You can consistently change the text “Material” to “Product” across your entire Fiori app.Note: These changes are independent of specific controls. You change the label for the underlying OData property. If a specific field or control does not use the text from the OData property, the changes will not be applied to that control. Need more complex changes? Seamless Transition from Key User to Developer Extensibility.If you need to make more complex changes — for example, adding fragments to visualize data as a chart, changing a responsive table to a grid table, or making the app available to different business roles, user groups, organizational units, and countries — you can extend an application by creating an SAPUI5 Adaptation Project (developer adaptation).When creating an SAPUI5 Adaptation Project, you can select the brand-new option Import Key User Changes (available since S/4HANA Cloud Public Edition 2602; not yet available for S/4HANA Private Cloud / On-Premise) to import all key user changes made so far. This means key user changes will not be lost — they become part of the new SAPUI5 Adaptation Project. For an introduction to Adaptation Projects, see Work with SAPUI5 Adaptation Projects to Make Changes and Extend the Source Code of an Application Variant of an SAP Fiori Application in SAP S/4HANA Cloud Public Edition.For more detailed information, see Extending SAP Fiori Applications. PrerequisitesPublic Cloud:The IAM app F6184_TRAN provides the relevant authorizations. It is included in the business catalogs SAP_CORE_BC_EXT_FLX_CUS_PC and SAP_CORE_BC_EXT_FLX_PC (see Adapting SAP Fiori UIs at Runtime – Key User Adaptation).Private Cloud / On-Premise:Your administrator assigned you to the authorization role SAP_UI_FLEX_KEY_USER (see Enabling Key User Adaptation).General requirements:You run your SAPUI5 app on a desktop computer or laptop.Your app is enabled for key user adaptation.A minimum screen size of 800×600 is required for key user adaptation. Anything smaller can affect the toolbar elements, causing them to overlap. Tips for Key User Adaptation for Fiori Apps in SAP S/4HANAWhere do I make Key User changes?Key users typically make changes in the Development environment.How do I transport Key User changes?Active changes must be published to make them ready for transport.To publish your changes for transport, you must be assigned a transport request by your technical team.Your technical team manages the transports through to your Production environment. Key takeawaysKey User Adaptation lets you make common changes to SAP Fiori apps directly in the Fiori Launchpad — no developer knowledge required.Key User Adaptation is now extremely powerful with new options for:Configuring important UI elements (tables, filter bar, complete list report / object page)Changing the text arrangement of fieldsChanging labels globally across an entire Fiori appChanges are made in the Development environment and published for transport.Published changes can be transported to other environments by your technical team.Key User Adaptation changes can be imported when creating an SAPUI5 Adaptation Project for more complex changes (S/4HANA Public Cloud 2602+). This allows a seamless transition from key user to developer extensibility. Where can I learn more about Key User Adaptation for Fiori Apps in SAP S/4HANA?SAP Help – Key User Adaptation (S/4HANA Cloud Public Edition): Adapting SAP Fiori UIs at Runtime – Key User AdaptationSAP Help – Key User Adaptation (S/4HANA Cloud Private Edition and On-Premise): Adapting SAP Fiori UIs at Runtime – Key User AdaptationSAP Learning – Tutorials: Key User Adaptation for SAPUI5 ApplicationsSAP Help – SAP Fiori elements V4: Extending Delivered Apps With Key User AdaptationSAP Help – SAP Fiori elements V2: Adapting the UI Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
