Reset to Head

An SAP system that supports development may store different versions of the same object. Changes on a development system are normally migrated to QA and Production. However sometimes, changes made on the development system are not migrated to Production - Projects may be abandoned, experimental code may be forgotten, and so on.

The Reset to Head workflow identifies the specific version of a custom object on a Development system (DEV) that matches the active version of the object on a Production system (PRD). With this information, the developer can activate that specific version on DEV, synchronizing DEV with PRD.

The workflow expands container objects (for example, Function Groups) so that their component objects may be analyzed.

Note that the purpose of the Reset to Head workflow is to identify object versions to be synchronized. It is up to the developer to actually change the active version of objects on the Development system.

The Reset to Head workflow provided with RFC Destinations for the Development and Production systems, and a set of custom objects to analyze. The workflow performs the following tasks:

  • It finds the most recent change to each input object by examining the transport history on the Production system. Assuming that objects are updated on the Production system by transporting them from the Development system, the last transport that changed each input object on the production system defines its current state.

  • It examines the transport history data on the Development system to identify active versions of the transported objects.

  • It identifies inactive versions of the input objects on the Development system. These are objects that are currently under development, and that have not yet been released to Production.

The workflow’s results are stored in a Excel report.

Creating RFC Destinations

Before you begin, you will need to create RFC Destinations for your Development and Production SAP systems.

Preparing the Workflow

To prepare the Reset to Head workflow, drag its workflow template from the Templates folder into your own workspace, and modify the workflow as follows:

To specify the Development and Production systems:

  1. Select the DEV parameter and choose ‘Edit RFC Destination’ from its context menu to display the RFC Destination dialog.

  2. Select the RFC Destination for the first system to compare, then click ‘Save’.

Repeat the above steps to link the PRD parameter to the RFC Destination for the Production system.

To specify the custom objects to analyze on the Development system:

  1. Select the Objects parameter and choose ‘Edit Table’ from its context menu to display the Table Editor dialog.

  2. Complete the following columns, then click ‘Save’.

Column Description
TYPE The type of the object to compare.
NAME The name of the object to compare.

Alternatively, a set of objects may be pasted into the Table Editor from an Excel spreadsheet.

Running the Workflow

To run the Reset to Head workflow, click the 'Run' toolbar button, choose ‘Run Now’ from the diagram’s context menu, or press F5. The currently running workflow action is marked with an animated display. When the workflow execution has completed, select the Report URL dataset and choose ‘View Details’ from the context menu to access the generated report.

Excel Report

Column Description
TYPE LiveCompare object type
NAME LiveCompare object name.
VERSNO The version number of the object on the Development system that corresponds to the active version of the object on the Production system.
TRANSPORT The ID of the transport on the Production system that includes the active version of the object.
OBJTYPE The object type listed in the version table (VSRD) on the Development system.
OBJNAME The object name listed in the version table (VSRD) on the Development system.