ReleaseOwl Docs
  • ReleaseOwl Admin Guide
    • General Administration
      • User & Role Management
      • Project Management
      • Landscape Registration
      • Global Credential Management
      • Settings
      • Landscape Connectors
      • Parallel Landscape Configuration
      • Static Code Analysis
      • RO Agents
    • ALM Integrations
      • Jira
        • Jira Cloud
        • Jira On-Premise
        • Jira Automation Rules
      • Azure DevOps
      • ServiceNow
      • Freshservice Integration
    • Other Integrations
      • ReleaseOwl Callout Feature
      • DocuSign
    • Landscape Mapping
  • ReleaseOwl User Guide
    • Change Management
      • Backlog
      • Sprints
      • User Stories
      • Release Versions
      • User Story Dependency
    • Transport Management
      • On-Prem Environment Registration
      • Creation of Transports
      • Transport Validation and Analysis Reports
      • Transport Promotion and Pipeline Activity
      • Transport Management Actions
      • Transport of Copies
      • Retrofit & Conflict Resolution
      • gCTS
        • Build pipeline support for onPrem Fiori
    • SAP BTP
      • Administration
        • Credential Management
        • Cloud Environment Registration
      • Working with Build Pipelines
        • Static Code Analysis
        • Change Log Analysis
        • Download Artifact
        • Labels
      • GIT Ops
    • SAP API
      • Adminstration
        • Credential Management
        • Cloud Environment Registration
      • API Management
    • SAP CPI
      • SAP CPI Integration with ReleaseOwl
      • CPI Test Generator
      • CPI Management
        • Synchronize CPI Artifacts
        • Artifact Versions
        • CPI Artifact Comparison
        • Backup & Rollback
        • CPI Validation - CPILint
        • iFlow Unit Testing
        • Integration Advisor
    • SAP Analytics Cloud
    • SAP Datasphere
    • Working with Release Packages
      • Create Release Package with User Stories
      • Create Release Package with Transports
      • Release Package Validation with Transports
    • Working with Release Pipelines
      • Pipeline Tasks
        • Approval Task
        • Callout Task
        • Manual Task
        • User Story Status Task
        • Test Execution Task
        • Message Listener Task
        • GCTS Merge Task
        • GCTS Activate Task
        • GCTS Switch Task
        • Import via Toc Task
        • Transport Retrofit Task
        • Release Transport Task
        • DocuSign Approval
        • Validation Task
      • Use Cases
        • Automated Transport import along with Transport Promotion
        • Automated MTAR Deployments
        • Automated CPI Deployments
    • Test Automation
      • HCL OneTest
        • Test Configurations
        • Running Automated Tests with Release Pipelines
      • Tosca Integration
      • Integrating UiPath with ReleaseOwl
    • My Tasks
    • Multiverse
    • Utilities
      • ABAP Version Compare
      • gCTS Merge
Powered by GitBook
On this page
  • Validate
  • How to Validate a Transport
  • Validation Report
  • Test Execution Report
  • Code Coverage
  • ATC Report
  1. ReleaseOwl User Guide
  2. Transport Management

Transport Validation and Analysis Reports

PreviousCreation of TransportsNextTransport Promotion and Pipeline Activity

Last updated 4 months ago

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. In the Transport Management screen, select a transport.

  2. Click Validate under Actions to trigger the validation process.

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.

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.

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.

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.

ATC Report

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.