Remote System Transport Request Tracking Tool
Introduction:
In the SAP, Version of a particular object can be found individually using the path as follows: UTTLITIES-VERSION-VERSION MANAGEMENT as seen below:
But in standard SAP there is no provision for checking different versions of different systems such as Development, Quality, and Production under a particular package. Some times for a particular project it is very difficult to check the individual object one by one and listed down the request numbers in excel. So in that case if there is a Utility Program which can resolve this problem and save a lot of manual effort.
Run the transaction Code , it will display the following screen:
This type of Utility program is very effective as this will give a complete control of the project. So this type of program will help for the developer as well as the Auditor.
The Utility program will display Package Name , Object Name , Object Type , Object Type Description , Development transport request number , Quality transport request number and production transport request number in the ALV layout format.
Analysis on different important function module, Database tables, Standard Programs:
Important Function Modules Used in the development:
TR_OBJECT_TABLE – To get the Object type texts SVRS_GET_VERSION_DIRECTORY_46 - To get the remote system request numbers
Important Database tables Used in this development:
TADIR – This database contains the Object name against package and first created object type E071 – This table contains all the request numbers against object. VRSD – This table contains all the released request numbers (Having Object Name Primary Key) E070 – Request number description is stored in the table
Logic for the Version Management Utility program:
Selection Screen of the Utility Program:
In the selection screen of the Utility program there will be Package name and program name and package name will be mandatory.
Package Name Can be like YSD, YMM etc. The object will be whatever is available in that package.
Selection the objects from the TADIR table:
Base on the selection condition (Package, Program name) objects will be selected from the TADIR table.
Selection the object type from the VRSD table:
After getting the full listed objects from the previous steps, passing to the VRSD table, object type of the respective object can be found. This table contains all released transport requests under an object.
For object which is just created in the development and not released, development request number will be selected from the E071 table.
Basically latest object type will be selected from the VRSD table.
Getting the Object type description:
Object type description can be found using the function module TR_OBJECT_TABLE.
Getting request numbers for Development, Quality and Production systems:
Pass the Parameters Object name, Development RFC destinations, Object type of a particular object in the function module SVRS_GET_VERSION_DIRECTORY_46, fetch all the development transport requests. We need the request which is latest.
To fetch transport requests from Quality and Production the only change of the RFC Destination parameter is required.
Output of the tracking tool:
Output of the report will be ALV display which consists for the following fields:
Package Name Object Name, Object Type, Object Type Description, Development transport request number, Quality transport request number and production transport request number.
Test Scenario 1: Testing for inconsistent version (When the object is available all the systems)
Here the object YSD_UPDATE_FINAL does not have consistent version as seen below:
Manual Checking of Development version:
Manual Checking :Now comparing the version with quality: Object is consistent in Quality
Manual Checking: Now comparing with production:
As we can see there is the difference with Development Request and Production request. This means the object does not have a consistent version so for this in the report output
This record will be highlighted in Red:
Test Scenario 2: Testing for consistent version (When the object is available all the systems)
Manual Checking: Development Version
Manual Checking: Quality Version:
Manual Checking: Production Version:
Transport request number of the all the client is same, this means the object have a consistent version so for this in the report output is Green.
Interactive Action Connecting to standard screen on the each line:
After double clicking on the each line of the output, automatically version management will call from there cross check with the actual request number available in the different system can be done. To check the transport request number of the other system only system number need to give in the popup screen.
For above example: Double click on the Object name: Popup will come and asking for the system name:
After giving the system name, the program will display the respective requests in that particular system:
Conclusion:
This Tool will be very useful and effective as this can be reused in any project for controlling the customized object.