Skip to Content
Technical Articles
Author's profile photo Jocelyn Dart

SAP Fiori for SAP S/4HANA – Best Practices for Structuring Spaces and Pages

*** Update 11th March 2021: Further recommendations for spaces and pages can be found in

With SAP S/4HANA 2020 comes the new Spaces and Pages capability. Compared to the older layout capability known as (Business) Groups, Spaces and Pages provides a more robust and more scalable layout of content on the launchpad for business users.  Spaces and Pages provide a better default user experience and starting point for business users to encourage high user adoption and optimal productivity.

For project teams Spaces and Pages bring an initial dilemma of how to make the most of these new capabilities. In this blog post you will find best practice recommendations based on how SAP itself is providing Spaces and Pages content across the more than 500 business roles delivered with SAP S/4HANA. You can use these recommendations when creating your own custom Spaces and Pages for your own custom business roles.

TL;DR The Spaces and Pages content SAP delivers with SAP S/4HANA 2020 follows clear best practice guidelines that you can leverage when creating your own custom Spaces and Pages.

When it comes to user adoption of SAP Fiori, sometimes half the battle as a business user is just making sense of your day:

  • How do I reconcile what I am trying to do with what’s available to do it on the system?
  • Where do I find my most frequent apps – the ones I need multiple times per day?
  • How do I get to the periodic activities I need to complete each week or each month without having them cluttering up my day-to-day work life?
  • When I am assigned to multiple business roles, how do I shift easily from one work area to another and back again?

Enter the Spaces and Pages capability for the SAP Fiori launchpad!

You may already be aware that with SAP Fiori Front-end Server 2020 for SAP S/4HANA brings a new, more robust, more controlled, and more scalable way to organize tiles on the launchpad called Spaces and Pages as explained in Set Up SAP Fiori Launchpad Spaces with SAP Fiori Front-End Server 2020 for S/4HANA.


Relationship of Spaces and Pages to Business Roles and Business Catalogs

Spaces and pages are a major improvement on the earlier (Business) Groups capability for business users, particularly those assigned to multiple business roles.  Bringing:

  • Condensed (simpler/cleaner) tabs
    • With each space shown on a new tab
    • And menu tabs collapsing pages within spaces, when a space holds multiple pages
  • Guaranteed section/tile order
    • Delivered as you designed it
  • Fewer authorization errors
    • Since the launchpad content administrator can only assign tiles if the catalogs is assigned to the security role already

Spaces and pages are a major improvement on the earlier (Business) Groups capability, for administrators.  Groups were assigned directly to the business role, requiring rework in the matching security authorization role for even simple layout changes. With spaces, only the space is assigned to the business role, the sub-elements of page and section can be reorganized and adjusted to meet your layout needs without any rework in the matching security authorization.

Important: Business Groups are still supported and will continue to be supported for some time to come.  If you are currently using Business Groups, you can move gracefully from Business Groups to Spaces and Pages one business role at a time. You can even allow users to make the decision on when to move for themselves, via personalization.

SAP S/4HANA 2020 also delivers Spaces and Pages content for many of the more than 500 Business Roles delivered with SAP S/4HANA 2020. You can use this content as a starting point for creating your own spaces and pages as explained in the SAP Fiori Launchpad guide section SAP-delivered Spaces and Pages.

For example: Here you can see the spaces and pages approach for a business user with General Ledger, Billing, and Internal Sales roles. Each work area has its own tab representing the work of that role, with menu dropdowns for different pages representing different sub work areas.


Spaces and Pages example showing Spaces as menu tabs, with Pages listed in the menus

Important: If you are on SAP S/4HANA 1809 or 1909 and upgrade your SAP Fiori Frontend Server from 6.0 to 2020, you can also use Spaces and Pages capabilities for all your launchpad content. Be aware that you will not get the SAP-delivered Spaces and Pages content until you upgrade to SAP S/4HANA 2020.  Your upgrade options are explained in How and Why to Upgrade SAP Fiori for your SAP S/4HANA solution.

Spaces and Pages are managed via the new SAP Fiori apps F4834 Manage Launchpad Spaces and F4512 Manage Launchpad Pages which are part of the launchpad administrator role (technical id SAP_FLP_ADMIN).  These new apps provide a WYSIWYG approach to assigning apps and classic UIs in your business roles to your launchpad layout.

Which leaves just one main dilemma for you as a launchpad content administrator:

  • How to make best use of Spaces and Pages across all our business roles to maximize user adoption?

To help you, in this blog post you will find some best practices that explain how SAP delivers the Spaces and Pages content. You can use these to create your own custom Spaces and Pages, and to leverage the out of the box Spaces and Pages content SAP delivers.

The best practices include:

  • Guiding principles for launchpad layout
  • Recommendations for page size, number, and sequence of elements
  • Naming guidelines for Spaces, Pages, and Sections

So you can make sure your security team are on board with these changes, you will also find a short introduction to:

  • Spaces and Pages and how they relate to security authorizations

And finally:

  • Outlook on upcoming capabilities for Spaces and Pages in 2021

Guiding principles for launchpad layout

You should consider the following guiding principles, when structuring launchpad pages:

  • Aim for lean pages
  • Apply an insight-to-action approach
  • Reflect “day in the life” working patterns of your users
  • Reuse the same app on multiple pages where needed to minimize navigation
  • Aim for a “Fiori first” approach where practicable
  • Keep less relevant apps and classic UIs off the pages
  • Avoid duplicating launchpad features
  • Aim to be coherent and consistent across all your business roles

These principles are aimed at optimizing usability and user adoption, by ensuring the pages are easy to understand by business users and reflect their natural working patterns. These principles also focus attention on the best new business value of SAP S/4HANA to help users transition from classic user interfaces such as SAP GUI transactions.

You can find a summary of each of these principles below.

Aim for lean pages

Aim for lean pages. Avoid using pages as a container for all available apps and classic User Interfaces that are part of the work area. Instead, focus on the most essential apps for the business role associated with this work area.

What do we mean by work area?

If you think about most organizations, the name of your business role can be different depending on organizational culture, history, and politics even when the work is much the same.

A person who does Accounts Payable work may be assigned to a business role called: Accounts Payable Clerk, Accounts Payable Officer, Finance Office Grade 1, AP Manager, or Senior AP Officer.  These organizational role names can be quite confusing for new hires to understand as they come into your organization. They can also be confusing for current employees when role names change due to changes in organizational strategy, structure or politics.

However, the term “Accounts Payable” and what type of work it represents remains largely the same across most organizations and industries.  So, by calling the Page by the work area “Accounts Payable”, regardless of what the business role is (currently) called, you make it easy for everyone to understand what is on this Page.

By keeping the page focussed on the most important and most frequent activities of an Accounts Payable person, it becomes easy for someone who does that work to focus on the essentials of what they need to do.

Example: A user who has the role General Ledger Accountant is assigned the space General Ledger.


A user with business role General Ledger Accountant is assigned the space General Ledger and its associated pages

Apply an Insight to action approach

Encourage “think before do”. Help users to first identify and prioritize what they need to work on via insights, and then guide the navigation to the actions. Aim to offer insight apps on the page – apps that provide an Overview of, or let them Monitor or Manage, the business entities they are responsible for.  From within these insight apps, they should then be able to drill down to the necessary tasks, i.e. “actions”, that they need to perform on these business entities, once they have decided what needs to be changed to meet organizational needs and priorities.

Example: A user who is assigned the General Ledger space, can clearly see their insight apps.


A user can clearly see their insight apps in a section named Insights on one of their pages

Reflect “day in the life” working patterns of your users

Identify working patterns of users when they perform their daily tasks using the offered apps. What are the most important apps for the user? How often will they use these apps?  Is there a sequence in which they will use the apps? Structure the pages according to these user patterns, such as:

  • Quick Access – your most frequent apps should appear at the top of the page
  • Insights apps that help you prioritize your work for the day should appear near the top of the page
  • Your regular daily processing work should appear in the middle of the page
  • Periodic Activities, such as occasional apps that you need a week, once a month, or once a fiscal period, should appear at the bottom of the page.


You can see the General Ledger main page – called Overview – focuses on Quick Starts and Insights.


In the General Ledger space, the first page Overview includes sections for Quick Access and Insights apps

For the General Ledger work area, Periodic Activities are separated to their own page and organized to fit with working patterns, e.g. Closing Preparation before Close.


In the General Ledger space the page Periodic Activities holds the apps needed for end of period activities in sections Recurring Processes, Closing Preparation, and Financial Close

Reuse the same app on multiple pages where needed to minimize navigation

Single apps can be included more than once on different pages, where needed. The aim is to enable users to complete the tasks relevant for the same work context on one page without having to navigate to other pages.

Important: Do NOT include apps from other work contexts, as this would lead to cluttered pages and breaks the principle “aim for lean pages”.


Many business roles may need to use My Inbox to approve or review rejected changes.  It is fine to include the My Inbox app on the first page of each of these business roles.

Tip: You might want to consider a scenario-specific variant of the My Inbox app to focus attention further, by filtering the inbox content to only those tasks related to the current business role, as explained in My Inbox – Part 1 – Activation.

Aim for a “Fiori first” approach where practicable

Preference SAP Fiori apps – SAP-delivered or custom – over classic User Interfaces (classic UIs) on the home page. Classic UIs include:

  • ABAP GUI transactions,
  • Web Dynpro ABAP applications, and
  • Web Client UIs

If there are classic UIs covering a related or extended functional scope to a SAP Fiori app, only display the app on the home page and offer navigation from this SAP Fiori app to the classic UI.

This intention of this guideline is to:

  • Encourage users to try out new apps
  • Avoid cluttering the home page with actions/tasks that are typically accessed via navigation from a SAP Fiori app where the user will first prioritize their work
  • Direct attention to the new business value of SAP S/4HANA, such as embedded analytics, and streamlined processes such as Lean Services

Part of the reasoning behind this guideline is that there are many SAP Fiori apps that bring embedded analytics that help users prioritize their work, while classic UIs are often included in business roles for completing specific tasks/actions.


If you would like to understand more about insight to action navigation, you can see this in action in this short video Insight to Action with SAP Fiori 3 with SAP S/4HANA.

Keep less relevant apps and classic UIs off the pages

Pages should not be containers for all possible apps and classic UIs.  Less relevant apps and classic UIs should be kept one step removed, to avoid clutter on the pages.  Typically, this includes apps that can be via navigation from an insight app, such as apps that you use to perform tasks(actions) on business entities.  It also includes apps and classic UIs that are only used rarely (less than once per month).  These less relevant apps and UIs can be accessed from:

  • Generic navigation links from other SAP Fiori apps, such as list of links dialogs and Related Apps buttons
  • Search
  • Home Navigation button
  • App Finder
  • SAP Menu
  • Easy Access Menu

Tip: Remember that if particular users want to add these apps to their pages, they can use the Edit Page option or the App Finder to add them.

You find the Edit Current Page feature in the User Actions menu.


Edit Current Page feature is accessed via the User Actions menu

In the Edit Current Page option users can add tiles, remove tiles (using the x icon in the corner of the tile) add their own sections, hide, show, or reset sections that are assigned to them.


Edit Current Page editing screen where users can add tiles, add sections, hide, show, or reset sections

Avoid duplicating launchpad features

Avoid creating tiles that duplicate launchpad features, such as setting default values, and searching for a single business object by id.

Consider that your users can already access SAP Fiori launchpad features.  These are a native part of the user experience, including:

  • Search
  • Notifications
  • Settings – such as Theme, set Default Values
  • Personalization – such as Edit Page (for Groups) and Edit Current Page (for Spaces and Pages)
  • App Finder
  • SAP Menu
  • Easy Access Menu
  • Home button navigation


Avoid creating a “Display <business object>” tile that launches a classic UI, such as SAP GUI transaction, where users manually enter a specific id before displaying the details.  This approach means that if they want to then move to any other app/UI with the same id, they then have some effort to copy the id, find the new app/UI and paste the id.   Instead encourage users to use the Search in the launchpad shell bar to find the object by id, partial id or wildcard.  They get a quick summary of the business object to confirm they have found the correct id, and can then launch from the to any of their relevant apps or classic UIs from Search results.

Be coherent and consistent across multiple spaces

When you are assigned to multiple roles, spaces, and pages, you need coherence and consistency to ease moving from one role, space, or page to another. A coherent and consistent approach improves productivity and avoids dissonance that can interrupt your train of thought.


Have a main page with quick access and insight apps for more complex roles that has the same name across all roles, e.g. “Overview”.  Users moving from one business role to another will learn to reach for the Overview page to get to their most frequently needed apps.

Recommendations for page size, number and sequence of elements

A Space can have one or multiple pages

A space can have one page or multiple pages depending on the complexity of the work area.

Only use multiple pages where the work area is sufficiently complex to justify multiple pages, i.e. where the work area has multiple sub-areas.

Avoid splitting the work area into many sub-areas: 2 to 5 sub-areas should be sufficient for most work areas.

When using only one page per space, the page should give an overview of the functional scope of the complete space.

When using multiple pages per space:

  • The 1st page should be an Overview page, containing the most important or most used apps as “favorites” from other pages
  • Additional pages should be separate pages either:
    • Defined for different sub-areas, e.g. Lean Services, Advanced Services
    • Defined for different work processes, e.g. one page for daily tasks and one page for tasks performed less frequently such as reporting activities.


General Ledger space with separate pages for work processes Periodic Activities and sub-work area Tax Declaration.


General Ledger has pages for sub work areas such as Tax Declaration, and for special processes such as Periodic Activities

A Page should have 2 – 5 sections 

The sequence of sections on a page should reflect the user’s working patterns, with more frequently used sections placed higher on the page:

  • High usage sections such as Quick Access and Insights should be first
  • Less used sections such as Periodic Activities should be last
  • Do not use sections to cluster apps according to app types or any other technical categories (transactional vs. analytical apps, or transactional apps vs. scheduling apps).


A Sales Commission and Incentives page for a Billing role with 3 sections displayed in order:

  • Commission and Incentive Processing – the go-to apps of this page
  • Insights – used for planning, prioritizing, and monitoring
  • Periodic Activities – for fiscal period activities


Sales Commission and Incentives page with 3 sections for Commission and Incentive Processing, Insights and Periodic Activities

A Section should have 3 – 8 apps 

The sequence of apps in one section should reflect:

  • Most used or more important apps should be placed before less used ones
  • Align the sequence of apps within a section to the process flow, where applicable

Guidelines for Space, Page, and Section Titles


The Space title appears on the tab, the Page title appears at the top of the Page, the Section title appears above the section

General Principles for Titles

The titles on homepages should help users when searching. They should therefore be based on the following principles:

Titles should be intuitive (easy to grasp content)

Users expect to find their own terms on the pages.

Use specific business terms as titles and avoid generic SAP terms.

Avoid abbreviations that assume knowledge or expertise.

Avoid special characters such as “&/#@_” that may be misinterpreted or misunderstood.

Use plurals rather than singular if the work is across multiple entities.


  • “Project Billing” is a better title than “Project Billing Management”
  • “Bill of Material” is a better title than “BOM”
  • “Journal Entries” is a better title than “Journal Entry”

Titles should be consistent with the titles on other pages (categories should match)

Users search for patterns. Structuring homepages along similar and consistent categories across homepages helps users to recognize these patterns.

For example: If you have several spaces that have multiple pages, the first page should be an easily recognizable name, e.g. “Overview”, and contain the most important favourite apps of the other pages in the same space.  When users move from one role to another they will quickly learn that the Overview page gets them to the most often needed apps for each role.

Titles should reflect tasks

Users enter the homepage to find apps in order to fulfill their tasks. Titles on homepages should therefore reflect tasks/actions.


  • “Capacity Planning” is a better section title than “Capacity”.

Avoid using titles that reflect products or solutions.


  • “Long-Term Planning” is a better section title than “Predictive Material and Resource Planning”.

Titles must differ

Within a space the title of space, page and sections must be different. Do not use the same title for these elements within a space.

Do not use the same title for both the space and the page – as the page titles are shown below the space title in the menu tab.


In the General Ledger space it would be confusing to have a page title General Ledger listed in the menu tab below the space title General Ledger. All of the page titles should be distinct from each other and from the space title. This example shows a better approach where the first page is Overview and all other pages have a clear and distinct purpose.


All the pages of the General Ledger space have unique titles within that space

Do not use the same title for both a page and a section on the page – as the Page title will be repeated at the top of the page.


The “Overview” page for the General Ledger spaces shows the page title at the top of the page followed by the first section title “Quick Starts”.


Section titles such as Quick Access differ from the page title Overview

Guidelines for Space Titles

The administrator is the most important target group at customer site viewing the spaces that are delivered as templates. For them, not only the space title is relevant, but also the space description and the space ID.

For the on-premise spaces, the guideline is that the space title, space description and space ID have to match.

Do not use the business role name as space title, or as part of the space description or in abbreviated form in the space ID.

Differentiate between the different variants of a space by including the variant name in the title. Place the work area name before the variant name. Separate the work area name from the variant name with a hyphen in the format <Work Area Name> – <Variant Name>


“Production Planning – Lean Manufacturing” is a better title than “Lean Manufacturing Planning” and is also a better title than  “Production Planning for Lean Manufacturing”.

Where there are commonly used spaces across roles, aim to use the same name. This helps the administrator assign the correct roles.


“Master Data – Product Compliance” and “Master Data – Business Partners” are better than “Product Compliance Data” and “Business Partner Masters”.

Guidelines for Page Titles

Use a work context term summarizing the tasks that can be performed on the page.

Do not repeat the space title as the page title.

  • For spaces with one page, either use Overview as page title or a work-context related term
  • For spaces with multiples pages,

Guidelines for Section Titles

Use a term summarizing the tasks that can be performed in the section. Do not use Overview as section title.

Do not repeat the space or page title.

Where there are similar sections in different roles use a fixed name that can gives consistency when moving from one business role to another.


  • Quick Access – for the most important apps of a space
  • Insights – for the most important analytical apps that aid planning and prioritization of day to day work
  • Periodic activities – for tasks that are done periodically, e.g. once a week, once a month, once a year, once per fiscal period.

Spaces and pages versus authorizations

Spaces are assigned to roles in SAP GUI transaction PFCG.  This means the only touchpoint between authorizations and layout is to the space.  You are free to organize the content on your layout however you wish within the Space.

The SAP Fiori apps F4834 Manage Launchpad Spaces and F4512 Manage Launchpad Pages only permit apps and UIs that have already been assigned to the related security authorization role to be added to the layout.

In addition, business users can only access apps they are authorized to launch.

From a security administrator your primary considerations are:

  • Make sure the correct Space is assigned to the role
  • Make sure the appropriate business catalogs are assigned to the role
  • When apps/UIs are added or removed from the role, advise the content administrator so they can adjust the layout


More features are coming with Spaces and Pages in 2021. You can see these listed in the SAP Fiori Road Map.

For example:

  • Links in Spaces/Pages – planned for Q1 2021
  • Enhanced personalization capabilities
    • Sort order of spaces – planned for Q2 2021
  • New tile sizes for Spaces/Pages – planned for Q2 2021

Becoming a SAP Fiori for SAP S/4HANA guru

You’ll find much more on the community topic page for SAP Fiori for SAP S/4HANA

Other helpful links in the SAP Community:

Brought to you by the SAP S/4HANA Customer Care and RIG.



Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Brendan Farthing
      Brendan Farthing

      Hi Jocelyn,

      Very nice blog.

      I have two questions.

      Is FES 2020 only available with S/4HANA and not standalone?

      Will the concept of Spaces and Pages flow over to SAP Cloud, either in the Portal>Fiori Launchpad sites or in standalone Launchpad?





      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Brendan, Yes FES 2020 is only available with SAP S/4HANA. It can be run in embedded or standalone mode (i.e. in front of an SAP S/4HANA system). See the blog from Carola Steinmaier

      Yes the concept of Spaces and Pages will be supported in SAP Cloud Platform launchpad service (with or without Work Zone)  - currently planned for Q2 2021. See the roadmap for SAP Cloud Platform Portal at


      Author's profile photo Christian Köhler
      Christian Köhler

      Hi Jocelyn Dart,


      in additon to your answer from 2020: Is the spaces and pages concept only in embedded scenario possible?

      We are now having a hub FES 2021 for S/4HANA with SP02. It is connected to one HCM business suite system, so normal on premise, of course non S/4HANA. In the MAINT_SERVICE transaction I can see all the /UI2/FMDM*-Services. But the processing mode is always "Co-deployed only". Is this relevant in this scenario or to ask directly: Should/can I change it to "Routing-based"?

      thanks in advance


      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Christian

      Yes spaces and pages should work for Hub mode as well.  Since our recommended mode is embedded, most services are delivered that way.

      I'm not sure why this would need to be Routing-based though? The Spaces and Pages live on the frontend server - so co-deployed would make sense.   Similarly the assignment of spaces and pages would be to the frontend business role.



      Author's profile photo Christian Köhler
      Christian Köhler

      Hi Jocelyn Dart

      thanks for this quick reply.

      I am completely new to this concept. I am a bit confused because of the follwing:

      I tried to add the /UI2/FDM*-Services in the maint_service-transaction. Two things were strange and new to me:

      1. only found service /UI2/FDM_SPACE_REPOSITORY_SRV under LOCAL-service for activation --> expected to found the other /UI2/FDM-services as well
      2. The other /UI2/FDM-services were already added, but with prcessing mode co-deployed. Because of that, it was not possible to add LOCAL-system alias. I have to change the processing mode first, to add the system alias.

      I will do a bit research. Hopefully it will be clear for me afterwards. 😉


      best regards


      Author's profile photo Joseph Chinnabathini
      Joseph Chinnabathini

      Hi Jocelyn,

      Is it possible getting this feature by upgrading FES to FES 2020?



      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Jo

      Yes if you upgrade your FES to FES 2020 you get the Spaces and Pages capability.

      You can upgrade to FES 2020 if you are on SAP S/4HANA 1809 or 1909 - embedded or standalone FES are both fine.

      What you only get with SAP S/4HANA 2020 is the SAP-delivered Spaces and Pages content as examples.

      However that said, I have a couple of customers already using FES 2020 with SAP S/4HANA 1909 specifically to use Spaces and Pages. It was easy enough to get going. Just follow the SAP Fiori launchpad guide for SAP S/4HANA 2020 - there's a section on Managing Spaces and Pages.

      Author's profile photo Thomas Menges
      Thomas Menges

      Hi Jocelyn Dart ,

      thanks for your blog. Great.

      Perhaps you can help me by solving following problem:

      I understand to reduce the flp from classic UIs but how can following part be done?

      We're using S/4HANA 2020 OP (FPS0)  and here we want to use spaces and pages in the flp.

      Everything is working fine by defining spaces and pages... but

      we consider following problem:

      If we're using groups instead of spaces and pages it is possible for the enduser to add user-specific  tiles (transactions) via the appfinder --> sap menu

      This functionality is missing if you're using spaces and pages. You can navigate to the appfinder and go to SAP menu. Here you can see the (transactions as tiles) but you're not able to add these tiles to a page /section.

      If you go to the catalog tab it is possible to add these tiles.


      How can this be done or is this a missing functionality?


      Thanks for your answer.


      BR Tommy

      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Tommy

      This is a known issue and the product owner tells me the fix will be included with SAP S/4HANA 2020 FPS1. We are also planning to make the fix available available for SAP S/4HANA 2020 FPS0.

      Once you have the fix you will be able to add favorites from the SAP menu to spaces.

      Author's profile photo Marion DUPIN
      Marion DUPIN

      Hi Jocelyn Dart,

      Thank you for this very nice blog.

      I now use Spaces & Pages in my S/4HANA 2020 SP01 but I have one issue: I can't find how to add a local tile with "Save as Tile" functionality.

      For example, on a KPI tile, if I click on "Save as Tile" to save my tile with my title and pre-selected filters, the tile is added to "My Home" group, but nowhere in Spaces and Pages.

      I don't find any way to use theses local tiles with Spaces & Group: how can I use my new tile saved?

      Thanks for your help,

      Best regards,

      Author's profile photo Sylvia Strack
      Sylvia Strack

      Hi Marion,

      If you are talking about the Smart Business KPI tiles, the plan is that they will contain the "Save as Tile" functionality in the upcoming SAP S/4HANA 2021 release. For all other tiles, the SAP Fiori launchpad already supports the "Save as Tile" functionality.

      Best regards,


      Author's profile photo Marion DUPIN
      Marion DUPIN

      Hi Sylvia Strack,

      Thanks, yes I was talking about Smart Business KPI tiles.

      Thanks for your help.



      Author's profile photo Manish Gupta
      Manish Gupta

      Hi Sylvia,

      We have upgraded to S4 HANA 2021 version, and facing an issue in saving the KPI tiles.

      I can see the tile in the allocated page, but it keeps on processing always and the name etc is not visible.




      Author's profile photo Sylvia Strack
      Sylvia Strack

      Hi Manish,

      In the case that you haven't done so yet, could you please create a support ticket on the component CA-FLP-FE-COR? Then our support teams can have a look into the issue.

      Best regards,


      Author's profile photo Hans Verreydt
      Hans Verreydt


      As we're currently on S/4HANA 2020 SP 01 (02/2021) FP, the "My Home" space option is not yet available. Is this addable with a note? or do we need to update our system?


      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Hans, You need to upgrade to get it sorry. You can always create an empty space and "My Favorites" page and use that as an equivalent in S/4HANA 2020.

      Author's profile photo Raghu M
      Raghu M

      Hi @Jocelyn Dart,


      we have a requirement to migrate the current set of users to spacing and paging concept in FLP.  Provided we have Fiori up and running for the users with groups and catalogs . So, while migrating to spaces and pages, Could you please throw some light on the things that should be taken care?


      1. The migration of the objects is a manual effort ? or do we have any tool for performing this? (i.e groups to spaces and pages , however business catalog can be reused if i am not wrong) so, please advise on the re-usability part
      2. or recommend to use the concept for upcoming activities and let the older one be as is ( if so, will that not affect the user experience)

      Thanks in advance for your valuable time and comment!



      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Raghu, There is a migration tool available from SAP S/4HANA 2021 FPS01. Please raise a SAP Incident if you need this downgraded to your release. See the advice Transition from the Home Page to Pages in the latest SAP Fiori launchpad guide.

      Author's profile photo Kiran J
      Kiran J

      Hi Dart,

      I am trying to translate custom Spaces (tabs) and Sections in our new S4HANA 2020. But as per the documentation in SE63, I am not able to find Spaces and Sections -

      Select Translation  ABAP Objects  Short Texts. Expand A5 User Interface Texts and select UISC or UIPC;

      For cloud this blog is very nice but there is no blog for OnPremise translations.

      Should I raise a message with SAP?




      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Yes please raise a SAP Incident for this and make sure you state your SAP S/4HANA release and FPS/SPS

      Author's profile photo Ranjit Daniel
      Ranjit Daniel

      Hi Jocelyn Dart have an issue were I have added a particular tile to page > section from a sap standard catalog via the manage launchpad pages app. The user's role authorises the user for that tile via a custom Z catalog, role also contains the spaceId.

      When the user's logs in, is not able to see that tile defaulted in the Space > Page > Section.

      Question is, do I need to add the tile to the page from the custom catalog as well? If yes, this might become an administration overhead as we will need to add tiles from custom catalogs as well as the security team authorise users for the apps they need through custom catalogs only.

      Would appreciate your thoughts/advice on this.



      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Ranjit, Yes you need to add the tile from the relevant custom business catalog assigned to the role. I would suggest raise your concern and explain your desired process in a SAP Incident to component CA-FLP-FE-DT and ask for a response from the product owner, as I am aware there have been some discussions around this type of scenario already and it may be something he/she is considering for the roadmap

      Author's profile photo Ranjit Daniel
      Ranjit Daniel

      Thanks Jocelyn Dart will do

      Author's profile photo Ranjit Daniel
      Ranjit Daniel

      Hi Jocelyn Dart have an issue were I have added a particular tile to page > section from a sap standard catalog via the manage launchpad pages app. The user's role authorises the user for that tile via a custom Z catalog, role also contains the spaceId.

      When the user's logs in, is not able to see that tile defaulted in the Space > Page > Section.

      Question is, do I need to add the tile to the page from the custom catalog as well? If yes, this might become an administration overhead as we will need to add tiles from custom catalogs as well as the security team authorise users for the apps they need through custom catalogs only.

      Also noticed that if I add the same tile from 2 different catalogs to the same page and if the user has both those catalogs assigned in their role it shows the tile twice for the user.

      Would appreciate your thoughts/advice on this.



      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Duplicate question? Please see my previous response.

      Yes it's perfectly possible to add the same tile twice. The tile in the custom catalog and in the SAP catalog are treated as separate entities. And you can have app variants (variations of the same app) assigned to the role. So multiples have to be possible.

      Author's profile photo Ranjit Daniel
      Ranjit Daniel

      Thanks Jocelyn Dart

      Author's profile photo Rachid Kaouass
      Rachid Kaouass

      Hi Jocelyn Dart

      I would like to be sure that we are following the best practices of structuring the spaces/pages among different roles. The following case where we have common applications and catalogs among the different roles, and for some specific users some different catalogs/applications.

      we've designed the following:


      Spaces - Pages and Catalogs

      So the idea is to build:

      • One domain (Buyer / P2P)
      • We have different Roles (Buyer, Buyer Manager, Support Buyer Manager, etc...)
      • They have lot in common, and some catalogs are different
      • To minimize the effort of building for each Role a different spaces with common/reused pages and some pages specific to a role, the idea is too only create on spaces and its pages. Thanks to catalogs concept, if the user doesn't have the catalog he won't see the tile (which is perfect in our context)

      Is it part of the best practices, or not at all?

      This avoid having several "identical" Spaces because of some differences between the roles.

      PS: this works fine, except that looking at the console of the Developer tools, I saw that some errors were logged to indicate that some tiles were not displayed as no catalog were found...

      Thanks for your feedback.



      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Rachid, So in your diagram is "Buyer" the space?

      From what you have shown, in my opinion this design certainly seems viable.

      You might want to raise an SAP Incident about the console errors - they are correct but it might be worth asking if they could be downgraded to a warning, just to avoid unnecessary troubleshooting.

      Author's profile photo Rachid Kaouass
      Rachid Kaouass

      Hi Jocelyn

      yes, "Buyer" is the space.

      Thanks a lot for the quick reply, we will continue then on that direction and we will open a SAP Incident to avoid confusion/troubleshooting.



      Author's profile photo Rachid Kaouass
      Rachid Kaouass

      Hi Jocelyn Dart

      It seems that changing the severity to warning instead of errors will not be possible:

      3193445 - Console errors when no authorization for a tile in a Page


      Except if you can discuss this internally 🙂




      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Thanks for letting me know! I will certainly discuss it internally. However that may take some time.

      For now, I would suggest you simply make a note of this in your support and troubleshooting procedures, so that it does not cause confusion. That is the error message is correct, but can be ignored, as this is part of your security design.

      Author's profile photo Eivind Boe
      Eivind Boe

      Hi Jocelyn

      Thanks for your contribution to the community.

      We are also considering what is the best way to structering roles that have alot in common. Do you know if there is anything planned to reuse the space for multiple roles and using catalogs/authorization to determine what applications a user can access and not acess?

      Author's profile photo Hans Verreydt
      Hans Verreydt

      Hi Jocelyn Dart

      When I started working with Spaces & Pages, I came also to the conclusion (from our key users) that when a user only has 1 space, it's easier to create multiple spaces for each of their pages (with only 1 page)

      Let me explain in detail:

      For example: Our Customer Service Agent, has 1 space "Customer Service". This Space has multiple pages. "Order Processing", "Delivery & Shipment", "Reporting", ...

      So, when they started to this test, they preferred not 1 space, but multiple spaces, with 1 page. Space "Order Processing", "Delivery & Shipment", "Reporting", ... with their own page.

      When we have our "Customer Supervisor", he has the Space "Customer Service", but also other Spaces. In this case, we just your the Space "Customer Service" with the pages "Order Processing", "Delivery & Shipment", "Reporting", ...


      For this I actually used my Business Roles without any Spaces attached. But I created 2 separated roles for the Spaces. For example: Z_SS_CUSTOMER_SERVICE & Z_MS_CUSTOMER_SERVICE  (SS = Single Space & MS = Multi Space). With this, I can also re-use all the pages and I only need to create more Spaces...

      These Space roles, are combined with the Business Roles in a specific Composite Role.


      Is this a way that you would say, Okay, you can work that way, or is this "not done"?

      Just want to know what you think about this way 🙂




      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Hans

      Thanks for asking and for explaining your design. It’s useful for us to understand different approaches - so thanks!  A little feedback and first thoughts below

      The way you describe your reuse of pages is fine and a naming convention is always a useful idea. The multi page spaces are all fine. Also having a role which has just one space and page is fine

      However giving users with 1 role many single page spaces?  Hmmmm…..this I raises several concerns in my mind 

      Did you talk to your users about why they preferred it that way? This sort of against the strategic direction of usability approach needs a bit of exploration (eg asking why x 5 to delve deeper and deeper into their thinking to uncover the mindset and root issues). 

      Unfortunately to me the approach with a role with lots several single 1 page spaces feels uncomfortably like using Spaces to reimplement Groups, so is likely to have similar disadvantages to groups when you try to scale. For example I can see it could be very confusing when a user changes positions and moves from having one business role to multiple business roles or vice versa. It also reintroduces some of the role maintenance effort issues we had with assigning groups to roles. 

      If it was me I would be inclined to try to avoid having users with only 1 space - e.g. everyone gets an Employee space  + their main business role space. That would be a simple way to get the role-based space approach across without creating problems later.

      Worth considering?


      Author's profile photo Hans Verreydt
      Hans Verreydt

      Hi Jocelyn,

      Thanks for your reply!

      I found out that our users, who only need to do their specific work, just like the "1 space / 1 page" concept, because of the overview that they have on top of the page. They don't like to do the extra click on the "more" arrow' before choosing their page.

      Of course it's more like the "Groups" concept, but I made sure that they don't have more then 6 spaces / pages. So Everything is visible on top of the Launchpad.

      After thinking a little bit further... What another possibility would be, when having only 1 space, is to have on each page, a sort of "quick links" on top of the page (breadcrumb like?) so users can switch easily between the pages in 1 single space, without having to have the extra click.

      But for this, we need to create a tile for each page of course 🙂

      Something like this (that I just quickly did...)

      In my case, I can switch directly to the Overview page from the Accounts Payable Space.

      Maybe this would be a nice option to build in standard?


      But, I'm further thinking outside the box, to check how I can make it as user friendly as possible, also with considerations to the future, with indeed a Employee Space, a Home Space, ...


      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Hans, I don't mind idea of a direct link to the page ... sneaky but could be effective 🙂

      Again my view would be 6 tabs is a lot to maintain for multiple roles - particularly when you need to add/remove spaces. I also suspect it will start to get really painful for users as soon someone with multiple single pages moves into a role with multiple spaces or vice versa.  I would expect users will get quite frustrated with that change. Especially if it's a temporary move such as someone acting on behalf of a manager.

      Giving them a quick link option that they could add to their My Home page for at least every Overview page.... that might a better option. Of course they could just use their My Home page to add the apps they use most often directly to that page.

      Probably best to prototype a couple of approaches, get them to actually try it out, and then agree on your design together.  For that you need to canvas a small set of users from your current single space and multiple space roles and ideally get them to touch and feel it. Talk to them about how would you get started each morning...

      Remembering also that launching a tile from a page is only ONE option to get to an app. They can also use the Search (on Apps), the Home navigation button, the App Finder, and app to app navigation.

      Good to agree on these options together and then document them including the reasons why in your UX Strategy.




      Author's profile photo Hans Verreydt
      Hans Verreydt

      Let me first say that I really like the Spaces & Page concept, but I already noticed that our users want to quickly access the apps that they need by just clicking on the tile instead of using the search, app finder, ...  with of course as less possible clicks.

      Maybe is would be a good improvement of the Space & Page concept when working with a sub-bar, under the Space titles with the specific page titles?

      Maybe instead of the "more" arrow, or in combination with it?

      Our users are currently testing this option (with the links of the pages on top op each page), but then currently the first 4 à 5 cm of the page are a bit "lost space".

      Current test case: (in this case, if they don't want to use the extra links, they can just remove that section from the space)

      An option for in the future of Spaces & Pages?



      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Hans

      Hmmm... are you on S/4HANA 2020 ? With 2021 every user gets a Home Page where they can organize their most frequent apps for themselves. You can see some screenshots in this blog

      In 2020 you can set up and assign an empty page as your My Home page.

      My thinking is I would be concerned that this might be tipping into over-engineering the design. Users won't be able to give you effective feedback until they can actually touch and feel it - which is why prototyping a couple of different designs is important.

      It's also important to respect personal preferences - even though you have found some of your users, and perhaps some of your most vocal users like all that on one page, for others so many links could become a lot of clutter and visual noise. Visual noise can negatively impact on people's stress levels and mental health.

      You also might want to set up a user feedback survey or review point 1-2 months after go-live to see what needs to be adjusted.





      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Hans, I have actually checked with the Spaces and Pages product owner and she has confirmed this sort of flat navigation style has been discussed and is under consideration - although not for the near future.

      So given that advice, if you want to try the flat links approach I would suggest that is fine to go ahead. And we would be interested to hear any feedback from your users.

      I would still recommend a prototyping approach to minimize effort and avoid rework.  That is, you might want to trial it with a couple of roles first and get feedback before committing to the effort of adjusting all roles.


      Author's profile photo Adrian Ruano Gonzalez
      Adrian Ruano Gonzalez

      Hello Jocelyn,

      Thanks a lot for all these Fiori posts which are really useful!

      We have recently upgraded to S/4 2021 and started implementing Spaces & Pages to replace the Groups. However, we are facing a very important issue: we have some spaces with multiple pages, but depending on the role the end user has assigned, some pages do not contain any application and therefore they are empty of content and are still visible. This does not happen when a section does not contain any app, it is hidden.

      Due to this issue and the complaints from the end users we have been forced to implement every page in a different space, getting a very similar approach to the old Groups.

      Do you have a recommendation for this scenario? Is there any setting or anything we can do to hide the pages which are completely empty?

      Thank you very much.


      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      HI Adrian

      Thanks for raising this... to me this is one of those areas where security administrators need to consider carefully the impact of role design on usability. 

      My feedback that what you describe is certainly a step backwards and not the approach we want.  I would suggest its better to rethink the role to pages design where you can.

      It's difficult to comment without seeing the design details.  What I have noticed is there can sometimes a point at which too much focus on technical reuse can result in degraded usability which I suspect is what has happened here - again it's difficult to verify that without knowing the design.

      Perhaps your spaces need to be more granular (so there are less conflicts between related roles) or your pages need to be less granular (so there are always some tiles)?  You could also look at creating similar spaces with the same tab title for users but with different combinations of pages.

      Or even better get your key users (power users? subject matter experts? business process experts?) to discuss better page names so users know when it's relevant.  I will also pass this to the product owner to consider how visibility of the page might be controlled when the user has no tiles assigned - but that would be something for the longer term. 

      I'm wondering also if you have allowed users to add their own apps to the page? Then they could at least use the empty pages for whatever apps they prefer. 

      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Some good news for the future...  the product owner tells me the team are working on providing a feature to hide empty spaces and pages from the spaces menu.

      So while we don't have an official release date for that feature yet, at least it gives you some hope that you can avoid this problem in future.

      In the meantime perhaps to manage the impacts with your current design, you might want to consider a FLP extension for example to add a "Find out why some pages have no tiles" to the footer bar of all pages that takes you to a static help page with possible causes. That would at least help reduce confusion for users.  Just a suggestion.

      Author's profile photo Klaus Kronawetter
      Klaus Kronawetter

      Hi Jocelyn,

      do you have any updates on this? (Hiding empty pages/spaces for Fiori users)

      We are currently in the middle of an S4 migration and it would really simplify the distribution of spaces. Basically, with this feature we could assign all spaces to just one role which every user gets and the rest is done with business catalogues.

      BR Klaus

      Author's profile photo Christophe Fleury
      Christophe Fleury

      Hi Jocelyn,

      First thanks a lot for all your informations that help us !

      I have some questions :

      • We currently use "groups"  in our Fiori hub. We will migrate soon (to 2020 release) and I would like to use now the SPACES/PAGES instead "group". Is there any tools for passing to that or do we need to do manually ?
      • During the testing phases, I understood it is possible to have "both world" in the FLP (by activate the SPACE usage in the "setting" ) and let the time to verify the organization (so as to validate that contents is ok). Right ?



      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Christophe

      yes and yes!!

      I have some newer blogs on this that will help you

      SAP Fiori for SAP S/4HANA – Spaces and Pages now available in the SAP Fiori apps library

      SAP Fiori for SAP S/4HANA – Migrating from groups to spaces and pages – Why, When, and Key Differences for Users

      SAP Fiori for SAP S/4HANA – How to migrate from groups to spaces and pages

      Author's profile photo Christophe Fleury
      Christophe Fleury

      Hi Jocelyn,

      Thanks a lot,

      I have hust read this comment : "Create Launchpad Pages from Groups is new in SAP S/4HANA 2021 FPS01" you mean if we pass from 1809 to 2020 we must manually create the SPACES and put all the TILES from "groups" into the corresponding PAGES...the "automatic" tool will only come with 2021 release. Right ?

      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Christophe, Yes that's correct. The new tool is available with the new release.

      If you wish, you could raise a SAP Incident and ask for it to be downported.

      Since it's part of the Fiori Frontend Server (rather than S/4HANA itself) you might also get it by upgrading your FES.

      In 2020 I would suggest focusing on some target user groups and work out your design... then move gradually.

      Author's profile photo Josep Balateu
      Josep Balateu

      Hi Jocelyn,


      we are implementing Space and Pages in an embedded on-site S/4Hana, release 2022. My questions are regarding "My Home Page":

      is there anyway to copy the HomePage from one user to another?

      is there anyway (besides program /UIF/MIGRATE_FES_PERSO) to copy the HomePage from one system/client to another)?



      Author's profile photo Jocelyn Dart
      Jocelyn Dart
      Blog Post Author

      Hi Josep,

      Re: is there anyway to copy the HomePage from one user to another? 

      No. The point of having a My Home is that it is personal to you. If you want a home page that is shared by more than one person then you should create a custom space in Manage Launchpad Spaces, assign it to the relevant role, and create custom page in Manage Launchpad Pages.

      We have a microlearning videos showing how: Creating SAP Fiori Launchpad Layouts for Custom Business Roles - SAP S/4HANA

      Re: is there anyway (besides program /UIF/MIGRATE_FES_PERSO) to copy the HomePage from one system/client to another)? 

      No that is the only tool provided for that purpose .. primarily where customers are moving from standalone FES to embedded FES, but it can also be used to copy personalization in broader use cases.

      Hope that helps.