Sending IDoc Packets (SAP Library - ALE Introduction and Administration)

Sending IDoc Packets

Several IDocs can be grouped into a packet and sent in one transactional Remote Function Call (tRFC). This has the following benefits:

The fewer administrative tasks reduce the load on the system
tRFC uses less dialog processes in the sending R/3 System
tRFC uses less dialog processes in the receiving R/3 System

Note

You can specify the packet size of message types in Customizing for ALE.
Modeling and Implementing Business Processes
Partner Profiles and Time of Processing
Generate Partner Profiles

As a guide, packet size should be between 10 and 200 IDocs. The smaller the IDocs are, the larger the packet size can be. For message types which contain large volumes of data, for example, GLROLL or ALEAUD, the packet size should be between 1 and 10 IDocs.

If the IDocs are not going to be posted immediately in the receiving R/3 System, an IDoc packet can contain up to about 10000 data records. For example, if each IDoc contains 10 data records, a packet can contain up to 1000 IDocs.