BI Transport Connection: Transporting
Objects 
...
1. Call up the Data Warehousing Workbench. (To do this, on the SAP Easy Access screen, choose Modeling ® Data Warehousing Workbench: Modeling, for example.)
2. Choose the function area Transport Connection using the pushbutton in the left-hand navigation window or from the main menu of the Administrator Workbench by using Goto ® Transport Connection.
You can
display or hide the left navigation window of the Data Warehousing Workbench
using 
Navigation Window On/
Off.
The procedure
for steps 3 to 6 is very much the same as the procedure for installing
Business Content (steps 3-6). For more information, see 
Installing Business
Content .
3.
If you want to
assign source systems, choose 
Source System Assignment. The
Choose
Source System by Default? dialog box appears.
The assignment of a source system is relevant only for transfer rules, file DataSources, and InfoPackages.
4.
Choose a setting
using 
Grouping.
There is the additional option Save For System Copyin the Transport Connection function area.
We recommend you make this setting when a source system needs to be copied and renamed.
You can avoid having to re-create objects for both SAP systems and BI systems in the following way:
· Collect objects dependent on the source system in BI.
· Save these to a request.
· Export the request.
· Delete the objects and rename the source system. Maintain the mapping table so that the old system name Original Source System is changed to the new system as Target Source System. For more information about using mapping tables, see Transport System.
· Import the request, to which you saved the objects dependent on the source system.
5. Choose a setting with Collection Mode
6. Select how you want to display the objects in the left-hand navigation window.
For more information about object types, see Transport-Relevant Metadata Object Types.
In the middle of the screen, choose the object(s) you want to transfer and move it/them using Drag&Drop, or via Insert Objects For Collection in the context menu of the respective object, into the Collected Objects area on the right hand side.
7. Check the Transport column in the Collected Objects screen area. The following objects are indicated automatically;
· Those that have not been displayed, that is objects that still have the $TMP package.
·
Those that must be
transported according to your selection in Groupings.
Requests for which collected objects are locked must be released before transporting the current request. In the log display, the system uses warnings to show for which objects there are still requests that must be released. These requests are also displayed in the Transport Request column.
You can add other objects manually.
Objects Being Transported for the First Time (Package $TMP)
8.
Select 
Transport Objects in order to transport the selected objects. The
Change
Object Directory Entry
dialog box appears.
9. Under Attributes, in the Package field, enter a transportable customer package (beginning with Y or Z).
This 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. For more information, see Subsequently Changing Package Assignment.
10. Save your entries. A dialog box appears asking for a transport request.
11. In the Request field, create a transportable request, or first create a new request.
12.
Choose 
Continue.
13.
Select 
CTO Transport Organizer:
Overview. The Workbench Organizer: Requests screen appears.
14. First release the individual tasks and then the complete request.
Note: You need to previously release requests for which objects are blocked, as described in step 7.
The system displays the corresponding information for individual objects in the Collected Objects screen area, in the following columns:
· Last Changed on
· Last Changed by
· Transport Request
· Transport Request Holder
· Package
15. In the log display in the lower screen area of Collected Objects, check the status of the transport.
Objects That Have Already Been Transported Once
From this point on, BI 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.
Please note 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 package. You must use the BI Transport Connection object collector to collect and transport either these objects or the InfoCube.
Only refrain from collecting objects using the BW Transport Connection when such changes do not produce any new objects.
See also: