Exposing SAP BW Bridge Objects to SAP Datasphere

You have created several objects in the SAP BW bridge and have already loaded data into the corresponding tables. You now want to integrate this content with data and objects from the SAP Datasphere core tenant. Your next step is to expose the SAP BW bridge objects as remote tables in SAP Datasphere (core tenant), which is called Import in the SAP Datasphere user interface.

This concept is recommended when the remote table is consumed in many different spaces. Perform the following tasks to enrich your SAP BW bridge data and make it available for SAP Analytics Cloud (SAC):

1. Import SAP BW bridge objects into SAP Datasphere as Remote Tables using the BW bridge connection.
2. Share the remote table with a customer space.
3. Create a graphical view or SQL view to combine the shared object data with other data of the customer space.
4. Create an analytic model to define further filters, key figures, and parameters that should be available in SAP Analytics cloud (SAC).

The following image shows an easier alternative.

You have a second option: Use the customer space as your starting point. The sharing and creation of a view is automatically done in the import process. This option is recommended if you need some BW bridge objects in just one space. You do not need to share objects manually. Moreover, SQL views are automatically created.

For this accelerated procedure, perform the following tasks to enrich your SAP BW bridge data and make it available for SAP Analytics Cloud (SAC):

1. Import SAP BW bridge objects into SAP Datasphere as Remote Tables and SQL view directly to a target space using the BWBRDIGE connection.
2. Create a graphical view or SQL view to combine the shared object data with other data of the customer space.
3. Create an analytic model to define further filters, key figures, and parameters that should be available in SAP Analytics cloud (SAC).

From SAP Datasphere core tenant, you need at least two spaces: a BW bridge space and a customer space. In your customer space, you can create connections to other sources, such as files, non-SAP sources, or databases and upload data from them. In the BWBRIDGE space, a dedicated connection called BWBRDIGE of type SAP Datasphere, SAP BW bridge is available. This SAP BW bridge connection differs from other connection types, as it can't be created or modified. It is being generated by default by SAP when the SAP BW bridge component is provisioned.

The first step to make data available in SAP Datasphere core tenant is to import the required BW bridge objects. This does not replicate its data, but allows access to it via a remote table. However, you are not allowed to generate objects manually in the BW bridge space. The only way to generate objects is via import.

Watch the following video to learn how the import to SAP BW bridge Space works.

Another option is to load values from BW bridge to the SAP Datasphere core tenant using transformation flow. When the source is a Standard ADSO with change log, the corresponding imported remote table has delta capture capabilities. They can be used for delta logic of transformation flow. In the transformation flow, you can change records with features of SAP Datasphere core tenant in a graphical editor.

Changes in source data are stored in a change log of a standard ASDO, ideally in Delta update mode for better performance, but even with full upload, only the changes are written to the change log. Metadata import generates a remote table with delta capture in SAP Datasphere core tenant. A transformation flow can read the delta capture information, process it, and fill a local table where the delta capture is reproduced. So, active records in the local table are up to date.

Let's sum up the SAP Datasphere space concept. In addition to the BW bridge space, there are customer-defined spaces. The definition of these spaces is tightly related to the authorization concept. Use them to foster collaboration within specific groups of users, and to separate the objects of one user group from objects of another user group. Only assigned users can work in a space as enabled and limited by the assigned space-related role (scoped role). This means, spaces are also secure areas created by an administrator, in which members can acquire, prepare, and model data. They are encapsulated to meet the specific demands of only the assigned users.

Cross-space sharing follows the concept to store data once and use it in many different contexts. By sharing data, organizations aim to avoid maintaining disconnected redundant data sets and keep a single source of data. There is no limitation as to what type of model or table can be shared.

In the case of SAP BW bridge, this concept is important because you cannot generate data builder objects manually in the BW bridge space. To generate objects on top of the generated objects, you need to set up one or more separate customer spaces, typically one space per topic. Then, to make the BW bridge objects and its data available, you must share the imported objects with the other space.

Suppose you have sales data from web applications, currency conversion rates, and hierarchies, and you want to integrate such external or local data with SAP data from SAP BW bridge. These values can be provided by the following types of models:

• Local tables for automatically replicated or manually updated values that are defined in SAP Datasphere core tenant and physically stored in its HANA cloud database.
• Remote tables that refer to an external source via a connection.
• Views on top of them with already transformed data.

If they are not already defined in the customer space for integration, you must share such objects with the same integration space.

Launch the following video to learn how to share the objects.

When your BW bridge objects are only used in one space, you can avoid the manual step of sharing models. When you import an object, a dependency analysis is performed in the background. All required objects are imported together with the selected object. In the background, remote tables are generated in the BW bridge space and shared with the target space of the import.

This is the most convenient way to import BW objects if you use them in just one space.

Launch the following video to learn how you can import data to any space.