Fiori Launchpad Part 4: Troubleshooting Missing Tiles and Apps That Don't Start

📌 KEY POINTS
✅ Tile not visible: check role assignment, catalog content and space/page assignment.
✅ 'Could not open app': check target mapping, parameters and the app's availability on the server.
✅ Blank screen or old version: check the UI5 app index and caches.
✅ App opens but errors on data: check OData service activation and back-end authorization.
⚠️ Clearing every cache first wastes time and hides the real cause.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
This final launchpad part gives a repeatable troubleshooting path.

━━━━━━━━━━━━━━━━━━━━
▶ 1. TILE NOT VISIBLE
Confirm the user has the PFCG role, that the role contains the catalog and the space or page, and that the tile exists in the catalog. In the launchpad, user settings or the app finder show which catalogs a user has. If the tile exists only in a technical catalog not referenced by any business catalog in the role, it won't appear.

━━━━━━━━━━━━━━━━━━━━
▶ 2. COULD NOT OPEN APP
The intent resolution failed or the target is unavailable. Check that a target mapping exists for the intent with matching parameters and device type, and that it points to an existing component. Launchpad troubleshooting tools and the browser console show the intent and the failure reason.

━━━━━━━━━━━━━━━━━━━━
▶ 3. BLANK SCREEN OR OLD VERSION
On ABAP front-end servers, deployed UI5 apps are registered in the app index; recalculating it (/UI5/APP_INDEX_CALCULATE) and invalidating caches (for example /UI2/INVALIDATE_GLOBAL_CACHES, used carefully) helps after deployments. Browser caches and cache busting also matter. The console usually shows missing resources or component load errors.

━━━━━━━━━━━━━━━━━━━━
▶ 4. DATA AND SERVICE ERRORS
If the app starts but fails when loading data, check the OData service: is it activated (for V2 /IWFND/MAINT_SERVICE, for V4 service groups in /IWFND/V4_ADMIN), are ICF nodes active, and what do /IWFND/ERROR_LOG and /IWBEP/ERROR_LOG say. Authorization failures show in SU53 on the back end.

━━━━━━━━━━━━━━━━━━━━
▶ 5. ORDER MATTERS
Follow the chain: role → catalog and page → target mapping → app resource → service → authorization. Document each ticket's cause; recurring causes such as missing navigation target mappings or unactivated services point to gaps in transport or role processes.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Reproduce a missing tile and trace role, catalog and page.
2. Break a target mapping in test and read the error and console.
3. Recalculate the app index after a deployment in test.
4. Check an OData service's activation and error logs.

✅ CHECKPOINT: you can diagnose each class of launchpad ticket with a fixed sequence of checks.

After a transport, a custom app showed the previous version for some users and a blank screen for others. The app index had not been recalculated after deployment, and some browsers cached old resources. Recalculating the index and adding it to the deployment pipeline fixed it permanently.

• Clearing all caches before diagnosis.
• Ignoring the browser console.
• Forgetting app index recalculation after deployment.
• Not checking back-end error logs.

• Fixed troubleshooting sequence.
• Use console and launchpad diagnostics.
• Automate app index updates in deployment.
• Document recurring causes.

Interviewers love 'the tile is not visible' or 'could not open app' questions — answer with a clear sequence from role to service.