lsa++ for sap netweaver bw on sap hana · bw edw with lsa is the accepted approach (not just for...
TRANSCRIPT
Juergen Haupt / CSA 08, 2012
EIM203
LSA++ (Layered Scalable Architecture) for SAP NetWeaver BW on SAP HANA
© 2012 SAP AG. All rights reserved. 2
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.
© 2012 SAP AG. All rights reserved. 3
Agenda
LSA++ - the holistic Picture for BI on structured Data
LSA++ Focus on Flexibility, Agility, Virtualization, Openness and Consistency
LSA++ flexible consistent EDW Core
Streamlined EDW & Architected Data Marts
LSA++ Open Operational Data Store Layer
Joining Operational BI & EDW
LSA++ Virtual Data Mart Layer
Summary
LSA++ - The holistic Picture for
BI on structured Data
© 2012 SAP AG. All rights reserved. 5
BW EDW LSA Grid Consistent EDW Architecture – Consistent BI & Reporting
BW EDW Standard LSA Layers
Layer and naming qualifier
BW EDW LSA Data Domains ^(standard Partitioning)
Example: C D B F E A
Standard Logical Partitions (Domains) and naming qualifier
Naming (e.g. DSO)
‒ Layer: byte 1
‒ Content Area: byte 2 to 5
‒ Sequence number: byte 6
‒ Domain: byte 7
‒ Sub-Partition: byte 8
Technical name of
DSO
© 2012 SAP AG. All rights reserved. 6
LSA standardized template-based Implementation – Templates as Link between LSA Blueprint & Implementation
Customer
EDW LSA Blueprint:
Standards & Guidelines
BW Projects using
Templates :
Consistent Implementation
adopting
LSA Blueprint
Standards & Guidelines
Templates: Data FlowTemplates
SPO Partition
Templates
© 2012 SAP AG. All rights reserved. 7
EDW, Data Marts and Model Richness Consistent BI on Consistent EDW
EDW
data model
Business View
Data Mart Model
source
data models
EDW transform
Data Mart transform
(Architected) Data Marts
built on EDW Model Data Marts
built on Source Models
Business View
Data Mart model
source
data models
Data Mart transform
© 2012 SAP AG. All rights reserved. 8
BW EDW with LSA is the accepted approach (not just for large companies) guaranteeing
standardized BI & Reporting on all organizational levels (local, regional, global) on the same
consistent, common data foundation (single version of truth)
BW EDW with LSA stands for:
High availability - 24x7
operational robustness
organizational independency
scalability
maintainability e.a.
The LSA is the corporate framework
for BW to manage reliably
the entire data & meta data life cycle:
Data delivery (extraction, RDA)
Data modeling (assign InfoObjects)
Data staging
Authorizations
Solution delivery (transports)
BW Layered Scalable Architetcure - Value & Positioning consistent, high Availability EDW for standardized BI
© 2012 SAP AG. All rights reserved. 9
Perception of BW EDW with LSA on RDBMS Shortcomings
An BW EDW with LSA is perceived as highly valuable but
costly: building it, moving steadily data to and within the EDW
not flexible enough: EDW/LSA standards, central development, overall responsiveness to business
needs (operational & agile BI)
Number of persistent InfoProvider
overall missing flexibility, agility
No direct business value of Acquisition Layer
EDW model (InfoObjects) assignment
Staging of data
Low Adoption of Near Real Time reporting
Costs of Corporate Memory
Setting up BW EDW - time to ROI
The BW data model (InfoObjects) must
be defined
The customer LSA must be defined
© 2012 SAP AG. All rights reserved. 10
Virtualization Layer
LSA++ for BW on HANA – A Holistic Framework LSA++ Principal Layers & BI Value Areas
Data Acquisition Layer
Op
era
tion
al
Data
Sto
re
Reporting Layer
(Architected Data Marts) Business Transformation
Layer
Data Propagation Layer
Harmonisation Layer
Corporate
Memory
EDW context data
Flexible Consistent
EDW Core
LS
A
LS
A+
+
Virtualization Virtual Data Mart Layer
Streamlined consistent EDW Core for
flexibility & lower TCO/ TCD • HANA-Optimized InfoProvider
• Direct data provisioning
• Real Time Master Data
Streamlined consistent EDW Core for
flexibility & lower TCO/D • Virtual Data Marts
• Queryable EDW Layers
• InfoProvider modeling
Standardized template-based BI
on LSA consistent EDW Core •Transparent (Layer)
• Scalable (Domains)
• Model-driven (EDW data model)
Consistent
EDW Core
© 2012 SAP AG. All rights reserved. 11
LSA++ for BW on HANA – A Holistic Framework LSA++ Principal Layers & BI Value Areas
Data Acquisition Layer
Op
era
tion
al
Data
Sto
re
EDW context data
Flexible Consistent
EDW Core
LS
A
LS
A+
+
Virtualization Virtual Data Mart Layer
Source context data Operational BI New LSA++ Inbound Layer on field-
level data (source models)
• Openess, Scalable BW Services
• Immediate querying
• ETL or Real Time
Open ODS Layer
(Open Operational Data Store)
Open ODS Layer for Operational BI
& Virtual Data Marts
• Wrapping & Combining
• Scalable integration with EDW
Operational BI Open ODS Layer on field-level data
(source models inherited)
• Openess, Scalable BW Services
• Immediate querying
• ETL or Real Time
Virtualization Virtual Data Mart Layer
© 2012 SAP AG. All rights reserved. 12
LSA++ for BW on HANA – A Holistic Framework LSA++ Principal Layers & BI Value Areas
EDW context data
Flexible Consistent
EDW Core
LS
A
LS
A+
+
Virtualization Virtual Data Mart Layer
Source context data Open ODS Layer
(Open Operational Data Store)
Agile
context data
Agile
Data Marts
Agile BI Central IT - Ad hoc productive solutions
•single time
•productive prototype
Departmental Agile Data Marts (BW
Workspaces)
Virtualization Virtual Data Mart Layer
Agile BI • Virtual Agile Data Marts combing volatile ad-hoc
data with EDW Core & Open ODS data
• Virtual Agile Data Marts wrapping of ad hoc data
© 2012 SAP AG. All rights reserved. 13
Open Operational Data Store Operational Extension
BW / Externally managed
LSA++ Holistic Framework
LSA++ Principal Persistent Layer
EDW Layers
Ag
ile
Data
Ma
rt L
aye
r
BW
Wo
rksp
ace
(La
yer)
Flexible Consistent
EDW Core
Architected
Data Marts
LS
A+
+
Prin
cip
al L
ayer
Dep
artm
en
tal
Ag
ile E
xte
nsio
n
Cen
tral
Ag
ile
Exte
nsio
n
© 2012 SAP AG. All rights reserved. 14
LSA++ Holistic Framework BI Flavours and LSA++ Principal Layers
Different BI flavours request for different services. LSA++ takes this into consideration structuring
data by purpose/ context with respect to BI requirements - this results in the principal layers:
Flexible Consistent EDW Core: EDW context data – Standardized template-based BI and Reporting on harmonized, consistent data
Operational Extension of the Core: Operational/ source context data – Operational / real time BI on source-level data
Agile Extension of the Core: Agile, ad hoc context data – Agile BI on all kind of data – single usage
LSA++ purifies the EDW Core addressing services for operational & agile purpose data
- free the EDW core from cholesterol -
This by itself increases overall flexibility and manageability
LS
A+
+
Prin
cip
al
La
ye
rs
LSA++
Operational
Extension
Source context
data
LSA++
Flexible
Consistent
Core
EDW context data
LSA++
Agile
Extension
Agile/ad hoc
context data
© 2012 SAP AG. All rights reserved. 15
LSA++ Holistic Framework Characteristics of Principal Layers & BI Solutions
BI solutions based on different LSA++ principal Layers have decisive differences with
respect to e.g. • Data model
• Solution time-to-market
• Data Processing
• Ownership
• Consistency
• Stability & Robustness
• BI query result stability
• Revision capability.....
Data model: Deployment:
© 2012 SAP AG. All rights reserved. 16
LSA++ Holistic Framework for BW on HANA flexible consistent Data Framework virtually Wrapped
BI on Streamlined EDW - Operational BI – Agile BI – Virtualization - Open BW Services
BW
Op
en
Serv
ices:
Data
Mo
del,
OL
AP
, A
uth
ori
zati
on
, D
ata
Ag
ing
BW Virtual Data Mart Layer
Architected Data Mart Layer
Business Transformations
EDW Propagation
Layer
EDW Transformation Layer
Externally managed BW managed
Open Operational Data Store Layer
Agile
DMs/
BW
Work
space
Cen
tral B
I- P
rom
ote
To
Pro
du
cti
on
Ag
ile
BI
- cen
tral/
dep
art
men
tal
LS
A+
+ fo
r BW
on
HA
NA
B
I on S
tream
lined
ED
W ,
Ope
ratio
na
l BI, A
gile
BI
Co
rpo
rate
Me
mo
ry
refe
ren
ce
BW Queries
EPM , BO BI, Apps
LSA++
flexible consistent EDW Core
Streamlined EDW & Architected Data Marts
© 2012 SAP AG. All rights reserved. 18
LSA++ EDW & Architected Data Marts Value Scenarios
Classic BW EDW Implementation Perspective
EDW & Architected Data Mart layers - reliable, manageable, consistent
Streamlined EDW & Architected Data Marts
• HANA-Optimized InfoProvider – increased availability, lower TCO
• Virtualization of persistent Data Marts (InfoCubes) - increased availability, lower TCO
• Queryable EDW layers - increased availability, lower TCO
• Virtual Data Marts – increased flexibility, lower TCO
• Real Time EDW Master Data – new solutions, lower TCO
• New modeling options – increased flexibility & coverage of business needs
• Flexible Master Data Modeling thru virtually joining semi-stable master data
• Large Master Data Modeling avoiding realignment thru compounding instead of
fact-table join
• New inventory modeling
…….
© 2012 SAP AG. All rights reserved. 19
LSA++ Layer Structure of Flexible Consistent EDW Core The LSA Heritage - Reliable, Managable, Consistent Data
LSA++ inherits the service definitions of LSA EDW Layers that stand for reliability &
consistency:
EDW Transformation Layer (Link between source-model and EDW-model)
(EDW) Corporate Memory (Persistent )
(EDW) Propagation Layer (Persistent )
Business Transformation Layer (Link between EDW-model and Data Mart model)
Architected Data Mart Layer (Persistent )
These Layers define
the consistent Core:
© 2012 SAP AG. All rights reserved. 20
LSA++ for BW on HANA Value Scenario Reliable Consistent EDW Core
EDW Core services are:
1. Transparency & addressability of different
quality stages of data
2. Managing different levels of data
harmonization within the organization
3. Maintainability thru transparent standards
4. Robustness thru standards
5. Auditability & reproducibility
6. Reusable, Digestible, Comprehensive EDW data mean consistency & flexibility
same reusable reliable consistent data foundation for all (Architected) Data Marts - extract once, deploy many
reusable meta data foundation (InfoObjects, InfoProvider)
7. Consistent, accurate query results, avoiding errors, miss-interpretations, reducing virtual complexity
8. Query performance - avoiding redundant calculations, transformations, (high cardinality) combinations
(joins) thru persistent Architected Data Mart
© 2012 SAP AG. All rights reserved. 21
LSA++ for BW on HANA Value Scenario Streamlined EDW - Reducing Flexibility Impact of Persistent Provider
LSA++ EDW persistent Provider offer accepted services in
(EDW) Corporate Memory
(EDW) Propagation Layer
Architected Data Mart Layer
But: persistent Provider have a huge influence on overall flexibility and cost
Flexibility is low & TCO is high if any new requirements result in changing or adding of persistent
providers (meta data & data content)
TCO is high & SLA fulfillment is low if source- or operational- issues lead to changes of persistent
providers (rebuild, recover of data content)
LSA++ focus is on Streamlining the Consistent EDW Core by
reducing number of persistent provider
optimizing design and implementation of persistent provider
reducing change impact on persistent provider
LSA++ Flexible Consistent EDW Core
© 2012 SAP AG. All rights reserved. 22
LSA++ for BW on HANA Value Scenario Streamlined EDW - EDW Propagation Layer using HANA Optimized DSOs
Increased availability thru dramatic decrease of load and activation time
Increased modeling flexibility
Increased flexibility & value thru comprehensive data content offering of Propagation Layer
Relaxed volume considerations during design time (Domains/ semantical Partitioning)
comprehensive
fast
dire
ct
Flexible, relaxed modeling
© 2012 SAP AG. All rights reserved. 23
LSA++ for BW on HANA Value Scenario Streamlined EDW - Architected Data Marts using HANA Optimized InfoProvider
LSA++ Architected Data Mart Layer should use HANA Optimized InfoCubes and/ or HANA
Optimized DSOs (Business Transformation Layer) in case there is a need for persistent
Architected Data Mart (s. Virtual Data Marts)
LSA++ Architected Data Mart Layer using HANA Optimized InfoCubes means
Increased flexibility thru dramatic decrease of load time (no dimension tables)
Increased modeling flexibility
No multi-dimensional modeling
skills needed
Relaxed volume considerations
during design time
(-> Domains/ semantical
Partitioning)
fast
Flexible, relaxed modeling
© 2012 SAP AG. All rights reserved. 24
Queries on DSOs (sid-enabled) show
similar performance compared to queries
on InfoCubes
LSA++ for BW on HANA Value Scenario Streamlined EDW - Virtualization of persistent Data Marts (InfoCubes)
BW Virtual Data Mart Layer
Architected Data Marts
Business Transformations
EDW Propagation
Layer
EDW Transformations
Co
rpo
rate
Me
mo
ry
MultiProvider
Composite Provider
© 2012 SAP AG. All rights reserved. 25
Streamlined EDW - Virtualization of InfoCubes Obsolete: InfoCubes as Accelerator on Business Transformation Layer DSOs
© 2012 SAP AG. All rights reserved. 26
Streamlined EDW - Virtualization of InfoCubes DSOs in Business Transformation Layer as Query Target
With complex business requirements we often find DSOs in the Business Transformation Layer
reducing complexity of transformations and/ or synchronizing various data sources
There is one final DSO in the flow that offers the result of all transformations
In LSA under RDBMS the result-DSO data are then transferred 1:1 to an InfoCube for query
performance reasons
Such InfoCubes are obsolete
Please observe notes given on obsolete InfoCubes
© 2012 SAP AG. All rights reserved. 27
Streamlined EDW - Virtualization of InfoCubes Eliminating InfoCubes – Things to Keep in Mind
An InfoCube is only an accelerator for queries on a DSO placed in the data flow before
the InfoCube if
The content of the InfoCube is derived from the DSO by a selection (DTP) and/ or a projection on the
DSO InfoObjects
The InfoCube does not contain information that is not contained in the DSO
No additional consistency checks (referential integrity) are performed loading the InfoCube
Such InfoCubes can be eliminated easily if a MultiProvider is defined on top of the InfoCubes and
queries access the InfoCubes via the MultiProvider (anyhow Best Practice) replacing the InfoCubes by
the DSOs
Before deleting the InfoCubes the query performance on the MultiProvider now working with DSOs
should be verified (RSRT)
Important for working with DSOs under a MultiProvider is that query pruning takes place (like with
InfoCubes under a MultiProvider) -> BW 7.30 SP7/8
The DSOs should be SID-enabled before querying on DSOs!
© 2012 SAP AG. All rights reserved. 28
LSA++ for BW on HANA Value Scenario Streamlined EDW – EDW Propagation Layer as Query Target
In publications we can read that the EDW in general is not a query target.
The reason for this statement is not that the EDW content is of no value on the contrary – the
reason is more that queries running on EDW tables on RDBMS will most likely not come back
(no secondary index = full table scan)
With LSA++ and BW on HANA you can run queries on Propagator Layer DSOs (SID-
enabled) with similar performance like on InfoCubes
© 2012 SAP AG. All rights reserved. 29
Streamlined EDW – EDW Propagation Layer as Query Target
US APJ EU
US AP EU
ED
W
Pro
pa
ga
tio
n
La
ye
r
Bu
sin
es
s
Tra
ns
form
ati
on
La
ye
r
Arc
hit
ec
ted
Data
Ma
rt
La
ye
r
LSA & BW on RDBMS LSA++ & BW on HANA
US APJ EU
1:1
© 2012 SAP AG. All rights reserved. 30
LSA++ for BW on HANA Value Scenario Streamlined EDW – Virtual Data Mart Layer
SAP HANA propagates working on basic
persistent providers doing all combinations
(joins) and transformations of data during
query execution instead of making the results
of combinations and transformations
persistent in a provider (staged approach)
The LSA++ home of virtual combinations is
the Virtual Data Mart Layer with Composite &
MultiProviders – the home of virtual
transformations is the BW query layer.
© 2012 SAP AG. All rights reserved. 31
Streamlined EDW - Virtual Data Mart Layer CompositeProviders – Virtualization or Persistent Join?
Scenario:
Multiple DataStore Objects loading into a single InfoProvider
Nowadays the relation between data (“join”) is modeled in BW transformation (routine) and loaded to a
DSO or through updating (overwrite) of a target DSO
UNION Join in MultiProvider doesn‟t correspond to reporting requirements
C Reporting Reporting
LSA
SAP NetWeaver BW
LSA++
SAP NetWeaver BW
powered by HANA
Composite
Provider
© 2012 SAP AG. All rights reserved. 32
Streamlined EDW - Virtual Data Mart Layer CompositeProviders
JOINs between InfoProvider –
Combine BW InfoProvider using the JOIN
operations (inner, left outer, union join)
Transaction RSLIMOBW.
© 2012 SAP AG. All rights reserved. 33
Composite Provider Considerations Things to keep in Mind – Test before replace a persistent BW Provider
HANA is not an OLAP Engine but a data base
A lot of BW query function results are provided by the BW OlAP engine not by the data base
– not all BW OLAP operations have been pushed down to OLAP calculation engine on HANA yet
– for a foreseeable time we will have still a separation of query work packages between HANA DB, OLAP
calculation engine on HANA and OLAP engine on the BW application server.
Development is continuously pushing down OLAP engine functionality to HANA what makes it difficult
giving a stable recommendations about virtualization of persistent providers
Roughly speaking: each query that needs the application server OLAP engine working on granular data to
provide the right result is expensive (correlating to the no of records that have to be transferred to the
application server OLAP engine)
: provided by OLAP Engine
© 2012 SAP AG. All rights reserved. 34
Decision Criteria on Using Composite Provider Architected Data Marts and BW Virtual Data Mart Layer
Goal: Virtualization of Architectured Data Mart Layer
Granularity / Cardinality
Architected Data Mart
vs. EDW Propagation Layer
Transformation / Join logic
EDW Propagation Layer to
Architected Data Mart
High/
same
low
no low complex
Investigate
Replace Data Mart
Keep Data Mart
Investigate
© 2012 SAP AG. All rights reserved. 35
Model & Content Stability of Persistent Provider Corporate Master Data and Local Attributes on RDBMS
Without HANA we can hardly avoid merging data of different stability into persistent InfoProvider
and InfoObjects – this causes huge impact on the stability of the resulting Architected Data
Marts!
Corporate
process
Central Template
Architected Data Mart
Corporate
Process –
Local Extension
Local Master data
semi-stable stable
© 2012 SAP AG. All rights reserved. 36
LSA++ for BW on HANA Value Scenario - Flexible Master Data Model
Corporate Master Data and Local Attributes
Corporate
Process
Stable core
Corporate
Process –
Local extension
Centr
al T
em
pla
te
pers
iste
nt
Arc
hitecte
d D
ata
Ma
rt
Stable Core corporate
master data local
master data
Departmental –
Departmental
extension
departmental master data
LSA++: Avoid merging data of different stability in an Architected Data Mart or InfoObject –
Instead use Virtual Data Marts (Composite Provider/ MultiProvider) to combine extensions with
the stable Architected Data Marts
Local / departmental attributes
joined via
Composite Provider
Virtual Data Marts
© 2012 SAP AG. All rights reserved. 37
LSA++ for BW on HANA Value Scenario - Flexible InfoProvider Model
Composite Provider Joining Core Providers with Local Masterdata
C_COSTC C_ATTR_1 C_ATTR_2
1 A AA
2 B BB
3 C CC
G_COSTC G_ATTR_1 C_COSTC
1 X 1
2 Y 2
3 Z 3
U_COSTC U_ATTR_1 C_COSTC
1 O 1
2 P 2
3 Q 3
DATE C_COSTC C_AMOUNT
20120301 1 30
20120301 2 50
20120301 3 60
20120302 1 10
20120302 2 20
CompositeProvider
Germany
CompositeProvider
US
Corporate Master Data
InfoProvider
Corporate
German Master Data
US Master Data
LSA++ Open Operational Data
Store Layer
Joining Operational BI & EDW
© 2012 SAP AG. All rights reserved. 39
LSA++ Holistic Framework for BW on HANA Open Operational Data Store Layer - Targets
BI on Streamlined EDW - Operational BI – Agile BI – Virtualization - Open BW Services
BW
Op
en
Serv
ices:
Data
Mo
del,
OL
AP
, A
uth
ori
zati
on
, D
ata
Ag
ing
BW Virtual Data Mart Layer
Architected Data Marts
Business Transformations
EDW Propagation
Layer
EDW Transformations
Externally managed BW managed
Open Operational Data Store Layer
Agile
DMs/
BW
Work
space
Cen
tral B
I- P
rom
ote
To
Pro
du
cti
on
Ag
ile B
I -
cen
tral/ d
ep
art
men
tal
LS
A+
+ fo
r BW
on
HA
NA
B
I on S
tream
lined
ED
W ,
Opera
tional B
I, Ag
ile B
I
Co
rpo
rate
Me
mo
ry
refe
ren
ce
BW Queries
EPM , BO BI, Apps
Immediate Querying –
no staging to EDW
On any data
Incremental integration with
EDW
© 2012 SAP AG. All rights reserved. 40
LSA++ Open ODS Layer Services - Operational Data Services, EDW Services & Integration Services
The Open Operational Data Store Layer is the LSA++ Inbound Layer and as such the home of
field-level data hosting data either delivered directly to HANA (externally managed) or delivered
under control of BW (BW managed)
Core BW Services for Open ODS Layer data are:
BW Integration Services
– Consume HANA Modeler schemas in BW and vice versa
– Transfer HANA Modeler managed data into BW managed area and vice versa
BW Operational Data Services
– Real time replication into BW
– Immediate querying on any delivered data – no staging into EDW necessary (Operational BI)
– Data Modeling
BW EDW Services
– Open ODS Layer as source for persistent EDW providers
– Open ODS Layer Provider as virtual part of the EDW (if feasible from EDW standpoint)
© 2012 SAP AG. All rights reserved. 41
business documents master data
Open Operational Data Store Layer Persistent Provider Data Models: Inherited Source Models at Field-Level
Extractor Models:
Fields -DataSources
Source Data models
Fields-3NF, Tables, Views
Open ODS Layer
Inherited Source Models:
Fields- DataSources, tables
EDW Layers Model
EDW actively modeled-
InfoObjects - InfoProvider
Data Marts
actively modeled- InfoObjects,
fields
Generic Extractors,
Replication:
Fields-Source Data Models
© 2012 SAP AG. All rights reserved. 42
Open Operational Data Store Layer Any Data - Externally and BW Managed Data
Open ODS Layer services for data delivered under control of BW & modeled with BW (BW
managed) and for data directly delivered to HANA tables & modeled with the HANA Modeler
(externally managed)
HANA modeler schema –
externally managed HANA BW managed schema
HANA
Models
© 2012 SAP AG. All rights reserved. 43
Open Operational Data Store Layer BW Integration Services for Externally and BW Managed Data
HANA modeler schema –
externally managed HANA BW managed schema
HANA
Models
BW Integration Services for data delivered directly to HANA or to BW
Consume HANA Modeler schemas in BW and vice versa
Transfer HANA Modeler managed data into BW managed area and vice versa
© 2012 SAP AG. All rights reserved. 44
Open Operational Data Store Layer BW Operational Data Services – Real time Replication into BW
SA
P B
W
Extra
cto
r
SL
T
Rep
licatio
n
Replicating
DB calls
Extracting
record
images
Op
en
OD
S L
aye
r
Exte
rnally
BW
ma
naged
(SA
P) S
ou
rce
HANA
Table
BW Inbound
© 2012 SAP AG. All rights reserved. 45
Open Operational Data Store Layer
BW Operational Data Services – Immediate Querying
BW Virtual Data Mart Layer
Architected Data Marts
EDW Layers
Open Operational
DataStore
BW Queries
Replication/ Extraction
Immediate Querying
Immediate querying on delivered data (Operational BI) - no staging into EDW Layers
required
Data Modeling on Open ODS Layer field-level Provider
© 2012 SAP AG. All rights reserved. 46
Open Operational Data Store Layer
BW EDW Services - Open ODS Layer as Source
BW Virtual Data Mart Layer
Architected Data Marts
Open Operational
DataStore
BW Queries
Replication/ Extraction
Integrate into EDW Model
Delta transfer/ transformation
Open ODS Layer Provider as source for persistent EDW providers - consistency
management (delta), transfer (staging) and transformation services for EDW
EDW Layers
© 2012 SAP AG. All rights reserved. 47
BW Virtual Data Mart Layer
Open Operational Data Store Layer
BW EDW Services - Open ODS Layer as virtual Part of EDW
Open
Operational
DataStore
BW Queries
Replication/ Extraction
Open ODS Layer Provider as virtual part of the EDW (if feasible from EDW standpoint) -
reduced redundancy, increased responsiveness, incremental EDW
EDW Layers Master data
Cloud:
InfoObjects
Virtual (EDW)
Provider
‘Fact’ table
© 2012 SAP AG. All rights reserved. 48
LSA++ Open ODS Value Scenarios & BW Services
Holistic picture of
• Externally, HANA Modeler managed data and BW managed data
• Operational BI and EDW based standard BI
BW Integration Services for Open ODS Layer
• Scalable Integration of HANA Models into BW (and vice versa)
• Modeling, Query & OLAP services, EDW master data, Authorizations for HANA Models
BW Operational Data Services for Open ODS Layer
• Real Time Data Replication into BW
• Extraction or Replication into BW ?
• New BW Open ODS Layer Provider
• Immediate querying on loaded data – no staging to EDW
BW EDW Services for Open ODS Layer
• Managing transfer of data to persistent EDW Providers
• Incremental build of EDW (from virtual to staged scenarios)
• Real time master data in EDW
© 2012 SAP AG. All rights reserved. 49
The Need for a holistic Picture on Operational BI Integration of Source Level/ Operational Data ?
BW HANA instance HANA
Application
instance BW
accelerator
SAP
Application Custom
Model
HANA
sidecar
instance
SAP
Application BI on EDW
Operational
BI
„Having data is a waste of time when you can't agree on an interpretation‟
There is a need for a holistic picture on Source Level/ Operational Data to avoid
uncontrolled redundancy and island-like BI
Holistic with respect to the operational data itself and with respect to the EDW
ERP2 ERP1
© 2012 SAP AG. All rights reserved. 50
LSA++ Open Operational Data Store Layer as Parenthesis
The target of the Open ODS Layer is to provide the services and technology
gaining a holistic picture on data for Operational BI
SAP note 1661202: most up to date list of supported scenarios (e.g. BW and Accelerators)
that may run on the same HANA instance
BW HANA instance HANA
Application
instance BW
accelerator
SAP
Application Custom
Model
HANA
sidecar
instance
SAP
Application
ERP2 ERP1
Open Operational Data Store Layer
© 2012 SAP AG. All rights reserved. 51
LSA++ Open ODS Layer - The Holistic Picture Get the Best out of both Worlds
BW managed & modeled data
Market
(Enterprise) DataWarehouse
Layered Scalable Architecture (++)
Model-driven, Governance, Security, …
Usage
>24,000 active installations
> 16,000 customers
Externally managed data - HANA Modeler
Market
Data Mart
Flexibility, Performance
Native, SQL, tables/views
Usage
HPAs, Accelerators (COPA, Pipeline, …)
Customer-build apps & scenarios
BW-HANA Apps (POS DM, DSiM, …)
Data Services bulk loads
© 2012 SAP AG. All rights reserved. 52
LSA++ Open ODS Value Scenarios & BW Services
Holistic picture of
• Externally, HANA Modeler managed data and BW managed data
• Operational BI and EDW based standard BI
BW Integration Services for Open ODS Layer
• Scalable Integration of HANA Models into BW (and vice versa)
• Modeling, Query & OLAP services, EDW master data, Authorizations for HANA Models
BW Operational Data Services for Open ODS Layer
• Real Time Data Replication into BW
• Extraction or Replication into BW ?
• New BW Open ODS Layer Provider
• Immediate querying on loaded data – no staging to EDW
BW EDW Services for Open ODS Layer
• Managing transfer of data to persistent EDW Providers
• Incremental build of EDW (from virtual to staged scenarios)
• Real time master data in EDW
© 2012 SAP AG. All rights reserved. 53
BW Integration Services for HANA Modeler managed Schema/ Data & vice versa
HANA models in BW
• Consume HANA models – treat
them as InfoProvider
BW models in HANA Modeler
• Provide InfoProvider views **
HANA schema data into BW
• Transfer data into EDW * BW data in HANA Modeler tables
• Transfer data *
(*SP08)
(**Q4 2012)
BW Services for HANA Modeler managed schemas & data
© 2012 SAP AG. All rights reserved. 54
BW Integration Services for LSA++ Open ODS Layer Integration of HANA Schemas – Treat HANA Schema as InfoProvider
HANA Modeler
any schema
Open Operational Data Store Layer
HANA Views
EDW Layer
DTP*
BW Virtual/
Transient Provider
on HANA Models
Composite / MultiProvider
Architected Data Marts
BW Query, OLAP & Authorization Services
Externally
Managed
HANA schemas as Transient or
Virtual InfoProvider
* DTP with SP8
• SAP BO DS
• SLT - replication
© 2012 SAP AG. All rights reserved. 55
Different Levels of Model-Integration of Field-level Data Why?
you have the InfoObjects but do not want to stage
(now) the data to the EDW
E.g. Operational (real time) BI (Virtual Provider)
Open ODS Layer Provider as virtual part of EDW (Virtual
Provider)
you do not have all InfoObjects
InfoObjects available but not for all fields (Virtual Provider
or Transient Provider)
you do not want to model InfoObjects
InfoObjects available but no knowledge about source
fields (e.g. 3rd party / legacy load) (Transient Provider)
you do not have InfoObjects
No EDW model available (Transient Provider)
you do not know the InfoObjects
E.g. Agile Scenarios (Transient Provider)
HANA
View/
Table
Virtual
Provider
Transient
Provider
Open ODS Layer-
Source Models:
Fields
Transient Model:
Transient InfoObjects
derived from Fields
EDW -
EDW Model:
InfoObjects Transient Model:
Transient InfoObjects
Partly assigned
InfoObjects
*As of now Transient Providers only used in Agile Data Marts
© 2012 SAP AG. All rights reserved. 56
BW Integration Services–Treat HANA Model as InfoProvider Transient and Virtual Provider on HANA Model
Open ODS Layer-
Source Models: Fields
Transient Model:
Transient InfoObjects
derived from Fields use Field
properties
may use
InfoObjects
EDW
Provider
*As of now Transient Providers only used in Agile Data Marts
Virtual
Provider
HANA
View/Table
Transient*
Provider
Transient Model:
Transient InfoObjects
Partly assigned InfoObjects
EDW -
EDW Model:
InfoObjects
Different Level of Integration of Field-level Data in BW
© 2012 SAP AG. All rights reserved. 57
Different levels of Integration of Field-level Data Virtual Provider on HANA Model
Virtual Provider based on a HANA model: new type of Virtual Provider available with BW
on HANA
• Modeled like any other Virtual Provider
• All services for InfoProviders and InfoObjects: Modeling (MultiProvider, Composite Provider), Query &
OLAP, authorization services
• Complete InfoObject master data services (hierarchies, navigational attributes, authorizations..) for
HANA models - joining all InfoObject master data tables to the HANA model
© 2012 SAP AG. All rights reserved. 58
Different levels of Integration of Field-level Data Transient Provider & Transient InfoObjects on HANA Model
Just publish Hana model in RSDD_LTIP and the Transient Provider is available for querying
Transient InfoObjects:
Maintain Reference InfoObjects - optional
© 2012 SAP AG. All rights reserved. 59
Different levels of Integration of Field-level Data Transient Provider based on HANA Model
Transient Provider:
Transient means the BW InfoProvider metadata is generated out of the metadata of the source at query
runtime : Transient Provider & Transient InfoObjects
Transient Providers can be used similar to other BW InfoProviders for reporting
Directly (MDX and BICS capable) or
Creating BEx Queries on top the complete set of Analytical Functions (Restricted / Calculated key
figures, Exceptions, e.a.) is available
Transient Provider fields may reference to a “real” InfoObject meaning
Inheriting BW InfoObject master data services (like description, texts, display properties, display
attributes and hierarchies). i.e. you can create a BEx Query on pure HANA data and model, but use a
BW hierarchy and the BW hierarchy processing
Inheriting InfoObject authorizations
© 2012 SAP AG. All rights reserved. 60
BW Services for LSA++ Open ODS Layer BW Integration Services - Summery
Consumption of HANA models in BW – Treat HANA models as BW InfoProvider
– Transient Provider generated on a HANA model
– Virtual Provider defined on a HANA model
Consumption BW models (InfoProvider) in HANA Modeler - Treat BW InfoProvider as HANA view
– Make BW Models available in HANA Modeler - publish InfoProvider views for usage in HANA Modeler**
Transfer of HANA schema data into BW* (-> BW EDW Services)
Transfer of BW data into HANA Modeler managed tables*(-> BW Operational Data Services)
(* SP8/ **Q4 2012)
© 2012 SAP AG. All rights reserved. 61
LSA++ Open ODS Value Scenarios & BW Services
Holistic picture of
• Externally, HANA Modeler managed data and BW managed data
• Operational BI and EDW based standard BI
BW Integration Services for Open ODS Layer
• Scalable Integration of HANA Models into BW (and vice versa)
• Modeling, Query & OLAP services, EDW master data, Authorizations for HANA Models
BW Operational Data Services for Open ODS Layer
• Real Time Data Replication into BW
• Extraction or Replication into BW ?
• New BW Open ODS Layer Provider
• Immediate querying on loaded data – no staging to EDW
BW EDW Services for Open ODS Layer
• Managing transfer of data to persistent EDW Providers
• Incremental build of EDW (from virtual to staged scenarios)
• Real time master data in EDW
© 2012 SAP AG. All rights reserved. 62
Open ODS Layer Data Provisioning – Extractors or SLT Replication ?
Answering the question ‘Shall I replicate or extract the data ?’ seems to be simple:
Replication is assumed being ‘cheaper’ than extraction and all that at real time
Answering this question is not that straight forward if we look to the complete picture from
business solution perspective:
1. BI solution & data freshness - Operational BI solutions may ask for real time and/ or right time
and/ or stable snapshots (scheduled, on request) and
2. BI solution & consistency– BI on an EDW what mean delivered data become
• a source for persistent EDW Layers (Open ODS Layer as Acquisition Layer) or
• a virtual part of the EDW and
3. BI solution and reproducibility, availability …
4. BI solution and the contribution of the delivered data content to the desired solution, i.e. to the
Data Marts regardless whether virtual or persistent ones
* BW 730 SP8
© 2012 SAP AG. All rights reserved. 63
SAP HANA system SAP LT Replication Server SAP source system
LT Replication Concept: Trigger-Based Approach Architecture and key building blocks (for SAP Sources)
Efficient initialization of data
replication based on DB trigger
and delta logging concept
(as with NearZero downtime approach)
Flexible and reliable replication process, incl.
data migration
(as used for TDMS and SAP LT)
Fast data replication via DB connect
LT replication functionality is fully
integrated with HANA Modeler UI
Application table Logging table
DB trigger
Read module Structure mapping &
Transformation
Application table
Write module
RFC
Connection
DB
Connection
© 2012 SAP AG. All rights reserved. 64
Real-time Data Replication into SAP BW Data Replication to SAP BW using SAP LT Replication Server
Replicating Data of any SAP System (or non-SAP) into SAP BW
Enabling real-time data supply into SAP BW (PSA) via WebService DataSource
Real-Time data processing from PSA via SAP BW Real-time Data Acquisition (RDA)
– into a DataStore Object (DSO) or master data tables (MD)
– New Operational DSO (planned 2013)
As of today SLT replication into BW on „How to‟ paper level (on request)
Full imbedding in SLT of replication into BW planned Jan/ 2013
LT - Server
Structure
mapping &
Transformation
Write module
SAP NetWeaver ECC
Or non_SAP
AnyDB
Application table
Logging table DB trigger
Read module
RFC-BAPI
SAP NetWeaver BW
SAP HANA
WebService
DataSource / PSA
RDA
Daemon
MD DSO
© 2012 SAP AG. All rights reserved. 65
Open ODS Layer BW Extractors and SLT Replication- Overview
SA
P B
W
Extra
cto
r
SL
T
Rep
licatio
n
Replicating
DB calls
Extracting
record
images
Op
en
OD
S L
ayer
Ex
tern
ally
BW
ma
na
ge
d
* Planned 2013 ** if no BW in place
SA
P S
ou
rce
HANA
Table
PSA
SAP
BO DS**
DB calls
DB calls
RFC calls
RFC calls
Operational
DSO*
© 2012 SAP AG. All rights reserved. 66
SLT Data Replication to HANA or BW Delivering Record as Insert-Images or DB-Calls
SL
T
Rep
licatio
n
DOC CST WGHT DB
CALL
4711 1 400 INS
4711 1 500 UPD
4711 DEL
Source-Table DB calls
insert
Record Images:
Op
en
OD
S L
ayer
HANA
Table
PSA
DB calls / records:
INSERT
UPDATE
DELETE
Operational
DSO*
* Operational DSO planned 2013
© 2012 SAP AG. All rights reserved. 67
SLT Data Replication to HANA or BW Differences between Insert-Image and direct DB-Call Replication
SL
T
Rep
licatio
n
DOC CST WGHT DB
CALL
4711 1 400 INS
4711 1 500 UPD
4711 DEL
Source-Table DB calls:
Table content after DB calls: DOC CST WGHT DB
CALL
DOC CST WGHT
No record
No record
HANA table:
Real Time BW PSA:
Open ODS Layer
Snapshots ?
Delta ?
BW generic delta
Real time ?
© 2012 SAP AG. All rights reserved. 68
Open ODS Layer Replication & Extraction Data into BW vs. directly into HANA DB
BW is a DWH (application)
• A DWH & BW principle is keeping history of delivered data and leaving the decision what
shall happen to the received records to the BW owner.
− i.e. the BW Inbound Provider (PSA, Operational DSO*) never delete records - all records are
inserted with an image classification (insert, before, after, reverse, delete … image)
• In addition each record gets a unique stamp (request, package, rec-no), which allows a
generic delta for further data processing (staging or immediate querying)
HANA is first of all a data base
• Any delivery of data to a HANA inbound table means a direct data base operation
• All necessary or wanted record handling must be done either by the replicator or the
extraction tool – if possible at all
− Content enrichment / Content transformations
− Providing a delta criteria for further processing (any kind of snapshot, EDW)
− Managing delete HANA calls
* Planned 2013
© 2012 SAP AG. All rights reserved. 69
Open ODS Layer- Replicating Data into BW BW Multi-Service Offering on Top of Real Time PSA
SL
T
Rep
licatio
n
Real time
BW PSA: Real time
Operational BI
HANA DB DSO/
Operational DSO*
Operational DSO*
* HANA DB DSO BW 730 SP8/ Operational DSO planned 2013
Real time on demand
Operational BI
Scheduled snapshot
Operational BI
Real time
EDW based BI std DSO, InfoObject
Consistent Images
EDW Propagator std DSO
All Images
EDW Corporate Mem WO-DSO
Open ODS Layer EDW Layers
© 2012 SAP AG. All rights reserved. 70
Open ODS Layer Data Provisioning – Replication into BW
As BW customer the question ‘Shall I replicate or extract the data ?’ can be answered like
• In case I decide for replication, I replicate into BW (full embedding into SLT 01/2013)
• BW replication & BW extraction inbound data offer the same services
− Immediate querying (Near real time: Via RDA & DSO, InfoObject and planned Operational DSO*)
− Generic delta for further data processing
− Transformations
• Thus for BW customer decision between replication & extraction is reduced to
considering
− the delivered data content
− desired data freshness by business solution
© 2012 SAP AG. All rights reserved. 71
Open ODS Layer- BW Extractors or SLT Replication What is delivered? Delivered Content & Business Logic
VBAP T001
2L
IS_11_V
_S
CL
Extra
cto
r S
LT
Rep
licatio
n
VBUP VBEP
VBAK VBKD
targ
et
targ
et
Replication of source tables
•target needs to know
− table associations
− table content logic
• latency: real time delivery
• delta: 1:1 replication of DB-operations
SAP ∆ Queue Business View Extractors
•delivered data are data mart ready
• inbuilt associations & content logic
• latency: extraction cycle
• delta (SAP ∆ queue, full)
ABCD
0A
BC
D_
AT
TR
Extra
cto
r
∆
∆
full
targ
et
SAP Generic Table/ View Extractors
• source table/ view level
• latency: extraction cycle
• delta (complete ? / full - lost deletes)
• often only full loads
∆
full
© 2012 SAP AG. All rights reserved. 72
Open ODS Layer- BW Extractors or SLT Replication Delivered Content as Decision Criteria
• SAP Generic Table/ View Extractors are candidates for replacement as they do not offer from
delivered content perspective any added value compared to replication and have technical
„deficits‟
• Generic full extractors
− Cannot catch deletes what makes EDW processing cumbersome
− Will be processed even if there are no changes (e.g. master data)
• Generic delta extractors - need of a safety interval what makes the business unhappy
(latency of data)
The trigger based SLT replication enables a delta mode for all tables (as it is a technical
approach, no delta capable field is required)
• SAP Extractors working with the SAP ∆ queue often address multiple tables joining them with
complex logic - they cannot easily be replaced by replication as the complex logic has to be
built on the replicated HANA tables / BW Provider
© 2012 SAP AG. All rights reserved. 73
LSA++ Open ODS Value Scenarios & BW Services
Holistic picture of
• Externally, HANA Modeler managed data and BW managed data
• Operational BI and EDW based standard BI
BW Integration Services for Open ODS Layer
• Scalable Integration of HANA Models into BW (and vice versa)
• Modeling, Query & OLAP services, EDW master data, Authorizations for HANA Models
BW Operational Data Services for Open ODS Layer
• Real Time Data Replication into BW
• Extraction or Replication into BW ?
• New BW Open ODS Layer Provider
• Immediate querying on loaded data – no staging to EDW
BW EDW Services for Open ODS Layer
• Managing transfer of data to persistent EDW Providers
• Incremental build of EDW (from virtual to staged scenarios)
• Real time master data in EDW
© 2012 SAP AG. All rights reserved. 74
LSA++ Open ODS Layer BW Operational Data Services – New BW Provider for Operational BI
New field-level BW Provider
HANA DB DSO*
Operational DSO*
providing
– immediate querying - no staging into EDW required and
– data transformation services
Transfer of BW data into externally HANA Modeler managed tables
– Replicating and Transforming BW data into HANA tables
BW Open Hub Services for transformation & consistent transfer into HANA tables or HANA DB
DSO*
(* HANA DB DSO SP8/ Operational DSO planned for 2013)
© 2012 SAP AG. All rights reserved. 75
EDW Layers
Composite / MultiProvider
Architected Data Marts
BW Query, OLAP & Authorization Services
LSA++ Open ODS Layer (BW 730 SP8)
BW Managed Inbound Data for EDW & Operational BI
Open Operational Data Store Layer
DTP
BW managed
BW enables Operational BI on
BW managed inbound data
via an HANA DB DSO
linked to the PSA & generated
HANA analytic views (*SP8)
PSA
Virtual/ Transient
Provider on HANA
Models
Real time
DTP/RDA
InfoObject/
Std DSO
HANA Views generated
HANA DB DSO
DTPs
• SAPI ETL
• SAP BO DS
• SLT replication
© 2012 SAP AG. All rights reserved. 76
BW DataSource Services
HANA allows immediate performant querying on loaded data without any specific modeling (e.g.
star schema) or tuning efforts (e.g. aggregates). This is a (necessary) prerequisite for
Operational BI/ real time BI.
In order to leverage this HANA capabilities BW on HANA provides (will provide) new Operational
/ real time BI Services for data at the earliest possible point in time.
The earliest point in time where BW has meta-knowledge about data is BW DataSource.
BW DataSource Services
Open Hub Service *
• Delivery Services
HANA DB DSO/ table
• Transformation Services
Operational DSO **
• Operational Data Services
• EDW Services
• Consistency Services
• Transformation Services
• Real time data Services
PSA Service
• EDW Services
• Consistency Services
• Real time data Services
(* SP8/ ** planned for 2013)
© 2012 SAP AG. All rights reserved. 77
SLT replication: Real Time InfoPackage
BW managed
Open Operational Data Store Layer
BW Operational Data Services Querying on BW Inbound Data New HANA DB DSO (BW 730 SP8)
BW
Data
So
urc
e
PSA
SAP ETL: InfoPackage
DataSource Service -
PSA:
• Consistency services
• Staging services
Externally managed
BW Virtual/ Transient
Provider on HANA
Models
BW Query, OLAP &
Authorization Services
DataSource Service -
Open Hub:
• Delivery Services
• Transformation services
DTPs
HANA DB DSO
HANA Table
Analytic views generated
© 2012 SAP AG. All rights reserved. 78
HA
NA
ta
ble
/
HA
NA
DB
DS
O
BW
Data
So
urc
e
BW Operational Data Services - BW Managed Provisioning, Staging & Query Services - New Operational DSO (*planned 2013)
Operational DSO*
SAP ETL: • DTP on ODQ • Real Time DTP on ODQ
DataSource Service -
Operational DSO:
• Operational Data Services
• EDW Services
• Consistency Services
• Transformation Services
• Real time data Services
BW Query, OLAP &
Authorization Services
PSA
SAP ETL: InfoPackage
DataSource Service -
PSA:
• EDW Services
• Consistency Services
• Real time data Services
DataSource Service –
Open Hub:
• Delivery Services
• Transformation Services
SLT replication: Real Time InfoPackage
Open
Operational Data Store
BW managed Layer
RDA
DTP
© 2012 SAP AG. All rights reserved. 79
Open Hub Service HANA DB DSO as DataSource Service
© 2012 SAP AG. All rights reserved. 80
HANA Footprint of HANA DB DSO
© 2012 SAP AG. All rights reserved. 81
HANA DB DSO as Open Hub Service Target Set up & Usage
• Field-based DSO with Activation-Queue and Active Table
• Works like a „normal‟ DSO
• Field list generated as proposal from DataSource (additional fields possible)
• Filled from PSA by Open Hub Service, which is generated as a DataSource Service providing
HANA DB DSO name and HANA schema
• DTP (not yet RDA) generated
• Transformations between PSA and HANA DB DSO allow enrichment
• Analytic view generated in defined HANA Schema
Usage:
• Consistent, queryable replication (with transformation) of BW PSA data to HANA Modeler
• Enable immediate BW querying and Services to source-level data – no staging into EDW context
necessary – Open ODS Layer HANA DB DSO as virtual part of EDW (if feasible)
© 2012 SAP AG. All rights reserved. 82
LSA++ Open ODS Value Scenarios & BW Services
Holistic picture of
• Externally, HANA Modeler managed data and BW managed data
• Operational BI and EDW based standard BI
BW Integration Services for Open ODS Layer
• Scalable Integration of HANA Models into BW (and vice versa)
• Modeling, Query & OLAP services, EDW master data, Authorizations for HANA Models
BW Operational Data Services for Open ODS Layer
• Real Time Data Replication into BW
• Extraction or Replication into BW ?
• New BW Open ODS Layer Provider
• Immediate querying on loaded data – no staging to EDW
BW EDW Services for Open ODS Layer
• Managing transfer of data to persistent EDW Providers
• Incremental build of EDW (from virtual to staged scenarios)
• Real time master data in EDW
© 2012 SAP AG. All rights reserved. 83
BW Services for LSA++ Open ODS Layer BW EDW Services – Open ODS Layer as Source
Open ODS Layer Provider as source for persistent EDW Provider
– BW Open ODS Provider (PSA & Operational DSO**) as source for EDW
oConsistent generic delta for data transfer
oData Transformation Services
oMapping Services for source-level fields to EDW data model (InfoObjects)
– Externally managed data (HANA tables/ views) as source for EDW
o Transfer and Transformation of HANA schema data into BW: BW Data Transfer and
Transformation Services (remote BW DTPs*)
o Providing a valid delta criteria is the task of the HANA schema data
(* SP8/ **Operational DSO planned for 2013)
© 2012 SAP AG. All rights reserved. 84
BW Services for LSA++ Open ODS Layer BW EDW Services – HANA Schema as Source
HANA Modeler
any schema
Open Operational Data Store
HANA Views
EDW Layer
DTP*
Architected Data Marts
Externally
Managed
LSA++ treats HANA schemas as
Open ODS Layer Provider that are
externally managed (modeling and
load)
* DTP with SP8 • SAP BO DS
• SLT -replication
© 2012 SAP AG. All rights reserved. 85
EDW Layers
Architected Data Marts
BW Services for LSA++ Open ODS Layer BW EDW Services – BW Open ODS Layer Provider as Source
Open Operational Data Store Layer
DTP
BW managed
Consistent, reliable, reproducible
Staging from PSA or Operational
DSO* to EDW
Real time
DTP/RDA
PSA/
Operational DSO*
InfoObject/
Std DSO/
HybridProvider
• SAPI ETL
• SAP BO DS
• SLT replication (* planned for 2013)
© 2012 SAP AG. All rights reserved. 86
LSA++ for BW on HANA Value Scenario – Streamlined EDW SLT Real-Time Master Data Replication into BW
Master Data (InfoObjects) are the heart of the EDW
Loading master data
– is cumbersome because of the number of entities
– means for most of the entities full loads with slowly changing dimensions most master data did not change
since the last load most records are loaded unnecessarily
– is challenging with global BWs (right time)
– was a cumbersome with BW on RDBMS (realignment of aggregates – change run)
With BW on HANA updating InfoObject master data tables means so to speak a NOOP
Full master data extraction & loads from single source tables can be replaced by real time
replication via SLT into BW and transfer to InfoObject tables via ‚real time„ DTP (RDA)
Extractions for core entities (e.g. material) are often joins on several source tables. In this case
the replacement must be carefully examined.
© 2012 SAP AG. All rights reserved. 87
LSA++ for BW on HANA Value Scenario - Streamlined EDW SLT Real-Time Master Data Replication into BW
Value of real time master data:
no more synchronization issues with transaction data (simplified staging)
less administration and operations overhead
simplified projects on BW EDW
overall increased flexibility
Externally managed BW managed
Open Operational DataStore
SAPI ETL
PSA PSA
SLT – real time replication
EDW Master data
InfoObjects
Real time
DTP (RDA)
normal
DTP
© 2012 SAP AG. All rights reserved. 88
LSA++ Open ODS Value Scenarios & BW Services
Holistic picture of
• Externally, HANA Modeler managed data and BW managed data
• Operational BI and EDW based standard BI
BW Integration Services for Open ODS Layer
• Scalable Integration of HANA Models into BW (and vice versa)
• Modeling, Query & OLAP services, EDW master data, Authorizations for HANA Models
BW Operational Data Services for Open ODS Layer
• Real Time Data Replication into BW
• Extraction or Replication into BW ?
• New BW Open ODS Layer Provider
• Immediate querying on loaded data – no staging to EDW
BW EDW Services for Open ODS Layer
• Managing transfer of data to persistent EDW Providers
• Incremental build of EDW (from virtual to staged scenarios)
• Real time master data in EDW
© 2012 SAP AG. All rights reserved. 89
BW Services for LSA++ Open ODS Layer BW EDW Services – Virtual Provider as Part of EDW
Virtual integration of Open ODS Layer Provider with EDW
If an Open ODS Layer Provider fulfills the consistency criteria of the EDW (customer defined e.g.
integrity, reproducibility…) it may well serve as virtual part of the EDW Propagation Layer
– Using the Virtual Provider service on HANA models (view on HANA tables or HANA DB DSOs *)
– Using Operational DSOs*
hence reduce redundancy (TCO) and increase responsiveness.
A later staging of the Open ODS Layer Provider to a persistent EDW Propagation Provider is possible
if it offers a valid delta – (for BW managed Provider this is always the case)
(* HANA DB DSO SP8/ Operational DSO planned for 2013)
© 2012 SAP AG. All rights reserved. 90
SAP ERP – leading system
as Reference
Virtual Provider as Part of EDW SAP ERP as BW EDW Reference
EDW
Source
Systems
BW EDW – the Golden Image
Reference
Customers invested a lot in SAP ECC resulting in highly integrated processes and master data =>
It is straightforward making SAP ERP(s) their reference system:
The data loaded from this SAP ERP to BW are by definition in a good shape i.e. we assume that
normally no integration transformations are necessary.
All other data have to be transformed with respect to this reference to integrate and harmonize with
the (SAP ERP) reference.
Harmonize – Integrate - Transform
© 2012 SAP AG. All rights reserved. 91
LSA++ for BW on HANA Value Scenario Incremental build of EDW - from virtual to staged scenarios
Providing Immediate Value of Loaded Data (1st Step)
BW on HANA is targeting to provide immediate value i.e. Local/ operational BI without
obstracting EDW targets allowing to introduce incrementally an EDW data model (InfoObjects)
and additional LSA++ Layers when it shows up value.
Incremental definition
of Data Model &
Architecture
© 2012 SAP AG. All rights reserved. 92
LSA++ Open Operational Data Store Layer - Summary Flexibility – Immediate Value
The new Open Operational Data Store is the LSA++ Inbound Layer.
The target of the Open ODS Layer is to provide a common framework for BI source level data.
Open ODS integrates data delivered directly to BW (BW managed) and data delivered to native
HANA models (externally managed)
The Open ODS data inherit the field-level (OLTP) data model from the source application.
The Open ODS Layer promotes scalable BW Services like OlAP services, master data services ,
authorization services...
The Open ODS is a hybrid, offering
– Acquisition Layer functionality
serving as source-layer for the EDW Layer
– Immediate querying** on data
o SAP extraction (SAPI)
o Data Services for non-SAP sources
o Real time replication via SLT
(*on the same HANA instance) (** HANA DB DSO SP8/ Operational DSO planned for 2013
LSA++ Virtual Data Mart Layer
© 2012 SAP AG. All rights reserved. 94
BW Virtual Data Mart Layer
MultiProvider
LSA++ Holistic Architecture Virtual Data Mart Layer - Overview
Architected Data Marts
EDW Layers
Open Operational
DataStore
Agile
DMs/
BW
Work
space
Cen
tral
BI
dep
art
men
tal
BI
LS
A+
+ fo
r BW
on
HA
NA
Virtu
al D
ata
Marts
BW Queries
EPM , BO BI, Apps
Virtual/
Transient
Provider
Analytic
Index ∞ Table/
HANA DB DSO
PSA
HANA Model
Composite Provider
refe
ren
ce
Composite Provider
(** HANA DB DSO SP8/ Operational DSO planned for 2013)
MultiProvider
Operational
DSO
© 2012 SAP AG. All rights reserved. 95
LSA++ Holistic Framework Virtual Data Marts: Virtual Wrapping & Combining Data
LSA++ promotes flexible virtual wrapping of agile / operational data and virtual combinations (with
core EDW context data) using BW on HANA virtualization features (Virtual Data Marts: Virtual
Provider, Transient Provider, Composite Provider)
Virtual Data Marts will increase overall LSA++ framework flexibility and manageability
EDW context data
Operational
Extension
operational, real time
context data
Flexible Consistent
EDW Core Agile Extension
Agile/ ad hoc
context data
LS
A+
+ fo
r BW
on
HA
NA
Virtu
al W
rap
pin
g &
Co
mb
ing
Da
ta
Virtual Wrap Virtual Wrap
Virtual Combination
Query
Vir
tual
Data
Ma
rts
Virtual Wrap
© 2012 SAP AG. All rights reserved. 96
LSA++ for BW on HANA Value Scenarios Virtual Data Marts on Open ODS and/ or EDW/ ADM
With LSA++ framework Virtual Data Marts come into focus. Beside the various technical types of
InfoProvider (VirtualProvider, TransientProvider, CompositeProvider, MultiProvider) we see a wide
variety of scenarios addressed by Virtual Data Marts.
Reporting on
Open ODS data
Mixed reporting on
Open ODS &
EDW data
Reporting on
EDW data
Virtual Data Marts flexibility
time-to-market
Persistent EDW consistency – standardized
integration – standardized
robustness, availability – standardized
reproducibility – standardized
latency, freshness - standardized
Persistent Open ODS consistency - source dependent
integration - source dependent
robustness, availability - source dep.
reproducibility - source dependent
latency, freshness – load dependent
© 2012 SAP AG. All rights reserved. 97
Criteria Structuring LSA++ Virtual Data Mart Layer
Virtual Data Marts Context:
Virtual Data Mart wrapping a HANA view versus Virtual Data Marts resulting from joining
(CompositeProvider) other Virtual Data Marts
Technical provider type (Virtual, Transient, Multi, Composite)
Addressed layer
Content area of addressed data
Different level consistency aspects joining data (e.g. Inner versus left outer join)
Ownership: reach (for whom e.g. Global, regional, market,..)
......
LSA++ suggests a proper structuring (layering) and naming of Virtual Data Marts
deployed via Promote-To-Production reflecting the context of Virtual Data Marts not
loosing control
© 2012 SAP AG. All rights reserved. 98
LSA++ Virtual Data Mart Layer Structuring Virtual Wrapping & Composition Layer - Naming
Virtual Data Mart wrapping a HANA view versus Virtual Data Marts resulting from joining
(CompositeProvider) other Virtual Data Marts
Please remember the restrictions of Basis & Joined Virtual Data Marts !
Source-level HANA view
Persistent EDW Core InfoProvider
Source-level HANA view
Open ODS
EDW Core
(Virtual) Wrap
Layer
(Virtual )
Composition
Layer
Vir
tual D
ata
Ma
rt
La
yer
I
W Transient
Provider
Virtual
Provider
Multi
Provider
Composite
Provider
© 2012 SAP AG. All rights reserved. 99
Virtual Data Mart Criteria for Structuring – Naming Proposal
• Virtual Data Mart Layer (1 Byte)
– W – wrapped , I – joined/ union
• Technical provider type (Virtual, Transient, Multi, Composite): (1 Byte)
– V – VirtualProvider
– T – TransientProvider
– M – MultiProvider
– C - CompositeProvider
• Addressed Layer: e.g. OP (ODS & Propagator) (2 Byte)
• Content Area of addressed data (4 Byte)
– Inherited or assigned
• Different level of ‚consistency„ resulting from join (1 Byte)
– I – inner join (referential integrity)
– O – outer join (all)
– U - Union
• Ownership: reach (for whom e.g. Global, regional, market) (1 Byte)
© 2012 SAP AG. All rights reserved. 100
Summary
With BW on RDBMS we were limited but the LSA was simple.
With BW on HANA we gain more flexibility and more options covering business needs –
this on the other hand requires a new holistic LSA++ providing a framework for all different
BI-flavours and their persistent data and virtual data marts
Please remember: we are just at the beginning of a great journey
© 2012 SAP AG. All rights reserved. 101
Further Information
SAP Public Web
scn.sap.com
www.sap.com
SAP Education and Certification Opportunities
www.sap.com/education
Watch SAP TechEd Online
www.sapteched.com/online
Feedback Please complete your session evaluation for EIM203.
Thanks for attending this SAP TechEd session.
© 2012 SAP AG. All rights reserved. 103
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of
other software vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of
Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System
z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7,
POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize,
XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere,
Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe
Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri,
and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry
Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered
trademarks of Research in Motion Limited.
© 2012 SAP AG. All rights reserved.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads,
Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice,
Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,
SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects
is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc.
Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG
in Germany and other countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied,
or transmitted in any form or for any purpose without the express prior written permission of SAP AG.