SAP Note

Header Data

Symptom

There are a very small number of DataSources that are not supported for use with SAP HANA Direct Extractor Connection (DXC).

Other Terms

DXC DEC

Reason and Prerequisites

1) SAP HANA does not presently provide functionality that is found in SAP BW for handling inventory movements data. Specifically, SAP BW includes special functionality known as "non-cumulative key figures" and "non-cumulative cubes". Data provided by certain DataSources (particularly ones related to inventory movements) requires the previously mentioned functionality in the receiving system (i.e. SAP BW) for correct data in reports. Therefore, since this required functionality is not presently available in SAP HANA, certain DataSources are not supported with DXC.

2) Hierarchy DataSources (“Hierarchy Nodes (HIER)”, e.g. Business Content DataSources ending with “_HIER”) should not be utilized directly by DXC. To be clear, they can be used by DXC, but only with a special workaround, which is needed to make sure the hierarchy data is rendered correctly in the SAP HANA system.  This is because hierarchy DataSources were originally designed with a BW InfoObject in mind as the target. One aspect of this is that the respective hierarchy node segment table doesn’t contain the hierarchy name that is loaded. The other aspect is that, when loading into BW, and performing recurring loads of the same hierarchy, new BW internal NODEIDs are created only in for every load; therefore a semantically identical node could therefore be considered as duplicate if used directly by DXC. Only when loading hierarchy data into an InfoObject in SAP BW, is the necessary information added.  Thus, in order to utilize hierarchy DataSources with DXC, the procedure would be to first perform the actions needed to activate the coresponding hierarchy InfoObject in the embedded BW (embedded inside the SAP Business Suite system).  Next, this hierarchy InfoObject should be configured as an export DataSource, which in turn should be used as the DataSource for DXC.  Thus, loading hierarchy data into SAP HANA using DXC would be a two-step process: first, load the hierachy InfoObject in the embedded BW, and then perform the DXC extraction from that same hierarchy InfoObject (export DataSource) into the SAP HANA In-Memory DSO (which was generated automatically by DXC).  It would make sense to set up a process chain to perform both actions, one after another. Also, please note that the hierarchy data is "flattened" in the SAP HANA In-Memory DSO.  Each record contains data about the parent node relationship.  This data can be utilized in data modeling in SAP HANA.

Solution

The following DataSources are not supported for use with SAP HANA Direct Extractor Connection (DXC): 0CFM_INIT_POSITIONS 0CML_INIT_BUDAT 0CML_INIT_DDISPO 0CML_INIT_DFAELL 0RE_1 0RE_3 0SCM_LIM_1 2LIS_02_SRV 2LIS_03_BX 2LIS_03_S197 2LIS_03_S198 2LIS_40_S278 2LIS_03_BF 0BV_BEV1_EM_CUSTSTO_BW_GET_TD 0RE_2 0RE_3 0RF_REASLOC_ATTR 0SCM_LIM_1 0SCM_LIM_2

    1710236 - SAP HANA DXC: DataSource Restrictions  

Version   4     Validity: 17.10.2014 - active   Language   English (Master)

Released On 10.12.2014 13:59:38

Release Status Released for Customer

Component HAN-DP-DXC SAP HANA Direct Extractor Connector

Priority Recommendations / Additional Info

Category Special development

All DataSource of type “Hierarchy Nodes (HIER)”, e.g. Business Content DataSources ending with “_HIER”. A workaround is needed, see 2) above.

Validity

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (2)

Software Component From Rel. To Rel. And Subsequent

HDB 1.00 1.00  

1548125   Interesting facts about Inventory Cubes

1501907   Non-cumulative cubes, validity interval,non-cumulative logic

1548125   Interesting facts about Inventory Cubes

1501907   Non-cumulative cubes, validity interval,non-cumulative logic