Some time ago I blogged about ODP – Operational Data Provisioning which is API is used for internal connection of SAP Data Services (DS former BODS) to (BW) application extractors (before solely used by BW). There is another similar solution which complements ODP. It is so called Direct Extractor Connection (DXC).
Currently there are following options how to transform data from SAP Business Suite to HANA:
- SAP Data Services (DS)
- SAP Landscape Transformation (SLT)
- Sybase Replication Server
With respect Direct Extractor Connection (DXC) consider following features: It is data provision tool (ETL tool). It is utilizing existing BW data sources. It is not real time solution. There are not possible complex transformations means no extra features or so called simple ETL.
Data provided by DXC is exposed directly to HANA's XS engine. Delta mechanism via data is being transformed is done by HANA's IMDSO (In-Memory DataStore Object) with activation processing. There will be particular datasource having its own IMDSO object sin HANA where the data will be flowing into HANA. You may not be able to change datasource key in standard TA RSA2 or RSA6. Therefore to change enable change of key of datasource you can user ABAP report ROSOA_CHANGE_KEY. The ABAP report comes with SAP note 1677278 - DataSource: Changing the key definition (A version). Load of data to HANA happens similarly as any other BW load. You can use InfoPackage (encapsulated into Process Chain) for that. On HANA side all tables are created: active data, change log, systems table. You need to use these tables in HANA model later.
Prerequisites / availability:
DXC needs at least ECC 6.0
DXC became generally available with HANA SP4
For more details check out following sources:
1710236 - SAP HANA DXC: DataSource Restrictions
1583403 - Direct extractor connection to SAP HANA
1670518 - SAP HANA Direct Extractor Connection: Monitoring
1714852 - Troubleshooting SAP HANA DXC issues
1677278 - DataSource: Changing the key definition (A version)