Apps and extensions for SAP

From a lean Fiori screen to an add-on: we extend your SAP system where your processes need more than the standard. Cleanly separated and upgrade-proof.

The SAP standard covers a lot, but not everything. Every company has workflows somewhere that need their own screen, an extra field or their own logic. The art lies in closing these gaps without blocking the system.

We build Fiori apps and extensions that follow the SAP guidelines: cleanly separated from the standard, documented and built so the next upgrade does not become a project. Delivery happens together with our partner Exsapt, while technical leadership and quality assurance stay with STROWA.

Why clients get in touch

Data entry takes too longA standard screen with thirty fields, four of which are actually needed.
The shop floor works on paperConfirmations and withdrawals run on printed lists and get typed in at the end of the shift.
A form no longer fitsA new layout, new languages or a new printer, and the old form printing cannot keep up.
The developer who built it has leftThe extension runs, but nobody understands it and nothing is documented.

Services

What we build

Individual apps or the extension landscape of a whole project.

Fiori apps

Screens for tasks that take too many clicks in the standard. At the desk and on a tablet on the shop floor.

Extensions within the SAP standard

BAdIs, extension points and custom logic, cleanly separated from the standard and upgrade-proof.

Forms and outputs

Delivery notes, labels and order papers: correct, readable and where they are needed.

Custom applications

Add-ons for workflows the standard does not offer, from entry to evaluation.

Replacing legacy developments

Understanding, cleaning up or replacing code that has grown over the years, especially ahead of a move to SAP S/4HANA.

Testing and acceptance

Test cases, acceptance with your key users and documentation your team can build on.

How we work

From requirement to handover

Step 1

Sharpen the requirement

We look at the actual workflow and first check whether the standard or a setting already covers it.
Step 2

Specification

A description your department can read and a developer can implement without follow-up questions.
Step 3

Build and test

Development in the Exsapt team, code review on our side, acceptance with your key users.
Step 4

Handover

Documentation, source code and knowledge stay with you.

What you get

Why this works

Little code

Every line we do not write is one nobody has to maintain later, or migrate to SAP S/4HANA.

Usability first

An app that saves three clicks gets used. One that is merely pretty does not.

You keep everything

Source code and documentation belong to you, with no lock-in.

Questions

Frequently asked

Fiori or classic screens?

For new developments Fiori is the way to go, especially with SAP S/4HANA in view. We replace existing screens where the benefit justifies the effort, not across the board.

What does a Fiori app cost?

A lean app for a clearly defined workflow often takes just a few development days. The preparation is decisive: the clearer the requirement, the shorter the build. With development through Exsapt, daily rates sit well below Swiss levels.

Do you also build on existing extensions?

Yes. Taking over, cleaning up and documenting code that has grown over the years is one of the most frequent requests.

Contact

Are your users missing an app or a field?

Describe the workflow. We will tell you whether it needs development or just a setting.

Describe your requirement