Philosophy¶

Before deciding to use Fiori Tracker suite, it's a good idea to understand the philosophy behind the project. That way, you can make sure it fits with what you're trying to achieve.

Design principles¶

Build to free the team from routine work - We noticed in our first SAP S/4HANA implementation that routine tasks often distracted developers and other team members from key work. One example is explaining how to identify SAP Fiori applications and what is needed to enable them for end users. We build Fiori Tracker to get rid of those mundane tasks and focus on our main goals.

Enables asynchronous work - Maximizes benefits of remote and asynchronous work, empowering team to do deep focused work without distractions. It achieves this by assigning unique identifiers to all SAP Fiori content objects and establishing clear responsibility.

Made to blueprint - Besides the system setup, maintaining records of the intended system configuration streamlines SAP S/4HANA deployment and support. This clear distinction between planning and execution minimizes delays.

Accessible for all team members - Available in your SAP landscape, for example in QA system with the same SAP users your team already has.

Connected with actual system setup - Actual SAP Fiori setup and SAP project most popular apps.

Open for further development - Since first customer implementation in 2018 we have rebuild the Fiori Tracker Suite multiple times to accommodate new types of content and relationships. Each new relation leverages the existing pool of content types. Moreover, the suite is open to customer-specific extensions that may not be included in official releases.

.