Services SAP Fiori & UX

SAP Fiori Consultancy & Implementation

SAP Fiori makes SAP processes intuitive, mobile, and user-friendly. Tycom supports you from evaluation and defining use cases through to successful implementation – with process understanding from across industry and the mid-market.

Enquire now

Initial situation

SAP in use – but not fully exploited

Many companies have been using SAP for years, yet a lot of processes still run separately: analyses in Excel, status requests via e-mail, approvals over the phone. Not because SAP can't do it, but because the interfaces aren't inviting enough to actually use it.

Especially with S/4HANA Migrations it becomes clear how much added value can be generated – or remain unused – through a well-thought-out Fiori strategy.

SAP is bypassed rather than used

If the user interface is too complex, employees resort to Excel and email – data outside the system, a lack of transparency.

Acceptance is lacking – training helps little

New features are being introduced, but not used. Not due to employees' willingness – but due to interfaces not built for everyday use.

S/4HANA potential remains untapped

Only those who can access functions intuitively will use them. Without an UX concept, the investment in S/4HANA remains undervalued.

Three approaches

Where are you with Fiori?

Implementing SAP Fiori doesn't always mean the same thing. What's crucial is which strategy suits your system landscape, your processes, and your organisation.
In the consultation, we will clarify together where you are.

New with S/4HANA

Flowers from the start

Who Introducing S/4HANA, has the chance to establish Fiori as the primary UX standard right from the start – without legacy issues and with maximum future-proofing.

Suitable if:

Planned S/4HANA Greenfield implementation
Standard processes dominate

Existing SAP landscape

Phased modernisation

Don't change everything at once, but introduce Fiori where the added value is greatest – prioritised, controlled and without risking ongoing operations.

Suitable if:

Extensive brownfield environment available
Many individual customisations in the system
Modernisation must proceed step by step

Complex processes

Customer-centric

First understand how your employees really work, then design the appropriate Fiori solution. Technology follows process, not the other way around.

Suitable if:

Complex role and process landscapes
Acceptance and productivity are critical
UX understood as a business lever

Request a free initial consultation

Wo Fiori makes the biggest difference

Typical areas of application for SAP Fiori apps

Individual SAP Fiori apps are particularly useful when processes are repetitive and require many clicks, involve multiple roles and approvals, need to consolidate information from different areas, require structured approval workflows, or when the app must be usable on the go – directly on the production floor.

Production Control & MDE

Workers on the machine need a simple, fast interface – not a SAP transaction with 40 fields. A custom-built Fiori app displays exactly what's relevant at that moment: order, quantity, status. Done.

Maintenance and upkeep

Field technicians work with tablets or smartphones. A bespoke app for fault reports, job feedback, or checklists saves time and reduces errors – without the need to go back to the office.

Logistics & Warehousing

Goods receipt, stock transfer, inventory – processes that occur hundreds of times a day. An optimised Fiori app makes the difference between 30 seconds and 3 minutes per transaction.

Authorisations & Approvals

Holiday requests, order approvals, invoice checks – structured approval processes can be mapped as a lean Fiori app that works on any device and directly informs approvers.

Making flowers a reality – together.

We analyse your SAP landscape and show you where SAP Fiori delivers the greatest added value.

Request initial consultation

Our services

What we specifically do for you

From initial analysis to productive deployment – our services cover the entire Fiori implementation path. Technically clean-core oriented: Development with RAP, CAP, and SAP BTP – upgradeable, maintainable, without technical debt.

Initial analysis & potential assessment

We'll explore together how SAP is used at your organisation – which processes are suitable for Fiori, and where quick wins are possible.

UX Strategy & Use Case Definition

User and role-based analysis. Clear prioritisation: standard apps versus individual development. Outcome: roadmap.

Fiori Configuration & Activation

Technical setup, activation of standard apps, Launchpad, SSO and authorisation concept – complete and clean.

Project support

We accompany the entire implementation – project management, quality assurance, go-live support, and user training.

Training & Knowledge Transfer

We train IT departments and business units so that your teams can independently use, maintain, and further develop Fiori.

Bespoke Apps

Some processes cannot be mapped with standard. We develop tailor-made Fiori apps for practice.

From idea to implementation

Our approach

From the initial idea to the production-ready app: our approach ensures clarity, structure, and a reliable outcome.

Stage 1: Free initial consultation

A joint clarification of your requirements, system landscape, and objectives. No pitch, but a genuine conversation. Free and without obligation.

Arrange a meeting

Stage 2: Analysis & Workshop

We analyse your processes and develop a precisely tailored technical and business concept, including prioritisation.

Stage 3: Design & Implementation

Our implementation of the Fiori solution: from mock-ups through development and configuration to handover and training.

Tyrolit AG – Our Roots

Tycom originates from the industrial SAP operations of Tyrolit AG. The areas of application for our Fiori apps are not theoretical – they stem from real projects in productive operation. What runs at Tyrolit every day, we are now making accessible to other SAP customers.

Learn more

30+

Years of SAP in practical operation

4.500+

Employees worldwide – Fiori in daily use

25+

SAP projects in an industrial environment

Philipp Steidl

Lead Developer

„Before I configure a single line, I want to understand how people actually work.“

Request initial consultation

Making SAP Fiori concrete – together.

We analyse your SAP landscape and show you where SAP Fiori offers the greatest added value – tailored to your processes, your system landscape, and your team.

Frequently Asked Questions

Is SAP Fiori already included in our S/4HANA license?

Yes – SAP Fiori is part of SAP S/4HANA. Many standard apps are already licensed. Individual extensions may require an SAP BTP license depending on the approach – we can clarify this in the initial consultation.

Der Hauptunterschied zwischen SAP GUI und SAP Fiori ist die Benutzeroberfläche und das Benutzererlebnis. SAP GUI ist die traditionelle und weit verbreitete Benutzeroberfläche für SAP-Anwendungen, die auf Desktop-Computern ausgeführt wird. Sie bietet eine umfangreiche Funktionalität, kann aber manchmal als veraltet und komplex für neue Benutzer empfunden werden. SAP Fiori hingegen ist eine moderne, rollenbasierte und benutzerfreundliche Benutzeroberfläche, die für eine Reihe von Geräten, einschliesslich Desktops, Tablets und Smartphones, optimiert ist. Sie bietet eine vereinfachte und intuitive Benutzererfahrung, die auf die spezifischen Aufgaben eines Benutzers zugeschnitten ist.

SAP GUI is the classic user interface – powerful, but complex. SAP Fiori replaces or supplements it with role-based, intuitive apps. The difference: Fiori shows each user only what they need for their task.

What is the duration of an SAP Fiori implementation?

The activation of individual standard apps can be achieved in a few days. A structured rollout with analysis, configuration, and training typically takes 6–12 weeks. In the workshop, we will collaboratively define a realistic timeline.

What needs to be considered during an S/4HANA migration?

An S/4HANA migration is the ideal time to get the Fiori strategy right from the outset – not as a follow-up project. Those who define the UX strategy in parallel with the migration avoid employees having to work with the same uncomfortable interfaces afterwards.