Enterprise Systems
Enterprise ESS Mobile Ecosystem
A unified mobile gateway giving 4,000+ employees one self-service app across Odoo and SAP — one identity, one employee data layer, one place for everything from leave requests to payslips.
FIG. 01 — SYSTEM FLOW
Constraint in → contract out. Every integration lands in a single system of record.
01
Problem
HR self-service was fragmented: employees bounced between Odoo screens and SAP portals, each with its own login and its own version of the truth. Adoption was low, HR staff drowned in manual requests, and the two systems silently disagreed on basic employee data. The real problem wasn't a missing app — it was that two enterprise systems had never agreed on who an employee was.
02
Architecture
A mobile gateway layer sits in front of both systems: single authentication, a normalized employee data model that maps SAP and Odoo fields to one canonical shape, and a set of REST services exposing only the HR operations employees actually need. The gateway owns identity and orchestration; Odoo and SAP remain systems of record behind clean anti-corruption boundaries. Reads are cached where the source tolerates it; writes go through to the source of truth with transactional confirmation.
03
Trade-offs
The SAP and Odoo data models fight each other — employee, partner, and user concepts overlap but never match, so the canonical model is a deliberate simplification and some edge-case fields are intentionally read-only. Sync-vs-realtime was decided per operation: read-heavy HR data syncs on a schedule with conflict rules, while approval actions execute live against the source system. This keeps the app fast at scale while never letting cached data make a decision.
04
Impact
One app serves 4,000+ employees across both systems. HR self-service adoption replaced the manual request pipeline, duplicate employee records between systems were eliminated by the canonical model, and the project is ongoing as the gateway becomes the standard front door for new HR processes.