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
  • Retrofit Approaches
  • Enabling and Performing Transport Retrofit in ReleaseOwl
  • Steps to Enable Retrofit:
  • Performing Transport Retrofit
  1. ReleaseOwl User Guide
  2. Transport Management

Retrofit & Conflict Resolution

The retrofit process in ReleaseOwl ensures that changes made in the maintenance landscape are synchronized with the implementation landscape while preventing downgrades, overwrites, and conflicts. It supports both automated and manual retrofitting mechanisms to handle various object types and development workflows.

Retrofit Approaches

Retrofitting in ReleaseOwl can be performed in two ways:

Automated Retrofit via Pipelines

ReleaseOwl offers an automated retrofit task as part of the release pipeline. This ensures that whenever changes are moved to Quality (QA) or Production (PRD), they are automatically retrofitted back to the implementation landscape.

The retrofit task:

  • Checks for conflicts

  • Ensures that only non-conflicting changes are moved forward automatically

Manual Retrofit via the Retrofit Screen

In cases where a transport request (TR) is modified or delayed, it will appear on the Retrofit Screen in ReleaseOwl.

Users can manually trigger the retrofit process from this screen, which will:

  • Dynamically create a new transport request

  • Transfer changes from the maintenance landscape to the implementation landscape

This manual method gives users control over which TRs to retrofit and when, especially useful in cases requiring conflict resolution or selective movement.

Enabling and Performing Transport Retrofit in ReleaseOwl

You can enable the retrofit option in the Transport Domain Controller screen.

Note: In ReleaseOwl, transport retrofit can be performed for Customizing and Workbench transports that have already been released.

Steps to Enable Retrofit:

  1. Navigate to Transport Domain Controller from the Administration view.

  2. If the Transport Domain Controller is not yet registered, click Register Transport Domain Controller. Otherwise, you can edit the existing configuration.

  3. Enter the required details.

  1. Check the option Enable Retrofit (Source) to enable retrofit.

  2. Click Save to apply the changes.

  3. The following screen is displayed upon registering the Transport Domain Controller.

Performing Transport Retrofit

  1. Navigate to Transport Retrofit under the Build section.

  2. Select the transport you want to retrofit and click Retrofit.

  1. After completing the retrofit process, you can view details of the retrofit objects by clicking the arrow button. This will display information such as the program ID, object type, retrofit conflict status, and more.

Note:

  • If the Retrofit is successful, the Retrofit Status will be Completed.

  • If there is a conflict, the Retrofit Status will be Retrofit Conflict.

Steps to Resolve Conflicts:

  1. Click on the transport request with the Retrofit Conflict status.

  2. View the object that has a conflict.

  1. Click the error icon against the Retrofit Conflict Status to view error details.

  1. Rectify the error and click Resolve to resolve the conflict.

  1. Click OK—the Retrofit Conflict Status will change successfully.

  1. Click Continue Retrofit to proceed.

  1. The retrofit process completes successfully.

PreviousTransport of CopiesNextgCTS

Last updated 2 months ago