Working with Remote Tables

Objective

After completing this lesson, you will be able to use remote tables in SAP Datasphere.

Remote Tables

Let's now explore how remote tables can be used for data provisioning.

Data Federation with Remote Tables

The figure shows an overview of different ways for data acquisition using SAP Datasphere connections: remote table (including federation, replication (snapshot and real-time), data flow, replication flow and transformation flow. The remote table federation is highlighted.

Data federation is a powerful data management strategy that enables seamless integration and efficient utilization of disparate data sources. In this approach, the data is left where it resides and virtualization techniques are used to provide a unified view.

In SAP Datasphere, a remote table is a virtual object that provides direct access to data residing in a source system.

The figure shows a screenshot of selecting an SAP HANA SQL View when importing a remote table.

You can use the option Import Remote Tables on the Data Builder landing page or the Repository Explorer to create a remote table.

Data Replication with Remote Tables

The figure shows an overview of different ways for data acquisition using SAP Datasphere connections: remote table (including federation, replication (snapshot and real-time), data flow, replication flow and transformation flow. The remote table replication (snapshot/real-time) is highlighted.

By default, when you import a remote table, its data is not replicated and must be accessed using federation each time from the remote system. You can improve performance by replicating the data to SAP Datasphere and you can schedule regular updates (or, for many connection types, enable real-time replication) to keep the data fresh and up-to-date.

The figure shows a screenshot of the option to define replication (snapshot/real-time) for remote tables.

The Data Integration Monitor offers the following data replication options for remote tables:

  • Snapshots:

    • Start Data Replication: Directly start a copy of the full set of data from the source in the background.

    • Remove Replicated Data: Stop replication and delete data from the replica table.

  • Real-time replication:

    • Enable Real-Time Data Replication: Start replication of data changes in the source in real-time.

    • Disable Real-Time Data Replication: Disable real-time data replication and switch the data access from Replicated (Real-time) to Replicated (snapshot). It preserves the replica table and its replicated data to allow further actions on the remote table such as deleting or changing the properties of the connection.

Validation for Remote Tables

The figure shows a screenshot of the option to validate remote tables.

The option Validate Remote Tables can be used to identify available table structure updates for all tables sharing the same source connection, and avoid errors and impact on dependent objects and run times in SAP Datasphere resulting from these updates, such as view runs, remote table replications or deployment. Data valuation is available for remote tables with or without persistence.

Mass validation offers to validate multiple remote tables at once. You can select an entire connection for validation.

The Remote Table Monitor provides ongoing runtime validation by showing the replication status for each remote table, error messages when real-time replication fails or stalls.

Create a Remote Table with Real-Time Replication

Scenario Overview

Let's have a look at the scenario overview:

The figure shows an overview of all objects to be created in the sales data scenario.

A DataStore Object (advanced) in the SAP BW/4HANA system stores sales orders. For these sales orders, a remote table is defined with real-time replication.

In this simulation, a remote table with real-time replication is created.

Create a Remote Table for Business Partner Attributes

Scenario Overview

Let's have a look at the scenario overview:

The figure shows an overview of all objects to be created in the sales data scenario.

SAP BW/4HANA contains master data for InfoObject 0D_NW_BP. A remote table for attributes has to be created. The semantic usage for the remote table and semantic types for the columns have to be set.

In this simulation, a remote table for business partner attributes is created.

Create Remote Tables for Product Master Data

Scenario Overview

Let's have a look at the scenario overview:

The figure shows an overview of all objects to be created in the sales data scenario.

SAP BW/4HANA contains master data for InfoObject 0D_NW_PRID. A remote table for attributes and a remote table for texts have to be created. The semantic usage for the remote tables and semantic types for the columns have to be set.

In this simulation, remote tables for product master data are created.