Getting Started New sletters

Welcome, Guest

Login

Register

Store

Search the Community

Products

Services & Support

About SCN

Downloads

Industries

Training & Education

Partnership

Developer Center

Lines of Business

University Alliances

Events & Webinars

Innovation

ABAP Development

IDoc Statuses
Created by Vijay kumar.Kalaveni, 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 w as copied from SDN blog - Troubleshooting of ALE Process by Raja Thangamani, Jul. 19, 2007, and broadly adapted.

Sequence of Inbound and Outbound statuses

Unknow n 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

num ber

of

Status description

success

status

status

01

Success

Outbound IDoc created

02

Error

Error passing data to port

Next

30

Next error status

Error reason

Solution to error

29
Correct the error and Execute RSEOUT00
program again

03

Success

Outbound IDoc successfully

None, 32

sent to port
04

Error

w ithin 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 check of

Missing mandatory segment for

You may edit the IDoc or force it to be

outbound IDoc

example

processed

02

Partner profile customized to not run

29

Error

ALE service (for example

29, 31

30

Success

Outbound IDoc ready for

03

dispatch (ALE service)

31

Error

no further processing

32

Success

Outbound IDoc w as edited

There w as a manual update of

the IDoc in SAP tables, the
original w as saved to a new
IDoc w ith status 33

33

Success

Original of an IDoc w hich

w as edited. It is not possible
to post this IDoc

35

Success

IDoc reloaded from archive.

None

None

Backup of another IDoc manually updated, see

status 32

Execute RSEOUT00 program

Can't be processed
37

Error

Erroneous control record (for

None, 37

example, "reference" field

should be blank for outbound
IDocs)
42

Success

Outbound IDoc manually

01

37

created by WE19 test tool

50

Success

Inbound IDoc created

64

65

51

Error

inbound IDoc data contains

53, 64

51, 66, 68, 69

errors

Error triggered by SAP application, incorrect

Ask functional people, modify

values in the IDoc data

erroneous values in the IDoc

(WE02 for example) and run it
again using BD87

53

Success

inbound IDoc posted

None, 53

56

Error

IDoc w ith errors added (You

50, 51, 56,

should never see this error

62, 68

code)
60

Error

syntax check of inbound IDoc

56, 61, 62

61

Error

Processing inbound IDoc

64

despite syntax error

62

Success

inbound IDoc passed to

53

51

62

51, 60, 63, 68, 69

application
63

Error

passing IDoc to application

64

Success

Inbound IDoc ready to be

execute BD20 transaction

passed to application
65

Error

ALE service - incorrect

(RBDAPP01 program)
64, 65

partner profiles
66

Waiting

Waiting for predecessor IDoc

51

(Serialization)
68

Success

no further processing

68

None

The IDoc w as created using inbound test tool

(WE19) and w ritten to file to do file inbound test.
Another IDoc is created if immediate processing
is chosen

69

Success

IDoc w as edited

64

51, 68, 69

There w as a manual update of the IDoc in SAP

tables, the original w as saved to a new IDoc
w ith status 70

70

Success

Original of an IDoc w hich

None

None

w as edited. It is not possible

Backup of another IDoc manually updated, see

status 69

to post this IDoc

71

Success

Inbound IDoc reloaded from

archive. Can't be processed

74

Success

Inbound IDoc manually

50, 56

created by WE19 test tool

More information about Inbound statuses

64 -> 62 : There is no w ay to distinguish automatic call from manual call (BD20, RBDAPP01)
Though an IDoc may contain partner profile errors, w e may force inbound processing (status becomes 62), but then an error w ill happen again
RSEINB00 program to process IDocs from a file
BD20 transaction (RBDAPP01 program) to process IDocs in status 64. If you w ant 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). Answ er from Rainer Hbenthal in SDN forum: "Idocs w ith w ith 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 dow n) 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 w ith SM58 and initiate resending by right click choosing execute LUW.
in BD75 you can check "unsent idocs" and you w ill get a similar list."
Note 189887 - ALE: Help report to search for IDocs sent tw ice: 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 w aiting to be processed).
RSEXARCL to reload IDocs from archive to the database. Status w ill 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

2 Comments
Guest
Very useful summary of statuses - thanks.

Alen S
Excellent: Many thanks

Contact Us
Privacy

SAP Help Portal

Terms of Use

Legal Disclosure

Copyright

Follow SCN