Page under active update (12/03/2026 - 13/03/2026) This document is currently being revised. Content may change. |
Governance step applies to all GUI and Web Dynpro transactions coming from Signavio. |
Signavio is the primary source for identifying and managing application requirements.
All functional consultants must capture required applications in Signavio against the relevant business processes. This includes All Executables. The project relies on Signavio as the authoritative source for determining which applications are required.
The Fiori Tracker is not the place where application requirements are defined.
The Tracker is primarily a deployment tracking tool used by the technical team to monitor the progress of application deployment in ERD and subsequent environments. The Tracker is automatically updated from the Signavio export every Thursday.
The Tracker is not used to define or request applications. It simply shows the current ERD deployment status of apps already captured in Signavio. See General Rule next. |
1. Capture application requirements in Signavio
Model the application in the relevant business process using Primary, Associated or Alternative Executables.
2. Use the Tracker only as a visual check to see the status of your applications that come from Signavio
Functional and business consultants should look at the Tracker to see:
• whether the app has been deployed.
The Image shows Apps ready in ERD and ready for testing. (Post ERD Status = 'Deployed in ERD' If you cannot access the App in ERD Launchpad then create a Jira Task, see section How to raise a Jira Task?)
• whether the app requires approval from the Integration team ( See Governance section in this doc for further details)
• whether there are technical issues or notes recorded by the Tech team while deploying App in ERD
• whether the app was rejected. This will be due to Integration Team Governance step, Check the App Approvals sheet or contact integration team for reasons. ( See Governance section in this doc for further details)
3. Be aware of the weekly update cycle
The Tracker is updated from Signavio every Thursday. Check the “Signavio Update Date” in Row 1 of the Tracker. If changes were made in Signavio after that date, they will appear in the Tracker after the next Thursday update.
If there is uncertainty about where an application should be captured, always begin with Signavio. For guidance on the correct modelling approach, contact the Signavio Team. For Governance and app approvals approach the Integration team For App deployed in ERD technical issues, e.g. App not visible in ERD Launchpad, App Visible but producing error etc, Raise a Jira Task for Technical Team (See How to |
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.
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.
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).
Jira tickets are raised for technical team to address Technical issue, once your app status shows 'Deployed in ERD' if you are still facing issues you can follow the instruction is this guide Jira Task
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:
This governance step is mandatory and applies to all PODs.
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.
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.