IDoc status Description

No.

Description

01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
29
30
31
32
33
34
35
36
37
38
39
40
41
42
50

IDoc created
Error passing data to port
Data passed to port OK
Error within control information of EDI subsystem
Error during translation
Translation OK
Error during syntax check
Syntax check OK
Error during interchange handling
Interchange handling OK
Error during dispatch
Dispatch OK
Retransmission OK
Interchange Acknowledgement positive
Interchange Acknowledgement negative
Functional Acknowledgement positive
Functional Acknowledgement negative
Triggering EDI subsystem OK
Data transfer for test OK
Error triggering EDI subsystem
Error passing data for test
Dispatch OK, acknowledgement still due
Error during retransmission
Control information of EDI subsystem OK
Processing despite syntax error (outbound)
Error during syntax check of IDoc (outbound)
Error in dispatch level (ALE service)
Error in ALE service
IDoc ready for dispatch (ALE service)
Error - no further processing
IDoc was edited
Original of an IDoc which was edited
Error in control record of IDoc
IDoc reloaded from archive
Electronic signature not performed (timeout)
IDoc added incorrectly
IDoc archived
IDoc is in the receiving system (ALE service)
Application document not created in receiving system
Application document created in receiving system
IDoc was created by test transaction
IDoc added

Changing an IDoc's status (By Nadine Hughes)

Idocs current status.. you wish to change.

SE38 ABAP editor

Pgm RC1_IDOC_SET_STATUS

click

execute

IDOC entry and status change screen:

Selection entered:

click

execute

and remove the test check if you want it to process. .. the check will run a
report with the number effected.. if you want to process.

and the report below is diaplayed

ALL orders status 51 idocs have been changed to 68

NOTE:
leave the message type BLANK if you want to use the IDOC number for selection

Sequence of Inbound and Outbound statuses

Starting statuses may be: 01 (outbound), 50 (inbound), 42 (outbound test), 74 (inbound test)
Status

Next

Next

Status

Type of

descriptio

success

error

number

status

status

status

30

29

Error reason

Outbound
IDoc
1

Success

created

Correct the error

Error

Error

and Execute

passing

RSEOUT00

data to port

program again

Outbound
IDoc
successfully
3

Success

sent to port None, 32

within
control
information
on EDI

Error

subsystem
during

Error

translation
Changed
from
status 03
by BD75
transactio

12

Success

Dispatch

n (see

OK

below)

Solution to error

Processing
outbound
IDoc
despite
syntax
25

Success

errors
Missing

26

Error

during

mandator

syntax

check of

segment

You may edit the

outbound

for

IDoc or force it to

IDoc

example

be processed

ALE service
(for
29

Error

example

29, 31

Outbound
IDoc ready
for dispatch

Partner profile

(ALE
30

Success

31

Error

service)

customized to not
3

run

no further
processing
There was
a manual
update of
the IDoc
in SAP
tables,
the
original
was
saved to a

32

Success

Outbound

new IDoc

IDoc was

with

edited

status 33

Original of
an IDoc
which was
edited. It is

Backup of another

not possible

IDoc manually

to post this
33

Success

IDoc

updated, see
None

None

status 32

Execute RSEOUT00 program

IDoc
reloaded
from
archive.
Can't be
35

Success

processed
Erroneous
control
record (for
example,
"reference"
field should
be blank for
outbound

37

Error

IDocs)

None, 37

Outbound
IDoc
manually
created by
WE19 test
42

Success

tool

37

64

65

Inbound
IDoc
50

Success

created

inbound

Error triggered by

Ask functional people, modify

IDoc data

SAP application,

erroneous values in the IDoc

51, 66,

incorrect values in

(WE02 for example) and run it

68, 69

the IDoc data

again using BD87

contains
51

Error

53

Success

errors

53, 64

inbound
IDoc posted None, 53
IDoc with
errors
added (You
should
never see
56

Error

this error

50, 51,

code)

56, 62, 68

syntax
check of
inbound
60

Error

IDoc

56, 61, 62

Processing
inbound
IDoc
despite
syntax
61

Error

error

64

inbound
IDoc
passed to
62

Success

application

53

51

passing
IDoc to
63

Error

application
Inbound
IDoc ready
to be
passed to

64

Success

application

62

51, 60,

Execute BD20 transaction

63, 68, 69

(RBDAPP01 program)

ALE service
- incorrect
partner
65

Error

profiles

64, 65

Waiting for
predecesso
r IDoc
(Serializatio
66

Waiting

n)

51

The IDoc was

created using
inbound test tool
(WE19) and
written to file to do
file inbound test.
Another IDoc is
created if
immediate
no further
68

Success

processing

processing is
68

None

chosen

There was a
manual update of
the IDoc in SAP
tables, the original
was saved to a
IDoc was
69

Success

edited

new IDoc with

64

51, 68, 69 status 70

Original of
an IDoc
which was
edited. It is

Backup of another

not possible

IDoc manually

to post this
70

Success

IDoc

updated, see
None

None

status 69

Inbound
IDoc
reloaded
from
archive.
Can't be
71

Success

processed
Inbound
IDoc
manually
created by
WE19 test

74

Success

tool

50, 56

Docs: Mass Deletion and

Changing Status
By Ashish GauravIDOCS, SAP BASISLeave a Comment

Mass Change of SAP IDOC Status

From time to time it becomes necessary to change the status of SAP IDOCs in SAP. The most
common scenario is the requirement to mark SAP IDOCs for deletion. There is no good way to mass

mark IDOCs for deletion via the standard IDOC processing transaction BD87. However there is a
program that will let you change status.
RC1_IDOC_SET_STATUS
CAUTION: This program should be used with great care and consideration. Improper use of
this program can result in data consistency issues. Make sure you know what you are
deleting, why you are deleting it, and what is required to correctly update you system after
deleting.

Example: Marking IDOCs for Deletion In

Mass
It is pretty typical for support users to set the deletion flag on IDOCs that have been incorrectly
created and have error. When there are a small number of IDOCs this is possible via transaction
BD87.
An inbound IDOC in error will have the status 51, when it is marked for deletion it has a status of 68.
A view of the IDOCs to be deleted in WE05.

To mass delete IDOCs run the following program via SE38: RC1_IDOC_SET_STATUS via the SAP
Transaction: SE38

There are only a few parameters on the selection screen for this program. It is most important that
you correctly restrict the IDOCs you select with this program. The program automatically defaults to
marking inbound IDOCs in error for deletion.
To mass select IDOCs to be marked for deletion select:

There are many options for selecting and restricting the IDOCs to Mass process. Select by single
value or range. Restrict by single value or range.
The

allows you to upload a list of IDOCs from a text file.

The

allows you to apply a list from your clipboard.

Execute the program

Check the status of the 3 IDOCs in WE05

Example: Changing IDOCs Status To Repost

It is also possible to use this program to reset an IDOC so that it can be reprocessed.

With the following selection we are going to reset the IDOCs with status 68 marked for deletion back
to status 64 to try and reprocess them.
Execute the program

As you can see, program RC1_IDOC_SET_STATUS is very helpful, but please be careful when you
use it!