If you’re an SAP Basis administrator moving to S/4HANA, here’s something you’ll discover quickly: Fiori isn’t optional anymore. SAP S/4HANA ships with Fiori as the primary user interface. SAP GUI still works — but all new features, analytics, and innovations are built for the Fiori launchpad. Your users will expect it. Your project team will demand it. And your Basis team needs to know how to set it up, configure it, and keep it running.
This SAP Fiori administration guide covers everything a Basis administrator needs — from deployment options and initial setup to role management, troubleshooting, and daily operations. Let’s dive in.
• ECC to S/4HANA Conversion — Complete Roadmap
• SAP Cloud ALM: Unlocking Cloud Solutions
• Architecting SAP on AWS
• SAP Security Audit Checklist
• SAP HANA DBA Calculations Guide
Table of Contents
1️⃣ Fiori Deployment Options: Embedded vs. Hub
The first decision your Basis team makes: how to deploy Fiori. You have two options:
| Feature | Embedded Deployment ✅ (Recommended) | Hub / Standalone Deployment |
|---|---|---|
| Architecture | Fiori front-end runs on the same server as S/4HANA | Separate Fiori front-end server(s) |
| Complexity | Low — simpler setup, fewer components | High — multiple systems, RFCs, load balancing |
| Performance | Better — no network hop between front-end and back-end | Depends on network latency between servers |
| SAP’s Direction | ✅ Strategic — SAP recommends embedded for all new implementations | ❌ Legacy — SAP Fiori front-end server 2023 was the last standalone version |
| Use Case | New S/4HANA implementations, most customers | Existing hub deployments, complex landscapes with multiple back-ends |
Bottom line for Basis teams in 2026: Choose embedded deployment for new implementations. If you already have a hub deployment, plan the migration to embedded — SAP has published a detailed Moving from Standalone to Embedded Deployment guide (version 3.0, March 2026) to help.
2️⃣ Initial Setup — Step by Step
For embedded deployment (recommended), SAP provides automated task lists that handle most of the configuration. Here’s the workflow:
Step 1: Run Task List SAP_GW_FIORI_ERP_ONE_CLNT_SETUP
This is your one-stop task list for embedded Fiori setup. In transaction STC01, create a task list run for SAP_GW_FIORI_ERP_ONE_CLNT_SETUP. It will automatically:
- Configure SAP Gateway (activate OData services, set system aliases)
- Initialize the Fiori Launchpad (ICF services, spaces/pages configuration)
- Schedule the OData cache update job
- Generate Fiori Foundation roles (
Z_FIORI_FOUNDATION_ADMIN,Z_FIORI_FOUNDATION_USER)
Step 2: Configure SAP Web Dispatcher
The task list includes a step for Web Dispatcher configuration. Ensure your SAP Web Dispatcher routes /sap/bc/ui2/flp requests to the correct backend. Use transaction SMICM to verify HTTP connectivity.
Step 3: Verify the Launchpad
Access the launchpad URL: https://<host>:<port>/sap/bc/ui2/flp?sap-client=XXX&sap-language=EN. Log in with a user assigned to the Z_FIORI_FOUNDATION_ADMIN role. If the launchpad loads without errors, your basic setup is complete.
Step 4: Activate Business-Specific Fiori Content
After the foundation is ready, use task list SAP_FIORI_CONTENT_ACTIVATION to activate business roles and Fiori apps for your scope. This generates PFCG roles based on SAP Best Practices templates.
3️⃣ PFCG Role & Authorization Management
Fiori authorization management is different from traditional SAP GUI role administration. Here’s what you need to know:
Key Concepts
- Technical Catalogs — Contain app definitions (tiles, target mappings). Created via /UI2/FLPD (Launchpad Designer) or Manage Launchpad Apps.
- Business Catalogs — References to technical catalogs, assigned to roles. Managed via Launchpad Content Manager (FLPCM).
- Spaces & Pages — The modern layout approach (SAP_UI 7.55+). Spaces are assigned to roles, pages go inside spaces.
Creating a Fiori Role
- Transaction PFCG → Create a new role (e.g.,
Z_FIORI_MATERIAL_MANAGER) - Menu tab → Add → SAP Fiori → Launchpad Catalog → Select your business catalog (e.g.,
SAP_MM_BC_BUYER_PROCUREMENT) - To use Spaces: Menu tab → Add → SAP Fiori → Spaces → Select your space
- Authorizations tab → Generate → Check and save profile
- User tab → Assign your test user
- Assign the composite role containing both the Fiori-specific role and any backend authorization roles
Critical SAP Note for Composite Roles
SAP Note 2538787: Catalogs assigned in composite roles are NOT visible to end users. Always assign catalogs at the single role level, not the composite role level. Use composite roles only for mass user assignment.
4️⃣ Essential Transaction Codes for Fiori Administration
| TCode | Purpose |
|---|---|
| /UI2/FLP_CUS_CONF | Central Launchpad Configuration — set global parameters (search scope, system info bar, app finder visibility) |
| /UI2/FLPD | Launchpad Designer — manage tiles, target mappings, technical catalogs |
| FLPCM (/UI2/FLPCM) | Launchpad Content Manager — manage business catalogs, assign to roles |
| /IWFND/MAINT_SERVICE | Activate and maintain OData services for Fiori apps |
| SICF | Activate/deactivate ICF services for Fiori and Gateway |
| STC01 | Execute Fiori setup task lists |
| SM30 with view /UI2/FLP_CUS_CONF | Maintain launchpad configuration via table maintenance |
| /IWFND/ERROR_LOG | View Gateway error logs — the first place to check when Fiori apps fail |
| /IWFND/TRACES | Enable detailed OData traces for troubleshooting |
| PFCG | Role maintenance — assign catalogs, spaces, authorizations |
| SU01 | User administration — assign Fiori roles to users |
5️⃣ Launchpad Configuration Parameters
Transaction /UI2/FLP_CUS_CONF is your control center for launchpad behavior. Here are the parameters I find myself setting most often:
| Parameter | Description | Recommended Value |
|---|---|---|
APPFINDER_EASYACCESSMENU |
Show/hide SAP GUI menu in launchpad | false (hide it — you want users in Fiori) |
SYS_INFO_BAR |
Show system information bar | true (especially useful in multi-system landscapes) |
SYS_INFO_BAR_COLOR |
Color of the system bar | Use different colors per system (e.g., yellow for QA, red for PROD) |
SYS_INFO_BAR_MAIN_TEXT |
Primary text in system bar | e.g., “PRODUCTION — Do Not Test” |
DEFAULT_SEARCH_SCOPE_APPS |
Default search in launchpad | true (search apps by default) |
UI5FLEX_ENABLE_VARIANTS |
Allow users to create public/private variants | true (but monitor storage growth) |
NAVIGATION_HOMETARGET |
Logo button behavior | Set to return to the last viewed page |
6️⃣ Troubleshooting Common Fiori Issues
🚩 Launchpad Loads But No Apps Appear
Most likely cause: missing role assignment. Check: Is the user assigned to a role with business catalogs? Does the role have the correct SAP_UI2_USER_750 and /UI2/FIORI_CATALOGS_READ authorization? Verify via SU01 → Roles → Check PFCG authorization generation.
🚩 App Returns “500 Internal Server Error”
Check /IWFND/ERROR_LOG for the OData error. Common causes: deactivated ICF service, missing OData service activation, or an RFC connection issue between front-end and back-end. Fix the specific error and re-test.
🚩 User Menu Shows SAP GUI Instead of Fiori
The user is likely assigned to a role with SAP GUI transactions in the menu but no Fiori catalogs. Either add Fiori catalogs to the role or hide the User Menu globally via APPFINDER_EASYACCESSMENU_USERMENU = false in /UI2/FLP_CUS_CONF.
🚩 Launchpad Returns “404 Not Found”
Check SICF — the service node /sap/bc/ui2/flp must be active. Also verify the SAP Web Dispatcher configuration if you’re using one.
🚩 Fiori Apps Are Slow
Check: OData cache freshness (run /UI5/SCHEDULE_JOB_UPDATE_CACHE or schedule it periodically), SAP Gateway work process load (SM50), and network latency between front-end and back-end. In embedded deployment, the last one isn’t an issue — another reason to prefer it.
7️⃣ Daily Operations & Housekeeping
- Monitor OData cache — Schedule job
/UI5/UPDATE_CACHE_JOBto refresh the Fiori cache periodically. Stale cache = users seeing outdated tiles - Check Gateway error logs — Weekly review of /IWFND/ERROR_LOG for recurring OData errors
- Manage spaces and pages — Use the Manage Launchpad Spaces and Manage Launchpad Pages apps (available since SAP_UI 7.55) for flexible layout management
- Transport Fiori content — Use transaction /UI2/FLP_SYNC for transporting launchpad configurations between systems. Do NOT manually recreate configurations in each system — always transport
- Monitor Fiori app usage — Transaction /UI2/FLCNT shows app usage statistics to help you understand which apps are being used and which can be retired
Conclusion
Fiori administration is now a core competency for SAP Basis teams. The good news? SAP has done the heavy lifting with automated task lists — SAP_GW_FIORI_ERP_ONE_CLNT_SETUP handles most of the initial configuration. Your job as a Basis admin is to understand the architecture choices (embedded vs. hub), manage PFCG roles correctly, configure the launchpad for your organization’s needs, and keep it running smoothly.
Start with the task list, verify with a test user, and expand from there. The most common mistakes I see: assigning catalogs at the composite role level (use single roles!), not scheduling the OData cache job, and skipping the system info bar (which leads to users working in the wrong system). Avoid those and your Fiori launchpad will serve your organization well.
Have a Fiori administration challenge I didn’t cover? Drop a comment below. And if you’re also managing the transition to SAP Cloud ALM, check out that guide too — your Basis toolkit in 2026 is Fiori + Cloud ALM + HANA. Get all three right and you’re set.
