Prior to PI 7.1 EHP1, to collect IDoc (package) we used to have a BPM or workarounds as mentioned here
From PI 7.1 EHP1, you will see a new feature that will help design scenarios in a better way when it comes to collecting IDocs.
The IDoc Sender adapter now is active and with a purpose. You can now define a package size in the adapter. The package size defined here will be used to create IDoc packages in PI.
The above screenshot shows you the IDoc sender adapter in PI 7.1 EHP1
So how does this feature help us?
With IDoc packaging now available as a standard feature in the adapter, this will help redefine some of the design approaches to integration scenarios. Some examples are as below;
1. Collect all Work Orders (ex. ZWordorder.ZWorkorder) and create a file out at 6PM everyday
In XI/PI versions < 7.1 EHP1,
a. You might have gone for a BPM design for collecting all IDocs
b. Use the concept of an IDoc XML file
In PI 7.1 EHP1, you can use IDoc packaging and R3/ECC would make sure they will dispatch all IDocs via a Job at 6 PM.
2. Create a file with a maximum of 1000 records only. Each record corresponds to an IDoc as the input
With the new feature, set the Package size as 1000. No BPM at all.
Thus the basic idea is an improved design and a better performance.
Configurations in R3/ECC that facilitate the Design
Use the collect IDocs Option
This report can be executed or scheduled as a background job to send the IDocs
How does the payload look like in SXMB_MONI?
As shown above you will have the payload (inbound to PI) with multiple IDocs in it when using the IDoc packaging feature.
I hope this was informative. It is upto you to design your scenarios and leverage the capability as found appropriate.