Checking and Adjusting Launchpad Content

Objective

After completing this lesson, you will be able to manage SAP Fiori Launchpad Content after an Upgrade.

Issues with Launchpad Content

Displaying Issues with Launchpad Content

The launchpad content manager displays issues with launchpad content.

  • The catalog state is different on the configuration and the customizing scope.
  • References to tiles and target mappings cannot be resolved.
  • There are issues with the configuration of tile and target mapping.

Scope-Related Catalog Issues

The launchpad content manager indicates if the state of a catalog differs on the configuration and the customizing scope.

The launchpad designer allows you to make client-specific changes to cross-client catalogs (for example, changing the catalog title or adding tiles). In this case, a copy of the cross-client catalog is created in the customizing scope. This copy has the same ID as the original catalog in the configuration scope. If the original catalog contains original tiles/target mappings, the copied catalog includes these objects as originals with the same ID. The copied catalog in customizing is now decoupled from the catalog in the configuration scope. Any changes made in the configuration scope (except changes of texts in tiles or target mappings) are no longer reflected in the customizing scope.

Note

To prevent these inconsistencies, cross-client catalogs cannot be changed in the client-specific launchpad content manager. We recommend you to change the cross-client catalog in the configuration scope (transaction /UI2/FLPM_CONF) or to copy the catalog in the customizing scope (transaction /UI2/FLPM_CUST) and make changes for the current client only

Note

To display the issue open the Catalogs tab in the client-specific launchpad content manager (transaction /UI2/FLPM_CUST). Filter the Scope columns for Customization and check the value in Status in Current Client column.

Value

Description

Original

The catalog was created in the current client and does not exist in the configuration scope.

Changed

The catalog was created in the configuration scope and changed in the current client using the launchpad designer, which means that it is now decoupled from the original catalog on the configuration scope. If the original catalog is now changed in the configuration scope, these changes will not be reflected in the current client.

Outdated

The catalog was created in the configuration scope and changed in the current client using the launchpad designer, which means that it is now decoupled from the original catalog on the configuration scope. The original catalog was then changed in the configuration scope. The catalog on the current client is outdated because the changes in the configuration scope are no longer reflected. If the catalog is now changed in the customizing scope, its status will be set to "Changed" again.

If a catalog is outdated, you have the following options:

  • Update the catalog to the latest changes of the configuration scope. Changes made in the customizing scope will be lost.
  • Continue working with the existing changes of the customization scope. In this case, you do not receive the latest changes provided in the configuration scope.

Issues with Tiles and Target Mappings

The launchpad content manager indicates broken references and issues with the configuration of tiles and target mappings.

To display the issue open the Tiles/Target Mappings tab in the launchpad content manager. Check the Title / Subtitle / Information column to get a first hint about the issue:

Issues with Tiles and Target Mappings

  • Reference Lost to Backend Catalog
  • Reference Lost
  • Configuration Error

To get further information on the issue, open the context menu for a selected row and choose Status Details.

Description of the Issues:

Reference Lost to Backend Catalog
The selected tile/target mapping refers to an original tile/target mapping which was defined in the backend using the launchpad app manager.

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.

Reference Lost
The selected tile/target mapping refers to an original tile/target mapping which was defined in 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.

Configuration Error
There are several reasons for a tile/target mapping configuration issue.

Note

For details on how to solve these issues and the reasons for configuration errors see section Issues with Tiles and Target Mappings on help.sap.com

(https://help.sap.com/docs/ABAP_PLATFORM_NEW/a7b390faab1140c087b8926571e942b7/bff8d59f71384fcf84b61df55a6bfb66.html)

.

Adjust Launchpad Content after an Upgrade

After an upgrade from a lower on-premise version to a higher one, it might be necessary to adjust your launchpad content due to some changes. Applications can become obsolete or deprecated and you might need to add a successor.

Transactions and their status allow you to find out if an app is still in use or if it needs to be replaced. Transactions are assigned to launchpad app descriptor items belonging to a SAP Fiori app. SAP assigns the transaction in the launchpad app manager and maintains the status in Maintain Authorization Default Values (transaction SU22) .

In the Launchpad Content Manager, you can check the transaction status and, if required, add new tiles and target mappings to your catalog using the associated successor transactions.

Note

This new feature is available as of SAP S/4HANA 2021.

Supported app types are:

  • SAP GUI transactions
  • SAPUI5 SAP Fiori applications
Screenshot showing transaction status in Launchpad Content Manager.

Checking the Status of Launchpad Content

On the Tile/ Target Mappings tab, the fields Transaction and Transaction Status are displayed by default. They show the status of the relevant content. On the tabs Catalogs and Roles, you see an aggregated status of the associated transactions.

Transaction Status in the Launchpad Content Manager

Transaction StatusDescriptionAction
DeprecatedThis status is a precursor of the status Obsolete. The app is not being developed anymore and is planned to be removed in the near future. The app can still be used.When the status was set to Deprecated, this usually means that launchpad content with an associated successor transaction is in place. We encourage you to use the successor and avoid using the deprecated content, as it will be removed in an upcoming version.
ObsoleteThe app does not meet important functional requirements and should therefore no longer be used.Remove the launchpad content with the obsolete transaction and add launchpad content with the associated successor transaction instead.
Remote ContentThe status of remote content (system alias is not mapped to local) cannot be determined.You have to manually check in the back-end system if the app is up-to-date.

If the status field is empty, the launchpad content is either up-to-date or no checks are needed, because, for example, the app type is not supported.

Adjusting Launchpad Content with Associated Successor Transactions to your Business Catalog

Screenshot on adjusting launchpad content.

You can view and directly update your launchpad content with the associated successor transactions in the Launchpad Content Manager. In order to do that, you need to perform following actions:

  1. Open theLaunchpad Content Manager (transaction /UI2/FLPCM_CUST) and go to the Catalogs tab.
  2. In the upper table, select the relevant catalog in which the obsolete or deprecated launchpad content is assigned to.
  3. In the lower table, you can see a list of tiles and target mappings and their transaction status. Click Other Functions  → Show/ Add Successors.
  4. If new content with an associated successor transaction is available, a new window is opened. Select the relevant tiles and target mappings and click Add Tile/ TM Reference.
  5. Remove the deprecated or obsolete tiles and target mappings from your catalog.

After you have adjusted your launchpad content in the launchpad content manager, you also need to:

  1. Add your new tiles to your page and remove the obsolete or deprecated ones.
  2. Activate the corresponding OData and ICF services of the newly added launchpad content.
  3. Adjust the corresponding roles and authorizations using the transactions:
    • Profile Generator: Upgrade and First Installation (transaction SU25)
    • Role Maintenance (transaction PFCG)

Practice System Exercise: Adjusting Launchpad Content with Associated Successor

Select Start Exercise to start the simulation.

ExerciseStart Exercise

Note

If you have access to a practice system, you can now execute this exercise.

Business Example

After an upgrade you want to check if it might be necessary to adjust your launchpad content due to some changes.

Task 1: Search for catalogs containing deprecated transactions and adjust the catalog content.

Use the Launchpad Content Manager to search for catalogs containing deprecated transactions and to adjust the catalog content.

Steps

  1. Log on to SAP Fiori Launchpad of system S4D with your train-## user. Use Google Chrome.

    FieldValue
    Usertrain-##
    Password

    Custom password

    1. In the Microsoft Windows start menu, choose Google Chrome.

    2. In Google Chrome, go to Bookmarks.

    3. In Bookmarks, choose 10 Development → s4dhost → 10 S4D SAP Fiori Launchpad.

  2. Start the Launchpad Content Manager: Client-Specific app from the Fiori Launchpad space.

    1. On the SAP Fiori Launchpad home screen, choose the Fiori Launchpad space.

    2. Launch the Launchpad Content Manager: Client-Specific app.

      Result

      The WebGui Transaction opens.

    3. Alternatively, you can start transaction /UI2/FLPCM_CUST from SAP GUI. To do so, enter /n/ui2/flpcm_cust in the OK field of the SAP GUI.

    4. Ensure that the Catalogs tab is selected.

  3. Search for catalogs containing deprecated transactions.

    1. On the Catalogs tab of the Launchpad Content Manager: Client-Specific (Customizing), select column Transaction Status.

    2. Choose Set Filter.

    3. In the Transaction Status field of the screen Determine Values for Filter Criteria, enter Contains deprecated transactions.

    4. Choose OK.

    5. Choose Execute (Enter).

      Result

      The result shows that your catalog ADM945_##_BC_FIN_ACCOUNT contains deprecated transactions

  4. Select your Financial Accounting Catalog ## catalog and adjust the Launchpad content.

    1. Select your catalog ADM945_##_BC_FIN_ACCOUNT.

    2. At the bottom (area Content in Catalog...), choose Other Functions → Show/Add Successors.

      Result

      The result shows the successor tile/target mapping for Transaction F1574:

      Transaction: F1574A

      Title: Manage Banks - Cash Management

    3. Select the transaction F1574A form the result list and choose Add Tile/TM Reference.

      Result

      The system will prompt for a customizing transport request since you are creating new customizing objects.

    4. Select the request you created in the previous exercise.

    5. Choose Continue.

    Result

    Now you have added the the app Manage Banks - Cash Management to your ADM945_##_BC_FIN_ACCOUNT catalog.

  5. Select your Financial Accounting Catalog ## catalog and delete the deprecated transaction F1574

    1. Select your catalog ADM945_##_BC_FIN_ACCOUNT.

    2. At the bottom (area Content in Catalog...), select the transaction F1574 from the list of tiles/target mappings .

    3. Choose Remove Tiles/Target Mappings.

    4. Select Tiles and Target Mappings on the screen Remove References from Catalog.

    5. Choose Continue.

      The screen Messagesindicates that the tile and the target mapping cannot be removed because they are assigned to a Launchpad space

    6. Choose Close.

  6. Choose SAP logo to get back to the FLP home screen.

Task 2: Adjust the page content

After adjusting the catalog content you also have to adjust the page content.

Steps

  1. In the Manage Launchpad Pages app, remove the Manage Banks app and add the Manage Banks - Cash Managementapp to the Z_ADM945_##_BANK_MGMT page.

    1. On the SAP Fiori Launchpad home screen, choose the Fiori Launchpad space.

    2. Launch Manage Launchpad Pages app.

    3. Select Z_ADM945_##_PG_BANK_MGMT.

    4. Choose Edit (pencil icon).

    5. Choose Remove on the tile Manage Banks to remove the Manage Banksapp.

    6. In the Derived from Roles section on the right-hand side, choose Add for the Manage Banks - Cash Management app.

      Result

      The tile is added to the Quick Access section.

    7. Choose Save ind the lower right-hand corner.

    8. Choose Back.

Task 3: Delete the deprecated app from the catalog

Finally you have to delete the deprecated app from the catalog.

Steps

  1. Start the Launchpad Content Manager: Client-Specific app from the Fiori Launchpad space.

    1. On the SAP Fiori Launchpad home screen, choose the Fiori Launchpad space.

    2. Launch the Launchpad Content Manager: Client-Specific app.

      Result

      The WebGui Transaction opens.

    3. Alternatively, you can start transaction /UI2/FLPCM_CUST from SAP GUI. To do so, enter /n/ui2/flpcm_cust in the OK field of the SAP GUI.

    4. Ensure that the Catalogs tab is selected.

    5. Search for your catalog ADM945_##_BC_FIN_ACCOUNT by using the Search Catalogs field.

  2. Select your Financial Accounting Catalog ## catalog and delete the deprecated transaction F1574

    1. Select your catalog ADM945_##_BC_FIN_ACCOUNT.

    2. At the bottom (area Content in Catalog...), select the transaction F1574 from the list of tiles/target mappings .

    3. Choose Remove Tiles/Target Mappings.

    4. Select Tiles and Target Mappings on the screen Remove References from Catalog.

    5. Choose Continue.

    Result

    Now the tile and target mapping are deleted from the catalog.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn