ETEXperience

Artificial intelligence for JD Edwards

Five solution lines take your company into the agentic era: AI data analysis via MCP server, conversational assistants on JD Edwards, agents with Orchestrator, business intelligence with Power BI and custom AI builds. All run on your current environment and its security model.

Guide: Artificial intelligence for JD Edwards →
UserCFO · CIO · Operations
Teams · WhatsAppTelegram · Web
AI AgentLLM · RAG
MCP · AIS · OrchestratorJDE security & roles
JD Edwardssystem of record
The ETEXperience intelligence layer relies on the MCP server, AIS and Orchestrator, respecting the JD Edwards security model. The ERP remains the system of record.

AI agents and automation with Orchestrator

Procurement (vendor onboarding with validation), collections (reminders and reconciliation), operations (releases, inventory alerts) and close (intercompany checks), via AIS and Orchestrator.
Explore AI agents →

Business intelligence with AI and Power BI

From JDE data to executive dashboards: governed semantic model, automatic refresh and conversational analytics on the same model — no duplicated business definitions.

Custom AI solutions

RAG over your documents and policies, internal assistants, document classification and extraction, and integrations via AIS, REST and BSSV, governed under ISO/IEC 27001.

Query or execute: where a person steps in

Asking for a figure is not the same as running an operation in the ERP. End to End separates both planes so you adopt AI without losing control.

Query — read-only

The MCP server answers business questions with figures traceable to the ERP. A database user restricted to queries blocks any write: AI never modifies JD Edwards.

Execute — with approval

Through AIS and Orchestrator, agents and the assistant trigger processes (approve orders, release held orders, onboard vendors) with the user’s identity and permissions; sensitive actions require approval and are logged.

Security, permissions and traceability

JD EDWARDS SECURITY Every query or action uses the security model you already have: identity, roles and company-level restrictions of the requesting user. No generic users.
ONLY WHAT’S AUTHORIZED MCP queries are read-only; execution actions require human approval and are logged.
YOUR ERP RULES We operate under ISO/IEC 27001:2022 and JD Edwards remains the system of record: AI does not replace it.

Compatibility and requirements

It runs on your current JD Edwards EnterpriseOne 9.2 environment (Tools 9.2.x), relying on the AIS and Orchestrator your ERP already has. No migration or foundational changes required. Configured per client: which companies, which data and which users take part.

FAQ

What is artificial intelligence for JD Edwards?

It means applying language models and agents on top of your ERP to query data, automate processes and converse with the system, without replacing it. End to End delivers it with an MCP server for queries, conversational assistants on Teams, WhatsApp and Telegram, and agents with Orchestrator for automation.

What is the difference between querying with MCP and executing with an agent?

The MCP server is read-only: it answers questions with traceable figures and never writes to the ERP. An agent runs processes (approve, release, onboard) through AIS and Orchestrator, with the user’s identity and permissions, and approval for sensitive actions.

Do I need to migrate or change my JD Edwards version?

No. It connects to your current EnterpriseOne 9.2 instance (Tools 9.2.x) and respects your security model; you adopt AI without touching the ERP foundations.

How are security and data protected?

Every query or action runs with the user’s identity, roles and company-level restrictions, is logged, and no generic users are created. Queries are read-only and we operate under ISO/IEC 27001:2022.

Which channels and languages are supported?

Microsoft Teams, WhatsApp and Telegram, plus web, in Spanish and English.

Take your operations into the agentic era.
Book a demo