Comparing Modeling Focus of SAP BW/4HANA, SAP HANA and SAP S/4HANA

Watch this video to compare the modeling focus of SAP BW/4HANA, SAP HANA, and SAP S/4HANA.

When integrating different sources, the following tasks have to be performed:

1. Harmonize the master data across source systems.

   For example, the same product could have different IDs that must be mapped or the assignment of categories ID is different.

2. Integrating master data and transactional data.

   For example, adding category information to the sales data.

In principle, the integration of data from different tables or sources can be modeled in three different ways:

1. Use databases views or function modules.

   When a source system already contains all the data that is required to generate the desired result, define database views or function modules in the source system. Then define generic data sources for the extraction to SAP BW/4HANA.

   Use transaction SE11 to generate database views and add missing values from another table.

   For complex transformations, use function modules instead of simple database views and profit from the full range of ABAP features. The original values are collected during extraction.

   If carrying out a join or function module slows down the extraction process, run a program in the source system to fill a new table in the source system. Then, only read from this smaller set of values during extraction. If this is your main area of modeling, you use the source system as your modeling focus.

   SAP BW/4HANA models can be kept simple, and data can be checked in the source system. This means that the source system is responsible for providing consistent data.

2. Create calculation views.

   When harmonizing data across systems, the data must be collected in one system. If values from different sources can be assembled in the same SAP HANA platform on the database level, using SLT or smart data access, models can be created in SAP HANA.

   Create calculation views to calculate the desired result whenever needed. Values are immediately available. This view can be directly consumed in reports or used as the basis for extraction to SAP BW/4HANA. In this case, SAP HANA is the modeling focus.

   Real time reporting is available, and data integration is fast. If calculation is done on the fly, no further results must be stored.

   You need SQL for complex cases and harmonization with historical data has to be implemented manually.

3. Create InfoObjects and InfoProviders

   Use SAP BW/4HANA as the modeling focus under the following circumstances:

   • When not all values are loaded to SAP HANA.

   • When you want to use ABAP for integration.

   • When you want to take snapshots of the source data at exact points in time.

   • When you want to keep a history.

   Use InfoObjects to store time-dependent master data.

   Use DataStore Objects (advanced) as persistent storage for snapshots, and to generate delta data after changes.

   As long as ABAP isn’t used, transforming values are processed in the SAP HANA database. ABAP can be used for special cases. There are excellent monitoring and scheduling options.

Why do we need a separate external data warehouse like SAP BW/4HANA, and how does it complement SAP S/4HANA embedded analytics? We know that real-time analytics on operational data are well supported by SAP S/4HANA, and the goal of taking operational reporting back to the operational systems is achieved. However, we also know that operational data must be moved to a suitable location when its value for day-to-day online business operations has decreased.

At this point, solutions are required for data archiving. Preferably, this solution must provide an intelligent and automated archive that can integrate with real time operational data, and also from multiple sources. For example, in a landscape made up of multiple SAP and non-SAP systems. A sophisticated data warehouse like SAP BW/4HANA provides the corresponding services including a strong data governance. Business planning is another scenario in SAP BW/4HANA, as planning requires data to be stored at various levels of aggregation, and not at the typical atomic level of line item data, as preferred by SAP S/4HANA. Also, whenever the need for long-term, strategic reporting is required on aggregated levels, SAP BW/4HANA is the solution.

It's important to consider that SAP BW/4HANA is moving away from the classic approach of acquiring all data and storing it in an own-managed persistence. SAP BW/4HANA provides new capabilities to design a logical data warehouse and to follow data federation approaches. Therefore, the data isn’t always transferred and stored in all cases: data managed on external sources can also be consumed virtually.

SAP S/4HANA embedded analytics provides operational reporting in SAP S/4HANA. In the past, these scenarios were often implemented in SAP BW due to lack of proper reporting capabilities, and performance limitations of ERP systems. However, with SAP S/4HANA embedded analytics, the role of SAP BW (SAP NetWeaver BW or SAP BW/4HANA) is to be reevaluated. The primary focus shifts to enterprise data warehouse use cases, because SAP S/4HANA can provide analytics for managing the day-to-day business, without redundancy in real time.

You can create scenarios where data, which is modeled in the SAP BW/4HANA system, is merged with data modeled in SAP HANA with SAP HANA tools.

SAP BW/4HANA system runs on SAP HANA and the data is stored in a special schema known as the SAP BW/4HANA-managed schema. In other SAP HANA schemas, data can be stored in SAP HANA tables. You can make data available from tables of any SAP HANA database schema in SAP BW/4HANA via Open ODS View or via BW DataSources.

You can also consume SAP HANA Views directly in Open ODS Views, in CompositeProviders, and in InfoObjects with Access Type SAP HANA View.

You can also make SAP BW/4HANA data (data from the SAP BW/4HANA-managed schema in the SAP HANA database) available in a different SAP HANA schema.

In SAP BW/4HANA, you can generate External SAP HANA Views (SAP HANA Calculation Views) on SAP BW/4HANA InfoProvider data models and BW Queries.

It’s recommended to model one topic mainly in one modeling focus. However, if some functions can’t be established within this modeling focus, consider a mixed scenario.