JD Edwards

Finance and operations

Built when you ask for it

Sync JD Edwards financials and distribution data. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The JD Edwards connector syncs general ledger, AP and AR, distribution into analytics-ready tables in your data warehouse. Ingest builds it on request, handling auth, pagination and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • General ledger
  • AP and AR
  • Distribution

How it gets built

  1. Choose JD Edwards when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads JD Edwards's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against JD Edwards itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

Username and password for an API user. Ask your JD Edwards administrator for a dedicated API user with read access to the data you want synced, and enter its login in Ingest's form.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a JD Edwards connector?
Not as a finished connector yet. Ingest builds it from JD Edwards's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can JD Edwards data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

JD Edwards API documentation: https://docs.oracle.com/en/applications/jd-edwards/

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for ERP teams: Ramp, SAP, Oracle NetSuite, Microsoft Dynamics 365, Workday, Odoo.

Request JD Edwards