Skip to Content
Technical Articles
Author's profile photo Vijay Sharma

Troubleshooting ‘Reference Lost’ error in Fiori Launchpad Designer

To enable reuse, original tiles and target mappings are defined once, in a technical catalog, and many business catalogs can contain references to these originals.

And many a times we see “Reference lost” error in Fiori Launchpad Designer or in Launchpad Content Manager or Manage Launchpad Pages. “Reference lost” means that a reference exists but its original tile or target mapping is not present in the current system/client.

In this blog, we will see how to troubleshoot and find out the cause and cure for the same.

Listing the all the Reference lost cases

Let’s start with listing down all the reference lost cases. To do the same, navigate to the Launchpad Content manager ( cust or conf mode) using transaction /UI2/FLPCM_CUST ( for customizing).

Open Tile/Target mapping tab and search for “Reference Lost”

Change the Table layout to include the below mentioned fields to analyze the data better.

As can be seen below, all the reference lost cases will be listed, it could be Tile or TM reference which is lost or for both depending on what all is referenced.

There will be two types of issues:

  • Error {Reference Lost}
  • Warning {Reference Lost to Backend Catalog}
Analyzing Specific “Reference Lost” issue.

The specific reference lost error can be analyzed using the standard report “/UI2/REFERENCE_LOST”.

The landing page of the report will look like below. Error message or Error Instance ID is the mandatory input field

Where to get the instance ID or Error message from?

There are different ways:

  • In Launchpad Content Manager, you can find the instance ID in columns ‘Original Tile ID’ or ‘Original Target Mapping ID’.

  • In Launchpad Designer and Manage Launchpad Pages, the title of the broken tile/target mapping contains the instance ID.

We can pick the complete error message from the Launchpad designer tile or Just the Instance ID from any one of the two places shown above and pass the same as input to the report “/UI2/REFERENCE_LOST” and execute.

Output of the report will show the issue analysis details along with the possible solution. As we can see, for this specific instance, the referenced catalog “SAP_TC_FIN_CM_COMMON” is existing but the referenced tile is not existing and that’s why the reference lost error.

The solution suggest either to reimport the catalog “SAP_TC_FIN_CM_COMMON” from another system which is not impacted or remove the reference to the tile and recreate it.

Let’s look at another example with warning {Reference lost to backend catalog}. Lets pick the instance ID and execute the report “/UI2/REFERENCE_LOST” with it as input.

The output again gives the detailed analysis of the error. The TM is supposed to be present in backend catalog and the catalog should be replicated to resolve the error. Solution suggests the steps to be executed to replicate the catalog by running the transaction “UI2/APPDESC_GET_ALL” or “UI2/APPDESC_GET”

With this we know how to analyze the Reference lost issues and find out the resolution for the same.

 

Keep Learning & Keep Sharing!

 

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.