Oracle ERP Integration - Signalx Webflow Ecommerce Website Template

Oracle ERP comes in two architecturally distinct flavors — Fusion Cloud ERP and E-Business Suite — with different integration approaches. Horizon's methodology covers both, using Oracle's own recommended patterns rather than reverse-engineering the data model.

Two Oracle ERPs, two integration approaches

Oracle Fusion Cloud ERP and Oracle E-Business Suite are different products with different data models, different integration interfaces, and different deployment patterns. The integration approach for each reflects what Oracle itself recommends — Horizon doesn't try to apply one method to both.

Oracle Fusion Cloud ERP

For Fusion Cloud, Horizon uses two complementary mechanisms:

REST APIs — for transactional and master data that needs real-time or near-real-time exchange. Item master, on-hand inventory, open orders, and purchase orders are read through standard Fusion REST endpoints. Authentication uses OAuth 2.0 with a service account configured in Fusion Security.
Business Intelligence Cloud Connector (BICC) — for bulk historical data extraction. Demand history (Order Management transactions over 18-24 months) and inventory snapshots are extracted via BICC to UCM (Universal Content Manager) and pulled into Horizon. BICC handles the volume that REST can't handle efficiently.
OTBI (Oracle Transactional Business Intelligence) — for ad-hoc reporting and reconciliation views. Used during the validation phase to verify Horizon's loaded data matches Oracle's own reporting.

Specific Oracle Fusion objects Horizon reads

Item master with item organizations (which plants/inventory orgs each item is enabled in)
Inventory organizations and subinventories
BOMs from the Product Information Management module
Work definitions and resources from Manufacturing Cloud (for customers using Oracle's manufacturing module)
Demand history from Order Management — booked orders, shipped orders, with their customer and date dimensions
Open POs from Procurement Cloud
Supplier master with lead times
Planning attributes from Supply Chain Planning Cloud, for customers running it

Oracle E-Business Suite (EBS)

EBS integration is fundamentally different — older architecture, on-premise or hosted, with mature but different interfaces:

Oracle Integration Cloud (OIC) — for customers who've adopted Oracle's middleware layer. OIC provides pre-built adapters for EBS modules and handles the API translation. Horizon connects to OIC; OIC handles EBS internals.
Direct database views — for customers without OIC, Horizon's preferred path is read-only access to EBS views (XLA, MTL, PO, OE tables) created by the customer's DBA team. This is the well-trodden path for EBS integration and avoids the API limitations of older EBS versions.
EDI and IDoc-equivalent flat files — for customers in EDI-heavy environments, scheduled file exchange remains viable.

Specific EBS objects Horizon reads

MTL_SYSTEM_ITEMS for item master with planning attributes
MTL_PARAMETERS and MTL_SECONDARY_INVENTORIES for organization and subinventory structure
BOM_STRUCTURES_B and BOM_COMPONENTS_B for bills of material
BOM_OPERATIONAL_ROUTINGS and related for routings
MTL_ONHAND_QUANTITIES_DETAIL for inventory positions
OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL for sales order history
PO_HEADERS_ALL and PO_LINES_ALL for purchase orders
WSH_DELIVERY_DETAILS for shipment history

Authentication and security model

Fusion Cloud: OAuth 2.0 service account, role-based access through Oracle Identity Cloud Service. Roles required are documented for the customer's Oracle administrator.
EBS via OIC: OIC connection with service account. Standard Oracle middleware security.
EBS direct DB: Read-only schema with VPN or private network connection. The DBA team controls what views are exposed and grants access to a specific Horizon user.

How the integration is sequenced

For a typical Oracle Fusion Cloud customer:

Week 1-2: Oracle administrator provisions service account with required role assignments. Horizon's connector is configured. BICC export definitions are created (typically 5-8 extracts).
Week 2-4: Bulk historical load through BICC. Real-time API connections tested. Master data validation against Oracle's OTBI reports.
Week 4-6: Forecast generation, demand planning parallel run.
Week 6-8: Write-back configured. First operational cycle in Horizon publishing back to Oracle.

For EBS through direct database views, the timeline is similar but front-loaded with the DBA work of exposing views (typically 1-2 weeks before Horizon configuration begins).

What Horizon writes back to Oracle

Planned purchase orders through Procurement Cloud REST endpoints (Fusion) or PO interface tables (EBS)
Planned work orders through Manufacturing Cloud APIs or WIP interface tables
Planning attribute updates — safety stock, planning method, lead time — written back to item or item organization records
Demand forecast records for Oracle's own planning processes where customers consume them

Oracle SCM Cloud and Horizon

For customers running Oracle Supply Chain Planning Cloud already, Horizon and SCM Cloud can coexist similarly to the SAP IBP pattern. Oracle SCP holds the executive planning rhythm; Horizon adds the operational planning capability for daily and weekly cycles, with scheduled data exchange between the two.

Multi-Oracle environments

Companies running both Fusion Cloud at HQ and EBS at acquired entities — a common situation — can use Horizon as the planning unification layer. Each Oracle instance integrates with the method appropriate to it; Horizon presents a unified planning view across the entities. The data flowing back goes to the appropriate Oracle environment based on the entity it belongs to.