Oracle E-Business Suite is Oracle's on-premise ERP, run by manufacturers alongside SAP or on its own. Lima reads its tables over JDBC in parallel partitions, picks up changed rows by their last-update columns, uses LogMiner where the database administrator allows it, and writes back through the open interface tables and public PL/SQL APIs, with the concurrent program's result 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 |
|---|---|---|
| Partitioned JDBC reads | Splits a large table into partitions read side by side, within a connection cap agreed with the DBA. | First loads, migrations, archives. |
| Incremental reads by LAST_UPDATE_DATE | Reads rows changed since the last run using the standard WHO columns. | Nightly and intraday deltas. |
| LogMiner change capture | Reads the database change log where the DBA enables it. | Low-lag change feeds. |
| Open interface tables and concurrent programs | Inserts into the interface tables, submits the import program and reads its result. | Write-back of requisitions, orders and forecasts. |
| Public PL/SQL APIs | Calls Oracle's released APIs for items, orders and receipts. | Write-back with business logic applied. |
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 |
|---|---|
| MTL_SYSTEM_ITEMS_B | item master by organisation |
| BOM_INVENTORY_COMPONENTS · BOM_BILL_OF_MATERIALS | bills of material |
| BOM_OPERATIONAL_ROUTINGS · BOM_OPERATION_SEQUENCES | routings |
| MTL_ONHAND_QUANTITIES_DETAIL | on-hand stock by subinventory and locator |
| PO_HEADERS_ALL · PO_LINES_ALL · PO_LINE_LOCATIONS_ALL | purchase orders |
| OE_ORDER_HEADERS_ALL · OE_ORDER_LINES_ALL | sales orders |
| WIP_DISCRETE_JOBS · WIP_REQUIREMENT_OPERATIONS | work orders |
| MRP_FORECAST_DATES · MRP_FORECAST_INTERFACE | forecasts and their interface |
| HZ_PARTIES · AP_SUPPLIERS | customers and suppliers |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | Yes |
| Change capture | LogMiner where the DBA allows; otherwise last-update columns |
| Streaming | — |
| Write-back | open interface tables, public APIs; the import result 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 E-Business Suite |
|---|---|
| Items | MTL_SYSTEM_ITEMS_B · MTL_ITEM_CATEGORIES |
| Bills of material | BOM_BILL_OF_MATERIALS · BOM_INVENTORY_COMPONENTS |
| Routings | BOM_OPERATIONAL_ROUTINGS · BOM_OPERATION_SEQUENCES |
| Stock by status and locator | MTL_ONHAND_QUANTITIES_DETAIL · MTL_MATERIAL_STATUSES |
| Open purchase orders | PO_HEADERS_ALL · PO_LINES_ALL · PO_LINE_LOCATIONS_ALL |
| Open sales orders | OE_ORDER_HEADERS_ALL · OE_ORDER_LINES_ALL |
| Work orders | WIP_DISCRETE_JOBS · WIP_REQUIREMENT_OPERATIONS |
| Forecasts | MRP_FORECAST_DATES · MRP_FORECAST_DESIGNATORS |
| Customers and suppliers | HZ_PARTIES · HZ_CUST_ACCOUNTS · AP_SUPPLIERS |
| Calendars | BOM_CALENDARS · BOM_CALENDAR_DATES |
The prerequisites are what the team that runs Oracle E-Business Suite 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 E-Business Suite 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.
