SapHanaTutorial.Com HOME     Learning-Materials Interview-Q&A Certifications Quiz Online-Courses Forum Jobs Trendz FAQs  
     Explore The World of Hana With Us     
About Us
Contact Us
Hadoop App
Tutorial App on SAP HANA
This app is an All-In-One package to provide everything to HANA Lovers.

It contains
1. Courses on SAP HANA - Basics, Modeling and Administration
2. Multiple Quizzes on Overview, Modelling, Architeture, and Administration
3. Most popular articles on SAP HANA
4. Series of Interview questions to brushup your HANA skills
Tutorial App on Hadoop
This app is an All-In-One package to provide everything to Hadoop Lovers.

It contains
1. Courses on Hadoop - Basics and Advanced
2. Multiple Quizzes on Basics, MapReduce and HDFS
3. Most popular articles on Hadoop
4. Series of Interview questions to brushup your skills
Hadoop App
Stay Connected
Search Topics
Topic Index
HANA Admin Basics
Data Provisioning
SAP HANA Cockpit
Availability and Scalability

SAP Direct Extractor Connection

In previous article Overview of Data Provisioning in SAP HANA, we explained various data provisioning technique in HANA.
In this article, we will learn more about SAP HANA Direct Extractor Connection (DXC).

What is SAP HANA Direct Extractor Connection (DXC)?

The SAP HANA Direct Extractor Connection (DXC) is used to redirect data from embedded SAP BW system (For SAP ECC extractors) to HANA table using http connection. SAP HANA DXC is batch driven data replication technique i.e. it can execute after a time interval.

Note: SAP BW is automatically included in SAP ERP systems since SAP NetWeaver 7.0, The SAP BW technology that exists inside such an ERP system is called ‘Embedded BW

DXC utilizes the embedded BW to enable extraction and monitoring.  The Data flow is redirected to HANA from embedded BW.
When a DataSource is activated inside embedded BW (data warehousing workbench), a corresponding in-memory DataStore Object (DSO) is generated in HANA. The in-memory DSO is utilized as a foundation table for further HANA modeling, e.g. analytic views, calculation views, etc.

In many cases, data from different areas in SAP Business Suite systems requires application logic to appropriately represent the state of business documents. SAP Business Content Data Source Extractors have been available for many years as a basis for data modeling and data acquisition for SAP Business Warehouse; now with DXC, these SAP Business Content Data Source Extractors are available to deliver data directly to SAP HANA.

DXC is a batch-driven data acquisition technique; it should be considered as a form of extraction, transformation and load although its transformation capabilities are limited to user exit for extraction.

Advantage of SAP DXC

  • SAP DXC requires no additional server or application in the system landscape.
  • It reduces the complexity of data modelling in SAP HANA, as it sends the data to SAP HANA after applying all business extractor logic in the source system.
  • It speeds up SAP HANA Implementation time lines.
  • It extract semantic rich data from SAP Business site and provide to SAP HANA.

Limitation of SAP DXC

  • Data Source must have pre-define ETL method, if not then we need to define them.
  • SAP DXC requires a Business Suite System on Net Weaver 7.0 or higher (e.g. ECC) equal or below SP level: Release 700 SAPKW70021 (SP stack 19, from Nov 2008).
  • A procedure with a key field defined must exist in Data Source.

Architecture of Embedded BW in SAP Business Suite system and DXC

An SAP Business Suite system is based on SAP NetWeaver. As of SAP NetWeaver version 7.0, SAP Business Warehouse (BW) is part of SAP NetWeaver itself, which means a BW system exists inside SAP Business Suite systems such as ERP (ECC 6.0 or higher). This BW system is referred to as an “embedded BW system”.
Typically, this embedded BW system inside SAP Business Suite systems is actually not utilized, since most customers who run BW have it installed on a separate server, and they rely on that one.
With the default DXC configuration, we utilize the scheduling and monitoring features of this embedded BW system, but do not utilize its other aspects such as storing data, data warehousing, or reporting / BI. DXC extraction processing essentially bypasses the normal dataflow, and instead sends data to SAP HANA. The following illustration depicts the default configuration of DXC.

SAP HANA Direct Extractor Connection (DXC)

An In-Memory DataStore Object (DSO) is generated in SAP HANA, which directly corresponds to the structure of the DataSource you are working with. This IMDSO consists of several tables and an activation mechanism. The active data table of the IMDSO can be utilized as a basis for building data models in SAP HANA (attribute views, analytical views, and calculation views).
Data is transferred from the source SAP Business Suite system using an HTTP connection. Generally, the extraction and load process is virtually the same as when extracting and loading SAP Business Warehouse – you rely on InfoPackage scheduling, the data load monitor, process chains, etc. – which are all well-known from operating SAP Business Warehouse

Note: DXC does not require BW on SAP HANA. Also with DXC, data is not loaded into the embedded BW system. Instead, data is redirected into SAP HANA.

Support us by sharing this article.

Explore More
Close X
Close X

Leave a Reply

Your email address will not be published. Required fields are marked *

Current day month ye@r *

 © 2017 :, All rights reserved.  Privacy Policy