A field service app connected to Oracle SCM

Field teams record stock counts, orders and returns on paper or in a legacy app, and someone re-keys them into the ERP later. Inventory in SCM drifts from inventory on the van, and the legacy app no longer passes store review. The enterprise system is fine; the last mile to the people using it is not.

This is a reference engagement: the architecture we use whenever a mobile product has to read from and write to Oracle SCM or ERP. The same pattern applies to portals and web applications.

The app is React Native with Expo, written for offline capture first: a warehouse has no signal, so every transaction is stored locally and synchronised when it can be. A product backend holds users, devices and the local transaction log. OCI API Gateway fronts a small set of integrations in OIC that call SCM's inventory and order APIs, so the app never talks to Fusion directly and every call is authenticated, throttled and logged.

• Idempotency keys on every write, so a retried sync never creates a duplicate order or count.
• Business exceptions from SCM (item not stocked at this sub-inventory, order on hold) come back to the user in plain language with the fix.
• Store builds through EAS with internal testers from the second week; JavaScript fixes ship over the air.
• The integration layer is versioned and promoted by pipeline like the rest of the Oracle estate.

What changes: inventory in SCM matches inventory in the field because the field is entering it once, at the point of work; re-keying disappears along with its errors; and the enterprise system gains a modern product surface without being customised.

This page describes the reference engagement rather than one client, so it carries no client figures.