As explained in QueryProvider: Seemantic Grouping, the DTP only can create packages when semantic grouping is used. The following simple example show what happens when sematic grouping is used and the package size is varied.
DTP Without Semantic Grouping
In the initial step for request 2999847, the package size 1000 was set.
In the executed request it can be seen that the result set is returned in one package:
DTP With Semantic Grouping
Adding the option of semantic grouping in this DTP should have the benefit of controlling the packages.
The characteristic STPE_CUST is chosen.
To check how many packages can now be expected for the QueryProvider, the original query was executed in transaction RSRT and the characteristic STPE_CUST was drilled down. There are 49 values for the STPE_CUST dimension, so it may be expected that 49 packages are returned for the DTP.
However, this is in general not guaranteed since it depends on the data and the setting of package size. In our example the DTP package size is still 1000:
It can be seen that 49 packages of different sizes are created and processed. The reason is that the package size of 1000 is simple too small for 49 plants, so, the systems needs to create bigger packages.
In general, it highly depends on data distribution and granularity which characteristic would be the best option.
Package Size changed to 10000
If the package size is increased to 10.000 in our example, 18 packages are created:
So now we have less but bigger packages. This also means that in one package we can find more than only one plant. You can see that the number of records per packages is often close to the package size, however, there is also packages with far more records. Such effects cannot be avoided.