I want to be able to transport all transportable objects related to a package, taking account of versions in table VRSD, but I have hit a snag:
1) Table TADIR allows you to list objects contained in a package by searching on DEVCLASS (Paskage name).
2) However, this does not reveal the objects that will actually appear in a transport request in VRSD.
For instance, in TADIR there will be an entry for a class such as PGMID = 'R3TR', OBJECT = 'CLAS' and OBJ_NAME = class name. However, in the transport request will appear objects such as OBJTYPE = 'CPUB', OBJNAME = class name
So although I can find object type 'CLAS' in TADIR, the actual objects transported are of different types.
I had a look at transaction SOTG, which shows the relationship between the object type groups and dependent types, but there are a couple of problems with this, namely, the object can appear in multiple groups (e.g. CLAS appears in groups OO_TYPE, SOURCE_BASED and several others; CPUB appears in OO_SECTIONS, which is a subgroup of OO_TYPE, but the relationshp is not direct, and no way to tell what sub-objects belong in a transport.
Does anybody know, is there a way to determine for each type in TADIR, what objects will appear in the transport and table VRSD?