SAP S/4HANA & ECC
S/4HANA on-premises and Cloud (Public, Private), ECC 6 with modern kernel, Business One. Custom ABAP, BAdI, enhancement spots, RFC modules.
SAP Mobile Apps
Mobile apps on SAP stack — Fiori, BTP, S/4HANA.
VOGO develops mobile apps on the SAP ecosystem: Fiori (UI5), SAP BTP (Cloud Application Programming Model), SAP Mobile Services, mobile extensions for S/4HANA. Mobile modules for SAP MM / WM (warehouse), PM (plant maintenance), SD (sales), HCM / SuccessFactors (employee self-service). We respect "clean core" — extensions on BTP, not modifications in S/4HANA.
SAP S/4HANA
SAP Fiori / UI5
SAP BTP
CAP (Cloud Application Programming)
SAP Mobile Services
OData v2 / v4
SAP Build Apps
Why SAP mobile
SAP-native mobility, not improvised adaptation.
Building mobile apps on SAP requires real knowledge of the stack: ABAP, BAPI, OData, IDoc, BTP, Fiori. VOGO has a team with concrete SAP experience — not "we integrate anything via REST".
Clean core, extensions on BTP
SAP recommendation is clear: do not modify S/4HANA; build extensions on BTP. Our mobile apps consume standard S/4HANA OData and use CAP for custom logic — so S/4HANA updates never break your mobile.
Fiori vs. native vs. hybrid
Fiori (UI5) — ideal for executive approvals, employee self-service, quick access through Launchpad. Native — for warehouse, field sales, industrial scanner. Hybrid — we combine both for optimal cost / experience coverage.
SAP Mobile Services (SMS) or custom alternative
For push notifications, offline sync, mobile analytics — we use SAP Mobile Services on BTP (recommended). If you don't have SMS in licenses, we build alternatively on Azure / AWS with the same feature-set.
We know ABAP, OData, BAPI
Our team writes ABAP when necessary (RFC exposure as OData, custom BAdI, enhancement spots). We don't "pass the requirement to a third-party SAP consultant" — we deliver end-to-end.
What we deliver
The capabilities of VOGO SAP Mobile.
SAP-certified
SAP-recommended patterns (clean core, BTP-first)
Multi-OS
iOS, Android, Web — same Fiori or cross-platform codebase
EU hosted
SAP BTP in EU, GDPR by design compliance
EN/RO support
Bilingual technical support — no L2 escalation
Use cases
SAP-mobile modules we do.
SAP MM / WM mobile (warehouse mobility)
Goods receipt, picking, putaway, transfers, inventory, direct integration with SAP MM (Materials Management) and WM (Warehouse Management) or EWM (Extended Warehouse Management) modules. Industrial device support Zebra, Honeywell.
SAP PM mobile (plant maintenance)
Intervention list for technicians, equipment file, intervention report, parts consumption, customer signature. Integration with SAP PM, work orders, maintenance notifications, preventive maintenance plan.
SAP SD mobile (sales force automation)
Product catalog with prices per customer (from SAP SD condition technique), order placement, scheduled visits, customer signature storage, optimized maps and routes. Integration with SAP SD for direct order entry.
SAP HCM / SuccessFactors mobile
Leave requests, payslips, HR announcements, events calendar, training, manager approvals. Integration with SAP HCM on-prem (with Gateway) or SAP SuccessFactors (Public APIs).
SAP Ariba sourcing & procurement mobile
Purchase request approvals, supplier orders, invoice validation (3-way match), contract viewing. Integration with SAP Ariba (Sourcing, Buying, Contract Management).
SAP executive dashboards (Fiori cards)
Fiori dashboards for managers — daily sales, critical stocks, project KPIs, cash-flow. SAP Analytics Cloud embedded or Custom Fiori cards. Drill-down into S/4HANA.
Stack & integrations
The SAP technologies we use.
SAP Fiori / UI5
SAPUI5 framework, Fiori design system, Fiori Launchpad, Fiori Elements, Smart Templates. Custom apps + extension projects on standard Fiori.
SAP BTP & CAP
Cloud Application Programming Model (CAP — Node.js / Java), SAP HANA Cloud, SAP Build Apps, SAP Build Code, Workflow Service, Destination Service.
SAP Mobile Services
Push notifications (APNs / FCM), offline OData store sync, mobile analytics, app distribution. Custom alternative on Azure / AWS if SMS is not licensed.
SAP Identity & SSO
SAP Identity Authentication Service (IAS), Identity Provisioning Service (IPS), federation with Microsoft Entra / Okta / ADFS. SAML 2.0, OAuth 2.0 / OIDC.
Mobile apps
For non-Fiori parts: native Swift / Kotlin, Flutter, React Native. Integration with OData via SAPUI5 ODataModel or custom clients (Olingo, OpenAPI generator).
How we work
The VOGO SAP Mobile process.
Discovery (1-2 wks)
Workshop with SAP team & business owners. Identification of SAP modules touched (MM, SD, PM, HCM), SAP version, existing customizations.
OData audit & gap analysis (1 wk)
We verify existing OData services in S/4HANA, identify what's missing (gap), plan CAP services on BTP for gap.
PoC (3-4 wks)
End-to-end on a single important flow. We validate OData performance, authentication, offline sync.
Iterative development (8-20 wks)
2-week iterations. Fiori apps + native apps, regular demo. Tests on SAP transport landscape (DEV → QAS → PRD).
UAT & performance test on S/4HANA
Testing with end users. Load test on SAP Gateway / API Management. OData query optimization.
Go-live & maintenance
Progressive deploy on SAP transport, SAP Solution Manager / Cloud ALM monitoring, SLA-backed maintenance contract.
Frequently asked questions
FAQ — SAP Mobile Apps.
Which SAP versions do you support?
- S/4HANA on-premises and cloud (public, private edition).
- SAP ECC 6 (with modern kernel).
- SAP Business One.
- SAP SuccessFactors.
- SAP Ariba, SAP Concur.
For mobile extensions we prefer S/4HANA + SAP BTP, but we can also deliver on ECC if SAP Gateway / NetWeaver Gateway is available.
Do you use Fiori or native apps?
We decide by use case:
- SAP Fiori (UI5) — ideal for employee self-service, executive approvals, quick access through Launchpad.
- Native (Swift / Kotlin) or cross-platform (Flutter) — for apps with premium UX requirements, offline-first, industrial scanner.
We combine them: native for warehouse / sales force, Fiori for executive approvals.
What is SAP BTP and why does it matter for mobile?
SAP BTP (Business Technology Platform) = SAP's cloud platform for extensions. Includes:
- Cloud Application Programming Model (CAP) — Node.js / Java backend.
- SAP Mobile Services — push, offline sync, analytics.
- SAP Build Apps — low-code mobile.
- SAP Build Code — pro-code IDE.
- Identity Authentication Service (IAS).
BTP is the SAP-recommended mode for extensions (clean core), avoiding modifications in S/4HANA.
How do you integrate the mobile app with S/4HANA?
Through SAP Gateway / OData (v2 or v4), exposed via SAP API Management or directly.
For complex flows we build custom services in CAP deployed on SAP BTP — they consume OData from S/4HANA and expose APIs optimized for mobile.
For S/4HANA Cloud we use Public APIs from SAP API Business Hub.
Do you support SAP Build Apps (former AppGyver)?
Yes. SAP Build Apps is useful for simple productivity apps (forms, dashboards, lookups).
For complex enterprise apps (offline-first, industrial scanner, hardware integration) we recommend pro-code (Swift / Kotlin / Flutter).
We can deliver hybrid: SAP Build for simple parts, pro-code for critical parts.
We already have SAP licenses — is mobile cost separate?
Mobile cost is separate from standard SAP licenses.
- Users with complete SAP license (Professional / Functional User) — can access Fiori or the mobile app without additional license.
- NEW users without complete SAP license (warehouse workers, field salespeople) — options: SAP Fiori Use Type (cheaper), SAP Build Apps subscription, or access via custom API gateway that doesn't require per-user license in SAP.
Concrete model defined with your SAP licensing team.
Next step
Talk to the VOGO SAP team.
Private session with a VOGO consultant specialized in SAP mobile.
Talk to a VOGO consultant
A private session — phone or WhatsApp. We respond on the same business day.
Or email us: info@vogo.family
Coverage
Global contacts.
