Demystify the Concept of Package Size for Data Extraction

  • by Anurag Barua, Independent SAP Advisor
  • June 1, 2005
Setting the optimal package size for your data loads from your SAP source system to your BW system is important for improved system performance and troubleshooting. Gain a better understanding of the consequences of improper sizing and the considerations for setting sizing parameters.
Key Concept
Data is transferred into BW not as individual records but in packages or packets. SAP uses both terms. To see how packages come across to your BW system, go to your monitor after you execute an extraction run via an InfoPackage. Alternatively, you can run transaction RSMO and open one of the successful extraction jobs. The details of this extraction run show a listing of the data packages and the number of records that came in with each package.

Package size is a vexing issue. For example, if you use a big package, a single faulty record could result in the whole package being dropped. You can choose smaller packages in the hope that you can run several work processes in parallel. This isn’t a bad idea, except that you may not have enough work processes available to handle the load.

I have come across a lot of misconceptions and confusion on this topic. I have often seen parameters related to package size set in a whimsical manner without a complete understanding of its implications. This leads to adverse effects on data extraction jobs into BW and overall performance in the source system.

I’ll explain the role of data packages in BW, the control parameters that influence the size of a data package, and how and where these parameters are set in the IMG. You’ll also see the considerations involved in setting the relevant parameters and how some of these parameters may be overridden in the target BW system. First I’ll provide a few basics about packages.

Anurag Barua

Anurag Barua is an independent SAP advisor. He has 23 years of experience in conceiving, designing, managing, and implementing complex software solutions, including more than 17 years of experience with SAP applications. He has been associated with several SAP implementations in various capacities. His core SAP competencies include FI and Controlling FI/CO, logistics, SAP BW, SAP BusinessObjects, Enterprise Performance Management, SAP Solution Manager, Governance, Risk, and Compliance (GRC), and project management. He is a frequent speaker at SAPinsider conferences and contributes to several publications. He holds a BS in computer science and an MBA in finance. He is a PMI-certified PMP, a Certified Scrum Master (CSM), and is ITIL V3F certified.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.