How to add a mobile app to SAP S/4HANA
Short answer
Use Fiori apps on a rugged device when they cover your process; build a custom app on released OData APIs when you need scanning, offline use or a simpler task flow. Authenticate through SAP identity services, sync with a mobile backend, and post transactions through the same APIs that desktop apps use.
S/4HANA ships with Fiori apps that run in a mobile browser, and for managers approving requests that is often enough. The shop floor is different. Operators scan labels, report time on a production order, move stock between storage locations and record scrap while holding a part with gloves on, sometimes in a plant with weak Wi-Fi.
The decision is between configuring standard Fiori, extending it, or building a purpose-built app. Standard apps are supported and upgrade safely, but they are designed for broad process coverage rather than one fast scan-and-confirm task. A custom app can be much faster for a single job but is something you must own.
This page lays out the S/4HANA interfaces, the architecture choices around offline and identity, and when a warehouse management or extended warehouse scenario already covers your needs with the RF framework.
What teams use it for
Production confirmation and labor reporting
Operators scan a production order barcode, start and stop an operation, enter good and scrap quantities and reason codes. The app posts a confirmation through the production order confirmation API.
Goods receipt against purchase orders
Receiving staff scan the PO and the supplier label, enter quantity and storage location, and post the goods receipt, with a quality hold option for incoming inspection.
Stock transfers and cycle counts
Move material between storage locations or bins and record physical inventory counts by scanning labels, using the material document and physical inventory APIs.
Maintenance rounds and notifications
Technicians view assigned maintenance orders, record time and parts used and create notifications with photos from the plant floor.
Quality inspection results
Inspectors enter measured values against an inspection plan and record defects with pictures, writing results into the inspection lot.
Approvals on the go
Managers approve requisitions and orders from a phone using the standard workflow tasks, with a simplified summary and biometric unlock.
SAP S/4HANA integration surface
- Released OData services for production orders and confirmations, material documents, physical inventory, maintenance orders and inspection lots; verify names and versions on the SAP API Business Hub for your release.
- SAP Fiori launchpad and Fiori apps on mobile browsers, and SAP Mobile Services with the SAP BTP SDK for iOS or Android for native or offline-capable apps (check current SDK support and lifecycle).
- Extended Warehouse Management RF framework or WM-style RF transactions for scanner-driven warehouse work, which may already cover goods movements on handheld devices.
- SAP Fiori Client or Mobile Start options for packaging and device management, where licensed.
- Identity through SAP Cloud Identity Services or your identity provider with SAML or OIDC, and device certificates via your MDM tool.
- Cloud Connector or a reverse proxy to expose only needed services from an on-premise S/4HANA to the mobile backend.
How it works
- 1
Map tasks to the right tool
List each mobile task, the user and the device. If a standard Fiori app or the RF framework already does it, use it. Build custom only for gaps.
- 2
Design a minimal task flow
Shop floor apps should need two or three taps per transaction. Pre-fill plant, work center and user. Use scanning for identifiers and avoid typing.
- 3
Choose offline strategy
If connectivity is reliable, an online web app is simplest. If not, use a native or PWA app with local queues, replay with idempotency keys and clear conflict messages.
- 4
Build a thin mobile backend
The backend authenticates devices, maps users, calls S/4HANA APIs, enforces business rules (for example, no confirmation above order quantity) and returns small payloads suited to mobile.
- 5
Integrate scanning and hardware
Support camera scanning and dedicated scanner intents. Standardise label formats, such as GS1 barcodes or SAP handling unit labels, so a scan resolves unambiguously.
- 6
Pilot on one line
Deploy on one cell or dock, compare transaction timing and error rates with the old method, and fix friction before scaling.
Example flows
Scan to confirm a production operation
Trigger: An operator finishes an operation at a work center.
- The operator scans the production order traveler barcode.
- The app loads the open operations for that work center.
- The operator enters good quantity and scrap with a reason code.
- The backend posts the confirmation through the API and updates remaining quantity.
- If the call fails offline, it queues with an idempotency key and retries.
Result: Confirmation happens at the machine in seconds, so work in process data is current instead of end of shift.
Goods receipt with quality hold
Trigger: A truck arrives at the receiving dock with a PO.
- The receiver scans the PO number and each supplier label.
- The app compares quantity with open PO lines.
- The receiver chooses a stock type, unrestricted or quality inspection.
- The goods receipt posts through the material document API and the label prints.
Result: Stock is received to the right stock type immediately, and quality sees inspection lots without waiting for paperwork.
Keeping data on-prem
A mobile app can work entirely on-premise: devices join plant Wi-Fi or private 5G, the mobile backend sits in your DMZ or internal network, and it calls S/4HANA directly. Use MDM to manage devices and certificates, and avoid public app stores for internal builds if policy requires private distribution. Where Mobile Services on SAP BTP is not allowed, a self-hosted backend with the same API calls achieves the same result. If you add AI features, such as photo defect classification or voice notes into structured reports, use open-weight models on local servers so images and plant data never leave the site.
Security checklist
- Authenticate users with SSO and device certificates; require screen lock and remote wipe through MDM.
- Give the mobile backend a technical user with only the required APIs and propagate the real user where posting must be personal.
- Encrypt local storage for offline queues and purge it after sync or logoff.
- Validate quantities, storage locations and statuses server-side; never trust the client.
- Restrict photos and attachments for controlled programmes, and avoid caching drawings on devices.
Ways to get it done
Standard Fiori apps and RF framework
Effort: Low to medium, configuration and role setup.
Best first stop. Supported, upgrade-safe and often sufficient, especially for warehouse scenarios already using EWM or WM RF.
Custom app on Mobile Services or your own backend
Effort: Typically two to three months for a first production-quality app with testing and device rollout.
For tailored scan-and-confirm flows, offline operation or non-SAP data in the same screen.
Netray-built mobile workflow
Effort: Pilot around one workflow in weeks; broader rollout depends on devices and sites.
When you want mobile plus AI features such as defect photo triage, voice reporting and natural-language lookups, with private models.
Pitfalls
- !Building a custom app for something a standard Fiori app already does adds long-term maintenance for little gain.
- !Offline posting without idempotency keys causes duplicate confirmations or goods movements.
- !Poor label quality kills adoption faster than poor software. Test scanning on real, dirty or curved labels.
- !Ignoring authorisation mapping means operators either see too much or hit errors that look like app bugs.
- !Skipping a pilot: line-level realities such as gloves, glare and shared devices change the design.
Frequently asked questions
Is there a standard SAP mobile app for S/4HANA?
There are Fiori apps usable on mobile browsers and, depending on licensing, mobile start and Fiori client options. The exact set differs by release and edition. For scanner-heavy shop floor tasks, many teams extend or build their own.
Can we use the warehouse RF framework instead?
If you run EWM or WM, the RF framework supports handheld scanning of picking, putaway and moves, and is usually the best choice for warehouse tasks. Production confirmations and maintenance are separate and may need other apps.
Do we need offline support?
Only if connectivity is unreliable where work happens. Warehouses and shop floors with stable Wi-Fi can run online, which is simpler. For field service, basements or remote sites, plan for offline queues and conflict handling.
How do we post as the real user?
Use SSO with principal propagation through Cloud Connector or a trusted token exchange so S/4HANA sees the user's identity. Where that is not possible, post with a technical user and record the real user in a reference field, accepting weaker audit.
Can we use AI on the device?
Yes for photo defect classification, voice-to-report and natural-language lookups. Run models on servers in your plant for privacy and latency, and keep the app responsible for capturing data and showing results.
Want Mobile app working on your SAP S/4HANA?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment