Oracle Fusion Cloud ERP is Oracle's SaaS ERP. There is no database to connect to, so Lima uses the interfaces Oracle releases: scheduled BI Cloud Connector extracts landed in object storage, REST APIs for current data and for write-back, and file-based data import for bulk loads, with the import job's status read back as the confirmation.
Each method has a job. The first load uses the bulk method; the daily run uses the incremental or change-capture method; write-back uses the interface the system itself uses.
| Method | What it does | When it is used |
|---|---|---|
| BI Cloud Connector (BICC) extracts | Scheduled full and incremental extracts of public view objects, landed as files. | Bulk reads on a schedule. |
| REST APIs | Reads current records and writes changes through released resources. | Intraday reads; write-back. |
| File-Based Data Import (FBDI) | Loads bulk data through Oracle's import templates and jobs. | Bulk write-back such as forecasts or requisitions. |
The objects are the tables, views or records Lima reaches through the methods above. The patterns say how a copy is made and kept current.
| Object | Plain meaning |
|---|---|
| Items and item structures | products and bills of material |
| Purchase orders and requisitions | procurement documents |
| Sales orders | order management |
| On-hand quantities | inventory balances |
| Suppliers and customers | trading partners |
| General ledger balances | finance |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | BICC incremental extracts by last-updated date |
| Change capture | no (SaaS; extracts and APIs) |
| Streaming | — |
| Write-back | REST and FBDI; job status is the confirmation |
A planning dataset is assembled from these objects. The pair pages show how each planning application shapes them.
| Planning object | Source objects in Oracle Fusion Cloud ERP |
|---|---|
| Items | Item public view objects |
| Item structures | Structure and component view objects |
| Work definitions | Manufacturing work definition objects |
| On-hand quantities | Inventory balance view objects |
| Open purchase orders | Purchasing document view objects |
| Open sales orders | Order management fulfillment lines |
| Work orders | Manufacturing work order objects |
| Demand plans | Supply chain planning extracts |
| Suppliers and customers | Trading partner objects |
| Calendars | Schedule and calendar objects |
The prerequisites are what the team that runs Oracle Fusion Cloud ERP grants. The four steps are the same for every connector.
Incoming data = valid records + exception records. A row that fails a check is kept, routed to the person who owns it with a deadline, and replayed once fixed. The load carries on with the valid rows and the report says exactly what was held back. How exceptions work →
Each pair page covers one path end to end: objects out, model in, checks, cadence and the offer.
Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →3 more pair pages for Oracle Fusion Cloud ERP are listed in the directory.
Lima connects from outside through the interfaces listed above with credentials your administrators grant. Where a vendor requires its own agent or add-on for a method, the prerequisites say so.
Parallel reads are capped and the cap is agreed with the team that runs the system. Large reads run inside an agreed run window. Change capture keeps the daily volume small.
A report per run: rows in, rows out, control totals and variance per table, the exceptions held back and who owns them, and whether the deadline was met.
Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.
A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.
