When working on changes to a report, table, class or any transportable object in SAP, it has often been found that some objects are not transported correctly or they are just stuck in quality system which the developer / basis forgot to release. This may not always cause a problem in production environment but can create a confusion. It also doesn't look neat if some transports are forgotten and gives the customer an impression of the inefficiency of the technical team.
To circumvent the issue I had once created a report in development system to help us view the transport logs of existing changes in an easier way. Generally we have to go to SE10, click on transports of each object or go to version history and check the logs. This report does all of this and displays the result in a tabular form.
Given below are the steps to follow on how to check for transport logs.
* Suppose we want to check the version history and the corresponding transport logs for the INCLUDE report ZXVEDU03. We go to SE38 and execute the report ZTRANSLOG.
* In the selection screen we provide the object name and select Report and Report texts radio button.
* After executing the report we will get a tabular display of the transport numbers associated with the version history (latest on top). Before starting development on an object we must make sure that other developers are not working on them concurrently. In case there is, we will find the object released from CMD(development) in the topmost log entry. It may or may not have reached quality, but if it has not reached production it could cause an issue if case we decide to continue with our development ignoring dependency.
In case you want to use the same report or just take it on a test run make sure to maintain the ALV fieldcatalog in the report correctly. It has been provided in the attachment.
For this you need to adjust the internal table i_alv, modify the calls the the form to_light and also adjust the form build_fieldcat.
For example, in my scenario, i had a development system CMD and a test system CSG. The east chain is CTC -> CAC ->C0C and west chain is CT5 -> CA5 -> C05 in development -> quality -> production manner. The green lights indicate that the transport have reached successfully in that system, yellow indicates transportation with warning and red is an error. A blank indicates that it has not been transported to the system.
If you want to build this kind of report from scratch, just to give you a lead, you might take a look into the functionality of the two function modules:
1. TR_OBJECT_TABLE
2. SVRS_GET_VERSION_DIRECTORY_46
These 2 function modules are the heart of the development.