Purpose

This document is meant to reintroduce the importance of SAP BW’s Technical Content and specifically the BW Administration Cockpit. In the recent years, SAP HANA has stolen much of the spotlight from everything else that is equally important to our existing customers who are not ready to move onto the SAP HANA platform.

While everyone has been busy acquiring knowledge and getting acquitted with the latest SAP HANA capabilities and functions, little did we notice that SAP has sneaked in significant changes to the technical content that we have been so familiar with. For example, an Xcelsius dashboard has been included to provide a management style reporting and installation has become much more straightforward. This article is not meant to discuss the importance of using technical content in a BW environment but to raise the awareness of how easy it is to implement, what the new functionality can address and learnings that we have gathered while enabling this feature.

This document should be use as a guide to enable the BW Administration Cockpit in an environment where this has not been setup yet. The effort is relatively minimal with no significant impact on existing objects but please address the warning messages in the installation log. The estimated effort require to complete this installation from an end to end process should not requirement anywhere greater than 10 hours using a single resource.

Benefits

You may skip this section if you have prior experience with SAP BW’s Technical Content. This section is aim to provide a high level understanding of the importance of using and having visibility of the system’s health thorough use of the generated numerical logs within the BW application.

Aside from the obvious benefits of being of being able to contextualise error and perform analysis, enabling the BW Administration Cockpit is surprising simple. There are no additional licensing costs associated with it and this feature comes as part of the NetWeaver platform. So in essence, you have a free, powerful and insightful tool that if not leverage, will be such a waste.

The advantage of empowering your clients to monitor the health of the system will allows them a greater knowledge to take proactive measure in ensuring everything stays at its optimal level. Having tangible numbers to indicate who their active users are can be a useful communication tool to drive the adoption of BW to the wider community within an organisation. For example, an organisation would have heavily investment in an enterprise warehouse solution and would like to see it being productively used. What better way to feed these information back to the management team on the number of active reporting users, the type of reports that are frequently used and how it is being used. It can also be used as impact assessments mechanism in the event where an underlying BW object needs to be modified and the need to understand what and importantly who it will be affected can save the team a lot of Monday morning hate mail.

In my opinion, the most beneficial of all in enabling the BW Administration Cockpit is that the information is provided in an Xcelsius dashboard, it is easy to understanding and the information is not overly sensitive. Because of these reasons, I do not see a valid justification for not sharing this information with the larger community. If an organisation uses SAP portal, it can be included as part of the corporate view where it can help to create a culture where information drives decision making and an open and honest view of how the reporting system is performing is a feature everyone can learn to appreciate. Some of the newly provided content such as data consumption by InfoArea is not included into the Xcelsius dashboard but is part of the delivered content. Using this report allows the business to make informed decision on cost e.g. this report will allow the business to allocate the usage cost across different departments and the below sample data indicates that the Finance department is the largest memory consumer therefore cross departmental charges can take place with the appropriate groups. Another sample report, the BW DB Usage report can give you an insight into the trend of the data growth and this can help with hardware sizing by avoiding preventable upgrades by channelling funds to other areas of improvement.

Supporting documentations

The BI Administration Cockpit is a recommended reporting feature that has been provided by SAP through the use of Technical Contents and this document is meant to cover the topic of installation and useful features within the BI Administration Cockpit and Technical BI Content layer.

Browse through the details found in the standard documentation as it is an excellent way to familiarised yourself with the installation procedure and the instructions provided are clear and concise.

Installation procedure

We discovered that an active SAP portal is a crucial component in having a working cockpit to allow reporting through Xcelsius. Others might argue that having established a BICS connection, it is sufficient to execute any dashboard reporting from BW, however, this was not the case for this exercise.

This installation procedure is meant to act as a guide under BW version 7.4 SP09 (SAPKW74009). Some installation procedure might have changed over the course of time due to product improvement and thus necessary precaution is required to successfully implement this Administration Cockpit in a landscape which might be on a different release.

While the installation of the BW Administration cockpit is simple and straight forward, the documented installation procedure can help to clarify any doubt or questions that might arise in your effort to provide this solution to your client.

Seq	Procedure
1	At a minimum level, ensure that SAP portal is present in the landscape and it is configured together with BW.   To check, in the BW server, execute this table RSPOR_T_PORTAL under SM30 and you should see some basic settings maintained   Alternatively, contact the system administrator to have this setup.
2	Ensure you have the BI Administrator role is added to your login (SAP_BW_BI_ADMINISTRATOR)
3	To activate the Technical Content, you have the choice of doing it via SPRO, execute the RSTCT_ACTIVATEADMINCOCKPIT_NEW program (SE38) or go directly to transaction RSTCT_INST_BIAC.
4	SAP has made it really easy to perform the Technical Content installation and it is no longer done under the Data Warehousing Workbench à BI Content section.   After you have made your selection criteria and ready to proceed with the installation, click on the execute button and wait for it to complete.   The options provided are self-explanatory and you would probably want to create a transport request to move these newly created objects across the landscape.   There will be 5 Process Chains added into RSPC under theUnassigned Nodes (NODESNOTCONNECTED) and you can set the schedule execution time prior to starting the installation. The default parameter is 04:00:00   1.     0TCT_C0_INIT_DELTA_P01 2.     0TCT_C2_INIT_DELTA_P01 3.     0TCT_C3_INIT_DELTA_P01 4.     0TCT_C0_FULL_P01 5.     0TCT_C25_FULL_P01
5	Upon completion of the installation, it is advisable to check the installation log for any errors or warnings. Please address these messages accordingly to the nature of the system environment.   We did not encounter any errors or warnings at this stage of the installation process in our internal environment.   If you encounter an error during the Technical Content installation, please refer to the Supporting Information section of this document.
6	The extensive list of activated objects can be found under the 0BWTCT InfoArea and importantly, ensure that these Process Chains have been added into RSPC.   1.     0TCT_C0_INIT_DELTA_P01 2.     0TCT_C2_INIT_DELTA_P01 3.     0TCT_C3_INIT_DELTA_P01 4.     0TCT_C0_FULL_P01 5.     0TCT_C25_FULL_P01   Note that there will be additional Process Chains added into the list for example, such as Process Chains to monitor BIA Statistics and if you are in an environment where BIA does not exist, this can be ignored.

When the installation is complete and you have verified that all the necessary process chains are in place, you can begin by loading the master data using Process Chain 0TCT_MD_C_FULL_P01 and subsequently followed by the 0TCT_C* Process Chains.

Xcelsius Dashboard

To use the Xcelsius dashboard, in the BW system, enter RSTC_XCLS and this will launch a web browser session extending to a preconfigured portal address and you should see a similar dashboard below provided that you have setup SAP portal and successfully activated the BW Administration Cockpit.

This dashboard will allow you an overview of three basic monitoring which is the Alerts, Performance and Usage of the system.

Monitoring Type	Usage
Alert	Alerts will alarm the BW administrator on data load failures for a given problematic InfoProvider or DataSource.   It will highlight error messages, list the impacted objects and the use of the Detail button to display the corresponding backend log.
Performance	The Performance tab will highlight high runtime objects for both Process Chains and queries by using a BEx query condition to select the TOP 20 object.   The Analyse Details button will provide the option for a graphical analysis on a granular level.
Usage	The Usage tab gives you information on the trend of the data growth for a 12 months period, the most frequently used queries and the most active users.   If BWA is present in the landscape, it will provide the percentage of data used by a query that fetches information from BWA.

Supporting Information

This section is a collection of additional information that has been useful in providing core information to strengthen the understanding, concept and troubleshooting guide towards the usage of the Technical Content. Please make full use of the attached links and SAP Service Market Place to find updated information on technical areas which might have changed during the course of multiple system improvements.

     1. Discovered errors after the Technical Content installation.

      To avoid having to reinstall the entire Technical Content, use transaction RSTCO_ADMIN to restart the failed installation. A yellow status can also be an             indicator that a newer version has been released and attention is required to handle this warning message. RSTCO_ADMIN can also be used to fix an                 installation that was executed by a user without the proper authorisation for Business Content installation. For supporting information, please refer to OSS 1069134 - Improved monitoring RSTCO_ADMIN

     2. The background (SM37) job name is BI_TCO_ACTIVATION.

       Use this to understand the installation procedure, the potential warning or error messages that might occur as a result of your installation.

     3. Assigning an importance criterion to SAP’s Technical Content.

     This feature will allow you to sort or filter BW technical objects and it needs to be maintained by assigning an importance value against the customer query          that you wish to create or maintain. E.g., by assigning an importance value to a Technical Content Process Chain or InfoCube, you are able to sort that                information to give it prioritisation amongst the other objects that is being monitored. The default importance value for all BW technical objects is set at 50 and      to change this, use transaction RSTCIMP to assign any value between 0 and 100. The underlying table that stores this information is RSTCIMPDIR.

                    With the customising complete, transfer the value to InfoObject 0TCTBWOBJCT via DataSource 0TCTBWOBJCT_ATTR and verify attribute                     0TCTIMPRTNC.

          4. Collection of Statistical Information.

          All newly created BW Query, InfoProvider, Web Template and Workbook have been defaulted to collect statistical information and this setting can be           change to disable it, turn it back on and determine the level of aggregation to report on. This setting is maintained using transaction RSDDSTAT and as a           rule of thumb, it is advisable to leave all objects turn on while maintaining a sense on the aggregation data that is required. Once you have evidence of           where performance monitoring is not required, e.g. on InfoProvider’s with low data volume, this setting can be turn off.

          If an InfoProvider has this setting disabled, e.g. InfoProvider ZKUST01, all newly created queries will inherit this property and no statistical information will           be collected for it. However, you can overwrite this setting in the Query tab to explicitly only collect information for that desired Query.

The amount of data or level of detail to be collected can also be adjusted based on the setting of 1, 2, 9 and 0. Below is an extracted text from SAP and further detail can be found here, http://help.sap.com/saphelp_nw70/helpdata/en/43/e37f8a6df402d3e10000000a1553f7/content.htm

Statistics Detail Level for the Query Object Type

For queries, you also have the option of selecting a detail level for the statistics data. You can choose from the following:

• 0 – Aggregated Data: The system writes only one OLAP event (event 99999) for the query. This contains the cumulative times within the OLAP processing of the query. The system does not record data from the aggregation layer of the analytic engine or aggregation information.
• 1 – Only Front End/Calculation Layer Data: The system records all OLAP events, but not separate data from the aggregation layer of the analytic engine.  The 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 the front end and calculation layer as well as 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 99999. However, it does record data for the BEx Web templates and workbooks, depending on the setting.

          5. Deleting Statistical Data.

          Statistical data can grow at an exponentially rate depending on factors such as the number of users in the system, the frequency of query activities and the           type of aggregation setting that has been enabled under transaction RSDDSTAT. SAP’s data retention period for table RSDDSTAT_* is 14 days but you           can overwrite the standard setting of 14 days by maintaining a numeric value in the RSADMIN table for entry TCT_KEEP_OLAP_DM_DATA_N_DAYS.          

          To do this, use the SAP_RSADMIN_MAINTAIN program to add or modify this entry. The example below holds a value of 7 days.

           Alternatively, to manually delete the statistical data use the standard Delete Statistical Data function under transaction RSDDSTAT or execute program           (SE38) RSDDSTAT_DATA_DELETE.

Conclusion

It will come as no surprise that the BW Administration Cockpit will need to be owned and managed by the IT department to ensure continuous improvement is performed productively. By having these statistical data turned into readable information, it allows an easier way to keep track of what is going on within the IT landscape regardless of the size of your enterprise.

There is no need to reiterate that the function of IT is to support the core business function but put on your green hat to find a business use case for it e.g. in an environment where SLA for BW plays an important KPI e.g. the BW server is hosted by an application provider, these information can be prove to be useful.

It is not enough to just activate the Technical Content and start running the Process Chain to collect the information that has been generated by the system but having a good understanding of the data and the standard reports is especially crucial to perform actionable task to safeguard the health of the BW server. Use the standard reports as building blocks to further enhance and drive specific monitoring and runtime statistics requirements once your team has a better understanding on the other areas to improve on. 

In terms of the new features provided by SAP, it is worthwhile to recognise that new contents might be available and be mindful that continuous improvement is certain with every release and upgrade.