# Sap Idoc

> | Diagnoses and reprocesses failing IDocs — the 1 AMS interface incident class — read-only over RFC (no GUI). find runs a bounded EDIDC search (status / message type / partner / date window / docnum), resolves status texts (TEDS2) and severity, and counts failures per status+message type. explain <DOCNUM gives the full EDIDS status history for one IDoc — each step with its severity, message id, parameters and rendered text — plus an SLG1 cross-reference, so the root cause (e.g. "posting period not open", "sold-to party not maintained") is read straight off the log. triage clusters status-51/56 failures by root cause and hands custom-handler clusters to /sap-fix-incident. reprocess status-routes a DOCNUM / cluster / selection to RBDMANI2 / RBDAPP01 / RSEOUT00 via /sap-run-report (confirm-gated) then re-reads EDIDS to verify. Prerequisites: SAP profile via /sap-login (RFC); SAP NCo 3.1 (32-bit). No GUI session, no Z-object dependency for find/explain/triage.

## Facts
- Page: https://tashan.sh/capability/skill-sapdev-ai-sap-idoc
- tashan id: skill:sapdev-ai/sap-idoc
- Source: https://github.com/sapdev-ai/sap-dev
- Type: skill
- Category: other
- tashan score: not scored (catalogued only — too little public evidence)
- Adoption: 9.0
- Upkeep: not measured
- Freshness: not measured
- Evidence coverage: not measured
- Health: abandoned
- Instruction depth: not yet graded
- Official: no

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-08-14 by tashan (https://tashan.sh) from public evidence. Scorer s5.