Showing posts with label SE38. Show all posts
Showing posts with label SE38. Show all posts

Tuesday, 9 September 2014

IDOC Status Codes and Reprocess reports

After the process of inbound function module and outbound function module the state of status will be recorded in the status record of IDOC. We can view the status by using transaction codes WE02, WE05 and WE07.Here is the list of main IDOC stats codes for Outbound and Inbound IDOC.

Outbound IDOC status codes with status description.

01: IDoc generated
02: Error passing data to port (It’s an error status)
03: Data passed to port OK
04: Error within control information of EDI subsystem
05: Error in translation
06: Translation successful.
07: Error on syntax check (It’s an error status)
08: Syntax check successful
09: Error on interchange handling (It’s an error status)
10: Interchange handling successful
11: Error on dispatch (It’s an error status)
12: IDOC Dispatch successful
13: Retransmission successful
14: Interchange Acknowledgement positive
15: Interchange Acknowledgement negative (It’s an error status)
16: Functional Acknowledgement positive
17: Functional Acknowledgement negative (It’s a warning error status)
18: Triggering EDI subsystem successful
19: Data transfer for test successful
20: Error on triggering EDI subsystem (It’s an error status)
21: Error on passing data for test (It’s an error status)
22: Dispatch successful, acknowledgement still due
23: Error on retransmission (It’s an error status)
24: Control information of EDI subsystem successful
25: Processing despite syntax error (It’s a warning error)
26: Error during syntax check of IDoc (It’s an error status)
27: Error in ALE dispatch level (It’s an error status)
29: Error in ALE service (It’s an error status)
30: IDoc is ready for dispatch in ALE service
31: IDOC is marked for deletion.
32: IDoc was edited
33: Original of an IDoc which was edited
34: Error in control record of IDoc (It’s an error status)
35: IDoc reloaded from archive
36: Timeout error on Electronic signature not performed (It’s an error status)
37: IDoc added incorrectly (It’s an error status)
38: IDoc archived
39: Arrival of IDOC in target system confirmed
40: Application document not created in target system (It’s an error status)
41: Application document created in target system

Inbound IDOC status codes with status description.

42: IDoc was created by test transaction
50: IDoc added
51: Application document not posted (It’s an error status)
52: Application document partially posted (It’s an error status)
53: Application document posted successfully.
54: Error during formal application check (It’s an error status)
55: Formal application check successful
56: IDoc with errors added (It’s an error status)
57: Test IDoc: Error during application check (It’s an error status)
60: Syntax error on IDOC (It’s an error status)
61: Processing despite syntax error (It’s a warning error status)
62: IDoc passed to application
63: Error passing IDoc to application (It’s an error status)
64: IDoc ready to be transferred to application
65: Error in ALE service (It’s an error status)
66: IDoc is waiting for predecessor IDoc in serialization process
68: IDOC is marked for deletion.
69: IDoc was edited
70: Original of an IDoc which was edited
71: IDoc reloaded from archive
73: IDoc archived
74: IDoc was created by test transaction

Using the standard report RC1_IDOC_SET_STATUS we can change the status of an IDOC if we require for that. We can reprocess IDoc if we are getting errors.

We can reprocess IDoc if we are getting errors. Several standard reports are available for this reprocessing. Here are some standard reports for reprocessing of IDOC.

Report RBDMANI2
We can execute this program for manual reprocess of IDOC. It can be used when we get the status 51 or status 63 errors for an inbound IDOC.
Report RBDMANIN
It used for Posting of inbound IDocs with Status 51.
Report RBDMOIND

It checks whether the communication with tRFC was successfully completed. If successfully completed, the status of the IDoc is changed. This reprocess program can be used for outbound IDOC with status codes from 03 to 12.
Report RSEOUT00
For reprocessing outbound IDOC with status 30
Report RBDAPP01
For reprocessing inbound IDOC with status 64
Report RBDAGAIN
It for reprocessing of incorrect outbound IDOC with statuses 02, 04, 05, 25 and 29
Report RBDAGAI2
It for reprocessing of IDOCs after ALE input error with statuses 56, 61, 63 and 65
Report RBDAGAIE
It for reprocessing of Edited IDOCs with status 32 and 69

Changing an IDoc's status:
Idoc’s current status.. you wish to change.


SE38 – ABAP editor
Pgm RC1_IDOC_SET_STATUS



click on execute

IDOC entry and status change screen:

Selection entered.




click on 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 displayed



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




Wednesday, 3 September 2014

Do we need to really log-out and log-in again to make authorization changes effective?

Whenever any changes were made to the user authorizations, normally it is required to log-out and log-in again to make these changes effective.

Here is an alternative:


Execute the report RSUSR405 in SE38. This would refresh all user-related buffers and changes to the authorizations are made effective immediately.