Why middleware exists in an Oracle Cloud WMS landscape

Oracle Cloud WMS is robust within the warehouse, but it is not a comprehensive enterprise system. In almost every real implementation, WMS must exchange data with:

• Oracle Fusion ERP (Inventory, Order Management, Procurement, Manufacturing)
• TMS
• Planning systems
• Legacy ERPs
• 3PL systems
• Automation systems (WCS, MHE, conveyors, ASRS)
• External partners, vendors, customers

These systems do not speak the same language, follow the same timing, or have the same error-handling expectations.

Middleware sits in between and does five core jobs:

1. Transforms data
2. Orchestrates processes
3. Decouples systems
4. Manages errors and retries
5. Secures and governs integrations

Without middleware, WMS becomes tightly coupled and fragile. OIC is Oracle’s PaaS integration layer. It is not just an interface tool. It combines:

• Application Integration
• File-based Integration
• API Management (basic)
• B2B Trading Partner Management
• Visual orchestration
• Tracking and monitoring

Master Data Interfaces (ERP → WMS)

Interface	Direction	Trigger	Pattern	Notes
Item Master	ERP → WMS	Scheduled / On change	Asynchronous (API or File)	Large volume, rarely needs real-time
Item Categories	ERP → WMS	Scheduled	Asynchronous	Used for task rules, wave logic
UOM Conversions	ERP → WMS	Scheduled	Asynchronous	Critical for picking accuracy
Customers	ERP → WMS	Scheduled / On change	Asynchronous	Address normalization needed
Suppliers	ERP → WMS	Scheduled	Asynchronous	Mainly for receiving
Locations / Warehouses	ERP → WMS	One-time + delta	Asynchronous	Organization to facility mapping
Price Lists (if used)	ERP → WMS	Scheduled	Asynchronous	Often optional in WMS

Transactional Inbound Interfaces (ERP → WMS)

Interface	Direction	Trigger	Pattern	Notes
Sales Orders	ERP → WMS	Order release	Asynchronous (Event/API)	Near real-time preferred
Transfer Orders	ERP → WMS	TO creation	Asynchronous	Often high volume
Purchase Orders	ERP → WMS	PO approval	Asynchronous	Used for ASN matching
Work Orders (Manufacturing)	ERP → WMS	WO release	Asynchronous	If manufacturing integrated
ASNs	ERP / Supplier → WMS	ASN creation	File or API	File still common
Return Orders	ERP → WMS	RMA creation	Asynchronous	Requires inspection logic

    

Outbound Execution Interfaces (WMS → ERP)

Interface	Direction	Trigger	Pattern	Notes
Shipment Confirmation	WMS → ERP	Ship confirm	Asynchronous (Event/API)	Triggers invoicing
Inventory Transactions	WMS → ERP	Real-time / batch	Asynchronous	Adjustments, moves
Receiving Confirmation	WMS → ERP	Receipt completion	Asynchronous	PO receipt
Cycle Count Results	WMS → ERP	Count approval	Batch (File/API)	Often daily
Physical Inventory	WMS → ERP	PI close	Batch	Finance controlled
Returns Receipts	WMS → ERP	Receipt	Asynchronous	Impacts credit memo

Thank You,

Pratip Chatterjee