Connectors Oracle JD Edwards EnterpriseOne

Oracle JD Edwards EnterpriseOne data integration with Lima, in both directions.

JD Edwards EnterpriseOne is Oracle's mid-market ERP, common in distribution and manufacturing. Its data lives in F-tables on Oracle, SQL Server or Db2. Lima reads those tables over JDBC in partitions, tracks changes by the update audit columns, and writes back through JD Edwards Orchestrator services so business rules apply.

SOURCEOracle JD Edwards EnterpriseOnePartitioned JDBC reads · Incremental re…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 JD EDWARDS ENTERPRISEONE · EACH WRITE CONFIRMED
How Oracle JD Edwards EnterpriseOne 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.
4
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 JD Edwards EnterpriseOne

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
Partitioned JDBC readsReads F-tables in parallel slices.First loads and history.
Incremental reads by audit columnsReads rows changed since the last run.Deltas.
Orchestrator REST servicesCalls orchestrations that run business functions.Write-back with validation.
Z-file interface tablesLoads interface tables processed by batch programs.Bulk write-back.
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
F4101 · F4102item master and item branch
F3002 · F3003bills of material and routings
F4311 · F4301purchase order detail and header
F4211 · F4201sales order detail and header
F41021item location: on-hand quantities
F4801 · F3111work orders and parts lists
F0101 · F0401 · F03012address book, suppliers, customers
PatternSupported
Full loadYes
IncrementalYes
Change captureby audit columns; database log capture where the DBA allows
Streaming—
Write-backOrchestrator services and Z-file tables; confirmation read back
What a planning application needs from Oracle JD Edwards EnterpriseOne

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 JD Edwards EnterpriseOne
ItemsF4101 · F4102
Bills of materialF3002
RoutingsF3003
StockF41021
Open purchase ordersF4311 · F4301
Open sales ordersF4211 · F4201
Work ordersF4801 · F3111
ForecastsF3460
Customers and suppliersF0101 · F03012 · F0401
CalendarsF0007
Before you start

Prerequisites, then four steps.

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

  • Read-only database user on the business data library
  • Orchestrator user and the orchestrations for write-back
  • Run windows agreed with the CNC 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 JD Edwards EnterpriseOne 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/oracle-jd-edwards-to-kinaxis-maestro

Oracle JD Edwards EnterpriseOne 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/oracle-jd-edwards-to-o9

Oracle JD Edwards EnterpriseOne 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/oracle-jd-edwards-to-blue-yonder

Oracle JD Edwards EnterpriseOne 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/oracle-jd-edwards-to-sap-ibp

Oracle JD Edwards EnterpriseOne 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/oracle-jd-edwards-to-omp

Oracle JD Edwards EnterpriseOne to OMP

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

Open the pair page →
/connectors/oracle-jd-edwards-to-anaplan

Oracle JD Edwards EnterpriseOne to Anaplan

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

Open the pair page →
/connectors/oracle-jd-edwards-to-snowflake

Oracle JD Edwards EnterpriseOne to Snowflake

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

Open the pair page →
/connectors/oracle-jd-edwards-to-databricks

Oracle JD Edwards EnterpriseOne to Databricks

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

Open the pair page →
/connectors/oracle-jd-edwards-to-microsoft-fabric

Oracle JD Edwards EnterpriseOne to Microsoft Fabric

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

Open the pair page →
/connectors/oracle-jd-edwards-to-bigquery

Oracle JD Edwards EnterpriseOne to Google BigQuery

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

Open the pair page →
/connectors/oracle-jd-edwards-to-amazon-redshift

Oracle JD Edwards EnterpriseOne to Amazon Redshift

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

Open the pair page →
/connectors/oracle-jd-edwards-to-azure-synapse

Oracle JD Edwards EnterpriseOne 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 JD Edwards EnterpriseOne 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 JD Edwards EnterpriseOne?

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 JD Edwards EnterpriseOne 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 JD Edwards EnterpriseOne 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.