Child pages
  • BW-B4H-CNV Conversion to BW/4HANA
Skip to end of metadata
Go to start of metadata

**The following guide is intended as a brief overview and omits certain steps required for successful BW/4HANA conversion. Therefore, it should be used only to supplement the official documentation. Please see the Conversion Guide and Note 2383530 below for full details of the required BW/4HANA Conversion steps. **


SAP BW/4HANA is SAP’s next generation data warehouse solution. It is a new product (not a legal successor of any existing SAP Business Warehouse solution), built entirely on one of the most advanced in-memory platforms today – SAP HANA. It provides a simple set of objects that is well suited for modelling an agile and flexible layered architecture of a modern data warehouse.

SAP provides three paths for the conversion from SAP BW to SAP BW/4HANA, the so called “In-place Conversion”, “Remote Conversion”, and “Shell Conversion”.

SAP Online Documentation

Important SAP Notes

  • 2383530 - Conversion from SAP BW to SAP BW/4HANA (Conversion Guide PDF inside)  — This is the Master Note for all conversions to BW/4HANA


  • 2421930 - “Simplification List for SAP BW/4HANA”
  • 2347382 - SAP BW/4HANA – General Information (Installation, SAP HANA, security corrections…)
  • 1729988 - SAP BW powered by SAP HANA and SAP BW/4HANA - Checklist Tool
  • 2421930 - Simplification List for SAP BW/4HANA

SAP Note 2347382 describes general information about and prerequisites for SAP BW/4HANA whereas SAP Note 2383530  contains systematic instructions, on how to prepare your system for a conversion. Note 2421930 contains specific information on conversion of individual object types. 


BW-B4H-CNV - Conversion to BW/4HANA  (Select this component for broad conversion queries or if don't know which conversion to perform)

  1.          BW-B4H-CNV-IPL   - In-Place Conversion to BW/4HANA

         2.    a)   BW-B4H-CNV-RMT  - Remote Conversion to BW/4HANA (Transfer Cockpit)

                b)   CA-LT-BW4 - Remote Conversion to BW/4HANA  (SAP BW/4HANA Conversion Cockpit)

         3.          BW-B4H-CNV-SHL - Shell Conversion to BW/4HANA

Paths to BW4/HANA

  1. In-Place conversion type: Convert your existing 7.5 BW on HANA system to BW/4HANA. 

             SAP strongly recommends to use the latest support package for SAP BW/4HANA when performing the conversion

         ****System must be 7.5 and must run on HANA database.****

        2. Remote conversion type: Install a brand-new SAP BW/4HANA system and transfer all or some existing data flows from existing system. 

        **** System must be at least 7.3 or above and can run on Any-DB.****

        3. Shell conversion type: A green field installation (new SID) of SAP BW/4HANA is used. Selected data models can be transported without data into system. 

      **** BW system can be on releases from 7.00 to 7.50 running on Any-DB****

Phases of Conversion 

Discover / Prepare Phase - Preparatory phase which includes gathering of system requirements, maintenance planner, pre-checks and custom-code /object specific preparations. 

Explore / Realization Phase- The actual execution of the conversion, steps are highly dependent on Conversion type selected (See Paths to BW/4HANA above). 


Transactions and Support Tools

RSB4HCONV  (A.K.A. BW4/HANA Transfer Cockpit)  — Executable on any BW system but minimum support packages apply 

All objects such as DSO's, InfoCubes, MultiProviders etc. are converted using the Transfer Cockpit. 

Exceptions include those not from Data Warehousing Workbench (e.g 3.x Queries) , which are converted using the Task List. 

STC01 - Current Task List Run

STC02 - Check Previous Task List Run 

RSB4HTRF – This tool automatically transfers BW objects to BW/4HANA compatible objects. For example, Infocube -> ADSO.

Can also be accessed via RSB4HCONV via 'Scope Transfer' button. 

RSMIGRATE - Used primarily to migrate 3.x master data flows to 7.x flows in advance of preparing objects for BW4/HANA.

Program RS_B4HANA_RC - Pilot pre-check report which replaces 'Execute Pre-Checks' option in RSB4HCONV, only available as of 7.50. See Note:

  • Note 2777672 - Pilot Release: new check tool

Program ZBW_HANA_CHECKLIST- Used to optimize a BW landscape for HANA prior to conversion to BW/4HANA. See Note:

  • Note 1909597 - SAP BW Migration Cockpit for SAP HANA

Some important steps to note for BW4/HANA Conversion

---→ (Please see Note 2383530  for further instruction

  • It is important to install the SAP BW/4HANA Starter Add-on, see SAP Note 2383530. It can’t be installed on release 7.4 or lower.


             There are 4 mode types:

             Compatibility mode: Default mode when add-on installed.  Existing objects supported but no new non BW4 optimized objects can be created in this mode.

             In Compatibility Mode, you can approve the export of objects that are not supported anymore in B4H Mode. You do this by registering the export on a white-list with program

             RS_B4HANA_WHITELIST_MAINTAIN. Objects that are registered on the white-list can be exported in a transport request.


            B4H mode: Temporary mode, switch to this mode only when all objects are optimized for SAP BW/4HANA. Further clean-ups executed here.

            Ready-For-Conversion-Mode: Temporary mode, only immediately before the migration to SAP BW/4HANA. 

            BW Mode: For emergency corrections only. 

            You can change the mode type in transaction RSB4HCONV → 'Change Operation Mode' → Execute New Mode 


Quick Tip:

             If you just want to check your SAP BW system, then the SAP BW/4HANA Starter Add-on is not required. However it is required to change the operating mode or use the Transfer Cockpit.


  • It is important to Install and run the Note Analyzer Program in SE38 transaction (Z_SAP_BW_NOTE_ANALYZER) with the XML's that correspond to your conversion path. 

  • It is important to run: Transaction RSB4HCONV 'Execute Pre-Checks'
          It determines which objects are compatible with SAP BW/4HANA and which objects are not available in SAP BW/4HANA and can be automatically converted, deleted, or need manual                adjustments.

Troubleshooting Tips:

  1. Remove all obsolete BW objects from the system to decrease the time needed to analyze objects for compatibility with SAP BW/4HANA and reduce the effort needed to convert them.

  2. The “Simplification List for SAP BW/4HANA”, describes what happens to individual object types when transitioning to SAP BW/4HANA. See the excel spreadsheet attached to the following Note for details on particular object types e.g InfoPackage, Composite Providers etc...
    See: Note 2421930 - Simplification List for SAP BW/4HANA

  3. Essential consistency checks are included in task list RS_B4H_CHK_CLEANUP.  This ensures the SAP BW system has repaired any issues that might exist before executing the 'Scope Transfer'. 

  4. Only one execution package of the SAP BW/4HANA Conversion Cockpit can be active in system at a given time. This action generates a report which highlights which objects are not  compatible for an SAP BW/4HANA system. The underlying job is RS_B4HANA_CHECK_ENABLE and is visible in SM37 transaction.

  • It is important that after all preparatory steps that you execute a scope transferTransaction RSB4HTRF → 'Execute Scope Transfer'.

            The selections of the scope transfer (with/without metadata etc...) will depend on the Conversion type selected. Alternatively, it can be run by using transaction RSB4HTRF and                                  selecting “In-Place Conversion”. You can find a detailed documentation of the tasks performed during a scope transfer in the system by running transaction STC01. After conversion                          type selection, then select the scope (which objects should be converted) and define object mapping using the check-boxes provided. Save and Execute once you are certain you have                    defined settings correctly.


Troubleshooting Tips

  1. If trying to transfer a recreated object in a subsequent task list run for some already transferred object that was previously deleted and you get an error message, you may have to clean-up the old transfer settings first using program RS_B4HANA_INPLACE_CLEANUP (Valid for In-Place Conversion ONLY). Alternatively, if an object is required, you may need to search and activate, or transport it from an original system. 

  2. It’s not possible to confirm when the task list run is in display mode. The task list run must be in maintenance mode.

  3. The scope transfer details error messages for technical names of objects. For missing/inactive objects, use RSA1 search feature to check if object exists. If inactive, activate the object. If object is missing and not required, run task list RS_B4H_CHK_CLEANUP to repair object cross-reference. If object is required, try transport it from original system.

  4. N.B: Do not skip or cancel a scope transfer, which stops in the middle of a task list run, when changes have already happened. If you do, the system could easily get into an inconsistent state. If a scope transfer stops, look into the details of the error messages. 

    If the task list run stops and it is not possible to adapt the object or correct the error, contact SAP Product Support (component BW-BW4-CNV)
    If a task list run is in such state, for example for DataStore objects (classic) or InfoCubes, there is no way back and the task list run must be continued until the end. Please do not lock or delete the task list run; do not delete or modify any SAP database tables manually; do not delete any of the involved SAP BW objects; do not release any involved transport requests. SAP Product Support will troubleshoot the issue and provide appropriate guidance to complete the task list run.








  • No labels