/UI2/FLIA
/UI2/FLIA is the transaction for Fiori Launchpad Intent Analysis, an SAP Fiori Launchpad support report that shows, for a given intent, device type and user, which authorization roles and catalogs carry the intent and which tile and target mapping belong to it. /UI2/FLIA is the first check when a tile is visible but navigation fails.
Quick facts
- Type
- Launchpad support report, started as a transaction
- Layer
- Content, navigation & access
- Full name
- Fiori Launchpad Intent Analysis
- Inputs
- Intent, form factor, user, adaptation layer, optional package
- Shows
- Roles, catalogs, tile and target mapping IDs, system alias per intent
- Who uses it
- Launchpad administrators, basis and security teams, SAP Fiori support
- Applies to
- SAP S/4HANA on-premise and Private Edition (ABAP-based launchpad)
Layer: Content, navigation & accessWhere it sits ▾
Layer: Content, navigation & access
Open the architecture map →What does /UI2/FLIA do?
/UI2/FLIA answers one question: can this user resolve this intent on this device, and through which content? For a semantic object and action, such as PurchaseOrder-display, the report lists:
- the authorization roles whose catalogs contain the intent, and whether the user is assigned to them;
- the catalogs, tiles and target mappings involved, with their IDs;
- the target system alias, plus reference IDs for referenced content.
The check is system-dependent: run it in the ABAP system whose launchpad content you want to verify. /UI2/FLIA reads the content the launchpad would use; it does not change anything.
When should you use /UI2/FLIA?
Use /UI2/FLIA when you already know the failing intent:
- a tile is visible, but clicking it shows an error or opens the wrong app;
- an in-app link is missing for one user but present for another;
- the app works on desktop and fails on a phone;
- the UI2 application log reports a navigation link resolution error; its details open /UI2/FLIA.
Do not start there when the tile is missing or the app opens without data; those are catalog or OData problems. SAP documents /UI2/FLIA for the ABAP-based launchpad; for SAP S/4HANA Cloud Public Edition, check the SAP Help Portal for the support options of your release. /UI2/FLIA is a navigation diagnostic, not a general launchpad health check.
How do you use /UI2/FLIA step by step?
A buyer at Alder Manufacturing reports that the purchase order tile fails on her phone:
- Start /UI2/FLIA in the system that holds the launchpad content.
- Enter the intent, here PurchaseOrder-display, and the form factor, here Phone.
- Enter the user and select Restrict to assigned roles to see only her roles.
- Choose the adaptation layer: Configuration (delivered), Customization (client-specific, can overwrite delivered content) or Personalization (user-specific).
- Optionally limit the check to a development package.
- Run the report and filter the result list.
- Copy the tile or target mapping ID, open the catalog in /UI2/FLPCM_CUST and jump to the tool that created the object.
Comparing results with and without the user restriction usually pinpoints the gap in /UI2/FLIA.
What do common /UI2/FLIA results mean?
| Result | Likely cause | Fix |
|---|---|---|
| No entry for the intent at all | Intent misspelled or not defined | Correct the intent or create its target mapping |
| Entries exist, none with the user restriction | The catalog is in no role assigned to the user | Add the business catalog to the user's role |
| Entries for Desktop, none for Phone | Target mapping not enabled for that form factor | Enable the device type or add a phone target |
| Customization differs from Configuration | Client-specific content overwrites delivered content | Review the customized object |
| Correct target, wrong system alias | Alias or destination misconfigured | Check with /UI2/FSAC |
If the target mapping is consistent and the app still fails to load, check the SAPUI5 application index log with /UI5/APP_INDEX_CALCULATE. /UI2/FLIA results separate role problems from content problems.
Which related transactions help?
- /UI2/LOG or SLG1: the UI2 application log; a log ID from the browser console finds the entry.
- /UI2/FLC: consistency checks for delivered and customized launchpad content; deprecated from ABAP platform 2025 in favor of the content manager issues view and /UI2/FLPCA.
- /UI2/FSAC: checks system aliases and their RFC and HTTP destinations; these checks also appear in /UI2/FLIA.
- /UI2/FLPCM_CUST: the launchpad content manager, for catalogs and references.
- /UI2/FLPAM: the launchpad app manager, for original tiles and target mappings.
- /UI5/APP_INDEX_CALCULATE: the SAPUI5 application index and its logs.
/UI2/FLIA locates the gap; these tools confirm and fix it.
/UI2/FLIA vs. /UI2/FLC: what is the difference?
| /UI2/FLIA | /UI2/FLC | |
|---|---|---|
| Full name | Fiori Launchpad Intent Analysis | Fiori Launchpad Checks |
| Scope | One intent, per user and form factor | Launchpad content as a whole |
| Question it answers | Why does this navigation fail for this user? | Is the delivered and customized content consistent? |
| Typical use | Reactive, after a user report | Preventive, after content changes or upgrades |
| Status | Current tool | Deprecated from ABAP platform 2025; successors are /UI2/FLPCA and the content manager issues view |
/UI2/FLIA diagnoses one failing intent; /UI2/FLC checks the content that every intent depends on.
FAQ
Is /UI2/FLIA a transaction or a report?
Both. SAP documents Fiori Launchpad Intent Analysis as a report that you start with the transaction code /UI2/FLIA. The report only reads launchpad content and role assignments, so running it changes no configuration.
Why does /UI2/FLIA show the intent but the user still cannot navigate?
Run it again with the user name and Restrict to assigned roles selected. If the intent appears only without the restriction, the catalog is in a role the user does not hold. If it appears with the restriction, compare the form factor and the system alias of the target mapping.
What is the adaptation layer in /UI2/FLIA?
The adaptation layer selects the content level to analyze: Configuration for delivered, client-independent content; Customization for client-specific content; Personalization for user-specific content. Comparing layers shows whether customized content overwrites what SAP delivered.
Does /UI2/FLIA work for SAP Build Work Zone?
Only for content from the ABAP system. When SAP S/4HANA launchpad content is federated into a SAP Build Work Zone site, run /UI2/FLIA in the back end. For apps deployed on SAP BTP, check the inbounds in the app descriptor instead.
Sources
- SAP Help Portal: Analyzing Intents for SAP Fiori Launchpad (/UI2/FLIA)
- SAP Help Portal: Determining Target Mappings for an Intent
- SAP Help Portal: Launchpad content checks (/UI2/FLC check list and deprecation note)
- SAP Help Portal: Launchpad Support Tools
- SAP Help Portal: Issues with Navigation (SAP Fiori launchpad troubleshooting)
- Applies to
- SAP S/4HANA on-premise · SAP S/4HANA Cloud Private Edition
- Last reviewed