Launchpad Content Manager

The launchpad content manager maintains business catalogs, which reference originals kept in technical catalogs. Its main functions are:

• Explore content: search tiles and target mappings across all catalogs; a tile and target mapping with the same intent and target in one catalog appear as one row.
• Maintain catalogs: create, copy, rename and delete catalogs, and add or remove references to tiles and target mappings, also as a mass operation.
• Check roles: see which roles hold a catalog, a space or a tile/target mapping combination, and assign catalogs to single roles.
• Check services: verify that the OData and ICF services behind SAPUI5 apps, Web Dynpro apps and dynamic tiles are active.
• Show content issues: list problems found while loading catalogs and matching tiles to target mappings.

The three tabs are Catalogs, Tiles/Target Mappings and Roles. The launchpad content manager is therefore the place where catalog content is combined and checked, not where it is first defined.

The launchpad content manager exists in two variants that write to different scopes:

Client-specific changes supersede the configuration settings for that client. SAP blocks editing cross-client catalogs in the client-specific variant, because doing so would leave outdated copies in the customizing scope. Both variants can also be started from the launchpad tiles "Launchpad Content Manager – Client Specific" and "– Cross Client", or from SAP Fiori Customizing in SPRO. For custom business catalogs, the client-specific launchpad content manager is the default choice.

A typical sequence for a purchasing role at Alder Manufacturing:

1. Copy the SAP business catalog closest to the need into the customer namespace. The copy keeps its references to SAP's originals.
2. Add references to further apps, or remove references the role should not have. Custom apps must first exist in a custom technical catalog created with the launchpad app manager (/UI2/FLPAM).
3. Run the service check on the catalog and activate missing OData services in /IWFND/MAINT_SERVICE and ICF nodes in SICF.
4. Assign the catalog to a single role in the Roles tab, or open the role in PFCG to change it there; composite and derived roles are changed in PFCG only.
5. Choose Refresh Roles to see role changes made in PFCG, then record the catalog on a transport request.

As of SAP S/4HANA 2023 FPS01, the launchpad content manager can also launch the rapid activation task list (STC01) for selected catalogs or roles. Built with the launchpad content manager, a business catalog stays connected to SAP's originals while its scope fits the role.

The tool is deliberately narrow. SAP documents these boundaries:

• No originals. It cannot create, change or delete original tiles and target mappings. That is the job of the launchpad app manager.
• No custom tiles. Custom tile types, such as SAP Smart Business KPI tiles, cannot be displayed or added here; SAP still points to the deprecated launchpad designer for them.
• No full role editing. It does not reimplement PFCG; it only assigns catalogs to single roles.
• No live refresh. Content is loaded once per session; changes made meanwhile in another session are not detected, which can cause inconsistencies.
• Cache dependency. It reads persisted content through the user-independent cache, so SAP asks administrators to schedule regular cache synchronization.

Knowing these limits prevents administrators from searching the launchpad content manager for functions that live in other tools.

Three built-in checks cover the most common catalog-level problems:

1. Content issues: the tool flags references that cannot be resolved, catalogs whose configuration and customizing versions differ, and faulty tile or target mapping configuration. SAP asks administrators to clear entries with status "Error" before exposing content to SAP Build Work Zone.
2. Service activation: Check Services works per tile/target mapping, catalog or role, or for all displayed items. Check and Show Services lists each OData V2, OData V4 and ICF service with its status and links to the activation transactions. Apps on remote systems and custom tiles are not checked.
3. Usage in roles: the Show Usage in Roles toggle answers "who would lose this app if I removed it?" before a reference is deleted.

When the catalog looks correct but a tile still fails, /UI2/FLIA is the next step, because intent analysis shows what the launchpad resolved for one user. The launchpad content manager answers catalog questions; it does not trace individual user sessions.

The launchpad content manager is an ABAP front-end server transaction, documented for SAP S/4HANA on-premise and Private Edition, not for Public Edition. In SAP S/4HANA Cloud Public Edition, administrators work with SAP-delivered business catalogs, custom catalog extensions and the Maintain Business Roles app instead. On SAP BTP, SAP Build Work Zone manages its own content and receives SAP S/4HANA catalogs through content federation. The launchpad content manager is therefore a tool for systems whose launchpad content the customer administers directly.