Skip to Content
Technical Articles
Author's profile photo swati gawade

SAP BW/4HANA Remote Migration Features of Scope Collection



This article covers various options and navigations available in the scope collection step in the ‘Collect scope and Metadata Transfer’ phase using transaction RSB4HCONV and provides detailed information on same.

Once we have selected the remote conversion as the migration approach for the BW system, we need consider the scope that we would want to collect in the package for remote migration.



Remote Migration


  • Remote conversion needs installation of a new BW/4HANA system.
  • Remote conversion allows you to transfer entire flows along with the data, into the new BW/4HANA system installed.
  • Remote conversion option can be used to migrate SAP BW 7.4 or lower system



  • Installation of all required Notes and Add-ons
  • Assignment of required Authorizations
  • Completion of all predecessor steps


Collect scope and Metadata Transfer step enables you to select the scope that you are considering migrate as part of your current package to target HANA system into HANA compatible objects.

Once you execute the collect scope for transfer (data flow) option you will see a screen as follows.

During migration, the objects to be migrated are copied to the target system using a transport request and can only be transferred and activated in the target HANA system. Hence its imperative that all their dependent objects are available in the target HANA system as well. Based on scope collection input, one or several transport requests are created in the sender system with all the objects in the scope along with all their dependent objects. These transports are then imported to the target HANA system.

Lets explore each option in detail.

  1. Add New Object


This option allows you to choose the objects that you would like to add to the current package scope.

When you click on this button, a new window pops up which is similar to the Find option pop up window in RSA1 transaction.


You must include at least one object in the list.

  1. Remove Object

              This option allows you to remove the rows from added objects from previous step.

  1. Enter Objects Manually


This option allows you to manually add the objects. We need to enter the object type and full technical name of the Object.

F4 help is also available for object type as well as object name.


  1. Enter many objects

This option allows you to add multiple objects of the same type in a single go.


  1. Add all datawarehouse objects

This option will add all the datawarehouse objects in the sender system to the scope.


  1. Add all Toplevel process chains


This option will add all the top level process chains in the sender system to the scope.

System will identify the top level process based on the system logs.


  1. Copy from Remote system


This option allows you to select option from a different system.


  1. Minimal scope / Mandatory Objects

Minimal scope option will allow you to skip all the reporting related objects from the scope.



All the Bex queries and corresponding query elements will be skipped if you choose this option. For those Bex queries and their corresponding elements to be available in the target HANA system, you can either transport them manually, otherwise in future packages you can select the same infoprovider with collect query option. As in the previous package its corresponding dataflows must have been migrated, it will only collect queries with this step.


  1. Collect Queries of start object


By default, collect queries option will be selected by the system. This option ensures that all the BEx queries built on the infoproviders selected in the scope in this step as start object and their corresponding query elements are also selected in the scope selection.


CMOD code needs to be manually adjusted using BADIs.


  1. Optimized Transfer/Requests


Remote migration allows us to move the dataproviders from sender BW system to the target HANA system with data that they posses.


In the existing sender system the data is stored in the dataproviders request by request. If we need these request information to be preserved in the target system as well then we will not opt for request optimization.


However, if the request header information is not required then we can opt for request optimization where system will direct copy the tables to the target HANA tables.



If we have opted for the optimized requests then we have to make sure that all the change logs in scope have been cleared and all the cubes in scope and compressed beforehand.



Remote Conversion of sender BW systems are largely dependent on the scope collection. Its quite necessary for the developers to acquaint themselves with various features available for scope collection.




Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.