Posting IDocs in Parallel

This is used for:

·        Immediate processing

When IDocs are processed immediately, all dialog processes on the receiving application system are used for posting. This could block the application server. You cannot distribute inbound IDoc packets among one server group.

An IDoc packet may consist of one or more IDocs. A dialog process to execute the posting function module is started on the application server for every IDoc packet. If the IDoc packet consists of several IDocs, and if the posting function module is not capable of mass processing, the ALE layer calls the function module several times in the same dialog process and each time transfers a single IDoc for processing.

·        Background processing

Inbound IDoc packets are split into individual IDocs and are stored in the database.

You can process IDocs that are ready for transfer (status 64) manually in ALE Administration (Monitoring ® IDoc Display ® Status Monitor- BD87). 

Alternatively, IDocs can be processed in the background.
To do this, in ALE Customizing choose:
Set-Up System Monitoring
   Post IDocs
     Post IDocs in Recipient System

All application servers in a server group can be used in parallel for updating IDocs in the background. There might be only one application server in a server group. If you do not specify a server group, all dialog processes in the local server are used in parallel.  This could block the application server.

For mass data it is better to process IDocs in parallel.

You must select the option Parallel posting on the screen Inbound processing of IDocs ready for transfer in the program RBDAPP01.

Specify a server group for parallel updating on several applications.

Because two dialog processes remain unused on every application server in a server group, make sure there are enough dialog processes available on the application servers.