Tuesday, 12 October 2021 08:12

SAP Fiori for SAP S/4HANA – How to fix Changed and Outdated Catalogs

Written by Jocelyn Dart
Rate this item
(0 votes)
Source https://blogs.sap.com/2021/10/13/sap-fiori-for-sap-s-4hana-how-to-fix-changed-and-outdated-catalogs/
“© 2020. SAP SE or an SAP affiliate company. All rights reserved.” “Used with permission of SAP SE”

One of the minor annoyances of upgrading in SAP S/4HANA is that occasionally you may find changed or outdated SAP Fiori business catalogs that need to be corrected.  These usually manifest themselves as:

  • Apps that do not appear in your launchpad page(s) or App Finder or Search even though they are assigned to your business catalog(s)
  • Apps that appear in some clients but not others, even though the app is assigned to your business catalog(s) in all clients
  • Business Catalog is assigned to the role but does not appear in the App Finder

App%20Finder%20is%20missing%20a%20business%20catalog%20assigned%20to%20the%20business%20role

App Finder is missing a business catalog assigned to the business role

  • Errors when you select a tile or link such as: “Navigation is not possible because your role is not assigned a business catalog that contains the navigation target #<SemanticObject>-<action>”

Error%20message%20Navigation%20is%20not%20possible%20because%20your%20roles%20is%20not%20assigned%20a%20business%20catalog%20that%20contains%20the%20navigation%20target

Error message Navigation is not possible because your roles is not assigned a business catalog that contains the navigation target

In this blog post you will learn how to quickly overcome them.

Generally, these issues come from a mismatch between the cross-client and client-specific versions of the same business catalog. There are 2 main causes:

  1. Upgrades
    • Primarily because in earlier releases the recommendations on whether to place catalogs in the cross-client or client-specific scope was less strict. On upgrade, the catalog is reassigned to the correct scope layer and this can result in mismatches.
  2. Unintentional or deliberate changes made in the Launchpad Designer.
    • This older tool had few protections against making client-specific changes to SAP catalogs and custom catalogs. The Launchpad Designer is now deprecated and the new tools – i.e. the Launchpad Content Manager and Launchpad App Manager – provide better scope visibility and avoid these errors.

You can find a detailed explanation of these Scope-related Issues with Setting up Launchpad Content  in the Fiori launchpad Administration Guide in the SAP Help Portal.

The Launchpad content manager provides some easy ways to find and fix these issues.

The quickest way to find outdated and changed catalogs is to use the Launchpad Content Manager (i.e.  transaction /UI2/FLPCM_CUST). You can launch the transaction in SAP GUI or from the Fiori Administrator’s launchpad using the tile FLP Content Manager: Client-Specific.

Fiori%20Administrator%20role%20showing%20the%20FLP%20Content%20Manager%3A%20Client-Specific%20tile

Fiori Administrator role showing the FLP Content Manager: Client-Specific tile

Hint: The Fiori Administrator user and their launchpad assignment can be automatically generated using task list SAP_FIORI_FOUNDATION_S4 as shown in the openSAP microlearning Activating

Continue reading here
Read 30 times

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.