Claude Code on JD Edwards — World & EnterpriseOne

The honest starting point

JD Edwards isn't one platform — it's two, plus 20 years of tools releases.

JDE World is the older, RPG/COBOL-based system that still runs on IBM i (AS/400) at plenty of manufacturers — no REST API, no Orchestrator. EnterpriseOne (E1) is the Java/C-based successor, and only its modern Tools releases (9.2.7 and later) ship a real API layer: Orchestrator and the AIS Server (Application Interface Services). That single fact decides almost everything about what an AI agent can do — and it's the fact most "AI + ERP" pitches skip.

Version by version

What the agent can reach.

Platform	Agent access	What that means in practice
JDE World (IBM i / AS/400)	Read-only, via SQL over ODBC/JDBC into the F-tables	Claude Code can query and report — inventory positions, open work orders, sales history — but it cannot submit a version, change a processing option, or drive a green-screen transaction. Every write still goes through the terminal.
EnterpriseOne Tools < 9.2.7	SQL read access only — same ceiling as World	Plenty of E1 shops are still on older tools releases without Orchestrator installed or licensed. Same answer as World: reporting agent, not an operating agent.
EnterpriseOne Tools 9.2.7+ with Orchestrator/AIS	Read and write, through published Orchestrations and AIS REST calls	Claude Code can call an existing Orchestration to submit a sales order, check ATP, or trigger an approval — the same way a mobile app or a middleware integration would. It cannot invent a new Orchestration on its own; someone builds that once in Orchestrator Studio, and the agent calls it forever after.

The pattern that actually works

Report first, act only where a door already exists.

Start every engagement on SQL.
Read-only access to the F-tables (F4101 item master, F4102 item branch, F3111/F3112 work order routing) gets an agent reporting value in week one, on World or E1, tools release irrelevant.

Inventory the Orchestrations that already exist.
Most E1 shops on modern tools already built a handful for mobile or EDI. Claude Code can call those immediately — no new development.

Build new Orchestrations for the highest-value writes.
A JDE developer (Denis, in my setup) builds the Orchestration once in Orchestrator Studio; from then on the agent can call it like any other API endpoint.

Never promise write access on World.
If a prospect is still on World, the honest scope is a reporting and reconciliation agent — genuinely useful, just not the same pitch as an E1/Orchestrator shop.

Why this matters more than the demo

Most "AI on your ERP" pitches quietly assume E1 + Orchestrator.

No false promises

Telling a World shop "the agent will submit your work orders" sets up a failed project. Scoping to reporting first builds trust and buys the case for a tools upgrade.

SQL access is still a real win

Slow-moving inventory reports, WMS exception queries, MRP output reconciliation — all deliverable from read-only access, no Orchestrator required.

Orchestrator is a multiplier, not a prerequisite

Once it exists, the same agent pattern used on Odoo (one agent, one domain, direct API calls) works identically on E1.

Running JDE, curious about AI

Let's scope what your tools release actually allows.

Tell me your Tools release and whether Orchestrator is licensed — I'll tell you honestly what's reporting-only and what's a real automation candidate.

Hire me on Fiverr↗

What Claude Code can
actually reach inside JD Edwards.