Tips for importing SAP BW objects from one system to another

It’s not common and recommended to work directly in a production environment.

So, in most of your BW projects, you must import SAP BW objects from one system to another.

We usually start working in a development system and transport all our objects from the source to the next target system chosen by the company (like Quality, Pre-Production,… ending to the production system).

In this blog, we will go through the main steps to achieve the transport successfully:

1. Check the connections between the source system and the target system.
2. In the source system, include your objects into a transport request, via T-Code RSA1.
3. Release your request from the source system to the target system, via T-Code SE10.
4. In the target system, import queue and transport the request from the source system, via T-Code STMS.

In the examples below, we will illustrate transport from a development system (called BDH) to a production system (called BPH).

Step 1: Check the connections between the source system and the target system

Before starting the transport, make sure that the connection between the two systems (source system and target system) is made properly.

Here all the checks that have to be done:

Check 1: In the target system, check that the transport route is active, via T-Code STMS_PATH.

Example in BPH:

Check 2: In the target system, check that the RFC Connections are done and test them, via T-Code SM59.

Example in BPH:

1. T-Code SM59
2. Double click on the RFC connection you want to test
3. Click on ‘Connection Test’
4. Check your result (if the connection is failing, contact the basis team to fix it)

Check 3: Make sure that all the source systems are also available in the target system, via T-Code RSA1.

Example in BDH and BPH: to compare both systems

1. T-Code RSA1
2. Source Systems
3. Check that the same sources systems are added in both environments (e.g. in our case below, the source systems are the same in development and production)

Check 4: Make sur that the assignment of the source system IDs is done in both environments, via T-Code RSA1.

Example in BDH and BPH: to compare both systems

1. T-Code RSA1
2. In the menu: Tools / Asgnmt of Srce Syst. to Srce Syst. ID
3. Complete the Source System IDs

Check 5: In the target system, make sur that you complete the conversion of source system names after the transport, via T-Code RSA1.

Example in BPH:

1. T-Code RSA1
2. In the menu: Tools / Conversion of Logical System Names
3. Go from ‘Display’ to ‘Change’ Mode
4. Click ‘New Entries’
5. Complete the ‘Original Source System’ and the ‘Target Source System’

Check 6: Make sure that the settings for external SAP HANA View for BW objects are the same in both environments, via T-Code RS2HANA_ADMIN.

Example in BDH and BPH: to compare both systems

1. T-Code RS2HANA_ADMIN
2. Click on ‘General settings’
3. Check that the settings are the same in both environments

Check 7: In the source and target system, check that the destination in client for import postprocessing has been created, via T-Code RSTPRFC.

Example in BDH and BPH: to compare both systems

1. T-Code RSTPRFC
2. Check that the destination and a user is assigned for the import and make sure that the user are the same in both environments

Step 2: In the source system, collect your objects into a transport request

By default, all the objects are added in the package $TMP. But most of the time, for a specific project, you get the package name from the basis team.

There are many ways to include a BW Object in a request.

In this case, we will explain you the steps to select your objects by your own:

Example in In the Source system (e.g. development system BDH):

1. T-Code RSA1
2. Transport Connection
3. Select ‘Object Types’
4. Double click on ‘Select Objects’ for the object that needs to be transported
5. Select the column ‘Object Name’
6. Set Filter
7. Click on ‘Multiple Selection’
8. Copy/paste the list of objects

Tips: You can find the list of objects for each object type in the tables RS*, via T-Code SE16.

Here, few examples of tables where you can find the list of active objects per object types:

Object Type	T-Code SE16 / Table Name
Info Areas [Directory of InfoAreas]	RSDAREA
Data Sources [DataSource – Segment Fields]	RSDSSEGFD
Info Objects [Directory of all InfoObjects]	RSDIOBJ
Info Objects [Navigation Attributes]	RSDATRNAV
Info Objects [Master data attributes] *All attributes (not only navigationall)	RSDBCHATR
aDSO [Datastore Object]	RSOADSO
Transformation [Transformation for all Object Type]	RSTRAN
DTP [BW: Data Transfer Process Header Data]	RSBKDTP
Process Chain	RSPCCHAIN
Composite Providers [HanaCompositeProvider]	RSOHCPR
Queries [Directory of the reporting component elements]	RSZELTDIR

• Select all the objects manually one by one
• Click ‘Transfer Selections’ and all objects selected will be dropped on the right side of the screen in the area ‘Collected Objects’
• In the option ‘Grouping’, select ‘Only Necessary Objects’
• Click on the ‘truck’ icon to transport all objects selected

Remark: It’s recommended to create one transport request per object type and transport them in the right order (e.g. one transport request for the Info Areas / one transport request for the Datasources / one transport request for the IOBJ / … and you will transport the Info Area first, then the Datasources, then the IOBJ, …).

Step 3: Release your request from the source system to the target system

Next step, you can release your request from one system (e.g. development) into further systems (e.g. production).

1. T-Code SE10
2. Select your request / Click on the ‘truck’ icon to directly release your requests:
   1. First, release the lowest task
   1. Then, release the highest task

Remark: Be aware if dependent objects are missing in the transport request, you will get an error while transporting your request

Step 4: In the target system, import queue and transport the request from the source system

You will find all your transport from the source system in the import queue list.

1. T-Code STMS
2. Click on the ‘truck’ icon to import overview
3. Double click on the target system where you want to import your requests
4. Click on the ‘refresh’ icon to display the last requests released from the source system
5. Select the request you want to import
6. Click on the ‘truck’ icon to import request
7. Complete the Target Client
8. Options: Check the import options you need if necessary
9. Click on the ‘green V’ to continue
10. Click ‘Yes’ to confirm the import of your transport request
11. Click on the ‘refresh’ icon to see the status of your transport
12. Check that your status become ‘green V’ which means that your request is transported with no error

Note: If you need, to re-import a request, follow these steps:

1. Tool bar, go to ‘Extras’
2. Select ‘Other Requests’, then ‘Add’
3. Complete the information’s:
   – Transp. Request: Type the transport request you want to transport again
   – Import again: Check it
4. The transport request is again available in the import queue, and you can import it again.

Before starting to import SAP BW objects from one system to another, keep in mind to check all connections between the systems. And make sure to put all dependent objects in your requests and transport them in the right order, or you will get an error while transporting your requests.