A Note for Functional and Business Consultants

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.

General rule

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.

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, or technical/admin apps). These will require a selection process via 'Manual App selection' sheet (See section: How to Select non-Signavio Apps)

How to raise a Jira Task?

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 in ERD Launchpad then you can follow the instruction is this guide Jira Task to raise a ticket/task for tech team

Governance for GUI, Web Dynpro, and Suggested Executable Apps

A governance step applies to all classic SAP GUI, Web Dynpro, and Suggested Executables that appear in the weekly Signavio export.

For GUI and Web Dynpro:

 All imported 'Executables' from Signavio that are not a Fiori app will automatically be set to Status = “Awaiting Approval” in the Tracker sheet and automatically captured in 'App Approvals' sheet.

Example:

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.