SAP Fiori App Troubleshooter
A Fiori app depends on a chain of settings across two servers: the user’s role, the catalog, the target mapping, the deployed app, the OData service, its ICF node and the authorizations behind it. When something breaks, the symptom tells you which end of the chain to start from. Pick what you see, paste the error if you have one, and get the checks in the order that finds the cause fastest.
What do you see?
Optional: paste the launchpad message, the failing request from the browser’s network tab, or the /IWFND/ERROR_LOG entry.
Two servers, one app
In most landscapes the launchpad and the UI5 app live on a front-end server (or the embedded hub), while the data comes from the backend through the Gateway. Roles, catalogs, target mappings and service activation are front-end settings; business authorizations and the service implementation are backend. A 403 can come from either side, which is why an authorization trace on both is quicker than adding roles until it works.
Tile missing versus could not open
A missing tile is a content problem: the role does not carry the catalog, or no group or page shows the tile. “Could not open app” is a navigation problem: the tile is there but the semantic object and action do not resolve to a target mapping the user is allowed to use. /UI2/FLIA (launchpad intent analysis) answers the second question for a specific user in one screen, so start there before opening the catalog.
When the fix does not show
The launchpad caches aggressively: the app index on the server, the launchpad caches, and the browser. After a deployment, recalculate the app index for that app, invalidate the launchpad caches if content changed, and test in a private window before telling the user to clear anything.
Related tools
For an OData call that fails, build and test the URL with the OData query builder. For an authorization failure in the backend, the authorization error decoder turns SU53 output into a role request.
Transaction names reflect standard S/4HANA and Gateway releases; spaces, pages and some launchpad tools differ by release. ERPClimb is an independent educational platform and is not affiliated with SAP SE.