Reverse Transport Mechanism in SAP BI
SAP COMMUNITY NETWORK SDN -
- boc.sap.com |
- uac.sap.com © 2011 SAP AG 3
This document helps you to understand the detailed step by step procedure in implementingthe Reverse Transport. It also includes different scenarios where we can implement a ReverseTransport and the advantages and disadvantages of implementing.
Reverse Transport is generally not advisable as there is a risk that some of the objects might get overwritten. Butin some rare situations we can go for this provided care must be taken so that no changes are overwritten.
In some cases Users will create adhoc queries directly in Production system for testingpurpose. In order to save some development effort, rather than re-creating of these queries indevelopment, we can implement Reverse Transport mechanism for these queries fromProduction to Development.
In some cases where the client is having multiple landscape for development and qualityusually, client copy will be done periodically i.e., development /quality systems will be synchedwith Production system. Let
assume that development system is synched with Productionsystem and there were some changes done in Development and they were overwritten by thesync, then if those changes were already transported to Quality, we can Reverse Transportthose changes from Quality system to Development system or we can do reversal of transportinstead of doing the changes manually.
In the case of adhoc queries created in Production, instead of recreating the queries inDevelopment, we can do reverse Transport them and this reduces the effort and time incase of complex queries.
If some changes were overwritten by sync up, we can get back the changes throughReverse Transport.
Reverse transport is not advisable as some changes already done in Development mightbe overwritten, if extra cautious not taken.