# Transport Validation and Analysis Reports

### **Validate**

Validating a transport ensures that the changes comply with enterprise standards, acting as an early warning system for developers.

### **How to Validate a Transport**

1. Navigate to the **Transport Management** screen.
2. Select the transport you want to validate.
3. Click **Validate** under the **Actions** menu.

<figure><img src="/files/rLpgAw1pNFU18YkCYLJ9" alt=""><figcaption></figcaption></figure>

4. A pop-up window will appear displaying the **Source** and **Target** systems.
5. Click on the **Target System** field to view the list of available systems.
6. Select the appropriate target system (for example, **DEQ** or **DEP**).
7. Once the target system is selected, the system performs the validation checks and displays the results, helping ensure that the transport meets all required compliance and configuration criteria before promotion.

<figure><img src="/files/I7rINiQm7tZu1yFN31ax" alt=""><figcaption></figcaption></figure>

### **Validation Report**

To view the validation report of a transport:

1. Select the required transport and click **Actions**.
2. Choose **Validation Report**.
3. The report is displayed.

<figure><img src="/files/t4n2V4MU0Du0ceuWBAcJ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/DraI1NbNZgecgasr5kWn" alt=""><figcaption></figcaption></figure>

| **Release Status check**                       | Checks whether the given transport is released or not.                                                                                                                                                                                                            |
| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Downgrade Protection check**                 | Identifies other transport requests with identical objects which have been released in the last 90 days, but have not yet been imported to the target system.                                                                                                     |
| **Cross Reference Check (Dependencies)**       | For all objects in the selected transport request, the referenced objects are identified by a where-used- analysis. If the referenced objects are not included in the transport requests, you compare their versions between the source and target system.        |
| **Cross Release Check (package level checks)** | If the current system and the target system are on different support package levels, this check identifies critical objects in the selected transport request, which belong to inconsistent software components and should not be imported into the target system |
| **Critical Object Check**                      | It will check if the objects in this transport are a part of the critical object list. If it is, then a warning pops up.                                                                                                                                          |

\
4\. Click **Details** under **Release Status Check** to view the status and message explaining the transport.

<figure><img src="/files/Bq4Qjt3cNFqbRZNILoiQ" alt=""><figcaption></figcaption></figure>

### Test Execution Report

The **Test Execution Report** provides insights into the number of tests executed, including:

* Count of **successful** and **failed** tests.
* Test name, object type, and URI.
* Status (**pass** or **fail**) along with relevant messages for debugging or analysis.

This report helps identify issues early and ensures code quality before deployment.

<figure><img src="/files/vYReg851qcOdC30E0yT0" alt=""><figcaption></figcaption></figure>

### Code Coverage

The **Code Coverage Report** summarizes overall code coverage, including:

* **Branch Coverage**
* **Procedure Coverage**
* **Statement Coverage**

It also provides details such as **Type, Object Name, Branch Coverage, Procedure Coverage, and Statement Coverage** for specific objects. This report helps assess test effectiveness and highlights areas for improvement to enhance software quality and reliability.

<figure><img src="/files/fxk6wlwcuYKM7nm0noyu" alt=""><figcaption></figcaption></figure>

### **ATC Report**&#x20;

The **ATC Report** offers a detailed analysis of **static code checks**, ensuring that ABAP programs comply with:

* **Coding standards**
* **Security guidelines**
* **Performance best practices**

Findings are categorized as **errors, warnings, and informational messages**, helping developers address potential issues effectively.

<figure><img src="/files/0z0vlXYZCepj1lyqgJJn" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://releaseowl.gitbook.io/releaseowl-docs/releaseowl-user-guide/sap-on-premise/transport-validation-and-analysis-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.