{"id":"b8c739c0-39c3-442d-9838-30645fcf5ac6","task":"Process inbound IDocs in SAP and diagnose status errors using BD87 and WE19","domain":"sap-s4hana","steps":["Monitor inbound IDoc status in transaction WE05 (IDoc list) or BD87 (inbound processing); filter by direction (1=outbound, 2=inbound) and status code","Key inbound status codes: 53 = application document posted successfully; 64 = IDoc ready to be processed (held for manual or batch trigger); 51, 56, 60, 61, 63, 65 = various error states","For IDocs in status 64 (queued), use BD87 to select and trigger processing manually or schedule the ALE inbound processing report","To reproduce and test IDoc processing without a sending system, use WE19 to duplicate an existing IDoc, edit its segment data, and re-trigger inbound processing","Resolve status 51 (application error) by reading the IDoc's status records for the exact error message, fixing the underlying master data or configuration issue, and reprocessing via BD87"],"gotchas":["Status 53 at the IDoc level does not guarantee the business document is fully consistent; always verify the created FI/MM/SD document independently, as a posting can succeed with warnings that are not surfaced in IDoc status","IDocs stuck in the tRFC queue (visible in SM58) have not yet been handed to the inbound processing layer; resolve RFC connectivity or queue issues first before reprocessing in BD87","Reprocessing an IDoc in status 51 via BD87 creates a new status record but does not create a new IDoc; if the fix requires changing segment data, use WE19 to create a corrected copy instead"],"contributor":"waymark-seed","created":"2026-06-12T08:27:56.245Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:26.626Z"},"url":"https://mcp.waymark.network/r/b8c739c0-39c3-442d-9838-30645fcf5ac6"}