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

Business Function/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 Business Function“SAP HANA-optimized BI Content” (/IMO/BWCONTENT) in transaction SFW5.

    For detailed information about the Business Function “SAP HANA-optimized BI Content” (/IMO/BWCONTENT) see SAP HANA-optimized BW Content (Reversible)

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

Note Note

SAP strongly recommends activating the Enterprise Business Function “SAP HANA-optimized BW Content” (/IMO/BWCONTENT) instead of the formerly delivered Industry Business Function “SAP HANA-optimized BW Content” (/IMO/BW_CONTENT). Therefore please apply BI CONTENT 7.37 SP16, 7.47 SP16, 7.57 SP9 or higher before activation of the Business Function.

The Enterprise Business Function “SAP HANA-optimized BW Content” (/IMO/BWCONTENT) replaces the formerly delivered Industry Business Function “SAP HANA-optimized BW Content” (/IMO/BW_CONTENT), as only one Industry Business Function can be active. For further details please see SAPNote 2257232.

End of the note.
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 will be provided for this layer in future releases. The structure of these DSOs will reflect the structure of the DataSources.

      End of the note.

    • The data is then harmonized and transformed to the core EDW layer. The DataSource and the DSOs in the core EDW 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 in-memory-optimized DataStore objects, which can be used for reporting.

    • 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.

      MultiProviders usually access the data from DataStore objects. Depending on the use case, VirtualProviders read additional real-time database on SAP HANA views.

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

  • 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/<InfoArea>_Onn

    /IMO/FIAR_O30

    Core EDW layer

    InfoSource

    /IMO/<InfoArea>_ISnn

    /IMO/FIAR_IS30

    Note Note

    The long description of the InfoSource contains the technical name of the corresponding DataSource. For example: FI-AR: Customer Line Items (0FI_AR_30)

    End of the note.

    DataStore object

    /IMO/<InfoArea>_Dnn

    /IMO/FIAR_D30

    Virtual data mart layer

    VirtualProvider

    /IMO/<InfoArea>_Vnn

    /IMO/FIAR_V01

    MultiProvider

    /IMO/<InfoArea>_Mnn

    /IMO/FIAR_M01
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 1817520: Collective Note: SAP HANA-Optimized BI Content.