Most ERP leaders say AI is a top-3 strategic priority. Few JDE shops have an implementation plan. The gap isn't ambition, it's access. JDE's data and processes are locked behind menus, navigation trees, and tribal knowledge. This article explains how JDE Orchestrator, combined with KS2's NL/slash, closes that gap and what your organization can start doing today without buying a new platform or starting over.

Your AI Strategy Already Lives Inside JDE. Here's How to Unlock It.

If you've been in a leadership meeting in the last eighteen months, someone has asked the question. Maybe it came from the board. Maybe from your CEO. Maybe from a vendor who wanted to sell you something new.

What's your AI strategy for JDE?

It's a fair question, and for most JD Edwards organizations, it's also a deeply uncomfortable one. Not because the will isn't there, but because the path forward isn't obvious. Do you need a new platform? A data lake? An expensive consulting engagement before you can even begin?

Most ERP leaders say AI is a top-3 strategic priority. But few JDE shops actually have an implementation plan. The number one barrier cited isn't budget or executive buy-in. It's this: "JDE's data structures are difficult. How do we even get started?"

The answer is already inside your environment. Most organizations just haven't seen it yet.

 The Bottleneck Isn't Intelligence. It's Access 

Here's what typically happens when a JDE organization decides to get serious about AI: they start looking outward. They evaluate tools. They sit through demos. They get excited about what AI can do in theory, and then they hit a wall when they try to figure out how any of it connects to their data.

That wall has a very specific cause. JDE's data and processes are locked behind menus, navigation trees, and tribal knowledge. AI can't help if it can't reach your system. It doesn't matter how powerful the model is; if there's no reliable, secure bridge between the AI and your ERP, you don't have an AI strategy. You have a demo.

The result is AI initiatives that stall before they start. Pilots that never make it to production. Frustrated IT teams caught between executive pressure to "do something with AI" and a technical reality that doesn't yet support it.

Meanwhile, the foundation for that bridge already exists inside JDE. Most organizations just haven't built on it.

 The Bridge You Already Own, And the Layer That Activates It 

JDE Orchestrator has been around for years. For many organizations, it's been used for targeted automation, a workflow here, a batch process there. But its real potential is something most teams haven't fully explored: it's the native layer that exposes JDE as a set of accessible, secure APIs. It preserves your existing security model, your business logic, your audit trail, everything you've built. And if you've already built orchestrations, they're enabled for AI right now.

The missing piece has been a layer that lets AI talk to those orchestrations in plain language. That's what KS2's NL/slash does.

NL/slash is KS2's AI-powered natural language interface for JD Edwards EnterpriseOne. No menus. No navigation. No query language. You type what you need, in plain English, and NL/slash translates your words into JDE actions and delivers answers the same way. It connects to Orchestrator and unlocks four core capabilities:

• NL/Q (Query): Ask about any JDE data in plain English: customers, orders, inventory, GL balances
• NL/R (Report): Search, submit, and retrieve UBE reports just by describing what you need
• NL/O (Orchestrate): Trigger JDE business processes conversationally, no menus, no navigation required
• NL/K (Knowledge): Tap into curated JDE expertise: system codes, table schemas, best practices

Together, Orchestrator and NL/slash turn JDE into an AI-ready platform, without replacing your environment, without moving your data, and without bypassing the governance model you've spent years building.

 What This Looks Like in Practice 

The best way to understand what this unlocks is to see it in practice. Here are four real conversations that NL/slash makes possible today:

A procurement manager types: "What are the open purchase orders for this supplier? Who are our top 10 suppliers?" NL/slash queries the right JDE tables, filters by open status, and returns a summary, no ticket to IT, no report request, no waiting.

A finance leader asks: "What's our AP aging look like this month?" NL/slash finds the AP Aging report, submits it with current-month parameters, retrieves the output, and summarizes: $2.1M total, $340K over 90 days across 12 vendors. A task that used to take 20 minutes takes 20 seconds.

A purchasing team member needs to update pricing: "How can I update PO item pricing and upload in bulk to JDE?" NL/slash identifies the right orchestration, maps the inputs to the required fields, executes it, and confirms completion.

And when a new team member asks: "What are the steps to enter a new sales order manually?" NL/slash checks the knowledge base, surfaces your company's specific implementation steps, and delivers the answer directly. Tribal knowledge becomes institutional knowledge.

This is what AI in JDE actually looks like. Not a concept. Not a roadmap item. Something your team naturally embeds into their workflows.

Where Do You Start? 

The organizations that are furthest along on this journey didn't start with the biggest plan. They started with the clearest first step, and most discovered they were further along than they thought.

If you have Orchestrator in your environment, you already have the engine. NL/slash is what turns it on.

Hear It Straight From the Team Building It

KS2 Technologies' Eric Kuefler and Joe Iorio will be walking through this at the Q1 2026 SCUG meeting on March 19th in City of Industry, CA, breaking down how Orchestrator connects to modern AI, what it looks like in a live JDE environment, and what your organization can start doing today, regardless of where you are on your AI journey.

The 30-minute session starts at 2:00. The event is free for all JDE customers and Quest members. If you've been looking for a clear, practical answer to the "what's your AI strategy?" question, this is worth your afternoon.

 → Register for SCUG here and add KS2’s session to your agenda 

 Can't make it to City of Industry on the 19th? We get it, reach out directly, and we'll make sure you don't miss the conversation. 

Connect with the KS2 Team to learn more

FREQUENTLY ASKED QUESTIONS

Do I need to buy new software to start building an AI strategy on JDE? 

If you're running JD Edwards EnterpriseOne with Orchestrator available in your environment, you already have the foundation. NL/slash is the layer that activates it. The starting point isn't a wholesale platform change; it's an assessment of what you have, how well it's configured, and what your business most needs to know faster. Most organizations are closer to getting started than they think.

How does NL/slash connect to JDE? 

NL/slash works through JDE Orchestrator, which exposes your ERP as a set of secure APIs. When you type a question or request in plain English, NL/slash maps your intent to the right JDE tool or orchestration, executes it, and returns the answer in plain language. Your existing security model, roles, and business logic stay completely intact; AI accesses JDE the right way, not around it. Getting that architecture right from the start is what separates pilots that succeed from ones that stall.

How mature does my Orchestrator environment need to be before I can start? 

You don't need to have Orchestrator running everywhere before you begin. Many organizations start with a focused use case, a handful of orchestrations that answer the questions their business asks most often, and build from there. The important thing is having someone who understands both the JDE side and the AI side well enough to connect them thoughtfully. That's exactly where a partner with deep JDE expertise makes the difference.