Background documentationSAP HANA-Optimized BI Content

 

SAP HANA-optimized BI Content combines enterprise data warehouse capabilities of SAP NetWeaver BW running on SAP HANA with explorative and interactive real-time analytics using the SAP HANA in-memory database. The new data model follows the recommendations for the layered scalable architecture LSA++, which is optimized for BW running on SAP HANA.

For more information about the layered scalable architecture optimized for BW on HANA, see Start of the navigation path http://help.sap.com Next navigation step SAP NetWeaver Next navigation step SAP NetWeaver Platform Next navigation step Application Help Next navigation step SAP NetWeaver Library: Funtion-Oriented View Next navigation step Business Warehouse Next navigation step Data Warehousing Next navigation step The Data Warehouse Concept Next navigation step Layer Architecture of a Data Warehouses with SAP HANA Database (LSA++) End of the navigation path.

Prerequisites

Switch

  • To use SAP HANA-optimized BI content, you need to run your BW system on a SAP HANA database.

  • To activate SAP HANA-optimized BI content, you need to turn on the switch “SAP HANA-optimized BI Content (BW / HANA)” (/IMO/BW_CONTENT).

    For more information, go to the SAP Help Portal at http://help.sap.comInformation published on SAP site and search for Switching On Business Functions.

Source System ID

Before you load data into the BW DataStore objects for SAP HANA-optimized content, you need to maintain the source system ID.

The two-digit source system ID (0GN_R3_SSY) is added to the BW DataStore objects for SAP HANA-optimized content. It is used to fill source system-dependent objects, such as consolidated InfoObjects (for example, 0GN_CUSTOM), and allows you to determine the system from which the data was loaded.

Procedure

  1. Open the Data Warehousing Workbench and choose Start of the navigation path RSA1 Next navigation step Tools Next navigation step Asgnmnt of Srce Syst. to Srce Syst. ID End of the navigation path.

  2. Enter the relevant values in the Source System ID column.

You can also use transaction SE16 to check that the two-digit source system ID has been defined in table RSSOURSYSTEM for your system and landscape.

Structure

LSA++ Aligned Data Model

The SAP HANA-optimized BI Content follows the LSA++ recommendations. The data model currently provides the following features:

  • Three-layer approach to the enterprise data warehouse

    • The data is acquired in the open operational data store layer. The PSA serves as the historical data foundation. No transformations or aggregations are defined in this layer.

      Note Note

      BI Content DSOs are provided for this layer if the data is loaded further into multiple EDW Core Layer DSOs. The structure of the open operational data store layer DSOs reflects the structure of the connected DataSources.

      End of the note.

    • The data is then harmonized and transformed to the EDW core layer. The DataSource and the DSOs in the EDW core layer are connected by an InfoSource. No transformation logic is applied between the open operational data store layer and the InfoSource. All harmonization and transformation logic is applied between the InfoSource(s) and the EDW core DSO(s).

      Note Note

      You can connect multiple sources of the open operational data store layer with the SAP HANA-optimized BI Content data flow without losing the predefined EDW transformations. This can be helpful if you need to connect multiple source systems.

      End of the note.

      InfoCubes are no longer required for SAP HANA-optimized BI content. They are replaced by in-memory-optimized DataStore objects, which can be used for reporting.

    • A corporate memory layer is provided to contain the complete history of the loaded data. It is used as a source for reconstructions without the need to access the sources again. The corporate memory is filled independently of the EDW core layer’s update.

    • A virtual data mart layer is used for reporting. InfoProviders that reside in this layer do not contain any data. Instead, they describe which data is accessed, and how it is displayed semantically to the end user.

      CompositeProviders are used as InfoProviders in this virtual data mart layer and access the data from DataStore objects. Depending on the use case, also data from SAP HANA information models is read and might be mixed with staged data in BW.

      All BI Content BEx Queries are deployed on top of the CompositeProviders.

  • Date of last update

    The InfoObject Last Update Date 0UPD_DATE is available for all DataStore objects. You can use this information to identify the last update date for any particular data record. It supports the data load process, and enables selective lookups or rebuilds.

  • Naming conventions

    The following naming conventions for the new SAP HANA-optimized Business Content are used throughout the data model:

    Layer

    InfoObject

    Technical Name

    Example

    Open operational data store layer

    DataStore object

    /IMO/O_<InfoArea>nn

    /IMO/O_PUR11

    EDW core layer

    InfoSource

    /IMO/<InfoArea>_ISnn

    /IMO/PUR_IS11

    Note Note

    The long description of the InfoSource contains the technical name of the corresponding DataSource. For example: MM-PUR: Purchase Data Item (2LIS_02_ITM)

    End of the note.

    DataStore object

    /IMO/D_<InfoArea>nn

    /IMO/D_PUR11

    Corporate memory layer

    DataStore object

    /IMO/CM<InfoArea>nn

    /IMO/CMPUR11

    Virtual data mart layer

    CompositeProvider

    /IMO/V_<InfoArea>nn

    /IMO/V_PUR01

Note Note

Product Cost Forecast and Simulation is not using the new BW artifacts (CompositeProvider, DataStore object (advanced)) yet.

End of the note.
Consolidated InfoObjects

The SAP HANA-optimized BI Content provides consolidated InfoObjects in its data model, where applicable.

SAP BW uses consolidated InfoObjects to integrate and harmonize information from different SAP components in a standardized (consolidated) data model (for example, 0MATERIAL from SAP ERP, and 0CRM_PROD from SAP CRM).

The consolidated InfoObjects can store information about duplicates in the master data, and therefore enable consolidated reporting using a group ID.

Note Note

If you use multiple source systems, you need to adapt the delivered business content to your specific system landscape setup (for example, by adding the source system ID to the key of each BW DSO).

End of the note.

For more information about consolidated InfoObjects, go to the SAP Help Portal at http://help.sap.comInformation published on SAP site and search for Consolidated InfoObjects for BP, Product and Product Category.

More Information

For documentation updates relating to SAP HANA-optimized BI content, see SAP Note 1817520Information published on SAP site: Collective Note: SAP HANA-Optimized BI Content.