Oracle ERP
The same role as SAP in a different estate: ledger, procurement, order management and the sub-ledgers that feed them.
01 What it holds
The data inside it
General ledger balances and journals, supplier and customer masters, purchase and sales documents, fixed assets, and in Fusion a set of published business objects rather than raw tables.
GL_JE_LINES and GL_BALANCES, AP_INVOICES_ALL, AR_CUSTOMER_TRX_ALL, PO_HEADERS_ALL, OE_ORDER_HEADERS_ALL, MTL_SYSTEM_ITEMS_B, HZ_PARTIES (trading community)
02 Getting the data out
Extraction, and the keys that decide whether it joins
E-Business Suite is usually read from the underlying tables or an ODS; Fusion Cloud is read through BI Publisher extracts, BICC or REST. Fusion deliberately does not give you the tables, which changes the integration pattern completely.
ORG_ID and SET_OF_BOOKS_ID / LEDGER_ID scope nearly everything, and the multi-org security model means an extract run under the wrong responsibility silently returns a subset rather than an error.
03 What goes wrong
The failures that look like success
Each of these produces a number that is plausible, reconciles to something, and is wrong. They are worth reading before the first extract, not after the first dispute.
_ALL tables versus secured views
The _ALL tables hold every operating unit; the views hide the ones your session cannot see. Reconciliations fail when one extract used a view and another used the table.
Trading Community Architecture
Customers live in HZ_PARTIES with accounts and sites beneath them. Treating the account as the customer breaks every relationship metric.
Fusion has no tables to hit
Cloud extraction is scheduled, file-based and eventually consistent. Designs that assume a live query against Fusion do not survive contact with it.
Sub-ledger accounting is where meaning lives
The journal in GL is the consequence; SLA holds why it was posted that way, and dropping it loses the ability to explain a figure.
04 Joins that matter
What this system is worth joining to
| Join to | What it lets you answer |
|---|---|
| CRM | party and account identity, which rarely matches between the two |
| HRIS | cost centre and employee, for anything measured per head |
| Procurement | requisition to purchase order to invoice, the three-way match |
05 Metrics it feeds
The numbers that come out of it
06 Questions
Frequently asked
Why is Fusion harder to integrate than E-Business Suite?
Because you no longer own the database. Everything is an extract on a schedule, so latency and completeness become design decisions rather than technical details.
What breaks most often in Oracle extractions?
Multi-org scoping. An extract that ran correctly in test under one responsibility returns a different population in production, and nothing raises an error.
Connect this system without replacing it
SCIKIQ reads it in place, resolves the entities inside it and governs what the fields mean.