Transporting SAP BI 7.0 Objects

Use

Development projects for Business Intelligence (BI) are generally not performed in a productive system. They are normally carried out in one or more development systems depending on their scope.

If you carry out your development projects in a 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 BI to provide the BI transport connection. Using the transport connection in your BI development system, you can collect a consistent amount of new or changed BI objects and then transport them using the Change and Transport Organizer (CTO).

Procedure

...

1. 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.

You can display or hide the left navigation window in the Data Warehousing Workbench by choosing This graphic is explained in the accompanying text

This graphic is explained in the accompanying text

Navigation Window On/Off.

2. Collect objects that you want to transport and check the settings.

More information: Collecting Objects

Objects Being Transported for the First Time (Package $TMP)

3. To transport the selected objects, choose This graphic is explained in the accompanying text

Transport Objects. The Change Object Directory Entry dialog box appears.

4. Under Attributes, in the Package field, enter a transportable customer package (beginning with Y or Z).

This prompt only appears once for all collected objects. If you want to transport objects in different packages, you must collect the objects more than once.

You can change the package assignment subsequently.

More information: Changing Package Assignments

5. Save your entries. A dialog box appears where you are prompted for a transport request.

6. In the Request field, enter a transportable request or create a new request first.

7. Choose This graphic is explained in the accompanying text

Continue.

8. Choose This graphic is explained in the accompanying text

CTO Transport Organizer: Overview. The Workbench Organizer:Requests screen appears.

9. Release the individual tasks first and then the complete request.

Ensure that you release any requests with locked objects beforehand.

In the Collected Objects screen area, the system displays the corresponding information for individual objects in the following columns:

● Last Changed by

● Last changed by

● Transport Request

● Transport Request Holder

● Package

10. In the log display in the lower screen area of Collected Objects, check the status of the transport.

Objects That Have Already Been Transported

From this point on, BI objects are subject to automatic change recording 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 automatic change recording: If you create new InfoObjects for an InfoCube that is subject to automatic change recording, these are not automatically written to the InfoCube request. Instead, they are assigned the $TMP package. You must use the BI transport connection to collect and transport these objects or the InfoCube.

Only refrain from collecting objects using the BI transport connection if the changes do not produce any new objects.

If you really want to list newly created objects in the standard transport system that belong to objects that have already been transported make sure that the objects are listed in the correct transport request. In the object maintenance screen, you can use the menu functions for the object catalog entry or Transport Organizer (if available) to assign the relevant package to the object and to write the object to the correct transport request.