Use
The following table provides an overview of the errors defined in the standard system and the tasks which are linked to the errors via the process codes. Possible (but not all!) causes of error are specified to aid troubleshooting.
Error |
Process code |
Workflow task |
Possible causes (examples) |
IDoc could not be generated |
EDIM |
TS30000020 |
Inbound: Error reading file;Outbound: Error generating IDoc from an MC record |
IDoc could not be generated under MC |
EDIN: Evaluates the partner data from the MC record |
TS70008037 |
No process code in the additional partner profile MC parameters; Error when writing the application data in the IDoc. |
Status file could not be read completely |
EDIL |
TS70008373 |
|
Error during inbound processing |
EDII |
TS00008068 |
Process code does not exist; |
Error during outbound processing |
EDIO |
TS00007989 |
Error during forwarding via RFC; |
Error during outbound processing affecting all IDocs in an IDoc stack ("Output mode: Collect IDocs") |
EDIP |
TS60001307 |
Error during forwarding via RFC; |
IDoc syntax error (outbound; syntax check activated in partner profiles) |
EDIX |
TS00008070 |
|
IDoc syntax error (inbound; syntax check activated in partner profiles) |
EDIY |
TS00008074 |
|
Error status reported |
EDIS |
TS30000078 |
Conversion error in EDI subsystem |
Error status reported |
EDIR |
TS70008125: In contrast to TS30000078, you can resend the IDoc here |
Conversion error in EDI subsystem |
The errors are processed from the work items in the integrated inbox. If a file read error could be corrected, for example, the IDocs which have not yet been read can be read and stored in the database manually, by starting report program RSEINB00.

Exception handling in the application, which can respond to the status 51 (application document not posted), is similar to exception handling in the IDoc interface.
The exception handling tasks in the IDoc interface are summarized in task group TG70000015, those from logistics applications in group TG20000011. You can display task groups with the Business Workflow Explorer (area menu SWLD).