8/19/2020 IDoc Statuses - ABAP Development - Community Wiki

Dashboard

IDoc Statuses
Created by Anonymous, last modified by Sandra Rossi on Apr 21, 2010

Sequence of Inbound and Outbound statuses

Table of statuses
More information about Inbound statuses
More information about Outbound statuses
Miscellaneous
Note: The initial version was copied from SDN blog - Troubleshooting of ALE Process by Raja Thangamani, Jul. 19,
2007, and broadly adapted.

Sequence of Inbound and Outbound statuses

Unknown macro: {gliffy}

Table of statuses
Table TEDS1 contains list of all status codes.
Starting statuses may be: 01 (outbound), 50 (inbound), 42 (outbound test), 74 (inbound test)

Status Type Status Next Next error Error reason Solution to

number of description success status error
status status

01 Success Outbound 30 29
IDoc created

02 Error Error passing Correct the error and

data to port Execute RSEOUT00
program again

03 Success Outbound None, 32

IDoc
successfully
sent to port

04 Error within control

information on
EDI
subsystem

05 Error during
translation

12 Success Dispatch OK Changed from

status 03 by
BD75
transaction
(see below)

25 Success Processing
outbound IDoc
despite syntax
errors

26 Error during syntax Missing You may edit the IDoc

check of mandatory or force it to be
outbound IDoc segment for processed
example

https://wiki.scn.sap.com/wiki/display/ABAP/IDoc+Statuses 1/5
8/19/2020 IDoc Statuses - ABAP Development - Community Wiki

Status Type Status Next Next error Error reason Solution to

number of description success status error
status status

29 Error ALE service 29, 31

(for example

30 Success Outbound 03 02 Partner profile Execute

IDoc ready for customized to not run RSEOUT00
dispatch (ALE program
service)

31 Error no further
processing

32 Success Outbound There was a

IDoc was manual update
edited of the IDoc in
SAP tables,
the original
was saved to a
new IDoc with
status 33

33 Success Original of an None None Backup of another

IDoc which IDoc manually
was edited. It updated, see status 32
is not possible
to post this
IDoc

35 Success IDoc reloaded

from archive.
Can't be
processed

37 Error Erroneous None, 37

control record
(for example,
"reference"
field should be
blank for
outbound
IDocs)

42 Success Outbound 01 37
IDoc manually
created by
WE19 test tool

50 Success Inbound IDoc 64 65

created

51 Error inbound IDoc 53, 64 51, 66, 68, 69 Error triggered by SAP Ask functional
data contains application, incorrect people, modify
errors values in the IDoc data erroneous
values in the
IDoc (WE02 for
example) and
run it again
using BD87

53 Success inbound IDoc None, 53

posted

https://wiki.scn.sap.com/wiki/display/ABAP/IDoc+Statuses 2/5
8/19/2020 IDoc Statuses - ABAP Development - Community Wiki

Status Type Status Next Next error Error reason Solution to

number of description success status error
status status

56 Error IDoc with 50, 51,

errors added 56, 62,
(You should 68
never see this
error code)

60 Error syntax check 56, 61,

of inbound 62
IDoc

61 Error Processing 64
inbound IDoc
despite syntax
error

62 Success inbound IDoc 53 51

passed to
application

63 Error passing IDoc

to application

64 Success Inbound IDoc 62 51, 60, 63, 68, execute BD20

ready to be 69 transaction
passed to (RBDAPP01
application program)

65 Error ALE service - 64, 65

incorrect
partner
profiles

66 Waiting Waiting for 51

predecessor
IDoc
(Serialization)

68 Success no further 68 None The IDoc was created

processing using inbound test tool
(WE19) and written to
file to do file inbound
test. Another IDoc is
created if immediate
processing is chosen

69 Success IDoc was 64 51, 68, 69 There was a manual

edited update of the IDoc in
SAP tables, the
original was saved to a
new IDoc with status
70

70 Success Original of an None None Backup of another

IDoc which IDoc manually
was edited. It updated, see status 69
is not possible
to post this
IDoc

71 Success Inbound IDoc

reloaded from
archive. Can't
be processed

https://wiki.scn.sap.com/wiki/display/ABAP/IDoc+Statuses 3/5
8/19/2020 IDoc Statuses - ABAP Development - Community Wiki

Status Type Status Next Next error Error reason Solution to

number of description success status error
status status

74 Success Inbound IDoc 50, 56

manually
created by
WE19 test tool

More information about Inbound statuses

64 -> 62 : There is no way to distinguish automatic call from manual call (BD20, RBDAPP01)
Though an IDoc may contain partner profile errors, we may force inbound processing (status becomes 62), but
then an error will happen again
RSEINB00 program to process IDocs from a file
BD20 transaction (RBDAPP01 program) to process IDocs in status 64. If you want future IDocs to be processed
immediately, change partner profile customizing (WE20).

RBDINPUT program:
status 51: BD73 / RBDMANIN
status 56, 61, 63, 65: BD84 / RBDAGAI2
status 60: RBDSYNEI
status 62: IDocs remaining in status 62 is abnormal. Use program RBDCHSTA ([Note 92552 - IDocs-Status
62 cannot be processed||http://service.sap.com/sap/support/notes/92552]), so that to change their status
back to 64 and process them again
status 64, 66: BD20 / RBDAPP01
status 68: WPIE / RBDAGAIE

More information about Outbound statuses

RBDOUTPU program:
status 02, 04, 05, 25, 29: BD83 / RBDAGAIN
status 26: RBDSYNEO
status 30: WE14 / RSEOUT00
status 32: WPIE / RBDAGAIE
-> 03 : IDocs are sent to the tRFC queue.
03 -> 12 : use BD75 transaction (RBDMOIND program). Answer from Rainer Hübenthal in SDN forum: "Idocs with
with status 03 are transferred to the tRFC queue. This does not mean that they are sent out, they may stuck up on
that queue (e.g. receiver system is down) in that queue. BD75 checks if it can find the idoc in that queue. If so, it is
not beeing send and status remains on 03. If it is not on the t-rfc queue, the systems considers that this icon is
sent and change the status to 12.
You can check the tRfc queue with SM58 and initiate resending by right click choosing execute LUW.
in BD75 you can check "unsent idocs" and you will get a similar list."
Note 189887 - ALE: Help report to search for IDocs sent twice: program ZDUPLICATEIDOC

Miscellaneous
RC1_IDOC_SET_STATUS program to change IDoc status. Exists since 6.10
Monitor for Inbound and Outbound: BD87 / RBDMON00 to restart erroneous IDocs
Archiving:
RSEXARCA archives IDocs. They must be in an archivable status (not possible to archive IDocs in status
30 or 64, ie waiting to be processed).
RSEXARCL to reload IDocs from archive to the database. Status will be either 35 (outbound) or 71
(inbound).
WE47 to change STACUST table; see [Note 26564 - IDoc: Can status values be defined?
||http://service.sap.com/sap/support/notes/26564]
RSECSTAT include contains constants for status

idoc

5 Comments
https://wiki.scn.sap.com/wiki/display/ABAP/IDoc+Statuses 4/5
8/19/2020 IDoc Statuses - ABAP Development - Community Wiki

Unknown User (104z9w9st)

Very useful summary of statuses - thanks.

Former Member
Excellent: Many thanks

Ilakkiaraj Sampath Kumar

As on 2016, the number of statuses is 76. (Starts from 00, ends at 75)

Former Member
Very good collation of important bits at one place.Just one observation which needs to be checked.
for Inbound idocs WPIE / RBDAGAIE supports status 69 rather then status 68 as far as i know.

Former Member
Excellent collection

Privacy Terms of Use Legal Disclosure Copyright Trademark Cookie Preferences

https://wiki.scn.sap.com/wiki/display/ABAP/IDoc+Statuses 5/5