e2e root cause analysis for sap business objects financial

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2012 SAP AG 1

E2E Root Cause Analysis for

SAP Business Objects Financial

Consolidation

Applies to:

SAP Business Objects Financial Consolidation 7.5 and 10.0 with SAP Solution Manager 7.01 SPS 26 or higher.

Summary

SAP Business Objects Financial Consolidation 7.5 and 10.0 have been integrated into Solution Manager 7.01 and 7.1 to support Root Cause Analysis. This document describes the supported features of Root Cause Analysis with SAP Business Objects Financial Consolidation7.5 and 10.0 in Solution Manager 7.01.

Authors: Ravikanth Bulusu, Morgan Che

Company: SAP America Inc., SAP China

Created on: April 18, 2012

Authors Bio

Ravikanth Bulusu (Rob) works for SAP America Inc. His area of specialization includes implementation of SAP Business Process & Application Operations, RUN SAP Like a Factory projects, E2E Root Cause Analysis, and Diagnostics application support integration into Solution Manager. Morgan Che is working for SAP China, Active Global Support. His current focus area is the support of SAP Business Objects Financial Consolidation solutions. As product integrator, Morgan works on SAP Solution Manager Diagnostic content for SAP and Business Objects products and applications.

E2E Root Cause Analysis for SAP Business Objects Financial Consolidation


© 2012 SAP AG 2

Table of content

End-to-End Root Cause Analysis Scope ............................................................................................................ 3

Root Cause Analysis (RCA) using Solution Manager ........................................................................................ 3

Host System Diagnostics .................................................................................................................................... 4

File System Browser ....................................................................................................................................... 4

OS Command Console ....................................................................................................................................... 5

Root Cause Analysis with SBOP FC .................................................................................................................. 5

Introscope Analysis Overview ......................................................................................................................... 5

Introscope Workstation\Web View .................................................................................................................. 6 Option 1: New Console ................................................................................................................................................ 7

Option 2: New Investigator ......................................................................................................................................... 14

Application Server Metrics ............................................................................................................................ 16 Instrumentation .......................................................................................................................................................... 16

Metrics measured in current Instrumentation ............................................................................................................. 16

Instrumented Methods and Dashboards .................................................................................................................... 17

Application Server Processes Monitoring .................................................................................................................. 18

Transaction Tracing at Component Level .................................................................................................................. 21

E2E Workload Analysis ................................................................................................................................. 21 Goal and Concept ...................................................................................................................................................... 21

Starting the E2E Workload Analysis for SBOP FC ..................................................................................................... 21

E2E Workload Analysis Overview .............................................................................................................................. 22

Key Performance Indicators ....................................................................................................................................... 22

Time Profile ................................................................................................................................................................ 25

BOFC Web Server specific Workload data ................................................................................................................ 25

E2E Exception Analysis ................................................................................................................................ 25 Goal and Concept ...................................................................................................................................................... 25

Starting the E2E Exception Analysis for SBOP FC .................................................................................................... 26

E2E Exception Analysis Overview ............................................................................................................................. 26

Key Performance Indicators ....................................................................................................................................... 27

Change Analysis ........................................................................................................................................... 28 Goal and Concept ...................................................................................................................................................... 28

Starting Change Reporting for SBOP FC ................................................................................................................... 28

Change Reporting ...................................................................................................................................................... 28

Starting Change Analysis ........................................................................................................................................... 29

Change Analysis ........................................................................................................................................................ 29

Related Content ................................................................................................................................................ 30

Copyright........................................................................................................................................................... 31



© 2012 SAP AG 3

End-to-End Root Cause Analysis Scope

This document describes the features of E2E and Component level Root Cause Analysis with SAP Business Objects Financial Consolidation 7.5 and 10.0. As of writing of this document, the next release of Solution Manager is in progress and that may include or integrated with End-to-End trace analysis, which allows us to trigger the trace recording the transactions from client-end to server-end. BOFC is one of the major products of SBOP (EPM Suite) Enterprise Performance Management Suite. For latest product specific documentation please check the reference links provided below.

SAP BOFC Production documentation can be referenced from the below link:

http://service.sap.com/instguides

SAP FC Admin Guide

SAP FC Master Guide

SAP FC Database Guide

SAP FC Installation Guide

SAP FC Configuration Guide

SAP FC Security Guide

Installation & Upgrade Guides

SAP BusinessObjects Enterprise Performance Management

Root Cause Analysis (RCA) using Solution Manager

The standard Root Cause Analysis (RCA) defines how to perform a root cause analysis across different support levels and different technologies. The basic idea behind Root Cause Analysis is to determine where and why a problem occurred. Root Cause Analysis is not only an E2E Standard defined by SAP, it is a procedure based on SAP best practices with a set of tools shipped with SAP Solution Manager.

Overall, Root Cause Analysis works towards simplifying the problem resolution process with-in an IT environment and reducing the total cost of ownership. Potential benefits of these standard tools for RCA are:

Ensured continuous business availability – Root Cause Analysis helps to accelerate the problem resolution process. As a result introducing SAP’s RCA methodology generally leads to increased availability of the IT solution.

Reduced costs for support experts - The targeted top-down approach of RCA supports a one step dispatching of issues from an IT Generalist to a Component Ex-pert. Thereby the overall problem-resolution time and the number of resources involved in the investigation are reduced. Progressive data aggregation and unified display of diagnostics data across applications and technologies drastically reduce the level of specialism required to isolate the area of concern.

Reduced license costs - Supporting RCA Tools offered by SAP are part of the standard maintenance contract and come at no additional fee.

Appropriate tools for root cause analysis are available off-the-shelf and quickly realized with minimal configuration. Thereby a time consuming identification process for analysis tools is avoided. Even a structured and proven resolution roadmap is provided by SAP.

One safe access channel to all systems – Root Cause Analysis provides one safe and central access channel to the customer’s landscape. If required, an investigation is continued on the system in concern using a predefined support user (SAPSUPPORT), who is only assigned read-only rights.

Collected workload and exception data is displayed in unified views, thereby abstracting data from the underlying technology stack. This approach supports the structured top down analysis approach, as generalists and experts start investigating at one common point.

Empowers the customer to solve problems by their own - E2E Root Cause Analysis pro-vides expert tools which enable a customer to quickly solve problems, thereby reducing overall resolution time.

Data foundation for monitoring and IT reporting - Diagnostics in SAP Solution Manager forms the technological foundation for SAP’s next generation application monitoring. As a result, implementing Diagnostics already marks one essential step for this upcoming functionality. Furthermore, data collected by Diagnostics is reused for automated IT reporting.

More information about Root Cause Analysis, please refer to E2E Root Cause Analysis.

http://service.sap.com/instguides

https://websmp107.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700004587912005E



© 2012 SAP AG 4

Note: In Solution Manager 7.1, BOFC Application Server and Web Server use the individual Technical type for Solution Manager Diagnostic setup, which is different from the prior versions of Solution Manger, like Solution Manager 7.0. For the more detailed information about Diagnostic setup of Solution Manager 7.1 or 7.0, please refer to Diagnostic setup guide. For Root Cause Analysis, such as Host Analysis, Working load analysis etc, BOFC Application Server and Web Server also use the separate technical system in Solution Manager accordingly. However, for the analysis methodology, it does not tell the version of Solution Manager and BOFC.

Host System Diagnostics

File System Browser

The File System Browser can be lunched from ―Solution Manager Work centers‖.

1. Log into Solution Manager. 2. Enter transaction ―SOLMAN_WORKCENTER‖. 3. Click ―Root Cause Analysis‖ tab. 4. Select ―Host Analysis‖.

5. Select the Financial Consolidation Host System 6. Press button ―File System Browser‖.

The File System Browser within Solution Manager Diagnostics allows browsing of the file system on the monitored systems. By default the component main directories are already available as entry points in the file system browser. We can use this function to Browse/Download files remotely without asking the system administrator to send us all the logs.



© 2012 SAP AG 5

OS Command Console

The OS Command Console within the Solution Manager Diagnostics allows executing the predefined OS commands on the monitored systems. Currently, BOFC has no custom specific commands.

In Host Analysis->OS Command Console, there are groups of Os commands we can execute OS command lines remotely for BOFC system. The results of the execution will retrun to the Result pane. The screenshot below is an example of Network status command.

Root Cause Analysis with SBOP FC

Introscope Analysis Overview

Introscope is an enterprise application performance management solution that enables us to monitor complex web based applications in production environments 24x7, detect problems before they affect us, and resolve these issues quickly and collaboratively.

Introscope provides comprehensive end-to-end transaction visibility and diagnostic capabilities across your entire infrastructure—BOFC Web Server, BOFC Application Server and host system.

It provides us a capacity to monitor BOFC web applications so we know what’s going on from the inside out across our broad enterprise network and systems. By monitoring load, requests, and sessions, Introscope lets us know how the BOFC web application system resources are getting consumed. Additionally, the dashboards in Introscope that provide an aggregated view on selected metrics are built for easy reference



© 2012 SAP AG 6

and analysis. This allows providing views that can be easily understood by support personnel with little knowledge or customer administrators.

Besides aggregated view, it also enables us to have the detailed view and do problem root cause diagnosis. These capabilities allow determining, for example:

What components inflict on performance bottleneck? Are our service levels acceptable? How many requests to a specific service failed during the last hour or past a few days? What’s the current status of my application network? How about hardware resource consumption, such as CPU, Network, RAM etc?

With Introscope, we can reliably answer these questions and determine where to assign the fix. Introscope’s major components are the agents, Enterprise Manager, WebView, and Workstation.

To learn more about how Wily Introscope monitors, detects, and triages application management problems, see the following document: Wily Introscope User Guide.

To implement Wily Introscope, firstly, we should ensure Wily .Net Agent has been installed and configured correctly. For more information on this topic, please see SAP Note 1126554 – Wily Introscope .Net Agent.

Secondly, we have to configure what applications should be instrumented, before measurements can be taken. This means that a list of relevant application performance areas should be predefined for performance monitor. The specific application, classes and methods should be identified & instrumented in instrumentation directive file, such as sap_bofc.pbd.

Finally, we can lunch BOFC Web Server and Application Server to evaluate if the performance related metrics have been successfully brought to Enterprise Manager.

Introscope Workstation\Web View

Introscope Workstation\Web View can be lunched via Solution Manager Root Cause Analysis ->Host Analysis-> Introscope ->Web view / Introscope Workstation

In poping up windows, click ―Start Introscope‖.

In Introscope logon dialogue, provide the host name of Enterprise Manager, Port, User Name and Password to finish authentication.

https://websmp107.sap-ag.de/~sapdownload/011000358700000080632007E

https://service.sap.com/sap/support/notes/1126554



© 2012 SAP AG 7

Performance metrics of Financial Consolidation Application, MS.Net/IIS web Server/Application Server, among others, can be accessed using multiple visual interfaces of Introscope. The metric data is collected periodically into the Introscope Enterprise Manager from the monitored systems by the Solution Manager Diagnostics, Host, IS agents that are installed on the monitored systems. The agents have to be running online on a continuous basis for the host(s)/application(s) to be monitored, analyzed.

Console -> Enables to access some of the important metrics that are prebuilt, have visual interfaces. Metric data in console view may be grouped or organized as per the relation with a specific application.

Investigator -> Enables to browse and search the metric data in a visual hierarchical tree structure.

An example screenshot is shown below with option of accessing the Investigator, Console from the Introscope workstation. One can open multiple instances of Investigator or Console via the Workstation Menu option New Console or New Investigator.

Option 1: New Console

The Console displays metric information in dashboards. Dashboards are preconfigured windows that presents graphical views of current or historical performance and availability metrics.

Once the Console is opened; navigate to the Page 3 as shown in the screen below.



© 2012 SAP AG 8

While on Page 3 of Console, scroll vertically to the bottom. Locate BOFC entry point into the Financial Consolidation application performance metrics.



© 2012 SAP AG 9

Financial Consolidation performance metrics can be accessed via two main views (referred as Dashboard) from console enabled navigation entry point.

BOFC Triage: BOFC Triage enables to look at a quick view of the performance data from Financial Consolidation Web server and Application Server. However, to get the details or access metrics at an increased scope, BOFC Overview option is provided.

BOFC Overview:

BOFC Overview enables to view Performance data organized and grouped by relevant application functionality/processes. Overview Dash board has been divided into multiple sections where each section provides multiple detailed dashboards.



© 2012 SAP AG 10

Web Server Instrumentation

Some of the most important entry methods for the execution of the Financial Consolidation Web application are instrumented dynamically.

Metrics measured in current Instrumentation

Average Response Times: Average response time measured for selected interval in ms

Responses per Interval: Number of successful executions for selected Interval

Concurrent Invocations Per Interval: Number of concurrent method calls

Errors per Interval: Number of executions for selected interval with an error code

Stall Count: Method execution longer than 30 seconds

Triage Dashboard

This view collects data from the execution of Critical BOFC Web Application methods. Measurement excludes client time (Example: Front-end browser level) and includes the time spent on the Ctserver Process from BOFC Application Server and web application server.

Information collected on this dashboard includes:

BOFC .Net Application Average Response Times (ms) Connection – Web Application User Login Package Process – Open Package Import Process – Import Collection



© 2012 SAP AG 11

Import Process – Import Package Import Process – Import Pack from Pack

Controls – Execute Controls from Editor Document Process – Execute Document

BOFC .Net Application Responses per Interval Connection – Web Application User Login Package Process – Open Package Import Process – Import Collection Import Process – Import Package Import Process – Import Pack from Pack Controls – Execute Controls from Editor Document Process – Execute Document

BOFC Application Server Process CPU utilization (%) CPU utilization (%) at process level – CtBroker, CtController, Ctserver …

IIS W3WP Bytes in all Heaps Indicates, in bytes, the current memory allocated on the garbage collection heaps.



© 2012 SAP AG 12

IIS W3WP Process CPU Utilization (%)

Indicates processor activity, displays the average percentage of busy time observed during the interval.

BOFC Overview

BOFC overview enables to view Performance data grouped by relevant application functionality/processes, which includes:

ExecuteControlsFromEditor: Execution of control actions for open package via web server client. This view collects data from the execution of Critical BOFC Web Application methods. Measurement excludes client time (Example: Front-end browser level) and includes the time spent on the ctserver Process from BOFC Application Server and web application server.

ImportCollection: Execution data import from file via data link using the web client. This view collects data from the execution of Critical BOFC Web Application methods. Measurement excludes client time (Example: Front-end browser level) and includes the time spent on the ctserver Process from BOFC Application Server and web application server.

ImportPackage: Execution of a data import. This view collects data from the execution of Critical BOFC Web Application methods. Measurement excludes client time (Example: Front-end browser level) and includes the time spent on the ctserver Process from BOFC Application Server and web application server.

ImportPackFromPack: Execution of a data import into a package. The data source can be another package or another system. This view collects data from the execution of Critical BOFC Web Application methods. Measurement excludes client time (Example: Front-end browser level) and includes the time spent on the ctserver Process (from BOFC Application Server(s)) and web application server.

ExecuteDocument: Execution of documents when a schedule has been opened. This view collects data from the execution of Critical BOFC Web Application methods. Measurement excludes client time (Example:



© 2012 SAP AG 13

Front-end browser level) and includes the time spent on the ctserver Process (from BOFC Application Server(s)) and web application server.



© 2012 SAP AG 14

Option 2: New Investigator

Browse the Investigator tree structure by expanding each node on the tree to find the host on which Financial Consolidation Web server/Server components are deployed.

To access Application specific Performance metrics follow the example:

BOFC Web Client Manipulation: *Super Domain* <Host Name> DotNet Process <SAP BOBJ> FC

BOFC Web Application: *Super Domain* <Host Name> DotNet Process Frontends -> [Apps] ->[Web]



© 2012 SAP AG 15

Application Server: *Super Domain* <Host Name> SAP HostAgent Process <SAP HostAgent>BOF <BOFC>

WMI: Host level performance metrics & Financial Consolidation application server process level metrics: (Example ctserver, CtBroker, CtController [windows level processes,*. exe]...) follow the example: Super Domain* <Host Name> <SAP HostAgent>WMI Process ctserver.exe[CtBroker]



© 2012 SAP AG 16

In the E2E Workload Analysis of Solution Manager, the application metrics above are further aggregated to an overview and per collected metric for Web Server application. For E2E Workload Analysis topic, it will be illustrated in more detail in ―E2E Workload Analysis‖ sector.

Application Server Metrics

Instrumentation

The most important entry methods on the Application Server side are instrumented as static instrumentation in the coding of the application.

Metrics measured in current Instrumentation

For the application server the metrics of all server processes are displayed aggregated on the same host.

Average Elapsed Time (ms): Response Time in ms

Finished Counter: Number of executions

Finished with undefined state: Executions without a successful state



© 2012 SAP AG 17

Instrumented Methods and Dashboards

Consolidation Task : Execution of consolidation task

Datalink Task: Integration of data into Financial Consolidation via data link

Document Execution from Web Client: Execution of documents on application server

Package Opening: Open package on application server



© 2012 SAP AG 18

User Connection: Logon process on application server

User Disconnection: Logoff process on application server

Application Server Processes Monitoring

The application server processes for each host the following WMI metrics are collected:

Private Bytes: Private memory allocated by CPU process.

Process ID: Process ID of the CPU process.

Processor Time (%): Percent processor time currently used by selected process.



© 2012 SAP AG 19

Access via Investigator:

For the metric pecentage, please click ―Metric Count‖ button to find the detail:



© 2012 SAP AG 20

Application Dashboard:



© 2012 SAP AG 21

Transaction Tracing at Component Level

A transaction can be traced using the Transaction Tracer view. Here is the log file of the Transaction that was traced. Transaction monitor has to be invoked with parameters to run for short duration prior to running the transaction, once the trace is on, the transaction can be executed. Once the execution is completed, ensure the transaction trace is turned off. The results can be viewed in the log as summarized below in the Summary View.

E2E Workload Analysis

Goal and Concept

The goal of the E2E Workload Analysis is to provide access to statistical performance data of different systems. You will be able to perform a cross-system correlation analysis based on the temporal behavior of performance metrics. Dedicated Key Performance Indicators (KPI) are calculated and displayed, allowing us to quickly gauge which system or software component is the root cause of a potential performance problem.

We can use the E2E Workload Analysis to identify general performance bottlenecks in BOFC Application Server and BOFC Web Server landscapes. Here, we take technical system E88 - BOFC Application Server and IIS00034 - BOFC Web Server for example.

The following describes the SBOP FC specific E2E Workload Analysis data. Additional information about architecture and features of E2E Workload Analysis can be found in the E2E Workload Analysis – User guide available in the SAP Support Portal (www.service.sap.com/diagnostics).

Starting the E2E Workload Analysis for SBOP FC

The E2E Workload Analysis application can be started from ―Solution Manager Work centers‖.

1. Log into Solution Manager. 2. Enter transaction ―SOLMAN_WORKCENTER‖. 3. Click ―Root Cause Analysis‖ tab. 4. Select ―End-to End Analysis‖. 5. Select the Financial Consolidation System 6. Press button ―Workload Analysis‖.

Note: Here, we only take BOFC 10.0 Application technical system – E88 for example. The same methodology can be also used for BOFC 10.0 Web technical system, BOFC 7.5 Web server and BOFC 7.5 Application Server.

http://www.service.sap.com/diagnostics



© 2012 SAP AG 22

E2E Workload Analysis Overview

The central entry point for the workload analysis is the Overview Tab of the E2E WA application. This section of the application has two parts: the left-hand side contains the graphical display of the time-dependent parameters. On the right-hand side, selected KPI values for the chosen E88 systems are displayed. Please note that these values are calculated for the timeframe chosen in the application.

Key Performance Indicators

The KPI area on the right-hand side allows the comparison of different parameters specific to the analyzed system. For E88 technical system, the average response time of the most important metrics are displayed. These values are recorded by Wily Introscope Enterprise manager and transferred once per hour to Solution Manager BI. The Workload summary view displays workload data for E88.

In the E2E Workload Analysis application the data is further aggregated to an overview and per collected metric for Application Server application.



© 2012 SAP AG 23

In ―Fin Cons. Appl Serv.‖ tab, we can see the component application metric percentage, which offer us the ability to judge the possible components or manipulations which may cause the performance bottleneck.

The CPU & Memory Util view in ―Host‖ tab displays CPU & Memory utilization of the host running the BFC SERVER. It allows identifying CPU or memory bottlenecks.



© 2012 SAP AG 24

The Monitored Processes view in ―Host‖ tab displays process consumptions in a summary method, which allows us to simply identify the top processes.



© 2012 SAP AG 25

Time Profile

For the Graphical Display, the standard Display Type is the "Time Profile". Here, regardless of the timeframe chosen for display, the aggregated Day Profile is always displayed. For example: If last week has been chosen for display, the graph - which always ranges from 0:00 to 23:00 on the x-axis - displays the average hourly values for the last week.

The intention of this kind of display is to allow a quick identification of the workload peaks which are directly correlated to typical working hours of the system.

BOFC Web Server specific Workload data

For BOFC Web Server specific workload data, we can click BOFC Web Server technical system tab. Since the methodology of analysis is the same as BOFC application server, the detailed information can be referred to the prior sections.

E2E Exception Analysis

Goal and Concept

The goal of the E2E Exception Analysis is to easily and efficiently identify the most frequent errors and the applications which are causing them.

Dedicated Key Performance Indicators (KPI) are calculated and displayed, allowing you to quickly isolate locations that cause a large number of errors or an unusual number of critical system errors.

Thus, E2E Exception Analysis serves as a central hub for the analysis of errors, exceptions and dumps across all monitored systems. All data is extracted in regular intervals and can either be displayed in a condensed manner or in greater detail according to the requirements. In-depth analysis of specific error states can be initiated by accessing individual logs, traces or transactions through various Jump-in features.

The following describes the SBOP FC specific E2E Exception Analysis data. Additional information about architecture and features of E2E Exception Analysis can be found in the E2E Exception Analysis – User guide available in the SAP Support Portal (www.service.sap.com/diagnostics).



© 2012 SAP AG 26

Starting the E2E Exception Analysis for SBOP FC

The E2E Exception Analysis application can be started from the ―Solution Manager Work centers‖.

1. Log into Solution Manager. 2. Enter transaction ―SOLMAN_WORKCENTER‖. 3. Click ―Root Cause Analysis‖ tab. 4. Select ―End-to End Analysis‖. 5. Select the Financial Consolidation System. 6. Press button ―Exception Analysis‖.

Note: Here, we take BOFC 10.0 Application technical system – E88 for example. The same methodology can also be used for BOFC 10.0 Web technical system, BOFC 7.5 Web server and BOFC 7.5 Application Server.

E2E Exception Analysis Overview

The central entry point for the exception analysis is the Overview Tab Strip of the E2E EA application. This section of the application has two parts: the left-hand side contains the graphical display of the time-dependent parameters. On the right-hand side, selected KPI values for the chosen BFC systems are displayed. Please note that these values are calculated for the timeframe chosen in the application.



© 2012 SAP AG 27

Key Performance Indicators

The KPI area on the right-hand side allows the comparison of different parameters specific to the analyzed system.

The following E88 specific KPIs are displayed for BOFC Application Server:

1. Total Number of S64 Log errors in the selected time interval. 2. Total number of Windows Event log data in the selected time interval.

These values are extracted from Windows Event log on BOFC server and transferred once per hour to Solution Manager BI.

For the Graphical Display, the standard Display Type is "History". In contrast to the Time Profile, the diagram type History displays the data un-aggregated as time series. Thus, the x-axis always directly reflects the timeframe selected at the start of the application. For time series, a two layered x-axis is displayed, where the next higher level of temporal granularity is displayed below the initial one. This pairing depends on the timeframe selected for display. In the example above, the time frame for which data is available spans two days. Thus, the Hour of the selected timeframe is displayed on top of the Calendar Day. This display type allows the analysis of error frequency and how it behaves over time. Trends and peaks can be correlated with other occurrences in the managed system and lead to a more detailed analysis by narrowing down the timeframe and employing the Product Instance specific Views.

In ―Fin Cons. Appl. Serv‖ tab, we can have the detailed view of error events.



© 2012 SAP AG 28

Change Analysis

Goal and Concept

Controlling the changes during the entire application lifecycle becomes crucial in Solution Manager Perspective. Indeed, we need a tool to report how/when/which changes are introduced to a software landscape in order to detect the Root Cause of an incident. The goal of the Change Reporting (CR) is to provide a top-down view on the Technical Configuration Parameters, Transport Requests, SAP Notes or Software Maintenance changes of the satellite systems. It is based on the data of the Configuration and Change Database (CCDB) which is also part of the Solution Manager - Diagnostic Capabilities. The numbers of changes are stored in BI and the configuration data itself is stored in the CCDB of the Solution Manager Diagnostics.

The following describes the SBOP FC specific Change reporting content data. Additional information about architecture and features of Change Reporting like comparing configuration , checking the change history can be found in the SP18 Change reporting – User guide available in the SAP Support Portal (www.service.sap.com/diagnostics -> Media Library).

Starting Change Reporting for SBOP FC

The Change Reporting application can be started from the ―Solution Manager Work centers‖.

1. Log into Solution Manager. 2. Enter transaction ―SOLMAN_WORKCENTER‖. 3. Click ―Root Cause Analysis‖ tab. 4. Select ―System Analysis‖. 5. Select the Financial Consolidation Server. 6. Press button ―Change Reporting‖.

Note: Here, we take BOFC 10.0 system – E88 for example. The same methodology can be also used for BOFC 7.5 server.

Change Reporting

The Change Reporting application collects and displays centrally relevant configuration data for BFC. To display the current configuration of BOFC, select the relevant Store Group, select the Configuration Store you are interested in and check the Store content.

http://www.service.sap.com/diagnostics



© 2012 SAP AG 29

We can also compare the changes of the specific system in the two different days by choosing Timestamp, which can allow us easily isolate the changes made for the system.

Starting Change Analysis

The Change Reporting application can be started from ―Solution Manager Work centers‖. 1. Log into Solution Manager. 2. Enter transaction ―SOLMAN_WORKCENTER‖. 3. Click ―Root Cause Analysis‖ tab. 4. Select ―End to End Analysis‖. 5. Select the Financial Consolidation Server 6. Press button ―Change Analysis‖.

Change Analysis

The Change Analysis aggregates data and displays centrally relevant change.



© 2012 SAP AG 30

Related Content

It is highly recommended by SAP to install and setup Solution Manager 7.01 SP26 or higher in order to benefit from the improved supportability capabilities for the SBOP FC product. Please refer to the setup guides as links are provided below for your reference.

Diagnostics Setup & User guides

SP18_SOLMAN_SETUP Guide

Introscope Version 8 Installation Guide For SAP

http://service.sap.com/diagnostics

https://websmp108.sap-ag.de/~sapidb/011000358700000066952009E/SP18_SOLMAN_SETUP.pdf

https://websmp108.sap-ag.de/~sapdownload/011000358700001995842008E



© 2012 SAP AG 31

Copyright

© Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

e2e root cause analysis for sap business objects financial

Documents