Skip to Content
author's profile photo Former Member
Former Member

Migrating Transfer rules using Conversion of Source System Name

Hi Experts,

I have BW DEV system linked to R/3 DEV system.

Recently, new client copy was taken place from existing R/3 DEV and I need to link BW DEV to this new R/3 Source system (Same R/3 but with new client number).

Instead of re-creating Transfer Rules again, I tried to use Transport Connection with conversion of source system. (Transport it back to BW DEV with replaced source system).

However, I am getting error message as below during the transport.

"R3TRISMP2LIS_03_BF original object cannot be replaced"

Does anyone know how to avoid such error?

Thank you,



Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Oct 10, 2005 at 12:11 PM

    Hi Steven,

    You don't need to transport the infosources this is a 1 -> N relation on sourcesystems. So your only (original) infosource get's overwritten by your transport. Just the transferstructures, transferrules and infopackages need to be transported.

    The most convenient way to do this is go to the transportconnection, and in grouping choose "save for system copy" then drag your original DEV sourcesystem into the collection window. Generate the transport and maintain the source system conversion for transport as you already mentioned.

    Kind regards, Patrick Rieken.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 11, 2005 at 05:41 AM


    Go through this oss notes

    Client transport: TW103 for R3TR CNTD TKO01:<b>94697</b>,

    R3TRFUGXX ... original object must not be replaced:<b>146458</b>

    Error:'Original object' in cross-client transport:<b>165528</b>



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.