InfoPackage/DTP Package Size

I learnt something new today about Package size while extracting from ECC into BI 7.0.

I happened to notice that one of the datasources which executes in delta mode from ECC to BI was transferring a very high number of packages. What was strange was that, although the number of packages were high, the number of records that each package contained was significantly less. This aroused my curiosity!

I did know that BW internally allocates the package size, but I did not know the criteria on which this was being done.

On reading a few posts at SDN, I figured out the logic behind this golden number called Package size.

[Credits to original posters at SDN]

Package size = MAXSIZE * 1000 / size of the transfer structure,but not more than MAXLINES.

I tried simulating and it worked out like a gem!

Read on to see the steps involved in this simulation. . .

For my testing I used the datasource 0FI_GL_14, which is the new GL Line Item datasource.

On executing an infopackage against this DataSource, I constantly received a package size of 7924!



In my source system – ECC 6.0 , SBIW T-code, I have configured the MAXSIZE in kb to be at 20,000. This is done under SBIW -> General Settings -> Maintain Control Parameters for Data Transfer

To identify the Transfer structure for a particular DS, open up the DataSource in your source system. You could use RSA6 to do this. As my test case was for the DS - 0FI_GL_14, the transfer structure is FAGLPOSBW.

To get the length of the transfer structure, use T-code SE11

Once you are in the “Display Structure” view, select Utilities->Runtime Object->Display to identify the length.

For my test case, this is 2524

When the pieces are assembled. . .

MAXSIZE=20000

Size of Transfer Structure = 2524

Package Size = 20000*1000/2524 = 7924

Hence the theory holds good!

Changing the MAXSIZE to accommodate a better package size is not advisable for the shear reason that the MAXSIZE would in turn multiple systems and datasources. Hence this needs to be done cautiously.

If you have just one BI system, you could change the value for MAXSIZE in SBIW, at the same time limit the MAXSIZE within the InfoPackages were you do need a large package size. This can be done in an IP under Scheduler->Data Source Default Data Transfer.