How to build a mobile app for Oracle E-Business Suite
Short answer
Build a mobile or rugged-handheld front end that calls Oracle EBS through Integrated SOA Gateway services or supported PL/SQL APIs behind a thin API layer, handles scanning on the device, queues transactions when offline, and posts them through the same interfaces the Forms screens use.
EBS shops that want mobility usually start from one of two places. Either they use Oracle Mobile Supply Chain Applications (MSCA) on telnet-style handhelds that were designed for older warehouse devices, or they have nothing and operators walk to a PC. Both leave gaps: modern phones and rugged Android scanners, photo capture, offline use and usable screens.
A mobile front end is not difficult in itself. The hard parts are choosing which EBS transactions are safe to expose, keeping multi-org and responsibility security intact, and designing for patchy Wi-Fi on a shop floor.
This page lays out the integration approach for 12.1.3 and 12.2.x and where Oracle's own mobile offerings fit.
What teams use it for
Barcode inventory moves and counts
Subinventory transfers, miscellaneous issues and receipts, and cycle counts with lot and serial scanning, posting through the Inventory transaction interface.
Labor and WIP reporting
Operators start and finish operations, report quantity moves and scrap, and record time against discrete jobs from a tablet at the cell.
Receiving at the dock
Scan PO and item, enter quantity and lot, take photos of damage, and submit to the Receiving Open Interface.
Mobile approvals
Managers approve requisitions, expense reports and POs from a phone with the same rules as the worklist.
Field service and maintenance
Technicians open work orders, log hours and parts, and capture signatures and photos with sync when back in coverage.
Quality inspections
Record inspection results with measurements and images against receiving or WIP plans.
Oracle E-Business Suite integration surface
- Oracle Mobile Supply Chain Applications (MSCA): character-mode and mobile web screens for WMS and Inventory transactions that run through the Mobile Application Server; useful baseline before building anything custom.
- Oracle E-Business Suite Mobile Apps and the Mobile Application Framework approach for some self-service and approval functions, with availability depending on release and patches.
- Integrated SOA Gateway: REST or SOAP services for supported public APIs, with PL/SQL wrappers when a service you need is not published.
- Inventory open interfaces such as MTL_TRANSACTIONS_INTERFACE and MTL_TRANSACTIONS_INTERFACE processing, WIP move transaction interface WIP_MOVE_TXN_INTERFACE and Receiving interfaces, each processed by its own manager or concurrent program.
- FND security: users, responsibilities and MOAC operating unit access that the API layer must set via FND_GLOBAL.APPS_INITIALIZE or the supported ISG authentication method.
- Workflow notifications for approval actions through WF_NOTIFICATION APIs.
How it works
- 1
Pick the transactions
Start with three to five high-volume tasks such as receiving, subinventory transfer and WIP move. Check each against MSCA first; use a custom app where the device UX, photos or offline needs justify it.
- 2
Design an API layer
Put a service between the app and EBS that exposes narrow endpoints, authenticates users, sets the correct responsibility and operating unit, and calls ISG or PL/SQL wrappers. The app never talks to the database.
- 3
Authenticate
Use the company SSO if EBS is integrated with it, issue short-lived tokens to the app and map them to FND users so every transaction records the real operator.
- 4
Build device features
Use the camera or hardware scanner for GS1, Code 128 and QR codes, with local validation for item, lot and subinventory against cached reference data.
- 5
Add an offline queue
Store transactions in a local database with idempotency keys, sync when connected, and show clear states: pending, posted, rejected with reason.
- 6
Process and reconcile
The API layer writes to open interfaces, waits for the processing result and returns errors in plain language. A reconciliation job checks for stuck rows in the interface tables.
- 7
Roll out by cell or warehouse
Pilot with one team, compare mobile and Forms transaction counts and error rates, then add users.
Example flows
Dock receiving with photos
Trigger: A truck arrives with a PO shipment.
- Receiver scans the PO barcode and the app loads open lines.
- Receiver scans item labels, enters quantity and lot.
- The app flags a quantity over tolerance and asks for a supervisor.
- Photo of a damaged carton is attached; the transaction goes to the Receiving interface.
- Result shows as received or rejected with the reason.
Result: Receipts are posted at the dock with evidence rather than keyed later from paper.
WIP operation move
Trigger: An operator finishes an operation at a work centre.
- Operator scans the job traveler barcode.
- App shows the current operation and expected quantity.
- Operator confirms completed and scrapped quantities.
- Move transaction posts via the WIP move interface, and the next operation appears.
Result: Job progress in EBS matches the floor within minutes.
Keeping data on-prem
A mobile app for on-prem EBS does not need the cloud. Host the API layer inside your network or DMZ, reachable by devices over plant Wi-Fi and a VPN or private APN for off-site users, and keep EBS and the database unexposed. Devices are managed through an MDM so you can restrict apps, wipe lost devices and pin the certificate. Any AI feature, such as voice entry, photo defect classification or a natural-language lookup, can run on a local GPU server. For air-gapped plants, distribute the app and updates through the MDM from an internal store.
Security checklist
- Authenticate every request and map it to an FND user and responsibility; never share a generic device account.
- Use TLS with certificate pinning and short-lived tokens, and keep tokens in the device secure store.
- Encrypt the offline database and wipe it on logout or MDM command.
- Limit exposed transactions and enforce quantity and subinventory validation server side.
- Log every transaction with device ID, user, time and idempotency key.
Ways to get it done
Use Oracle MSCA or Oracle's mobile apps
Effort: Configuration and device setup; limited UX changes.
Fits standard warehouse and approval tasks with supported devices.
Custom app on your own API layer
Effort: Two to five months for a first set of transactions.
Fits offline needs, photos, specific workflows and modern devices.
Partner build with Netray
Effort: Pilot on one warehouse or cell.
Fits sites wanting on-prem AI features such as voice or defect capture inside the app.
Pitfalls
- !Skipping MSCA evaluation can mean rebuilding functionality Oracle already supports for standard inventory tasks.
- !Calling transaction APIs without the right responsibility and operating unit context creates errors that look random.
- !Offline queues without idempotency keys produce duplicate receipts after a flaky sync.
- !Inventory interface rows can sit unprocessed if the transaction manager is down; monitor and alert on them.
- !Handheld scanners differ in how they send barcode data, so test each device model early.
Frequently asked questions
Does Oracle EBS have an official mobile solution?
Yes, in parts. Oracle Mobile Supply Chain Applications covers warehouse and inventory transactions on handhelds, and some releases offer mobile approvals and self-service apps. Coverage varies by version and licensing, so confirm what applies before you build custom.
Can the app write directly to the database?
It should not. Use ISG services, public PL/SQL APIs or the open interface tables so Oracle's validation, accounting and audit logic run. Direct writes risk corrupt balances and unsupported states after patching.
How do offline transactions work?
The app stores each transaction with a unique key and syncs when connected. The API layer checks the key to avoid duplicates and returns a status. Design the UI so users see what is still pending.
Is a native app better than a web app?
For scanning, camera, offline and background sync a native or cross-platform app usually wins. For simple approvals a responsive web page over the same API may be enough and easier to maintain.
Can voice or photo AI be added?
Yes. Speech to text and photo classification models can run on a server inside your network. Keep their output as a suggestion that the user confirms before a transaction posts.
Want Mobile app working on your Oracle E-Business Suite?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment