Overview
In modern enterprise order
processing, organizations often require a hybrid architecture that combines
custom-built applications with enterprise SaaS solutions. In this project, we
implemented an end-to-end integration between an APEX-based custom Order Entry
application and Oracle Fusion Order Management (OM) Cloud using Oracle
Integration Cloud (OIC).
The integration enables users to
perform various order management actions—such as creating new orders,
adding lines, deleting orders or lines, updating order details, and applying or
releasing holds—directly from the APEX interface. OIC validates, processes, and
synchronizes these transactions with Oracle Fusion OM, ensuring real-time
visibility and seamless business operations.
Key
Business Requirements
- Real-Time Order Processing: Allow APEX users to trigger order-related actions in
Fusion OM without manual re-entry.
- Validation Before Processing: Run basic business validations in OIC before sending
requests to Fusion OM.
- Bidirectional Synchronization: Update APEX application whenever relevant events
occur in Fusion OM.
- Error Handling & Feedback Loop: Return success or detailed error messages to APEX for
user visibility.
- Event-Driven Updates:
Subscribe to Fusion OM events and push updates to the APEX application
automatically.
High-Level
Process Flow
The integration is built around two-way
communication between APEX, OIC, and Fusion OM.
1. User Action in APEX
From the APEX UI, a user can
perform:
- Create New Order
- Add Lines to Existing Order
- Update Order/Order Lines
- Delete Order/Order Lines
- Apply Hold
- Release Hold
Once the user saves their changes, APEX
triggers an OIC job, passing:
- Order Number or Order Line reference
- Action to be performed
- Required order details
2.
OIC Request Processing
When OIC receives the request:
- Read Order/Line Data
from the APEX tables via the Oracle ATP Adapter.
- Run Custom Validations:
- Ensure mandatory attributes are present.
- Check business rules (e.g., pricing, product
availability).
- Validation Outcome:
- Fail
→ Update APEX request status to E (Error) with error messages.
- Pass
→ Update APEX request status to S (Submitted) and proceed.
3.
Interaction with Oracle Fusion OM
OIC invokes Oracle Fusion OM REST
APIs such as salesOrderForOrderHub to:
- Create new sales orders.
- Add or update lines.
- Apply or release holds.
- Cancel orders or lines.
If the API call succeeds:
- Return Status = S to APEX with the Fusion Order
Number.
If it fails: - Return Status = E with detailed error
information.
4.
Event Subscriptions for Status Updates
OIC also subscribes to Fusion OM
business events like:
- Line Status Change
- Pick Wave Creation
- Pick Confirmation
- Shipment Advice
When these events occur:
- OIC fetches the latest order status from Fusion
OM.
- OIC updates the corresponding order in APEX.
- The APEX user always has real-time visibility into the
order lifecycle.
Key
Integration Highlights
- Hybrid Processing:
Combines synchronous request/response for order actions with asynchronous
event-driven updates from SaaS.
- Data Consistency:
Ensures both APEX and Fusion OM reflect the same order status at all
times.
- Validation Layer:
Prevents bad data from entering Fusion OM, reducing downstream exceptions.
- Reusable Framework:
The OIC flows are modular, making it easy to add new order actions in the
future.
Benefits
- Faster Order Turnaround: Orders move from APEX to Fusion OM instantly.
- Reduced Errors:
Pre-validation in OIC prevents common mistakes.
- Operational Efficiency: Eliminates manual re-keying of orders.
- Real-Time Updates:
Business events keep both systems in sync.
- Scalable Design:
Can easily accommodate future expansion of order workflows.
