SAP HANA-Optimized Objects

We recommend using central CompositeProviders, Open ODS views and DataStore objects (advanced) for modeling. You can continue using the classic BW InfoProviders however.

After migration to the SAP HANA database, normal standard DataStore objects and standard DataObjects are contained in the SAP HANA database's column-based store. DataStore objects are automatically optimized for activation in SAP HANA. You should convert all existing InfoCubes and semantically partitioned objects that are based on InfoCubes into SAP HANA-optimized objects. This will allow you to enjoy the advantages of the SAP HANA database when loading data. When you create new standard InfoCubes or semantically partitioned objects, these are automatically created as SAP HANA-optimized objects. If possible, transformations and data transfer processes are processed in the SAP HANA database.

Data modeling has been simplified. Using SAP HANA-optimized objects means that it is not necessary to load to a BWA index for example, while the database architecture allows you for example to delete characteristics from an InfoCube that still contains data. Loading data from a DataStore object into a downstream InfoCube can also become unnecessary, if the InfoCube is only there to improve query performance.

To merge data from InfoProviders, analytic indexes or other SAP HANA views (by union or join), you can use the CompositeProvider. Storing the data in the SAP HANA database facilitates rapid data access for reporting and analysis.