This blog is a part of Master blog Tools to Analyze Fiori Launchpad Issues, where we looked at different tools available to analyze the issues in Fiori Launchpad and Launchpad Designer.
In this Blog, we will look at the standard tools Fiori System Alias Checks (/UI2/FSAC) and Fiori Intent Analysis (/UI2/FLIA) and Fiori Launchpad Texts (/UI2/FLT) and how to analyze the Fiori Launchpad content issue using these.
SAP has provided Transaction /UI2/FSAC to check the consistency of the System alias created for Fiori launchpad. This report displays consistency issues for the selected system alias or RFC Destination configured in SM59.
Let's see how these tools work...
Procedure:
Below is the list of checks this report performs and the corrective action for each one:
The second transaction /UI2/FLIA (Fiori Launchpad Intent Analysis) provides an overview of all the intents (semantic objects – action).
Execute the transaction /UI2/FLIA and landing page will be as shown below:
As we can see, there are multiple option to filter the content for Analysis along with Intent .
Intent: Here combination of semantic object and action need to be passed separated with “-“ (for e.g. PaymentOrder-manage)
Form Factor: To filter the content based on device type defined in configuration i.e. Desktop or Phone or Tablet)
Lets Say we want to analyze the specific Fiori app intent for which we are facing issue, for e.g EnterpriseSearchBusinessObject-manage and we want to analyze it for the roles assigned to specific user, input the details as below:
The output will list, if there are any, issues with the intent in the roles assigned to the user specified. As we can see below, the intent is assigned in 3 different roles and the issues. The error can be checked in column “Message”
In this particular case error is “invalid semantic Object” and that could mean wrong semantic object is maintained in Tile or Target mapping or semantic object is not maintained in transaction /UI2/SEMOBJ or /UI2/SEMOBJ_SAP.
Here it was missing in /UI2/SEMOBJ and /UI2/SEMOBJ_SAP and once maintained in /UI2/SEMOBJ error is gone.
This tool is used to analyze texts used in Fiori Launchpad and fix the issue related to them. This tool provides the features like:
Moving on, lets see how to check all this information in the report.
Execute Transaction /UI2/FLT and landing screen will be as shown below.
As we can see the screen is similar to the initial screen of Fiori Intent Analysis report except couple of changes like here, we have Text field instead of Intent filed and an additional filed Software component to filter the content for analysis.
Enter the filter criteria and execute the report to analyze the Text content. In this case I searched for Text “Upload General Journal Entries” and want to look for the same in roles assigned to my user.
The output list the Usage of the entered text in all the places like catalogs, Groups, TM, tiles etc. and can see in Column “Type” as shown below. All the details related to the usage of Text can be checked by selecting the record and clicking on details icon.
Click on the link in Catalog ID to navigate to the Catalog in Launchpad Designer directly from the report.
Click on the link in column “TEXT” to get the details including Text ID and Configuration ID.
This Text ID and Configuration ID will be handy to identify the text in the translation system. To know where to maintain and check Fiori Launchpad Text translations , check this blog.
So,with this , we learnt how using standard tools we can analyze the System alias, Intent related issues, or Fiori Launchpad Text content.
Keep Learning & Keep Sharing!
In this Blog, we will look at the standard tools Fiori System Alias Checks (/UI2/FSAC) and Fiori Intent Analysis (/UI2/FLIA) and Fiori Launchpad Texts (/UI2/FLT) and how to analyze the Fiori Launchpad content issue using these.
SAP has provided Transaction /UI2/FSAC to check the consistency of the System alias created for Fiori launchpad. This report displays consistency issues for the selected system alias or RFC Destination configured in SM59.
Let's see how these tools work...
Fiori System Alias Checks
Procedure:
- Execute transaction /UI2/FSAC. The landing page has only single field, System Alias, on the selection screen.
- We can run it for single system alias or multiple.In this case I am going to run it for all the system alias available.Enter all the Alias and execute
- The output screen will show all the discrepancies in the System alias as shown below
- Message column shown the error for the specific Alias and we need to take corrective action accordingly.
Below is the list of checks this report performs and the corrective action for each one:
| Message | Status | How to Fix the Issue |
| System alias is not maintained | Error | Create missing system Alias in transaction /UI2/GW_SYS_ALI |
| No RFC destination is maintained for system alias | Warning | In transaction SM59, maintain a destination with connection type 3 (Connection to ABAP System) with the name <system alias>_RFC. |
| No HTTP destination is maintained for system alias | Info | In transaction SM59, maintain a destination with connection type H (HTTP Connection to ABAP System) with the name <system alias>_HTTP. |
| No HTTPS destination is maintained for system alias | Warning | In transaction SM59, maintain a destination with connection type H (HTTP Connection to ABAP System) with the name <system alias>_HTTPS. |
| Path Prefix field should be empty for system alias | Error | In transaction SM59, on the Technical Settings tab, make sure that the Path Prefix field is empty. |
| SSL should be active for HTTPS connections for system alias | Error | In transaction SM59, on the Logon & Security tab, make sure that SSL is set to active. |
| HTTP and HTTPS are using the same port for system alias | Warning | In transaction SM59, on the Technical Settings tab, make sure that different ports are maintained in the Service No. field for HTTP and HTTPS destination. |
| HTTP port for system alias should start with <port number> | Warning | In transaction SM59, on the Technical Settings tab, make sure that the correct port is maintained in the Service No. field. |
| HTTPS port for system alias should start with <port number> | Warning | In transaction SM59, on the Technical Settings tab, make sure that the correct port is maintained in the Service No. field. |
Fiori Launchpad Intent Analysis
The second transaction /UI2/FLIA (Fiori Launchpad Intent Analysis) provides an overview of all the intents (semantic objects – action).
Execute the transaction /UI2/FLIA and landing page will be as shown below:
As we can see, there are multiple option to filter the content for Analysis along with Intent .
Intent: Here combination of semantic object and action need to be passed separated with “-“ (for e.g. PaymentOrder-manage)
Form Factor: To filter the content based on device type defined in configuration i.e. Desktop or Phone or Tablet)
Lets Say we want to analyze the specific Fiori app intent for which we are facing issue, for e.g EnterpriseSearchBusinessObject-manage and we want to analyze it for the roles assigned to specific user, input the details as below:
The output will list, if there are any, issues with the intent in the roles assigned to the user specified. As we can see below, the intent is assigned in 3 different roles and the issues. The error can be checked in column “Message”
In this particular case error is “invalid semantic Object” and that could mean wrong semantic object is maintained in Tile or Target mapping or semantic object is not maintained in transaction /UI2/SEMOBJ or /UI2/SEMOBJ_SAP.
Here it was missing in /UI2/SEMOBJ and /UI2/SEMOBJ_SAP and once maintained in /UI2/SEMOBJ error is gone.
Fiori Launchpad Text Analysis (/UI2/FLT)
This tool is used to analyze texts used in Fiori Launchpad and fix the issue related to them. This tool provides the features like:
- Search for specific text strings used in Catalogs, Groups, tiles, or target mappings
- Navigate to the object that contains the text definition in Fiori Launchpad Designer
- Find out the Text ID and Configuration ID needed to identify the text in translation system
Moving on, lets see how to check all this information in the report.
Execute Transaction /UI2/FLT and landing screen will be as shown below.
As we can see the screen is similar to the initial screen of Fiori Intent Analysis report except couple of changes like here, we have Text field instead of Intent filed and an additional filed Software component to filter the content for analysis.
Enter the filter criteria and execute the report to analyze the Text content. In this case I searched for Text “Upload General Journal Entries” and want to look for the same in roles assigned to my user.
The output list the Usage of the entered text in all the places like catalogs, Groups, TM, tiles etc. and can see in Column “Type” as shown below. All the details related to the usage of Text can be checked by selecting the record and clicking on details icon.
Click on the link in Catalog ID to navigate to the Catalog in Launchpad Designer directly from the report.
Click on the link in column “TEXT” to get the details including Text ID and Configuration ID.
This Text ID and Configuration ID will be handy to identify the text in the translation system. To know where to maintain and check Fiori Launchpad Text translations , check this blog.
So,with this , we learnt how using standard tools we can analyze the System alias, Intent related issues, or Fiori Launchpad Text content.
Keep Learning & Keep Sharing!
- SAP Managed Tags:
