SAP HANA -SAP HANA-optimized InfoCube

  • Published on
    01-Nov-2015

  • View
    11

  • Download
    0

Embed Size (px)

DESCRIPTION

The SAP HANA-optimized InfoCube is a standard InfoCube that is optimized for use with SAP HANA. When you create SAP HANA-optimized InfoCubes, you can assign characteristics and key figures to dimensions. The system does not create any dimension tables apart from the package dimension however.

Transcript

<ul><li><p>SAP HANA-optimized InfoCube The SAP HANA-optimized InfoCube is a standard InfoCube that is optimized for use with SAP HANA. When you </p><p>create SAP HANA-optimized InfoCubes, you can assign characteristics and key figures to dimensions. The system </p><p>does not create any dimension tables apart from the package dimension however. The SIDs (master data IDs) are </p><p>written directly to the fact table. This improves system performance when loading data. Since dimensions are </p><p>omitted, no DIM IDs (dimensions keys) have to be created. </p><p>The dimensions are simply used as a sort criterion and provide you with a clearer overview when creating a query in </p><p>BEx Query Designer. </p><p>Inventory Management with SAP HANA-Optimized InfoCubes </p><p>For InfoCubes with non-cumulative key figures, the different types of data are loaded separately (initial non-</p><p>cumulative, historical transactions and new deltas). You need two data transfer processes (DTPs) for this: </p><p> A DTP to initialize the non-cumulative data. Go to your DTP's Extraction tab, under Extraction Mode, and </p><p>choose Initial Size for Non-Cumulative Values. </p><p> A DTP to load data and historical transactions: </p><p>o For new deltas, go to your DTP's Extraction tab, under Extraction Mode, and choose Delta. </p><p>o If historical data is supplied by the source, go to your DTP's Update tab and choose Historical Transactions. </p><p>Note </p><p>A DTP can be changed in a production system if the development class of the imported DTP can be changed. </p><p>You then just need to change the settings in the DTP and reactivate it. For more information, see 1558791 . </p></li><li><p>This logic replaces the compression logic (and therefore the associated marker update) for the SAP HANA-</p><p>optimized InfoCube. There is no semantic basis for compression with SAP HANA-optimized InfoCubes. The data is </p><p>only compiled. Markers are not updated. </p><p>Prerequisites </p><p>You are using an SAP HANA database. </p><p>Constraints </p><p>If you are using an SAP HANA database, you can only create SAP HANA-optimized InfoCubes. You can continue </p><p>using existing standard InfoCubes that do not have the SAP HANA-optimized property or you can convert them. </p><p>The property Data Persistency in BWA is not available in SAP HANA because the SAP HANA database assumes </p><p>the role of primary persistence. </p><p>More information: Converting Standard InfoCubes to SAP HANA-Optimized InfoCubes </p></li></ul>