Troubleshooting Tips – Integration Custom UI5 APP with SAP FIORI Launchpad

On my journey to learn integrating a custom app in FIORI launchpad, there was this one error which haunted me big time

“”Error in Configuration ””

1. i.e. The config error shown on trying to open the app from FIORI Launchpad.

And I must accede it is a painstaking task to get it working .

So I thought of penning down some common troubleshooting tricks which might help to resolve the same error :

Trick 1 : Check your FIORI Launchpad customizations

First  and Foremost , check your Catalog Definition is correct . And if you are using Semantic Object , check your Launchpad customization .Check all your customizations in LPD_CUST are good

As mentioned below

1. Application Type : URL
2. URL : /sap/bc/ui5_ui5/sap/<BSP application name>
3. Application Alias : <Specify BSP Application Name only  >
4. Additional Info : Component.js file relative path as below

     SAPUI5.Component=<relative path of Component.js file specified using jquery.sap.declare >

     e.g. SAPUI5.Component=sap.ui.demo.myFiori

     In mycomponent.js file  below is the path

jQuery.sap.declare(“sap.ui.demo.myFiori.Component”);

Trick 2 : Clear the Browser and Gateway Cache to refresh User roles

Ensure the FIORI user has the role to access the required FIORI group & catalog defined for the app .

NOTE : the Browser cache and GW cache could be a big culprit , so if your roles are not getting refreshed as desired , follow below

1. Clear your browser cache
2. Clear the Gateway Cache by running below reports for your user

     /UI2/DELETE_CACHE

     /UI2/INVALIDATE_GLOBAL_CACHES

        Trick 3 : Go to Browser Developer Tools , to look for any App related error

Check the error in your browser , press F12 if you are in chrome or go to Developer tools as shown below

Some of the common reasons here could be :

Syntax error in your bsp application

Some Library not supported

Path to the i189/messageBundle file for managing the Application texts is not as per the Component.js path

Hope this helps someone facing a similar issue .