Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 6 of 6

Choosing and naming apps

7 min

"Use the sales order app" is not an instruction. SAP S/4HANA has several apps with similar names, versions that replaced older ones, and SAP GUI transactions available in the launchpad. Key users and testers need to find the right app for a task and name it so precisely that anyone can repeat the step. The SAP Fiori apps reference library is the tool for both.

Searching the reference library

The reference library is a public SAP website that describes every SAP Fiori app and many classic apps available through the launchpad. You can search by app name, app ID or keyword, and filter by product (for example SAP S/4HANA versus SAP S/4HANA Cloud Public Edition), line of business, role, app type and release. For each app it shows a description, its key features, the business roles and catalogs that include it, and implementation information for the release you select.

  1. Describe the task"Display open supplier items for company code 1710"
  2. SearchKeyword "supplier line items", product SAP S/4HANA, your release
  3. Compare candidatesRead descriptions and app types; check which business roles include them
  4. Choose and recordApp name, app ID, release, required business role
  5. Check in your systemConfirm the app appears in the App Finder for the test user
Finding the right app for a task.
The Sign-Off Table · thesignofftable.com/academy/sap-xpr-202

What the app ID tells you

Every app in the library has an app ID. Fiori apps typically have IDs beginning with F followed by digits, such as F1873 for Manage Sales Orders or F0712 for Manage Supplier Line Items. A suffix letter can mark a newer version of an app: Manage Purchase Orders, for example, is listed with a version-2 ID ending in A. Classic apps are identified by their transaction code or application name. The ID is unambiguous where names are not: there are, for instance, separate sales order apps for different purposes, and the library will show you which is which.

Instruction in a test caseProblemBetter
"Open the sales order app"Several apps work with sales orders"Open Manage Sales Orders (F1873)"
"Go to supplier items"Could mean the Fiori app or SAP GUI FBL1N"Open Manage Supplier Line Items (F0712)"
"Create the PO"Fiori app or SAP GUI ME21N? Different screens"Create purchase order in SAP GUI transaction ME21N"
"Check the invoice"No object, no app, no expected result"Open the supplier invoice in Manage Supplier Invoices and check status Posted"
Naming apps precisely in test steps. App IDs shown are examples; confirm them for your release in the reference library.
The Sign-Off Table · thesignofftable.com/academy/sap-xpr-202

Edition and release matter

An app available in Public Edition may not exist in your Private Edition release, or may exist in a different version. Always filter the library to your product and release. For Contoso, that is SAP S/4HANA 2025 in a private cloud. If a test case was written from a Public Edition demo, check every app ID against Contoso's release before the test cycle starts.

Writing the step

  1. Name the app and its ID, or the transaction code: "Open Manage Sales Orders (F1873)".
  2. Name the variant or filters: "Select variant O2C – Blocked orders 1710".
  3. Name the object: "Open sales order 1000457".
  4. Name the action: "Choose Edit, remove delivery block, Save".
  5. State the expected result: "Order saved; delivery block field is empty; process flow shows no delivery yet".
  6. State the role used: "Executed as test user with Contoso internal sales role".

What would you do?

A Contoso test case written last year says "Open Manage Purchase Orders". In the current release, testers find two apps with similar names in the App Finder. What should Priya do?

Key points
  • The SAP Fiori apps reference library describes apps by name, ID, product, release, role and type.
  • App IDs identify apps unambiguously; suffix letters can indicate newer versions.
  • Filter the library to your product and release; Public Edition and Private Edition differ.
  • Test steps should name app and ID, variant, object, action, expected result and role.

Check your understanding · not graded

Lesson check

  1. 1. Why include the Fiori app ID in a test step?

  2. 2. What can you filter by in the SAP Fiori apps reference library?

  3. 3. Why must you select your release in the reference library?

  4. 4. Which test step is the most precise?