Start of Content Area

Procedure documentation Transporting BI Objects  Locate the document in its SAP Library structure

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

Note

You can display or hide the left hand navigation window in Data Warehousing Workbench by choosing 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).

 Note

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.

Caution 

Ensure that you release any requests with locked objects beforehand.

Note

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

        Last Changed

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

Caution

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.

Note

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

Result

Depending on their object type, the transported objects are imported to the target system in either A, M or T version and are automatically activated using the after-import method RS_AFTER_IMPORT. The dependent DDIC and program objects are generated in the target system after the import. If objects deletions have been transported, the corresponding objects are deleted in the target system.

With the implementation of Business Add-In (BAdI) RSO_BADI_TRANSPORT, you can automatically trigger follow-on activities such as executing or rescheduling process chains once the objects have been imported. After the standard BI after-import methods have run, method AFTER_IMPORT from interface IF_EX_RSO_TRANSPORT is executed. For more information, see Implementing BAdIs in Enhancement Builder and the method documentation for IF_EX_RSO_TRANSPORT AFTER_IMPORT.

More Information

Technology of the SAP Change and Transport System (CTS):

      Transport Organizer

      Transport Strategy in the CTS

Transport Landscape in BI

Recording Time for Transports

Defining Object Changeability

Changing Package Assignments

Special Features of Individual Object Types

Troubleshooting (Transport)

 

 

 

 

 

End of Content Area