/UI2/FLP — Start the SAP Fiori Launchpad
/UI2/FLP starts the SAP Fiori launchpad from SAP GUI, opening the browser with the launchpad URL of the front-end server for the logged-on user. It is a quick way to check what a user sees, which tiles and spaces they have, and whether the launchpad itself loads before investigating individual apps.
Opens the SAP Fiori launchpad in a browser from SAP GUI for the current user and system.
Published 31 Oct 2026· 457 words
What /UI2/FLP is for
Users and consultants often need to switch from SAP GUI to the Fiori launchpad. Instead of typing the URL, /UI2/FLP opens it directly with the system's configured host, port and client. For support teams it is the first step in reproducing a launchpad problem in the same system and client the user works in.
When it is used
It is used during Fiori rollouts, in testing, and in support when users report missing tiles or apps that do not start. Basis teams use it to verify that the launchpad service and ICF nodes respond after a system copy, upgrade or certificate change.
How it is used in practice
Run /UI2/FLP in the front-end server or embedded system. The browser opens the launchpad, using single sign-on where configured. If it fails, the browser message usually points to ICF services, certificates or SSO configuration. Compare what you see with the user's roles and the spaces and pages assigned to them.
Fields and objects that matter
- System and client of the SAP GUI session, which determine the launchpad opened
- ICF services for the launchpad, which must be active
- Spaces, pages and catalogs assigned through the user's roles
- Browser and SSO settings that affect login
How to prove it in the data
If the launchpad opens for a support user but not for the affected user, compare their PFCG roles and the spaces assigned. If it fails for everyone, check the ICF nodes in SICF and the ICM status in SMICM. Errors on loading data inside apps point to OData services and the Gateway error log instead.
ECC vs S/4HANA
Used in S/4HANA on-premise and private cloud systems with the embedded or hub front-end deployment. In SAP S/4HANA Cloud public edition and SAP Build Work Zone, users reach the launchpad by URL instead.
Common pitfalls and how they show up
Launchpad problems are often environment problems mistaken for app problems.
- Testing with an administrator user who sees far more than the business user
- Inactive ICF services after a system copy
- Expired certificates causing browser warnings or failed logins
- Browser cache showing an outdated launchpad after changes
- Opening the launchpad in the wrong client, where content and roles differ
Whose problem this is
Shared between Basis, which owns ICF services, certificates and single sign-on, and the Fiori or security team, which owns launchpad content and roles. Functional teams decide which apps each business role should see, and help desks use the transaction to reproduce user reports.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Learn this properly
Lessons and topics
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ui2-flpERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.