Downtime Announcement: Please note the SAP Community Wiki will be unavailable due to a system upgrade on Thursday, September 24th between 6 and 7 AM CEST
Skip to end of metadata
Go to start of metadata

Purpose

This WIKI page lists common issues related to SAPUI5 Application Index and helps you to resolve them. This applies to S/4HANA Cloud (ABAP) and S/4HANA on-premise (ABAP).

Overview

In this WIKI you will find all the steps needed in order to troubleshoot or fix a known SAPUI5 Application Index (ABAP) issues.

Cannot Load Tile

  1. Issue ( FCLM_ANALYSIS)

    • Symptom
      Console shows following error: App fin.acc.query.analyze has errors and may not run correctly; please see SAP Note 2364579 - fin.acc.query.analyz
      Error in app dependency sap.ui.core.UIComponent: No descriptor was found - fin.acc.query.analyze
      failed to load Javascript resource: sap/ui/core/UIComponent/Component-preload.js - sap.ui.ModuleSystem
      error in App pop-up:
      Application 0FCLM_ANALYSIS could not be loaded
      Could not instantiate planning service "".
      error ],"Error":,"ErrorDetails":[]}
      Runtime error CALL_FUNCTION_NOT_FOUND has occurred

    • Solution
      Implement SAP Note: 2700065 - Tile for Cash Flow Detailed Analysis is not loading

  2. After transport from dev to quality system application still has old code
    • Reason
      Customer used transaction SE80 directly to modify and transport a single file.

    • Solution
      Follow this KBA 2696956 - Launchpad still using old version of UI5 after transporting new code to product.
      SAP recommends using the SAP WebIDE to create/maintain Fiori artifacts. Using SE80 for this is not supported.

  3. Issue Smart Business tile cannot load - 1
    • Symptom
      Console shows following error: Cannot read property 'indexOf' of undefined

    • Solution

      1. Follow this KBA:  2713719 – Smart Business KPI Tile is hanging during loading
      2. Note: A workbench request must be transported from client to a client even in the same system when it comes to Smart Business application
      3. See also:  KBA 2732972 - How to Transport KPI Tile Application Step-by-Step Guide
      4. See also: KBA 2662463  - KPI activation fails when transport request is used


  4. Issue Smart Business tile cannot load - 2

    • Symptom
      1. Failed to load tile after configuring a numeric KPI tile.
      2. Error: No Vocabulary Annotation File found for ID xxx Version xx 
      3. "Failed to initialize" message when launching KPI tile 
      4. "Metadata or annotation document load failed" message displayed in console 
      5. EntitySet is not displayed

    • Solution
      1. To resolve this issue, please follow this KBA: 2536551 - KPI tile failed to load after configuring a numeric KPI tile

  5. Issue Smart Business tile cannot load - 3
    • Symptom
      1. Smart Business Tiles 'Cannot Load Tile' randomly after configuring Fiori launchpad to display Smart Business tiles

    • Solution
      1.  The following KBA,  2779630 - Smart Business tiles showing cannot load tile randomly, needs to be followed.

  6. Issue HTTP Status Code 403 - cannot load - 4
    • Symptom
      • After upgrade several fiori apps of an application cannot be launched in the Fiori Launchpad. The error received is: App could not be opened because the SAP UI5 component of the application could not be loaded. Look at the http trace. If there are requests with http status code 403 unauthorized this may be an indication that the ICF node is not active.
    • Solution
      • Call trx SICF and activate the corresponding node. The name of the ICF node is part of the URL.
      • UI5 app: .../sap/bc/ui5_ui5/<namespace or 'sap'>/<bsp app name> The ICF node is either <bsp app name> or <namespace>/<bsp app name>
      • OData service: .../sap/opu/odata/<namespace>/<odata service name> The ICF node is <odata service name> or <namespace>/<odata service name 

Cannot Load App

    1. Cannot load app - 1
      1. Symptom
        User has created a KPI tile with the KI Modeler. However the tile cannot be loaded in the Fiori Lauchpad. The Startup service shows following error for target mapping xxxxxxxxKPI-display~64wp
        "Error in app component customer.kxxx: No descriptor was found"

      2. Reason
        Execute report /UIF/GET_FILES_4_NS and specify in field 'Namespace' customer.kxxx. The app variant does not exist in the system.

      3. Solution
        Refer to “Smart Business tile cannot load” In this WIKI above.

    2. Cannot load app  - 2

      1. Symptom
        Fiori app "Inspection app" is not working properly, and shows error message -  Could not open app. Please try again later. Console error msg - Failed to resolve navigation target: "#XXXXXX-display". This is most likely caused by an incorrect SAP Fiori launchpad content configuration or by missing role assignment. - Could not resolve navigation target sap.ushell.renderers.fiori2.Shell.controller

      2. Solution
        BSP application <APP> has a dependency to <APP> component and this dependency cannot be found. This can happen if either the required component or library is not deployed to the system or the name of the component is misspelled. 
        1. To check this run a TA sui_support in the target system and run the report 'Check of SAP NetWeaver Infrastructure for SAPUI5 Apps'. (Support for UI Technology ->SAPUI5 -> System Checks -> Check of SAP NetWeaver Infrastructure for SAPUI5 Apps)
        2. After executing this report, press Show As Text and search for your BSP application name '<APP>'. => SAPUI5 library/component <COMPONENT> used in application <APP> does not exist.

    3. Cannot load app – 3
      1. Symptoms
        SAPUI5 App cannot be loaded 

      2. Reason
        App cannot be loaded beca
        use the main component sap.<comp> cannot be also loaded. This is because 
        one of its sub-component sap.<comp>.<sub-comp> cannot be loaded.App cannot be loaded because component <COMPONENT> cannot be loaded .
        The main component is <COMPONENT> which embeds among their sub-component
        COMPONENT>. This sub-component embeds component <COMPONENT>.
        The startup service does not return <COMPONENT>

      3. Solution
        BSP <BSP-APPLICATION> is constructed as an app and not as a library user has to remove "sap.app": { "embeddedBy": "../"} from the embedded component.
        Specifics for the Manifest of "reuse" Components
        "Reuse" Components embedded by a library must have an explicit entry in the manifest underneath the section sap.app/embeddedBy:
        "sap.app": {
        "embeddedBy": "../"
        }
        The embeddedBy should be the relative path to the namespace root of the library. This would allow that tooling like the AppIndex can discover embedded libraries and will not include them into the transitive scope which could cause unwanted 404 requests. Additionally, user should declare a library dependency to the embedding library. This will ensure that the library containing the Component preload will be loaded automatically instead of the try to load the Component preload by itself

    4. Cannot load app - 4
      1. Symptom
        User has created a KPI tile with the KI Modeler. However the tile cannot be loaded in the Fiori Lauchpad. The Startup service shows following error for target mapping xxxxxxxxKPI-display~64wp
        "Error in app component customer.kxxx: No descriptor was found"

      2. Reason
        Execute report /UIF/GET_FILES_4_NS and specify in field 'Namespace' customer.kxxx. The app variant does not exist in the system.

      3. Solution
        Refer to Smart Business tile cannot load In this WIKI above.

    5. Cannot load app - 5
      1. Symptom
        Fiori app "Inspection app" is not working properly, and shows error message - Could not open app. Please try again later. Console error msg - Failed to resolve navigation target: "#XXXXXX-display". This is most likely caused by an incorrect SAP Fiori launchpad content configuration or by missing role assignment. - Could not resolve navigation target sap.ushell.renderers.fiori2.Shell.controller

      2. Solution
        BSP application <APP> has a dependency to <APP> component and this dependency cannot be found. This can happen if either the required component or library is not deployed to the system or the name of the component is misspelled.
        1. To check this run a TA sui_support in the target system and run the report 'Check of SAP NetWeaver Infrastructure for SAPUI5 Apps'. (Support for UI Technology ->SAPUI5 -> System Checks -> Check of SAP NetWeaver Infrastructure for SAPUI5 Apps)
        2. After executing this report, press Show As Text and search for your BSP application name '<APP>'. => SAPUI5 library/component <COMPONENT> used in application <APP> does not exist.

    6. Cannot load app - 6
      1. Symptoms
        SAPUI5 App cannot be loaded

      2. Reason
        App cannot be loaded beca use the main component sap.<comp> cannot be also loaded. This is because
        one of its sub-component sap.<comp>.<sub-comp> cannot be loaded.App cannot be loaded because component <COMPONENT> cannot be loaded .
        The main component is <COMPONENT> which embeds among their sub-component
        COMPONENT>. This sub-component embeds component <COMPONENT>.
        The startup service does not return <COMPONENT>

      3. Solution
        BSP <BSP-APPLICATION> is constructed as an app and not as a library user has to remove "sap.app": { "embeddedBy": "../"} from the embedded component.
        Specifics for the Manifest of "reuse" Components
        "Reuse" Components embedded by a library must have an explicit entry in the manifest underneath the section sap.app/embeddedBy:
        "sap.app": {
        "embeddedBy": "../"
        }
        The embeddedBy should be the relative path to the namespace root of the library. This would allow that tooling like the AppIndex can discover embedded libraries and will not include them into the transitive scope which could cause unwanted 404 requests. Additionally, user should declare a library dependency to the embedding library. This will ensure that the library containing the Component preload will be loaded automatically instead of the try to load the Component preload by itself
    7. Cannot load app - 7
      1. Symptoms
        Application with intent #<SEMANTICOBJ-ACTION> cannot be opened. 

      2. Reason
        To debug or trace this issue,
        a. Create an HTTP trace. 
        b. Look for the Startup request: GET /sap/bc/ui2/start_up?so=*&action=*&shellType=FLP&depth=0
        Find out how many target mappings matching the navigation intent. Here is an example if what was found in this situation

        LeaveRequest-approve~XX is assigned to an inexistent SAPUI5 component, "applicationData": "SAPUI5.Component=leave".

        Further the SAP UI5 application index complains that application leave has errors: "applicationDependencies": "{\"name\":\"leave\",\"self\":{\"name\":\"leave\"},\"messages\":[{\"severity\":\"error\",\"text\":\"App leave has errors and may not run correctly; please see SAP Note 2364579\"},{\"severity\":\"error\",\"text\":\"Error in app component leave: No descriptor was found\"}]}".

        It is contained in business catalog SAP_HR_BC_EMPLOYEE_T.

        The Fiori Launchpad runtime selected the erroneous target mapping which you can also see at the bottom of the trace:

        - GET /sap/bc/ui5_ui5/ui2/ushell/resources/~xxxxxxxxxx~/leave/Component-preload.js HTTP/1.1  -> HTTP code 404

        - GET /sap/bc/ui5_ui5/ui2/ushell/resources/~xxxxxxx~/leave/Component.js HTTP/1.1  -> HTTP code 404


        It attempted to read component 'leave' which does not exist

      3. Solution
        Please follow the following KBA, 2803677 - Cannot load application leave has errors and may not run correctly, to address this issue.

    8. Cannot load app - 8

      • Symptom
        • When clicking on app Sales Contract Fulfillment Rates you receive error dialog App could not be opened because the SAP UI5 component of the application could not be loaded. Pressing the 'i' button there is some more information: Failed to load UI5 component for navigation intent "#SalesContract-analyzeSBKPIDetailsS4HANA?EvaluationId=.E.xxxxxxxxxxxxx"
        • Looking at the console tab in the browser development tools there is following entry: The issue is most likely caused by application F1905. Please create a support incident and assign it to the support component of the respective application. - Failed to load UI5 component with properties: '{...

      • Reason
        F1905 is not a valid application. In fact it is the Fiori id. You can verify it in the Fiori Apps Library. The reason for the error is that the target mapping that is used for this UI5 app was configured wrong in the Fiori Launchpad Designer. Meaning the ID under the target mapping was set to the Fiori application library id which is not correct.

      • Solution
        For this particular case the id in the target mapping should be set to ssuite.smartbusiness.runtime.s1
        For more information on how to set this up, please follow up this KBA: https://launchpad.support.sap.com/#/notes/2864086

App Descriptor has outdated version

    1. App Descriptor is outdated - 1
      1. Symptom
        The developers made changes to the app descriptor of an app. However, when the app is run in the Fiori Launchpad the manifest does not show the latest changes.

      2. Reason
        The LOAD layer in LRep was for some reason not updated. To check do the following:
        1. Call tcode SUI_SUPPORT
        2. Click on Layered Repository
        3. Execute Check load for consistency (support only)
        4. In field 'Namespace' specify *<BSP repository in lower case>* Note:  In an S/4 Hana Cloud customer cannot go to the frontend server to call the report directly. Instead, SAP product support engineer use transaction SUI_SUPPORT to select the appropriate report.


      3. Solution Execute report /UI5/APP_INDEX_CALCULATE for that app. In an S/4 Hana Cloud system use transaction SUI_SUPPORT → SAPUI5 → Application Index → Calculation of UI5 Application Index.

    2. App Descriptor is outdated  - 2
      1. Symptom
        When calling an app a button is missing

      2. Reason
        There are several reasons why a button or some other UI element is missing

      3. Solution
        User needs to execute report /UI5/APP_INDEX_CALCULATE, please refer to this SAP Note 2364579 - SAPUI5 application index is not calculated, is outdated or contains errors

    1. App Descriptor is outdated - 3
      1. Symptom 
        After upgrade a button in an app is missing. Some changes files have the right version and others don't. The correct version is identical to the version in the manifest.json file. Regenerating the App Index for the BSP repository in question always fixes the issue. To verify this, do the following:
        1. Get the name of the BSP repository from the manifest 
        2. Call transaction SUI_SUPPORT and navigate to Layered Repository -> List repository files (Support only)
        3. In field 'Namespace' specify *<BSP repository in lower case>*, set the layer to 'Vendor'
        4. You are interested in file types 'appdescr' and change.

      2. Solution
        Executing report /UI5/APP_INDEX_CALCULATE for that app always solves it. You can also execute analysis report /UI5/ANALYSE_LEVEL0_CHANGES that shows all BSP repositories in the system for which the changes have not the same version as the manifest. The report may also be used to fix the issue.

App Index Calculate Error Message

Duplicate ID

  1. Symptom
    One of the following error message is shown in  job log of App Index Calculate:
    • Duplicate id for SAPUI5 Fiori Application when running in SAP Fiori launchpad on ABAP system

    • SAPUI5 component &1 resides in multiple (&2) repositories

    • Component &1 exists in multiple UI5 repositories
  2. Reason

The application id is used as sap.app/id in the manifest.json in multiple SAP UI5 applications. This is not permitted as the app id needs to be unique.

  1. Solution

For customer applications delete those apps, which are no longer needed (see documentation) or change app id in your app (see KBA 2177717).

For SAP delivered applications, please create or forward incident to application component, which owns this application. Search for "ach" under sap.app in manifest.json.


Wrong libraries and components

  1. Symptom

SAPUI5 library/component <component> used in application <app> does not exist


  1. Reason

A wrong library or component is referenced in the manifest.json under sap.ui5/dependencies.

  1. Solution

Verify whether the dependency is really needed and spelled correctly. There are several reasons why a dependency cannot be found. See long text of message /UI5/APP_API 021.

General SAP Note

  1. Note 2364579 - SAPUI5 application index is not calculated, is outdated or contains errors

 

 

 

  • No labels