Skip to Content
Technical Articles
Author's profile photo Deniz Osoy

SAP Data Warehouse Cloud, SAP BW bridge: Overview and Technical Deep Dive

Abstract

This blog post is about a strategic feature of SAP Data Warehouse Cloud, namely the SAP Data Warehouse Cloud, SAP BW bridge. SAP offers its customers through RISE with SAP, the opportunity to move with a business transformation as a service (BTaaS) to the cloud. For BW customers, this means SAP BW to SAP Data Warehouse Cloud. SAP positions SAP Data Warehouse Cloud as the strategic target solution for Data Warehousing in the public cloud, with SAP BW/4HANA Private Cloud Edition (PCE) as an option to start the transition. In this context, SAP BW bridge offers customers the opportunity to implement their new data warehousing use cases directly in the cloud environment while protecting, and retaining their existing on-premises investments. The blog provides an overview about SAP BW bridge, explains how to move from an existing SAP BW system to the cloud, and gives insights with a complete end-to-end greenfield scenario including a system demo in SAP Data Warehouse Cloud.

Overview

SAP Data Warehouse Cloud is SAP’s offering for all data warehousing use cases. This SaaS (Software-as-a-Service) is based on SAP HANA Cloud. It combines data, and analytics in a cloud solution that offers data integration, database, data warehouse, and analytics services. This enables customers to realize the full potential of a data-driven business. As a way to improve the integration with SAP ERP systems, the SAP BW bridge enables ABAP-based data extraction and staging capabilities within SAP Data Warehouse Cloud (see figure 1).

Figure 1: SAP Data Warehouse Cloud, SAP BW bridge. Overview of data integration

In the future, a tool-based transfer of existing SAP BW and SAP BW/4HANA staging scenarios will be enabled. Then the SAP BW bridge will enable a seamless transfer of existing ETL processes in a dedicated SAP BW bridge Space in SAP Data Warehouse Cloud. Here, the extensive functions of ODP extractors, and ABAP code within the SAP Business Technology Platform (SAP BTP) ABAP environment can be adopted in SAP Data Warehouse Cloud using the Cross-Space-Sharing approach.

SAP BW to SAP Data Warehouse Cloud

Within SAP BW bridge, customers are able to implement data extraction and staging scenarios up to the CompositeProvider level. In other words, it is not possible to create new queries within the SAP BW bridge environment. In this regard, within the SAP BW bridge, there is no support for OLAP engine, and functionality dependent on OLAP (e.g., analysis authorizations, query as info provider, query execution). Front-End tools do not have the possibility to access SAP BW bridge artefacts directly.

Figure 2: Future Modeling Capabilities in SAP Data Warehouse Cloud

 

The SAP BW bridge environment is primarily intended for ODP-based source systems, which means that the connection scenarios only become available via Operational Data Provisioning (ODP). Non-SAP sources will be connected directly to SAP Data Warehouse Cloud (see figure 2). Objects from source SAP BW system(s) will be converted to the SAP BW bridge environment using Conversion Tools, including the SAP BW queries.

To take the full advantage of SAP’s data warehousing offerings, customers today need to deploy both SAP BW/4HANA, and SAP Data Warehouse Cloud. In the future, the SAP BW bridge will enable customers to merge these offerings into a single data warehouse solution in the cloud. With SAP BW bridge, SAP addresses BW customers that are looking for a way forward from SAP BW NetWeaver, and SAP BW/4HANA (See figure 3).

SAP%20BW%20to%20SAP%20Data%20Warehouse%20Cloud

Figure 3: Future Modeling Capabilities in SAP Data Warehouse Cloud

SAP BW Customers will have the option in 2022 to convert their existing on-premises investments to the cloud via remote, and shell conversion. First, the SAP BW bridge conversion will be offered for SAP BW 7.4, and SAP BW 7.5 systems (initially as shell conversion, followed as remote conversion), subsequently the conversion for SAP BW 7.3 systems (shell and remote conversion) will be available. Additionally, the conversion will be available for SAP BW/4HANA 2021 (shell and remote conversion). Regarding release coverage, please consider the details in the roadmap. Customers with lower SAP BW releases will need to upgrade their system(s) first, and then convert the required scope to SAP BW bridge in SAP Data Warehouse Cloud. Please note that SAP BW systems 7.40, and lower are already out of maintenance (see figure 4).

Figure 4: SAP BW bridge. SAP BW to SAP Data Warehouse Cloud

The SAP BW bridge artefacts out of the Business Technology Platform (SAP BTP) ABAP environment are available via remote tables using SAP HANA Cloud Smart-Data-Access (SDA) in a dedicated SAP BW bridge Space in SAP Data Warehouse Cloud. The remote tables in the SAP BW bridge Space can then be used in the regular SAP Data Warehouse Cloud Spaces via the SAP Data Warehouse Cloud cross-space sharing approach.

Add-ons are not supported in SAP BW bridge. Therefore, planning is not available within SAP BW bridge. In this regard, SAP positions SAP Analytics Cloud Planning as the planning application, and in the future (earliest end of 2022) SAP Data Warehouse Cloud as the planning foundation for the data. Application development is not supported in SAP BW bridge. Any app development should be done via the Business Technology Platform App Building on SAP HANA, for which customers need to license, and use the stand-alone version of SAP Business Technology Platform ABAP Environment.

Target Scenarios for SAP BW bridge

Greenfield with SAP Legacy Sources
Customers building a new data warehouse in the cloud with SAP Legacy systems as data sources that will only be migrated to a cloud-based system in the future. Expecting the same level of data integration, and convenience functions as known from SAP BW/4HANA.

Conversion with SAP BW NetWeaver & SAP BW/4HANA
Customers with an SAP BW (SAP BW 7.3 and upwards, any DB) moving their data warehouse to the cloud expecting to retain their data, and their legacy data flows, but renovating their data consumption layer with SAP Analytics Cloud or 3rd party clients on top, and expanding their data footprint to cloud, and non-SAP sources.

Hybrid with SAP BW/4HANA
Customers with an on-premise SAP BW/4HANA looking for a path into the cloud for their data warehouse workload. Starting with hybrid scenarios for consumption to combine SAP BW/4HANA data, and SAP Data Warehouse Cloud data, and then easily moving more and more of the SAP BW/4HANA data flows to the cloud, and successively transition them to modern SAP Data Warehouse Cloud data ingestion approaches.

End-To-End Greenfield Scenario

As an example, the Greenfield approach is demonstrated in the following use case (See Figure 5). This means when the customer operates SAP Data Warehouse Cloud together with SAP BW bridge to connect SAP on-premises systems. This provides proven SAP BW-based data integration technology for ABAP-based SAP systems, and enables the rich feature set of extractors in SAP Data Warehouse Cloud.

Figure 5: Architecture of End-To-End Greenfield Scenario

The SAP BW bridge data, and processes are administered, and managed via an SAP UI5 environment called SAP BW bridge Cockpit. The implementation of new objects is done within Eclipse via SAP BW Modeling Tools, and ABAP Development Tools. Within the SAP Data Warehouse Cloud, the SAP BW bridge artefacts are available via remote tables, and can be used via the SAP Data Warehouse Cloud cross-space sharing approach. An SAP GUI is not required to access the SAP BW bridge environment.

SAP BW bridge: Development-Environment

In the following data flow (see figure 6) it can be seen, that the Eclipse environment with SAP BW Modeling Tools, and ABAP Development Tools are used. The well-known SAP flight data model is the foundation for this use case.

Eclipse%20Environment

Figure 6: Eclipse Environment for SAP BW bridge

In this scenario, the tables “Flight” for transaction data, and “Airline carrier” for master data are considered. The left branch of the data model handles transaction data, the data is loaded from an SAP ECC system respectively a classic ABAP extractor. The right branch of the data model handles master data, the data is loaded from a CDS view. As it can be seen, there is still the subdivision into master data texts, and master data attributes. Within the data flow, transformations, and data transfer processes are used to load data into the advanced DataStore Object, and the master data-bearing InfoObject. Within the Composite Provider, the data is then combined with a join.

The SAP BW bridge component is primarily intended for ODP-based source systems. In this regard, customers have the option to create source systems in the context of ODP. This means that ODP-BW, ODP-SAP, ODP-CDS, and ODP-SLT based source systems can be connected. This offers the additional benefits of the Operational Data Provisioning Framework, such as Extract Once Deploy Many, data compression, and more.

SAP%20BW%20bridge%20Cockpit

Figure 7: SAP UI5 Environment for SAP BW bridge

Dedicated process chains are created for both branches in order to load data into the InfoProviders. The process chains are modelled in the SAP UI5 environment for SAP BW bridge called SAP BW bridge Cockpit (see figure 7).

SAP BW bridge Space in SAP Data Warehouse Cloud

If a customer wants to use SAP BW bridge, a provisioning process is triggered by SAP. With that, there will be a dedicated Space for SAP BW bridge in the SAP Data Warehouse Cloud Tenant itself, generated by the provisioning process. This space then has a specific type “SAP BW bridge” (see figure 8).

Figure 8: Space Type: SAP BW bridge

In the generated SAP BW bridge Space, a connection (see figure 9a) to the SAP BW bridge environment, within the SAP Business Technology Platform, will be generated that contains an SAP HANA Cloud Smart Data Access endpoint, and a HTTP ABAP endpoint. It is possible to connect only one SAP BW bridge System to an SAP Data Warehouse Cloud Tenant.

Figure 9a: Connection to SAP BW bridge

The SAP HANA Cloud Smart Data Access endpoint is used to connect to the external schema of SAP BW bridge’s SAP HANA Cloud Database that contains the read-only views to the data tables, for moving over the data. The HTTP ABAP endpoint is used to be able to call Monitor UIs via Single Sign on with a named user, and to get Meta Data e.g., for a value help or import of SAP BW bridge Objects (see figure 9b).

Figure 9b: Connection to SAP BW bridge

The new connection type cannot be edited by a user in the SAP BW bridge Space, as this connection will be generated by the SAP BW bridge provisioning process automatically. The credentials for the SAP HANA Cloud Smart Data Access connection are provided when the connection is generated. The data tables of the Business Technology Platform environment for SAP BW bridge are exposed as remote tables in the SAP BW bridge Space.

Important: The SAP BW Service Key should be copied, as this needs to be entered when an SAP BW bridge project is set up in Eclipse.

Figure 9c: Connection to SAP BW bridge

Inside the SAP BW bridge Space, the Create-Button for new connections is disabled, as this Space is restricted to the SAP BW bridge only. The Real-Time Replication Status is inactive for this connection, as it only allows Remote Tables (see figure 9c).

SAP BW bridge Space: Data Builder for importing remote tables

The main purpose of the Data Builder regarding the SAP BW bridge Space (see figure 10) is to import, and share the remote tables for other Spaces, using the Cross-Space Sharing Approach of SAP Data Warehouse Cloud. Unlike the regular Spaces of SAP Data Warehouse Cloud, it is not possible to create Tables, Graphical Views, SQL Views, Entity Relationship Models, or Data Flows within the Data Builder of a SAP BW bridge Space. SAP Data Warehouse Cloud artefacts using the SAP BW bridge remote tables can only be created in other spaces based on the shared remote tables.

Figure 10: SAP BW bridge Space: Data Builder

Using the Import button in the Data Builder, then via “Import Remote Tables”, the tables of SAP BW bridge InfoProvider can be accessed via the underlying connection (see figure 11).

Figure 11: Import Remote Tables

In the “Import Remote Tables” wizard there is only one connection available, the connection to the SAP BW bridge System (see figure 12). By selecting the defined connection, the connection gets validated. If the validation process is successful, the next step is available.

Figure 12: Connection to SAP BW bridge

The wizard for the data tables of SAP BW bridge InfoProvider contain the following data tables, which are then available as Remote Tables in SAP BW bridge Space in SAP Data Warehouse Cloud itself.

  • Advanced DataStore Object (Reporting View)
  • Composite Provider
  • Master Data Tables
    • Attributes
    • Texts

The data tables are displayed by InfoAreas (see figure 13). It is possible to multi select tables to support a mass take over. It is also possible to select an entire InfoArea, then all the tables underneath the objects are selected. Afterwards it is possible to deselect some tables (then the InfoArea can be deselected).

Figure 13: Select SAP BW bridge InfoProvider

The last step displays the list of objects which are ready for import. There is one more section for Remote Tables, which are already in the repository of SAP Data Warehouse Cloud. The user can also change the technical name, and the business name of the appropriate object. Via “Import and Deploy” the remote tables will be generated with Semantic Usage as Relational Dataset. The Master Data Text tables can be generated as either Dimension or Text (see figure 14).

Figure 14: Import and Deploy Remote Tables

Next, the remote tables located in the SAP BW bridge Space in SAP Data Warehouse Cloud need to be shared with the regular SAP Data Warehouse Spaces. As already outlined before, the main functionality here is to import, and share the remote tables for other spaces. SAP Data Warehouse Cloud artefacts using the remote tables can only be created in other spaces, based on the shared remote tables.

In my example, I have created a standard SAP Data Warehouse Cloud Space “DENIZBWBRIDGE”, which consumes the artefacts, and allows further implementation within the SAP Data Warehouse Cloud (see figure 15).

Figure 15: Share Remote Tables

SAP Data Warehouse Cloud Space: Consuming Shared SAP BW bridge Artefacts

Within standard SAP Data Warehouse Cloud Spaces, the shared SAP BW bridge Remote Tables can be accessed, and other SAP Data Warehouse Cloud functionality can be applied accordingly (see figure 16).

Figure 16: Graphical View in SAP Data Warehouse Cloud

The following SQL code of the previous graphical view (see figure 17) states that the view within the standard SAP Data Warehouse Cloud Space accesses the remote tables of the SAP BW bridge Space in SAP Data Warehouse Cloud.

SELECT *
FROM (("BWBRIDGEDEMO.ZDOFLIGHTREPORTING" AS "ZDOFLIGHTREPORTING"
INNER JOIN "BWBRIDGEDEMO.ZDO_AIRLATTRIBUTES" AS "ZDO_AIRLATTRIBUTES" 
ON "ZDOFLIGHTREPORTING"."CARRID" = "ZDO_AIRLATTRIBUTES"."ZDO_AIRL") 
INNER JOIN "BWBRIDGEDEMO.ZDO_AIRLTEXT" AS "ZDO_AIRLTEXT" 
ON "ZDO_AIRLATTRIBUTES"."ZDO_AIRL" = "ZDO_AIRLTEXT"."ZDO_AIRL");

Figure 17: SQL-Code of Graphical View

SAP Analytics Cloud: Story based on SAP BW bridge data

Finally, based on the analytical data set of SAP Data Warehouse Cloud, which in this case processes SAP BW bridge data, a visualisation of the data can be done via SAP Analytics Cloud (see figure 18) or any other 3rd party front end solution.

Figure 18: Story in SAP Analytics Cloud

Like for other data models in SAP Data Warehouse Cloud you can use SAP Data Warehouse Cloud Live Data Connection of SAP Analytics Cloud. However, SAP Analytics Cloud generally has certain limitations with SAP Data Warehouse Cloud Live Data Connection, detailed information is available in SAP Note 2832606.

SAP BW bridge Space: Data Integration Monitor

Figure%2021%3A%20Data%20Integration%20Monitor%20for%20SAP%20BW%20bridge%20Space

Figure 19: Data Integration Monitor for SAP BW bridge Space

Within the SAP BW bridge Space only Remote Tables are available. For the Data Integration Monitor of the SAP BW bridge Space that means, that the View Persistency Monitor, and Data Flow Monitor are not visible (see figure 19).The available functionalities here are the Remote Table Monitor, and Remote Query Monitor. In addition, access to the SAP BW bridge Cockpit is possible via the Data Integration Monitor of the SAP BW bridge Space.

End-to-End Demo for SAP Data Warehouse Cloud, SAP BW bridge

The following video demonstrates the steps for an entire end-to-end greenfield scenario in SAP Data Warehouse Cloud using SAP Data Warehouse Cloud, SAP BW bridge. Finally, the data is visualised in SAP Analytics Cloud. The video is also available on the official SAP Technology YouTube Channel.

Summary

The value of SAP Data Warehouse Cloud is clearly recognized by many of SAP’s existing data warehousing customers. However, they want a seamless migration path, and do not want to implement their existing data warehousing logic from scratch. At the same time, the market wants a single-target solution to reduce the system landscape complexity, and costs. This is where SAP BW bridge helps to accelerate the transition to cloud data warehousing while protecting previous, and new implementation investments in the cloud. This enables the integration of on-premises SAP Business Suite data with trusted connectivity, and semantic richness (business content). It also enables organizations to rapidly innovate on SAP BW data with an open, unified, data and analytics service in the cloud.

Find further information to get started with SAP Data Warehouse Cloud and check out the Best Practices on the Community for SAP Data Warehouse Cloud. Please also check out this blog post regarding this topic. Additionally, this brochure provides an overview of SAP Data Warehouse Cloud, SAP BW bridge. It is also recommended to check the SAP Note 3117800 – Information/Restrictions for SAP DWC, SAP BW bridge.

Please let me know, if you have any specific question. SAP’s Experts from SAP Data Warehouse Product Management & Strategy, and SAP Data Warehouse Development are involved in this topic.

Thanks to my colleagues Klaus-Peter, Gordon, Dirk, and Udo for their support.

Best regards,
Deniz

 

 

 

Assigned Tags

      38 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Mehmet Ince
      Mehmet Ince

      Great blog Deniz! Thank you very much. Very valuable and innovative for our customers.

      Author's profile photo Frank Riesner
      Frank Riesner

      Hi Deniz,
      great blog providing deep insight into the interrelation of the BW Bridge space and the native DWC spaces within DWC. One question please: You mention the ODP source system types which are leveraged to consume onprem sources for BW Bridge. What about other source system types which customer BW landscapes use as well, e.g. DBConnect, UDConnect, WebService etc... Can you also provision data into BW Bridge based on these interfaces?

      Thanks a lot - Frank

      Author's profile photo Glen Leslie
      Glen Leslie

      No, this is not possible.  The BW Bridge is the BW/4HANA Codeline and only supports ODP data sources.

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hi Frank,

      thank you for your feedback!

      As my colleague Glen has already answered, SAP BW bridge is only intended for ODP-based source systems (ODP-SAP, ODP-BW, ODP-CDS, and ODP-SLT). The source system must support ODP 1.0 (see SAP Note 1521883) or ODP 2.0 (see SAP Note 1931427). A Cloud Connector serves as a link between the on-premise source system and the SAP Data Warehouse Cloud, SAP BW bridge tenant which is technically based on an ABAP Platform in SAP BTP. RFC is used as a protocol for data exchange between on-premise source systems and SAP BW bridge.

      Other source system types such as DBConnect, and UDConnect have to be converted to SAP Smart Data Integration (SDI) and then have to be connected directly to the SAP Data Warehouse Cloud (Core) environment.

      Best regards,
      Deniz

      Author's profile photo Govindasamy Bhaskaran
      Govindasamy Bhaskaran

      Excellent Blog

      Author's profile photo Arvind kumar
      Arvind kumar

      Excellent blog, will it allow also to  access BW Planning data model and enable to do planning through remote table, without moving data in to DWC or in sap analytics cloud.

      Regards,

      Arvind kumar

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hi Arvind,

      Many thanks for your feedback!

      Add-ons are not supported in SAP BW bridge. Therefore, planning is not available within SAP BW bridge. In this regard, SAP positions SAP Analytics Cloud Planning as the planning application, and in the future (earliest end of 2022) SAP Data Warehouse Cloud (Core) as the planning foundation for the data.

      Best regards,
      Deniz

      Author's profile photo Bhavani Krothapalli
      Bhavani Krothapalli

      Hello Deniz,

      Great to see the detailed write up about Bridge!  Very nicely articulated!

      Best Regards, Bhavani

      Author's profile photo Sebastian Wiefett
      Sebastian Wiefett

      Hi Deniz,

      very valuable content, thanks for that!

      Regards
      -Seb.

      Author's profile photo Andreas Worch
      Andreas Worch

      Hi Deniz,

      you can use a Calculation View generated from BW/4HANA to build an SAP DWC data model.

      The Calculation Views can be found as runtime object in the SAP HANA schema SYS_BIC.
      If it is a Calculation View based on a SAP BW/4HANA Composite Provider, you get automatically the master data (Nav. Attributes, Texts) delivered with it.
      This saves the repeated construction of a star schema in the SAP DWC.
      Otherwise, the BW/4HANA connections between the transaction data and master data in the SAP DWC would have to be reconstructed manually.

      BW/4%20CompositeProvider

      BW/4 CompositeProvider

       

      SAP%20DWC%20Analytical%20Dataset

      SAP DWC Analytical Dataset

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hello Andreas,

      Thank you for your input. This point is in fact just a current weakness. Here, however, it is planned that this "star schema" will also be made known to SAP Data Warehouse Cloud (Core). For this purpose, SAP will probably already create associations on the remote tables, which will then also remain in place during the "Share" step. Stay tuned for the coming releases, and check out the roadmap.

      Best regards,
      Deniz

      Author's profile photo Daniel Klein
      Daniel Klein

      Thanks for the blog.

      Additionally, the conversion will be available for SAP BW/4HANA 2021 (shell and remote conversion)

      Does that mean BW/4HANA 1.0 and 2.0 customers have to upgrade to BW/4HANA 2021 first? I did not find anything about lower BW/4 releases in the roadmap.

      Author's profile photo Sebastian Wiefett
      Sebastian Wiefett

      Hello Daniel,

      current state of planning is that we deliver the Tool supported conversion in Q1/2022 affecting BW 7.4/7.5. With Q2/2022 we plan to deliver the tool supported conversion for BW 7.3.

      Please be aware that these dates are supject to change. Please check the Roadmap regular.

      Thanks and Regards
      -Seb.

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hello Daniel,

      Thank you very much for your feedback. I hope my effort is effective and it goes down well.

      Exactly, you got it right out of the blog post. This means that customers with an SAP BW/4HANA 1.0 & 2.0 will have to upgrade to SAP BW/4HANA 2021. So the prerequisite for SAP BW/4HANA migration to SAP BW bridge is SAP BW/4HANA 2021.

      Kind regards,
      Deniz

      Author's profile photo Thomas Baer
      Thomas Baer

      Hi Deniz,

      thanks for this very comprehensive blog - good work!

      Author's profile photo Marcelo Viveiros
      Marcelo Viveiros

      Good work, thanks for share with us

      Author's profile photo Martin Joveski
      Martin Joveski

      Deniz, excellent work!

       

      Thanks a lot for sharing this with the community.

      Author's profile photo Tim Huse
      Tim Huse

      Hi Deniz,

      this is a great blog post!

      Very valuable and nice to have a youtube video with the end-to-end-scenario, too.

       

      Best wishes, Tim

      Author's profile photo Seshupraveen Cherukuri
      Seshupraveen Cherukuri

      Hi Deniz,

      Is BW Bridge is going to replace the existing on solution BW/4 HANA in Future.

      As we already have BW/4 HANA which was integrated with SAC and the BW/4 HANA can connect to Non sap sources as well.

      On which type of scenarios the Business needs to go with the BW Bridge integration with DWC instead of BW/4 HANA.

      Would like to understand what are the benefits of using this BW Bridge except the cloud experience.

       

       

       

       

       

       

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hi Seshupraveen,

      No, the SAP BW bridge is not replacing SAP BW/4HANA. It is offering a bridge to the public cloud for our SAP BW NetWeaver or SAP BW/4HANA customers, as SAP Data Warehouse Cloud is the strategic public cloud solution. SAP BW/4HANA is the strategic offering for private cloud or on premises deployments, which is also underlined with the long-term support commitment until 2040.

      Kind regards,
      Deniz

      Author's profile photo Vivek Chaudhary
      Vivek Chaudhary

      Excellent Blog

      Author's profile photo Ian Dempsey
      Ian Dempsey

      Great blog post Deniz, good information for all involved with DWC and our customers!

      Author's profile photo Muhammad Zubair Khan
      Muhammad Zubair Khan

      Hi Deniz,

      It's a great blog about new feature in the SAP Data Warehouse world (cloud). Good content Especially the end-to-end scenario on YouTube, very helpful.

      Thanks for the sharing.

      Best Regards,

      Zubair

       

       

      Author's profile photo Patricia Shor
      Patricia Shor

      Nice Post! Thanks for sharing such an amazing article, really informative, it helps me a lot.

      Author's profile photo Paul Vatter
      Paul Vatter

      Hi Deniz

      thanks for your blog!

      Am I interpreting figures 4 and 5 correctly, that the BW bridge is based on a separate HANA cloud instance and is not "just a space / schema" of DWC?

      I have the fear that this might cause some unnecessary latency due to temporary data transfers over the network during the story execution...

      Thanks and best regards

      Paul

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hello Paul,

      Thank you very much for your feedback. I hope the blog is helpful.

      That is correct, SAP BW bridge is running on SAP HANA Cloud in a separate ABAP tenant. SAP BW bridge will be deployed to the main SAP Data Warehouse Cloud tenant, thereby enabling to access ingested data via cross-space sharing with regular SAP Data Warehouse Cloud Spaces and data.

      Best regards,
      Deniz

      Author's profile photo Dirk Umbach
      Dirk Umbach

      Hi Deniz,

      thanks for you blog.

      I am interesting how an integration of a composite provider is working? In your demo you are using a ADSO and info-objekt data. This join is typically allready done in a composite provider.

      Is there also an automatic integration? If you designed a complex data model, e.g. a composite provider with 40 part providers, 500 attributes (approx 300 nav-attributes) and 200 key figures. How should the be managed?

      As you mentioned the OLAP and authorization part will be dumped. Will the OLAP and authorization part of the DWC enhanced to manage such complex scenarios as in BWMT-query designer and BW data authorizations?

      Best regards, Dirk

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hello Dirk,

      Thank you for your feedback and your interest.

      In general, it will also be possible to access the Composite Provider of the SAP BW bridge environment. At the moment, it is not known whether and what restrictions there will be. Basically, we have included the CompositeProvider (HCPR) as a staging object in the SAP BW bridge environment for the time being. Therefore, extraction from the HCPR via remote tables will also be possible. In future, we will map the join from ADSO to the InfoObjects by declaring associations in the remote tables.

      OLAP engine and OLAP-dependent functionality (e.g. analysis authorizations, query as info provider, query execution) is not supported within SAP BW bridge. This needs to be adopted within the SAP Data Warehouse Cloud (Core). The functionality within SAP Data Warehouse Cloud is constantly being enhanced. Queries that are available as metadata in the SAP BW bridge environment, become available in SAP Data Warehouse via SAP BW/4HANA Model Transfer. For the next releases, keep up to date and have a look at the roadmap.

      Best regards,
      Deniz

      Author's profile photo Frank Riesner
      Frank Riesner

      Hi Deniz,
      I understand the BW Bridge is a SAP BW/4HANA system on an ABAP stack in the public cloud.
      What release is it? And will it be upgraded regularly when a new SP is released for the standard onprem release?
      Thanks - Frank

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hello Frank,

      Thank you for your question, and your interest.

      The SAP BW bridge environment is actually not just an SAP BW/4HANA system in the cloud. It is a different product, with an independent release cycle. As it is a cloud product, it regularly receives updates.

      Kind regards,
      Deniz

      Author's profile photo Mohammed Wayeez
      Mohammed Wayeez

      Hi Deniz,

      Can a Traditional DSO in BW 7.5 be migrated to SAP BW Bridge as an Advanced DSO which is then rendered as Remote Table in DWC.

      Assuming we don't need to convert Traditional DSO as a ADSO as a prerequisite to start using SAP BW Bridge.

       

      Regards,

      Wayeez

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hello Wayeez,

      Thank you for your question, and your interest.

      SAP BW Customers will have the option in 2022 to convert their existing on-premises investments to the cloud via remote, and shell conversion. In Q1/2022 the SAP BW bridge conversion will be offered for SAP BW 7.4, and SAP BW 7.5 systems (initially as shell conversion, followed as remote conversion). With this, it is possible to convert SAP BW objects into the SAP BW bridge environment via Conversion Tools. (The classic DSO is also included).

      Best regards,
      Deniz

      Author's profile photo Max Bodendörfer
      Max Bodendörfer

      Hi Deniz,

      a bit out of context question - Hopefully you still able to answer 🙂

       

      I am asking myself if it is possible to write Data back from SAP DWC to a SAP BW/4HANA.

      I can see pulling data from tables of the SAP DWC HANA DB via SDA, or?

      And what about Pushing data from SAP DWC to the SAP BW/4HANa ...via Data Flows?

       

      Best Regards,

      Max

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hello Max,

      this question isn't directly related to SAP BW bridge. But of course, I can also answer this one.

      It is possible to generate a technical SAP HANA Cloud User (Space Database User) for the relevant SAP Data Warehouse Cloud Space. While creating this technical user, the authorisations of this user are also defined (Enable Read Access (SQL), Enable Write Access (SQL, DDL, & DML), etc.). The data can then be consumed via this technical user within SAP BW/4HANA using SAP Smart Data Access, or SAP Smart Data Integration. SAP Smart Data Access, and SAP Smart Data Integration utilize virtual tables so that the current status of the SAP Data Warehouse Cloud tables can be accessed within SAP BW/4HANA. The data can then be used within SAP BW/4HANA either completely virtually via an OpenODS View or persistently stored in an advanced Data Store Object.

      The DataFlow object of SAP Data Warehouse Cloud is not relevant for this scenario.

      If you have more detailed architecture-related questions, feel free to call me. Just send me an email.

      Best regards,
      Deniz

      Author's profile photo Ibrahim Tamayo Blanco
      Ibrahim Tamayo Blanco

      Hi Deniz:

      Thanks for your blog.

      I want to ask you about Hierarchy support in BW Bridge and DWC.

      All the solutions that I have reviewed about implementing hierarchies in DWC so far, are based on importing external file as CSV or mapping CDS views, or BW Hierarchy tables. But to obtain the  required structure of parent-child columns, according to the DWC design, you need to manipulate  those tables and create a hierarchy view to be able to associate it to the Attributes. And in S4 and in BW4 these structures are standards.

      I was hoping BW Bridge will support Infoobjects Hierarchies automatically, but I don't see it.

      Is there any standard solution now or in the future for consuming BW hierarchies directly in DWC without additional modeling or importing?

      Thanks in advance.

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hi Ibrahim,

      thank you for your feedback and your interest.

      It is possible to maintain hierarchies within the SAP BW bridge environment. We plan to make these hierarchies available via import functionality within the SAP Data Warehouse Cloud Core. This means that, in addition to master data attributes, and master data texts, an InfoObject would also offer remote tables for the hierarchies in order to import them. The foundation for this is currently in development for hierarchy handling in SAP Data Warehouse Cloud. Stay tuned for the coming releases, and check out the roadmap.

      Best regards,
      Deniz

      Author's profile photo Koen Van Dijck
      Koen Van Dijck

      Thank you for the great video you recorded and this blog.

      I am currently working at a customer implementing DWC on SAP ECC systems in combination with group reporting in S/4HANA private cloud (RISE).

      Is BW bridge the only solution to make use of the delta mechanism of BW extractors on SAP Source systems? I have been looking in blogs, but found little or nothing on this matter. I can access the BW Datasources without a problem when they are activated (and ODP enabled), but I guess this only supports full loads. As an example we need Datasource 0FI_GL_4.

      When is BW Bridge available and is it installed by SAP? 

      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hello Koen Van Dijck,

      Thank you for your feedback. I'm glad you like the blog post and the video.

      Data Flows in SAP Data Warehouse Core do not support deltas from ODP extractors. If remote tables are used, you can use RealTime Replication for the ODP extractor sources to achieve something similar. You can also have a look at the First Guidance Document Data Integration for ABAP Source Systems.

      SAP BW bridge is already available as a greenfield approach. If a customer wants to use SAP BW bridge, a provisioning process can be triggered by SAP sales. The customer contacts Sales and the order form with the (additional) CUs then triggers the installation.

      Kind regards,
      Deniz