SAP First Guidance Collection for SAP BW powered by SAP HANA – Application Specific
SAP First Guidance
The First Guidance documents are the beginning of a series of documents that should help to better understand the various concepts of SAP BW powered by SAP HANA. The documents are still “work in progress”, so these guides are not intended to be exhaustive.. The purpose of these documents is to deliver additional information besides SAP Help and blogs to get a better understanding of the concepts of SAP BW on SAP HANA.
Read also about the SAP First Guidance Collection for SAP BW powered by SAP HANA – ALM Specific
One of the key differentiators of SAP BW are the various easy-to-consume options to model business semantics without the need to care for their technical implementation. The delta capability of DataStores, hierarchies, elimination of internal business volume, and non-cumulative key figures are just a few examples. This document focuses on inventory handling and non-cumulative key figures in SAP BW.
Are you looking for a way to define custom transformation rules which cannot be implemented using standard BW functionality and want to leverage the power of the SAP HANA database platform? This First Guidance document describes the option to defined custom transformation rules with SAP BW powered by SAP HANA, which are processed completely on the SAP HANA database effectively eliminating the need to move data over the network between database and the application server. Not only does this option provide maximum performance, but also allows to leverage many of the powerful capabilities of the SAP HANA platform.
Starting with SAP BW 7.4 SP5 on HANA a new feature to analyze data from certain perspectives, for example to calculate ABC classes or to calculate scoring classes, is introduced. This new feature is called SAP HANA Analysis Process and enables the data warehouse modeler to analyze the data using different predefined or own written functions or scripts. HANA provides the integration numerous specialized libraries like PAL, AFL, R to understand the correlation of the data in the existing EDW.
The focus of this document is the exposure of BW data natively in HANA as HANA views that point directly to the data and tables managed by BW. This enables HANA-native consumption of BW data.
This SAP first guidance document describes the handling of non-cumulative InfoCubes on SAP HANA. As the handling of Inventory InfoCubes changed within SAP BW 7.30 based on SAP HANA, this document wants to briefly describe the differences. for better understanding it is recommended to read How to Guide based on previous release How to Handle Inventory Management Scenarios in BW.
In SAP BW 7.4 SP05 on HANA the new metadata object Open ODS View is introduced, which provides the data warehouse modeler with a flexible, easy to use tool to integrate external data in the EDW Core Data Warehouse.
A CompositeProvider is an InfoProvider in which you can combine data from BW InfoProviders such as InfoObjects, DataStore Objects, SPOs and InfoCubes, or SAP HANA views such as Analytical or Calculation Views using join or union operations to make the data available for reporting. This paper explains how to create a CompositeProvider in SAP BW 7.4 SP5 using the BW modeling tools in SAP HANA Studio.
The advanced Data Store Object (aDSO) is a new object type introduced in SAP BW 7.4 SP8 powered by SAP HANA. The aDSO simplifies data persistency consolidating the InfoCube, Data Store Object (write-optimized, standard and direct update) and PSA tables of prior releases. When implementing the aDSO, it is important to understand the configuration options available and the scenarios in which they are designed to be used. It is the aim of this first guidance’s document to provide this information as well as general guidance for the use of the aDSO.
The paper describes the SAP BW on HANA Dynamic Star Schema, which is a new modeling pattern partitioning Dimensions (master data) of fact-table InfoProvider using Composite Providers or Open ODS Views of type fact. With the Dynamic Star Schema and partitioned Dimensions we achieve a new degree of dynamics and flexibility implementing a LSA++ without losing the business orientation of SAP BW. The scenarios discussed in this paper were verified on SAP BW on HANA version 7.5 SP2.
SAP BW 7.4. on HANA provides new ways to flexibly integrate non SAP data in a virtual way. This paper discusses technical options as well as architectural considerations and provides guidance for the implementation of such scenarios.