sc4sap:analyze-symptom

To analyze SAP runtime dumps and identify the root cause, query the live system through MCP to auto-collect dumps, system state, recent transports, and code call graphs, narrowing findings into 2–3 viable hypotheses with confidence levels and concrete verification steps.

The best way to triage SAP incidents with minimal manual investigation is using MCP-driven auto-collection to gather dumps, system state, recent transports, and where-used relations, which reduces ambiguity and generates SAP Note keywords and actionable remediation steps.

Yes, you can use MCP to check recent transports when troubleshooting SAP ABAP dumps. The auto-investigation queries the live SAP system through MCP to collect transport logs and code context alongside runtime errors to build evidence-based hypotheses.

SAP incident triage through MCP requires a connection to the live SAP system via MCP to directly query for dumps, transports, and code context. You provide an incident description and the analysis auto-investigates to return prioritized hypotheses and recommended actions.

SAP incident analysis returns multiple hypotheses instead of a single root cause to reduce ambiguity. By collecting evidence through MCP, it narrows findings to 2–3 viable options with explicit confidence levels, guiding you through concrete verification paths and SAP Note keywords.