- SAP Managed Tags:
One is asked to identifiy a certain app running in the Fiori Launchpad, e.g. to identify a relevant support component or explain to technical person which application is exhibiting a specific issue.
As an example, we consider the following applicaiton, which happens to be displayed in portuguese.
As SAP does not publish all information in portugese, the app title may not be of use here.
(And I unfortuatly don't understand portugese 😞 ).
However, this article will give you several ways to collect technical information about the application:
| Property namne | Value in this example | comment |
|---|---|---|
| Application Intent | Customer-manageLineItems (potentially including paramters like ?CUstId=4711 | Note: The intent is the semantic name of the operation. This intent may be mapped to different applications depending on parameters and business context. SAP or a customer installation may remap it to a different application in a specific installation depending on version etc.. Thus make sure to also collect other information. |
| BSP Path | /sap/bc/ui5_ui5/sap/fin_cust_lits | The path where the main Javascript resource comprising the application (Component-preload.js) is located. |
| BSP Name FIN | fin_cust_lits | The BSP (Business Server Page) name of the application, where you can find the resources in SE80. Note that the name is the same as the path segment of the BSP path. |
| Javascript package name | fin.ar.lineitems.display | The Javascript name of the application code. This is typically internally and (apart from web-searches) there is no easy way to locate the application code from this in the BSP. |
| Catalog | SAP_SFIN_BC_AR_DOCUMENT | Note, for a given user, the intent may appear in more than one catalog. Also, an application may be targeted by multiple intents. (E.g. the same javascript code may serve different business operations). |
| tmChipId | 00O2TPKTQNBJCE64H43FKG4Z1 | Target mapping in FLPD (not of general interest, may differ in systems). |
Now let's collect this information:
The application Intent from the URL
Inspecting the URL displayed above the appliction gives the first technical key, the part after the # is called the "Intent". This is the "semantic name" of the Application.
Here:
#Customer-manageLineItems
Note that sometime the intent is followed by business paramters, Make sure to copy the full intent with parameters, as sometimes the started application depends on the paramter signature.
Component name from Info Dialogue
The technical name of the component is displayed in the info dialogue:
Determine BSP Path and package from Network trace content of Component-preload.js
The BSP path, and thus the BSP name can be determined from the network trace.
Open the developer tools (press F12), record the network trace ,refresh the page and filter for the Component-preload loaded.
(typcially the first Component-preload.js,
The path of this file gives you the bsp name,
Inspecting the content gives you an alternative way to determine the javascript pacakge name.
Determine bsp path, Catalog name and javascript name from Intent and start_up request
(Fiori 1.32+, TargetMappings request before)
Here another method to determine the BSP path, name and package name.
(This also works if the application does not come up, as this request is fired early independent of the application).
Searching for the intent:
BSP name -> fin_cust_lists
applicationData -> fin.ar.lineitems.display
Catalog -> SAP_SFIN_BC_AR_DOCUMENT
tmChipID ( Target Mapping ID),
Determine official name and support component from technical information
No we have collected a number of technical information.
Using the search engine of your choice,
- Documentation
- Fiori Apps Library
Under support component you will find the associated support component.
Related articles
Understanding launchpad object relationship with screenshots
1 Comment
