SAP HANA Direct Extractor Connection: Details - 2 The extraction from the SAP Business Suite system is controlled by the Data Warehousing workbench inside the embedded BW § When data is extracted from, the SAP Business Suite system, it is not loaded into the PSA of the embedded BW it is redirected instead and sent to SAP HANA § it gets loaded into in-memory DSO’s activation queue - and then gets activated into the active table of the in-memory § However, in the data load monitor of the embedded BW, the data load into the activation queue in the DSO in SAP HANA appears like data is loading into the PSA of the embedded BW Delta processing (aka “change data capture”) § Works the same for DXC as it would if BW is the receiving system § If the Data.
An architectural variation is available, which uses a “sidecar” BW instead of the embedded one. 0 Support Package Stack 19 – first available Nov 2008 § DXC uses the embedded BW system to enable extraction towards SAP HANA and monitoring § DXC mainly requires applying SAP note 1583403 Note: Modeling in the embedded BW is not part of the DXC solution. Weaver ABAP § In typical SAP Business Suite systems, the embedded BW is not utilized § customers used to run separate BW systems § Most customers already have the Support Package level needed on source SAP Business Suite system, e. DXC utilizes the embedded BW § Starting with Net. SAP HANA Direct Extractor Connection: Details - 1 SAP HANA Direct Extractor Connection (DXC) § Utilizes the Data Source extractors that exist in SAP Business Suite systems § Originally, those were developed for use with BW § DXC is for use in SAP HANA standalone scenarios (data mart) BW on SAP HANA is a separate topic. Source (flat structure) Activation Processing Extractor Status ERP data 13 Source http Activation Active version Queue generic data transfer Data. Cubes In memory DSO Data Store Objects Info. SAP HANA Direct Extractor Connection (DXC) Leverage pre-existing foundational data models of SAP Business Suite entities for use in SAP HANA data mart scenarios § § Significantly reduces complexity of data modeling tasks in SAP HANA Speeds up timelines for SAP HANA implementation projects Provides Semantically Rich Data from SAP Business Suite to SAP HANA § § Ensures data appropriately represents the state of business documents from ERP Application logic to “make sense of the data” already built into many extractors Simplicity / Low TCO § § Re-uses existing proprietary Extraction, Transformation, and Load mechanism built into SAP Business Suite systems, over a simple http(s) connection to SAP HANA No additional server or application needed in system landscape Change Data Capture (delta handling) § § Efficient data acquisition – only bring new or changed data into SAP HANA DXC provides a mechanism to properly handle data from all delta processing types © 2012 SAP AG. > Mainly recommended for batch type data replication for stand alone HANA business scenarios Other Data Provisioning Options Sybase Event Stream Processor (ESP) * : will be available for replicating real time event streams from Sybase ESP (CEP) into SAP HANA * Planned to be available as part of SAP HANA SPS 05 and Sybase ESP 5. SAP HANA SPS 04: Data Provisioning Positioning SAP LT Replication Server (SLT) is positioned for real-time data replication from SAP and non-SAP sources (SAP supported data bases only) -> Mainly recommended for real time data replication business scenario SAP Data Services (DS) is positioned for batch load-based data replication from non-SAP sources and SAP sources (with complex ETL requirements) -> Mainly recommended for batch type data replication business scenarios SAP HANA Direct Extractor Connection (DXC) DXC is available as a simple option in batch mode for data replication from existing SAP Data Source extractors (ERP) into SAP HANA.
0 kommentar(er)
