Skip to Content
Technical Articles
Author's profile photo Michael Sanjongco

Part 1 – SAP S/4HANA Cloud Data Integration to power your Intelligence Enterprise

Note: This blog series was created in a team effort with our colleague Shady Hanna.

As cloud operations gain prominence, organizations across all industries need a way to integrate business processes and bring in innovation such as Analytics by leveraging data across multiple applications to drive better planning and decision-making and turn their insights into actions.

Our job is to accelerate your journey to become an Intelligent Enterprise and achieve your overall business objectives and mission by harnessing the data from your SAP S/4HANA environment and assist in building bridges between your Enterprise Applications in order to lower the total cost of ownership and deployment.

This blog series will help you understand the recommended way of extracting data out of SAP S/4HANA Cloud to enrich your data orchestration across your complex landscapes.

Before we get started, it’s best to know the basics and realize the nomenclature around the technology.

Let’s begin with Virtual Data Models and ABAP Core Data Services. The virtual data model (VDM) is a structured representation of ABAP Core Data Services (CDS) views in SAP S/4HANA and SAP S/4HANA Cloud. CDS Views forms the basis in defining a semantically rich VDM and for exposing all relevant business data from SAP S/4HANA Cloud.

You can learn more about VDMs and CDS in this SAP help.

 

Figure%201%3A%20High%20level%20representation%20of%20VDM%20and%20CDS%20Views

Figure 1: High level representation of VDM and CDS Views

 

Figure%202%3A%20Example%20of%20business%20data%20CDS%20Views

Figure 2: Example of business data CDS Views

 

CDS Views provide a variety of purposes such as interface across multiple applications and analytics. With this in mind, SAP has introduced “stability contract” to ensure the CDS Views fulfill the variation of tasks. To understand the different stability contract use cases, please refer to this SAP help.

Now that you understand the basics, let’s jump right in to how you can extract data from SAP S/4HANA Cloud. If you have not seen the blogs from our colleague Simon Kranig, here is Part 1 – Overview which goes over some of the basics we just described and a lot more detail on how CDS based extraction is handled by the Operational Data Provisioning (ODP) framework.

 

What’s the best way to find the CDS Views that are extraction enabled?

Here’s a nice blog from our colleague Ranjitha Balaraman which explains how to discover extraction enabled CDS Views.

Another option is to go to SAP API Hub. You can select “CDS View” under the side menu “Content Types”, look for the specific CDS View and go to “details” tab. Under “Supported Capabilities” you will find “Data Source for Data Extraction” for the CDS Views that are extraction enabled.

In addition, starting in SAP S/4HANA Cloud 2011, “View Browser” Fiori App is enhanced with improvised search of CDS views in table, column, and annotation names. You can search for the extraction enabled CDS View by searching for the annotation  @Analytics.dataExtraction.enabled.

 

What are the use cases for SAP S/4HANA Cloud Data Integration?

Figure 3: Architecture overview of the different data integration options

 

In the next blogs, we will discuss in detail each of the different consumers of SAP S/4HANA Cloud data.

Do not hesitate to leave a comment if you have any suggestions on other data integration related topics.

See you soon…

 

Part 2 – SAP S/4HANA Cloud Data Integration Overview

Assigned tags

      2 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Frank Riesner
      Frank Riesner

      Hi Michael,

      I think there is another option to find extraction enabled CDS Views now in SAP S/4HANA starting with version Cloud version 2008 / on premise version 2020:
      We provide a CDS View I_DataExtractionEnabledView, which provides a list of them. You can call it in SAP S/4HANA in tr. SE16 and table name = IXTRCTNENBLDVW we well.

      Regards, Frank

      Author's profile photo Michael Sanjongco
      Michael Sanjongco
      Blog Post Author

      Thank you Frank.

       

      The information is also available in the comment section of the blog link from Ranjitha Balaraman

      It is great to know about the transaction code as well and the table name.

      Thanks again for sharing.

       

      Kind Regards,

      mike