Reverse Transport Mechanism in SAP BI

Reverse Transport Mechanism in SAP BI
Applies to:
SAP Net Weaver 2004s BI 7.0 Ehp1 SP 08. For more information, visit the EDW homepage
Summary
This document helps you to understand the detailed step by step procedure in implementing the Reverse Transport from production system to development system. Author: Surendra Kumar Yadla
Company: Infosys Limited Created on: 21 September 2011
Author Bio
The author has been associated with Infosys Limited, for 3 years with around 6 years experience in SAP BI. He has been involved in an end-to-end implementation of SAP BI 7.0 and upgrade of support pack for a renowned client
SAP COMMUNITY NETWORK 2011 SAP AG
SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 1
Table of Contents
Introduction ......................................................................................................................................................... 3 Scenario 1: ...................................................................................................................................................... 3 Scenario 2: ...................................................................................................................................................... 3 Advantages: ........................................................................................................................................................ 3 Disadvantages: ................................................................................................................................................... 3 Step by step procedure for Reverse Transport: ................................................................................................. 4 Related Content ................................................................................................................................................ 11 Disclaimer and Liability Notice .......................................................................................................................... 12
Introduction
This document helps you to understand the detailed step by step procedure in implementing the Reverse Transport. It also includes different scenarios where we can implement a Reverse Transport and the advantages and disadvantages of implementing.
Note: Reverse Transport is generally not advisable as there is a risk that some of the objects might get overwritten. But in some rare situations we can go for this provided care must be taken so that no changes are overwritten.
Scenario 1: In some cases Users will create adhoc queries directly in Production system for testing purpose. In order to save some development effort, rather than re-creating of these queries in development, we can implement Reverse Transport mechanism for these queries from Production to Development. Scenario 2: In some cases where the client is having multiple landscape for development and quality usually, client copy will be done periodically i.e., development /quality systems will be synched with Production system. Lets assume that development system is synched with Production system and there were some changes done in Development and they were overwritten by the sync, then if those changes were already transported to Quality, we can Reverse Transport those changes from Quality system to Development system or we can do reversal of transport instead of doing the changes manually.
Advantages:
In the case of adhoc queries created in Production, instead of recreating the queries in Development, we can do reverse Transport them and this reduces the effort and time in case of complex queries. If some changes were overwritten by sync up, we can get back the changes through Reverse Transport.
Disadvantages:
Reverse transport is not advisable as some changes already done in Development might be overwritten, if extra cautious not taken.
Step by step procedure for Reverse Transport:

Consider a Y query which was created in Production system and it has to be Reverse transported to Development System: Go to Transaction SCC4 in Production System
Make the necessary settings in the source system for collecting transports. This will be done by the basis team. Before:
After:
Get the required authorizations for the particular User ID. A Package should already be present in the Production System to include the Y Query. If not create a package in Development and transport it to Production System. Steps to create a package: a) Go to Transaction SE80 -> Repository Browser: b) Select Package from the drop down list and then give the Package name which you want to create.
c) Click on the Display button. It will prompt to create object as shown below:
d) Click on Yes. The below screen will pop up:
e) Give the Description and Application Component and give Package Type as Not a Main Package. Then click on Create. f) It will prompt for a Transport Request. Include the Package in a new TR and save it as shown below:
g) Transport the Package to Production System.
Create a new Transport Request in the Production system and collect the Y query in that Transport Request and include it in the above created Package.
Release the Transport Request.
Go to Target system -> Import Queue and Import the Request as you normally do.
Validate the imported Objects by comparing with production system to verify if the objects have been transported properly or not. After completing the above step, revert the system changes to as before in SCC4. After importing the query to development system, change the technical name of the query as per the naming standard and transport to the production system by standard transport mechanism. Now delete the Y query created in both Production and Development Systems.
Related Content
http://help.sap.com http://www.sdn.sap.com http://www.bw-biexpertonline.com
Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Reverse Transport Mechanism in SAP BI

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Reverse Transport Mechanism in SAP BI

Caricato da

Copyright:

Formati disponibili

Reverse Transport Mechanism in SAP BI

Company: Infosys Limited Created on: 21 September 2011

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com 1