Posting IDocs in Packets
There are two groups of function modules used to post IDocs:
INPUTTYP contains the code for posting function modules. It can contain the following values:
To display the function module's INPUTTYP, in Customizing for ALE, choose Extensions ® Inbound ® Define settings for inbound modules.
If you post the IDocs immediately the R/3 sending system determines the packet size. ALE inbound processing can identify if the posting function module recognizes packet processing and if so, passes the IDoc packet to it. If not, the IDoc packet is split into individual IDocs.
If IDoc posting is running in the background, you can specify the size of the IDocs to be generated in the program RBDAPP01.
If you use function modules capable of mass processing IDocs, database utilization is reduced.
Grouping IDocs into packets is also practical for function modules that post inbound IDocs one at a time, because the ALE layer calls the function module several times in the same dialog process, thereby reducing the administrative load on the R/3 System.
If the background processing is carried out in program RBDAPP01, as a guide, you should use a packet size of between 20 and 100 IDocs.
Packet processing and parallelism complement each other, although in some situations they may compete with each other. If the size of the packet is too big, this may mean that not all available dialog processes are being used.