Connectors Oracle NetSuite

Oracle NetSuite data integration with Lima, in both directions.

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.

SOURCEOracle NetSuiteSuiteAnalytics Connect · SuiteTalk REST…LIMA BACKBONEExtractfull · incremental · change captureCheckevery row valid, or an exception with a…Transform and load150+ operators · Python · loads on the…TARGETSPlanning applicationsKinaxis · o9 · Blue Yonder · IBP · OMPWarehouses and lakehousesSnowflake · Databricks · Fabric · S3 …Reporting and partnersPower BI · Tableau · EDI · filesRESULTS RETURN TO ORACLE NETSUITE · EACH WRITE CONFIRMED
How Oracle NetSuite fits the six Backbone steps. It is a source and a target: data comes out through the methods below, and results go back in with confirmation.
3
ways to read or write it
this connector
4
patterns supported
this connector
3
ways to run: SaaS, private cloud, on-premise
product
22 days
from contract to production
showcase estate
How Lima reads and writes Oracle NetSuite

Method by method.

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.

MethodWhat it doesWhen it is used
SuiteAnalytics ConnectReads record tables through a JDBC driver with incremental filters on last-modified dates.Bulk and incremental reads.
SuiteTalk RESTReads and writes records.Write-back; small intraday reads.
Saved searchesReads business-defined result sets.Curated data.
What it covers

Objects and patterns.

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.

ObjectPlain meaning
Items and assembly itemsproducts and bills of material
Purchase orders and sales ordersdocuments
Inventory balances by locationstock
Vendors and customerstrading partners
Transactions and GLfinance
PatternSupported
Full loadYes
IncrementalYes
Change captureby last-modified date
Streaming—
Write-backSuiteTalk REST; response is the confirmation
What a planning application needs from Oracle NetSuite

The objects a first load is built from.

A planning dataset is assembled from these objects. The pair pages show how each planning application shapes them.

Planning objectSource objects in Oracle NetSuite
ItemsItem records
Bills of materialAssembly item members · BOM revisions
RoutingsManufacturing routings
StockInventory balance by location
Open purchase ordersPurchase order lines
Open sales ordersSales order lines
Work ordersWork order records
ForecastsDemand plan records
Customers and suppliersCustomer and vendor records
CalendarsLocation calendars
Before you start

Prerequisites, then four steps.

The prerequisites are what the team that runs Oracle NetSuite grants. The four steps are the same for every connector.

  • SuiteAnalytics Connect licence and a role with the record permissions
  • Token-based authentication for REST
  • Concurrency limits agreed with the administrator
Register the connectionEndpoint, credentials from the vault, and the method. The connection is tested and a failed test names the cause.
Choose the objects and the patternPick tables or objects from the discovered schema, and the pattern: full, incremental, change capture or streaming.
Run the first load with checks onEvery row is valid or becomes an exception with an owner. The run ends with a count and a control total per table.
Schedule it on the business calendarA run window with a deadline; pause, resume and replay if a check trips; the report after every run.
What happens to a bad record

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 →

Pair pages

Oracle NetSuite in a source-to-target path.

Each pair page covers one path end to end: objects out, model in, checks, cadence and the offer.

/connectors/netsuite-to-kinaxis-maestro

Oracle NetSuite to Kinaxis Maestro

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/netsuite-to-o9

Oracle NetSuite to o9 Solutions

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/netsuite-to-blue-yonder

Oracle NetSuite to Blue Yonder Planning

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/netsuite-to-sap-ibp

Oracle NetSuite to SAP Integrated Business Planning

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/netsuite-to-omp

Oracle NetSuite to OMP

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/netsuite-to-anaplan

Oracle NetSuite to Anaplan

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/netsuite-to-snowflake

Oracle NetSuite to Snowflake

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/netsuite-to-databricks

Oracle NetSuite to Databricks

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/netsuite-to-microsoft-fabric

Oracle NetSuite to Microsoft Fabric

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/netsuite-to-bigquery

Oracle NetSuite to Google BigQuery

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/netsuite-to-amazon-redshift

Oracle NetSuite to Amazon Redshift

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/netsuite-to-azure-synapse

Oracle NetSuite to Azure Synapse Analytics

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.

Terms on this page

Plain meanings.

ConnectorA packaged way to read or write one kind of system, with its authentication, methods and prerequisites described.
Full, incremental, change capture, streamingFour ways to make and keep a copy: read everything; read what changed since last time; read changes from a log as they happen; consume events in small batches.
Write-backWriting a result into the system that owns it through its released interface; the system's response is the confirmation.
Control totalThe sum of a key amount column compared between source and target, along with the row count, at the end of a run.
Exception recordA row that failed a check: kept, routed to an owner, replayed once fixed.
Questions

Asked about this connector.

Does Lima install anything in Oracle NetSuite?

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.

How is load on Oracle NetSuite kept in check?

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.

What do we see when a run finishes?

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.

Can we start small?

Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.

Try Oracle NetSuite on your own estate.

A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.