read-onlySupport
Diagnose
Triages an incident across ST22 dumps, SM37 jobs, SLG1 logs, SM13 updates, IDocs and tRFC, and returns ranked root causes with a single typed next action.
From “it's broken” to a ranked cause and next step, read-only.
Support · read-only
Incident diagnostics, read-only
It diagnoses incidents read-only: dumps, jobs, IDocs, RFC queues. Over the same official ADT channel as Development.
read-only
Read-only incident diagnostics over the same official ADT channel. No RFC SDK, no S-User. Triage across dumps, jobs, logs, IDocs and RFC queues; morning health checks; deep IDoc triage. Each incident becomes a request with findings you decide on. The fix is always handed off, never executed.
What you get: root cause and the next action in minutes, with nothing touched in the system.
What a diagnosis looks like
You paste the symptom. Makion correlates ST22 dumps, SM37 jobs, SLG1 logs, SM13 updates, IDocs and tRFC, and returns ranked root causes with a single typed next action.
- 1You write: the symptom, a ticket text or a screenshot of the error.
- 2Reads the diagnostic tables over ADT: ST22, SM37, SLG1, SM13, IDoc status, tRFC / qRFC.
- 3Correlates the evidence into ranked root causes.
- 4Result: findings with evidence and one typed next action. Nothing changed in the system.
The fix is a handoff
Every Support role is read-only: it physically receives only SAP read tools and cannot change anything. Read-only is a tool boundary, not a prompt-level promise. Reprocessing an IDoc, restarting a job, applying a note: all of it stays with you.
Read-only roles can't write at the tool level, not just at the prompt level. An admin can override any role's methodology or add new ones. How the boundary is enforced →
Three Support roles
Every Support role is read-only. All 23 roles →
read-onlySupport
Health check
A morning sweep of the system: stuck IDocs, failed jobs, tRFC/qRFC backlog and fresh dumps. The health picture before users report it.
Problems found before the first ticket lands.
read-onlySupport
IDoc triage
A deep-dive on IDoc failures: status records, control data and segments (EDIDC / EDIDS / EDID4), to explain why one failed and what to do. Reprocessing stays a handoff.
The real reason an IDoc failed, not just a status number.
Runs on your server
Same server, same AI account as Development. Your SAP connection and credentials stay on your infrastructure. Makion never sees your code. Full details on the security page →
Get started
Put Makion inside your SAP
Your SAP, your standards, your terms.
Several developers or a client rollout? Teams & enterprise