Select language:

Procedure documentationBW Administration Cockpit

 

You use the BW administration cockpit to monitor the performance of BW systems in the system landscape. The BW administration cockpit provides a central point of entry and displays all the 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 the technical BI content for runtime and status data for BW objects and activities. You can monitor and administer the performance of a BW system by using either a SAP NetWeaver Portal or an intuitive Xcelsius dashboard. The usability of BW administration cockpit monitors is enhanced by the presentation of BW administrative data in the intuitive Xcelsius dashboards. The following preconfigured dashboards are available:

  • 0XCLS_0TCT_BW_MONITOR

  • 0XCLS_0TCT_PC_DETAILS

  • 0XCLS_0TCT_REPORTING_DETAIL

BW administration cockpit is used to:

  • Track the status of BW objects, BW operations, and so on.

  • Optimize the performance of BW activities.

  • Manage multiple BW systems from a central location thus 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 the need to explicitly log on to any system.

Prerequisites

You have:

  • Activated the technical BI content and set up all activities for the BW administration cockpit customization for SAP NetWeaver under   Business Warehouse  General Settings   Settings for the Administration Cockpit.  

  • Established connection to Xcelsius using the BICS Connection.

  • Logged in as a SAP_BW_BI_ADMINISTRATOR.

Procedure

Using SAP NetWeaver Portal
  1. On the initial portal screen, choose   System Administration  Monitoring  .

  2. In the Detailed Navigation panel, choose Business Intelligence.

  3. To check the execution status, start time, and start date of BI operations, choose Data Load Status.

    See: Displaying the Data Load Status

  4. To check reports that do not have the latest data available, runtimes of BW Reports and its deviation from average time needed to execute BW operations, choose Query Runtime Statistics.

    See: Displaying Query Runtime Statistics

  5. To check the runtimes and the deviations from the average time needed to execute BW objects, choose Data Load Statistics.

    See: Displaying Data Load Statistics

  6. To check the total number of executions for BW applications and the number of executions per user, choose BI Usage Statistics.

    See: Displaying BI Usage Statistics

  7. To check the utilization of your database by different BW objects, choose Database Usage Statistics.

    See: Displaying Database Usage Statistics

Using Xcelsius Dashboards

Xcelsius dashboards present useful BW administrative data thus enhancing the usability of BW administration cockpit monitors. Xcelsius uses BICS connection to communicate with BW.

In the BW system, enter RSTC_XCLS to launch BW administration cockpit in Xcelcius.

Note Note

The following options are displayed on the Xcelcius dashboards:

  • Alerts: choose this option to check the status of data in different data storages such as Persistent Storage Area (PSA) and Data target.

  • Performance: choose this option to check for daily query performance and weekly process chain performance.

  • Usage: choose this option to check the usage of BW memory and BW objects.

End of the note.
Monitoring Alerts

This option allows you to:

  • Identify different data storages containing data in the error state. The data storages can be DataSource, Data Targets and so on.

  • Understand the reason for data errors from the Error Cause and other details pane. For more information about an error, choose the Details button on the Error Cause and other details pane. For example, use the Details button to display the process chain log, if an error occurs in a process chain.

  • Identify affected BW objects based on the data error displayed in the Impacted Object List pane. For example, if data load to PSA has failed, the Impacted Object List pane displays the corresponding Data targets, InfoProviders, and BEx Queries built for the BW objects.

    Note Note

    0TCT_C15 is the InfoProvider that provides information about BW objects with inconsistent and incomplete data.

    End of the note.
  • To view the corresponding SAP back-end error log, choose Details.

    Note Note

    If the error is due to a process chain for example, the system opens the process chain log.

    End of the note.

To view the details of an error in Alerts, select Type.

Corresponding data is populated in the BW Data Storages with Data Errors pane. The table below provides a description of the different columns:

Name

Description

Type

Provides information about the type of data storage object.

Name

Provides technical name of the data storage object.

Error

Provides information about the cause of the error.

To view the corresponding SAP back-end error log, choose the Details button in the Error Cause and other details pane. For example, use the Details button to display the process chain log, if an error in process chain occurs.

The Error Cause and other details pane contains details of the error listed in the BW Data Storage with Data Errors pane. The columns available in the Error Cause and other details pane and their respective description are explained in the table below:

Name

Description

Type

Provide TLOGO of objects with errors.

Name

Provides technical name of object with errors.

Error

Provides information about the cause of the error.

For a particular error in the BW Data Storage with Data Errors pane, the Impacted Object List pane displays the BW objects impacted. The table below describes the columns available in the Impacted Object List pane:

Name

Name

Type

Provides information about the type of impacted object.

Name

Provides the technical Name of the impacted object.

Monitoring Performance

This option allows you to:

  • Identify BW queries having high runtime in the last 24 and 48 hours.

  • Identify process chains having high runtime in the last 7 and 14 days.

  • Analyze the average runtime for each query or process chain at a granular level.

Note Note

  • 0TCT_MCA1 is the multi-provider that provides an overview of the query runtime statistics.

  • 0TCT_MC21 is the multi-provider that provides an overview of the process runtime statistics.

End of the note.

Daily Query Performance — Runtimes

This pane displays average runtimes of successfully executed BW queries for the last 24 and 48 hours. Queries are sorted according to their runtime and only the queries with high runtime are displayed. The table below provides a description about the columns in the Daily Query Performance – Runtimes pane:

Name

Description

Name

Provides technical name of the BEx query.

Runtime in 24 hours

Provides average runtime (in seconds) of executed queries in the last 24 hours.

Runtime in 48 hours

Provides average runtime (in seconds) of executed queries in the last 48 hours.

For a graphical analysis of the average runtime for each query, choose the Analyze Details button under the Daily Query Performance – Runtimes pane. The runtime details of each query are displayed at a granular level. In the resulting screen, you can select a query name in Select Query.

Use the Analyze Details button, to view the performance, together with the short-term and long-term trend.

Note Note

Select the row and click on Analyze Details.

  • Under Short term Runtime trends, you can view the average runtime of query execution on an hour scale for the last 24 hours.

  • Under Long term Runtime trends, you can view the average runtime of query execution on a day scale for the last 7 days.

End of the note.

Weekly Process Chain Performance — Runtimes

This pane displays the average runtime of successfully executed process chains for the last 7 and 14 days. Process chains are sorted according to the runtime and only the process chains with high runtime are displayed. The table below provides a description about the columns in the Weekly Process Chain Performance – Runtimes pane:

Name

Description

Name

Provides technical name of the BEx query.

Runtimes in 7 days

Provides average runtime (in seconds) of executed process chain in the last 7 days.

Runtimes in 14 days

Provides average runtime (in seconds) of executed process chain in the last 14 days.

For a graphical analysis of the average runtime for each process chain, choose the Analyze Details button under the Weekly Process Chain Performance – Runtimes pane. The runtime details of each query are displayed at a granular level. In the resulting screen, you can select a process chain name in Select Process Chain.

Use Process Chain Details, to view the performance, along with the short-term and long-term trend.

Note Note

To view the performance of any other process chain, select it.

  • Under Short term Runtime trends, you can view the average runtime of process chain execution on a day scale for the last 7 days.

  • Under Long term Runtime trends, you can view the average runtime of process chain execution on a day scale for the last 30 days.

End of the note.
Monitoring BW Usage Statistics

This option allows you to:

  • Identify the usage of BW Accelerator by knowing the percentage of queries that fetched data from BWA in the last 24 hours.

  • Display the trend of Database size consumed by BW Objects for the last 12 months.

  • Identify the users executing most number of queries.

  • Identify the BW queries that are frequently used.

BW Usage Statistics

To view the usage statistics, choose BW Usage.

Memory Usage

The Memory Usage screen contains the following panes:

  • Usage of BWA/OLAP Cache/Database during Query Executions

  • BW Database Usage Statistics

Usage of BWA/OLAP Cache/Database during Query Executions (in % for last 24 hours)

This pane displays queries (in percent) that fetched data in the last 24 hours from:

  • BWA

  • Database

  • OLAP Cache

Note Note

0TCT_MCA1 is the multi-provider that provides the highly aggregated front end and OLAP statistics.

End of the note.

BW Database Usage Statistics (Last 12 months trend)

This pane displays the trend in database size (in GB) used by BW objects over the last 12 months.

Note Note

OTCT_MC25 is the multi-provider that provides the database volume statistics.

End of the note.

BW Objects Usage

The BW Objects Usage screen contains the following panes:

  • Top 10 Query Users

  • Top 10 Frequently Used Queries

Top 10 Query Users (Last 24 hours)

This pane displays the top 10 users who have executed the most number of queries in the last 24 hours. The pane also displays the percentage of query executed by these users.

Note Note

0TCT_MCA1 is the multi-provider that provides the highly aggregated front end and OLAP statistics.

End of the note.

Top 10 Frequently Used Queries (Last 24 hours)

This pane displays the top 10 most executed queries in the last 24 hours. The pane also displays the frequency percentage for these queries.

Note Note

0TCT_MCA1 is the multi-provider that provides the highly aggregated front end and OLAP statistics.

End of the note.
Monitoring BWA Usage Statistics

The BWA Usage tab is enabled only if memory is allocated for the workspaces and is available.

Note Note

BWA Usage statistics is not applicable for systems with the ‘HDB‘ database (HANA use cases).

End of the note.

This option allows you to:

  • Identify the memory used by central and local providers.

  • Identify the memory available for workspace and BWA.

  • Identify the workspaces occupying maximum percentage of memory and the maximum local provider usage.

  • Identify the workspaces with respect to their expiry date.

  • Analyze data providers of each workspace.

Note Note

  • 0TCT_MCWS is the multi-provider for the workspace multi-provider.

  • 0TCT_MCWS_Q0100 is the query used.

End of the note.

The search criteria for BWA Usage statistics are classified as below:

  • Top 10 workspaces consuming memory (in percent).

  • Top 10 workspaces with respect to the Local provider usage (in percent).

  • Top 10 workspaces with respect to the minimum life time (in days).

Top 10 Workspaces consuming memory (in percent)

This pane displays the top 10 workspaces consuming maximum memory. It also displays the memory allocated and the memory usage (in percentage). The information displayed as a result of this search is workspace name, memory allocated, memory occupied, and percentage of memory used.

Note Note

  • 0TCT_MCWS is the multi-provider that provides the workspace details.

  • 0TCT_MCWS_Q0108 is the query used to provide the top 10 workspaces consuming memory.

End of the note.

Top 10 workspaces with respect to the Local provider usage (in percent)

This pane displays the top 10 workspaces with maximum local provider usage. It also displays the number of local providers assigned and the number of local providers consumed by the workspaces. The information displayed as a result of this search is workspace name, local provider assigned, local provider consumed, and number of local providers consumed (in percent).

Note Note

  • 0TCT_MCWS is the multi-provider that provides the workspace details.

  • 0TCT_MCWS_Q0107 is the query for providing the top 10 workspaces with respect to the local provider usage.

End of the note.

Top 10 workspaces with respect to the minimum life time (in days)

This pane displays the top 10 workspaces with minimum life time. The information displayed as a result of this search is workspace name, expiry date and remaining lifetime (in days).

Note Note

  • 0TCT_MCWS is the multi-provider that provides the workspace multi-provider.

  • 0TCT_MCWS_Q0109 is the query that provides top 10 workspaces for minimum life time.

End of the note.

The Analyze button under each pane displays the Data Provider details of the workspace selected in the panes. The detail consists of the Data Provider Type, Data Provider, Last changed/loaded Date, Last accessed Date, Frequency of Data access and Memory used for the workspace.

Note Note

0TCT_MCWS_Q01 is the query used to understand the usage of BWA memory in KB. The individual InfoProviders that contribute to 0TCT_MCWS are as listed below:

  • 0TCT_DS26 (BWA Usage Status)

  • 0TCT_DS27 (Workspace Properties)

  • 0TCT_DS28 (Local provider properties of WorkSpace)

End of the note.

Was this page helpful to you?