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). A dedicated blog post is available, see Conversion to SAP Data Warehouse Cloud: Conversion Paths and Cloud Transformation Steps.

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 2021
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.

Limitations of SAP Data Warehouse Cloud, SAP BW bridge

  • Application development is not supported in SAP Data Warehouse Cloud, SAP BW bridge. Any app building should be done “natively” using the SAP BTP app building on SAP HANA, for that customers need to license and use the stand-alone version of SAP BTP.
  • Customer do not have the option to connect with SAP GUI to SAP Data Warehouse Cloud, SAP BW bridge.
  • Connection scenarios are limited to ODP source systems only.
  • Queries are not supported.
  • No support for the OLAP engine and functionality dependent on the OLAP engine, e.g., analysis authorizations, query as InfoProvider, query execution.
  • The generation of External SAP HANA Views is not supported.
  • Planning is not available in SAP BW bridge. Therefore, SAP positions SAP Analytics Cloud Planning as the SAP Planning Application and SAP Data Warehouse Cloud as the Planning foundation for the data. SAP Analytics Cloud Planning is the strategic direction for planning. Also, as highlighted already at SAP SAPPHIRE NOW 2021, future releases will make SAP Data Warehouse Cloud the foundation for SAP’s planning solutions.
  • In SAP BW bridge, add-ons (such as BCS, DSiM, TPM, …) are not supported. The use of SEM-BCS or BCS/4HANA is not supported in SAP Data Warehouse Cloud – explore other solutions like SAP Group Reporting instead.
  • For DataStore objects, cold store and DTO handling are not supported.
  • For CompositeProviders, temporal joins are not supported.
  • For DTPs, variables as selection criteria are not supported.
  • The following process types are not supported in SAP Data Warehouse Cloud, SAP BW bridge:
    ABAP, ADSOOLR, ARCHIVE, BDHTASKWF, BDHVFLOW, BOBJDSJOB, BOBJEVENT, CL_ARCHIVE, COMMAND, CPS_EVENT, CPS_JOB, DTO_EXEC, HAAP, OHD_NOTIFY, PLSEQ, PLSWITCHL, PLSWITCHP, REMOTE, RS2HANA, RSDASYB_PM, RSSDA_STAT, SDI_INIT, WORKFLOW

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. You will find more information about what is new or changed with SAP BW bridge on the SAP Help Portal: New Features and Changes in SAP Data Warehouse Cloud, 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

      78 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 Former Member
      Former Member

      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 Andrei Dorfman
      Andrei Dorfman

      Hi Deniz!

      Thanks for a wonderful post!

      And thanks for your answer about DWC vs. on-premise, it's good to know that.

      I would like to discuss this further if it is possible for you. As we can see, SAP BW Bridge opens more data staging scenarios for DWC and it is actually getting closer to on-premises BW/4HANA in terms of staging capabilities, does it sound right? And having such upsides as user-driven design for data flows (among many others), I think DWC is now becoming more attractive in situations where only BW/4HANA was capable before. And as you mentioned, DWC is not a replacement for BW/4HANA, but with the BW Bridge, I think these two solutions may have similar offerings and start to compete in the sense that customers will now start to see it as a cloud vs. on-premise choice rather than DWC vs BW/4HANA choice. I guess DWC will now cover much more scenarios than DWC alone, possibly covering what was available only as a part of BW/4HANA before. Maybe I missed the point here and I'm not a marketing expert, but for SAP BW consultants it would be great to understand what companies could potentially use DWC in the coming years and what companies may migrate to the DWC to better choose the next skills to upgrade. Could you share your thoughts on that, please? For example, I imagine that maybe the banking industry will not be so quick to adopt DWC as it is a cloud solution, but many other industries would consider migration to DWC in the coming years, given the pros that DWC offers. Sorry for a bit longer question, but do you think it is something that you could comment on, please?

      I would be happy if you could reply to me, but given that the question is so complicated and probably already has been answered elsewhere, I will totally understand if it will be not possible for you to answer.

      Thanks & Best Regards,
      Andrei

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

      Hi Andrei,

      Thank you for your feedback, and your interest.

      All in all, you correctly understand the concept of SAP BW bridge. Regarding your question: SAP Data Warehouse Cloud is industry-independent, specific industries do not really stand out. Companies decide individually, whether they want to start their transformation journey towards the cloud.

      Best 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 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 by a transfer mechanism. 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

      Author's profile photo Anup Kulkarni
      Anup Kulkarni

      Hi Deniz,

       

      Great blog with attention to details!

      With respect to greenfield approach (S/4 HANA On Premise being ERP), is there a clear documentation that addresses the dilemma "To bridge or Not to bridge"? As I understand from the first guidance document, most UPSERT compatible ODP S-API extractors and CDC based CDS extractors should work for delta extraction without a need for BW bridge. It is also stated that DWC only allows "Real-Time" delta extraction (an equivalent of streaming process chain in BW). What is the harm of relying entirely on this approach especially when SAP has made it clear that eventually all extractors will be CDS based?

      Secondly, is BW bridge a stop-gap arrangement for greenfield scenario while SAP is simultaneously working on enriching the core DWC to allow seamless delta extraction of everything extractable from S/4 HANA system? If this is the case, doesn't it make sense to wait until DWC matures rather than investing in the bridge? I do understand that standalone DWC will not support ABAP runtime but apart from that, is there any benefit of investing in the bridge when DWC is maturing day by day?

      Thirdly, what's the future of BW bridge, is this a temporary tool? do we see it as strategic tool that goes hand-in-hand with DWC?

       

      Thanks,

      Anup

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

      Hi Anup,

      thank you for your feedback, and your great question!

      Extraction-enabled CDS views can be used directly as a source for SAP Data Warehouse Cloud Core environment as an alternative to SAP BW bridge. Here it is possible to use the Real-Time Replication feature to implicitly map a delta. For CDS views in SAP S/4HANA on-premise environment, this is done via the SAP SDI ABAP adapter, and for CDS views in SAP S/4HANA Cloud environment, this is done via the SAP SDI CloudDataIntegration adapter.

      If customers have extensive ODP S-API extractors in use, the recommendation here is clearly to connect them to the SAP BW bridge environment. Most ODP S-API extractors cannot be connected to the DWC using the delta procedure. The reason for this is that primary key definitions are missing. For the highly demanded extractors 0FI_ACDOCA_10 and 0FI_ACDOCA_20, it has been confirmed that a modification to the key fields RLDNR, RBUKRS, PERIV, FISCYEARPER, BELNR, DOCLN is possible (See SAP Note 2341038). In addition to the delta processing, SAP BW bridge offers SAP BW functionality directly in the public cloud, such as ABAP logic, business content, partitioning, currency conversion, aDSO-Changelog functionality, etc. SAP BW bridge also has a key role, when customers want to protect their existing investments, keep them, and convert them to the public cloud.

      SAP Data Warehouse Cloud is SAP’s strategic target solution for all data warehousing use cases, and SAP BW bridge is a SAP Data Warehouse Cloud feature that provides a path to the public cloud for SAP BW NetWeaver & SAP BW/4HANA customers. SAP BW bridge will be available as long as customers integrate on-premises SAP Business Suite data in their SAP Data Warehouse.

      Best regards,
      Deniz 

      Author's profile photo Ashwini Deshpande
      Ashwini Deshpande

      Really informative blog. Thanks

      Author's profile photo Chiranjeevi Alla
      Chiranjeevi Alla

      Hello Deniz

      it is really helpful and informative for BW consultants.

      what is the scope of ABAP in DWC?

      how do we transition the ABAP customisations to DWC from BW?

      Do we have predefined logics in DWC?

       

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

      Hi Chiranjeevi,

      thank you for your interest and feedback.

      ABAP is not supported in the SAP Data Warehouse Cloud Core environment. Here it is possible to develop in Python, SAP HANA SQL, and SAP HANA SQLScript.

      ABAP is supported within the SAP BW bridge environment. In the future, it will be possible to convert existing ABAP coding into the SAP BW bridge environment. Customers can create ABAP code according to SAP BTP ABAP environment coding conventions for custom-logic transformations in SAP BW bridge. Application development is not supported in SAP BW bridge. Any app building should be done “natively” using the SAP BTP app development.

      Best regards,
      Deniz

      Author's profile photo Umesh Kumar
      Umesh Kumar

      Hi Deniz,

      Really very nice blog which gives overall picture of SAP BW Bridge .

      I was wondering if there is any Trial version to play with it? In Datawarehouse cloud I cannot create a space with space type ''SAP Bridge" as it seems it can be only provisioned by SAP.

      Is there anything planned for BW Bridge Trial version? I wanted to connect with BW Trial (on Amazon cloud) . Pls. suggest.

      Thanks,

      Umesh

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

      Hi Umesh,

      Thank you for your positive feedback, and your interest.

      When using the trial version of SAP Data Warehouse Cloud, there are some product limitations at the moment. The SAP BW bridge feature is not available in the Low Touch Trial. This is one of the limitations, see SAP Note 3007887.

      Please reach out to your account manager and request a High Touch Trial (former known as PoC), or licensed tenant to test, and execute the SAP BW bridge feature.

      Kind regards,
      Deniz

      Author's profile photo Dean Farrow
      Dean Farrow

      Excellent blog - explains this subject very well and in a very clear way.  Great job

      Author's profile photo Bartlomiej Poteraj
      Bartlomiej Poteraj

      Hi Deniz,

      thank you for explaining the BW Bridge concept.

      Some additional questions:

      1. Can you deploy objects from BI Content in BW bridge?
      2. Is the HANA database behind BW bridge available for use in Eclipse? (e.g. for SQL console)
      3. Are mainstream 3rd party connectors supported for extracting data out of BW Bridge?
      4. Are the licence conditions, for transferring data from BW bridge to 3rd party solution, similar to those regarding BW/4HANA?
      Author's profile photo Deniz Osoy
      Deniz Osoy
      Blog Post Author

      Hi Bartlomiej,

      thank you for your interest and your feedback.

      1. Yes, Content also exists within the SAP BW bridge environment. An adapted version of the SAP BW/4HANA content add-ons, optimized for SAP BW bridge are supported.
      2. No, the SAP HANA Cloud database of the SAP BW bridge environment is not available for external access.
      3. No, 3rd party connectors are not supported for extracting data directly out of the SAP BW bridge environment. This needs to be adopted in SAP Data Warehouse Cloud Core, after the data is consumed by remote tables.
      4. See answer #3. However, SAP BW bridge is an independent feature that relates only to SAP Data Warehouse Cloud, and has in fact no relation to SAP BW/4HANA.

      Best regards,
      Deniz

      Author's profile photo Poshan Kumar Reddy Ponnamreddy
      Poshan Kumar Reddy Ponnamreddy

      .

      Author's profile photo Shoaib Haider
      Shoaib Haider

      Hi Deniz,

      Great and very informative blog here. I have the following questions after reading the whole blog if you could perhaps comment on the same.

      1. If we have built some BW objects using Embedded BW (7.5) in S/4HANA 1610 system, can we bring some of those BW 7.5 artifacts to DWC using the new BW Bridge concept? Or is it totally for fully functional and standalone BW Netweaver?
      2. Is DWC BW Bridge a separate subscription or it comes free of cost for the DWC customers?
      3. Can we bring in S/4HANA CDS views from a S/4HANA OP system to DWC?
      4. Can we Persist some of the data from the S/4HANA 1610 and 2020 system tables in a DWC table and build some further logic/calculation/join using the data builder/data flows?

      Thanks

      Best Regards

      Shoaib

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

      Hi Shoaib,

      thanks for your feedback, and your interest.

      1. Yes, an Embedded BW (release 7.5) can be used as a sender system for a conversion to SAP BW bridge.
      2. SAP BW bridge is an additional feature for SAP Data Warehouse Cloud. Here, the customer needs additional capacity units explicitly for the SAP BW bridge environment. The customer contacts Sales and the order form with the (additional) CUs then triggers the installation. Feel free to check the Pricing Calculator.
      3. Yes. For CDS views in SAP S/4HANA on-premise environment, this is done via the SAP SDI ABAP adapter, and for CDS views in SAP S/4HANA Cloud environment, this is done via the SAP SDI CloudDataIntegration adapter.
      4. Yes, persisting data in SAP Data Warehouse Cloud is possible. There are various options here, e.g., via the Remote Table Monitor (table replication), View Persistency Monitor (snapshot option).

      Kind regards,
      Deniz

      Author's profile photo Shoaib Haider
      Shoaib Haider

      Thanks Deniz for the clarity. Appreciate it

      Author's profile photo Paul Vatter
      Paul Vatter

      hi Deniz Osoy

      regarding 1: Embedded BWs are BW 7.5x where x is > 0 -  so e.g. 7.55 or 7.54.

      As far as I know they are not supported for the conversion tools into BW/4 so I would be surprised if this would have changed. Could you maybe recheck this?

      Thanks and best regards

      Paul

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

      Hi Paul,

      Thank you for your remark. Any SAP BW system that exists "inside" an SAP ECC or SAP S/4HANA system is considered an Embedded SAP BW, regardless of the version (This is valid since release 7.0). Therefore if you have software component SAP_BW installed along with SAP ECC or SAP S/4HANA, it is an Embedded SAP BW no matter its version. The difference here is that versions 7.51+ have specific functionalities to be used along with SAP ECC or SAP S/4HANA, which older versions do not. See SAP Note 2773651 for details. 

      An embedded SAP BW system Release 7.50 & 7.51 can be used as a sender system for a conversion towards SAP BW bridge.

      If the embedded SAP BW has a release > 7.51, then there are no coding fixes provided by the SAP support team. This means that the existing conversion tasklists in the sender system are no longer updated after delivery (SP0). A conversion towards SAP BW bridge with an embedded BW system > 7.51 is not possible, as the corresponding functionality is not available. If the embedded BW system is Release > 7.51, a possible recommendation would be to transfer the objects to a standalone sandbox SAP BW 7.50 system via a transport request, and to use this system as the sender system.

      Best regards,
      Deniz

      Author's profile photo Paul Vatter
      Paul Vatter

      Thanks for your detailed reply, Deniz!

      Author's profile photo Lucas Gaston Lazzarotto
      Lucas Gaston Lazzarotto

      Hi Deniz!

       

      Excellent blog, and very clear information. I would like to ask you some questions, hopefully is not lat for it 🙂

      Today, we are currently in BW (7.5) on HANA (2) on promise. with low performance because of size, complexity and not fully LSA++ development (we still have some 3.x objects). The idea is to get more than an simple 1:1 migration (using BW4 conversion tool), so basically we need optimization and re-engineering of most of our flows, so the conclusion is that we would like to go green fields, ...so the question are:

      1- With the  BW Bridge, it is possible to migrate some flows, in order to save at least the staging area, MD, etc.?

      2- If not, it is possible to create a high complexity dataflows using SAP DWC, or because of this complexity, is better to re-build the solution in BW4 cloud instance?

      3- If (once SAP release the migration option) we move some flows to SAP DWC, what would happens with the security around it? (roles/analytical privileges already created)

      Thank you very much for all the information, and thank you in advance for answering the questions 😉

      Best regards,

      Lucas

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

      Hi Lucas,

      thanks for your feedback and your interest.

      1. Yes, partial migrations are also supported, where you can select a subset of data flows. SAP BW Customers have the option in 2022 to convert their existing on-premises investments to the cloud. With this, it is possible to convert SAP BW NetWeaver and SAP BW/4HANA objects into the SAP BW bridge environment via Conversion Tools. (See Roadmap)

        Attention regarding your 3.X objects: The Transfer Cockpit is not able to convert legacy 3.x data flows (originating in SAP BW systems before release 7.0). Such 3.x data flows must be migrated to corresponding 7.x data flows before a conversion to objects compatible with SAP Data Warehouse Cloud, SAP BW bridge is possible. As soon as 3.X objects are in use in any way, these objects must be converted (RSMIGRATE) to 7.X objects, and can then be converted to the SAP BW bridge environment.

      2. The SAP BW bridge environment is suitable for complex data flows, based on SAP ABAP sources (ODP context). It is also possible to create data flows directly in the SAP DWC Core environment, which is especially relevant for non-SAP sources and Cloud sources.

        Regarding strategic positioning, we would have to analyze your system to see whether SAP Data Warehouse Cloud or SAP BW/4HANA Private Cloud Edition (PCE) makes sense. A general recommendation is not possible.

      3. Here I would refer you to the blog post of my colleague Heiko Schneider (responsible for authorizations on the SAP DWC Product Management side).
        https://blogs.sap.com/2021/09/23/introducing-remote-authorizations-from-sap-bw-4hana-for-sap-data-warehouse-cloud/

      Best regards,
      Deniz

      Author's profile photo Stefano Voltolina
      Stefano Voltolina

      Hi Deniz!

      Excellent blog!

      I was wondering when remote conversion will be available for 7.4/7.5BW system. At the moment I see only shell conversion is available.

      Finally, I have searched thoroughly but have not found any precise instruction about the stesp to follow for a shell conversion and for a remote one, in case of migration from 7.5BW environment to DWC.

      Any answer would be apreciated.

      Regards,

      Stefano

       

       

       

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

      Hello Stefano,

      Thank you for your feedback and interest.

      1. It is planned that the Remote Conversion option for SAP BW bridge will be available with release 2205 by 21st May 2022. For SAP BW systems on releases from 7.30 to 7.50 running on SAP HANA or Any-DB, and for SAP BW/4HANA 2021, a remote conversion is planned for SAP Data Warehouse Cloud 2205. For that conversion type, a newly provisioned SAP Data Warehouse Cloud, SAP BW bridge is needed. The Transfer Cockpit can be used to migrate selected data models into an SAP BW bridge tenant and to perform a remote data transfer into that tenant.
      2. A conversion guide explicitly for SAP BW bridge will be available soon.

      Best regards,
      Deniz

      Author's profile photo Stephan Schork
      Stephan Schork

      Hello Deniz,

      thanks a lot for this great blog!

      Best regards

      Stephan

       

      Author's profile photo Ramon Alberto Sanchez Bujama
      Ramon Alberto Sanchez Bujama

      Hello,

       

      I have a couple of doubts,

      Does it possible to do extractions filtered from bw to dwc? for example, extract data dynamically (current_date -1 or other kind of rules)

      Does it possible use delta extractions?

       

      Regards

      Ramón Sánchez.

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

      Hi Ramón,

      thanks for your question and your interest.

      1. SAP Data Warehouse Cloud offers several ways to control the volume of data that is loaded in your remote table. From the table editor of the Data Builder, you can remove the unnecessary columns, you can define a central filter to load only the data that is needed, and you can add new columns available in the source, or reinsert previously excluded columns.
        Attention: Customers can select existing values only. No dynamic filtering such as "last 3 years" is supported at the moment. (See SAP Help). As a workaround, you could create an SQL view within SAP DWC Core that includes an expression "CURRENT_DATE - 1" in your case.
      2. In SAP Data Warehouse Cloud it is possible to use the Real-Time Replication feature to implicitly map a delta. For ABAP ODP sources, real-time replication is supported for InfoProviders with a change log. This can be: DataStore objects (advanced) with data activation and change log, Standard DataStore objects (classic), InfoObjects. Real-Time Replication is also supported for all ABAP CDS views with primary key that are delta-enabled. If customers have extensive ODP S-API extractors in use, the recommendation here is clearly to connect them to SAP BW bridge. Using the delta procedure for most ODP S-API extractors is not supported when connecting to SAP DWC Core. The reason for this is that primary key definitions are missing.

      Best regards,
      Deniz

      Author's profile photo Lakshmi Sankaran
      Lakshmi Sankaran

      Hi Deniz

      Thanks for such a fantastic blog. I have a couple of questions and confirmation from your and community expertise.

      1. with respect to the software components in SAP BW 7.5, when I read here there is no SAP GUI support, that means we don't have any SAP BW Bridge software installation components right on top of a SAP BW system? Please confirm.
      2. For all 3 implementation scenarios a BW Bridge space enabled in DWC is sufficient
      3. What is a typical project time line for such conversion in the 3 scenarios, am sure it varies based on object complexities. But will the db size/volume of data determine such time lines?
      4. as the conversation seems partially automated, we can choose the objects and flows we wish to convert/migration. Does this helps to manage project time lines and priorities for conversions?

      Thanks

      Lakshmi

       

       

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

      Hi Lakshmi,

      thanks for your feedback and your interest.

      1. SAP BW bridge is an additional feature for SAP Data Warehouse Cloud. An SAP GUI is not required to access the SAP BW bridge environment. SAP BW bridge is actually not just a component on-top of SAP BW On-Premises. It is a different product, with an independent release cycle.
      2. Yes, but the Hybrid-Scenario with SAP BW/4HANA actually works also without SAP BW bridge.
      3. It is not possible to give a general answer to this question. The effort depends very much on the number of objects, organizational structure, optimization needs, and type of conversion.
      4. Yes. Each transfer is based on a selection of a specific scope, a set of SAP BW objects, e.g. a data flow, that can be transferred together in a consistent way.

      Best regards,
      Deniz

      Author's profile photo Prafful Agrawal
      Prafful Agrawal

      Hi Deniz,

      Thanks for sharing the information.

      How do we address below issues :-

      1. How do we manage life cycle management in BW bridge ?
      2. In single DWC Tenant , can we create multiple BW bridge space to cater the need of 3-TIER landscape (Dev ,QUA , Prod ) ?

      Regards

      PA

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

      Hi Prafful,

      thanks for your feedback and your interest.

      1. In SAP Data Warehouse Cloud, SAP BW bridge, transports are carried out via gCTS (git-based Change and Transport System. This is controlled via the software component. For SAP Data Warehouse Cloud artefacts we recommend to use ACN for transports and for the SAP BW bridge objects you can use ABAP gCTS (works similar to ABAP transports in the on-prem world). Both transport mechanisms work independently, we recommend to (1) transport the SAP BW bridge objects first, expose the data and objects in the SAP BW bridge space and then (2) transport the SAP Data Warehouse Cloud objects on top.
      2. At the moment it is not possible to have multiple SAP BW bridge spaces in the same SAP DWC tenant. A 2-tier landscape is supported. You can combine an SAP Data Warehouse Cloud test tenant with SAP BW bridge as non-productive “DEV” system and a regular SAP Data Warehouse Cloud tenant with SAP BW bridge as productive “PROD” system. 

      Best regards,
      Deniz

      Author's profile photo Prafful Agrawal
      Prafful Agrawal

      Hi Deniz ,

      Thanks for your quick response .

      Regarding Point-2 --> While reviewing the BW bridge here , I can view multiple BW bridge space available in same tenant .how is it possible? Are these referring it to same source connection ? Refer snapshot :-

      Customer may have scenario like :-

      (A) Source connection -- > S4HANA , ERP & BW

      (B) Each source Connection have 3 tier landscape - DEV , QAS , PROD

      How the above scenario can be handed with single/Multiple BW Bridge space ?

       

      Regards

      PA

       

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

      Hi Prafful,

      1. At the moment it is not possible to have multiple SAP BW bridge Spaces in the same SAP DWC Tenant. Your screenshot above from my demo doesn't actually display multiple SAP BW bridge Spaces, the "DENIZBWBRIDGE" Space is of type SAP Data Warehouse Cloud and not SAP BW bridge.
      2. Currently a 2-tier landscape is supported. Different approaches can be considered here. For example, the source systems from DEV and QAS can be connected to the SAP Data Warehouse Cloud test tenant with SAP BW bridge as a non-productive "DEV" system. The source system from PROD, for example, can be connected to the regular SAP Data Warehouse Cloud tenant with SAP BW bridge as a productive "PROD" system.

      Best regards,
      Deniz

      Author's profile photo Prafful Agrawal
      Prafful Agrawal

      Hi Deniz,

      Thanks for your help.

      Based on your reply on Point-2, I have follow-up queries & sought clarification as follows :-

      1. Question --->Does we only support 2-tier landscape What if customer wants to go for 3-tier landscape ?
      2. Clarification Required --> It appears customers will have to manage the Bw Bridge space with Dev/QAS data i.e  Metadata objects related to BW will have single image in non-production BW bridge space . Customer will have to load data from development system for Unit  test cycle & thereafter truncate Dev data and load from QAS system to perform Integration test / User acceptance cycle .
      3. In continuation to above point --> Can we connect one BW bridge space with Multiple ODP enabled systems simultaneously (BW,S4HANA ,ERP) ?

      Regards

      PA

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

      Hi Prafful,

      1. Currently, a 2-tier landscape is supported.
      2. Yes, that would be one option. Of course, customers can decide individually how they would like to proceed. A general recommendation is not possible.
      3. Yes, several ODP-based source systems (ODP-SAP, ODP-BW, ODP-CDS, and ODP-SLT) can be connected to SAP BW bridge.

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

      Best regards,
      Deniz

      Author's profile photo Githen Ronney
      Githen Ronney

      Hi Deniz,

      Great Blog.

      I have couple of doubts. I really appreciate if you can help me here.

      BW bridge means, customers have to have BW and DWC licenses at the same time ?

      Bridge is a middleware which helps to expose your existing BW investments to public cloud DWC ?

      Is there anyway to convert existing BW system to DWC completely so that customers need not pay for BW anymore ? Something like a system conversion with SAP supported tool sets.

      Regards

      Githen

       

       

       

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

      Hi Githen,

      thanks for your feedback and your interest.

      1. No, SAP BW bridge is a feature for SAP Data Warehouse Cloud and therefore available independently of SAP BW and SAP BW/4HANA.
      2. SAP BW bridge is a feature for SAP Data Warehouse Cloud, that provides a path to the public cloud for SAP BW and SAP BW/4HANA customers. It enables connectivity and business content via proven SAP BW-based data integration (extractors) from SAP source systems. In addition, it provides staging layers of SAP BW to manage data loads (including deltas) with partitioning, monitoring, and error handling. This allows customers to leverage their existing SAP BW skills and protect their SAP BW investments in the public cloud.
      3. Yes, looking at conversion, SAP offers the possibility of a tool-supported move of SAP BW or SAP BW/4HANA investments to SAP Data Warehouse Cloud, SAP BW bridge.
        A dedicated blog post is now available, see Conversion to SAP Data Warehouse Cloud: Conversion Paths and Cloud Transformation Steps

      Kind regards,
      Deniz

      Author's profile photo Kamal Mehta
      Kamal Mehta

      Hi Deniz,

      First of all thanks for sharing the valuable information. I have few questions please:

      1. Is BW Bridge a mandatory step to consume Data flows built in BW 7.5 to DWC?
        • (ADSO's, Composite Provider, Info Objects ) : Can be consumed directly in DWC without BW Bridge. Can you confirm please.
        • (Non ODP extractors, SAPI extractors) can be consumed directly in DWC ?. If yes, Can you provide details. Also, confirm if they can be enabled for real time replication in DWC.
        • (Bex Query and components like variable, exits, conversions, authorization etc.) are not supported currently in BW bridge but can they be consumed in DWC directly.
      2. Non SAP Data sources connectivity:
        • Can you provide details/list of Non SAP connectivity/ data source supported in DWC.
        • We are checking options to merge data from SAP BW 7.5 and various other Non SAP data sources for consolidation reporting.
      3. SAC
        • Is SAC coupled with DWC. How existing SAC customers can take benefit of both the world DWC and SAC.
        • Any license/ cost benefits provided to existing SAC customers.

      Regards

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

      Hi Kamal,

      thanks for your feedback and your interest. If you have conversion-related topics, check out also SAP blog post Conversion to SAP Data Warehouse Cloud: Conversion Paths and Cloud Transformation Steps

      • 1a) No, SAP BW bridge is not mandatory when connecting SAP DWC to SAP BW 7.5. You can use the SAP BW connection type via Remote Tables in SAP DWC to access data from InfoObjects (characteristics), InfoProviders, or Queries as InfoProviders as well as from SAP ABAP dictionary tables. For legacy SAP BW systems that do not have the ABAP Pipeline Engine extension or DMIS Add-on installed, you can leverage Operational Data Provisioning (ODP) connectivity und use ODP extractors as sources in SAP DWC data flows. Note that ABAP Dictionary tables are not supported as sources in data flows.
      • 1b) If customers have extensive ODP S-API extractors in use, the recommendation here is clearly to connect them to the SAP BW bridge environment. Most ODP S-API extractors cannot be connected to SAP DWC using the delta procedure. Extraction-enabled CDS views can be used directly as a source for SAP Data Warehouse Cloud Core environment as an alternative to SAP BW bridge. Here it is possible to use the Real-Time Replication feature to implicitly map a delta.
      • 1c) Yes, in general it is possible to access queries within SAP DWC. See for example SAP Note 2932647 regarding supported and unsupported features.
      • 2) Yes, See SAP Help - Integrating Data and Managing Spaces in SAP Data Warehouse Cloud, here section “Connection Types Overview”
      • 3) Yes, definitely. SAP Analytics Cloud and SAP Data Warehouse Cloud are SAP’s strategic cloud solutions for Data Warehousing, Planning and Analytics. See the blog post by my colleague about: SAP Analytics Cloud & SAP Data Warehouse Cloud: Key Feature Overview.

      Best regards,
      Deniz

      Author's profile photo Sebastian Gesiarz
      Sebastian Gesiarz

      Hi Deniz Osoy

      Could you please tell me if the ABAP Pipeline Engine extension should be by default installed in BW/4?
      I noticed that some of the FMs listed for the BW (RFC based) connection which are a part of the ABAP Pipeline Engine are not available in BW4.

      Kind regards,
      Sebastian

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

      Hi Sebastian,

      the ABAP Pipeline Engine (APE) component is delivered via the DMIS add-on. For SAP BW/4HANA, DMIS 2018 SP06 or higher is required. So no, it is not available by default. In fact, there are APE components in SAP_ABA, but they are already technically outdated. For more information, check out this blog post by my colleagues: ABAP Integration – Software Delivery & Installation Aspects.

      Best regards,
      Deniz

      Author's profile photo Sebastian Gesiarz
      Sebastian Gesiarz

      Thanks!