Performance Tuning in SAP BW/BI

If the client have BW Accelerator implemented. By Creating BWA indices we can improve Query Performance.
else (No BWA Exist)

Check whether BI Stattstics Cubes has been enabled or not
Go to T.code RSDDSTAT -->Query Name --> All, On (X) --> Save it.
So now we have enabled statistics on that query.

For Query RunTime : Stats InfoCubes
0TCTC01 - Low level details can be seen in this Stats cube.
0TCTC02 -
0TCTC03 :(Very Detailed Stats Info) Aggregates fast providing, Aggregates being in use, 
DB Ratio = Read / Transferred, the ratio only recommended is 10%.

For Loading Related:
0TCTC21 - Process statistics
0TCTC22 - InfoPackage
0TCTC23 - DTP

To Check Runtime of BW/BI Queries : Goto T.code RSRT
Provide Query Name - ->Execute & Debug. Query Step ID.
A pop-up window will appear.....Check a few : Use without Cache, Display Statistics Info.

You can check further more info in the following tables :
RSDDSTAT
RSDDSTATAGGR
RSDDSTATAGGRDEF
RSDDSTAT_OLAP
RSDDSTAT_DM

We can build indexes for DSOs, for more performance, we can build Secondary Indexes on DSO Tables.

Comments

Post a Comment

Popular posts from this blog

One stage stop to know all about BW Extractors-Part1

Image
Types of Extractors:               Application specific BW content extractors: Lo Extraction: Logistics refers to the process of getting a product or service to its desired location upon request which involves transportation, purchasing, warehousing etc. Main areas in logistics are: Sales and Distribution (SD) : application 11, 13, 08 (in LBWE T-code) Materials Management (MM) : application 03, 02 Logistics Execution (LE) : application 12 Quality Management : application 05 Plant Maintenance (PM) : application 04, 17 Customer Service (CS) : application 18 Project System (PS) : application 20 SAP Retail : application 40,43,44,45 How the data extraction happens? Extraction can be done using either Full update/delta update. Full load: Incase of logistic application, Full/Initiali
Read more

Generic Extraction via Function Module

How does the extraction API work in case you are extracting data using a self defined function module with generic delta? Sometimes, if your application or requirement makes it necessary, you have to create your own function module to extract the data from whatever sap system to bw. Therefore you normally make a copy of the standard fm 'RSAX_BIW_GET_DATA_SIMPLE'. To make this new function work for you, you have to realize the following. 1) The FM gets called by the extraction API for at least 2 times. First time is for initialization and from the 2nd time on it is for data extraction. 2) Right after the last data package (somehow you need to make sure that it is the last one) you have to raise the exception no_more_data. Example with lots of comments FUNCTION RSAX_BIW_GET_DATA_SIMPLE. *"-------------------------------------------------------------------------- *"*"Local interface: *" IMPORTING *" VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUN
Read more

COPA Extraction Step By Step in SAP BW

Image
COPA Extraction Step by Step: SAP R/3 or SAP ECC: 1. SAP R/3 or ECC goto T.Code KEB0 , In Function: Select Create  Control Parameters: Provide a New CO-PA DataSource Name:1_CO_PA%CL%ERK 2. Select your O perating C oncern, e.g.,IDES. 3. Select radio button Costing-based or Account-based as OC . 4.Select field names for partitioning.e.g. BUKRS (Company Code), Check 5.Click on Info Catalog (F7) 6. Select the Characteristics & Value fields & Keyfigures 7. Select the Package/Development Class for Workbench request 8. Edit your DataSource to select/Hide fields, Save. Datasource created successfully. 9. Extractor Checker or RSA3, extraction. SAP BW:   1. Replicate DataSource 2. Assign InfoSource 3. Transfer all the datasource elements to an InfoSource 4. Activate InfoSource 5. Create a InfoCube (Copy Str from InfoSource) 6. Create Dimension & Define and Assign it. 7. Check & Activate. 8. Create Transformation (Insert or Modify KF
Read more