Intent Resolution

Use the application log to analyse the root cause of a failed intent resolution.

In order for a link from the SAP Fiori launchpad to be resolved successfully, the intent referenced in the URL must be valid and assigned to the current user’s PFCG role.

If the navigation from the launchpad to an application fails, a log is written in the Application Log: Display Logs (transaction SLG1). To display a message containing an application log ID, use the console log of your browser. You can use the log ID to search for the relevant entry in the application log. To get more details on the root cause of the failed intent resolution, you can navigate from the message text of the log to the Fiori Lauchpad Intent Analysis (transaction /UI2/FLIA).

For more info, see Message Logging for Launchpad and Launchpad Designer.

The intent resolution fails in the following cases:

Table 1:
Issue	Message Log Type	Error Analysis and Possible Solution
The intent does not exist	Warning	Make sure the intent that is referred to in the URL exists. Correct the intent reference in the URL or create an intent. See Configuring Target Mappings
The intent exists and is valid but it is not assigned to the current user’s PFCG role	Warning	If the current user should be able to navigate to the link, make sure that the user is assigned to a PFCG role that is assigned to the catalog containing the app launcher tile and the target mapping. See Assign Tile Catalogs to Roles.
The intent exists and is assigned to the user’s PFCG role, but the configuration of the navigation target is not consistent.	Error	The target mapping references a target (launchpad role, launchpad instance, application alias/application ID) that is not configured in transaction LPD_CUST. Start transaction LPD_CUST and make sure a valid target is customized. See Customizing Navigation Targets in LPD_CUST. Make sure the target mapping configuration is correct. See Configuring Target Mappings.