RFC / Queue Incident Decoder
Paste one LUW or queue error from SM58, SMQ1 or SMQ2. Get a rule-based explanation, the evidence behind it and checks to work through before retrying. No SAP connection or AI call is made.
Free · No sign-in · No AI credits. Analysis runs in this browser. Pasted logs are not uploaded or saved; copy/download happens only when you choose it.
Analyzer loading…
Collect the first failing entry
Use SM58 for transactional RFC, SMQ1 for outbound queues and SMQ2 for inbound queues. Copy the full error, reported state and nearby messages from one attempt. Keep the destination/client, timestamp and business reference available to the owning team.
SYSFAIL points to a processing exception; CPICERR needs the detailed communication message. READY or RUNNING alone does not prove a failure. A stopped or dependent queue may be waiting intentionally. This analyzer does not infer a queue's age, inspect your scheduler or confirm delivery.
Preserve order and business outcomes
Resolve the first blocking LUW with its application owner. Before retrying, check whether the target already processed the business request. Deleting entries or bypassing serialization can lose work or break sequence; XI/EOIO flows may require recovery through the owning application's monitor.
SAP references and related tools
- SAP: transactional RFC and queued RFC monitoring
- SAP: inbound queue states and dependencies
- SAP: XI message restart and EOIO restrictions
- IDoc Incident Doctor for an IDoc status and posting message.
- Background Job Failure Analyzer for an SM37 job attempt.
- Issue Copilot for a broader investigation (free to try; existing AI limits apply). Inputs are not transferred automatically.
This tool provides triage guidance, not a system diagnosis. Behavior depends on SAP release and application ownership; verify in your own system before changing production. ERPClimb is independent of SAP SE.