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

Transport.

Posted on Jan 25, 2005 at 04:26 AM 9 Views

Hi,

Is there any difference between R/3 transports & BW

transport. Give me details.

Regards,

Ravi Chelikani.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 25, 2005 at 08:40 AM
    0

    Hi

    The basic transport framework is the same. However You often have release scenarios involving Data Source development. In this situation, You need to coordinate Your BW transports with R/3 transports (transport R/3 side, replicate data source and transport BW side). In addition to this You have the challenge of multiple source systems, which is handled in the system mapping. So when performing transports of Info Sources You should consider which pair (BW-R/3) is the target for the transport.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 25, 2005 at 09:49 AM
    0

    BW transports tend to have many objects in them. So if many people are working in the same area it is easy to lock eachother (not be able to complete the transport until someone else is ready with their bit).

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Gianfranco Vallese
    Gianfranco Vallese
    Posted on Jan 25, 2005 at 04:44 PM
    0

    In the Pilot section you can find very usefull and complete presentation about Transports in BW (SAP BW and Transports) written by ASUG.

    Best regards

    GFV

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member
      Jan 26, 2005 at 02:34 PM

      The biggest differences between BW and R/3 are three main topics:

      1. Objects in BW are most often created in package $TMP. So whenever you create a new InfoSource, InfoObject etc. you are not asked for a transport request. This may lead to inconsistencies during transport. So expect some more error messages especially if different developers use the same objects. These errors are easily solved when you transport the missing objects.

      2. Standard BEx request.

      All changes on queries that you once transported are always collected in one big transport request, the standard BEx request. It depends on your organization if you want to transport this one request regularly or if you want to release it, delete it and transport the queries on itself. I'd suggest variant 1 for small organizations with few people working on the queries, 2 for huge BW teams.

      3. Mapping of Source system names.

      Different objects need to be changed on transport. E.g. if you have transfer rules from your development system you want to load the data from your prod system after transporting the rules to your P system. So you can change the source system after transport.

      Best regards

      Dirk

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.