I. SAP BW Admin Cockpit Introduction and Architecture
BW Administration Cockpit is used to monitor the performance of BW systems in the system landscape. The BW Administration Cockpit provides a central point of entry and makes available cockpits and dashboards that provide real-time monitors and runtime statistics. It provides context-specific access to comprehensive reports and applications that help you identify and analyze issues. The BW Administration Cockpit is based on technical BI Content for runtime and status data for BW objects and activities.You can monitor and administer the performance of a BW system using either SAP NetWeaver Portal or intuitive Xcelsius Dashboards. The usability of BW Administration Cockpit monitors is enhanced by the presentation of BW administrative data in intuitive Xcelsius Dashboards.
- Track the status of BW objects, BW operations, and so on
- Optimize the performance of BW activities
Manage BW systems from one location, decreasing the total cost of ownership (TCO)
The BW Administration Cockpit allows you to navigate to the relevant BW systems, transactions and queries to analyze system performance and resolve issues without your needing to explicitly log on to any system.The BI administrator supports in
- Status tracking
- Performance optimization
- Data quality controlling
- Strategic administration
- BI statistics allow you to record runtime data for BI processes and events in the BI suite, Analytic Engine and in the Data Warehouse. The system records the performance-critical parts of the processing (statistics events). It calculates the net times by calculating the runtime of an event using the difference between the start and end times (minus the times for other events called from within the event). You can also use the statistics to record the monitoring status of BI objects from the Data Warehouse.
- Technical BI Content provides you with predefined BI objects for analyzing statistics data.
- BI Administration Cockpit provides a central point of entry to the web templates in Technical BI Content. The BI Administration Cockpit enables integration with other portal entities, such as the universal worklist.
The graphic below illustrates the architecture of BI Administration Cockpit. The interaction between BI statistics, technical BI Content and BI Administration Cockpit is based on this architecture:
II. Activation Steps
Overview: Steps to Implement BI Administration Cockpit –
0. Ensure the user id that will perform the installation of the technical content has the appropriate authorizations
1. Activate the new technical content in SAP NetWeaver BI. Use automatic installation report (transaction SPRO). See note 965386 “Activating the technical content for the BI admin cockpit”
We recommend using the automatic installation report which is available in the Implementation Guide (transaction SPRO). You must then activate the required objects. In addition, activate the relevant step in the implementation guide (IMG) for the BI administration cockpit:
Implementation Guide (transaction SPRO)
-> SAP NetWeaver
–> Business Intelligence
—> Settings for BI content
—-> Business Intelligence
—–> BI Administration Cockpit
——> Activate Technical Content in SAP NetWeaver BI
2. Assign the BI Administrator Role. BI administrators (users) in transaction SU01 to the role SAP_BW_BI_ADMINISTRATOR
Please assign BI administrators (users) in transaction SU01 to the role SAP_BW_BI_ADMINISTRATOR.
3. Check Statistics Update – Transaction RSDDSTAT
Calling transaction RSDDSTAT, you can check the updating of statistics for InfoProviders, Queries and Data Transfer Process. Please consider that the system default is ‘X’ (= statistics turned on) and detail level ‘2’ (= all details). If for certain objects no logging of performance statistics is needed please switch them off in this transaction in order to avoid unnecessary load on statistics data storage and analysis.
4. Activate and Schedule Process Chains
a. Activate the process chains using transaction RSOR technical content (0TCT*).
b. Schedule the technical content process chains (0TCT*) in transaction RSPC. Note:”INIT” process chains need to be scheduled once and “DELTA” process chains should be scheduled periodically.
5. Activate direct access for virtual provider
Please assign source system for all the virtual providers (0TCT_VC*).
Virtual Provider ->Right Click -> Activate direct access-> Under Source Syst. For Infosource3.x tab give myself system ->Save
If we want to monitor statistics in SAP BI Portal then below steps are needed
6. Connect BI and Portal
With these IMG activities, you have to assign the portal in which you wish to call the BI Administration Cockpit to the BI system.
7. Install Business Package ‘BI Administration 1.0’
Download the Business Package BI Administration 1.0 from the Portal Content Portfolio on http://sdn.sap.com or from http://service.sap.com/swdc and import it into your SAP NetWeaver 2004s Portal (minimum: Support Package Stack 5). Then assign the roles ‘System Administrator’ and ‘BI Administrator'(or any Administrator role which contain these roles as a subset) to your BI administrator users in the portal.
8. Set up call to BI Administration Cockpit
If you want to call the BI Administration Cockpit from BI transactions such as the Data Warehousing Workbench, you have to configure in the IMG the call to the BI Administration Cockpit.
9. Define Importance (optional)
Within this optional IMG activity, you can assign importance to BI objects. You can take into account these importance in technical content queries during analysis (for example for filtering or sorting).
10. Using the Technical Content without the SAP NetWeaver Portal.
In case you wish to see the statistics as seen in the portal, the technical web templates could be run in the backend. It will produce the same results.
The statistics for short term trends, long term trends, total runtimes, deviations in runtimes of each of the following can be obtained from the templates mentioned analysis
III. Issues faced during Activation
Issue 1: Missing Formula’s in Transfer Rules
1. Go to transaction code – SE38.
2. Execute the Report – RSFO_REFERENCE_CHECK for correcting the transfer and update rules that were
missing during the admin cockpit installation. (see SAP note 884385)
3. Check mark the Update Rule [UPDRCHCK], Transfer Rule [ISTSCHCK] and Repair [REPAIR] check
buttons and execute the report.
4. Execute the report with the above selections for ‘A’ and ‘M’ versions individually. After the execution of the
report for both the versions you can see the formulas which have been repaired by the report in the report
5. Go to transaction code – RSA1. Navigate to the transfer rule for which formulas were repaired by the report
.Open the transfer rules in edit mode and activate it with the activate button in the toolbar.
Issue 2- Data Source Activation Issue
Datasource 0TCTPRCSVAR_ATTR from source system could not be activated
Issue 3- Process Chain error- Missed Infopackage for some Datasource
Solutions for Issues 2,3
Please follow the manual steps described below: (Please refer to note 1078465)
- Run Transaction ‘RSDS’. Replicate the DataSources 0TCTPRCSVAR_ATTR,0TCTBWOBJCT_TEXT, 0TCTPRCSVAR_TEXT and 0TCTBWOBJCT_ATTR.Replication is carried out by entering the DataSource name and source system name in the respective fields and selecting in the menu bar DataSource->Replicate. The DataSource needs to be replicated as ‘3.x DataSource’.
Process variant LOADING 0PAK_8K20VQGEBZRQXUE2PKWS90ZO8 does not exist in version A
Go to table RSLDPIOSH enter the InfoPackage technical name and take note of the OLTPSOURCE name then go to RSDS replicate and activate
0TCTPRCSVAR_ATTR :- OLTP Source name
2. Run the SE38 report “rssm_shipdvers_cleanup”. Select the checkbox “”Check Shadow InfoPackages’.
Execute. In the next screen, if you find any of these InfoPackages:
Select these and “Repair”. More information about using this report can be found in note 844739.
3. Install the process chain 0TCT_MD_C_FULL_P01 in copy mode.
After that take the technical names of the process chains go to business content installation and reactivate these chains (with option only necessary objects) This will solve the issue The reason of this error is the following, some master data DataSources from the BI statistics business content is not installed properly.
Issue 4- DataSource 0TCTBWOBJCT_ATTR, 0TCTBWOBJCT_TEXT InfoPackage load is in yellow status for long time in 0TCT_MD_C_FULL_P01
Go to RSA6 in BW and double check those Datasources are listed under the BW_TECH/TCT area… If they’re not then go to RSA5 and transfer then.
After that go to your Source Systems Tab in RSA1 and replicate datasources for the “myself” BW system since they’re local.
Issue 5- Init Process Chain Error
Steps to follow
- Replicate metadata for that DataSources
- Go to SE38 and execute the function module RS_TRANSTRU_ACTIVATE to reactivate transfer rules
- Repeat the failed steps in PC. It will succeed now.
Delete red request, delete index, repeat step
IV. Manual steps after Activation /Transport to the other system
- Activating Direct access to virtual providers
Virtual Provider ->Right Click -> Activate direct access-> Under Source Syst. For Infosource3.x tab give myself system ->Save
- Replicating metadata for some DataSources
- Activating transfer rules by using the program RSDG_TRFN_ACTIVATE
V. Authorization Issues
- To maintain BW statistics settings,we need authorization for T-Code – RSDDSTAT
- Create a new role with all admin cockpit objects or add to an existing role
VI. Recording BI Statistics
BI statistics are recorded for the following areas:
● BI query runtimes (actions on the front end and in the Analytic Engine, including BI Integrated Planning)
In Data Warehousing Workbench, you can set which objects the system will record statistics for by choosing Tools ® BI Statistics Settings.
● Runtimes of subprocesses in SAP NetWeaver BIA index maintenance In Data Warehousing Workbench, you can set which objects the system will record statistics for by choosing Tools ® BI Statistics Settings.
● Runtimes and status of data transfer and data processing in the Data Warehouse The system always records statistics on the runtimes and status of data transfer and data processing in the Data Warehouse. This is not the case for statistics for the data transfer process. These are deactivated in the default setting and can be activated in table RSDDSTATOBJLEVEL. More information: SAP Note 966964.
● Runtimes for performing planning functions Depending on the area, the system writes the statistics recordings to tables RSDDSTAT* or UPC_STATISTIC*. For statistical analyses in Data Warehouse processes, tables RSMDATASTATE, RSMDATASTATE_EXT, RSDDSTATDTP, RSBKREQUEST, RSBSOURCEPROP, RSPCLOGCHAIN, RSPCPROCESSLOG are used too.
VII. Analyzing BI Statistics and Admin Cockpit Usage Recommendations
You have a number of options for analyzing statistics data. These options are illustrated in the following graphic and described below:
Analysis Using the Tables or Views
You can analyze the tables and views directly in the data browser (transaction SE16).
Analysis of query runtime statistics is simplified using views RSDDSTAT_OLAP and RSSDDSTAT_DM.
When analyzing the runtimes and status for the load and maintenance processes in Data Warehouse, tables RSDDSTATWHM and RSDDSTATDTP are particularly relevant.
Runtimes of subprocesses in SAP NetWeaver BIA index maintenance are analyzed in table RSDDSTATTREX.
Runtimes of planning functions are analyzed in table UPC_STATISTIC*.
Analysis (Technical Content) Using the Workload Monitor (ST03)
The workload monitor contains the function BI System Load, which you can use to analyze statistics data. The analysis is based on the technical content.
ST03N (BI system load) does not work at all without the new technical content installation.
ST03N accesses the reporting statistics data from the technical BI-content.As a prerequisite for this, the technical content must be activated and the
statistics data must be downloaded regularly into the relevant InfoCubes
Analysis (Technical Content) Using BI Administration Cockpit
BI Administration Cockpit offers you a central point of entry to the web templates in the technical content. It provides you with an overview of critical situations in query runtime and the runtime and status of load and processing processes in the Data Warehouse. You can navigate to detailed information and to troubleshooting and optimization applications.
As explained under Analysis Using Technical BI Content for BI Statistics, you can also use the InfoProviders, queries and Web templates used in BI Administration Cockpit without the portal, thus combining the standard Web templates into a Web template of your own.
Direct Access to Statistics Tables Using Technical Content
As well as analysis scenarios based on persistently stored data, 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 InfoProviders. If you want to analyze the data in real time, you can use the VirtualProvider 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 InfoCube and to read delta data that has not been loaded yet directly from the statistics tables using a VirtualProvider.
For performance reasons, the statistics data should be read directly from the InfoCube if possible; otherwise, direct access to the original table views RSDDSTAT_OLAP und RSDDSTAT_DM is also supported.
VIII. New BI Statistics: Source Tables
• Front end and OLAP Statistics: RSDDSTAT_OLAP (database view)
• Data Manager Statistics: RSDDSTAT_DM (database view)
Data Load Statistics
• Process Chain Statistics: RSPCLOGCHAIN, RSPCPROCESSLOG
• DTP Statistics: RSDDSTATDTP, RSBKREQUEST
• InfoPackage Statistics: RSDDSTATWHM
Data Load Status
• BI Object Status: RSMDATASTATE_EXT
• Process Status: RSPCPROCESSLOG, RSPCLOGCHAIN
IX. Admin Cockpit Queries
A) Query Runtime Statistics:
A.1 – BI Application Statistics – 0TPLI_0TCT_MC01_Q0111-114.
A.2 – BI Application object Statistics – 0TPLI_0TCT_MC01_Q0121-124.
A.3 – Infoprovider Statistics – 0TPLI_0TCT_MC01_Q0131-134.
B) Data Load Statistics
B.1 – Process Chain Statistics 0TPLI_0TCT_MC21_Q0101-104.
B.2 – Process Statistics – 0TPLI_0TCT_MC21_Q0111-114.
B.3 – Infopackage Statistics – 0TPLI_0TCT_MC23_Q101-104.
B.4 – DTP Statistics – 0TPLI_0TCT_MC22_Q101-104.
C) Data Load Status
The process status,process chain status,Master data request status, Infocube request status, Datastore object request status can be obtained
from the following web templates.
C.1 – Process Status – 0TPLI_0TCT_MC12_Q0100,0TPLI_0TCT_MC12_Q0110.
C.2 – BI Object request Status – 0TPLI_0TCT_MC11_Q0120,0TPLI_0TCT_MC11_Q0130,0TPLI_0TCT_MC11_Q0140.
C.3 – Infoprovider request Status – 0TPLI_0TCT_MC11_Q0120, 0TPLI_0TCT_MC11_Q0130,0TPLI_0TCT_MC11_Q0140.