Reprocessing and Deletion of IDOC

IDOCs are Intermediate Documents which are used for the communication between two SAP systems which can be having the encoded data which SAP system only can read.

IDOCs will be getting transferred between SAP systems and will sometime fails due to the lack of resources or due to queue stuck etc.

In such situations, we'd like to reprocess the idocs. Below are the steps which shows us to re-process/flag the IDOCs in SAP system.

How to reprocess an Idoc:

1. Go to transaction BD87

2. Enter Idoc number, and make sure the dates are correct

3. Click the Execute button or press F8

4. To reprocess, select the Idoc status within the "IDOC in inbound processing" tree.

5. Click the Process button

6. the subsequent screen will give the status of the IDOC and wheter it processed sucessfully

How to flag an Idoc to be deleted:

1. Go to transaction BD87

2. Enter Idoc number, and make sure the dates are correct

3. Click the Execute button or press F8

4. To delete, select the Idoc status within the tree and click on EDIT -> RESTRICT AND PROCESS

5. Click the Execute button

6. Un-check the Bkgd Processing checkbox.

7. Click the Execute button

8. Click the Delete Flag button.

Administration of IDoc Communication

IDoc communication is predicated on transactional Remote call (tRFC).

You can optimize the performance of ALE processing by using the subsequent settings and procedures.

Suppressing Background Processing
If tRFC errors occurs in the standard SAP system, , a background job is generated to re-establish the connection. In certain circumstances this might end in an outsized number of background jobs being started that completely block backgrounding .

Note:
Use program RSARFCEX to restart tRFC to cancel a background job if tRFC errors occur .

Select a connection to change in ALE Customizing (transaction SALE), 

Communication

Create RFC Connections (SM59)

Choose Destination ® tRFC Options and select the option Suppress Background Job at Comm. Error.

Setting Dispatch Status to OK
When an IDoc is passed to the communication layer, it's assigned a globally unique transaction identifier (TID). If the IDoc has been successfully dispatched, this information isn't automatically passed to the ALE communication layer. So that ALE processing sets the IDoc status to Dispatch OK, you ought to compare the TID numbers within the communication layer and therefore the ALE layer.

The SAP program RBDMOIND checks that the IDocs passed to the tRFC have already been sent to the receiving SAP system. If they need been sent, the IDoc status is modified to "12" - Dispatch OK

Note:
To set the IDoc dispatch status, run the program RBDOIND after the IDocs are passed to the communication layer.

Checking the tRFC Status

Use
Transactional RFC calls which transfer IDocs use the function module IDOC_INBOUND_ASYNCHRONOUS at reception (before release 4.0: INBOUND_IDOC_PROCESS).

If an IDoc in the sending system has been passed to tRFC (IDoc status "03"), but has not yet been input in the receiving system, this means that the tRFC call has not yet been executed.

Activities
To check the status of the tRFC calls, select Tools -> IDoc Interface/ALE -> Administration -> Monitoring -> Troubleshooting -> RFC Queue (SM58) and setout any additional selection criteria.

The program RSARFCEX restarts unsuccessful tRFC calls.

Note:
You cannot choose the choice is being executed in backgrounding .