IDoc statuses
Table TEDS1 contains list of all status codes.
Starting statuses may be: 01 (outbound), 50 (inbound), 42 (outbound test), 74 (inbound test)
Status number
|
Type of status
|
Status description
|
Next success status
|
Next error status
|
Error reason
|
Solution to error
|
|---|---|---|---|---|---|---|
01
|
Success
|
Outbound IDoc created
|
30
|
29
| ||
02
|
Error
|
Error passing data to port
|
Correct the error and Execute RSEOUT00 program again
| |||
03
|
Success
|
Outbound IDoc successfully sent to port
|
None, 32
| |||
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 check of outbound IDoc
|
Missing mandatory segment for example
|
You may edit the IDoc or force it to be processed
| ||
29
|
Error
|
ALE service (for example
|
29, 31
| |||
30
|
Success
|
Outbound IDoc ready for dispatch (ALE service)
|
03
|
02
|
Partner profile customized to not run
|
Execute RSEOUT00 program
|
31
|
Error
|
no further processing
| ||||
32
|
Success
|
Outbound IDoc was edited
|
There was a manual update of the IDoc in SAP tables, the original was saved to a new IDoc with status 33
| |||
33
|
Success
|
Original of an IDoc which was edited. It is not possible to post this IDoc
|
None
|
None
|
Backup of another IDoc manually updated, see status 32
| |
35
|
Success
|
IDoc reloaded from archive. Can't be processed
| ||||
37
|
Error
|
Erroneous control record (for example, "reference" field should be blank for outbound IDocs)
|
None, 37
| |||
42
|
Success
|
Outbound IDoc manually created by WE19 test tool
|
01
|
37
| ||
50
|
Success
|
Inbound IDoc created
|
64
|
65
| ||
51
|
Error
|
inbound IDoc data contains errors
|
53, 64
|
51, 66, 68, 69
|
Error triggered by SAP application, incorrect values in the IDoc data
|
Ask functional people, modify erroneous values in the IDoc (WE02 for example) and run it again using BD87
|
53
|
Success
|
inbound IDoc posted
|
None, 53
| |||
56
|
Error
|
IDoc with errors added (You should never see this error code)
|
50, 51, 56, 62, 68
| |||
60
|
Error
|
syntax check of inbound IDoc
|
56, 61, 62
| |||
61
|
Error
|
Processing inbound IDoc despite syntax error
|
64
| |||
62
|
Success
|
inbound IDoc passed to application
|
53
|
51
| ||
63
|
Error
|
passing IDoc to application
| ||||
64
|
Success
|
Inbound IDoc ready to be passed to application
|
62
|
51, 60, 63, 68, 69
|
execute BD20 transaction (RBDAPP01 program)
| |
65
|
Error
|
ALE service - incorrect partner profiles
|
64, 65
| |||
66
|
Waiting
|
Waiting for predecessor IDoc (Serialization)
|
51
| |||
68
|
Success
|
no further processing
|
68
|
None
|
The IDoc was created 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 edited
|
64
|
51, 68, 69
|
There was a manual update of the IDoc in SAP tables, the original was saved to a new IDoc with status 70
| |
70
|
Success
|
Original of an IDoc which was edited. It is not possible to post this IDoc
|
None
|
None
|
Backup of another IDoc manually updated, see status 69
| |
71
|
Success
|
Inbound IDoc reloaded from archive. Can't be processed
| ||||
74
|
Success
|
Inbound IDoc manually created by WE19 test tool
|
50, 56
|
No comments:
Post a Comment