Without any doubt: your fault it is... and not only because obviously you didn't pay enough attention to objects' dependencies when you released your transport requests, but mainly because you didn't take 3 seconds to start transaction SE38 and run report ZCEX_TRDA_START to let the system check those dependencies for you.
Remark: if you do not find this report in your system, that's probably because you missed this blog post:
How-to check dependencies between transport requests
What's new with code exchange project "TRDA - Transport request dependencies analyzer" then?
First of all, the first versions had been developed on SAP Netweaver 7.02 Developer edition which made its use limited to the happy few customers running one of the last versions of SAP Netweaver... Well, I believe this period is over as it has now been backported to SAP NetWeaver 7.0 Trial version:
- Two missing classes have been copied from 702 into customer namespace.
- Some statements have been adapted: for example every "&&" character has been replaced by the corresponding "CONCATENATE" statement.
- ABAP Unit tests have been reviewed.
- Etc.
Speaking of which, those ABAP Unit tests have been enhanced to make sure TRDA finds the following dependencies:
| Predecessor | Follower |
|---|---|
| Domain | Data element based on Domain |
| Data element | Structure with one component based on Data element |
| Structure | Table type based on Structure |
| Table type | Function group with one function module using Table type as importing parameter |
| Function group | Class implementing a method where a function module from Function group is called |
| Interface | Class implementing Interface |
| Class | Program using objects of type Class |
| Enhancement spot | Function module where Enhancement spot is implemented |
| Enhancement spot | Enhancement spot implementation of Enhancement spot |
| Function module | Enhancement spot implementation in Function module |
| Enhancement spot implementation | Composite enhancement implementation containing Enhancement spot implementation |
| Database table | Enqueue object for Database table |
| Database table | Search help based on Database table |
| Database table | Maintenance view for Database table |
| Search help | Database table where one component is using Search help |
| Table maintenance view | Generated function group for Table maintenance view |
But that's not the only new feature you'll find on TRDA Code exchange project page: this program can now be installed very easily via SAPlink too (provided you follow the corresponding How-to guide available). Note however that this version released as a nugget file doesn't include any ABAP Unit test class to simplify the installation process (but of course all ABAP Unit tests have been passed before creating the nugget).
And even more new features can be found in the Release notes document:
- Parameters to influence the scope of the dependency analysis.
- Ability to check dependencies that have been added manually in transport request attributes.
- New columns to display transport request status in TMS queues.
- Ability to exclude successfully imported request.
- Ability to start dependency analysis in background.
- Etc.
So if you're interested do not hesitate to join the project and give it a try: even if SAP is working on a similar program at the moment, we don't know yet when it's released, and for which SAP Netweaver versions it will be delivered... hence TRDA may still have some fine days ahead of it!