Technical Business Content overview:
BI Technical Business content is different from the BI content. BI content delivers as any other BW objects that are easily deployable and runnable. There are many pre-delivered reports that can provide the data without much of changing it as well. But BI Technical Business content is different from common BI content because it contains technical objects. From this perspective we can say there are objects which are used to monitor BW system itself or any other SAP system as well like Administrator, helping to maintain BW authorization and BEx personalization, planning functions, and tracing reporting issues etc.
In detail there are following components of Technical Business Content:
BW Statistics BI Content: It is used to evaluate performance of SAP BW system. There are two main areas of performance evaluation which are as follows:
- OLAP processor
- Warehouse Management.
CCMS BI Content: It comprises of BW objects for Computing Center Management System (CCMS) data in order to monitor and operate SAP systems. There can be thresholds sets for alert monitor and BW monitor, also we can monitor BW relevant SAP monitoring trees for processes like process chains, consistency checks etc. Basically it has the data from T-codes RZ20, RZ21, RSRV etc.
Central Performance History (CPH) BI Content: As performance figures are not stored in the system for long period it enables storing of historical performance data of SAP systems to monitor architecture of the systems in landscape from long term point of view.
ABAP statistics BI Content: Enables reporting on statistics data from SAP’s Workload Monitor (T-code ST03).
Distributed Statistics Record (DSR) BI Content: Reporting on Distributed Statistics Records (DSR) generated by non-ABAP components (e.g. AS Java, TREX). DSR are statistics records created for monitoring the SAP system performance and its components collected by associated CCMS agent.
BEx Personalization BI Content: Objects used to fill variables with user specific values and to save user specific start views for Web applications (Personalizing Variables in Web Applications.) and in BEx reports (Personalizing Variables).
BI Users and Authorizations BI Content: Objects used to generate Analysis Authorizations. Function available in T-code RSECADMIN.
BI Features Characteristics BI Content: 19 Info Cube objects (0M000100 – 0M111111) used to test the loading process for master data attributes and texts. By setting of settings for master data characteristics several aspects of the loading process can be tested.
BI Integrated Planning BI Content: Parameters of BI-IP planning functions types stored in those BI content delivered characteristics and key figures. Also personalization of values for variable replacement works with these BI content objects.
Planning functions BI Content: SAP provides Info Objects (characteristics and key figures) that the system requires as parameters for the standard planning function types. I.e. Personalization data for variable replacement.
BI Trace Tool BI Content: BW objects needed parameters in trace tool like: Test Results Archive 0RSTT_TESTLOG Info Area for objects for describing the test results, Test Reporting 0RSTT_TESTREP Info Area for detailed description and analysis of the tests. Namespace for the objects starts with the character string 0RSTT*.
Exchange Rate Type BI Content: Objects like 0RTYPE that are supporting currency translation functionality.
BI Formula Builder BI Content: There was a Data Store Object used to store formulas created in Formula Builder.
So these are some types of components and overview for simple understanding what all technical BI content that it contains to administer it. Now will try to understand what actually BW statistics is.
What is BW Statistics? What are Statistics Providers and Their Purposes?
Terms like database (DB) and BW statistics are often referred in SAP. We always hear that it is important to maintain statistics in order to achieve good performance of SAP systems. Especially in BW area performance topic is very important. So what it is
It is a part of technical Business Content which helps to evaluate performance of SAP BW system. As I mentioned above there are two main areas of performance evaluation:
- OLAP processor
- Warehouse Management
OLAP processor: It gives information how BW reporting is performing and a way how statistics data is collected. Every navigational step within the reporting that request data from the database is saved in transparent table in BW Backend (tables RSDDSTATHEADER, RSDDSTATINFO, and RSDDSTATEVDATA). It includes characteristics, navigation attributes and hierarchies. Here event concept is used. Event is uniquely identifying each step in the process from DB table’s statistics from where the data are loaded into BW statistics Info Cubes via technical process chains.
Warehouse Management: In case of warehouse management it determines performance of loading transforming and all other staging operations even it is also known as data load statistics. In principal system is gathering the data from process chains,DTP’S and info packages.
For example : Here time of execution is stored along other data load statistics data. Table where data is written is RSDDSTATWHM. Warehouse Management is customized via transaction RSDDSTAT
Maintenance requires scheduling data loads and monitoring Delta load functionality delivered Transaction Data Master Data One of several sources of performance monitoring information.
As well as analysis scenarios based on persistently stored data (PSA), you can also access statistics data directly.
With persistent data storage, the statistics data is extracted from the tables in scheduled processes and stored in the relevant Info Providers. If you want to analyze the data in real time, you can use the Virtual Provider tool in the technical BI content to read the data in the tables directly from the query or Web application.
Taking query runtime statistics as an example, the graphic below illustrates how you can use a MultiProvider to read periodically loaded delta data (recommendation: daily) from the Info Cube and to read delta data that has not been loaded yet directly from the statistics tables using a virtual Provider.
Deleting Statistics Recordings
Query runtime statistics generate a very large amount of statistics data in the BW statistics tables Depending on the (user-defined) delta statistics level, between 20 and 80 data records are written to the BW statistics tables for each single navigation step. We therefore recommend loading the statistics data into the technical content and deleting the original data from BW statistics tables RSSDDSTAT* and UPC_STATISTIC* on a regular basis.
When using technical content, deletion of statistics recording for query runtime statistics is automated.