/UI5/APP_INDEX_CALCULATE — Calculate the SAPUI5 Application Index

UI5 apps deployed to the ABAP repository are registered in the application index so the launchpad and the UI5 runtime can resolve components and dependencies. Normally the index updates automatically, but after transports, mass deployments or errors it can be incomplete. The report recalculates it for one app, a set of apps or the whole repository.

It is used after deploying custom Fiori apps, after transport imports of UI5 repositories, after upgrades of UI5 libraries and when apps fail to load components or show a blank screen with module loading errors in the browser console. Many teams schedule it as a background job to run regularly.

Run it for the specific repository of the app first; a full recalculation takes longer and is better scheduled at night. Check the log for errors, such as manifest problems or missing dependencies, which also need fixing in the app. Afterwards, clear browser caches and, if needed, the launchpad caches, then reload the app. If the problem remains, examine the browser console for component load errors.

Before the run, the browser console shows a failure to load the component or an older version. After recalculation and cache cleanup, the app loads its current version. The index entries can be checked with the related display reports for the repository.

Relevant for ABAP front-end servers in S/4HANA on-premise and private cloud, whether the front end is embedded or a separate hub. Apps deployed to SAP BTP HTML5 repositories are not registered in this index and follow their own deployment and caching rules.

Index problems imitate many other errors.

Owned by Basis or the Fiori operations team, which schedules the recalculation and checks its log. Developers request a targeted run after deployments, and the release checklist should include it so blank screens after transports do not become tickets.