Any issues during the calculation of the index are written as messages to the application log.
Message Type |
Classification |
What's the Issue? |
---|---|---|
Error |
Very high |
Exception because manifest.json file is not valid or cache buster token could not be calculated |
Error |
High |
Component ID occurs or is used more than once |
Warning |
Medium |
Component ID is potentially not valid |
To access the application log, choose View … Logs in the report /UI5/APP_INDEX_CALCULATE. The application log is also persisted in client 000 by default and can be analyzed using transaction SLG1.
Technically, the application log is referenced by the object /UI5/APPIDX. This object has the following subobjects:
Subobject |
What Does It Contain? |
---|---|
GENERAL |
General information like time and duration of the last calculation of the index, number of single repositories, and number of updated table entries |
UI5REP |
Error messages that occurred when a single repository was processed The external ID is the name of the single repository. |
UI5COMP |
Component-related messages from a consistency check carried out at the end of the calculation of the index The consistency check includes the following:
The external ID is the component ID. |
The application log contains only entries of the last run of the report /UI5/APP_INDEX_CALCULATE and any older entries are removed automatically. For more information, see SAP Library for SAP Business Warehouse on SAP Help Portal. Open Business Warehouse (Function-Oriented View) for SAP NetWeaver 7.4 or 7.5 and search for Analyze Logs.