> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/knowledge-base/sealights-for-abap/test-cycles/reviewing-change-analysis-results.md).

# Reviewing Change Analysis Results

The Change Analysis tab is the first output produced after a test cycle is created. It answers the question: *what changed and what is at risk?* It shows how many SAP functional areas were touched, how many executables are affected, which are ranked most-at-risk, and the total count of changed ABAP objects — all derived from structural analysis before a single test runs.

***

### Business Value & Key Use Cases

* **Pre-test risk briefing** — Release managers understand the scope and concentration of risk before testing begins, enabling informed decisions about priorities and resources.
* **Stakeholder communication** — The downloadable report provides a shareable impact summary in business terms, without requiring stakeholders to interpret raw ABAP object names.
* **Transport validation** — Teams verify that the transports in scope match what was expected — catching missing or unexpected transports before the test run starts.

***

### Detailed Functionality

#### The Four Metrics

<table><thead><tr><th width="200.55859375">Metric</th><th>What It Measures</th></tr></thead><tbody><tr><td><strong>App Areas</strong></td><td>SAP functional modules (e.g., Finance, Purchasing) containing at least one impacted executable</td></tr><tr><td><strong>Impacted Executables</strong></td><td>All executables that depend on at least one changed object in the cycle's transports</td></tr><tr><td><strong>Untested Changes</strong></td><td>Total ABAP objects modified across all transports in scope, and not tested yet</td></tr><tr><td><strong>Total Changes</strong></td><td>Total ABAP objects modified across all transports in scope</td></tr></tbody></table>

The relationship between these numbers tells the real story. A high Impacted count with a low Most-At-Risk count means changes are broad but concentrated in lower-risk areas. A high Most-At-Risk count signals that changes landed in high-stakes executables and warrants careful attention.

#### How the Analysis Is Built

The tab is produced entirely through structural analysis — no execution history is needed:

1. SeaLights reads the list of changed ABAP objects from the cycle's transports via SAP metadata tables (no source code accessed)
2. Changed objects are mapped to the production-active executables that depend on them
3. Those executables are ranked by the five risk heuristics to identify the most-at-risk set

This runs automatically within minutes of cycle creation.

#### Downloading the Analysis

The full export includes impacted executables, their risk rankings, the changed objects they depend on, and the app areas they belong to. It is formatted for sharing with stakeholders who do not have SeaLights access, and for archiving independently of the platform.

***

### FAQ

**Q: The Most-At-Risk count is much lower than Impacted Executables. Is something missing?** A: No — this is expected. The Most-At-Risk set is a curated subset filtered by the risk heuristics. Many impacted executables are deprioritized because they are low-usage, functionally unrelated to the change, or have long dependency paths to the changed object.

**Q: The Changed Objects count is higher than expected. Why?** A: Transport packages — particularly support packs and third-party add-on upgrades — often contain more objects than their label suggests. The count reflects everything the transport touched, not only custom Z-objects.

**Q: Does the analysis update if new transports are imported after the cycle is created?** A: No. The transport scope is fixed at cycle creation. To include new transports, create a new cycle using Carry Over.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/knowledge-base/sealights-for-abap/test-cycles/reviewing-change-analysis-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.