The report RBDAPP01 is used for processing inbound IDocs not passed to the application immediately. This report executable via transaction code SE38. Alternatively, you can use transaction code BD20.
This report forwards all IDocs with:
- Status 64 “ready to be passed to application”
- Status 66 “IDoc is waiting for predecessor IDoc (serialization)
These match the selection criteria to be passed to the application for further processing.
Essentially there are two groups of IDocs:
- IDocs to be serialized in accordance with the associated object.
- All other IDocs
There are also two types of processing:
- Serial processing (IDocs are processed one after each other in one process)
- Parallel processing (IDocs are passed in packets to other processes for processing).
Purpose of parameter ‘Packet size’: For IDocs to be serialized by object and for activated parallel processing, this parameter specifies the size of a packet to be processed in a task. If applicable, independent objects are processed in a separate task as with serial processing. (Large packet sizes lowers the level of parallel processing).
For all other IDocs, as far as possible, an appropriately sized document is passed to the application. On the one hand, this supports some applications capable of mass processing. On the other hand, the number of parallel packets is less as with activated parallel processing. (Lower system load, longer runtime).
Notes on Program Terminations in Parallel Processing
In parallel processing, processes containing the IDocs to be processed are started in parallel. If there is a termination (dump/ A message), no message is issued by RBDAPP01. The best way to identify such problems is to run RBDAPP01 without parellel mode after a scheduled RBDAPP01 with parallel mode. Then a termination is logged (dialog message or message in job log).
Output
The processed IDocs are output.
