Outbound IDoc, Distribution Model and Reprocessing

Explanation

Outbound IDocs are triggered by a change pointer or explicit call, routed by the ALE distribution model (BD64), sent via tRFC (SM58) to the partner. Failed IDocs sit in status 02/03/29 and can be reprocessed via BD87. Change pointers are managed by BD50/BD52/BD61.

Code example

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'  EXPORTING master_idoc_control  = ls_control            master_idoc_data     = lt_data  IMPORTING return               = ls_return.

Real project scenario

After a network incident 12k outbound MATMAS IDocs failed. BD87 reprocessed the batch in 30 minutes without data entry.

Common mistakes

Forgetting to activate change pointers per message type; distributing every field change instead of relevant ones.

Best practices

Monitor SMQ2/SM58; schedule RSNAST00 or RBDMIDOC as needed; batch outbound to reduce network chatter.

Interview angle

Difference between tRFC and qRFC.