When you build next to SAP
- You are migrating from ECC to S/4HANA and have to take data along.
- SAP does not offer the functionality or the flexibility to set it up on the SAP platform.
- Setting it up in SAP costs too much.
What we do
The options side by side
We show which options there are to build next to SAP, and what each option asks of your organisation and of SAP.
Assessment
We assess what you can solve with low-code or with FlightDeck.
Building on FlightDeck
We build the concrete functionality that is not in SAP, on our FlightDeck and integrated with SAP.
Setting up FlightDeck for you
We set up FlightDeck in your organisation, including SAP connectors, so your teams can start working with FlightDeck themselves and build their own applications.
Integration: the way SAP intends it
An interface with SAP should follow the rules of SAP. We first read out which standard interfaces your system offers and choose the most modern one available. Every data question gets one verifiable object, the versions are recorded and SAP itself checks every posting. That way an interface keeps working after an upgrade and you know which data goes where.
How the assessment works
In the SAP architecture assessment we look at what you can solve next to SAP with low-code or with FlightDeck.
-
Your question
You tell us what you want to build and what prompted it.
-
The conversation
A conversation with Erwin about your SAP system, your processes and what you need.
-
The options
You receive on paper what you can solve with low-code or with FlightDeck and what the first step is.
-
Your choice
You decide what to do with it.