Transporting BW Objects
In most cases, SAP Business Warehouse (BW) development projects are not carried out in a productive system, rather in one or more development systems, depending on their scope.
If you carry out your development projects in one development system, you have to transport the development to a target system (a test or productive system).
To do this, the standard transport system has been enhanced in BW to provide the BW transport connection. Using the transport connection in your BW development system, you can collect a consistent amount of new or changed BW objects and then transport them using the Change and Transport Organizer (CTO).
In the Data Warehousing Workbench, choose the Transport Connection functional area (transaction RSOR) by choosing the pushbutton in the left navigation window or by choosing the menu option
Goto 
Transport Connection 
.
NoteYou can display or hide the left navigation window of the Data Warehousing Workbench using
.
Collect objects that you want to transport and check the settings.
More information: Collecting Objects
Objects Being Transported for the First Time (Package $TMP)
Select
to transport the selected objects. The Change Object Directory Entry dialog box appears.
Under Attributes, in the Package field, enter a transportable customer package (beginning with Y or Z).
NoteThis box only pops up once for all collected objects. If you want to transport objects in different packages, you must collect the objects more than once. You can subsequently change the assignment for a package.
More information: Changing Package Assignments
Save your entries. A dialog box appears asking for a transport request.
In the Request field, create a transportable request, or first create a new request.
Choose
.
NoteThe system displays the corresponding information for individual objects in the Collected Objects screen area, in the following columns:
Last Changed
Last Changed By
Transport request
Transport Request Holder
Package
In the log display in the lower screen area of Collected Objects, check the status of the transport.
Select
: Overview. The Workbench Organizer: Requests screen appears.
First release the individual tasks and then the complete request.
The system checks the task or the request for inconsistencies. You can find additional information under Consistency Check when Releasing Transports.
If an error occurs, the check log is displayed in a dialog box. You have the following options:
To cancel the release of the task or request, choose
.
To continue with the release of the task or request, choose
. Confirm the prompt that appears to release the task or request. The check log is saved in the application log under RSO_REPOSITORY and subobject BEFORE_EXPORT.
CautionEnsure that you release any requests beforehand that contain dependent objects of the current request.
Objects That Have Already Been Transported Once
From this point on, BW objects are subject to automatic change display since they were assigned to a transportable package when transported for the first time. This means that all changed objects are written automatically to a request, and can be transported.
Note the following for the automatic change display: When you create new InfoObjects for an InfoCube that is subject to the automatic change display, these are not automatically written to the InfoCube request. Instead, they receive the $TMP. You must use the the BW transport connection to collect and transport these objects or the InfoCube.
Only refrain from collecting objects using the BW Transport Connection when such changes do not produce any new objects.
The transported objects, regardless of the object type in the A, M or T version, are imported to the target system and automatically activated using the after import method RS_AFTER_IMPORT. After importing, the dependent DDIC or program- objects are generated in the target system. If the deletion of objects has been transported, the corresponding objects are deleted in the target system.
By implementing the Business Add-Ins (BAdI) RSO_BADI_TRANSPORT, you can automatically trigger subsequent activities such as the execution or rescheduling of process chains after objects have been imported. Here, the method AFTER_IMPORT of the interface IF_EX_RSO_TRANSPORT is executed after the standard BW after-import methods are finished. For more information, see Implementation of BAdls in the Enhancement Builder and in the method documentation for IF_EX_RSO_TRANSPORT AFTER_IMPORT.
More information:
Technology of the SAP Change and Transport System (CTS):
Transport Landscape in BW