Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Conversion R3TR PROG in LIMU REPS & LIMU REPT

Former Member
0 Kudos

Hi to all,

I've a problem.. I'have to make a remote comparison during the release of a cr of an object (table, program, function and any other objects) beetween my development and production system.

I've found the function SVRS_GET_VERSION_REMOTE and I run it on my destination system and the function SVRS_GET_VERSION_LOCAL for my origin system, but I've a problem for all the objects that change object name if you transport the entire object or a part of it (for example the program that if I transport the full program, the entry of my cr is R3TR PROG XXX, or if you transport only the code, the entry is LIMU REPS XXX.. and there is many of this kind of object.. FUGR>FUNC or TABL>TABD)

Is there a function that when I enter for example R3TR PROGR give me the 2 entries LIMU REPS and LIMU REPT??

I've found the TR_CHECK_TYPE function but is the contrary function that one I need.

Best Regards.

Paolo

Edited by: Paolo Castello on Dec 4, 2008 10:18 AM

5 REPLIES 5

Former Member
0 Kudos

Try function WB_TREE_CONVERT_OBJECTNAME with WB_TREE_RETURN_OBJECT_LIST

Former Member
0 Kudos

Hi Paolo,

I also needed this functionality when building the application for recovery of version management database after it was corrupted during upgrade. I was very lucky finding this blog (big thanks go to Sandra Rossi):

http://wiki.sdn.sap.com/wiki/display/ABAP/ABAP+program+to+perform+environment+analysis

If you dig into the code in the blog, you realize that the following function module does the miracle:

CALL FUNCTION 'TRINT_RESOLVE_OBJ'

            EXPORTING

              is_e071             = ls_e071

            TABLES

              et_vrso             = lt_vrso_source

            EXCEPTIONS

              not_versionable     = 1

              communication_error = 2

              OTHERS              = 3.

And there is one very interesting thing - even though it was changed in 2011/05 last time, it's not used anywhere in the system. So, it's called dynamically or not at all. Still - it works as expected.

Please, elaborate the blog for further details about necessary types and data declarations - it's all in there.

BR

Michal

0 Kudos

Hi,

It seems that function module TRINT_RESOLVE_OBJ has been deleted in 740, but it only calls function module SVRS_RESOLVE_E071_OBJ which looks like it will do the same trick.

0 Kudos

for the opposite direction, LIMU to R3TR see

(use function module GET_R3TR_OBJECT_FROM_LIMU_OBJ)

vonglan
Active Participant
0 Kudos

function SVRS_RESOLVE_E071_OBJ looks promising as well