test-manager
latest
false
UiPath logo, featuring letters U and I in white

Test Manager user guide

Last updated Aug 26, 2025

Working with Change Impact Analysis

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, 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

View tabs for SAP Changes

When using an RFC connection, 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.


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.

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

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.
You can generate test cases for the transactions marked as GAP, using AutopilotTM.
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

    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.
  3. Select Next and provide additional instructions that AutopilotTM should use when generating test cases. Choose from a prompt from the 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 AutopilotTM the number of test cases that you want to generate. The maximum number of test cases is 50.
    • You can specify AutopilotTM to cover all user steps and acceptance criteria described in the loan request requirement.
    • You can instruct AutopilotTM to generate pre-conditions.
    • You can specify AutopilotTM 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 3. Entering instructions in the Provide additional guidance window

  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, 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 4. Expanding a generated test case

  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 AutopilotTM 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 5. Adding impacted transactions to new test sets

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

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2025 UiPath. All rights reserved.