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

what sequence to be followed to move tranport req's from r/3 dev-> quality

Hi all

we are having our landscape as

r/3 dev -> bi dev

r/3 quality -> bi dev

r/3 prod -> bi prod

we are now in development and moving all our transport requests from r/3 dev -> r/3 quality. and our r/3 quality will be connected to bi dev.

we have to make a list of transport requests in a sequence taking care of all the dependencies.

Can anyone please explain what all things have to be taken care when making a list of our transport requests from r/3 dev to r/3 quality.

for example : Like we have many enhancements that are done to the standard datasources.

suppose we have list of transport requests like this what should be the order of preference.

1. request1-datasource activation.

2. request2- new append structure

3. request3-changes to extract structure (adding them from the pool into lbwe)

4. request4-new data element created for within the above append structure.

5. request5 - cmod code for transaction data zxrsau01 program

6. request6- cmod code for master data zxrsau02 program.

we have seen issues like we found some appended fields missing in quality system after transporting.

please help me with the sequence in which transport requests ( r/3 datasources )have to be transported from r/3 dev to r/3 quality

thanks

Krishna

Edited by: krishnav3.5 on Sep 2, 2011 10:56 PM

Add a comment
10|10000 characters needed characters exceeded

Related questions

6 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 03, 2011 at 05:21 AM

    Hi,

    The sequence given by Gaurav is perfectly fine. You can follow the same. As your dictionary elements should go first then code changes can go in the end.

    Regards,

    Durgesh.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 03, 2011 at 05:26 AM

    Hi,

    Sequence is fine just remeber all structural changes in one TR, then activation in one TR and then Code changes in one TR.

    Thanks,

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 02, 2011 at 05:44 PM

    I guess you need to send requests in following format;

    request4-new data element created for within the above append structure

    request2- new append structure

    request3-changes to extract structure (adding them from the pool into lbwe)

    request1-datasource activation.

    request5 - cmod code for transaction data zxrsau01 program

    request6- cmod code for master data zxrsau02 program.

    Logically structure chagnes should go first like data elmement, append structure etc

    Activation TRs can be sent after that.

    Once structure is ready, code changes can be sent after that.

    Another way to make sure that we do not do anything wrong, send the TRs in order they were created.

    If case, same objects have been transported mulitple times or new TRs have been created and we have a doubt about what should be sent first, if there is not a big list of changes, multiple TRs can be clubbed together. e.g. all structural changes in one TR, then activation in one TR and then Code changes in one TR.

    I hope it helps.

    Regards,

    Gaurav

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 05, 2011 at 02:08 PM

    thanks all

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      one last question

      when transporting requests related to generic datasources from dev to quality or dev to pro what should be the order of transports.

      is it the same order as for standard datasources?

      we have following requests related to our generic datasource

      request1: data element used in append structure

      request2: request for append structure

      request3 : data source activation.

      What is happening is like when we are following the above order we see that in our datasource all the appended fields are hidden (hide tick).

      so we have followed the order

      request1

      request 3

      request 2

      request3 again.

      Can any one explain if this is that right order . becoz now we see all the append structure fields hide-untick but

      importing request 3 twice seems something odd. can anyone explain why this is happening

      regards

  • author's profile photo Former Member
    Former Member
    Posted on Sep 07, 2011 at 06:58 AM

    one last question related

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Krishna,

      Transport sequence is same for standard and generic data sources.

      before activating your generic data source which is enhanced with append structure.

      make sure you have unchecked the check boxes in Hide column(which is in maintenance mode of data source)

      then activate the data source and move the same into further system with the sequence mentioned in first(1,2 and3)

      It will get successful( i mean your fields will not be in hidden)

      Regards,

      Venkatesh

  • author's profile photo Former Member
    Former Member
    Posted on Feb 06, 2012 at 11:27 AM

    1 2 3

    thanks

    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.