Trasporting Variants

[Former Member]

Hi,

I 'm trying to transport variants that are already created from one system to other , all the SAP defined variants are getting transported but not the Z program variant.But it can be seen in the destination's Trasport Organizer as released , when i check in editor it is not showing any variants.

Could anyone help.

<b></b>

[Former Member]

Hi

Customer variants that have a name starting with

CUS& can be transported. Other custom variants cannot be transported . You can also try report RSTRANSP to create transports for variants.

You have not mentioned how are you transporting Z program variants . Variants are client dependant so the client in which you are importing will also matter, Check the log of transport and it will give you the info in which client the variants are imported. Check the program variants in this client .

Cheers

Message was edited by: Sanjay Sinha

[Former Member]

Hi Sanjay,

Thanks , i'll try that.

In the source system in SE38 i entered the program name (that contains the variant to be transported) and selected variant radiobutton - In the Variant screen i selected Utilities -> Trasport Request - In the selection screen i entered the variant name to be transported .

[Former Member]

Hi Krithika ,

I guess you are doing it right way . Reporst RSTRANSP does the same . Just check the client in which your transport was imported or if there is any error in the transport log in SE01 or whether it has moved to the target system at all . If no errors the variants should be there in the client.

Cheers.

[Former Member]

Hi Sanjay,

I checked the log message in the destination system it shows error meessages for every z programm names :

R3TRPROG"z program name" ORIGINAL OBJECT CANNOT BE REPLACED.

If i get help for the error msg it's showing

" try to import with unconditional mode2"

[Former Member]

Hi Krithica,

It seems that you are trying to port programs as well with the same transport and the programs already exist in the target system.

Normally this happens if the target system is not in your system landscape. Usually a system landscape is DEV->TST->PRD which is configured in TMS. You can move objects from DEV to TST to PRD and transports will not fail. This happens as the "Orig Sys" for an object ( directory entry ) will be same throughout the landscape but outside the landscape it will be different. For SAP objects orig system is "SAP" in all system and hence no problem .

You can ask your BASIS person to import the request into target system using command "tp" in a forced mode or give more details .

How did you transport ?? . I mean how was the transport moved to target system?? Is the target system already in your landscape ?? Please clarify more on how the target system was build and how the programs were ported / created on this .

Cheers