‎2013 Aug 14 8:10 AM
I am working on a tool for Version Management. I made a function module via RFC that searches for object names with their types in different boxes by accessing the tables such as VRSD, E071, E070, E070A, etc.. One object name I found is that it exist in the production box's VRSD but in the other box (test box's VRSD table), the object name is not existing. Checking manually in SE37 because the object is a FUNC type, the object exists physically and I wonder why it is not in VRSD or any version management tables. Do you have any idea where else can I look for the object names but I need to return the information that looks like the structure of VRSD. Or how does table VRSD or any version management table get updated?
Thanks in advance!
‎2013 Aug 14 12:50 PM
‎2013 Aug 14 12:56 PM
Hello,
You only have the correct versions of your objects on your development system because for most objects the versions are not transported.
That's why you miss most of the versions in the VRSD table on systems different from your development environment.
This is also explained in SAP Note :
Note 130906 - How can versions be transported?
Table TADIR contains all your repository objects, this table is always updated when you perform a transport.
When you need more details for a specific object afterwards you need to query more tables.
Example TRDIR contains more details like change date for all your ABAP programs.
More info for other repository objects like data elements, tables, ... can be found in the DD* tables (DD02L, DD01L, DD03l, ...).
Regards.
Wim
‎2013 Aug 15 10:39 PM
Hello Allan,
Can you brief on the purpose of your tool when you say "Version management" ?.
You can use the function 'SVRS_GET_VERSION_DIRECTORY_46' by passing the appropriate logical destination and object type and objectname .
It will give you the VRSN and VRSD tables.
*" LVERSNO_LIST STRUCTURE VRSN
*" VERSION_LIST STRUCTURE VRSD
Depending on the settings of your Q and Prod boxes, you may not have any versions in version database ( VRSD ). But you still will have a 0000 version ( The Active version ) as at least one entry in the VERSION_LIST itab.
We have already developed a smartVersion Comparison for one our products which does automatic version comparison across landscape and provides alerts to the developer while they are going to change the code at critical contexts.
Please note that unless you want to track transports, for just versions the E070 and family need not be referred.
So you may contact me for any help.
Regards
Kesari Katakam