Skip to content
MGrid Technologies
AI AgentJD EdwardsSupport & operations

JDE Doctor™

AI-powered support and issue resolution assistant

Part of JDE AgentOS™ · Governed. Reliable. Built for JD Edwards.

Talk to an expertAll Agents
Type
AI Agent
Platform
JD Edwards
Category
Support & operations
Governance
Human approval before any action

The Problem It Solves

Who works with it

  • Support desk
  • JD Edwards administrators
  • Managed services team

Most JD Edwards support tickets are variations of problems the team has already solved: a batch job that failed, a user locked out of an application, a document that will not post. Each one still lands on a consultant, who reads the ticket, hunts through work centre messages, logs and the knowledge base, and writes back, often days later.

JDE Doctor™ handles that first pass. It reads the ticket, checks what actually happened in the system, matches it against known fixes and past tickets, and proposes a resolution with the evidence attached, so the team spends its time on the problems that are genuinely new.

What JDE Doctor™ does

  • Reads incoming tickets and classifies them by application, module and severity

  • Checks work centre messages, job logs and error codes for the affected user or process

  • Matches the symptoms against past tickets, SOPs and Oracle knowledge articles

  • Drafts the resolution, the reply to the user and the steps a consultant should verify

  • Escalates to a named consultant when confidence is low or the fix needs a change

How JDE Doctor™ works

The same governed loop as every Agent on JDE AgentOS™ (monitor, analyse, recommend, execute), applied to this Agent's job. Nothing reaches JD Edwards without a person approving it.

  1. Monitor

    Watches the support queue and the JD Edwards job and message logs for new issues.

  2. Analyse

    Correlates the ticket with system evidence and the history of similar cases.

  3. Recommend

    Proposes a fix, ranked by confidence, with the evidence and the rollback path.

  4. Execute

    Applies routine, pre-approved fixes; everything else waits for a consultant's approval.

Works with

  • JD Edwards

What Data It Touches

  • Reads: support tickets, work centre messages, batch job and error logs, knowledge articles
  • Writes: ticket updates, draft replies, and only pre-approved corrective actions
  • Never touches: financial postings, master data changes or security configuration without approval

Security: Where the Data Stays and Who Can Access It

A governance layer routes every action through human approval workflows, and the action layer only executes JD Edwards transactions that have been approved. The connector layer is AIS, Orchestrator, REST APIs and the database.

Where it sits in the JDE Agent Fabric

JDE Doctor™ lives in the Agent layer. Everything above it governs what it may do; everything below it is how it reads JD Edwards.

  1. 01Action layer

    Execution of approved JDE transactions

  2. 02Governance layer

    Security, audit, human approval workflows

  3. 03Agent layer

    JDE Doctor™ and the rest of the portfolio

  4. 04Reasoning layer

    LLMs, RAG, rules, business policies

  5. 05Enterprise knowledge layer

    Documentation, SOPs, configurations, historical tickets

  6. 06JDE connector layer

    AIS, Orchestrator, REST APIs, database

See JDE Doctor™ on your own data

A short demo against your environment, with your team in the room.

Talk to an expertExplore MGrid Lab