
Issue | What it means? | What to do? |
Reference Lost to Back-end Catalog Issue | The selected tile/target mapping refers to an original tile/target mapping which was defined in the back-end. The reference is broken because the original tile/target mapping or the catalog in which the originals were defined do not exist on the front-end server. | Look for Original Tile Catalog ID and Original Target Mapping Catalog ID (in error details, as shown above) and replicate the catalog to the front-end server |
Reference Lost | The selected tile/target mapping refers to an original tile/target mapping from another catalog. The reference is broken because the original tile/target mapping or the catalog in which the originals were defined do not exist in the system or client. | Look for Original Tile Catalog ID and Original Target Mapping Catalog ID (in error details, as shown above) . Check if the Catalog exist in other system or client (if deleted by mistake in current system/client) and if it does, transport the same to current system/client. If it doesn’t work, delete the reference and create again. |
Configuration Error: Tile Configuration Does not Exist | An instance of the tile was created in the catalog, but the tile configuration form was not filled out. | Check the tile configuration in the launchpad designer and maintain it correctly. |
Configuration Error: Target Mapping Configuration Does not Exist | An instance of the target mapping was created in the catalog, but the target mapping configuration form was not filled out. | Check the target mapping configuration in the launchpad designer and maintain it correctly. |
Configuration Error: Invalid Tile Configuration | The tile configuration contains errors. | Check the tile configuration in the launchpad designer and maintain it correctly. |
Configuration Error: Invalid Tile/Target Mapping Configuration | The target mapping configuration contains errors. | Check the target mapping configuration in the launchpad designer and maintain it correctly. |
Configuration Error: Custom tile data could not be read | The configuration of the custom tile could not be extracted. This leads to incomplete information about this item. | Open the catalog in the launchpad designer to display information on the custom tile. |
Configuration Error: LPD_CUST data could not be read | The LPD_CUST entry referenced by the tile/target mapping configuration in the launchpad designer was not found. | Check the configuration of the target mapping for application type SAP Fiori App using LPD_CUST In transaction LPD_CUST, check the respective settings |
App descriptor not found | The app descriptor for the SAPUI5 component ID was not found by the SAPUI5 application index. | There could be different root causes:
|
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
5 | |
3 | |
3 | |
3 | |
2 | |
2 | |
2 | |
2 | |
2 |