Transitioning to SAP Datasphere with SAP BW Bridge

⇨ Modernization of existing SAP BW or BW/4HANA system with SAP Datasphere is part of SAP’s roadmap and vision to move existing and new customers to this comprehensive data service on SAP BTP.

⇨ This article aims to simplify and explain the use of SAP BW Bridge as a mandatory service to make the move to SAP Datasphere using tool-based conversion approach.

⇨ Customers can leverage SAP BW Bridge to reduce complexity, factor amount of manual interaction and redesign required to help transition to a modern business data fabric.

SAP Datasphere is the next generation SAP Data Warehouse Cloud (DWC) offering a comprehensive data service built on SAP BTP and provides seamless and scalable access to business data with business context and logic intact. SAP Datasphere allows for data cataloging, data integration, semantic modeling, data federation, data virtualization and analytics capabilities in one single platform.

Figure 1: SAP Datasphere – High Level Architecture Overview

A few key features of SAP Datasphere include the following:

• SAP’s strategic target solution for all data warehousing use cases in the Public Cloud.
• Browser-based access empowering workforce with cloud-based simplicity – available as SaaS on SAP BTP.
• Self-service based no-code/low-code graphical data modeling and analytics capabilities for business users.
• Innovation in the cloud by leveraging existing investments on SAP BW including hybrid scenarios (BW/4HANA or native HANA).
• Access semantically rich data via business layer from any source (SAP, non-SAP sources across on-prem, inter-cloud).
• Open for external tooling for data Integration, data modelling and consumption.
• Advanced analytics capabilities by powerful embedded integration with SAP SAC.

SAP BW Bridge is a component of SAP Datasphere on SAP BTP that offers SAP BW capabilities directly in the public cloud. SAP BW Bridge allows the connectivity and business content for SAP BW-based data extractors from SAP ECC and S/4HANA. It provides the SAP BW layer for loading data with partitioning, monitoring, and error handling according to the business requirements.

A few key features of SAP BW Bridge include the following:

• Source system connectivity: Connectivity offered to on-premises SAP systems via ODP.
• Data modeling capabilities: Option to create data flow objects, Data Store Objects (DSOs), transformations and DTPs.
• Process chains usage: Option to create and schedule process chains.
• Data Management: SAP BW Bridge Cockpit allows data management in InfoObjects, Data Store Objects, and monitoring of process chains.
• Access to SAP BW objects to SAP Datasphere via spaces: BW Bridges allows import of Data Store Objects and composite providers and is available in SAP Datasphere for consumption via BW Bridge space. Further modelling can be done in SAP Datasphere on these objects.
• Business content available for use: An adapted version of the BW/4HANA content add-on has been optimized for SAP BW Bridge and can be used to create data models.

Figure 2: SAP BW Bridge – Data Integration Overview [High Level Diagram]

• SAP BW Bridge offers ABAP-based data extraction and staging capabilities with SAP Datasphere including integration with ERP systems.
• Tool-based transfer of existing compatible SAP BW, SAP BW/4HANA objects such as Composite Providers, Advanced DataStore Objects (ADSOs), InfoObjects to the SAP Datasphere ecosystem.
• SAP BW Bridge space is readily accessible in Datasphere’s Data Builder (Space sharing).

SAP BW Based Data Integration Scenarios with tool-based conversion

There have been multiple queries in various forums on the recommended approach for converting existing SAP BW or SAP BW/4HANA system to SAP Datasphere. This article aims to simplify and explain how SAP BW Bridge is a mandatory service for transitioning to SAP Datasphere.

Figure 3: Tool based conversion from SAP BW to SAP Datasphere

• Customers who have invested in SAP BW 7.3 (or higher) on any DB or BW/4HANA 2021 (or higher) require SAP BW Bridge mandatorily for conversion of existing SAP BW systems to SAP Datasphere.
• SAP BW Bridge is a component of SAP Datasphere, available as a service on SAP BTP and needs to be licensed separately.
• Conversion of existing SAP BW system to SAP Datasphere via BW Bridge can be done primarily using any of the following approaches:
  • Greenfield migration: Fresh development of SAP BW objects to be migrated inside SAP BW Bridge leveraging SAP BW/4HANA capabilities.
  • Shell conversion: Compatible metadata transfer without data.
  • Remote conversion: Compatible metadata transfer with data transfer via RFC.

• SAP provides automated SAP Readiness Check tools that allows to assess the readiness for sender and receiver systems migration.
• Tool-based migration has limitations on existing SAP BW objects being planned for migration to SAP Datasphere and therefore should be factored in during technical assessment and planning.

Converting an SAP BW or SAP BW/4HANA system to SAP Datasphere is a complex process and there is no direct conversion wizard available for it. However, SAP has created a well-defined process that leverages SAP BW Bridge and allows customers to complete the conversion smoothly.

SAP BW Bridge service on SAP BTP allows SAP BW capabilities directly in the public cloud and includes connectivity and business content for extractors based on ECC, S4, and warehousing layer for data loading, partitioning, monitoring, and error handling for all business requirements.

Remote Conversion using SAP BW Bridge

For remote conversion, SAP Datasphere and SAP BW Bridge are mandatory. Transfer cockpit is available to select the data models that are required to be transferred into the BW Bridge tenant, followed by a remote data transfer into that tenant. There is also option available for transporting data models and remote data transfer. If the migration program is considering a greenfield approach, transferring and converting data models and flows using tool-based conversion can accelerate the program.

Key Takeaways

• By using the Remote Conversion, it is possible to automatically transfer the compatible metadata and already existing data of the sender system via RFC.
• The metadata transfer converts object types (TLOGO), for example, PSAs, Classical DSOs and InfoCubes to ADSOs; InfoPackages to DTPs.
• Integration with ERP systems.
• Transfer of Delta queue pointers (cloning) is supported.
• The Remote Conversion to SAP BW Bridge is supported by the tooling from BW 7.3 (SP10 and higher) and SAP BW/4HANA 2021 (SP00 and higher) releases.

Shell Conversion using SAP BW Bridge

For shell-based conversion, SAP Datasphere and SAP BW Bridge are mandatory. Transfer cockpit is available to select the data models without data that are required to be transferred into an SAP BW Bridge tenant. If the migration program is considering a greenfield approach, transferring and converting data models and flows using tool-based conversion can accelerate the program.

Key Takeaways

• By using the Remote Conversion, it is possible to automatically transfer the compatible metadata only (no data transfer).
• The metadata transfer converts object types (TLOGO), for example, PSAs, Classical DSOs and InfoCubes to ADSOs; InfoPackages to DTPs.
• Integration with ERP systems.
• Data transfer process to be setup fresh.
• Delta queue needs to be reinitialized.
• The Shell Conversion to BW bridge is supported by the tooling from BW 7.3 (SP10 and higher) and BW/4HANA 2021 (SP00 and higher) releases.

Conversion Paths for SAP Datasphere/SAP BW Bridge

Figure 4: Conversion Paths – Comparison at a glance [Source: SAP]

Conclusion

SAP recommends its customers to start planning their move to SAP Datasphere by aligning to its overall data warehousing strategy and statement of direction. There are several ways to do this depending on various factors such as landscape complexity, business requirements, future business strategy, and roadmap. This article has explained how customers can leverage a well-defined tool-based conversion approach using SAP BW Bridge to reduce complexity, factor amount of manual interaction and redesign required to help transition to a modern business data fabric with SAP Datasphere.

Key Takeaways

• All conversion paths require manual interaction and redesign.
• Number of manual tasks to be carried out varies from customer to customer and depends on the configuration and state of the SAP BW or SAP BW/4HANA system.
• Automated tool-based conversion offers transfer of objects via XML files.
• Pre-check tool is provided by SAP to check compatibility and identification of critical steps.