How Oracle Digital Assistant and OCI AI services via JDE Orchestrator connects to JD Edwards EnterpriseOne
JDE Orchestrator calling OCI REST APIs
Orchestrator can call external REST services, so an orchestration invokes an OCI AI endpoint and returns the result to a JDE flow or to a conversational front end. Oracle's white paper states a current Tools Release is required, so check your release first.
Orchestrator as the JDE-facing API
In the other direction, Orchestrator publishes JDE business functions and data as REST services that a digital assistant can call. Security follows the JDE user and role used by the orchestration.
What data moves
| From | To | Data | When |
|---|---|---|---|
| User | Digital assistant | Natural-language question or request | User message in the chat channel |
| Digital assistant | JDE Orchestrator | Structured request such as a supplier or order lookup | Intent recognized by the assistant |
| JDE Orchestrator | OCI AI services | Text or document content for summarization or extraction | Orchestration step that calls the OCI REST endpoint |
| OCI AI services | JDE | Extracted fields, summaries or classifications | Response returned to the orchestration |
Setting it up
- 1Check Tools Release and AISConfirm the JDE Tools Release meets Oracle's requirement and that the AIS server hosting Orchestrator is available and secured.
- 2Pick one use caseStart with a single scenario, such as supplier spend questions or document extraction, instead of a general assistant.
- 3Build the orchestrationsCreate orchestrations in Orchestrator Studio for the data the assistant needs and for the OCI REST calls.
- 4Configure OCI accessSet up OCI credentials, network access from the AIS server and the AI service endpoints, with least-privilege policies.
- 5Decide data handlingDecide what JDE data may leave your network for OCI, and get that approved by security and compliance before building.
- 6Test with real rolesTest the assistant under real JDE user roles so it never returns data the user could not see in JDE.
What usually breaks
- !Data sent to a cloud AI service leaves your network, which conflicts with export-controlled or air-gapped policies.
- !An orchestration running under a powerful service account bypasses row-level restrictions the end user would have in JDE.
- !Tools Release or AIS version gaps cause orchestrations to fail in ways that look like network problems.
- !Unbounded generative output used in a business decision without review introduces errors that nobody checks.
- !Cloud AI usage costs and quotas are easy to overlook until a high-volume process hits a limit.
A private AI layer across both systems
On-prem model behind the same Orchestrator pattern
For sites that cannot send data to a cloud, the same Orchestrator-calls-REST pattern can point to an open-weight model served on your own GPUs, with retrieval over JDE data and documents.
Grounded questions with the query shown
A private assistant answers questions about orders, suppliers and inventory from live JDE data, shows the query used, and respects JDE roles.
Document extraction for approval
It reads supplier documents or inspection reports and drafts structured JDE entries for a person to approve before anything is written.
Try it here, free
JD Edwards Orchestrator Design Template
A fill-in design document for a JD Edwards Orchestrator orchestration: purpose, inputs, steps, rules, outputs, security and test cases.
When something else fits better
- If the cloud is acceptable and your use case is narrow, Oracle's own OCI services through Orchestrator are the simplest route.
- Plain JDE One View reports or dashboards may answer the question without any AI at all.
- A private on-prem assistant is the better choice when data must not leave the site.
Frequently asked questions
How does JD Edwards connect to OCI AI services?
Through JDE Orchestrator, which calls OCI REST APIs, per Oracle's white paper on AI with JDE. It requires a current Tools Release. The orchestration passes data to the OCI service and returns the result to a JDE flow.
Can this run fully on-prem?
The OCI services themselves run in Oracle's cloud, so it is not air-gapped. The Orchestrator pattern can call a model hosted inside your network instead, which is the usual approach for restricted environments.
Does the assistant respect JDE security?
Only if you design for it. Run orchestrations under the end user's role where possible, avoid broad service accounts, and test with real roles. Writes should require human approval.
Pairing documented at www.oracle.com/webfolder/technetwork/tutorials/jdedwards/White%20Papers/Oracle-A . Oracle Digital Assistant and OCI AI services via JDE Orchestrator is a product of Oracle; Netray is independent and not affiliated with either vendor.