cancel
Showing results for 
Search instead for 
Did you mean: 

data packet size

Former Member
0 Kudos

hi everybody,

i have doubt regarding the data packet size.

i know that in R/3 we can do the data packet sizing thru

<b>SBIW>MANAGE DATA TRANSFER PARAMETERS>--

</b>

BUT THIS IS FOR ALL THE LOADS RIGHT.

HOW CAN WE DO IT FOR INDIVIDUAL INFOPACKAGES--WHERE CAN I FIND THIS OPTION. AND

IS THIS THE ONLY OPTION R ELSE CAN WE DO IT IN A TABLE ON R/3 CAN YOU HELP ME WITH TABLE NAME AND PROCEDURE.

AND <b>I EVEN READ A ARTICLE ABOUT DATA PACKET SIZING IN BW SERVER </b>ALSO..COULD ANYONE TELL ME THE USE OF IT AND HOW TO DO IT.

<b>PLZ I DON;T HAVE ACCESS TO OSS NOTES .</b>I WILL APPRICIATE IF ANYONE CAN GIVE ME THE AVAILABLE NOTES.

THANKS AND REGARDS

NEELKAMAL

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

hi,

for individual infopackage setting, go to infopackage << scheduler << DataS. Default Data Transfer

0 Kudos

OSS note 417307

Package size specified in table ROIDOCPRMS

Former Member
0 Kudos

HI

I AM SORRY FOR TROUBLING YOU BUT I DON;T HAVE ACCESS TO OSS NOTES IT WILL BE KIND YOUR PART IF YOU CAN SEND ME THE OSS NOTES ON DATA PACKET SIZING.AS WELL AS ANY DOCUMENTATION.

AND MY SECOND QUESTION IS THAT I HAVE READ IN ONE OF THE DOCUMENTATION THAT WE CAN DO DATA PACKET SIZING IN BW AS WELL COULD YOU THROW SOME LIGHT ON IT LIKE WHEN DO WE DO IT AND HOW TO DO IT. YOUR HELP IS WELL APPRICIEATED.

MY EMAIL ID IS sreedhar_neelu@yahoo.com

THANKS AND REGARDS

NEELKAMAL

0 Kudos

hi,

in bw, transaction rscustv6.

oss note send you later, i'm getting 'page cannot be displayed'

Former Member
0 Kudos

Hi,


Symptom
Performance load is too high/not justifiable during data load.

Customizing settings via extractors IMG path (Transaction SBIW in the OLTP system; can be called directly in the OLTP or using Customizing, from the BW system) do not yield any considerable improvement or are not clear.

The settings in Table ROIDOCPRMS or in the Scheduler in the BW system are not taken into account by some extractors. How is the data package size defined for the data transfer to the BW? Are there application-specific features to determine the package size? If so, what are they?

Other terms
SBIW, general settings extractors, MAXSIZE, data volume, OLTP, service API, data package size, package size, performance

Reason and Prerequisites
The general formula is:

      Package size = MAXSIZE * 1000 / size of the transfer structure,

                    but not more than MAXLINES.

You can look up the transfer structure (extract structure) in Table ROOSOURCE in the active version of the DataSource and determine its size via SE11 (DDIC) -> Utilities -> Runtime object -> Table length.

The system default values of 10,000 or 100,000 are valid for the MAXSIZE and MAXLINES parameters (see the F1 help for the corresponding fields in ROIDOCPRMS). You can use the IMG Transaction SBIW (in the OLTP system) "Maintain General settings for extractors" to overwrite these parameters in Table ROIDOCPRMS on a system-specific basis. You also have the option of overriding these values in the scheduler (in the target BW system). However, in the Scheduler (InfoPackage) you can only reduce the MAXSIZE. The advantage of using the Scheduler to carry out maintenance is that the values are InfoSource-specific.


However, some extractors have their own flow logic which MAXSIZE does not load 1:1 from the ROIDOCPRMS.


This Note does not cover all SAP applications.


Solution
Application/DataSource               Standard settings or note

---------------------------------------------------------------

Generic extractor                     Standard (Example: Note 409641)

Delta Extraction via DeltaQueue       Standard as of PlugIn 2000.2
                                           Patch 3

LO-LIS                                 Standard

Logistic Cockpit SD                       Notes 419465 and 423118

Logistic Cockpit MM-IM:

Extraction 2LIS_03_UM                     Notes 537235 and 585750

Extraction 2LIS_03_BF                     Note 454267

           In general, the following applies to Logistic Cockpit Extraction: The package size set only serves as guideline value. 

            Depending on the application, contents and structure of the documents, and the selection in the reconstruction program, the actual size of the transfer packages may differ considerably. That is not an error. 

            For 'Queued Delta' update mode the package size of 9999 LUWs (=Logical Unit of Work, in this particular case documents or posting units per transaction are concerned) is set for LO Cockpit. However, if a transaction updated more than 10000 documents at once, the number 9999 would be invalid. This is because an update process cannot be split. 

            In the case of a 'Direct Delta' update mode there is no package size for LUW bundling. In the DeltaQueue (RSA1) every LUW is updated individually. 

           Also note the following: 

                     If you want to transfer large data sets into the BW System, it is a good idea to carry out the statistical data setup and the subsequent data transfer in several sub-steps. In doing so, the selections for the statistical data setup and in the BW InfoPackage must correspond to each other. For performance reasons, we recommend using as few selection criteria as possible. You should avoid complex selections. After loading init delta with selection 1, the setup table has to be deleted and rebuilt with selection 2. 

                     Bear the following in mind: The delta is loaded for the sum of all selections from the init deltas. Remember that the selections are made so that they do not impede the delta load, for example, if you have initialized the delta for the periods January 1st, 1999 to December 1st, 2000 and December 2nd, 2000 to August 1st, 2001 then you get a time interval from January 1st, 1999 to August 1st, 2001 in the BW. Documents from August 2nd, 2001 are no longer loaded. 

CO-OM                                     Note 413992

PS                                        Standard or according
                                           to Note 413992

CO-PC                                     Standard

FI (0FI-AR/AP-3)                          First tables with open items(BSID for customers, BSIK for vendors) are read. The package size from the MAXISE field in Table ROIDOCPRMS is used in the extraction from these tables. If the packages are grouped together according to ROIDOCPRMS and a few data records still remain, these remaining records are transferred in one additional package.

After the open items are extracted, the system extracts from the table of cleared items (BSAD for customers, BSAK for vendors). In this extraction,the package size from the MAXSIZE field is adhered to.

FI (0FI-/AR/AP/-4 , new as of BW 30A) Like FI-AR/AP-3, but with one difference: if there are remaining records after the system reads the open items using the setting in the MAXSIZE field, they are not transferred in one extra package, but added to the first package of items read from the table of cleared items. For example, if 10 data packages with 15000 data records are extracted from Table BSID in accordance with ROIDOCPRMS, and 400 data records remain, the package size of the first data package from Table BSAD is 15400.

Both new and changed records are formatted in the following sequence in the delta transfer: 1) new BSIK/BSID records; 2) new BSAK/BSAD records; 3) changed BSIK/BSID records; 4) changed BSAK/BSAD records.


Package size 0FI_GL_4:

Prior to Note 534608 and the related notes, package size could vary considerably since the MAXLINES were applied to the document headers only. Then all documents lines for the document headers were read and transferred. As a result, the packages were 2 to 999 times as large as MAXLINES depending on the number of line items per document.

Note 534608 and the related notes changed the logic so that the MAXLINES is now also applied to the document lines. For each package, MAXLINES can be exceeded by up to 998 lines since a document is always transferred completely in one package. Smaller 'remaining packages' may also occur; for example if MAXLINES = 10000, and 10000 document headers with 21000 lines are selected, 2x10000 and the remainder of 1000 were were transferred in a separate package. Selection logic in 0FI_GL_4: Selection of the new FI documents via CPUDT -> the changed documents are then selected via Table BWFI_AEDAT. When changing the selection from new to changed documents, a package may occur which consists of the 'remainder' of the CPUDT selection and the first package of the BWFI_AEDAT selection. This package can then have a maximum size of 2 x MAXLINES.

FI-FM                                  Note 416669

EC-PCA                                 For the most part, the systemadheres to the standard settings but for technical reasons, packages packages smaller than the MAXSIZE or 7200 larger than the MAXSIZE may be omitted in Table ROIDOCPRMS

FI-SL                                  as in EC-PCA

PT                                     Standard (refer to Note
                                       397209)

PY                                     Standard

PA                                     Standard

RE                                     Standard

ISR-CAM (Category Management,

         new as of PlugIn 2001.1)     Standard

CO-PA                                  During the initialization and fullupdate in the profitability analysis, a join is always read from two tables (For details see Note 392635). To avoid terminations caused by Select statements that run for too long, access occurs with intervals for the object numbers (fixed size 10,000). New intervals are read until the package size requested by BW is reached. Therefore the size of the data package is always equal to or larger than the specification, but it can vary considerably.


Master data:

Business partner                       Standard

Product                                Standard

Customer                               Standard

Vendor                                 Standard

Plant                                  Standard

Material                               Standard

Best regards,

Eugene

0 Kudos

SAP OSS note 417307

Symptom

Performance load is too high/not justifiable during data load.

Customizing settings via extractors IMG path (Transaction SBIW in the OLTP system; can be called directly in the OLTP or using Customizing, from the BW system) do not yield any considerable improvement or are not clear.

The settings in Table ROIDOCPRMS or in the Scheduler in the BW system are not taken into account by some extractors. How is the data package size defined for the data transfer to the BW? Are there application-specific features to determine the package size? If so, what are they?

Other terms

SBIW, general settings extractors, MAXSIZE, data volume, OLTP, service API, data package size, package size, performance

Reason and Prerequisites

The general formula is:

Package size = MAXSIZE * 1000 / size of the transfer structure,

but not more than MAXLINES.

You can look up the transfer structure (extract structure) in Table ROOSOURCE in the active version of the DataSource and determine its size via SE11 (DDIC) -> Utilities -> Runtime object -> Table length.

The system default values of 10,000 or 100,000 are valid for the MAXSIZE and MAXLINES parameters (see the F1 help for the corresponding fields in ROIDOCPRMS). You can use the IMG Transaction SBIW (in the OLTP system) "Maintain General settings for extractors" to overwrite these parameters in Table ROIDOCPRMS on a system-specific basis. You also have the option of overriding these values in the scheduler (in the target BW system). However, in the Scheduler (InfoPackage) you can only reduce the MAXSIZE. The advantage of using the Scheduler to carry out maintenance is that the values are InfoSource-specific.

However, some extractors have their own flow logic which MAXSIZE does not load 1:1 from the ROIDOCPRMS.

This Note does not cover all SAP applications.

Solution

Application/DataSource Standard settings or note

-


Generic extractor Standard (Example: Note 409641)

Delta Extraction via DeltaQueue Standard as of PlugIn 2000.2

Patch 3

LO-LIS Standard

Logistic Cockpit SD Notes 419465 and 423118

Logistic Cockpit MM-IM:

Extraction 2LIS_03_UM Notes 537235 and 585750

Extraction 2LIS_03_BF Note 454267

In general, the following applies to Logistic Cockpit Extraction: The package size set only serves as guideline value.

Depending on the application, contents and structure of the documents, and the selection in the reconstruction program, the actual size of the transfer packages may differ considerably. That is not an error.

For 'Queued Delta' update mode the package size of 9999 LUWs (=Logical Unit of Work, in this particular case documents or posting units per transaction are concerned) is set for LO Cockpit. However, if a transaction updated more than 10000 documents at once, the number 9999 would be invalid. This is because an update process cannot be split.

In the case of a 'Direct Delta' update mode there is no package size for LUW bundling. In the DeltaQueue (RSA1) every LUW is updated individually.

Also note the following:

If you want to transfer large data sets into the BW System, it is a good idea to carry out the statistical data setup and the subsequent data transfer in several sub-steps. In doing so, the selections for the statistical data setup and in the BW InfoPackage must correspond to each other. For performance reasons, we recommend using as few selection criteria as possible. You should avoid complex selections. After loading init delta with selection 1, the setup table has to be deleted and rebuilt with selection 2.

Bear the following in mind: The delta is loaded for the sum of all selections from the init deltas. Remember that the selections are made so that they do not impede the delta load, for example, if you have initialized the delta for the periods January 1st, 1999 to December 1st, 2000 and December 2nd, 2000 to August 1st, 2001 then you get a time interval from January 1st, 1999 to August 1st, 2001 in the BW. Documents from August 2nd, 2001 are no longer loaded.

CO-OM Note 413992

PS Standard or according

to Note 413992

CO-PC Standard

FI (0FI-AR/AP-3) First tables with open items(BSID for customers, BSIK for vendors) are read. The package size from the MAXISE field in Table ROIDOCPRMS is used in the extraction from these tables. If the packages are grouped together according to ROIDOCPRMS and a few data records still remain, these remaining records are transferred in one additional package.

After the open items are extracted, the system extracts from the table of cleared items (BSAD for customers, BSAK for vendors). In this extraction,the package size from the MAXSIZE field is adhered to.

FI (0FI-/AR/AP/-4 , new as of BW 30A) Like FI-AR/AP-3, but with one difference: if there are remaining records after the system reads the open items using the setting in the MAXSIZE field, they are not transferred in one extra package, but added to the first package of items read from the table of cleared items. For example, if 10 data packages with 15000 data records are extracted from Table BSID in accordance with ROIDOCPRMS, and 400 data records remain, the package size of the first data package from Table BSAD is 15400.

Both new and changed records are formatted in the following sequence in the delta transfer: 1) new BSIK/BSID records; 2) new BSAK/BSAD records; 3) changed BSIK/BSID records; 4) changed BSAK/BSAD records.

Package size 0FI_GL_4:

Prior to Note 534608 and the related notes, package size could vary considerably since the MAXLINES were applied to the document headers only. Then all documents lines for the document headers were read and transferred. As a result, the packages were 2 to 999 times as large as MAXLINES depending on the number of line items per document.

Note 534608 and the related notes changed the logic so that the MAXLINES is now also applied to the document lines. For each package, MAXLINES can be exceeded by up to 998 lines since a document is always transferred completely in one package. Smaller 'remaining packages' may also occur; for example if MAXLINES = 10000, and 10000 document headers with 21000 lines are selected, 2x10000 and the remainder of 1000 were were transferred in a separate package. Selection logic in 0FI_GL_4: Selection of the new FI documents via CPUDT -> the changed documents are then selected via Table BWFI_AEDAT. When changing the selection from new to changed documents, a package may occur which consists of the 'remainder' of the CPUDT selection and the first package of the BWFI_AEDAT selection. This package can then have a maximum size of 2 x MAXLINES.

FI-FM Note 416669

EC-PCA For the most part, the systemadheres to the standard settings but for technical reasons, packages packages smaller than the MAXSIZE or 7200 larger than the MAXSIZE may be omitted in Table ROIDOCPRMS

FI-SL as in EC-PCA

PT Standard (refer to Note

397209)

PY Standard

PA Standard

RE Standard

ISR-CAM (Category Management,

new as of PlugIn 2001.1) Standard

CO-PA During the initialization and fullupdate in the profitability analysis, a join is always read from two tables (For details see Note 392635). To avoid terminations caused by Select statements that run for too long, access occurs with intervals for the object numbers (fixed size 10,000). New intervals are read until the package size requested by BW is reached. Therefore the size of the data package is always equal to or larger than the specification, but it can vary considerably.

Master data:

Business partner Standard

Product Standard

Customer Standard

Vendor Standard

Plant Standard

Material Standard

http://help.sap.com/saphelp_nw04s/helpdata/en/51/85d6cf842825469a51b9a666442339/frameset.htm

quote from performance tuning ppt :

Extraction Tuning: Configuring DataPackage Size

Size of DataPackages: Influencing Factors

- Specific to application datasource, the contents and structure of records in

the extracted datasets.

- Package size: impacts frequency of COMMITs in DB .

- SAP OSS note 417307: Extractor Packet Size Collective Note for SAP

Applications

- Consider both the source system and the BW system (RSADMINC).

- Package size specified in table ROIDOCPRMS and/or InfoPackages

Scenario:

- Set up the parameters according to the recommendations; if upload

performance is not improved, try to find other values that fit exactly your

requirements.

Expected results:

- In a resource constrained systems, reduce DataPackage size

- In larger systems, increasing the package size to speed collection;

but take care not to impact communication process and unnecessarily hold work

processes in SAP source system.

- Greater throughput = Faster time to completion per request

Former Member
0 Kudos

HI EUGENE & A.H.P

THANKYOU VERY MUCH AND I REALLY APPRICIEATE YOUR VALUABLE HELP.

THANKS AND REGARDS

Answers (0)