SAP BW/4 HANA

Introduction &
Architecture
Contents
 What is DW  Things NOT supported in BW/4HANA

 Introduction  Design Principles

 Business Benefits  SAP BW/4HANA Roadmap

 Architecture  Quiz session

 Cade-to-Data Paradigm  Q&A

 AMDP

 CDS

 Data Provisioning

 New Objects in BW4HANA

 Key Features
Question

What is an Enterprise Data Warehouse?

What is an Enterprise Data Warehouse?
Characteristics

 Consolidates data across the enterprise

 Standardized data model
 Supports decision making

Main Tasks

 Harmonize data values.

 Establish a ‘single version of truth’.
 Provide a single, comprehensive source of current and historical Information.
 Keep copy of source data to ensure independency of source and support the unknown.

Modern Challenges for Data Warehouses

 Different Locations –cloud, data lakes

 Additional Types – behavioral data, IoT (Structured and Unstructured)
 Higher Volumes – > 40% growth YoY
Enterprise Data Warehousing with SAP BW/4HANA
Introduction
SAP BW/4HANA is an evolution of SAP BW that is completely optimized and tailored to SAP HANA. It is
SAP’s next generation data warehouse solution and a new product (not a legal successor of any existing
SAP Business Warehouse solution), built entirely on one of the most advanced in-memory platforms
today – SAP HANA.

SAP BW/4HANA…
 is a new data warehouse solution
 is highly optimized for SAP HANA
 solves analytics problems in
seconds
 accelerates the solution
development
 is ready for the internet of things
at petabyte scale
Introduction
 Normal SAP BW release, built on NetWeaver
which supports classic objects only and can run on
any database.
 SAP BW on HANA/ powered by HANA is more
robust optimization to SAP HANA as a database
backend. Supports legacy objects such as Info
Cubes but also support HANA optimize objects like
Composite provider.
 New BW that is BW/4HANA built on lean ABAP
application server which supports only HANA-
optimized objects. 

Note:
We need to upgrade system to move to BW on HANA from any previous version but to move to
BW/4HANA customer have to migrate system from SAP BW on HANA 7.5 to BW/4HANA.
Evolution From SAP BW/4HANA 1.0 to 2.0
Benefits to Business
BW∕4HANA Architecture

SAP BW∕4HANA is a highly optimized data warehouse

solution for the SAP HANA platform  inheriting the high
performance, simplicity, and agility of SAP HANA.

BW/4HANA offers the possibility to design a true logical

EDW platform that can help customers to run their EDW
in a real-time fashion, but also caters to all possible
scenarios that a modern data warehouse demands…
such as out of the box big data connectivity, smart data
tearing, cloud readiness, advanced analytics, planning &
consolidation, advanced processing like predictive,
geospatial, text analysis etc.

SAP BW∕4HANA has an open architecture. This enables

the integration of external, non-SAP sources and the
distribution of BW data in downstream systems via the
open hub service.
Architecture
The overall SAP BW/4HANA architecture can be
grouped into four parts:

1. Consumption (Purple color): SAP Analytics and SAP

Planning on premise or in the cloud, or third party
solutions.
2. Application (Red color): SAP ABAP-based stack with
data warehousing core functions. The focus is in the
orchestration of those as the runtime is pushed to SAP
HANA where ever possible.
3. Platform (Yellow color): SAP HANA provides the
platform for all data management tasks but enhances
the application logic with its modeling, calculation and
integration services.
4. Sources (Grey color): The sources for all data to be
integrated physically or virtually. Most of them
leverage interfaces provided by SAP HANA or SAP
NetWeaver.
OLAP & Planning Functions
Analytic Manager
 Analytic Manager is the built - in OLAP engine of BW
 The majority of analytical functions in BW/4HANA are pushed
down to HANA and executed directly in the database.
 Rich set of analytical capabilities like
• Hierarchy handling,
• Currency and unit conversions
• Exception aggregation & conditions
• Restricted and calculated key figures
• Inventory handling for non cumulative key figures

Planning Capabilities
 Provide rich set of in-memory optimized planning capabilities
using the
 SAP Business Planning and Consolidation, version for SAP
BW/4HANA:
• Aggregation, Disaggregation, Conversions, Revaluation
• Copy, Delete, Set value, Repost, FOX-Formulas
 Supports embedded and standard models
Code-to-Data Paradigm

Code pushdown or Code to

Data is just a mechanism that
Pushes the code to the database
layer and get required result set
instead of getting all the data to
the application layer and write the
code in the application layer to get
the required output. 

Currently Top-Down approach is

used in the CDS views and ABAP
Managed Database Procedures
(AMDP).
AMDP
 ABAP Managed Database Procedures are new feature available in AS ABAP 7.40, SP05.
 It is a class-based framework for managing and calling database procedures (or) stored
procedures in ABAP.
 An ABAP Managed Database Procedure is a procedure written in its database-specific language
(SQL) implemented in an AMDP method of an AMDP class.
 A AMDP class is a global class which contains marker tag interface IF_AMDP_MARKER_XXX,
where XXX means database like IF_AMDP_MARKER_HDB for SAP HANA database.

Advantages

 Easily implemented in ABAP and SQL script can be used.

 Powerful functions of native HANA like currency conversion and CE functions can be used.
 Code change at runtime is possible in debugging.
CDS
CDS Views allow developers to create data models which
expose to UI clients. It is the central pillar of S/4HANA
development. With CDS, data models are defined and
consumed on database server rather than on application
server. It is an enhancement of SQL for defining
semantically rich database CDS entities. Some
enhancements include: Expressions, Associations &
Annotations.
Advantage of Using CDS:

 With the help of Core Data Services, we can expose data in views which are compatible with ABAP
Dictionary.
 We can perform complex queries, associations and join operations and reuse existing CDS views.
 We can use CDS view inside the ABAP® program with AMDP to Take Advantage of the Performance of HANA
and Features of ABAP.
 CDS also come up with feature-rich annotations, with the help of which we can expose CDS views as OData
source in few simple steps.
 Transport CDS views across multiple systems with ABAP transport system.
CDS Types
There are 2 main CDS views, Interface views (Basic and
Composite) and consumption views.

 Basic views (Core Entity views, Text view and Hierarchy views) are built
directly on top of DDIC tables or views and hence interact with database
tables for fetching data.
 Composite Views are built on top of one or more basic views. Multiple
basic views can be joined, and calculation done (using expressions and
functions) to make a composite view.
 Consumption Views are built on top of composite views and hence do not
interact either with basic views or DDIC tables. Consumptions views are the
ones which are exposed to the front-end tools
 Predefined View: Predefined View is the predefined CDS Views for business
entities or for applications in S/4HANA Iike I_PURCHASEORDERITEM.
 Extend View: Extend View is used to add fields to predefined views without
changing predefined VDM itself. It is possible to associate the view and add
it in the source view, and it is also possible to use the association for foreign
key association on the added field. 
CDS Consumption
CDS Views can be consumed in many ways as a data source. Whether it is well known ALV report or
modern SAP Fiori application with the CDS view exposed using SAP Gateway in the OData format.
SAP BW/4HANA – Mixed Data Model Integration
Use the best of both worlds

 Reuse both BW and SQL skills.

 Seamless data model integration.
 Use your data at the frequency they are
generated: batch, real - time, stream or
remote.
 Store data once – use multiple times.
 Consume via native HANA SQL or BW
query
by any tool.
 Add predictive, spatial and other HANA
platform features.
System Conversion (BW on DB/HANA to BW/4HANA)
For an SAP customer who is using SAP BW as their primary tool for analytics and reporting, SAP
BW/4HANA is the next recommended and logical upgrade in their journey for building an EDW platform.

For customers running SAP BW powered by SAP HANA or any DB today, who choose to move to SAP
BW/4HANA, Initial and mandatory step is to upgrading to SAP BW 7.5 (SP02) on HANA and applying the
SAP BW/4HANA Starter add-on as an intermediate step.

SAP has provided different migration options for BW4/HANA, you can find more details on this note 
2383530-Conversion from SAP BW to BW/4HANA.

Converting a SAP BW system to SAP BW/4HANA is not a simple task. There is no "wizard" that magically
converts everything. Instead, SAP provides a well-defined process to guide you through the renovation of
your data warehouse. We have developed tools to automate this renovation where applicable and
feasible.

In any conversion there is a need for manual interaction and re-design. The amount of such manual tasks
varies from customer to customer and depends state of the SAP BW system.
Paths to SAP BW/4 HANA
Paths to SAP BW/4 HANA

1. New implementation or fresh start

New implementations are the best choice for customers converting from a legacy system or building a system from
scratch with new data model only.

Steps: Install SAP BW/4HANA, selective transport of BW objects (optional), implement HANA-optimized data models
and flows, followed by data load and quality checks.

2. System conversion

A system conversion addresses customers who want to change their current SAP BW system into a SAP BW/4HANA
system using the Transfer Cockpit provided by SAP. The logical systemname of the system can be kept (in-place
conversion) or a new  logical systemname can be used (remote conversion resp. shell conversion).

A conversion project typically follows sequence check system for BW/4HANA compliance gather information about
objects and code that needs to be transferred or changed later transfer legacy objects into HANA-optimized
counterparts, system conversion, post conversion tasks.

In-place, Remote & shell conversion are three different approaches for system conversion.
System Conversion
2.1 In-Place conversion

Systems running on SAP BW 7.50 powered by SAP HANA can be converted in-place keeping their logical
system-name. In the realization phase the transfer can be performed scenario-by-scenario where all
classic objects have been replaced. SAP highly recommends to use the latest support package for SAP
BW/4HANA when performing the conversion.

Steps: Migrate and/or upgrade to SAP BW 7.50 powered by SAP HANA (if necessary), install SAP
BW/4HANA Starter Add-On (see “Installation” below), install Transfer Cockpit, transfer data models, adjust
custom coding, perform system conversion.
System Conversion
2.2 Remote conversion

For SAP BW systems on releases from 7.30 to 7.50 running on Any-DB, a remote conversion can be
performed. For that conversion type, a green field installation (new  logical systemname) of SAP
BW/4HANA is used. The Transfer Cockpit is able to transport selected data models into the new
installation and to perform a remote data transfer.

Steps: Install SAP BW/4HANA, install DMIS Add-On, transfer data models, transport custom developments
(might need adjustment to work with SAP BW/4HANA).

2.3 Shell conversion

For SAP BW systems on releases from 7.00 to 7.50 running on Any-DB, a Shell conversion can be
performed. For that conversion type, a green field installation (new  logical systemname) of
SAP BW/4HANA is used. The Transfer Cockpit is able to transport selected data models without data into
the new installation.

Steps: Install SAP BW/4HANA, transfer data models without data using SAP BW/4HANA Transfer Cockpit,
and transport custom developments (might need adjustments to work with SAP BW/4HANA).
3. Landscape Transformation
Landscape transformation is for customers who want to consolidate and optimize their complex SAP BW
landscape (multiple production systems) into a single SAP BW/4HANA system or who want to carve-out
selected data models or flows into a global SAP BW/4HANA system.

Steps: Install SAP BW/4HANA, implement consolidated and HANA-optimized data models and flows,
followed by data load and quality checks.
Question
Q. Suppose your organization have multiple SAP BW systems on oracle DB for various regions over
globe. So, which path (New install, System conversion or Landscape transformation) you will choose for
this case, using below recommendations from SAP?
Simplified Data Provisioning

Number of Source System Types reduced from 7

to 4.

 ODP Source System (For SAP sources such as

ECC, SRM , CRM etc., including SLT).

 HANA Source System (For non-SAP sources,

including Hadoop data lakes (using EIM –
SDI).

 Flat File

 Big Data
New objects corresponding to old ones

 Number of Modelling object types reduced

from 10 to 4

 No complex data structures (extended star

schema)

 Field or Infoobject based Modelling Greater

control of data persistency and
virtualization.

 Support for external, structured and

unstructured data
SAP BW/4HANA Key Features
In-memory Data Warehousing – SAP BW/4HANA brings real-time performance to the EDW with in-
memory data warehouse processing. In-memory processing not only provides a performance boost of 10-
1000X over standard disk-access database environments, it vastly simplifies the structure of the data
warehouse and the amount of work required to make it functional.
An in-memory data warehouse running on HANA requires no performance-boosting objects to be built or
maintained. It does not require aggregates or roll-up processes.

Simplified Data Structures and Flows- SAP BW/4HANA accelerates and reduces the complexity of
designing, implementing, and modifying a data warehouse environment via simplified data structures
data flows. 

Native SQL Access SAP BW/4HANA enables users to access SAP HANA logic and data via SQL queries.
Users can run SQL queries to generate calculated HANA views of data. Automatically generating SAP
HANA views enables users to deploy SQL logic on top of generated views.

Smart Data Access SAP HANA Smart Data Access is a virtualization technique that enables businesses to
merge data in heterogeneous EDW landscapes and to access remote data without having to replicate the
data to the SAP HANA database first.
Features
Dynamic Tiering SAP’s dynamic tiring provides the ability to store data either in memory or on disk in a
columnar format via the high-performance SAP IQ analytics relational database. This enables users to
assign hot (active) data to the in-memory environment while handling warm (less critical) data in IQ.
Cooler data (data that is less likely to be accessed) can be moved to near-line storage (NLS).

Advanced Analytics SAP BW/4HANA supports advanced analytics via the wide variety of analytical
functions already available in the HANA Application Function Library (AFL) or via custom HANA
procedures. Core analytics capabilities available via AFL include:

 Predictive
 Text Analysis
 Data Mining
 Machine Learning

SAP BW/4HANA also supports analytical procedures written in Rscript, the scripting front-end of the R
analytical programming language.
Things NOT supported in BW/4HANA
 The SAP Business Explorer (BEx) are not supported any more. Queries are now defined in SAP BW,
Edition for SAP HANA in the BW Modeling tools.

 BW4/HANA does not support traditional BEx tools such as Web Application Designer, Web templates,
Analyzer, Workbooks etc.

 Modeling in the Data Warehousing Workbench (SAPGUI) is replaced by modeling in the BW Modeling
tools in Eclipse. 

 BW4/HANA does not support legacy BW objects like Multiprovider, Infocubes, Infosets 　 etc. All
Classical objects need to be migrated to BW/4HANA supported objects using the migration tools
provided.

 PSA maintenance and related process types in process chains are NOT supported. Hence, InfoPackage
creation, maintenance and related process types in process chains are also NOT supported.

 Object types from the 3.x data flow are not supported any more and must be migrated.
Design Principles
SAP BW/4HANA has been designed according to four central principles:
1. Simplicity
2. Modern UI
3. Openness
4. High Performance
Design Principles
1. Simplicity

SAP BW/4HANA aims to reduce the complexity of the development

environment and decrease the end-to-end development time.
BW/4HANA has reduced the number of modelling objects from 10 to
4. Two of the objects will allow for persistency of data and 2 objects
are for virtualization that allows for fewer layers. This simplification
helps to make the architecture leaner and more flexible, and less
development effort. The reduction in persistence of data cuts down
the data foot print. Along with SAP’s increased capability for Cloud
deployment, including HANA Enterprise Cloud, Microsoft Azure and
Amazon Web Services, this all leads to helping bring down the TCO
for BW/4HANA.
Design Principles
2. Openness

There are two aspects to openness:

 Bringing data into BW from different data sources and

 Being able to consume data from BW.

The integration of data and solutions from data sources, including

3rd party applications and data stores in Hadoop or cloud, whether
structured and unstructured, has been made easier. In terms of
utilizing data, the BW objects easily allow for exposing of data for
SQL consumption by front-end tools
Design Principles
3. High Performance

BW/4HANA is designed to push an increased amount of OLAP

functionality and computation to the HANA database as well as for
the Planning and Data Management elements. But the higher
performance for BW/4HANA is not just about pushing the
workload to the HANA engine. It is also about the greater
integration to leverage the HANA platform capabilities within BW,
for example, integrating data from a HANA model into a BW
model. In addition, BW/4HANA provides the capability to leverage
various advanced analytical libraries and algorithms for data
mining or predictive analytic scenarios.
Design Principles
4. Modern UI

To align to the changes in the BW/4HANA, simpler and more

modern interfaces are available for business users, developers and
administrators. For Business users, the BEx interface is no longer
available (although BEx Queries still form part of the solution), and
BW/4HANA has tighter integration with the SAP Business Objects
BI toolset, as well as SAP Business Objects Cloud. The developer
interface is via the Modelling tools integrated into SAP HANA
Studio and Eclipse, and from an administrator perspective, UI5
tools such as the UI5-based Process Chain Monitor are available as
a replacement for the ABAP Process Chain Monitor.
SAP BW/4HANA Roadmap
Simplicity
 Data Tiering Optimization (DTO) − Machine Learning based automation.
 Further cloud storage options for cold data based on SAP Vora.
 Data Protection Workbench

Modern Interface
 Continued System Health Monitoring and Prediction.
 Continued Machine-learning Based DW Administration.
 Enhanced Web-based Administration & Monitoring.

Openness
 Further integration with SAP Data Hub providing Big Data Warehouse architectures common transports &
improved impact analysis and seamless data exchange.
 Open Hub Modernization.
 Integration with SAP Cloud Platform.

High Performance
 Leveraging new SAP HANA engine capabilities for Analytics and Transformations.
 Advanced Analytics Environment
SAP BW/4HANA is SAP‘s strategic EDW solution
SAP BW/4HANA offers fully integrated data warehouse application with

 Agile and flexible data modelling to also combine BW and native SQL data for real - time insights.

 Predefined Content for fast implementation.

 Sophisticated data acquisition with rich scheduling & monitoring.

 Integrated lifecycle management for metadata.

 Built - in Data Tiering Optimization for hot, warm and cold data.

 Detailed security & auditing.

Quiz Time
Quiz
Q1. Number of Source System Types supported by BW4HANA are:

A. 10
B. 5
C. 4
D. 3

Q2. SAP BW/4HANA is a separate product which is not part of and does not depend on a Net Weaver delivery. 

E. True
F. False

Q3. Which one of the following is the design principle of SAP BW4HANA

G. Exploratory Analysis
H. Effective Loading
I. Modern UI
J. Adaptive
Quiz
Q4. Which of the following objects are supported in SAP BW/4HANA

A. Composite Provider
B. ADSO
C. InfoSets
D. Hybrid Provider

Q5. Which SAP HANA Platform capabilities are integrated in SAP BW/4HANA?

E. Predictive Algorithms
F. SAP HANA Scala scripts
G. SAP HANA Models
H. Smart Data Quality (SDQ)
Quiz
Q1. Number of Source System Types supported by BW4HANA?

C. 4

Q2. SAP BW/4HANA is a separate product which is not part of and does not depend on a Net Weaver delivery. 

A. True

Q3. Which one of the following is the design principle of SAP BW4HANA

C. Modern UI

Q4. Which of the following objects are supported in SAP BW/4HANA

A. composite Provider B. ADSO

Q5. Which SAP HANA Platform capabilities are integrated in SAP BW/4HANA?

A. Predictive Algorithms C. SAP HANA Models

 Thank You…
Abhishek Patel

© 2019 YASH Technologies | www.yash.com | Confidential