# Working with 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.

## Overview

**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](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/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 of 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.

## Prerequisites

To enable Change Impact Analysis, go through the following prerequisites steps: [Prerequisites](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/heatmap-and-change-impact-analysis-prerequisites)

## View tabs for SAP Changes

Change Impact Analysis offers a comprehensive way to consider the potential impact of changes (Fits and Gaps) on your SAP system. It does this by presenting three different view tabs that help examine transaction relationships:

1. **UI**: Displays transactions impacted by the selected transports.
2. **API**: Displays technical interfaces impacted by the selected transports, such as SAP BAPI, SAP RFC, SAP QUERY, and SAP IDOC.
3. **Security**: Displays security transactions and corresponding users impacted by the selected transports.

## 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.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-docs-image-302572-d5d601f4-eaa2ddd7.webp)

## 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.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-docs-image-313090-6f157a72-7ea7d231.webp)
   2. If you have unconsumed **Transport units** licenses, the **Transports** view opens.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-docs-image-340415-d7c3e319-f00e7af9.webp)

## 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**.

## Switching view tabs for SAP changes

Change Impact Analysis offers view tabs for switching between the SAP changes that you want to investigate. You can choose what tabs are available in your Change Impact Analysis when configuring the connection.

The available view tabs are:

* **UI**: This tab is always available, and it displays transactions impacted by the selected transports.
* **API**: Displays technical interfaces impacted by the selected transports, such as SAP BAPI, SAP RFC, SAP QUERY, and SAP IDOC.
* **Security**: Displays security transactions and corresponding users impacted by the selected transports.

Under **Impact Analysis**, select one of these view tabs to investigate the SAP changes in your system.

Figure 1. Change Impact Analysis view tabs

  ![Change Impact Analysis view tabs](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-change-impact-analysis-view-tabs-553451-44a0a441-82ee660c.webp)

## 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**.

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

In the Impact Analysis view, you get the option to filter the view of impacted transactions based on different criteria. Irrespective of the view tab, you have the option to filter impacted transactions based on impact types:

* **All impact types** (default)
* **Fits**
* **Gaps**

Depending on the view tab you are currently in, you can filter impact transactions based on the following criteria:

* **UI** tab – You can filter transactions based on interface types:
  + **All interface types** (default)
  + **[T] - Transaction in SAP WinGui**
  + **[R] - Report/Program in SAP WinGui**
  + **[W] - Transaction in SAP WebGui**
  + **[F] - Application in SAP Fiori**If you are using an **RFC connection**, the following view tabs are also available:
* **API** tab – You can filter transactions based on API types:
  + **QUERY**
  + **IDOC**
  + **RFC**
  + **BAPI**
* **Security** tab – You can filter transactions based on security types:
  + **Security TCode**: Displays security TCodes and the user authorized to access them.
  + **Transactions**: Displays transactions along with their corresponding users.
    :::note
    Information for this security type is not shown in the List view, but you can select **Export** to view it as a CSV file.
    :::
  + **Users**: Displays users along with their corresponding transactions.
    :::note
    Information for this security type is not shown in the List View, but you can select **Export** to view it as a CSV file.
    :::

For further investigation, you can select **Export** to retrieve the filtered transactions in a CSV file.

## Generate test cases for impacted SAP transactions

### Prerequisites

* To use AI-powered test generation for SAP transaction, your Test Manager role must have the following permissions: **Test Case** - Create.
* (For Cloud Commercial only) If you want to leverage RAG when generating tests, you first need to get started with using Context Grounding, which RAG is a component of. To get started with Context Grounding, visit the dedicated [Best practices](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/context-grounding-best-practices) page.

You can generate test cases for the transactions marked as GAP, using Autopilot.
:::note
If you are using an **RFC connection**, you can only generate tests from the **UI** view tab.
:::

1. In the **Analyze Transports** step from the **Impact Analysis**, select **List view** to switch to a table of the impacted transactions.
2. For the transactions marked as **GAP**, select **Generate**. The **Provide Supporting Documents** window opens, focused on the **Add documents** section, prompting you for attachments or other documents necessary for generating test cases. Figure 2. Selecting GenerateTests for Gaps in the Impact Analysis

   ![Selecting GenerateTests for Gaps in the Impact Analysis](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-selecting-generatetests-for-gaps-in-the-impact-analysis-553473-3a04c5c8-675971ac.webp)

   1. In the **Add documents** section of the **Provide additional context** window, select additional attachments. These are used when generating tests. You can also upload other files yourself.

Figure 3. The Add documents section for generating tests For Cloud Commercial only

   ![The Add documents section for generating tests](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-the-add-documents-section-for-generating-tests-515509-6388f000-aa0d8d01.webp)
   2. (For Cloud Commercial only) In the **Leverage RAG** section of the **Provide additional context** window, select an index which stores your data uploaded to [Context Grounding](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/about-context-grounding). The selected index helps Autopilot in generating more accurate tests by giving it context about the applications that you are trying to automate. For example, you can leverage RAG when a requirement document has incomplete information or refers to additional details in other sections. In this case you can leverage RAG to draw those details from indexed references. **Note:** For best practices on working with Context Grounding, visit [Best practices](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/context-grounding-best-practices).
      1. From the **Select folder** dropdown list, select the folder where you store the indexes storing the desired information you want to share with Autopilot.
      2. From the **Select index** dropdown list, select the specific index that you want Autopilot to reference.
      3. For **Number of results**, enter the number of tests you want Autopilot to generate based on the referenced information.

Figure 4. The Leverage RAG section for generating tests

   ![The Leverage RAG section for generating tests](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-the-leverage-rag-section-for-generating-tests-523351-5dcf8e8d-5d891c5f.webp)
3. Select **Next** and provide additional instructions that Autopilot should use when generating test cases. Choose from a prompt from the [Prompt library](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/prompt-libraries#prompt-library) or type these instructions in the **Provide Additional Guidance** window. These are some of the instructions that Autopilot can follow:
   * You can instruct Autopilot the number of test cases that you want to generate. The maximum number of test cases is 50.
   * You can specify Autopilot to cover all user steps and acceptance criteria described in the loan request requirement.
   * You can instruct Autopilot to generate pre-conditions.
   * You can specify Autopilot to generate an expected result for each test step.
   * By default, Autopilot considers existing tests linked to a requirement to prevent duplicating tests. However, you can instruct Autopilot to disregard existing tests during new test generation. You can do this by providing an instruction like: "Do not consider tests that are linked to this requirement when generating tests".

Figure 5. Entering instructions in the **Provide additional guidance** window

   ![Entering instructions in the Provide additional guidance window](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-entering-instructions-in-the-provide-additional-guidance-window-463769-470f5443-fa14b856.webp)
4. Select **Generate tests** to initiate the process. When the generation finishes, you will receive a **Test Case generation completed** notification. Depending on your [notification preferences](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/my-notifications#subscribing-to-events), you can receive the notification both in-app and via email.
5. Select the **Test generation completed** notification to review the generated test cases.
   1. Expand each test case in the **Generate tests** panel, and review the generated test cases.
   2. If you are satisfied with their content, select **Create tests**.

Figure 6. Expanding a generated test case

   ![Expanding a generated test case](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-expanding-a-generated-test-case-463765-5e551874-5d9cf4c3.webp)
6. If you are not satisfied with the generated test cases, select **Regenerate**, and provide additional details about your use case.
   1. Attach more relevant documents for Autopilot to use.
   2. Click **Next** and type additional details in the **Provide instructions** text box.
   3. After refining the steps, select **Regenerate**.
   4. Click the **Test generation completed** notification to access the regenerated test cases.
   5. Expand each test case and review them.
   6. Select the test cases that you are satisfied with, and then select **Create tests**.

### Supported file types

Autopilot can process various file types. Depending on the file type, Autopilot can process certain content from it. The following list presents the file types you can offer to Autopilot, along with details about the type of content Autopilot can process from each type:

* Processes only text content – Autopilot processes only the text content from these file types:
  + TXT
  + BPMN
  + CSV
* Processes both text and image content – Autopilot processes both the text and images from these file types:
  + DOCX
  + XLSX
  + PNG
  + JPG
  + PDF

## 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**.

Figure 7. Adding impacted transactions to new test sets

   ![Adding impacted transactions to new test sets](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-adding-impacted-transactions-to-new-test-sets-553480-638ba389-2abfb41a.webp)
5. Create a new test set.
6. When you're done creating test sets for gaps in your SAP testing portfolio, select **Finish**.