Lesson 6 of 6
Looking up apps in the reference library
9 min
SAP publishes a catalog of every Fiori app, called the SAP Fiori apps reference library, at fioriappslibrary.hana.ondemand.com. It is free to use and does not need a logon. For anyone who writes or reviews test steps, it is one of the most useful websites SAP offers.
What the library tells you
- The official app name and app ID, such as F1873 for Manage Sales Orders.
- What the app does, often with screenshots and a link to its documentation on help.sap.com.
- The application type and technology, such as SAP Fiori elements, SAP GUI or Web Dynpro.
- Which product and release the app is available in, including Public Edition.
- The business roles that include the app, and the technical catalogs behind them.
- Related apps, which helps you find the next step in a process.
Looking up an app step by step
- SearchType the app name or the app ID, for example F1873.
- Choose the releaseSelect SAP S/4HANA and release 2025 (or your Public Edition release).
- Read Product FeaturesPurpose, key features, documentation link.
- Open Implementation InformationUnder configuration, find the business roles and catalogs.
- Check Related AppsSee which apps come before and after in the process.
Selecting the correct release matters. Apps are added, changed and occasionally deprecated between releases, and an app can exist in Public Edition but not in on-premise, or the other way around. The library shows the latest release by default, so choose yours before you read the details.
Business roles in the library
Under the implementation information you will find the business roles that include the app. For Manage Sales Orders, that includes SAP’s template role for an internal sales representative (SAP_BR_INTERNAL_SALES_REP). Companies usually copy SAP’s template roles into their own roles with their own names, so Contoso’s role might be called something like "Z_SALES_REP_1710." The library tells you which SAP template to look for; your security team tells you which company role was built from it.
Writing test steps that name the right app
Vague steps such as "use the sales order app" cause confusion and inconsistent evidence. A good step names the app as it appears in the library, gives its ID, and states the expected starting view. For example: "Open Manage Sales Orders (F1873). Apply view UAT – 1710 fleet orders. Select the order created in step 2." The app ID survives translation and renaming of tiles, which makes it the most reliable reference.
| Weak test step | Better test step |
|---|---|
| Use the sales app to find the order | Open Manage Sales Orders (F1873); filter Sales Organization 1710, Sold-to Party 1710001 |
| Approve it | Open My Inbox; select the approval task for purchase requisition from step 3; approve with comment "UAT" |
| Check stock | Open the stock app named in the test design, filter material CMC-ALT-100, plant 1720; record unrestricted stock |
Naming the app makes a test step repeatable
What would you do?
A test script written for an earlier release refers to a Fiori app that Luis cannot find in the 2025 system, even in the App Finder. What should he do first?
- The SAP Fiori apps reference library lists every app with its ID, purpose, type, release availability and roles.
- Always select your product and release before reading app details.
- Implementation information shows SAP template business roles; your company’s roles are usually copies.
- Name apps and app IDs exactly in test steps.
Check your understanding · not graded
Lesson check
1. Where is the SAP Fiori apps reference library published?
2. Why should you choose the release in the library before reading details?
3. Where in the library do you find the business roles that include an app?