Understanding OLAP Processor and RSRT Applies to: SAP R/3, SAP ECC 6.0 and SAP BI NetWeaver 2004s. For more information, visit the EDW homepage. Summary This article gives the idea about Architecture of OLAP Processor (OLAP Engine) and different features available in RSRT to analysis queries in different scenarios. Author: Vipin A Company: Cognizant Created on: 4 August 2011 Author Bio Vipin is currently working with Cognizant as BW Senior Consultant. He has more than 4 years of experience in BW and 2 years of experience in ABAP 2011 SAP AG 1
Table of Contents Introduction... 3 How it is Beneficial to BW Consultant?... 3 OLAP Processor Architecture... 3 RSRT Details... 4 Features of RSRT... 4 Execute + Debug... 5 Technical Information about Query... 6 Query Definition Designer... 7 Query Definition Processor... 9 Properties:... 10 SQL of Query:... 11 Aggregates:... 12 Default Breakpoints:... 12 How to Learn OLAP:... 13 Important Function Modules:... 14 Related Content... 15 Disclaimer and Liability Notice... 16 2011 SAP AG 2
Introduction This article gives the idea about Architecture of OLAP Processor (OLAP Engine) and different features available in RSRT to analysis queries in different scenarios. How it is Beneficial to BW Consultant? A) OLAP Processor When we are executing our Queries, we need to understand the following: How data get processed by OLAP Engine and display result as per our requirement on Frontend tools. What all are the different Stages through which data get passes from InfoProvider to Frontend. B) RSRT RSRT have many features which helps BW Consultants to Analysis Queries in a details way. It helps to find root cause of many issues like Performance, Aggregates, RRI, Wrong Values, BIA and many others. OLAP Processor Architecture Above Diagram shows the flow of OLAP Processor. OLAP Processor starts with the Query Execution. OLAP Processor checks Authorization, Variable values and it pass these information to DATA MANAGER. According to it, Data Manager retrieves values from Database. And values get back to Data Manager. It checks for USEREXITS, after that OLAP Processor checks for any Formula, Exception Aggregation, CKF. After modifying retrieved data as per User requirement, it will display result in BEX, Web or RSRT. 2011 SAP AG 3
RSRT Details Features of RSRT List of Options available in RSRT for Displaying Results a) BEX Analyzer: It s look and feel like BEX Analyzer only but no Navigation Block. b) HTML: It feels like Portal with a Default Template. c) List: It displays values only. 2011 SAP AG 4
Execute + Debug These are the Break Points available in Execute + Debug. From these options, we can do Debugging on: 1. Data Manager 2. Currency Conversion 3. Data Get 4. Authorization 5. Cache 6. BIA 7. SQL 8. Planning 9. Statistics / RRI 10. Variables 2011 SAP AG 5
Technical Information about Query 2011 SAP AG 6
Query Definition Designer In Technical Information screen, Press Query Definition Designer tab. Program take us to Debugger, here we can find details about Query Designing. We can see the entire Component used in particular Query. 2011 SAP AG 7
Details about L_THX_FORM: Double click on L_THX_FORM and a list appears. From there we can find following Information s: NAV = Free Characteristics Characteristics that are Navigational STR = Structures SEL = Selection Element - all restrictions on all Characteristics FIX = collection of all Filters in the boxes filters, rows, columns and free characteristics. In this same way we can find more details from following tables: l_ts_var - will display all Variables for the query l_th_dkf - will display all Keyfigures for the query. l_tsx_fst_f - will display all Formulas for the query l_tsx_fst_k - will display all Formulas for Calculated Keyfigures. N_SX_REPORT give information about CELLS. 2011 SAP AG 8
Query Definition Processor A piece of coding and the complex data structure SX_REPORT are generated for a query in a timeconsuming process. During this generation, the query definition and all of the metadata information are processed. A range of flags and control tables are created that accelerate the processing considerably during runtime. CELL: Structure elements CHAFREE: Free characteristics of the query. LRECH: SEL: SFC: Formulas after aggregation. All selections. All characteristics, navigation attributes and units. SFK: SH: SN: Collects all basic key figures. Collects all hierarchies in the query. Collects the hierarchy nodes. 2011 SAP AG 9
SUMM: Formulas after aggregation. VAR: All variables. VAR_LRECH: Numerical variables with replacement paths. VCHECK: Controls the validation of variables, that is, the dependencies among variables. VREP: Controls the replacement of variables. Properties: By PROPERTIES, we can set CACHE MODE, READ MODE for particular Query as per user requirement. 2011 SAP AG 10
SQL of Query: 2011 SAP AG 11
Aggregates: S = Search or Wanted Aggregates A = Available or Used Aggregates. Default Breakpoints: 1) OLAP Processor Start (RTO Open) (RRK_RTO_OPEN) : Here all Variables get processed. 2) Frontend / OLAP Processor (List Notify) (RRK_LIST_NOTIFY): Passing Data Request from Frontend to Data Manager. 3) OLAP Processor / Data Manager (Fill Sp) (FILL_SP_1): Data Manager sends Data Request to Database and gets data back in table C_TX_DATA. 4) Aggregate Split (Seldr Split) (RSDRC_ SELDR_SPLIT): This Function Module splits the query in SUB QUERIES. 5) Data Transfer OLAP Processor / Frontend (Data Get) (RRK_DATA_GET): Pass data from OLAP Processor to Frontend. 6) Eliminate Int. Bus. Vol. Function Module for Internal Business Volume. 2011 SAP AG 12
How to Learn OLAP: HELP TEXT This will help us to understand OLAP Processor in details way with showing Proper Function Modules for different scenarios. 2011 SAP AG 13
Important Function Modules: These are the important Function Modules for OLAP Processor. RSDRC_BASIC_DB_QUERY_DATA_GET function Module retrieve data from Database. E_T_DATA : Each single result of one query stored in E_T_DATA C_TX_DATA: Whole result of Query Stored in C_TX_DATA. 2011 SAP AG 14
Related Content SAP HELP Analyze Multi-Dimensional Data For more information, visit the EDW homepage. 2011 SAP AG 15
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2011 SAP AG 16