Show TOC

Launchpad DesignerLocate this document in the navigation structure

Prerequisites

You have maintained the following settings:

  • If you are in configuration scope, you have maintained the workbench request and package name
  • If you are in customization scope, you have maintained the customizing request.

You may encounter certain errors even after following the above steps.

If an error occurs in the launchpad designer when entities (e.g. catalogs or tiles) are created, updated, or deleted, a log is written in the UI services application log (object /UI2/BE). You can use the application log to analyse the root cause of an error. For more information, see Message Logging for Launchpad and Launchpad Designer.

Here is a list of some of the common errors encountered with possible causes and solutions:

No. Error Possible Reason Possible Solution
1. Unable to create or delete group
  • Back end is not available
  • Workbench request not maintained
  • Customizing request not maintained
  • If you are in customization scope, maintain the customizing request under the Settings button on the launchpad designer page.
  • If you are in configuration scope, maintain the workbench request under the Settings button on the launchpad designer page.
  • Contact the system administrator.
2. Unable to create or delete catalog
  • Back end is not available
  • Workbench request not maintained
  • Customizing request not maintained
  • If you are in customization scope, maintain the customizing request under the Settings button on the launchpad designer page.
  • If you are in configuration scope, maintain the workbench request under the Settings button on the launchpad designer page.
  • Contact the system administrator.
3. Unable to add or delete a tile in catalog or group
  • Correct path to the tile not provided
  • Workbench or customization request not maintained
  • Back end service (OData) failure
  • Maintain the transport request appropriately.
  • Contact the system administrator.
  • The tile templates are in the universal catalog (FLPD_CATALOG). If you want to add a new tile template, it has to be registered to the universal catalog using back end transaction (UI2/CHIP).

    For more information, see Registering a CSR CHIP in a Catalog.

4. SAP note is applied, but the changes are not reflected. Browser cache contains old resources Clear the browser cache to fetch the latest resources
5. Tile configuration changes are not saved
  • Customization or workbench request or package not maintained
  • Back end service failure
Maintain the transport request appropriately
6. Changes made for a catalog or a group in CONF scope are not reflected in CUSTscope. Catalog or group is outdated. Delete the responsible catalog or group in CUST scope and refresh. (All the customization changes done are deleted).
7. I delete a catalog or group in CUST scope, but it appears again when I refresh the launchpad designer tool. Catalog or group is created in CONF scope. If you really want to delete the catalog or group, then delete in CONF scope as this might impact other clients.
8. I see an error tile in some of the groups. Why?
  • You have no authorization for this tile.
  • The tile might have been deleted from the parent catalog.
  • Check for authorizations
  • Delete the tile from group even if it was deleted from the catalog.
9. The system displays incorrect data after you change catalogs or groups. As a result, for example, the title of a catalog that was created previously is missing after you restart the launchpad designer. In a system with several application servers, data was written on one server and read on a different server before the load balancing synchronization was complete. You configure a logon group that is assigned to only one application server.

For more information, see Configuring Systems with Several Application Servers.

Given below is a list of common error messages or system messages:
No. Messages Possible Reason Possible Solution
1. Cannot login with PERS scope; login with CUST or CONF PERS scope is not supported in the launchpad designer Either remove the scope parameter or add &scope=CONF at the end of the URL.
2. Remote catalog '<catalog_id>' cannot be retrieved Some of the SAP HANA catalogs are not supported due to the system landscape setup.
  • Check whether the system landscape was set up correctly and check the authentication to the remote catalog, for example, SAP HANA based Smart Business catalog works correctly.
  • Contact the system administrator.
3. Operation Failed. Transport information not specified.
  • If the application is launched in CONF scope, default workbench request and default package are not maintained.
  • If the application is launched in CUST scope, default customizing request is not maintained.
  • Check the user parameter settings in back end ABAP system or settings on the launchpad designer page.
  • You can work with catalogs or groups in ā€˜zā€™ and ā€˜yā€™ namespace in case no transport to other systems is required.
  • Select the Local Object checkbox under the Settings button on the launchpad designer page.