08.08.2012 Page 1 of 4

SAP Note 130253 - General tips on uploading transactiondata to BW

Note Language: English Version: 15 Validity: Valid Since 13.06.2005

Summary

SymptomUploading transaction data to BW takes too long

Other termsBusiness Warehouse, data upload, batch upload, transaction data upload,performance, runtime, data load, SPLIT_PARTITION_FAILED ORA00054

Reason and PrerequisitesLoading data from a mySAP system (for example, R/3) or from a file takes avery long time.

SolutionThe following tips are a general check list to make the mass data upload tothe Business Warehouse (BW) System as efficient as possible.

Tip 1:Check the parameter settings of the database as described in composite Note567745.

Check the basis parameter settings of the system.Note 192658 Setting basis parameters for BW Systems

See the following composite notes:Note 567747 Composite note BW 3.x performance: Extraction & loadingNote 567746 Composite note BW 3.x performance: Query & Web applications

Tip 2:Import the latest BW Support Package and the latest kernel patch into yoursystem.

Tip 3:Before you upload the transaction data you should make sure that ALLrelating master data has been loaded to your system. If no master has beenloaded yet, the upload may take up to 100 percent longer because in thiscase, the system must retrieve master data IDs for the characteristicattributes and it must add new records to the master data tables.Tip 4:If possible, always use TRFC (PSA) as the transfer method instead ofIDocs. If you (have to) use IDocs, keep the number of data IDocs as lowas possible. We recommend an IDoc size of between 10000 (Informix) and50000 (Oracle, MS SQL Server).To upload from a file, set this value in Transaction RSCUSTV6.To upload from an R/3 system, set this value in R/3 Customizing (SBIW ->General settings -> Control parameters for data transfer).Tip 5:If possible, load the data from a file on the application server and notfrom the client workstation as this reduces the network load. This alsoallows you to load in batch.

Tip 6:If possible, use a fixed record length when you load data from a file(ASCII file). For a CSV file, the system only carries out the converison toa fixed record length during the loading process.

08.08.2012 Page 2 of 4

SAP Note 130253 - General tips on uploading transactiondata to BW

Tip 7:When you load large data quantities from a file, we recommend that yousplit the file into several parts. We recommend using as many files of thesame size as there are CPUs. You can then load these files simultaneouslyto the BW system in several requests. To do this, you require a fast RAID.

Tip 8:When you load large quantities of data in InfoCubes, you should deletethe secodary indexes before the loading process and then recreate themafterwards if the following applies: The number of the records that areloaded is big in comparison to the number of records that already exist inthe (uncompressed) F fact table. For non-transactional InfoCubes, you mustdelete the indexes to be able to carry out parallel loading.

Tip 9:When you load large quantities of data in an InfoCube, the number rangebuffer should be increased for the dimensions that are likely to have ahigh number of data sets.To do this, proceed as follows. Use function module RSD_CUBE_GET to findthe object name of the dimension that is likely to have a high number ofdata sets.Function module settings:I_INFOCUBE = 'Infocube name'I_OBJVERS = 'A'I_BYPASS_BUFFER = 'X'The numbers for the dimensions are then contained in table 'E_T_DIME',column 'NUMBRANR'. If you enter 'BID' before this number, you get therelevant number range (for example BID0000053).You can use Transaction SNRO (-> ABAP/4 Workbench -> Development --> Othertools --> Number ranges) to display all number ranges for the dimensionsused in BW if you enter BID*. You can use the object name that wasdetermined beforehand to find the required number range.By double-clicking this line, you get to the number range maintenance.Choose Edit -> Set-up buffering -> Main memory, to define the 'No. ofnumbers in buffer'.Set this value to 500, for example. The size depends on the expected dataquantity in the initial and in future (delta) uploads.!! Never buffer the number range for the package dimension !!

Tip 10:When you load large quantities of data, you should increase the numberrange buffer for the info objects that are likely to have a high number ofdata sets. To do this, proceed as follows:Use function module RSD_IOBJ_GET to find the number range name of the infoobject that is likely to have a high number of data sets.Function module settings:I_IOBJNM = 'Info object name'I_OBJVERS = 'A'I_BYPASS_BUFFER = 'X'The number for the info object is in table 'E_S_VIOBJ', column 'NUMBRANR'.Enter 'BIM' in front of this number to get the required number range (forexample BIM0000053).Use Transaction SNRO (-> ABAP/4 Workbench -> Development --> Other tools--> Number ranges) to display all number ranges used for the info objectsin BW by entering BIM*. By entering the object name determined beforehandyou can find the desired number range.By double-clicking this line you get to the number range object

08.08.2012 Page 3 of 4

SAP Note 130253 - General tips on uploading transactiondata to BW

maintenance. Choose Edit -> Set-up buffering -> Main memory, to define the'No. of numbers in buffer'.Set this value to 500, for example. The size depends on the expected dataquantity in the initial and in future (delta) uploads.!! Never buffer the number range object for the characteristic0REQUEST!!

Header Data

Release Status: Released for CustomerReleased on: 14.06.2005 06:42:09Master Language: GermanPriority: Recommendations/additional infoCategory: PerformancePrimary Component: BW-WHM-DST Data Staging

Secondary Components:SV-BO-BI Business Information

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SAP_APPL 40 40B 40B

SAP_APPL 45 45A 45A

SAP_APPL 46C 46C 46C

SAP_BW 12 12B 12B

SAP_BW 21 21C 21C

SAP_BW 30 30B 30B

SAP_BW 310 310 310

SAP_BW 35 350 350

SAP_BASIS 46 46D 46D

SAP_BASIS 60 620 640

Related Notes

Number Short Text

828725 Parallel processing for flat file upload

688647 DB6: SAP BW and SAP NetWeaver BI Administration Tasks

567747 Composite note BW 3.x performance: Extraction & loading

567745 Composite note BW 3.x performance: DB-specific setting

549184 FAQ: What is important for extraction

546262 DB6:Administration & Performance on SAP BW, SAP SCM, SAP SEM

482494 Loading data from liveCache: Performance optimization

398155 SQL911 (Deadlock) in parallel data loads in BW DB6

365762 Loading data: Pre-analysis of (performance)problems

359761 Demand Planning: loading performance data

181945 Performance guide: BW on Informix

180605 Oracle database parameter settings for BW

08.08.2012 Page 4 of 4

SAP Note 130253 - General tips on uploading transactiondata to BW

Number Short Text

156319 Collective note performance BW 1.2B