Overview of Statistics Events (Table RSDDSTATEVENTS)

The tables below provide an overview of the events from the following areas:

• BEx Suite: Business Explorer: Times required to format and present data in SAP NetWeaver BW end user tools
• analytic manager: times required to detect and calculate query results in SAP NetWeaver BW and to plan processes and data entry
• Data Warehousing: Times required to provide data in the Enterprise Data Warehouse of SAP NetWeaver BW

BEX Suite: Business Explorer

The events for BEx Suite: Business Explorer relate to:

• BEx Web SAP NetWeaver 7.0
• BEx Web 3.x
• BEx AnalyzerSAP NetWeaver 7.0
• BEx Analyzer 3.x
• Information Broadcasting
• Multidimensional Interfaces of the Analytic Server (MDX)

  Event ID	Long Text	Description
  10000	Remote Call of a BEx Function Module
  BEx Web SAP NetWeaver 7.0
  12500	Application Step
  12600	Web Java: Process Request	The HTTP request of a BEx Web application for Java is processed. The duration of processing depends on the complexity of the Web template, the queries, and the commands.
  12601	Web Java: Build Whole Page	The structure of the page of a BEx Web application for Java is built. The structure is calculated from the number and nesting of the items in the Web template that is used.
  12602	Web Java: Rendering of the Web Items	The items of a Web template (such as tables and charts) generate the output. The duration depends on the complexity of the query and on the size of the data displayed (for a table for example, the duration depends on the number of cells displayed).
  12603	Web Java: Return Binary Content	Binary content (such as charts, PDF) of a BEx Web application for Java is returned as an HTTP response.
  12604	Web Java: Late Rendering of the Web Items	Downstream outputs are generated (messages for example).
  12605	Web Java: Return Text-Like Content	Text-type content (such as HTML) of a BEx Web application for Java is returned as an HTTP response.
  12606	Web Java: Send Event	Not used at present
  12607	Web Java: Read Local MIME File	Not used at present
  12608	Web Java: Page: Command Processing	A command is processed as part of an HTTP request in a BEx Web application for Java. Data providers are generated for example, or an item is switched to visible.
  12609	Web Java: Page: Reading the Customizing Data	Not used at present
  12610	Web Java: Start Web Template	A Web template is started in a BEx Web application for Java.
  12611	Web Java: Start Query	A query is started in a BEx Web application for Java. In this process, the data provider of the query is flagged as the main object of the Web template.
  12612	Web Java: Start Query Views	A query view is started in a BEx Web application for Java. In this process, the data provider of the query view is flagged as the main object of the Web template.
  12613	Web Java: Start Enterprise Report	An enterprise report is started in a BEx Web application for Java. In this process, the item of the enterprise report is flagged as the main object of the Web template.
  The table below will help you to get a better understanding of the times that can be measured for the APIs that are part of the BW Consumer Services: Table 1: BW Consumer Services API Description BWCS Consumer API API that is used by BW clients that use the BWCS BWCS Provider API API that has to implement a provider in order to be used in the BWCS
  13001	BW Consumer Services: Build initial view	Set the initial status of the data provider.
  13002	BW Consumer Services: Load view	Load the view definition from the ABAP back end.
  13003	BW Consumer Services: Master Data Access	Master data access (Input Help)
  13050	ABAP BICS: Provider Initialization	Initialization of the data provider on the ABAP page.
  13004	BW Consumer Services: Load result data	Java time to load and format the result set (minus provider time)
  13040	BW Consumer Services: Load provider result data	Provider Java time to load the result set (minus time 13054 OLAP)
  13054	ABAP BICS: Read result set	ABAP time to load the result set (minus OLAP time)
  13055	ABAP BICS: Create output data	ABAP time for formatting data for transport to Java
  13051	ABAP BICS: Load status	Time for synchronization when status changes (navigation) from Java to ABAP, here: when loading the state
  13052	ABAP BICS: Set status	Time for synchronization when status changes (navigation) from Java to ABAP, here: when setting the state
  13053	ABAP BICS: Read master data	Time for master data access (such as input help or filter texts). The customer can only adjust the master data accesses, for example, by selecting the read mode or by avoiding filter dropdown boxes
  13056	ABAP BICS: Set hierarchy	Time for setting the hierarchy configured in Java in ABAP and reading the metadata
  13057	ABAP BICS: Read hierarchy master data	Time for master data access, here: for reading a master data hierarchy
  13058	ABAP BICS: Miscellaneous	Other time in the data provider in the ABAP.
  13059	ABAP BICS: New Plan Data
  13100	Web Java: Data Provider: Initialize	A data provider is initialized in a BEx Web application for Java.
  13101	Web Java: Data Provider: Command Processing	A data provider command is processed as part of an HTTP request in a BEx Web application for Java. A data provider is filtered for example.
  13102	Web Java: Data Provider: Release	A data provider is released in a BEx Web application for Java.
  13103	Web Java: Data Provider: Send Event	Not used at present
  13104	Web Java: Data Provider: Set Status	Not used at present
  13105	Web Java: Data Provider: Save Status	Not used at present
  13200	Web Java: Data Area Provider: Initialize	A data area provider is initialized in a BEx Web application for Java.
  13201	Web Java: Data Area Provider: Command Processing	A data area provider command is processed as part of an HTTP request in a BEx Web application for Java. Plan data is stored for example.
  13202	Web Java: Data Area Provider: Release	A data area provider is released in a BEx Web application for Java.
  13203	Web Java: Data Area Provider: Send Event	Not used at present
  13204	Web Java: Data Area Provider: Set Status	Not used at present
  13205	Web Java: Data Area Provider: Save Status	Not used at present
  13300	Read InfoProvider Documents from DB/RM (Including Cells with Icons)	This event measures the time taken to specify links or content of documents about InfoProvider data.
  13310	Read Master Data Documents from DB/RM	This event measures the time taken to specify links or content of documents about master data.
  13320	Read Metadata Documents from DB/RM	This event measures the time taken to specify links or content of documents about metadata.
  14100	Web Java: Item: Initialize
  14101	Web Java: Item: Command Processing
  14102	Web Java: Item: Release
  14103	Web Java: Item: Send Event
  14104	Web Java: Item: Data Provider: Set Status
  14105	Web Java: Item: Data Provider: Save Status
  14500	Web Java: Dialog: Initialize
  14501	Web Java: Dialog: Command Processing
  14502	Web Java: Dialog: Release
  14503	Web Java: Dialog: Send Event
  14504	Web Java: Dialog: Data Provider: Set Status
  14505	Web Java: Dialog: Data Provider: Save Status
  BEx Web 3.x
  19910	3.x Web Reporting: General	This event measures all times that are not entered in more detail for the ABAP Web runtime.
  19911	3.x Web Reporting: Item Rendering	This event measures the time taken to generate the item output in the ABAP Web runtime.
  19912	3.x Web Reporting: Load Template
  19919	Close Web 3.x	This event measures the time taken to close an ABAP Web application.
  19950	3.x Query View: Open	This event measures the time taken to generate a data provider in the 3.x runtime.
  19951	3.x Query View: Status Check	This event measures the time taken for the status check of the data provider in the 3.x runtime.
  19952	3.x Query View: Data Access	This event measures the time taken to read the data in the 3.x runtime. (The OLAP times are recorded separately).
  19970	3.x Alert Monitor: Data Access
  19971	3.x Batch Printing	This event measures the time taken to print in the background.
  BEx AnalyzerSAP NetWeaver 7.0
  15002	Generate Workbook	This event measures the time taken to generate the constructor of a workbook.
  15003	Read Data	This event measures the time taken to convert the data to flat format.
  15004	Render Item	This event measures the time taken to draw the data of a data provider into Excel.
  15005	Process Command	This event measures the time taken to process a general command.
  15006	Draw Symbols	This event measures the time taken for the special case grid item, which is particularly time-consuming.
  15007	Deserialize Metadata	This event measures the time taken for XML conversions for deserializing the metadata.
  15008	Deserialize Result Set	This event measures the time taken for XML conversions for deserializing the result set.
  15010	Number of Excel Cells	Counter event: Number of Excel cells to be drawn in a grid.
  15011	Number of Blocks	Counter event: Number of rectangular areas to be formatted.
  15012	Number of Symbols	Counter event: Number of shapes to be drawn in a grid
  15013	Process Dialog	This event measures the time taken to process a dialog (selector, open save, variable screen).
  15014	Serialize Result	These two events measure the time taken to transform the data and metadata from the OLAP format into the format used in Microsoft Excel.
  15015	Serialize Request
  BEx Analyzer 3.x
  19900	3.x BEx Analyzer: Server Logic	BEx Analyzer 3.x: This event measures the time for the logic at the ABAP server.
  19901	3.x BEx Analyzer: Client Time	BEx Analyzer 3.x: This event measures the time for the logic in the Microsoft Excel Add-In.
  19902	3.x BEx Analyzer: Load Workbook	BEx Analyzer 3.x: This event measures the time taken to load a workbook.
  19903	3.x Analyzer VarScrn	BEx Analyzer 3.x: This event measures the time taken to display a variable screen.
  Information Broadcasting
  14601	Broadcasting: Execute Setting	This event measures the time taken to execute an information broadcasting setting for one user and one language.
  14611	Broadcasting: Execution of Producer, Distributor	This event measures the time taken to execute an information broadcasting setting that is composed of the following substeps: Generation of a document (by a producer) Conversion (by a converter) if required Broadcasting by a distributor This event measures the runtimes of the individual parts.
  14671	Broadcasting: Determine Properties of Base Object	BEx Broadcaster examines the BW objects you want to broadcast (to find which characteristics are in the query for example, Which alert levels can occur in a template? Which variables does a BW object have? The user then receives meaningful Input Help in BEx Broadcaster. This examination can be time-consuming (partly carried out in the Java stack). This event measures the runtime for this.
  Multidimensional Interfaces of the Analytic Server (MDX)
  40000	OLAP BAPI	This event measures runtimes in the OLAP BAPIs that are not specified in more detail.
  40001	Create MDX Runtime Object	This event measures the time taken to generate a runtime object, including the call of the MDX parser if necessary.
  40002	Delete MDX Runtime Object	This event measures the time taken to release resources that are no longer needed.
  40010	MDX Execution	This event measures the general runtime for the MDX execution.
  40011	MDX Execution (Initialization)	This event measures the time taken to read the metadata for an MDX InfoCube.
  40012	MDX Execution (Axes)	This event measures the runtime for preparing the axes. The total number of data cells is in the counter.
  40013	MDX Execution (Transaction Data)	This event measures the runtime needed to read the cell data from the analytic manager (OLAP).
  40020	Read MDX Query Object	This event measures the time taken to read the query definition and start the BEx query.
  40021	MDX OLAP Accesses	This event counts accesses to read the cell data from the analytic manager (OLAP).
  40030	MDX Axis Data	This event measures the runtime taken to retrieve the axis data. Here, the texts and display attributes are first of all requested and sorted.
  40031	MDX Axis Info	This event measures the runtime taken to determine the geometry of the multidimensional result set. NON EMPTY is usually evaluated here. The total runtime is high in this case because the analytic manager (OLAP) has to be addressed.
  40032	MDX Cell Data	This event measures the runtime taken to retrieve and format the cell data.
  40033	MDX Flattening	This event measures the time taken to convert the multidimensional result into a flat table. Here, the texts and display attributes are requested and sorted.
  40034	MDX basXML	Information about the rowset
  40035	MDX basXML	Set binding for rowset
  40036	MDX basXML	Get data of rowset

analytic manager

The events for the analytic manager relate to:

• Data Manager (reading of the data)
• OLAP Services (calculation and provision of the query results)
• Planning Services (planning and data entry)

  Event ID	Long Text	Description
  0	Global Event for "Non-Assigned" Times	Collective event for all parts that are not explicitly assigned to an event (normally a small value)
  1	Wait Time of User	Time between two steps, such as entry of a variable, execution of an additional navigation step.
  1000	Front end: non-assigned times
  99999	Aggregated Events (No Detailed Info Recorded)	The setting for the statistic object (such as query, template) is set to "aggregated", which means that all times are added together for this event.
  Data Manager
  9000	Data Manager Event	This event measures the time in the data manager if the data manager is called from the OLAP. You can find more detailed data in the data manager statistics (table RSDDSTAT_DM). The times measured there do not normally cumulate to the data manager time.
  9001	External Call of the Data Manger (RSDRI)	This event measures the time in the data manager if the data manager is called using the RSDRI read interface. You can find details of this in the data manager statistics if the corresponding detail level was selected for the InfoCube.
  9002	Execution of Delta Cache Test	This event measures the time taken to execute the delta cache test.
  9010	Total Number of Transported Records (DBTRANS)	This event measures the number of transported records, aggregated from all read accesses (counter event).
  9011	Total Number of Read Records (DBSEL)	This event measures the number of read records, aggregated from all the read accesses (counter event).
  OLAP services: cache times
  2500	Generation of a Cache Entry	In each query execution, the generation of the cache object and the objects that belong to this is determined (even if the global cache is deactivated, a cache object is generated). The CREATE time is therefore always greater than "0".
  2505	Read Cache Entries	This event includes the search of a storage entry or data entry and the reading from the persistent medium if this has not yet happened (SPs that have already been read are buffered locally in the roll area)
  2510	Write Cache Entries
  2515	Deletion of Cache Entries or Whole Cache
  2520	Commitment of Cache Entries	The OLAP processor marks entries that are stored in the cache as Committed and therefore as suitable to be written into the persistent storage. Since a local cache is created even if the cache is deactivated, the COMMIT time is always greater than "0".
  2525	Counts the Read Accesses to the Cache	This event counts and measures, on a deeper level of the cache framework, the read accesses to the persistent storage. This is only done if the global cache is active.
  2530	Counts the Write Accesses to the Cache	This event counts and measures, on a deeper level of the cache framework, the write accesses to the persistent storage. This is only done if the global cache is active.
  OLAP Services: OLAP Times
  3000	OLAP: Settings	This event measures the time that is needed to process the interface settings, especially the disclosure of the display hierarchy.
  3010	OLAP: Query Generation	This event measures the time that is needed to check the query definition and, if necessary, to generate the query. Note If events 3010 and 3100 have been run in a session for a query handle, the query counter (0TCTQUCOUN) for a navigation step is set to 1.
  3100	OLAP: Read Data	This event measures the time needed to group together the data requests to the data manager or to read the OLAP cache. The number of characteristic combinations that have been read is in the counter. Note If events 3010 and 3100 have been run in a session for a query handle, the query counter (0TCTQUCOUN) for a navigation step is set to 1.
  3110	OLAP: Data Selection (Check)	This event measures the time taken to call the data manager and to sort the read data according to structure element selection or a restricted key figure.
  3120	OLAP: Pruning Based on MultiProvider Hint	In the case of a MultiProvider, it is decided here whether an InfoProvider contained in this MultiProvider has to be read. This decision can be made on the basis of the cha-const. conditions, the metadata restrictions or the MultiProvider hint. These events measure the times for performance of the corresponding algorithms and the number of the MultiProvider's InfoProviders that could be excluded from the query. For more information about pruning, see Pruning of Queries on MultiProviders.
  3121	OLAP: Pruning Based on Cha-Const. Conditions
  3122	OLAP: Pruning Based on Metadata Restrictions
  3130	User exit IF_EX_RSR_OLAP_BAPI	This event measures the time needed in the exit for virtual characteristics and key figures.
  3200	OLAP: Data Transfer at Front End	During a data transfer to the front end, exception aggregations and simple currency translations are carried out, formulas are calculated, and the correct number of decimal places for the data cells is determined. The result set is also sorted according to the interface settings. The number of cells that have been read is in the counter.
  3210	Reading Master Data	This event measures the time taken to call the Input Help on the SAPGUI Variables screen.
  3310	Quantity Conversion	This event measures the time taken to call the quantity conversion.
  3500	OLAP Initialization	This event measures the time taken to start the query, read the query definition, execute the variable exists, and replace the variables.
  3510	OLAP: EXIT Variables	OLAP: Process EXIT variables
  3900	OLAP: Read Texts	Texts are read to sort the data. This event measures the time taken to call the text read class.
  3999	OLAP Other Time	Runtimes in the analytic manager (OLAP) that are not specified in more detail.
  OLAP Services: Times for Authorizations
  4300	Authorized Values and Intervals	This event measures the time taken to determine the authorized individual values and intervals.
  4400	Authorized Hierarchy Nodes	This event measures the time taken to determine the authorized hierarchy nodes.
  4500	Authorization Check Selection	This event measures the time taken to thoroughly check the authorizations.
  4510	Authorization Check Selection Old (up to BW 3.5)	This event measures the time taken to thoroughly check the authorizations for 3.x.
  4600	Filling the Authorization Buffer	This event measures the time taken to buffer the authorization data; it is always executed.
  4610	Filling the Authorization Buffer Old (up to BW 3.5)	This event measures the time taken to buffer the authorization data for 3.x; it is always executed.
  OLAP Services: Times for Input Help
  6000	Input Help: Flat	This event measures the time taken to call the input help for selecting individual values, the transformation of the records from the database to the input help output structure (concatenate for compounding and internal-external conversion).
  6001	Input Help: Read Data from DB (or Generate)	This event measures for generic InfoObjects - the time taken to read the records from the database. for InfoObjects with a separate master data read class - the time in the respective master data read class.
  6010	Input Help for Hierarchy Nodes - Initialization	This event measures the time taken to execute the hierarchy node input help. It includes the restriction of the hierarchy by means of the selected F4 mode and the initial structure of the hierarchy until the predefined start level.
  6011	Input Help for Hierarchy Node - Read Nodes/Children	This event measures the time taken to execute the hierarchy node input help. It includes the reading of subnodes in a hierarchy.
  6013	Input Help for Hierarchy Node - Find Node
  Planning Services
  50000	Planning: Writing Delta Records	Not used at present
  50001	Planning: Enqueue	Not used at present
  50002	Planning: Characteristic derivation	Not used at present
  50003	Planning: Saving Data	Not used at present
  50010	Planning: Executing a Planning Function	This event measures the time taken to execute a planning function (including writing the data to the buffer, but without reading the reference data and saving).
  50011	Number of Records Read	This event counts the data records that are read by the planning function. The data records are in the selection criteria of the filter and are locked.
  50012	Number of Changed Records	This event counts the data records that are changed by the planning function. The system checks whether changed records are locked by data slices. A derivation is carried out when the modified values are written.
  50013	Number of Records Deleted	This event counts the data records deleted by the planning function. The system checks whether deleted records are locked by data slices. A derivation is carried out during the deletion.
  50014	Number of Read Reference Data Records	This event counts the data records that are also read as reference data. Reference data is not locked.
  50015	Number of Newly Created Records	This event counts the data records that are newly created by the planning function. The system checks if the master data of the newly created records is valid. A combination check and a derivation are also carried out.
  50016	Gross Runtime PLSQ	Counter event: Gross runtime of planning sequence
  50017	Gross Runtime PLSE	Counter event: Gross runtime of planning function
  50018	Read Gross Filter Data	Counter event: Gross runtime of reading filter data
  50019	Read Gross Ref Data	Counter event: Gross runtime of reading reference data
  50020	Execute planning sequence	This event measures the runtime of all planning functions including the reading of data. This does not include analysis of the variables.
  50030	Planning Data Query	This event measures the runtime for getting the planning data from the planning buffer.
  50098	Planning: BAdI INIT	Planning: BAdI initialization for saving plan data. This measures the time for the log_structure method (see Saving Changed Values)
  50099	Planning: BAdI SAVE	Planning: BAdl when saving plan data. This measures the time for the log_write method (see Saving Changed Values)

  Note

  More information about how to read gross runtimes of the planning functions and planning sequences with planning-specific events: SAP Note 1171082.

Data Warehousing

The events for Data Warehousing relate to load processes and administration processes as regards the provision of data by the Enterprise Data Warehouse.