IDoc Errors Explained: Status 51, 56, 29 and 02, Reprocessing with BD87 and Testing with WE19

Keep this: job aid

IDoc error triage card

• Read in order: control record, status records bottom up, long text of the first error, then data records.
• Inbound: 51 not posted (read the message), 56 partner profile, 60 syntax, 64 waiting for RBDAPP01, 66 predecessor, 68 closed for good.
• Outbound: 30 waiting for RSEOUT00 (WE14), 02 port or destination, 29 ALE service, 26 syntax from custom code, 03 handed to port only.
• 03 but partner has nothing: check SM58, then the middleware monitor, then the partner's 997.
• Fix the cause first (master data, customizing by transport, partner profile, job), then reprocess the original IDoc.
• Reprocess with BD87; jobs: RBDMANI2 (51), RBDAPP01/BD20 (64), RBDAGAI2/BD84 (56, 65), RSEOUT00/WE14 (30), RBDAGAIN/BD83 (02, 29).
• Never edit amounts, prices, tax, bank data or quantities; edits leave 69/70 (inbound) or 32/33 (outbound).
• Close IDocs that must not post (68 or 31) and record the replacement document.
• Prove fixes in CMQ with WE19 Standard Inbound: one positive and one negative case, plus the business document.
• Close the incident on business confirmation plus cause, transport, test and reprocessing evidence.