Importing Entities with Semantics from SAP S/4HANA

You can use the Import Entities wizard to load metadata from your SAP S/4HANA Cloud and SAP S/4HANA on-premise connections via semantically-rich objects. The wizard creates Business Builder and Data Builder entities (along with all the objects on which they depend) in SAP Datasphere.

Prerequisites

To import entities with semantics from SAP S/4HANA, you must have a scoped role that grants you access to a space with the following privileges:
  • Data Warehouse General (-R------) - To access SAP Datasphere.

  • Data Warehouse Connection (-R------) - To access remote objects.

  • Data Warehouse Data Builder (CRUD----) - To create, edit, and delete Data Builder objects.

  • Data Warehouse Business Entity (CRUD----) - To create, edit, and delete Business Builder business entities.

  • Data Warehouse Consumption Model (CRUD----) - To create, edit, and delete Business Builder consumption models.

  • Space Files (CRUD----) - To create, read, update, and delete objects in your spaces.

The DW Modeler role template, for example, grants these privileges. For more information, see Privileges and Permissions and Standard Roles Delivered with SAP Datasphere.

Context

You can import entities from the following types of sources: We recommend that, where possible, you use the Import Entities wizard for importing CDS views from these connection types, as it as able to leverage their rich semantics to import higher-level objects and to follow associations to dimensions, hierarchies, and text entities and include them in the import.

Procedure

  1. Open the wizard from the Repository Explorer, Semantic Onboarding, or the Data Builder:
    • In the side navigation area, select (Repository Explorer), and select Start of the navigation pathImport Next navigation step Import EntitiesEnd of the navigation path.

    • In the side navigation area, select (Semantic Onboarding), and then select the appropriate tile.

    • In the side navigation area, select (Data Builder), select a space if necessary, and select Start of the navigation pathImport Next navigation step Import EntitiesEnd of the navigation path.

  2. Select your connection and target space:

    Semantic Onboarding

    Repository Explorer/ Data Builder

    Select the connection to the source you want to import from the list, and then click Next Step.

    You can use the Filter By pane on the left to filter the connections by space.

    1. Select the SAP S/4HANA Cloud or SAP S/4HANA connection type, and then click Next Step.

    2. Select the connection/target space that you want to import the entities from/into, and click Next Step.

      If you opened the wizard from the (Data Builder), only connections in your current space can be selected.

  3. On the Select Entities page, select the entities that you want to import from the Results list, and click Next Step.
    Use the Search field to search by label. Depending on your connection type, you can filter by:
    • Application Component

    • Modeling Pattern (see Supported Capabilities for CDS Views in the SAP S/4HANA Cloud documentation)

    • Release Contract (see Stability Contracts for CDS Views in the SAP S/4HANA Cloud documentation)

    • Software Component

  4. On the Review Entities page, review the entities that you will import.
    The left pane lists the entities you have selected for import and the right pane has two tabs listing all the entities that will be created in the SAP Datasphere Business Builder and Data Builder during the import of the selected entity.
    The following entities are created when you import entities with the most common modeling patterns:

    Source Modeling Pattern

    Business Builder Objects Created

    Data Builder Objects Created

    ANALYTICAL_FACT

    (SAP S/4HANA on-premise only)

    • Selected entity:

      • One business entity (Fact)

    • Supporting entities:

      • One entity (Dimension) for each associated dimension.

    • Selected entity:

      • One remote table (Relational Dataset)

    • Supporting entities:

      • One remote table for each associated dimension, hierarchy, and text entity.

    ANALYTICAL_DIMENSION

    • Selected entity:

      • One business entity (Dimension)

    • Supporting entities:

      • One entity (Dimension) for each associated dimension.

    • Selected entity:

      • One view (Dimension)

      • One remote table (Relational Dataset)

    • Supporting entities:

      • One view and one remote table for each associated dimension, hierarchy, and text entity.

    LANGUAGE_DEPENDENT_TEXT

    (none)

    • Selected entity:

      • One remote table (Text)

    ANALYTICAL_PARENT_CHILD_HIERARCHY_NODE

    (none)

    • Selected entity:

      • One remote table (Hierarchy)

    Each object has the following read-only properties:

    Property

    Description

    Business Name

    Generated from the Label value.

    Technical Name

    Generated from the ID value as: remote.<connection_name>.<ID>.

    Import Status

    Specifies whether the object needs to be created in SAP Datasphere during the import:
    • Ready for Import - The object will be created.

    • Already Imported - The object has already been created during a previous import. If the structure or semantics of the object have subsequently changed in the source system, the object will be automatically updated and redeployed.

  5. Click Import and Deploy.
    A notification is sent immediately, and this notification will update as the import process continues. When the import is complete:
    • You have two notifications:

      • Click the first notification to see the imported entities listed in the (Repository Explorer).

      • Click the second notification to view the import log messages.

        If any entity could not be created, an error is given.

    • The imported entities are available for use in the (Business Builder) and the (Data Builder).
  6. Navigate to the appropriate objects to review data access:
    • Replication Flow to Local Tables - Open the replication flow and run it (or create a schedule) to replicate the data (see Run a Replication Flow).

    • Remote Tables - By default, data is only federated. To replicate the data, open the Data Integration Monitor (see Monitoring Remote Tables).

    • Local Tables - If you have selected an entity that is not extractable, only local tables are imported, and you must choose an appropriate method to load data to them.