Change impact analysis

Change Impact Analysis represents the process of identifying and assessing the impact of a proposed change to an SAP system. It is a proactive approach that contributes to the reliability, stability, and efficiency of SAP systems. Change Impact Analysis is a systematic process to understand the potential effects that a proposed change can have on a SAP system. The primary goal is to proactively manage and mitigate risks associated with software changes.

In the Heatmap, hover over the information icon next to Analyze Transports to see an overview of the impact of changes on your SAP system.

Select Analyze Transports and understand the impact of changes on your SAP system using Change Impact Analysis. The impact on changes is shown as Fits and Gaps. Below is a description for the two states:

• Fit: The transactions impacted by the selected transports that are covered by test cases.
• Gap: The transactions impacted by the selected transports that are not covered by test cases.

Conditions

You can analyze your SAP transports and generate the Change Impact Analysis only if Test Manager has a direct connection to your SAP instance.

Note: Change Impact Analysis supports SAP ECC, SAP S/4HANA, and SAP EWM systems.

Prerequisites

To use the Change Impact Analysis, you must allow your SAP system to communicate with your Test Manager instance. To achieve this, follow these procedures:

• Prerequisites
• Direct connection to SAP instance

Impact analysis display

Change Impact Analysis, similar to the Heatmap offers a two-level view:

1. Application components—containers inside the heatmap that contain all the transactions used inside a specific application component.
2. Transactions—boxes inside the application containers that contain data about a certain transaction or program, such as: name, SAP code, and the percentage of test relevance in the heatmap.

   Yon can zoom in on a selected area of interest and focus only on a specific SAP component or module.

   1. Gap - The transactions impacted by the selected transports that are not covered by test cases.
   2. Fit - The transactions impacted by the selected transports that are covered by test cases.
   3. Not impacted - The transactions in the transport weren't impacted by the change.

Licenses

When you analyze transports with Change Impact Analysis you consume Transport units. Transport units come in bundles of 100 units.

Every unique transport analyzed consumes one Transport unit. For example, if you purchase three bundles of Transport units, you can analyze 300 unique transports.

When you analyze a transport that has been analyzed before, no Transport unit is consumed.

Working with Change Impact Analysis

Follow the procedures below to leverage the capabilities of the Change Impact Analysis.

Accessing Change impact analysis

To access the Change Impact Analysis:

1. Open Heatmap.
2. Select Analyze Transports in the top-right.
   1. If you don't have Transport units licenses, or if you consumed all your licenses, you will only see an overview of your analyzed transports and impacted transactions.
      
      

      

      
      
   2. If you have unconsumed Transport units licenses, the Transports view opens.
   
   

   

   
   

Analyze transports

You can analyze transports in your SAP system, focusing on data only from the last 30 days for retrieval.

1. In the Transports view, next to Retrieve transports from, select a date range within the last 30 days for retrieving transports.
2. After you choose a range of dates, select Search to filter the transports.
3. Select the transports that you want to analyze.
4. Select Analyze transports to generate the Change Impact Analysis.

   The Change Impact Analysis is generated in the Heatmap View.

View the test coverage of impacted transactions

In the Change Impact Analysis view you can see the transactions impacted by changes within a transport, and their relevance in your SAP system, based on the ratios you configured for the Heatmap. Visit Heatmap ratios to learn how the ratios of the heatmap influence the relevance of transactions.

To see the impact of changes within a transport on your transactions:

1. Under the heatmap, select Gap to see the transactions that are impacted and aren't assigned to test cases.
2. Under the heatmap, select Fit to see the transactions that are impacted and are assigned to test cases.
3. Under the heatmap, select Not impacted to see the transactions that aren't impacted by the changes.
4. Select Show all (selected by default) to see all the above transactions.

Filter the impacted transactions

1. In the Change Impact Analysis view, select the type of impacted transaction that you want to see from the All transaction types dropdown:
   1. All transaction types (default)
   2. Fits
   3. Gaps
2. Select the types of interfaces where you want to see transactions from the All interface types dropdown:
   1. All interface types (default)
   2. [T] - Transaction in SAP WinGui
   3. [R] - Report/Program in SAP WinGui
   4. [W] - Transaction in SAP WebGui
   5. [F] - Application in SAP Fiori

Create test sets for impacted transactions

1. In the Change Impact Analysis view, select Table view to switch to a table of the impacted transactions.
2. Inspect the impacted transactions, based on the following information:
   1. Code: the unique code of a transaction.
   2. Name: the name of the transaction.
   3. Transport: the transport that a transaction is part from.
   4. Relevance: the relevance of a transaction based on the ratios configured at the Heatmap level.
   5. Process: the process used to publish the test cases that cover the impacted transactions.
   6. Impact: the type of impact of the change on the testing status of the transaction. This can be either Fit, Gap, or N/A.
   7. Test Set: the test set where the impacted transactions belong to.
3. Select the transactions that you want to add to a test set.
4. Select Add to New Test.
   
   

   

   
   
5. Create a new test set.
6. When you're done creating test sets for gaps in your SAP testing portfolio, select Finish.