AdvancedOracle JD Edwards EnterpriseOneIntegration / AIS, Orchestrator, Business Services

JD Edwards API Documentation: AIS REST, Orchestrator, BSSV and Connector Options

Question
jd edwards api documentation

Also searched as

  • jd edwards erp system integration
  • concur integration with jd edwards
  • jde ais rest api
  • jde integration options

Short answer

JD Edwards EnterpriseOne exposes integration through the Application Interface Services (AIS) REST server, Orchestrator for no-code flows, older business services (BSSV, SOAP) for published business functions, and batch interfaces such as Z-files and UBEs. Third-party tools like Concur typically connect through these, often via an integration platform rather than directly.

Applies to: JD Edwards EnterpriseOne 9.1 and later; AIS and Orchestrator are most complete on 9.2 and later tools releases.

Choose and use an integration option

  1. 1List the integration need: read data, create a transaction, trigger a process, or exchange files in batch.
  2. 2For REST or JSON needs, deploy the AIS Server (it fronts the Enterprise Server) and confirm the base URL and token or basic authentication for a service account.
  3. 3For no-code flows, build an orchestration in Orchestrator Studio that calls a form, a business function or a data request, and publish it as a REST endpoint through AIS.
  4. 4For existing SOAP integrations, review the published business services (BSSV) in your environment and their WSDLs.
  5. 5For bulk loads, use the Z-file interface: load the Z table, run the processor UBE, and review the error table for rejected rows.
  6. 6Use a dedicated integration user with the minimum JDE security needed, and test in a non-production environment.
  7. 7Document the endpoint, versions and fallback so upgrades do not break the integration silently.

Where the documentation actually lives

There is no single public API reference like a typical SaaS product. The AIS REST services (form service, data service, orchestrator service) are documented in the Oracle JD Edwards EnterpriseOne documentation for your tools release, and Orchestrator Studio shows the contract of each orchestration you publish. BSSV contracts come from the generated WSDLs in your own environment.

Treat your own AIS server as the source of truth: it can show which services are enabled, and your orchestration definitions are the API you actually publish. Document those for consumers.

Choosing between AIS, Orchestrator, BSSV and Z-files

AIS form and data services are quick for reads and for scripted use of existing applications. Orchestrator wraps logic into a named, versionable endpoint that other systems can call without knowing JDE forms, which is better for stable integrations.

BSSV is the legacy route and still common where it was built years ago. Z-files remain the right choice for large batch loads and transactions that need the standard edit and error handling of the interface tables.

POST https://<ais-host>/jderest/v2/tokenrequest
{ "username": "INTEGRATION_USER", "password": "***", "deviceName": "integration-1" }
POST https://<ais-host>/jderest/v2/dataservice
{ "targetName": "F0101", "targetType": "table", "dataServiceType": "BROWSE", "maxPageSize": "10" }

Third-party connectors such as Concur

Expense and spend platforms usually integrate by exporting an accounting file or journal that JDE imports, through a vendor or partner connector, or through an integration platform that maps their API to a JDE interface. Which pattern you get depends on the connector vendor and your JDE version.

Ask what the connector writes to (voucher batches, journal entry Z-files, address book) and who handles rejected records. Most operational pain comes from error handling, not from the happy path.

Try it here, free

JD Edwards Orchestrator Design Template

Open full tool

A fill-in design document for a JD Edwards Orchestrator orchestration: purpose, inputs, steps, rules, outputs, security and test cases.

Common pitfalls

  • !Exposing AIS to the internet without a gateway, TLS and a restricted integration user.
  • !Using a named human's credentials for an integration, so password rotation breaks it.
  • !Calling form service for high-volume work, which is slow compared with batch interfaces.
  • !Not versioning orchestrations, so a change for one consumer breaks another.
  • !Ignoring the Z-file error table, so rejected rows never get corrected.

How an ERP-grounded AI assistant handles this

Because JDE publishes read and write surfaces through AIS and Orchestrator, a private AI layer can query your data through read-only orchestrations or data services and answer in plain language. Netray designs these with approval before any write-back and deploys on-prem so AIS and the model stay inside your network.

See ERPray

Frequently asked questions

Does JD Edwards have a REST API?

Yes. The Application Interface Services (AIS) server provides REST services for forms, data and orchestrations. Orchestrator lets you publish your own named endpoints on top of JDE logic without writing code in the application.

Where is the JD Edwards API documentation?

In the Oracle JD Edwards EnterpriseOne documentation for your tools release (AIS and Orchestrator guides), plus the contracts generated in your own environment: orchestration definitions and BSSV WSDLs. There is no single public reference for custom integrations.

How does Concur connect to JD Edwards?

Typically through a connector or integration platform that maps Concur expense or accounting extracts to JDE interfaces such as vouchers or journal entries. Details depend on the connector and JDE version, so confirm the supported pattern with the vendor.

Should I use BSSV or Orchestrator for a new integration?

For new work prefer Orchestrator and AIS, which are the direction Oracle has invested in. Keep BSSV only where existing integrations depend on it.

Related

How-to

How to set up JD Edwards Orchestrator (step by step)

An EnterpriseOne orchestration chains one or more requests (form requests that drive an interactive application, or service requests that call a BSFN, business service, or SQL) plus optional rules and notifications, then exposes the whole thing as a callable REST endpoint via the AIS (Application Interface Services) server. The setup work happens in Orchestrator Studio, not the Fat Client.

How-to

JD Edwards Import Tool: Excel Upload, Z-Files and Orchestrator Options

JD Edwards has no single import button. For small loads use the grid or Excel paste and import features in an application, for large transactional loads use the Z-file interface (load a Z table, run the processor UBE, fix errors), and for repeatable automated loads use Orchestrator or a custom UBE. Choose by volume and by how much validation you need.

How-to

How to set data selection and processing options in JD Edwards

Data selection controls which rows a UBE's underlying business view reads (a filter, stored per version in F9210/F9211), while processing options control how the program behaves once it has that data (a settings template stored per version in F983051/F983052). They are configured from the same Version Detail screen but are separate, unrelated mechanisms that new users routinely confuse.

Advanced

How to set up row security in JD Edwards Security Workbench

Security Workbench (fast path SECURITY, application P00950) is where every type of EnterpriseOne security record is defined, including row security, which restricts which rows of data a role or user is allowed to see or act on based on a key field like business unit or company, independent of whether they have access to the application itself. Application security controls whether a role can open a program at all; row security controls what data they see once they are in it.

Error fix

JDE UBE failed (status E): how to read jde.log and jdedebug.log

A UBE (batch report/program) that ends with status E in Work With Submitted Jobs tells you almost nothing on its own. The real error is in jde.log on the enterprise server, in the job's own PDF/log subdirectory (jdedebug.log if you turned on debug), and in the work directory for that job number under PrintQueue or the OS temp path.

Error fix

JD Edwards: record is being used by another user (record reservation)

EnterpriseOne places a soft record reservation lock when a user opens a record for edit, tracked in the F00165 table, and releases it when the user saves, cancels, or the session ends cleanly. A stuck lock almost always means a session died abnormally (browser crash, network drop, kiosk timeout) without triggering the release, and it must be cleared by an admin, not by the original user retrying.

AI for ERP

AI for JD Edwards EnterpriseOne, Built on Orchestrator and AIS

Add AI to JD Edwards E1 9.2 using Orchestrator, AIS, and BSSV rather than screen-scraping. Ground a private LLM on F4211, F4111, and F0411 data.

AI for ERP

AI Agents for ERP, Running On-Prem

A practical guide to on-prem AI agents for ERP: what they can safely automate, where human approval belongs, and how to design the guardrails.

Stuck on Oracle JD Edwards EnterpriseOne?

Talk to engineers who work inside Oracle JD Edwards EnterpriseOne every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations

Software

TermsJD Edwards Orchestrator