What this tracker is

The Fiori App Tracker is a single place where functional consultants record the standard SAP Fiori apps required to run each business process. It brings 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.

• Manually selected apps – important apps that don’t naturally sit inside a Signavio process (e.g. apps used for system setup, configuration, support, or technical apps). These must be added directly in the tracker.

Why it matters: it gives the Tech team a reliable, deduplicated list of required apps per POD so we can plan deployment, roles/authorizations, and change impacts.

Where the apps come from

• 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 – confirm which apps are required and manually select additional supportive/setup apps the business will need.

• Tech team (FYI) – uses the consolidated view to expose apps, and will set Deployed in DEV when an app is available.

What you can edit

In the Tracker sheet, you can edit only:

• Manual Selection – set to TRUE to indicate “we need this app.”

• POD – choose one or more PODs requesting the app (multi-select).

Other columns are reference or maintained by Tech.

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.

How to manually add apps

1. Open the Tracker sheet: use Ctrl+F or header filters to find an app by App ID or App Name. Use the SAP Fiori Apps Library to help locate relevant apps. 

2. Confirm the app: click the URL link (“Open Fxxxx”) to open the SAP Fiori Apps Library and validate it’s the correct app.

3. Mark it as required: in Manual Selection, choose TRUE.

4. Select requesting POD(s): in POD, choose all PODs that need the app (multi-select).

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.