SAP NetWeaver BW Administration Cockpit Technical Content BI Statistics

Transcription

1 SAP NetWeaver BW Administration Cockpit Technical Content BI Statistics Rudolf Hennecke, SAP Technology RIG Raghu Ganesh, SAP Technology RIG Feb 2011 As of SAP NetWeaver BW 7.0 Enhancement Package 1 (including outlook to SAP NetWeaver BW 7.30)

2 Agenda 1. Administration Cockpit & Technical Content 2. Query Runtime Statistics 2.1. Migration & Maintenance 2.2. Performance Analysis 2.3. Usage Analysis 2.4. Tips & Tricks 3. Data Load Statistics 4. Data Load Status 5. Administration Cockpit and Technical Content Update for BW Further Information SAP 2010 / Page 2

3 SAP NetWeaver Administration and BI SAP NetWeaver Portal BI Administration Cockpit BI Content Web Application for CCMS Universal Work List SAP NetWeaver Administrator SAP Solution Manager Technical Content for BI Statistics BI Content for CCMS Alert Management System (ALM) Central Performance History (CPH) BI Suite, BI Platform & Data Warehousing Process Chains (RSPC) BI Checks (RSRV) Computing Center Management System (CCMS) SAP NetWeaver BW SAP Web Application Server SAP 2010 / Page 3 Web AS ABAP & Java Data Alert Scope of this presentation

4 BI Administration Cockpit Motivation Easy administration for complex Enterprise Data Warehouses using the BI Administration Cockpit SAP 2010 / Page 4

5 BI Administration Cockpit Scope Support the BI administrator in Performance optimization Monitor BI system usage Status tracking in the areas of Enterprise Data Warehousing Enterprise Query, Reporting and Analysis Business Planning and Analytical Services by providing a central point of entry with cockpits Real-time monitors Runtime Statistics including context-specific Drill-down to details Processing options Exceptions (optional) using proven technology BI Queries BI Web Applications SAP NetWeaver Portal to make administration easier and faster and thus to lower the TCO Cross system monitoring SAP 2010 / Page 5

6 BI Administration Cockpit Overview Central access to most important BI monitoring information Context menu for access to more detailed information or BI Transaction Exception definition for intuitive display of critical monitoring data (optional) Monitoring of multiple BI systems in one view Flexible filtering of relevant information Graphical display SAP 2010 / Page 6

7 BI Administration Cockpit Architecture SAP NetWeaver Portal Portal Pages Data Load Statistics iviews Data Warehousing BI Web Applications Queries InfoProviders / MultiProviders Data Load Status iviews DataSources BI Platform iviews Query Runtime Statistics BI Suite Business Package BI Administration 1.0 (Patch 2) from the Portal Content Portfolio. BI Administration Cockpit can run in a central or in a local portal. Technical Content for SAP NetWeaver BW (software component BI_CONT, release 7.0.3), The Technical Content is entirely based on SAP BW 3.x functionality not requiring BI_JAVA. SAP NetWeaver 7.0 BI technology (software component SAP_BW) SAP NetWeaver BW SAP 2010 / Page 7

8 BI Administration Cockpit Main building blocks BI Administration Cockpit (Business Package) Portal Pages Single iviews point of entry iviewsand iviews integration with other (non BI related) portal content (example: Universal Work List) Technical Content (Web Application and Queries) Flexible BI Web analysis Applications of statistics data and sophisticated presentation of Queries information (graphs, charts, tables) InfoProviders / MultiProviders Technical Content (InfoProviders and DataSources) Central DataSources Basis for BI Administration Cockpit and BI system load transaction ST03 Persistent Data Storage and Remote Access to BI Statistics Data Information Load Data Load Query Runtime Statistics Status Statistics BI Statistics Detailed Runtime Statistics Data collection for various BI Objects Data in Data Warehousing, BI Enterprise BI Reporting and Planning Warehousing Platform Suite SAP 2010 / Page 8

9 Overview on Technical Content Technical Content: general objects BI Objects that are required for running the SAP NetWeaver BW system Analysis Authorizations, BI Trace Tool, Personalization, Shipped as part of BI Technology (software component SAP_BW) and installed automatically Some objects are already installed in the XPRA phase during the upgrade Most objects are installed when you call the Data Warehousing Workbench (DWB) for the first time. Important Notes Installing technical BI Content after upgrade Improved monitoring RSTCO_ADMIN Automatic installation of technical BI Content Technical Content: BI Statistics (focus of this presentation) Monitoring Performance and Status of BI Objects Main focus of this presentation Shipped as part of BI Content (software component BI_CONT) SAP 2010 / Page 9

10 New Technical Content for BI Statistics Main enhancements New Technical Content for new and enhanced BI Statistics New Query Runtime Statistics Process Chain and DTP Statistics BI Object Request and Process Status Technical Content for direct access and analysis on persistent data Per default, queries from the Technical Content filter on reading from persistent InfoProviders only Reading from Virtual Providers can be enabled on query level by customers Technical Content on detailed and aggregated level For Query Runtime Statistics New maintenance for query statistics data collection Enabling statistics and selection of detail level for statistics Data load statistics are collected automatically for IPs and process chains No maintenance necessary (as of SAP NetWeaver 7.0 BI, SPS9 and SAP Note ) For DTP set STATON = X in RSDDSTATOBJLEVEL for TLOGOTP = DTPA and this is done automatically by the installation program. SAP 2010 / Page 10

11 VirtualProviders in Technical Content Real-time Analysis of BI statistics data through VirtualProviders in Technical Content (example: Query Runtimes Statistics): 0TCT_C01 Standard InfoCube Periodical delta updates (loading) 0TCT_MC01 0TCT_DS01 0TCT_VC01 VirtualProvider Transfer next potential delta at query runtime Access to VirtualProvider Disabled in Technical Content Queries used in the BI Administration Cockpit Can be enabled in customer defined queries on Technical Content by removing restriction on characteristic 0INFOPROV Enabled in ST03 queries accessing the Technical Content Frequent loading of delta data is recommended (guideline: once a day) few remaining delta data in BI Statistics Tables fast (virtual) query access! BI Statistics Tables (database view) SAP 2010 / Page 11

12 BI Administration Cockpit Configuration steps SAP NetWeaver Portal Business Package BI Administration 1.0 Technical Content for SAP NetWeaver BW BI Statistics SAP NetWeaver BW Configuration steps (executed from IMG, Transaction SPRO) 7. Set Up Call to BI Administration Cockpit 6. Install Business Package 'BI Administration 1.0 (Patch 2) 5. Connect BI System and Portal (See note ) 4. Schedule Technical Content Process Chains (only needed if not done in step 1) 3. Check Updating of Statistics 2. Assign the BI Administrator Role 1. Activate the new technical content in SAP NetWeaver BW (automatic activation, no manual activation needed) Available with installation or upgrade to SAP NetWeaver 7.0 BI Please find additional information on the individual steps in the configuration IMG. SAP 2010 / Page 12

13 BI Administration Cockpit IMG for Configuration Configuration of the BI Administration Cockpit (Transaction SPRO) This activity starts transaction RSTCC_INST_BIAC which links the report RSTCC_ACTIVATEADMINCOCKPIT_NEW for automatic installation of the Technical Content activating all the Technical Content objects that are assigned to role SAP_BW_BI_ADMINISTRATOR, including the relevant data flows and process chains Prerequisite: Software component BI_CONT with latest Support Package It is recommended to install BI_CONT as BI_CONT is out of maintenance! SAP 2010 / Page 13

14 BI Administration Cockpit Scope of automatic installation report Activation of all Technical Content for given source system (including activation of direct access for VirtualProviders). If source system is not the MYSELF connection the RFC connection has to be established in advance. Option to create transport request for transport to production. It is not recommended to install the Technical Content directly on production systems. Instead you should transport the Technical Content from development in order to allow for proper change management. Automatic Scheduling of Init Process Chains 0TCT_C0_INIT_P01 and 0TCT_C2_INIT_P01 if flag set. Automatic daily scheduling of specified Delta Process Chains (if time is set). SAP 2010 / Page 14

15 Process Chains in Technical Content Overview Process chains - to load BI Statistics data to the Technical Content Report RSTCC_ACTIVATEADMINCOCKPIT_NEW activates the process chains Alternatively they can get scheduled manually Master Data - loads attributes & text for objects like Process Variants, Process Chain 0TCT_MD_S_FULL_P01 0TCT_MD_C_FULL_P01 loads text for objects like Process Status, BI Object type, Process Type loads attributes & text for objects like Process Variants, Process Chain Initialization loads - Need to run only once (Immediate scheduling) 0TCT_C0_INIT_P01 0TCT_C2_INIT_P01 Query Runtime Statistics Data Load Statistics Delta Loads - These process chains can be scheduled for periodic execution 0TCT_C0_DELTA_P01 0TCT_C2_DELTA_P01 Query Runtime Statistics - Delta Data Load Statistics - Delta SAP 2010 / Page 15

16 BI Administration Cockpit Best Practice Architecture central monitoring SAP NetWeaver Portal Business Package BI Administration 1.0 Technical Content Optional objects in local systems SAP NetWeaver Portal Business Package BI Administration 1.0 InfoProviders DataSources BI Statistics SAP NetWeaver BW Central Monitoring System Only if central system is monitored itself SAP NetWeaver Portal Business Package BI Administration 1.0 Technical Content InfoProviders DataSources BI Statistics SAP NetWeaver BW Local System 1 Technical Content InfoProviders DataSources BI Statistics SAP NetWeaver BW Local System n SAP 2010 / Page 16

17 BI Administration Cockpit Central Note SAP Service Marketplace note Collective note: (FAQ) BI Administration Cockpit Prerequisites for running the Technical Content and the BI Administration Cockpit General comments on installation Specific comments on the installation steps to be performed Tips on Running and Maintaining the Technical Content Important corrections SAP 2010 / Page 17

19 Query Runtime Statistics in SAP NetWeaver 7.0 Front end / OLAP Statistics and Data Manager Statistics Splitting the BW 3.x OLAP statistics into Frontend / OLAP statistics and Data Manager statistics Serial execution (Front-End/OLAP) vs. parallel execution (Data Manager, mostly) Many different events (FE/OLAP) vs. small number of events (DM) Statistic detail levels Introducing statistic detail levels on query level Customize the level of detail of statistic data collection for a certain object Event Concept Introducing the concept of the Event ID (characteristic) Flexible and extensible framework Enhanced coverage of BI functionality Enhanced: BEx Web, Planning New: BI Accelerator SAP 2010 / Page 19

20 Decentralized Statistics Data Storage (1) RSDDSTATHEADER RSDDSTATINFO RSDDSTATEVDATA RSDDSTATEVENTS RSDDSTATDM RSDDSTATAGGRDEF SAP 2010 / Page 20

21 Decentralized Statistics Data Storage (2) use the new DB_VIEWS to display statistics data: RSDDSTAT_OLAP RSDDSTAT_DM SAP 2010 / Page 21

22 BI Statistics framework new event concept Event ID At many different events in processing, runtime information gets collected Common concept used in query runtime, planning and warehouse management statistics Guarantees flexibility for further extensions Is the basis for end to end runtime monitoring of processing in SAP NetWeaver BW Depending on the event, the time is measured from start to end point or only at end point (time since last end point) Excerpt from table RSDDSTATEVENTS SAP 2010 / Page 22

23 Query Runtime Statistics - Overview (example) Front end BI Web Application containing two web items OLAP Query 1 Query 2 Data Manager InfoCube 1 InfoCube 2 DS Object 3 Aggregate BI Accelerator SAP 2010 / Page 23

24 Query Runtime Statistics - Overview (example) User Session (SESSIONUID) User Step 1 (STEPUID) Waiting time Step 2 Query 1 Query 2 Web Items, Web Application Event ID = OLAP, Cache, Master Data Front end / OLAP statistics (RSDDSTAT_OLAP) Data Manager (DMUID) DS Object 3 InfoCube 1, Aggregate 1 InfoCube 2, BI Accelerator Index = total runtime of the navigation step in your BI web application, your workbook or your front end Data Manager statistics (RSDDSTAT_DM) SAP 2010 / Page 24 Event 1: 2,324 sec

25 Administration Cockpit: Query Runtime Statistics SAP 2010 / Page 25

26 Administration Cockpit: Query Runtime Statistics This Workset provides an overview of the statistics of the query runtime. The Workset includes three pages with the following information: 1. BI Application Statistics with the iviews: Short-Term Trends in Total Runtimes of BI Applications Long-Term Trends in Total Runtimes of BI Applications Runtimes of BI Applications Deviations in Runtimes of BI Applications BI Application Type Selection 2. BI Application Object Statistics with the iviews: Short-Term Trends in Total Runtimes of BI Application Objects Long-Term Trends in Total Runtimes of BI Application Objects Runtimes of BI Application Objects Deviations in Runtimes of BI Application Objects BI Application Object Type Selection 3. InfoProvider Statistics with the iviews: Short-Term Trends in Total Runtimes of InfoProviders Long-Term Trends in Total Runtimes of InfoProviders Runtimes of InfoProviders Deviations in Runtimes of InfoProviders InfoProvider Type Selection SAP 2010 / Page 26

27 Technical Content for Query Runtime Statistics: Queries Technical content queries for analyzing the runtime of Queries BI Web Applications each with various key figures (excerpt) Ø Frontend-time Ø OLAP-time Ø DM-time Ø Planning time being calculated as Averages, Long Term & Short Term Deviations, Rankings and displayed in different time intervals: Hours per day, Days per month, Weeks per quarter SAP 2010 / Page 27

28 Technical Content for Query Runtime Statistics: Data Flow Front-End and OLAP Statistics (Highly Aggregated) New! 0TCT_MCA1 0TCT_MC01 Front-End and OLAP Statistics (Aggregated) 0TCT_CA1 0TCT_VCA1 0TCT_C01 0TCT_VC01 0TCT_DSA1 0TCT_DS01 RSDDSTAT_OLAP Use Cases (database view) New InfoProvider for High level monitoring on day / query level (high aggregation) Additional flag for marking initial query executions (in comparison to subsequent navigations) DataSource 0TCT_DSA1 is available since SP 16 of SAP_BW / Technical Content on top is available since BI_CONT SP 8 Use Cases Average Query Runtimes Predefined runtime categories Drilldown to navigation step Monitor query activity (example: navigations / day) SAP 2010 / Page 28

29 Technical Content for Query Runtime Statistics: Data Flow contd Front-End and OLAP Statistics (Details) 0TCT_MC02 0TCT_MC03 Data Manager Statistics (Details) 0TCT_C02 0TCT_VC02 0TCT_C03 0TCT_VC03 0TCT_DS02 0TCT_DS03 RSDDSTAT_OLAP (database view) Use Cases Advanced query runtime monitoring and troubleshooting No automatic data loading (not contained in standard TCT process chains) Data Loading to be activated on custom basis RSDDSTAT_DM (database view) Use Cases MultiProvider runtimes Query performance tuning using the BI Accelerator or Aggregates SAP 2010 / Page 29

30 New Technical Content InfoProvider 0TCT_CA1 Further links Documentation 313d636/frameset.htm Important SAP Notes Time characteristics incorrect for 0TCT_DSA BI Application name missing for 3.X Workbook and Templates BIAC:BI Admin Cockpit - Usage Statistics New Technical Content for Query Usage Statistics 1e/frameset.htm Further information on custom implementation of custom counters on the next slides SAP 2010 / Page 30

31 Technical Content for Query Runtime Statistics: Details Data in Technical Content InfoCube 0TCT_CA1 (Highly Aggregated) InfoCube 0TCT_C01 (Aggregated) InfoCube 0TCT_C02 (Detailed) InfoCube 0TCT_C02 (Detailed) all details all details Table RSDDSTAT_OLAP Data in BI Statistic Tables Table RSDDSTAT_DM SAP 2010/ Page 31

32 BI Application / BI Application Object Runtimes for Application and Application Objects are displayed In this eg: a Web-template displays 2 diff: queries Statistics pertaining to each of the objects are extracted BI Application BI Application Object Front End Time OLAP Time Data Manager Time Web Template Count Query Count Web Template 1 4,07 1 Web Template 1 Query 1 0,23 0,60 1 Web Template 1 Query 2 0,81 0,70 1 Please note that OLAP & Data Manager times for the individual queries could be displayed. Front End Time for the Web-template is also displayed. SAP 2010 / Page 32

33 Query Runtime Statistics: Aggregation in Extraction BI statistics data is aggregated within DataSource 0TCT_DS01 which populates the main Technical Content InfoCube 0TCT_C01 (Aggregated Query Runtime Statistics) Data is assigned to aggregated key figures using the HANDLETP (Handle type) and the EVENTID (Event ID) of the BI statistics data SAP 2010 / Page 33

35 Maintenance of the query statistic data collection (1) For Queries, InfoProviders, Web Templates, Workbooks Switch Statistics data collection on or off Set the statistic detail level 0 = Aggregated data only 1 = No detail on data manager 2 = Detail on all levels accessible from the Data Warehousing Workbench Tools or using transaction RSDDSTAT SAP 2010 / Page 35

36 Maintenance of the query statistic data collection (2) Default settings for statistic data collection For newly created queries: InfoProvider default All new queries of this InfoProvider will inherit the setting If no InfoProvider setting exists: custom system default for all queries Extras Change Default or Change entry Default Value in list If no (custom) system default exists: (Delivered) System Default: D = X = On, Statistic Detail level: D = 1 (Only Front End/Calculation Layer Data) Statistic Data Management Please review the (delivered) system default and disable statistic data collection where performance monitoring is not necessary Example: InfoProviders with low data volume Setting Statistic Detail Level 2 for all queries will result in large amounts of data in statistic data collection tables (rule of thumb: ~ records per query navigation step) Frequent transfer to Technical Content InfoProviders recommended Frequent deletion of Statistics Data (in transaction RSDDSTAT) recommended SAP 2010 / Page 36

37 Maintenance of the query statistic data collection (3) Statistics Detail Level setting 0 - Aggregated Data: System writes only one OLAP event (event 99999) for the query. Contains the contains the cumulative times within the OLAP processing of the query. System does not record data from the aggregation layer of the analytic engine or aggregation information. 1 - Only Front End/Calculation Layer Data: System records all OLAP events, but does not separate data from the aggregation layer of the analytic engine. System writes only the general data manager event 9000 in the OLAP context as well as the aggregation information. 2 - All: The system records all data from the area for front end and calculation layer Also, records data from the area for the aggregation layer and aggregation information. 9 - No Data: The system does not record any data from the front end and calculation layer or from the aggregated event But it does record data for the BEx Web templates and workbooks, depending on the setting. For more details, please click here SAP 2010 / Page 37

38 Deletion of Query Runtime Statistics Estimated data volume in query runtime statistics Depending on the detail statistics level records may be written per navigation step to the BI Statistics Tables (for those InfoProviders and Queries where statistics data collection is turned on) Example: 500 Users / day with each 6 navigation steps in average = 500 x 6 x 30 = records / day in BI Statistics Tables 1. Manual deletion of statistics data In transaction RSDDSTAT. Dates to be deleted are selected. Using program RSDDSTAT_DATA_DELETE (for query runtime statistics only in 7.0x, in addition for data warehouse management statistics with BW 7.30) 2. Automatic deletion during data load Per default, with a delta load for query runtime statistics, data of the last 30 days is deleted out of the BI Query Runtime Statistics Tables where the corresponding Query Runtime DataSource extracts from. This time frame can be customized using the TCT_KEEP_OLAP_DM_DATA_N_DAYS parameter in the RSADMIN table. Please see following SAP Notes for more information Query runtime statistics: Corrections for extractors BIAC: Reduction in Data volume in QT Statistics Tables SAP 2010 / Page 38

39 Technical Content for Query Runtime Statistics Migration Migration mandatory 0BWTC_C02 BW Statistics - OLAP 0TCT_C01 0TCT_C02 Front-End and OLAP Statistics 0TCT_C03 Data Manager Statistics 3.x InfoCube 0BWTC_C02 will not receive any new data as source table RSDDSTAT is not used for statistics data collection anymore Please note that data in the obsolete table RSDDSTAT can get deleted through the reports RSDDK_STA_DEL_DATA and RSDDK_STA_DEL_DATA_TO_DATE No migration: Technical content 3.x still valid 0BWTC_C03 BW Statistics - OLAP, Detail Navigation With SAP NetWeaver 7.0, table RSDDSTATAGGRDEF has been enhanced. The technical content 3.x is currently not reflecting this update but can still be used. For more details and best practices on using this statistical information in BW Monitoring please refer to the slide System usage statistics - Number of usages of characteristics in queries SAP 2010 / Page 39

40 Query Runtime Statistics Key Figures in 3.x and 7.x More information on SAP 2010 / Page 40

41 Query runtime statistics extraction Improvements in SAP NetWeaver 7.00 SP19 Motivation and Scope The query runtime statistics in the BW System (view RSDDSTAT_OLAP) contains more information than needed for query runtime performance analysis in Technical Content Through improvements in the Technical Content extraction (DataSources 0TCT_DS01 and 0TCT_DSA1) only data relevant for query runtime performance analysis will get extracted Relevant data in this context includes all navigation steps recorded in the BI Statistics which are directly attached to a navigation step in the BW Analytic Engine (OLAP). Aim: only statistics data linked to real user interaction and navigation gets transferred to TCT InfoProviders. Hence, focusing on relevant data allows to decrease the data volume in Technical Content InfoProviders (performance) while at the same time easing analysis on query runtimes Availability and Information Please find more detailed information in the SAP Notes and Availability of this improvement with SAP NetWeaver BW 7.00 SPS 17 (SP19) Documentation is available here SAP 2010 / Page 41

42 Query runtime statistics extraction Improvements in SAP NetWeaver 7.00 SP19 Data transferred to Technical Content InfoProviders 2. Customizing table RSTCTEXTRACT defines which step categories and therefore navigation steps (UIDs) will get transferred to the Technical Content InfoProviders. Default is OLAP and MDX 0TCT_DSA1 0TCT_DS01 Technical Content Data Sources Customizing on step category Table RSTCTEXTRACT 1. At extraction time every navigation step (UID) from the BI Statistics tables get assigned to a step category (OLAP, MDX, APPL, ). More information in SAP Note Data in BI Statistics Tables (view RSDDSTAT_OLAP) SAP 2010 / Page 42

43 Query runtime statistics extraction Data Manager / External read interface (RSDRI) Data transferred to Technical Content InfoProviders 3. If you want to include this data in Technical Content Reporting please change the respective setting in table RSTCTEXTRACT and check SAP Note which gives further information on RSDRI use cases and how these get recorded in BI Statistics. 0TCT_DSA1 0TCT_DS01 Technical Content Data Sources Data in BI Statistics Tables (view RSDDSTAT_OLAP) Customizing on step category Table RSTCTEXTRACT 2. These BI statistic records get assigned to step category EXTN which per default gets not transferred to Technical Content InfoProviders. 1.In Query Runtime Statistics many entries appear containing RSDRI in the object name. This is the result of BW internal read operations on InfoProviders through the Data Manager Interface. These are typically not directly related to end user query execution and often carry high runtimes. SAP 2010 / Page 43 BW Query RSDRI For more information on the Data Manager Interface please refer to 33e a155106/frameset.htm

45 Analysis of BI Statistics data in SAP NetWeaver 7.0 New: ST03 based on Technical Content BI Administration Cockpit ST03 BI System Load New: Persistent data storage and direct access New and enhanced Technical Content New set of BI Statistics tables New: Ad hoc analysis of statistics data Query Monitor (RSRT) Direct analysis of RSDDSTAT* BI Integrated Planning Perf. Toolset Ad hoc Analysis in (new) BEx Web and (new) BEx Analyzer SAP 2010 / Page 45

46 Analysis of Query Runtime Statistics: ST03 Based on Technical Content for BI Statistics Accessing persistent data (0TCT_C*) and real-time data from BI Statistics through VirtualProviders (0TCT_VC*) See note : Adjusting ST03N to new BI-OLAP statistics in Release 7.0 Precondition: EXPERT mode Header information: Timeframe Source system (Default: MYSELF) Timeframe selection (User-defined is possible) Analysis views for different BI areas SAP 2010 / Page 46

47 Analysis of Query Runtime Statistics: Query Monitor In the Query Monitor (transaction RSRT) detailed query runtime statistics can be displayed: Data Manager: Runtime of all (parallel) sub queries: InfoProvider (<InfoProvider>) BI Accelerator (<InfoCube>$X) Aggregate (1xxxxx) Front-End and OLAP : detailed list of all (sequential) events BWA Access: Details of BWA times SAP 2010 / Page 47

48 Analysis of Query Runtime Statistics: Profiling In the (new) BEx Web, experts / administrators can display query runtime statistics of the current user session using the expert mode profiling. &profiling=x SAP 2010 / Page 48

49 Analysis of Query Runtime Statistics: BEx Analyzer Ad-hoc Analysis of Statistics Select Collect statistics Need to login again for the changes to take effect More details on Note: This setting is used for ad hoc analysis of runtime statistics in BEx Analyzer itself and does not interfere with settings made in transaction RSDDSTAT in order to collect runtime statistics in RSDDSTAT* tables. SAP 2010 / Page 49

50 Analysis of Query Runtime Statistics: Integrated Planning BI Integrated Planning Performance Toolset Available as of note (Report ZBPPOIP) It is planed to deliver this report within a ST-A/PI (Solution Manager Plug In) Release Note Planning functions: Statistic events for measuring runtime. Available from SAP BI 7.0 SP19 Event IDs for Planning services start from SAP 2010 / Page 50

51 Query runtime statistics - BW Accelerator Counter for read accesses In systems that are linked to an SAP NetWeaver BW Accelerator (BWA) server, statistics are generated for each InfoCube to see whether the query reads the data from the BWA or not. In addition, the reasons why the query may not read from the BWA are listed. The data is written to the database table RSDDSTATBIAUSE. This statistics data cannot and should not be a detailed runtime analysis of a query or a BI system. The query runtime statistics can be used for this. These new statistics enable you to investigate the BWA usage quickly and easily. Currently, there is no Technical Content available for this statistics data. Analysis is done on table RSDDSTATBIAUSE itself. For more details please refer to SAP Note Table Field INFOPROV CALDAY BIA_USED BIA_TECHINA BIA_INA DB_FALLBACK BIA_NOTPOSSIBLE NO_BIA Description Name of the InfoCube from which the data is read Calendar day. One entry is generated and counted for each InfoCube, each day. Counter, the BIA index of the InfoCube is used Counter, the BIA index of the InfoCube is active and filled, however it currently has the status "Inactive (cannot be used for queries) since certain data loading processes are running (for example, change run, delete request, and so on). Counter, the BIA index is active and filled, however it is manually set to the status "Inactive" or the user is prevented from using the BIA by the system parameters. Counter, the BIA index is active and filled, however, currently the DB fallback is active and all queries read from the database. Counter, this query cannot read from the BIA data. This may be a manual change in the query properties, the selection in the debug options in RSRT, reading from an open request in the InfoCube, reading with the characteristics RequestID, ChangeID or RecordTP in the drilldown or in the Filter. Counter, there is (currently) no BIA index for this InfoCube. SAP 2010 / Page 5110

53 New Technical Content - BI Usage Statistics The BI Usage Statistics workset provides an overview of the statistics of BI usage in terms of the Application and Application Objects The Workset includes two pages with the following information: For more information please refer to ata/en/26/9ef41d14dc424183b b e8e1e/frameset.htm SAP Note BIAC:BI Admin Cockpit - Usage Statistics 1. BI Application Object Usage Statistics No: of BI Application Object Executions per User No: of Executions per BI Application Object 2. BI Application Usage Statistics No: of BI Application Object Executions per User No: of Executions per BI Application Object SAP 2010 / Page 53

54 New Technical Content for Usage Statistics: Queries Technical content queries for analyzing details on BI Usage In terms of BI Applications and BI Application Objects In terms of the Users Objects and Object Types No: of times specific objects have been executed No: of times specific object types have been accessed Users and their usage Idea about the frequent users of the system managing roles Depending on the usage patterns SAP 2010 / Page 54

55 System usage statistics Example on different counters Time / Day User 1 User 2 Examples on counters (for selected timeframe) Number of (distinct) users 2 Number of user sessions 4 Number of BI Application executions 8 Number of (initial) query executions 12 Number of query navigation steps 28 User Session BI Application (Web Template, Workbook) Query Navigation Step SAP 2010 / Page 55

56 System usage statistics Best practice implementation of different counters Number of (distinct) users Implemented in query as key figure with exception aggregation on user or alternatively with DataStore Object using key figures with update mode overwrite. The same logic would apply to number of distinct queries (using the BI Application Object = Query) in the exception aggregation. Number of user sessions Implemented with DataStore Object (Session UID in key). Implementation in query as key figure with exception aggregation on Session UID might be critical in terms of performance. Number of BI Application executions Total number (COUNT): Implemented with queries using key figure 0TCTWTCOUN out of InfoProvider 0TCT_MC01. Total number of different BI Application executions (COUNT DISTINCT): This can be implemented in a query as key figure with exception aggregation on BI Application (to be tested on performance) or alternatively with a DataStore Object. SAP 2010/ Page 56

57 System usage statistics Best practice implementation of different counters Number of (initial) query executions (= BI Application Object) An Initialization / Navigation Flag (0TCTINITFL) is available in InfoProvider 0TCT_CA1 since BW 7.00 SP16. The first call of a given query in a user session is marked with 0TCTINITFL =. All subsequent call in the same user session (= navigation) will have 0TCTINITFL = X. Number of query navigation steps (= BI Application Object) Total number (COUNT): Implemented with key figure 0TCTQUCOUN available in InfoProvider 0TCT_MC01 and 0TCT_CA1. Total number of different query executions (COUNT DISTINCT): This can be implemented in a query as key figure with exception aggregation on BI Application Object (to be tested on performance) or alternatively with a DataStore Object. Number of usages of a characteristic in queries (1) This analysis can be undertaken based on InfoCube 0BWTC_C03 from the 3.x Technical Content (underlying table RSDDSTATAGGRDEF). Please find additional information on this scenario on the next page SAP 2010 / Page 57

58 System usage statistics Number of usages of characteristics in queries Number of usages of a characteristic in queries (2) However this InfoCube does not contain information on the Query name or the InfoProvider in case the Query is built on a MultiProvider. If this is required, please consider a customer extraction (join through STEPUID) on views / tables RSDDSTATAGGRDEF, RSDDSTAT_DM and RSDDSTAT_OLAP. Also, this Table and InfoProvider miss details on the characteristic values used. This is planned for future releases. RSDDSTATAGGRDEF and 0BWTC_C03 only receive data if query statistics detail level is 2 and if corresponding InfoProvider is not indexed through the BW Accelerator. More information on this can be found in SAP Note NetWeaver BW Accelerator: Continuous improvements. If you require RSDDSTATAGGRDEF also in case the query uses the BW Accelerator please implement SAP Note Data from RSDDSTATAGGRDEF recorded even if you use the BIA. SAP 2010 / Page 58

59 Agenda 1. Administration Cockpit & Technical Content 2. Query Runtime Statistics 2.1. Migration & Maintenance 2.2 Performance Analysis 2.2. Usage Analysis 2.4. Tips & Tricks 3. Data Load Statistics 4. Data Load Status 5. Administration Cockpit and Technical Content Update for BW Further Information SAP 2010 / Page 59

60 Query Runtimes Statistics Monitoring DBSEL and DBTRANS 0TCTNDBSEL: Selected records (from DB or BI Accelerator) 0TCTNDBTRA: Transferred records (from DB or BI Accelerator) These two key figures indicate the aggregation (factor) that took place before data was handed over to the Analytical Engine. This is important for improving the performance of your aggregates and your data modeling in general 0TCTNDBSEL / 0TCTNDBTRA should be monitored using InfoProvider 0TCT_MC03 Prerequisite: statistics detail level for query is set to 2 in statistics customizing) 0TCTNDBSEL / 0TCTNDBTRA in 0TCT_MC01 are only meaningful if query data was selected out of one InfoProvider only. In case of PartProvider queries within a MultiProvider, data will be aggregated (results not meaningful). Example: MultiProvider PartProvider Selected Transferred Technical Content TCT_MC01 0TCT_MC03 0TCT_MC03 SAP 2010 / Page TCT_MC03

61 Time Zones in BI Statistics and Technical Content Data Load Statistics Used in both Query Runtime Statistics LOCAL = System time zone, customized in transaction STZAC, can be displayed in System Status UTC = Coordinated Universal Time = Greenwich Mean Time (GMT) SAP 2010 / Page 61

62 Alerting in the Technical Content for BI Statistics SAP NetWeaver Portal BI Administration Cockpit BI Content Web Application for CCMS Universal Work List SAP NetWeaver Administrator SAP Solution Manager SAP 2010 / Page 62 Technical Content BI Suite, BI Platform & Data Warehousing SAP NetWeaver BW Process Chains (RSPC) BI Checks (RSRV) SAP Web Application Server Data BI Content Alert Alert Management System (ALM) Web AS ABAP & Java Central Performance History (CPH) In the preconfigured BI Administration Cockpit / Technical Content no alerting functionality is available, but customer specific alerting can be set up easily using Exception Broadcasting on top of the Technical Content Queries. Computing Center Management System (CCMS) Recommendation: Copy Standard Technical Content Queries to your own namespace and add alerting capabilities as described on the following slides.

63 Implementing Exception Broadcasting -1- Integration of Exception Reporting Searching queries for exceptions that have occurred Distribution of exceptions that have occurred by or with the Alert Framework Application Server Other Applications BI BEx Query with Exception Central Alert Framework BEx Broadcaster Send a Short Text via SMS or Pager Send a Long Text via or Fax Send an Alert to the UWL SAP 2010 / Page 63

64 Implementing Exception Broadcasting -2- Query Designer 1. Create Exception BEx Broadcaster 2. Create Broadcasting Section Broadcast whenever a certain exception takes place Broadcast only for specific exception level SAP 2010 / Page 64

65 Sorting / Filtering using importance customizing Assigning Importance to BI Object To achieve custom sorting and filtering in queries based on technical content Eg: Show most Important InfoProviders at the top of the list Steps to follow Maintain importance in transaction RSTCIMP Transfer importance customizing to InfoObject 0TCTBWOBJCT (attribute 0TCTIMPRTNC) using DataSource 0TCTBWOBJCT_ATTR. Display attribute 0TCTIMPRTNC can now be used queries for sorting or filtering. SAP 2010 / Page 65

66 Query Runtimes Statistics: Value helps Through the new EVENTID concept much more detail and additional information is available in BI Statistics and Technical Content. Example: Runtime for value helps in query definition and query execution RSDDSTAT_OLAP HANDLETP F4 EVENTID 6001 INFOPROV 0SD_C03 OBJNAME 0CALMONTH OBJPROP M EVTIME 0,02574 All EVENTIDs = * describe the HANDELTP F4 in detail. In this case, 6001 means Value Help: Read Data from DB Within the object properties, the origin of the data can be analyzed (Q = Posted values for query navigation, D = Values in InfoProvider, M = Values in Master Data) In Technical Content, this information can be analyzed through MultiProvider 0TCT_MC02 (0TCT_MC01 containing the information as part of the Not Assigned time. SAP 2010 / Page 66

67 Query runtimes statistics: SEM-BCS (Consolidation) Through the new query runtime statistics data storage, improved monitoring for VirtualProvider based query access in SEM-BCS (Consolidation) is possible. Data in BI Statistic Tables 0BCS_VC11 VirtualProvider reads from Excerpt from Table RSDDSTAT_OLAP Details on Data Manager Example 0BCS_C11 InfoCube for direct update Table RSDDSTAT_DM 3,8 sec of which 1,4 sec are due to reading from 0BCS_C records from DB, 564 transferred to 0BCS_VC11, 82 transferred to OLAP SAP 2010 / Page 67

69 Administration Cockpit: Data Load Statistics SAP 2010 / Page 69

70 Administration Cockpit: Data Load Statistics This Workset provides an overview of the length of the load process and process chains, as well as the length and number of data records from InfoPackages and data transfer processes. The Workset includes four pages with the following information: 1. Process Chain Statistics with the iviews: Short-Term Trends in Total Runtimes of Process Chains Long-Term Trends in Total Runtimes of Process Chains Total Runtimes of Process Chains Deviations in Total Runtimes of Process Chains 2. Process Statistics with the iviews: Short-Term Trends in Total Runtimes of Processes Long-Term Trends in Total Runtimes of Processes Total Runtimes of Processes Deviations in Total Runtimes of Processes 3. InfoPackage Statistics with the iviews: Short-Term Trends in Total Runtimes of InfoPackages Long-Term Trends in Total Runtimes of InfoPackages Total Runtimes of InfoPackages Deviations in Total Runtimes of InfoPackages 4. DTP Statistics with the iviews: Short-Term Trends in Total Runtimes of DTPs Long-Term Trends in Total Runtimes of DTPs Total Runtimes of DTPs Deviations in Total Runtimes of DTPs SAP 2010 / Page 70

71 New Technical Content for Data Load Statistics: Queries Technical content queries for analyzing performance details of process chains Ø Total runtime Run-times data load, data update, activation, compression, aggregation, attribute change performance details of Data Transfer Processes Ø Total runtime, Ø Number of records, Ø Amount of data Run-times of each step type performance details of InfoPackages Ø Total runtime, Ø Number of records, Ø Amount of data Run-times of each action type SAP 2010 / Page 71

72 Data Load Statistics in SAP NetWeaver 7.0 Statistics data for SAP BW 3.x data flow technology Detailed Statistics data for new data flow Statistics data on process chains InfoProvider Update Rules InfoSource 3.x DTP InfoProvider Transformation InfoSource All other warehouse management processes Transfer Rules DTP statistics Transformation DTP DataSource 3.x NEW DataSource Drill down NEW SAP 2010 / Page 72 InfoPackage Source system InfoPackage Statistics InfoPackage Source system InfoPackage Statistics InfoPackage Process Chain Statistics

73 New Technical Content for Data Load Statistics: Data Flow 0TCT_MC21 0TCT_MC22 0TCT_MC23 0TCT_C21 0TCT_VC21 0TCT_C22 0TCT_VC22 0TCT_C23 0TCT_VC23 0TCT_DS21 0TCT_DS22 0TCT_DS23 RSPCPROCESSLOG RSPCLOGCHAIN RSDDSTATDTP RSBKREQUEST RSDDSTATWHM Process (Chain) Statistics DTP Statistics InfoPackage Statistics SAP 2010 / Page 73

74 Technical Content for Data Load Statistics: Migration Migration recommended 0BWTC_C05 BW Statistics - WHM 0TCT_C23 InfoPackage Statistics 3.x InfoCube will still contain data, migration recommended as of new data model and new InfoObjects used No migration: Technical content 3.x still valid 0BWTC_C04 BW Statistics - Aggregates 0BWTC_C06 BW Statistics: Condensing InfoCubes 0BWTC_C05 BW Statistics: Deleting Data from InfoCubes SAP 2010 / Page 74

76 Administration Cockpit: Data Load Status Processes SAP 2010 / Page 76

77 Administration Cockpit: Data Load Status Requests SAP 2010 / Page 77

78 Administration Cockpit: Data Load Status This Workset provides an overview of the status of the loading process and process chains, and also of the requests (and data records) in the InfoProviders and InfoObjects. The Workset includes three pages with the following information: 1. Process Status with the iviews: Process Chain Status Process Status Process Type Selection 2. BI Object Request Status with iviews: InfoCube Status DataStore Object Status Master Data Status PSA Table Status 3. InfoProvider Request Status with the iviews: InfoCube Correctness Aggregate Rollup DataStore Object Correctness DataStore Object Activation SAP 2010 / Page 78

79 Technical Content for Data Load Status: Queries Technical content queries for analyzing status details of InfoCubes, DataStore objects, Master data (only flexible update) PSA tables with various key figures and characteristics Total numbers of requests, Last request, Time-stamp of last change each for the several criteria All requests Qualitatively not OK (ranking criterion, not for PSA) Technically not OK (filter criterion) Not activated (only for DataStore objects) Not compressed (only for InfoCubes) Not aggregated (only for InfoCubes) SAP 2010 / Page 79

80 Technical Content for Data Load Status: Queries Technical content queries for analyzing status details of Process Chains, Data Transfer Processes, InfoPackages, DataStore object activations, InfoCube compressions, Hierarchy and Attribute change runs and various other processes with the following status information Status (red, yellow, green) (ranking criterion) Ended with error Still running Ended successfully Not yet started SAP 2010 / Page 80

81 Technical Content for Data Load Status: Data Flow 0TCT_MC11 0TCT_MC12 0TCT_VC11 0TCT_VC12 0TCT_DS11 0TCT_DS12 RSMDATASTATE_EXT RSMDATASTATE BI Object Request Status RSPCLOGCHAIN RSPCPROCESSLOG Process Status SAP 2010 / Page 81

82 Technical Content for Data Load Status: Migration Migration recommended 0BWTC_C06 BW Data Slice 0BWTC_C07 Requests in the InfoCube 0TCT_C11 BI Object Request Status 3.x InfoCubes will still contain data, migration recommended as of new data model and direct access capabilities SAP 2010 / Page 82

83 Agenda 1. Administration Cockpit & Technical Content 2. Query Runtime Statistics 2.1. Migration & Maintenance 2.2. Performance Analysis 2.2. Usage Analysis 2.4. Tips & Tricks 3. Data Load Statistics 4. Data Load Status 5. Administration Cockpit & Technical Content - Update for BW Further Information SAP 2010 / Page 83

84 Administration and Technical Content Overview New Monitors in BW Administration Cockpit Database usage in SAP NetWeaver BW e.g. in MB by InfoProviders). Enhanced Usability through Xcelsius Integration of monitors Further Enhancements of the technical content OLAP cache and SAP NetWeaver BW Accelerator usage Queries which display the OLAP usage, Cache memory and SAP NetWeaver BW Accelerator status. RDA Monitoring Display the status of usage and free capacity of RDA daemons in the system Integration of technical content into Solution Manager, thereby offering the BW monitoring solution through a central system monitoring solution This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP 2010 / Page 84

85 New TCT InfoProviders in BW 7.30 New Technical Content InfoProviders 0TCTHP24 - Real Time Daemon Statistics 0TCT_MC05 - OLAP Statistics: Cache type Memory Consumption 0TCT_MC06 - OLAP Statistics: Cache vs SHM 0TCT_C14 - Report Availability Status Information about Queries (Reports) which do not have up-to-date data available in underlying Data Targets due to various reasons Reasons can be Error when loading to PSA or to DataTarget Requests not rolled up Process Chain was scheduled to start and it did not start due to several reasons 0TCT_C15 - BW InfoProviders with inconsistent and incomplete data Data required for alerts in the dashboards Dashboard shows name/type of the object, reason for error etc 0TCT_C25 - Database Volume Statistics 0TCT_C31 - BWA Statistics: CPU Consumption 0TCT_C32 - BWA Statistics: InfoProvider Memory Consumption This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP 2010 / Page 85

86 BW Administration Cockpit in Xcelsius Overview Monitors in the Xcelsius based BW Administration Cockpit Alerts: BW InfoProviders with erroneous requests Performance Monitoring: Daily Query Performance and Weekly Process Chain Performance BW Usage Statistics: DB Usage, Query Usage, Top Users, BWA / DB / OLAP usage This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP 2010 / Page 86

87 BW Administration Cockpit in Xcelsius Prerequisites and Details Prerequisites Technical Content exists (installed via Transaction RSTCT_INST_BIA) 0TCT* Process Chains are executed (see transaction above or RSPC) User is assigned to role SAP_BW_BI_ADMINISTRATOR BI-Java is in place and BEx Web is configured Xcelsius communicates to BW through the BICS Connection Access Launch Administration Cockpit in Xcelsius via transaction RSTC_XCLS Technical Content involved Preconfigured dashboards 0XCLS_0TCT_REPORTING_DETAIL, XCLS_0TCT_PC_DETAILS, 0XCLS_0TCT_BW_MONITOR that are shipped with above role These involves several new 0TCT* queries but use standard 0TCT* InfoProviders This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP 2010 / Page 87

88 New Technical Content for Database Volume Overview and Motivation 1. A new technical content with SAP NetWeaver BW 7.30 (0TCT_C25) provides information on data volumes of various BI objects 2. The Database Volume can be analyzed according to InfoArea, Application Component, BI Objects types and BI specific table classifications. 3. Use Case 1: Support of housekeeping activities like Archiving, periodic PSA and Change Log deletion, etc. 4. Use Case 2: Service Level Agreement Monitoring of implemented reporting scenarios for cross charging of cost to business departments This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP 2010 / Page 88

89 Administration Cockpit Database Volume Statistics This Workset provides overview of the size of the BW database, as well as the rate of growth of database sizes on a periodic basis Also provides an insight into the BW size in terms of InfoAreas, Object Types and Table Types. The Workset includes 2 pages with the following information: 1. BI Data Distribution By Hierarchies BI Data Distribution By InfoArea 2. BI Data Distribution Object/Table Types BI Data Distribution By Object Types BI Data Distribution By Table Types This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP 2010 / Page 89

90 Database Volume Statistics Example Cockpit built with Technical Content This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP 2010 / Page 90

91 Database Volume Statistics Data Model Aim of the data model is to analyze DB growth and size from a BW perspective, using typical BW taxonomy and dependencies Hierarchical display of InfoArea (for InfoProviders) and Application Component (for Datasources) Database table size (possibility of analyzing the DB size using the actual DB size after DB compression) Logical DB Size(number of rows * record width) Deriving BW Object Information from the underlying database table name Table Name e.g. /BIC/FZSALES01 Table Type InfoCube F Fact table InfoProvider Name ZSALES01 BW Object Type InfoCube InfoArea ZSALES This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP 2010 / Page 91

92 Technical Content for Query Runtime Statistics Overview Front-End and OLAP Statistics (Highly Aggregated) 0TCT_MCA1 0TCT_MC01 Front-End and OLAP Statistics (Aggregated) 0TCT_CA1 0TCT_VCA1 0TCT_C01 0TCT_VC01 0TCT_DSA1 0TCT_DS01 Use Cases New InfoProvider for High level monitoring on day / query level (high aggregation) DataSource 0TCT_DSA1 is available since SP 16 of SAP_BW / Technical Content on top is available since BI_CONT SP 8 RSDDSTAT_OLAP (database view) Use Cases Average Query Runtimes Predefined runtime categories Drilldown to navigation step Monitor query activity (example: navigations / day) This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP 2010 / Page 92

93 Technical Content for Query Runtime Statistics News Additional functionality with BW 7.0 SP 16 Flag in 0TCT_CA1: Initial Execution / Navigation Flag (0TCTINITFL). The first call of a given query in a user session is marked with 0TCTINITFL =. All subsequent call in the same user session (= navigation) will have 0TCTINITFL = X. Additional functionality with BW 7.30 Flag in 0TCT_CA1: Number of cells sent to front end as key figure in 0TCT_CA1 (0TCTNOCELL) Flag in 0TCT_C01 and 0TCT_CA1 which differentiates between pure OLAP Cache access and Data Manager access (Characteristic 0TCTOLAP_DM with the potential values 01 BWA access, 02 Cache Read, 03 DB Access) This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP 2010 / Page 93

94 Agenda 1. Administration Cockpit & Technical Content 2. Query Runtime Statistics 2.1. Migration & Maintenance 2.2. Performance Analysis 2.2. Usage Analysis 2.4. Tips & Tricks 3. Data Load Statistics 4. Data Load Status 5. Administration Cockpit & Technical Content Update for BW Further Information SAP 2010 / Page 94

95 Further information Documentation BI Query Runtime Statistics f7/frameset.htm Documentation BI Administration Cockpit 66f/frameset.htm Frequently Asked Questions on the Administration Cockpit / Technical Content adab-b08a3b675ca0 Central Collective Note on the Administration Cockpit / Technical Content SAP 2010 / Page 95

96 Thank you! SAP 2008 / Page 96

97 2011 SAP AG. All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.