TRDA – Release notes
Important preliminary note
if you want the same kind of tool to be included in SAP standard delivery, you can vote for it on Idea Place:
Version 5.4: view cluster content is now supported
TRDA will identify dependencies for view cluster content (“CDAT” object). Meaning that the underlying views and corresponding tables will be searched for and the transport requests they belong to will be added to the computed sequence.
Also, a new method IS_OBJ_ENVI_VALID has been developed to avoid looking for dependent objects when it is not necessary (for example “MERG” objects, i.e. transport request comment, that do not have to be decomposed as they cannot result in return code 8 during import into a target system).
Version 5.3: abap unit tests and application log
Abap unit tests of class ZCL_TRDA_SEQUENCER have been included. If you run a unit test, the local test class will create every “sample” transport requests automatically, and check that TRDA finds every expected dependencies. Here is a screenshot of the transport requests that will be created:
However, if you start a unit test just after importing release 5.3 into your system, it is more likely that many tests will fail:
This is due to the fact that the navigation index is not updated immediately after import. So you’ll have to start program SAPRSEUT first, and wait until it is completed.
In this release a small bug was also fixed regarding version dependencies, and some information are stored in the application log for object “ZCEX_TRDA”:
Version 5.2: user parameters on selection screen
Three new parameters have been added to the selection screen of program ZCEX_TRDA_START_MAIN, in order to offer the possibility to overwrite values stored in the connected user master data:
Also, the logic to read transport request statuses that are displayed in the ALV tree has been completely reviewed to take into account the case where the requests are not left in the TMS queue after import. As of version 5.2, statuses are extracted from the corresponding transport request log.
Last but not least, the way objects are filtered depending on their namespace has been improved too. The system will now correctly interpret program names beginning with Z* or Y* as customer objects for example (if namespace /0CUST/*, which is the one set by default, is used). The same with program includes, or customer includes, that were not correctly processed before released 5.2, because of their names not starting with Z*.
Version 5.1: start sequencer in background
In case a very high number of transport requests need to be analyzed, you may want to start TRDA in background. This is now possible via the “Start sequence in background” button available on the selection screen:
When this button is clicked, the usual popups will be displayed to schedule the job. Once the job is completed, you can display the corresponding spool via SM37 to check the dependencies that were found.
Version 5.0: exclusion functionality
This may be useful in case you set user parameter ZCEX_TRDA_ALL_TR to ‘X’.
Indeed when this parameter is set, TRDA will analyze every request found, even released ones… but this may be very time consuming when a lot of transport requests are found. So you might want to exclude from analysis some transport requests that were already successfully imported to one given system: this is what the “skip_ok” flag from table ZCEX_TRDA_TRGSYS is for:
Version 4.4: transport request status
Three additional columns have been added to the result tree:
Those columns are intended to give the status of the corresponding transport request in the TMS queue.
Meaning of icons:
1) Red Cross: request was not found in the queue.
2) Gray/Green/Yellow and Red led : status of the request from STMS.
3) Empty : system is unknown.
For those icons to be displayed, each column needs to be mapped to a system ID in table ZCEX_TRDA_TRGSYS:
In the picture above you can see that TRN column will display status of system called VIR.
You can find this system ID on the screen that appears when pressing F5 after you start tcode STMS:
Older versions: basic functionalities
Kindly check the following blog post on SDN that describes most of the functionalities of the transport requests dependencies analyzer: How-to check dependencies between transport requests