Fiori App Tracker - User Guide

What this tracker is

The Fiori App Tracker is a central governance and deployment tracker for SAP Fiori apps selected for the project. It is used by the Tech team to assess, approve, and deploy apps, and by functional teams to track selection status, approvals, and deployment progress.

The tracker is pre-populated with the complete SAP Fiori app catalogue for the target release (SAP S/4HANA Private Cloud 2025), sourced from the SAP Fiori Apps Reference Library. This baseline catalogue explains why the tracker contains a large number of apps and should not be interpreted as project scope.

Project scope is defined by selection indicators, which bring together two sources:

• Signavio-driven apps
  Apps that are registered as primary or associated executables in processes modelled in Signavio. These are imported from Signavio into the tracker on a regular cadence and flagged as selected.

• Manually selected apps
  Apps that are required but do not naturally sit inside a Signavio business process (for example system setup, configuration, support, or technical/admin apps). These are explicitly flagged as selected in the tracker.

Why it matters: by combining the full SAP catalogue with clear selection flags, the tracker provides the Tech team with a reliable, deduplicated list of apps that are actually in scope per POD, enabling controlled deployment, role and authorisation design, and impact assessment.

How apps are selected and flagged in the tracker

• From Signavio (automatic): a report loads apps referenced in Signavio models into the tracker every two weeks.

• From consultants (manual): Supportive apps that don’t appear in Signavio because they aren’t part of a business process flow can be selected manually.

Each app is identified by an App ID taken from the SAP Fiori Apps Library. This also provides details about the functionality of each app, technical prerequisites, etc. 

Who should use this

• Functional consultants
  Validate that the apps already selected via Signavio or agreed manual requests are correct, and track approval and deployment status.

• Tech team
  Use the tracker as the governance and deployment control, exposing apps and updating deployment status (for example marking apps as Deployed in DEV).

What you can edit

In the Tracker sheet, functional teams may update only the following fields:

• Manual Selection
  Set to TRUE only when an app is required but does not belong to a business process and therefore cannot be captured in Signavio (for example configuration, setup, monitoring, or technical/admin apps).
  This must not be used for apps that should be modelled in Signavio.

• POD
  Select the POD or PODs that require the manually selected app. This indicates ownership and demand for the manual request.

All other columns are reference data or are maintained by the Tech team as part of governance and deployment.

Steps to manually select non-Signavio apps:

• Locate the app
  In the Tracker sheet, use Ctrl+F or header filters to find the app by App ID or App Name. The SAP Fiori Apps Reference Library can be used to help identify the correct app.

• Validate the app
  Use the URL link (“Open Fxxxx”) to open the SAP Fiori Apps Reference Library and confirm that it is the correct app.

• Flag as required
  Set Manual Selection to TRUE.
  Only do this when the app does not belong to a business process and therefore cannot be captured in Signavio.

• Assign requesting POD(s)
  In POD, select all PODs that require the manually flagged app (multi-select).

Governance for GUI and Web Dynpro Executables

A governance step applies to all classic SAP GUI and Web Dynpro transactions that appear in the Signavio export. Everything imported from Signavio that is not a Fiori app will automatically be set to Status = “Awaiting Approval”. This rule is enforced by Bhargavi Narahari.

The steps for approval are:

• The functional team raises all GUI and Web Dynpro requests with Bhargavi and requests approval.
• NARAHARI-ext, Bhargavi reviews the request and confirms whether the classic executable is required or whether a Fiori alternative must be used.
• Once Bhargavi approves the request, she provides written confirmation by email to Tech team
• After the Tech team receives this email, we reset the status from “Awaiting Approval” to “Not Started”.
• This authorises the request to enter the deployment pipeline, where it will progress through In Process, Ready for Test, and Deployed in ERD.

This governance step is mandatory and applies to all PODs.

Column guide (only what you touch)

• App ID / App Name – identifier and title of the standard SAP app from the SAP Fiori Apps Library.

• Manual Selection – TRUE = required; FALSE = not required.

• POD – multi-select; pick all PODs requesting the app.

• URL – opens the SAP Fiori Apps Library entry to verify details.

• Status – maintained by Tech (read-only for you), shows deployment progress.

  • “Awaiting Approval” is used for all classic transactions (SAP GUI and Web Dynpro) to confirm there is no suitable Fiori alternative before deployment.

  • "Deployed in ERD" is the final state.

Note

Cadence and steps may evolve as we fine-tune the process and as team capacity changes. This page will be updated as the tracker matures.