Loading Transactional Data from SAP S/4HANA

Objective

After completing this lesson, you will be able to load transactional data from SAP S/4HANA

Transactional Data Load from SAP S/4HANA into a Data Mart DataStore Object

Scenario

A Data Mart DataStore Object has been defined to store cost center actual postings. As a next step we'll create a graphical data flow for the cost center transactional data.

Using this data flow, a DataSource in SAP BW/4HANA is created on the SAP S/4HANA Business Content DataSource 0CO_OM_CCA_9, presenting cost center actual postings. Source system ODP_SAP is used, leveraging the Operational Data Provisioning Framework. The creation of a Transformation and a Data Transfer Process to the Data Mart DataStore Object completes the data flow.

By executing the Data Transfer Process, the data is loaded into the Inbound Table of the Data Mart DataStore Object. In our scenario, we do not activate this request. For a Data Mart DataStore Object, it only means compressing the data and the data is already available for reporting.

Note

In the Transformation, the global transfer routine of U##_COSTC is also used (again), because it has been defined on the InfoObject level. This will transform the cost center key from the SAP S/4HANA source system (10 chars) into 13 chars.

Requests in a Data Mart DataStore Object

During the upload of data, a request is always inserted into the inbound table (new data). Each request gets its own request ID (time stamp). This feature enables you, for example, to delete a request from the inbound table after the upload. However, this may result in several entries in the inbound table with the same values for all Characteristics except the request ID. This increases the size of the inbound table and decreases the performance of your Queries.

To compress the data, you can activate requests. The records are then summarized for each request ID into the active table and the data of the activated requests are deleted from the inbound table. The Change Log is not used for a Data Mart DataStore Object. After the data has been activated, it is not possible to delete the data for a specific request ID.

Watch this video to learn about request activation in a Data Mart DataStore Object.

Reporting on this Data Mart DataStore Object is consistent and provides stable navigation. A Query can be run immediately after loading. You do not need to activate data beforehand. When a Query is run, the system automatically accesses the active data table and the inbound table (using a union across both tables).

Video: Creating a Graphical Data Flow for Transactional Data

Watch this video to learn how to create a graphical data flow for transactional data.

Video: Loading Transactional Data from SAP S/4HANA into a Data Mart DataStore Object

Watch this video to learn how to load transactional data from an SAP S/4HANA source system into a Data Mart DataStore Object.

Log in to track your progress & complete quizzes