NetSuite is Oracle's cloud ERP for mid-sized companies and subsidiaries of larger groups. Lima reads its records through SuiteAnalytics Connect (an ODBC/JDBC service over the analytics data source) and writes back through SuiteTalk REST records, with NetSuite's response 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 |
|---|---|---|
| SuiteAnalytics Connect | Reads record tables through a JDBC driver with incremental filters on last-modified dates. | Bulk and incremental reads. |
| SuiteTalk REST | Reads and writes records. | Write-back; small intraday reads. |
| Saved searches | Reads business-defined result sets. | Curated data. |
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 assembly items | products and bills of material |
| Purchase orders and sales orders | documents |
| Inventory balances by location | stock |
| Vendors and customers | trading partners |
| Transactions and GL | finance |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | Yes |
| Change capture | by last-modified date |
| Streaming | — |
| Write-back | SuiteTalk REST; response 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 NetSuite |
|---|---|
| Items | Item records |
| Bills of material | Assembly item members · BOM revisions |
| Routings | Manufacturing routings |
| Stock | Inventory balance by location |
| Open purchase orders | Purchase order lines |
| Open sales orders | Sales order lines |
| Work orders | Work order records |
| Forecasts | Demand plan records |
| Customers and suppliers | Customer and vendor records |
| Calendars | Location calendars |
The prerequisites are what the team that runs Oracle NetSuite 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 NetSuite 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.