Column Name | Description | Problem Resolution |
State | Rating: Green - the app has been developed and configured correctly to be used on the Fiori Launchpad Yellow - the app has been developed correctly but is not yet configured for use Red – the app has not been developed correctly or is not active | Check in SE80 if the application contains a Component.js file which includes a metadata declaration. Moreover, the ICF service of the application should be active and an active OData service should be used. |
Application Name | Technical name of the UI5 (Fiori) application | |
Transported | Application has been transported to another system | |
Development Class of Service | Name of the transport package | |
Software component | The service's software component if it can be read | |
SAP Release | Release number of the software component | |
Business Server Page Text | Application description | |
BSP ICF Service Active | Rating: Green - the app has been developed following the Fiori design guidelines and configured correctly to be used in the Fiori Launchpad Yellow - the app has been developed following the Fiori design guidelines but is not yet configured for use Red – the app has not been developed following the Fiori design guidelines or is not active | 1. Activate the ICF service 2. The app name should not start with an "/" 3. The service should reside in directory /sap/bc/ui5_ui5/sap/ |
ID/Namespace | The app's ID or namespace read from the Component.js file | |
Current Application Version | App version read from the Component.js file | |
Last changed on | Date when the file has been changed the last time | |
Last changed by | User when the file has been changed the last time | |
Index.html | “X” if the file Index.html exists, empty if not. | |
Component.js | “X” if the file Component.js exists, empty if not. | |
Component-preload.js | “X” if the app includes the file Component-preload.js, empty if not. | |
Metadata | Rating: Green – metadata is declared in the manifest.json Yellow – metadata is declared in the Component.js Red – no metadata declaration | Declare the metadata in the manifest.json file |
OData URL | URL of the application’s OData Service | |
OData ICF Service Active | Rating: Green – Odata Service is active Red – Odata Service is inactive n/a - ICF node of the OData service cannot be found | Register the OData service in transaction /IWFND/MAINT_SERVICE |
System Alias(es) | Assigned system alias(es) | |
HTTP Response Code | HTTP response code of the OData metadata call. The HTTP response codes are explained in this SAP blog. | Check if correct backend SW component is installed. Check the RFC connection, user authorizations, and ICF service activation |
Min. UI5 Version | Displays the minimum SAPUI5 version specified in the manifest.json file. A developer can also refer to the installed SAPUI5 version. You will see then “${sap.ui5.dist.” in the cell | |
Used SAPUI5 Libraries | The field shows the SAPUI5 sub libraries used by the application. | |
# .js Files | Amount of Java Script files within the application which are not one of the following: Component-preload.js, Configuration.js, Component.js or Application.js | |
# .xml Files | Amount of XML files in the application | |
# .css Files | Amount of CSS files in the application | |
Initial Created On | Date when the file has been created. | |
Initial Created By | User who created the file | |
Vendor | “Customer” when the application is a custom app. “SAP” when it is an SAP standard application |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
35 | |
25 | |
14 | |
13 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 |