Skip to Content

IT departments have an ever growing need to address the following challenges:

  • The lack of  reporting performance as well as high data latency
  • Changes in the BW environment that  result in disruption of the BW application
  • Insufficient planning and security regarding effort and timeline for a database migration
  • Complex IT landscapes and high IT workload

The migration of the underlying database of SAP NetWeaver BW to SAP HANA is one of the key enablers that addresses these complex business challenges of today & tomorrow. Hence, there is a great demand of doing this transition faster, better, and in a more cost effective fashion. For more information about SAP NetWeaver BW powered by SAP HANA, please visit this link:

While SAP HANA Enterprise Cloud provides a great way to start your SAP NetWeaver BW journey on SAP HANA, there is still a need to perform a database migration for customers with an existing SAP NetWeaver BW system, regardless whether moving into the cloud or staying on-premise for customers who are willing to manage their infrastructure services. Considering mission critical information using SAP NetWeaver BW, doing database migration need to be safe, secure and predictable in terms of cost & timeline. Rapid database migration of SAP NetWeaver BW to SAP HANA package addresses this particular need and it does nicely by leveraging the SAP rapid-deployment solution methodology.

Rapid database migration of SAP NetWeaver BW to SAP HANA

This package enables customers to leverage the best migration practices to replace the underlying relational database of their SAP NetWeaver BW system with SAP HANA as a database. Benefits of a rapid-deployment solution approach:

  • Accelerated project methodology via HTML-based “Step-by-Step” guide, additional project tools and detailed WBS
  • Guided process to migrate your database in a IT project format leveraging SAP documentation and new project accelerators
  • Incorporates the best approach and sequence to plan and migrate your system.
  • Service offerings from SAP and qualified RDS SAP Partners, or use RDS content within a SAP customer’s own experienced SAP Program Office / COE team

This rapid-deployment solution leverages the latest in SAP tool development like the DMO for SUM (Database Migration Option for Software Update Manager) to combine upgrade and database migration into one step with only one system downtime, as well as PCA (Post Copy Automation) to offer a minimized downtime approach with minimal business downtime for the SAP NetWeaver BW system. For more information follow the direct link to this rapid-deployment solution (s-users only):

Go live in as little as 10 weeks!

As per the SAP rapid-deployment solution methodology, this also assures customers with a predictable cost and timeline migration (as little as 10 weeks). Also, this includes a lot of pre-defined content (project kick-off presentation, how-to/training guides, etc.), supports a wide variety of databases as the source, and provides a comprehensive service offering. Based on the results of the Strategy and Technical Design for SAP NetWeaver BW powered by SAP HANA assessment the customer relevant services are determined and scoped, in order to provide an end-to-end solution. Depending on these results the SAP rapid-deployment solution will be sized.

Many customers already used this rapid-deployment solution for its safe and quick migration of SAP NetWeaver BW to HANA. Besides SAP consulting there are many SAP partners around the globe that migrate your SAP NetWeaver BW database to HANA using the methodology from this RDS. Ask SAP consulting or your SAP implementation partner about this offering.

Solution scope:


System requirements:

  • SAP NetWeaver BW 7.00 SP29 or higher, Unicode or Non-Unicode, ABAP only
  • SAP Solution Manager 7.0 EHP1 SP23 or SAP Solution Manager 7.1 SP01 minimum
  • Software Logistics Toolset 1.0 SP09 minimum (for Database Migration Option – DMO)
  • SAP NetWeaver Landscape Virtualization Management, Enterprise Edition (for BW Post-Copy Automation – PCA)
  • SAP HANA Platform Edition 1.0 SP07 minimum
  • Your operating system platform must be 64-bit
  • For a comprehensive list of supported operating system releases, see the Product Availability Matrix (PAM) at:
  • Oracle 11.2 (10.2 with DMO)
  • IBM DB2 LUW 10.1 (9.1 with DMO)
  • MaxDB 7.9
  • MS SQL server 2008
  • DB2 for i61, 7.1 (not yet supported for DMO, see SAP Note 1875197)
  • DB2 for z/OS V9, V10
  • SAP Sybase ASE 15.7

In addition I can recommend to take a look at the follow links which provide additional information if needed:

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Frank Densborn

    RDS is doing a great job in providing SAP’s customers the full story of DB migration for their existing SAP BW systems. But even new customers not running BW on HANA yet who are interested in the power of HANA can easily test run SAP BW powered by SAP HANA with their own data warehouse sample data. Just check this out:

    BW? Rapid Data Migration family keeps growing!

    1. Kim Mathaess Post author

      Dear Ashutosh Chaturvedi,

      Please let me know if I understood and answered your question correctly:

      The minimum software and database requirements for this RDS are mentioned above in the text in an overview table. For example, the RDS could start if your current BW release would be 7.00 SP29 and running on Oracle 10.2. Then the scope would be to upgrade to the 7.40 release and conduct the database migration. As said, both steps are covered by the RDS.

      If your questions is, what the requirements for an SAP HANA database migration of BW are “in general” (which would be a 7.30 minimum release and the same database releases as mentioned in my blog), then I can recomment the following:

      At the very bottom of my blog I also linked additional sources of information, where in this case I would refer to the SAP BW on HANA Cookbook or the

      In general you can always refer to the official Product Availability Matrix if in doubt:


      Kim Mathäß

  2. Ashok Oleti

    Hi Kim,

    1) Is the RDS solution provided, for Migration of SAP BW database to HANA, free or any license fee is included and how much it costs?

    2) The tools SUM with DMO and BW Post Copy Autmoation are also provided with license fee, if those needs to be used to migrate database of the existing SAP BW to HANA?

    Thanks in Advance..


    Ashok Oleti.

    1. Kim Mathaess Post author

      Hi Ashok,

      1) The RDS content itself is completely free and can be found via the link I posted in the blog:

      However, in order to migrate an existing BW system to SAP HANA as a database, the SAP HANA license is needed of course. There the SAP HANA license fee applies, where the price is calculated using the sizing metric.

      2) The DMO is part of the SUM (SL Toolset download in the SAP Service Marketplace) and therefore free of charge. For BW Post Copy Automation (which is optional) a license is needed, but there are possibilities for project licenses (database migration specific).



      1. Ezequiel Pardo

        Hi Kim,

        I used to run the RDS GTM for SAP Latin America as RDS Sales Lead, and working now on an SAP partner company.

        Can you please help me to understand if point 1) “The RDS content itself is completely free”, refers not only to the “Discovery” content, but also to the “Deployment” content including the complete Step-by-step (SBS) guide?

        If the SBS is free, how should I request downloading authorization?

        I tried the RDS link RDS step-by-step guide download link without success.

        Thanks for your time and help.


        1. Kim Mathaess Post author

          Hi Ezequiel,

          we have different entry points and different access levels. for access to HTML information, with S-User access to full packaging content. Content itself is then classified for customers and partners. However, partners should have full access to the packaging content so I suppose this is related to the S-user of the particular person and has nothing to do with our access concept. You might need to talk to the PAM / PSA responsible for your partner company to clarify.

          Best regards,



Leave a Reply