Digitize processes in SAP without the wait.
You build Fiori apps by drag and drop right inside your SAP system, with no middleware. This works on-premise, in the private cloud and now also in the SAP Public Cloud. The first app is usually live within a few days.
The standard fits. Your process doesn't.
The moment a workflow deviates from the SAP standard, the waiting begins: for IT, for budget, for the next release. In the meantime, people make do with paper.
The IT queue
Every process change becomes a project and lands behind twenty other tickets.
Paper as a stopgap
Lists, travelers, Excel. Whatever gets created once tends to stay for years.
Siloed knowledge
Only three people know the special workflows. If one is out, the process stalls.
Costly workarounds
Rebookings, double entry, troubleshooting. Costs nobody budgets for.
Three steps to a production-ready app.
Describe the process
You define what should happen at the workstation: fields, checks, postings.
Click the app together
Put building blocks together by drag and drop, with AI assistance along the way. You write no frontend code.
Roll out and adjust
Live in the SAP system, on every device. Adjustments take days instead of a full release cycle.
One app, one browser. The interface adapts to screen size, scanner and touch input.
Handheld scanner
Confirmations, inventory counts and postings right at the material.
Industrial tablet
At the workstation on the line, easy to read and usable with gloves.
Handheld with scan grip
For goods receipt and picking with many scans per day.
One tool, three perspectives on the same process.
Manufacturing, logistics and SAP each look at a mobile app differently. Choose the entry point that fits your work.
The machine is running. The system isn't ready yet.
A changeover, new material, a new workflow, and the process in the system no longer fits. Until the change arrives, people rebook and improvise.
Special requirements turn into a permanent workaround.
New customer, different handling: packaging, labeling, forklifts. The system processes lag behind, and paper lists pile up in the yard.
No custom code for every little thing.
You build the logic once, cleanly, in the standard and give the business a controlled framework. Transport, authorizations and release capability stay with you.
Everything stays in your SAP system. In the Public Cloud, too.
The Mobile Builder runs as an ABAP application in your system, with no middleware and no data leaving it. Authorizations, documents and logs stay where they belong: audit-ready and Clean Core compliant.
Anyone moving to S/4HANA now should not write special processes back into the core. The Mobile Builder keeps them outside the core.
Tablet · scanner · phone
Fiori
ABAP, in your system
On-premise · Private · Public Cloud
Frequently asked.
Does the Mobile Builder run in the SAP Public Cloud?
Yes. The Mobile Builder runs on S/4HANA on-premise, in the private cloud and in the SAP Public Cloud. You don't need middleware, and no data leaves the system boundary.
How long does the first production app take?
Usually a few days. Most of the work goes into clarifying the process, not into building the app itself. The Check helps with that.
Can business departments build apps themselves?
Yes, within a framework that IT defines. Authorizations, approved building blocks and transport paths stay under your control.
What happens during an S/4HANA upgrade?
Apps keep running because only approved interfaces are used. We provide a compatibility statement for every release.
Which devices are supported?
Anything with a browser, with no additional app installation: industrial tablets, handheld scanners, smartphones. All you need is an HTML5-capable standard browser (SAP recommends Google Chrome). The interfaces are Fiori-based and optimized for gloves and scanners.
How many workarounds are running in your operation?
In 30 minutes we look at one concrete process together and tell you honestly what is possible. Free of charge.