Show TOC

Message Logging for Launchpad and Launchpad DesignerLocate this document in the navigation structure

This section explains how message logging is handled for SAP Fiori launchpad and SAP Fiori launchpad designer.

The SAP Fiori system landscape comprises a front-end server and application servers. All errors occurring in the launchpad or launchpad designer are written into the UI services application log (object /UI2/BE) and into an SAP Gateway message container. All logs are written on the front-end server.

The options to display messages are as follows:

Display Messages in the Browser

If an error occurs during processing, you can use the developer tools available for browsers to display the message. If no error occurs during processing, you can only display the messages in the back end for SAP Gateway SP07 or lower versions.

To display messages in the front end, proceed as follows:

  1. Start the SAP Fiori launchpad.

  2. In the browser, open the developer tools.

    Note For Internet Explorer, Google Chrome and Firefox, this is done by pressing the F12 key.
  3. In the developer tools, switch to Network to display a network trace. All network requests sent by the client are displayed.

  4. Select a request from the list. To display further details, for example headers that were sent or the response that was retrieved, switch to Headers or Response.

  5. If there is an error like HTTP 404 (Page/file not found), select the entry and choose Response. For more details, switch to Console.

Display Messages in the Front-End Server

OData services and utilities (e.g. reports) of the SAP NetWeaver User Interface Services write to the application log under object /UI2/BE. All errors occuring in a service are also written to the SAP NetWeaver Gateway log.

Application Log: Display Logs for SAP NetWeaver User Interface Services (transaction SLG1)
  1. Start Application Log: Display Logs (transaction SLG1) in the ABAP system.

  2. Enter the following data:

    • Object: /UI2/BE (UI2 Backend Enablement: Application log)

    • Subobject:

      • /UI2/INTEROP: interoperability service

        The following use cases write to the log:
        • Transfer personalization from Web Dynpro Configuration to database

        • Delete expired personalization

        • Setting up end user feedback

        • Errors in navigation link resolution

        • Cleanup of application states

      • /UI2/PFCG: PFCG integration

        The following use case writes to the log:

        An application used in the assigned catalog is not available in the ABAP system when an administrator determines authorization defaults. See Assign Tile Catalogs to Roles.

      • /UI2/PAGE_BUILDER:

        The following use case writes to the log:

        Entities in the launchpad designer or in the launchpad home page are created, updated, or deleted.

      • /UI2/CLEANUP_CACHES: clean up all server-side caches

    Note Alternatively, you can enter the External ID. This is a unique ID that is displayed in the error details in the browser.
  3. Choose Execute.

    In the message list that is shown, you can double-click an entry to display the message text.

    Depending on the error cause, you can choose (Details) for further information:
    • Errors in navigation link resolution:

      You are directly navigated to theFiori Launchpad Intent Analysis (transaction /UI2/FLIA). Run the report to determine the root cause of the failed link resolution. For more information, see Intent Resolution.
    • Errors occuring in launchpad designer or launchpad home page for actions create/update/delete:

      A call stack is displayed and you can navigate to the message code.

The log for subobject /UI2/INTEROP does not always return the required results for the SAP Fiori launchpad use case. For example, errors occurring because the user does not have the required authorization to call a service or because the service is inactive, are not written in the UI services application log (object /UI2/BE). In this case, you use one of the following logs that are written in the SAP NetWeaver Gateway infrastructure:

Application Log: Display Logs for the SAP Gateway Runtime (transaction SLG1)
  1. Start Application Log: Display Logs (transaction SLG1) in the ABAP system.

  2. Enter the following data:

    • Object: /IWBEP/

    • Subobject: RUNTIM

    • External ID

      This is the transaction ID displayed in the error details in the browser.
  3. Choose Execute.

GW Backend Error Log (transaction /IWBEP/ERROR_LOG)
  1. Start GW Backend Error Log (transaction /IWBEP/ERROR_LOG) in the ABAP system.

  2. Choose Re-Select.

  3. Enter the following data:

    • User ID

    • Date

    • Time interval

  4. Choose Execute.

SAP Gateway Error Log (transaction /IWFND/ERROR_LOG)
  1. Log on to the SAP Gateway server in case it is not installed in the back end.

    If SAP Gateway is installed in the back end, you can start the transaction directly in the back end.

  2. Start Gateway Error Log (transaction /IWFND/ERROR_LOG) in the ABAP system.

  3. Choose Re-Select.

  4. Enter the following data:

    • User ID

    • Date

    • Time interval

  5. Choose Execute.

  6. Select an error message.

  7. To display the application log of SAP Gateway, choose Application Log.