SAP Fiori Apps Reference Library

Each app entry is a release-specific record of what the app is and what it needs:

The same app can carry different catalogs, roles or services per product and release. The SAP Fiori Apps Reference Library is therefore read for one release at a time, never in general.

Take Manage Purchase Orders (F0842A) for SAP S/4HANA 2025 FPS02 on-premise. The entry shows:

• Intent: PurchaseOrder-manage, which a target mapping must resolve;
• Technical catalog: SAP_TC_PRC_COMMON, where the tile and target mapping are defined;
• Business catalog: SAP_PRC_BC_PURCHASER_PO, the unit that roles reference;
• Business role: SAP_BR_PURCHASER, the SAP-delivered role template that contains the catalog;
• OData service: MM_PUR_PO_MAINT_V2_SRV, which must be active for the app to load data.

Each line maps to a setup task: activate the service, include the business catalog in a role, assign the role to users, and confirm that the intent resolves. When Alder Manufacturing builds a custom purchaser role, the entry tells the team which catalog to reference rather than which tiles to copy. An app entry in the SAP Fiori Apps Reference Library is a checklist for the content and services an app depends on.

SAP organizes the library's functions along the project phases:

1. Explore: use Search and Filter to find apps that match business and system requirements, or run Get SAP Fiori App Recommendations. The recommendation wizard compares a usage profile (the transaction codes used in production, which can be extracted from the workload monitor ST03) and a system profile (installed software component versions) with the library.
2. Plan: the List View produces one row per app and exports to a spreadsheet; App Details shows product features and implementation information.
3. Set up and configure: the Aggregate function returns a validated, redundancy-free list of configuration data for a selection of apps, such as all required OData services, and shows changes between releases, including predecessor and successor apps.

Saving selections and running recommendations require logging on with an SAP user ID. The SAP Fiori Apps Reference Library is most valuable before content activation, when scope is still being decided.

The SAP Fiori Apps Reference Library sits outside every customer system. It describes the content SAP ships — catalogs, roles, intents, services — but it does not run, store or assign anything. At runtime, the launchpad reads only what exists in the system: activated catalogs, roles assigned to users and active services.

That separation explains two practical rules. First, the library is the reference for SAP-delivered content, while the system is the reference for what users actually have; when the two disagree, the system wins. Second, custom apps, copied catalogs and customer roles never appear in the library. Content activation tools, such as the rapid content activation task lists on-premise, use the same SAP business roles that the library lists. The SAP Fiori Apps Reference Library is documentation of SAP's content, not an inventory of a customer's launchpad.

The library keeps separate release lines for SAP S/4HANA Public Cloud (releases such as 2602 and 2608) and for SAP S/4HANA Private Cloud and On-Premise (releases such as 2025 FPS02, with separate on-premise and Private Cloud records). An app's business roles, catalogs and even availability can differ between these lines.

• Public Edition: SAP delivers and activates the content; customers mainly use the library to find which business role template or business catalog grants an app.
• Private Edition and on-premise: customers activate content and services themselves, so the implementation information becomes a configuration checklist.

SAP also released a new version of the SAP Fiori Apps Reference Library, documented under SAP Cloud ALM, in March 2026 and added an Aggregated Information feature in April 2026; check the SAP Help Portal for how it relates to the classic library. Selecting the correct product and release is the first step in every SAP Fiori Apps Reference Library lookup.

1. Reading the wrong release. Roles and services change between releases; filter by the exact product and release before copying any name.
2. Mixing Public Edition and on-premise data. An entry for SAP S/4HANA Public Cloud does not describe a Private Edition system, and the reverse also holds.
3. Treating "listed" as "available". An app in the library may need a product version, support package or service the system does not have.
4. Copying tiles instead of referencing them. The entry names the SAP catalogs to build on. Business catalogs hold references to tiles and target mappings in SAP technical catalogs, so central changes propagate; copied tiles and target mappings no longer receive them.
5. Ignoring successor information. Deprecated apps often have a named successor; implementing the predecessor creates rework at the next upgrade.

Most errors with the SAP Fiori Apps Reference Library come from reading a correct entry for the wrong context.