SAP FIORI RESOURCE HUB · 2026
SAP Fiori Launchpad TCode — Complete Reference List (2026)
SAP Fiori Launchpad transaction codes (tcodes) are the backend commands administrators and Basis teams use to configure, customize, and troubleshoot the Fiori Launchpad — the tile-based entry point every Fiori user logs into. This page is a complete, categorized reference: configuration, designer, content management, administration/authorization, and monitoring/troubleshooting tcodes, organized so you can jump straight to what you need
TABLE OF CONTENTS
1. Why Do Launchpad TCodes Matter?
2. Why TCodes Still Matter in a Fiori World
3. Master TCode Reference Table
4. Configuration TCodes
5. Designer TCodes
6. Content Management TCodes
7. Administration & Authorization TCodes
8. Monitoring & Troubleshooting TCodes
9. Catalogs, Groups & Roles — How They Interconnect
10. How to Assign Fiori Apps to Roles via TCode
11. How to Create a Custom Fiori Launchpad Tile
12. TCodes vs. Classic SAP GUI TCodes
13. TCodes by SAP Version (ECC vs. S/4HANA)
14. Quick-Reference Summary
15. FAQs
16. Related Resources
Why Do Launchpad TCodes Matter?
The Launchpad looks simple to the end user — log in, click a tile. Behind it is a full configuration layer, and none of it is editable from inside the Launchpad itself.
The Fiori Launchpad looks simple from the user’s side — log in, click a tile, the app opens. Behind that simplicity is a configuration layer: which apps exist, which catalog and group they belong to, which roles can see them, and how navigation between apps is wired together. It’s configured and maintained through a specific set of transaction codes in the backend system.
If you’re setting up a new role’s Launchpad view, troubleshooting a missing tile, or registering a new OData service so a custom app can pull data, you’re working through these tcodes — not through Fiori itself.
Why TCodes Still Matter in a Fiori/Launchpad World
It might seem counterintuitive that a “modern, tcode-free” interface still depends entirely on tcodes to configure — but that’s exactly the split: Fiori replaced tcode-driven work for end users, not for administrators. The Launchpad, catalogs, groups, roles, OData service activation, and error monitoring are still managed the classic way, through SAP GUI and transaction codes, even on the newest S/4HANA Cloud releases.
- Left: End Users — Fiori Apps, no tcodes
- Right: Admins — SAP GUI + TCodes, no Fiori apps
This is also why “Fiori” and “SAP GUI” aren’t really competitors — they’re two different audiences using two different tools for two different jobs. A finance approver never sees a tcode; the person who set up their Launchpad role used several.
Before you rely on a tcode
Availability depends on your SAP release and Launchpad model (classic catalogs/groups vs. Spaces & Pages). Verify a tcode exists in your own system before building a process around it.
Master TCode Reference Table
Not every tcode below exists in every SAP system — availability depends on your SAP release and which Launchpad model (classic vs. Spaces &
Pages) your landscape uses. Verify against your own system before relying on any single tcode
SAP’s exact transition and retirement status for older URLs can change — confirm
current status against SAP’s documentation before citing a definitive retirement date.
|
TCode
|
Purpose
|
Category
|
|---|---|---|
|
/UI2/FLP
|
Opens the Fiori Launchpad directly from SAP GUI
|
Access
|
|
/UI2/FLPD_CUST
|
Launchpad Designer — client-specific customization (catalogs, groups, tiles)
|
Configuration
|
|
/UI2/FLPD_CONF
|
Launchpad Designer — cross-client configuration
|
Configuration
|
|
/UI2/FLPCM_CUST
|
Launchpad Content Manager — client-specific (business catalogs)
|
Content
|
|
/UI2/FLPCM_CONF
|
Launchpad Content Manager — cross-client
|
Content Management
|
⚙Fiori Launchpad Configuration TCodes
|
TCode
|
Purpose
|
|---|---|
|
/UI2/FLPD_CUST
|
Client-specific Launchpad Designer for catalogs, groups, and tiles
|
|
/UI2/FLPD_CONF
|
Cross-client Launchpad Designer configuration
|
|
/UI2/SEMOBJ
|
Maintain customer-specific semantic objects used in navigation
|
|
/UI2/SEMOBJ_SAP
|
View SAP-delivered standard semantic objects
|
Fiori Launchpad Designer TCodes
|
TCode
|
Purpose
|
|---|---|
|
TCode Purpose /UI2/FLPD_CUST
|
Primary Designer transaction — build/edit catalogs, groups, and tiles at client level
|
|
/UI2/FLPD_CONF
|
Designer transaction for cross-client configuration changes
|
|
/UI2/FLP_INTENTCHECK
|
Validate that tile navigation intents correctly resolve to their target apps
|
Fiori Launchpad Content Management TCodes
|
TCode
|
Purpose
|
|---|---|
|
/UI2/FLPCM_CUST
|
Manage business catalogs at client level — group related apps for role assignment
|
|
/UI2/FLPCM_CONF
|
Manage business catalogs cross-client
|
|
/UI2/FLP_CONTCHECK
|
Run validation checks across Launchpad content for broken references
|
Fiori Launchpad Administration & Authorization TCodes
|
TCode
|
Purpose
|
|---|---|
|
PFCG
|
Assign catalogs and groups to PFCG roles — this is how tiles actually reach specific users
|
|
SU01
|
Maintain user records and role assignments
|
|
SU24
|
Check the most recent authorization failure — first stop when a user reports "access denied"
|
|
SU53
|
Activate the ICF services Fiori/Gateway depends on to run at all
|
|
SICF
|
Maintain default authorization values tied to transactions/services
|
6. Explore SAP Fiori — Choose Your Path
Consectetur adipiscing elit, sed do eiusmodLorem ipsum dolor sit amet, consectetur adipiscing elie lorem ipsum dolor sit amet, consect adipiscing elit sed do eiusmod
Catalogs, Groups, and Roles — How TCodes Interconnect
These three concepts are where most Launchpad configuration confusion happens, because they’re built in one tcode but
consumed in another:
Catalogs
Built in /UI2/FLPCM_CUST or /UI2/FLPD_CUST . A catalog is a container of tiles/apps — the "supply" side
Groups
Also built in /UI2/FLPD_CUST . A group is how tiles get organized visually on a user's home page. Catalogs supply apps; groups arrange how they're displayed.
Roles
Assigned in PFCG . A role connects a catalog/group combination to a specific user — the "demand" side. Without it, a perfect catalog is invisible
The most common admin mistake is building a flawless catalog and group in the Designer, then forgetting the PFCG role
assignment step, which is why “the app exists but the user can’t see it” is almost always a role/authorization issue, not a
Launchpad configuration bug.
Fiori Launchpad Monitoring & Troubleshooting TCodes
|
TCode
|
Purpose
|
|---|---|
|
/IWFND/ERROR_LOG
|
Review Gateway (frontend) errors — usually the first place to check when an app fails to load data
|
|
/IWBEP/ERROR_LOG
|
Review backend service errors, one layer deeper than the Gateway log
|
|
/IWFND/GW_CLIENT
|
Check the most recent authorization failure — first stop when a user reports "access denied"
|
|
ST22
|
Check for ABAP runtime dumps tied to a failed app or service call
|
|
SM21
|
Review the system log for broader system-level issues
|
|
SLG1
|
Review application-specific logs, useful for custom app troubleshooting
|
How to Assign Fiori Apps to Roles via TCode
Coverage spans major SAP business areas, but exact availability depends
on product, release, deployment model, and scenario.
Build or confirm the catalog
In /UI2/FLPD_CUST or /UI2/FLPD_CUST — verify the target app's tile is included.
Build or confirm the group
In /UI2/FLPD_CUST — arrange how the tile should appear on the home page.
Open PFCG
Select or create the target role.
Add the catalog and group
Attach both to the role's menu under the Fiori Launchpad-relevant tab.
Generate and assign the role
Assign to the user(s) via SU01 or PFCG's user assignment tab.
Test the result
Log in as (or impersonate, where permitted) the target user and confirm the tile appears, or check SU53 if it doesn't.
How to Create a Custom Fiori Launchpad Tile
Define the tile's target
Confirm the app/URL/intent it should launch — a standard app, or a custom SAPUI5 app already deployed.
Open the catalog
In /UI2/FLPD_CUST , navigate to the relevant catalog, or create a new one.
Create a new tile
Specify tile type (static, dynamic, or app launcher), title, and icon.
Set the navigation target
Link the tile to the correct semantic object and action — configured via /UI2/SEMOBJ for a new custom semantic object.
Add the tile to a group
So it's positioned correctly on the target home page/Launchpad view.
Assign the catalog/group to a PFCG role
So the intended users actually see it.
Run intent validation
Use /UI2/FLP_INTENTCHECK to confirm navigation resolves correctly before rolling out to users.
Fiori Launchpad TCodes vs. Classic SAP GUI TCodes
|
Fiori Launchpad TCode
|
Purpose
|
Closest Classic GUI Equivalent
|
|---|---|---|
|
/UI2/FLPD_CUST
|
Configure catalogs/groups/tiles
|
No direct GUI equivalent — Fiori-specific
|
|
PFCG
|
Assign Launchpad content to roles
|
Same tcode used for classic GUI authorization roles — shared
|
|
/UI2/FLPD_CONF
|
Activate OData services for Fiori apps
|
No GUI equivalent — Gateway/OData is Fiori-specific
|
|
SICF
|
Activate ICF services
|
Also used for classic GUI web-enabled transactions — shared
|
|
ST22 / SM21 / SLG1
|
Troubleshooting and logs
|
Identical usage in both classic GUI and Fiori — unchanged
|
TCodes by SAP Version (ECC vs. S/4HANA Differences)
ECC with Fiori Add-on
Launchpad tcodes function largely the same, but availability depends on which Fiori add-on packages (UI, Gateway) were installed — not every ECC system has the full /UI2/* namespace active.
S/4HANA On-Premise
The full standard set of Launchpad tcodes covered on this page is generally available and actively maintained
S/4HANA Cloud
Classic catalog/group configuration is shifting toward the newer Spaces & Pages model, managed increasingly through Fiori apps themselves — though Gateway/OData and authorization tcodes still apply
Always confirm which Launchpad model (classic catalogs/groups vs. Spaces & Pages) your specific system uses before assuming atcode from this list applies directly — this is the single most common source of confusion when following generic tcode guides
Quick-Reference Summary
The table below condenses this guide into a single scannable list — bookmark or print this version
|
Category
|
Key TCodes
|
|---|---|
|
Access
|
/UI2/FLP
|
|
Configuration
|
/UI2/FLPD_CUST , /UI2/FLPD_CONF
|
|
Content Management
|
/UI2/FLPCM_CUST , /UI2/FLPCM_CONF
|
|
Gateway/OData
|
/IWFND/MAINT_SERVICE , /IWBEP/REG_SERVICE , /IWFND/GW_CLIENT
|
|
Authorization
|
PFCG , SU01 , SU24 , SU53
|
|
Monitoring/Troubleshooting
|
/IWFND/ERROR_LOG , /IWBEP/ERROR_LOG , ST22 , FAQs What is the tcode for the Fiori Launchpad Designer? /UI2/FLPD_CUST for client-specific changes, or SM21 , /UI2/FLPD_CONF for cross-client configuration. How do I check my Fiori Launchpad configuration? Use /UI2/FLPD_CUST to review existing catalogs and groups, and SLG1
|
What is the tcode for the Fiori Launchpad Designer?
/UI2/FLPD_CUST for client-specific changes, or
SM21 ,
/UI2/FLPD_CONF for cross-client configuration.
How do I check my Fiori Launchpad configuration?
Use
/UI2/FLPD_CUST to review existing catalogs and groups, and
SLG1
/UI2/FLP_CONTCHECK to validate that content references aren’t broken.
Why can't a user see a Fiori app tile that should be assigned to them?
This is almost always a role assignment issue, not a Launchpad bug — confirm the catalog/group is correctly added to their PFCG role, then
check SU53 for authorization failures.
Is there one universal tcode for the Fiori Launchpad
No —/UI2/FLP opens the Launchpad itself, but configuration, content management, and troubleshooting are each handled by different,
purpose-specific tcodes covered throughout this guide.
Do these tcodes work the same in S/4HANA Cloud as On-Premise?
Not entirely. S/4HANA Cloud is shifting toward the Spaces & Pages model, where more configuration happens through Fiori apps themselves
rather than pure backend tcodes.
What's the difference between /IWFND/ERROR_LOG and /IWBEP/ERROR_LOG?
/IWFND/ERROR_LOG shows errors at the Gateway (frontend) layer;
/IWBEP/ERROR_LOG shows errors one layer deeper, in the backend service
itself. Checking both helps isolate where a failure is actually occurring.
Can end users access any of these tcodes?
No ,these are administrative/technical transactions used by Basis teams, technical consultants, and developers. End users interact only with
the Fiori apps themselves
What tcode do I use to clear the Fiori cache after making changes?
/UI2/CACHE_DEL is the primary tcode for clearing specific UI2 cache entries after catalog, group, or tile changes.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Change one filter at a time when troubleshooting — it’s the fastest way to isolate what’s excluding an application.
FAQs
What is the tcode for the Fiori Launchpad Designer?
/UI2/FLPD_CUST for client-specific changes, or
SM21 ,
/UI2/FLPD_CONF for cross-client configuration.
How do I check my Fiori Launchpad configuration?
Use
/UI2/FLPD_CUST to review existing catalogs and groups, and
SLG1
/UI2/FLP_CONTCHECK to validate that content references aren’t broken.
Why can't a user see a Fiori app tile that should be assigned to them?
This is almost always a role assignment issue, not a Launchpad bug — confirm the catalog/group is correctly added to their PFCG role, then
check SU53 for authorization failures.
What tcode do I use to activate an OData service for a Fiori app?
/IWFND/MAINT_SERVICE on the Gateway/frontend system, alongside
/IWBEP/REG_SERVICE if the service needs to be registered in the
backend first.
Is there one universal tcode for the Fiori Launchpad
No —/UI2/FLP opens the Launchpad itself, but configuration, content management, and troubleshooting are each handled by different,
purpose-specific tcodes covered throughout this guide.
Do these tcodes work the same in S/4HANA Cloud as On-Premise?
Not entirely. S/4HANA Cloud is shifting toward the Spaces & Pages model, where more configuration happens through Fiori apps themselves
rather than pure backend tcodes.
What's the difference between /IWFND/ERROR_LOG and /IWBEP/ERROR_LOG?
/IWFND/ERROR_LOG shows errors at the Gateway (frontend) layer;
/IWBEP/ERROR_LOG shows errors one layer deeper, in the backend service
itself. Checking both helps isolate where a failure is actually occurring.
Can end users access any of these tcodes?
No ,these are administrative/technical transactions used by Basis teams, technical consultants, and developers. End users interact only with
the Fiori apps themselves
What tcode do I use to clear the Fiori cache after making changes?
/UI2/CACHE_DEL is the primary tcode for clearing specific UI2 cache entries after catalog, group, or tile changes.
Where can I find which Fiori apps exist before configuring tiles for them?
Check the Fiori Apps Library first to confirm the app exists and is available for your SAP version, before building out its Launchpad tile and role
assignment.
15. Related resources
SAP Fiori Launchpad TCode: Complete Reference List
SAP Fiori Launchpad TCode: Complete Reference List
SAP Fiori Launchpad TCode: Complete Reference List
Found a process the standard library doesn't cover?
Our SAP Fiori team can help evaluate the gap and determine whether extensibility or custom development is the right approach.