Guide · SAP Fiori
Fiori Spaces and Pages: Fix "Out of Role Context" Tiles
Why Fiori spaces and pages show missing tiles or "Out of role context" in S/4HANA, and the role and catalog checks that fix them. Test per role.


A tile on a Fiori space page appears only when three things line up: the space is assigned to a business role the user holds, the tile's business catalog is granted by a role the user holds, and the page itself is visible. When one link breaks, the tile shows "Out of role context" in Manage Launchpad Pages or simply disappears for the user. Fix it by checking the chain in order, then testing each role's home page before anyone signs off.
What "Out of role context" actually means
The message is a design-time warning, not a runtime error. An administrator adds a tile to a page, and the tile's source catalog is not part of the role context of that page. SAP Learning's spaces and pages course explains that tiles added by selecting catalogs manually show this warning and do not appear in the preview. The fix is in the role, not the page.
SAP Knowledge Base Article 3422718 confirms the cause for S/4HANA Cloud: the business catalog behind the application is not assigned to the business role or space. Its resolution is to assign that catalog to the role. The KBA also points you to the Fiori Apps Reference Library to find the catalog an app needs.
Check the chain in order
Work from the user's side backward. Most tickets close at step one or two.
- Space to roleConfirm the space is linked to the business role in PFCG, under the transaction menu.
- Page visibleConfirm the page is set to Visible in Manage Launchpad Spaces or Pages.
- Catalog in roleConfirm the tile's business catalog is in a role the user holds, not just the page's role.
- User assignmentConfirm the role is assigned to the user in SU01 and the user is not missing a derived role.
- Runtime proofLog on as the test user and confirm the space, page and tile show up.
- Space to roleSpace linked in PFCG
- Page visiblePage set to Visible
- Catalog in roleTile catalog granted
- User assignmentRole held in SU01
- Runtime proofTest user sees tile
Step 1: Link the space to the role
Spaces are linked to roles in PFCG. SAP Learning makes the sequencing point clearly: the space should be assigned to a role before you add apps to its pages. Practitioners also report that a space linked only to a derived role may not appear for users, while the master role works. One SAP Community thread describes exactly this pattern, so test derived roles separately rather than assuming inheritance.
Also confirm the launchpad mode. Spaces appear only when the SPACES parameter is set and the user can reach them. A blank launchpad, according to one practitioner guide, usually means the SPACES parameter is not active for that user, or the role in SU01 has no space linked at all.
Step 2: Make the page visible
A new page is not automatically shown. A SAP Community walkthrough notes that a page can be created in a hidden state and must be set to Visible before it appears in the space. SAP's own course makes the same point, so check the visibility flag for every page in the space, not just the ones your team built this sprint.
Step 3: Grant the catalog through a role
This is where most "out of role context" cases sit. The catalog must be reachable through a role the user holds. SAP Learning states the rule directly: the source catalog of the tile must sit in a role that is also assigned to the user. A catalog attached only to the space's role, but not to the user's roles, still fails.
For composite roles, check SAP Note 3625412. It describes the "Out of role context" error when editing pages in composite roles that include derived roles, with S/4HANA 2023 as the example release. The note says the problem is design-time only and does not occur at runtime. That distinction matters: a tile can look broken in Manage Launchpad Pages while users see it fine, and the reverse can also happen.
Step 4: Confirm the page is not empty for the role
Design-time checks catch most of this. In Manage Launchpad Pages (F4512), use the Page Preview with role context to see which tiles appear for a chosen role combination. This is the fastest way to prove a page works for a role before a user logs on.
Empty spaces and pages: the setting depends on your release
A space or page with no visible content for the user can clutter the menu. SAP added a launchpad setting for this, but the release matters. SAP Note 3635191 covers hiding empty spaces and pages, and its keywords list S/4HANA 2025 on-premise. Its symptom is spaces or pages created without any catalog, which then appear empty.
The setting is SPACES_HIDE_EMPTY_SPACES_PAGES, changed in Manage Launchpad Settings. SAP Community describes the switch as hiding empty spaces and pages from the space menu and the App Finder, where "empty" means no role-based or device-based content. A practical caveat: pages a user emptied by personalization are not hidden.
The default has moved. The SAP IBP 2502 documentation says the setting defaults to false. SAP Note 3580798 states that with release 2508 the feature is activated by default and the setting is removed from Manage Launchpad Settings. Those two sources describe different releases, so do not assume the behavior from one. Check your system's Manage Launchpad Settings and the note that applies to your release.
What changed from ECC and from groups
In ECC, most teams built the home page with catalogs and groups. S/4HANA moves that to spaces and pages. SAP Community quotes SAP Note 3500249 on the status: groups are deprecated, but they remain in S/4HANA 2025, and SAP has not set a removal date yet. The same thread says the Technical Catalog Migration is part of the upgrade itself, while the groups-to-spaces move is a post-upgrade project.
The move is not automated. SAP's cloud blog says SAP does not provide a mass tool to migrate group content into spaces and pages. Two practical differences affect testing. First, the content of pages cannot be locked the way groups could. Second, switching users to spaces can leave the home page empty until users rebuild it, so prepare users first.
There is also a tool-name conflict to resolve in your system. One SAP Community post names /UI2/FLP_GTP for creating pages from groups, while a practitioner guide names /UI2/FDM_GTP. Confirm the transaction in your release before you write it into a runbook. The same SAP post says the Overview of Roles, Spaces and Pages (/UI2/RSP_LIST) is retired in favor of the Launchpad Content Aggregator (/UI2/FLPCA), which SAP describes as including spaces and pages from S/4HANA 2025. Academy material still lists /UI2/RSP_LIST, so check which transaction your release provides.
| SPACES setting | SPACES_ENABLE_USER setting | What the user gets |
|---|---|---|
| true | true | Spaces on, and the user can switch between spaces and the classic home page |
| true | false | Spaces only; the user cannot switch back |
| false | true | Home page by default; the user can switch to spaces |
| false | false | Spaces deactivated |
Source: SAP Help Portal, Enabling Spaces
Test every role before the sign-off
Launchpad content is a role-driven defect area, so test it per role. Treat a missing tile as a content or role defect until proven otherwise. Our guide on testing Fiori catalog authorizations in S/4HANA roles covers the catalog side in depth; this section focuses on the space and page layer.
- Build the expected list. For each business role, list the spaces, pages and tiles the role should show. Use the design guidelines as a sanity check: SAP Learning lists one space per role, one to five pages per space, two to five sections per page, three to seven tiles per section, and under 25 tiles per page.
- Run Page Preview per role. Use F4512 with role context for each role, and save the screenshots as evidence.
- Log on as a test user per role. Confirm spaces, pages and tiles match the list, and launch one tile per catalog to prove the target mapping works.
- Retest after every transport. Spaces and pages are customizing objects, and a customizing transport is mandatory when you create or change a space. A catalog change in one role can hide tiles in another, so rerun the role checks after each transport.
- Check derived and composite roles separately. Use the logon result, not the design-time view alone, as the sign-off evidence.
For the broader role and authorization testing approach, the free Academy course "Testing Business Roles and Authorizations" walks through the same logic for business testers. Use our SAP Fiori Launchpad Role and App Test Checklist to record each role's result.
Frequently asked questions
Why does my Fiori page say "Out of role context"?
The tile's business catalog is not granted through a role the user, or the page's space, holds. SAP's knowledge base fix is to assign the required business catalog to the role. Confirm the catalog in the Fiori Apps Reference Library first.
Why does a user see no spaces even though the role has one?
Check that the SPACES parameter is active for that user and that the space is linked to the role the user actually holds. If the space is linked only to a derived role, test the master role too, because one SAP Community thread reports that inheritance did not work.
Can I stop empty spaces and pages from showing?
Possibly, depending on the release. SAP Note 3635191 introduced the SPACES_HIDE_EMPTY_SPACES_PAGES setting, and SAP Note 3580798 says it becomes active by default in 2508 and is removed from the settings app. Check your release and its note before you change the setting in production.
Do I have to move from groups to spaces in S/4HANA 2025?
Not in the upgrade itself. SAP Note 3500249 says groups still exist in S/4HANA 2025, but they are deprecated and will be removed in a future release. Plan the move as a post-upgrade project with user change management.
Sources
- Creating SAP Fiori Spaces and Pages, SAP Learning, undated
- Creating SAP Fiori Spaces and Pages (Learning the Basics of SAP Fiori), SAP Learning, undated
- 3422718 - Manage Launchpad Pages: Page content tiles are displaying error 'Out of role context', SAP Knowledge Base
- 3625412 - Error "Out of role context" when editing Launchpad Pages with composite roles, SAP Knowledge Base
- 3635191 - Hide empty Spaces and Pages in SAP Fiori Launchpad, SAP Knowledge Base
- 3580798 - Hide Empty Spaces/Pages - SAP Fiori Launchpad, SAP Knowledge Base
- Catalogs and Groups for FIORI Launchpad, SAP Community Q&A (cites SAP Note 3500249)
- Enabling Spaces, SAP Help Portal
- Switching from Groups to Spaces and Pages in SAP S/4HANA Cloud, Public Edition, SAP Community blog
- SAP Fiori for SAP S/4HANA: Composite Roles in launchpad content and layout tools, SAP Community blog
- SAP Fiori launchpad: Hiding empty spaces and pages, SAP Community blog
- Hide Empty Spaces and Pages in SAP Fiori Launchpad, SAP Help Portal (SAP IBP 2502)
Free S/4HANA testing templates
Master test strategy, migration test plan, cutover runbook, go/no-go checklist and more.
The RISE Testing Playbook
One practical move a week for testing your ECC to S/4HANA transformation.
How this guide is made: researched with AI-assisted search across SAP documentation and practitioner sources, with every fact linked to its source. Found an error or have field experience to add? Tell us.