A Note for Functional and Business Consultants

Signavio is the primary source for identifying, capturing, and managing application requirements.

• All functional consultants must capture required applications in Signavio, linked to the relevant business processes. This includes all Executables associated with those processes.
• The project relies on Signavio as the authoritative source for determining which applications are required.
• The Fiori App Tracker is not used to define application requirements.
• The Tracker is primarily a deployment monitoring tool used by the Tech team to track the progress of application deployment in ERD and subsequent environments.
• The Tracker is automatically updated from the Signavio export every Thursday.
• Functional and business consultants should therefore use the Tracker only to verify the status of applications already captured in Signavio.

General rules for consultants

1. Capture application requirements in Signavio

Applications must be modelled in Signavio within the relevant business process using:

• Primary Executables

• Associated Executables

2. How to use the Tracker to check the status of applications

Functional and business consultants should consult the Tracker to verify:

• whether the application has been deployed in ERD

• whether the application requires approval from the Integration Team

• whether there are technical notes or deployment issues recorded by the Tech Team

• whether the application was rejected during governance review

Examples:

The image below shows applications that have been deployed in ERD and are ready for testing.

NOTE: If ERD Status = "Deployed in ERD" but the application is not accessible in the ERD Launchpad, create a Jira task for the Tech Team (see “How to raise a Jira Task?”).

The next two images show applications awaiting Integration Team approval and applications with an approval status (Approved or Rejected). See the Governance section for details.

The image below shows examples where the Tech team recorded technical notes or deployment issues during ERD deployment.

Whether the application was rejected during Integration Team governance review. Check the App Approvals sheet or contact the Integration Team for the reason.

3. Weekly Update Cycle

• The Tracker is updated from the Signavio export 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 during the next Thursday update cycle.

• Technical Team deployment activities start immediately for apps that do not require approval.

• The Integration Team reviews approvals on an ad-hoc basis. Follow up with them directly for status.

What this Tracker is

The Fiori App Tracker is a central governance and deployment tracker for SAP applications selected for the project. It is used by the Tech Team to deploy applications, by the Integration Team to assess and approve requests, 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 applications and should not be interpreted as project scope.

Some solutions are not part of the SAP S/4HANA Private Cloud 2025 Fiori catalogue (for example GTS or AFC). For these cases, the POD must capture the applications in a spreadsheet and send them to the Integration Team for approval. After approval, the Signavio Team loads the applications as Executables in Signavio, and the UX Team adds the applications to the Tracker.

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

• Signavio-Driven Apps
  Applications captured as Executables within business processes modelled in Signavio. These are imported from Signavio into the Tracker every Thursday.
  
  

• Manually Selected Apps
  Applications that are required but do not naturally belong to a Signavio business process (for example system setup or technical/admin applications). These require a selection process through the “Manual App Selection” sheet (see section How to Select non-Signavio Apps).

How to Select non-Signavio Apps

16/03/2026 - A “Manual App Selection” sheet is being developed to capture requests from functional and business consultants for applications that cannot be captured in Signavio.

This sheet is currently under development. Once the process and automation are finalized, an announcement will be posted in the “Tracker Announcements” sheet.

Governance for GUI, Web Dynpro, and Suggested Executables

A governance step managed by the Integration Team applies to SAP GUI transactions, Web Dynpro applications, and Suggested Executables imported from Signavio. To support this process, a separate sheet called “App Approvals” has been created in the Fiori Tracker spreadsheet.

The approval process differs for Suggested Executables compared to SAP GUI and Web Dynpro applications. The explanation is therefore split into the sections below.

1. For SAP GUI and Web Dynpro:

All Executables imported from Signavio that are not SAP Fiori apps will automatically have their ERD Status set to “Awaiting Approval” in the Tracker. These applications are also automatically copied to the App Approvals sheet.

Example:

The Tracker sheet is updated with application SM35. Because this is an SAP GUI transaction, the ERD Status is automatically set to “Awaiting Approval”, and the application is copied to the App Approvals sheet (see next image).

POD teams must provide justification in Column H 'Justification' of the App Approvals sheet for Integration Team review.

The steps for GUI and Web Dynpro

• The Tracker is updated from the Signavio export every Thursday.
• SAP GUI and Web Dynpro applications are automatically assigned “Awaiting Approval” in Column I (ERD Status).
• These applications are automatically copied to the App Approvals sheet.
• POD teams must enter a justification in Column H of the App Approvals sheet.
• The Integration Team reviews the App Approvals sheet and may contact the POD for clarification or assign an approval status.
• The approval status entered in Column I (Approval) of the App Approvals sheet automatically updates Column J (Integration Approval) in the Tracker.
• If approved, the Tech Team deploys the application. If rejected, the Tech Team sets Column I (ERD Status) in the Tracker to Rejected.
• For queries, delays, or urgent deployment requests, contact the Integration Team.

2. For Suggested Executables:

• All Suggested Executables imported from Signavio are captured in the App Approvals sheet.
• Suggested Executables require approval from the Integration Team.
• After approval, the Signavio Team converts the Suggested Executable into an Executable in Signavio.
  This allows the application to be captured in the Tracker during the next update cycle.

Example:

The steps for Suggested Executables

• The Tracker spreadsheet is updated from Signavio every Thursday. Suggested Executables will automatically appear in the App Approvals sheet.

• POD teams must enter a justification in Column H of the App Approvals sheet. This is the only action required from the POD team.

• The Integration Team reviews the App Approvals sheet on an ad-hoc basis. They may contact the POD for clarification or set the status to Approved or Rejected.

• The Signavio Team reviews the App Approvals sheet and updates Signavio by converting Suggested Executables into Executables.

• During the next weekly update, the Tracker will reflect these changes because the applications will now appear as Executables coming from Signavio. The approval status will remain recorded in the App Approvals sheet.

• For questions, delays, or urgent deployment requests, contact the Integration Team or the Signavio Team, depending on the step in the process.

Support: Where to Ask for Help

• Application capture and Signavio modelling questions – Contact the Signavio Team

• Governance and app approvals – Contact the Integration Team

• Technical issues after deployment in ERD – Raise a Jira task for the Tech Team (see section How to raise a Jira Task)
  Examples:

• • App not visible in ERD Launchpad
  • App visible but producing errors
    
    

How to raise a Jira Task?

Jira tickets should be raised for the Tech Team to resolve technical issues.
If an application shows “Deployed in ERD” but you still experience issues in the ERD Launchpad, follow the instructions in this guide:

 Jira Task – How to raise a ticket for the Tech Team ( The image below is extracted from the guide and highlights the most relevant section)

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.