What is End-to-End Change Analysis and Why it is used?
If a system behaves differently after a certain date or change, E2E Change Analysis is the first tool to use. Changes are a common starting point for problems in your landscape. Imagine that something worked yesterday, but it is not working anymore today. The first question would be what changed in between?
E2E Change Analysis is the tool to analyze problems like this. Again, the tool starts with an overview on the overall changes which have been applied to the landscape
In development system we will have many inflight changes which are in process of movement to Production. There might be a chance of differences in the landscape in a given time. Change Analysis helps you to keep track of these changes in the landscape and it stores regular snapshots of the changes performed and changes in configuration settings in system and store in Configuration & Change Database(CCDB).
It is possible to compare different systems and generate a report which contains the results. This approach identifies the problem by comparison rather than by drilling down, which is faster and easier in most cases.
This application is based on a central Configuration & Change Database (CCDB).
Why Change Analysis?
Change Analysis displays changes of configuration items in a system like OS, DB, ABAP parameters, Java parameters, transport requests, Support Packages and serves with in each timeframe which serves as a central entry point for root cause analysis.
From this we can identify the problem by comparison rather than by drilling down, which is faster and easier in most cases
It provides an overview of the changes that have been applied to the managed systems. It also displays the number of changes per system, change category, and day.
It also provides the details of number of changes and the history of changed item
How to access Change Analysis and how to interpret results?
Change Analysis can be accessed form: SM_Workcenter-->Root Cause Analysis-->Change Analysis
Once we click on Change Analysis tile, we need to select system which is required for analysis and provide the timeframe of changes.
Figure: Change Analysis below is the home screen.
Change Analysis Home screen
From here, we can drill down to the type of changes and from there to the actual changes itself.
The available changes are categorized (again depending on the system type) and then displayed like in the lower part (example for an ABAP system). Here you can easily identify that on certain dates a lot of changes in the definition of RFC destinations or that on another day Gateway relevant parameter changes have been applied to the system.
With a further drill down, it is then possible to identify the changes in detail and also get a history on the single change.
In addition to the time-based analysis, it is possible to compare the configuration of two systems against another one using the Change Reporting tool. By this it is possible for example if you have a problem in your production system which cannot be reproduced in the quality assurance system, what the configuration differences between the two systems are