LSA++ Positioning

LSA++
Layered Scalabl e Architecture for BW on HANA

Positioning, Value & LSA++ WS Content
J uergen Haupt, Architect
SAP AG
May 2012
2012 SAP AG. All rights reserved. 2
Legal disclaimer
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.
LSA++ The Holistic Picture on Structured Data for BI
LSA++ Value Areas Comparison to LSA
LSA++ Streamlined EDW & Architected Data Marts
LSA++ Open Operational Data Store Operational & Real Time BI
LSA++ Virtualization
LSA++ Agile BI
BW EDW LSA Grid
Consistent EDW Architecture Consistent BI & Reporting
BW EDW Standard LSA Layer
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-Parti tion: byte 8
Technical name
of DSO
BW Layered Scalable Architetcure - Value & Positioning
Consistent, High Availability EDW for Standardized BI
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
enabling BW managing reliably
the entire data & meta data life cycle:
Data delivery (extraction, RDA)
Data modeling (assign InfoObjects)
Data staging
Authorizations
Solution delivery (transports)
L
S
A
L
S
A
+
+

V
a
l
u
e

A
r
e
a
s
LSA++ Virtual Data Mart Layer
LSA++ for BW on HANA A Holistic Framework
LSA++ Value Areas
Data Acquisition Layer
O
p
e
r
a
t
i
o
n
a
l

D
a
t
a

S
t
o
r
e
Virtualization Layer
Reporting Layer
(Architected Data Marts)
Business Transformation
Layer
Business Transformation
Layer
Data Propagation
Layer
Harmonisation
Layer
Corporate
Memory
EDW context data
LSA
Consistent
EDW Core
Source
context data
LSA
Acquisition
Agile
context data
LSA++
Agile
Data Marts
Virtualization
LSA++
Flexible Consistent
EDW Core
LSA++
Open ODS
Layer
LSA++ Holistic Framework
Structuring Persistent Data by Data Categories
LSA++ structures data by purpose/ context with respect to BI requirements
resulting in categories of data :
LSA++ Flexibl e Consistent 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
Agil e Extension of the Core: Agile, ad hoc context data
Agile BI on all kind of data single usage
LSA++purifies the flexible consistent EDW Core offering dedicated services for
operational & agile purpose data (free the core from cholosterol)
This by itself increases overall LSA++framework flexibility and managebility
Classifying BI Requirements before Implement
BI solutions based on different LSA++ data categories have decisive
differences from IT perspective 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:
B
W

O
p
e
n

S
e
r
v
i
c
e
s
:

D
a
t
a

M
o
d
e
l
,

O
L
A
P
,

A
u
t
h
o
r
i
z
a
t
i
o
n
,

D
a
t
a

A
g
i
n
g
LSA++ for BW on HANA
Flexible Consistent Data Framework Virtually Wrapped
BI on Streamlined EDW - Operational BI Agile BI
Virtualization - Open BW Services
BW Virtual Data Mart Layer
Archi tected Data Marts Archi tected Data Marts
EDW Propagation Layer EDW Propagation Layer

EDW Transformations EDW Transformations
Externaly
managed
BW managed
Open Operational DataStore Open Operational DataStore
Business Transformations Business Transformations
Agile Agile
DMs/ DMs/
BW BW
Work Work
space space
C
e
n
t
r
a
l

B
I
-
P
r
o
m
o
t
e

T
o

P
r
o
d
u
c
t
i
o
n
A
g
i
l
e

B
I

-
c
e
n
t
r
a
l
/

d
e
p
a
r
t
m
e
n
t
a
l

L
S
A
+
+

f
o
r

B
W

o
n

H
A
N
A
B
I

o
n

S
t
r
e
a
m
l
i
n
e
d

E
D
W

,
O
p
e
r
a
t
i
o
n
a
l

B
I
,

A
g
i
l
e

B
I
BW Queries
C
o
r
p
o
r
a
t
e
C
o
r
p
o
r
a
t
e
M
e
m
o
r
y
M
e
m
o
r
y
r
e
f
e
r
e
n
c
e
Applications: EPM , BO BI, Apps
LSA++ Agile BI
LSA++ EDW & Architected Data Marts Value Scenarios
Streamlined EDW & Architected Data Marts
Streamlined Architected Data Marts thru Virtual Data Marts
Modeling persistent InfoProvider for Flexibility
Real Time Master Data for Flexibility
LSA++ Layer Structure of Flexible Consistent EDW Core
The LSA Heritage
LSA++ inherits the service definitions of LSA layer that stands for
reliability & consistency:
EDW Transformation Layer (Link)
(EDW) Corporate Memory (Persistent )
(EDW) Propagation Layer (Persistent )
Business Transformation Layer (Link)
Architected Data Mart Layer (Persistent )
These Layer define the consistent Core:
LSA++ for BW on HANA Value Scenario
Streamlined EDW - EDW Propagation Layer
LSA++ EDW Propagation Layer using HANA Optimized DSOs means
Increased flexibility 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)
Increased flexibility thru direct Querying on Propagation Layer (Streamlining
Architected Data Marts)
f
a
s
t
comprehensive
d
i
r
e
c
t
Flexible, relaxed modeling
Streamlined Architected Data Marts
LSA++ Architected Data Mart Layer using HANA Optimized InfoCubes means
Increased flexibility thru dramatic decrease of load time
Increased modeling flexibility
No multi-dimensional modeling skills needed
Relaxed volume considerations during design time (->Domains/ semantical
Partitioning)
f
a
s
t
Flexible, relaxed modeling
LSA++ Streamlined EDW
Fundamental Changes in LSA++ with respect to LSA
1. Queries on DSOs (sid-enabled) show similar performance
compared to queries on InfoCubes
2. BW Composite Provider feature allows defining Virtual Data Marts
combining LSA++ Core InfoProviders
LSA++ Streamlined EDW
EDW Propagation Layer as Query Target
In publications we can read that the EDW in general is not query-able.
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 EDW on HANA you can run queries on
Propagator Layer DSOs (side-enabled) with similar performance like
on InfoCubes
LSA++ Streamlined Architected Data Marts
Obsolete: InfoCubes as Accelerator on Business Transformation Layer DSOs
LSA++ Streamlined Architected Data Marts
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 /
or through updating (overwrite) loaded one target DataStore Object
UNION J oin in MultiProvider doesnt correspond to reporting requirements
C
Reporting Reporting
LSA
SAP NetWeaver BW
LSA++
SAP NetWeaver BW
powered by HANA
Composite
Provider
Composite Provider Considerations
BW OLAP Engine & HANA DB Things to keep in Mind
: provided by OLAP Engine

Decision Criteria on Using Composite Provider
Architected Data Marts and the BW Virtual Data Mart Layer
Goal: Streamline 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
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
Central Data
US Data
German Data
LSA++ Agile BI
B
W

O
p
e
n

S
e
r
v
i
c
e
s
:

D
a
t
a

M
o
d
e
l
,

O
L
A
P
,

A
u
t
h
o
r
i
z
a
t
i
o
n
,

D
a
t
a

A
g
i
n
g
LSA++ for BW on HANA
Flexible Consistent Data Framework Virtually Wrapped
BI on Streamlined EDW - Operational BI Agile BI
Virtualization - Open BW Services
Archi tected Data Marts Archi tected Data Marts
EDW Propagation Layer EDW Propagation Layer

EDW Transformations EDW Transformations
Externaly
managed
BW managed
Business Transformations Business Transformations
Agile Agile
DMs/ DMs/
BW BW
Work Work
space space
C
e
n
t
r
a
l

B
I
-
P
r
o
m
o
t
e

T
o

P
r
o
d
u
c
t
i
o
n
A
g
i
l
e

B
I

-
c
e
n
t
r
a
l
/

d
e
p
a
r
t
m
e
n
t
a
l

L
S
A
+
+

f
o
r

B
W

o
n

H
A
N
A
B
I

o
n

S
t
r
e
a
m
l
i
n
e
d

E
D
W

,
O
p
e
r
a
t
i
o
n
a
l

B
I
,

A
g
i
l
e

B
I
BW Queries
C
o
r
p
o
r
a
t
e
C
o
r
p
o
r
a
t
e
M
e
m
o
r
y
M
e
m
o
r
y
r
e
f
e
r
e
n
c
e
Applications: EPM , BO BI, Apps
LSA++ Open ODS Value Scenarios
Holistic picture of externally and BW managed data
Scalable Integration of externally managed native HANA data
Query & OLAP services
EDW model (master data)
Authorizations
Operational BI using BW Queries on any loaded source data
Immediate querying on loaded data no staging
Streamlined EDW releasing EDW from Operational BI scenarios
Faster time-to-market of BI scenarios
Incremental build of EDW (from virtual to staged scenarios)
Real time BI (real time replication (SLT) to HANA or to BW (& RDA))
Real time master data in EDW (SLT & RDA to InfoObjects)
Release ERP from operational reporting workload
Free EDW Core from Cholosterol
Holistic Picture of Externally and BW Managed Data
The Mixed Scenario case in BW HANA
any schema
Replication
Services
Data
Services
DXC
SAP
Extractors
Data
Services
Replication
Services
HANA
BW managed schema
HANA Model
BW
Market
(Enterprise) DataWarehouse
Layered Scalable Architecture (++)
Model-driven, Governance, Security,
Usage
>24,000 active installations
~16,000 customers
>50 BW-HANA customers
>7 live BW-HANA installations
HANA Information 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, )
BW on HANA Interoperability
Consuming HANA models Consuming BW models**
Replicating HANA schema data*
Replicating BW data*
Strategic Integration
into BW & LSA++
Tactical Integration
Into HANA applications
(*SP08)
(**Q4 2012)
LSA++ Open ODS as Parenthesis
BW HANA instance
HANA
Application
instance
EDW
accelerator
accelerator
SAP
Application
Custom
Model
HANA
sidecar
instance
HANA
sidecar
instance
Tight coupling DTP*
Querying via Virtual/ Transient Provider
& Composite Provider
Soft coupling remote HANA tables**
(querying via federation)
HANA remote
tables/ views*
HANA remote
tables/ views*
* Planned SP8
** Not available today
DTPs*
tables/ views
SAP
Application
LSA++ Open ODS Layer
Querying on Open ODS Layer
HANA Views
EDW Layer EDW Layer
Virtual / Transient
Provider on
HANA Models
Composite / MultiProvider
Archi tected Archi tected
BW Query
Externally
Managed
BW
Managed
LSA++deals with
externally and BW
managed data of Open
ODS Layer pretty much the
same when it comes to
querying:
Via creation (Virtual
Provider) or generation
(Transient Provider) of
meta data (InfoObjects,
InfoProvider) on top of a
HANA view*
Why this different options?
*BW managed planned SP8
LSA++ Virtual Data Marts and Model Richness
EDW
data model
Business View
Data Mart Model
source
data model
EDW
transform
Data Mart
transform
LSA++ EDW Core LSA++ Core Extensions
Business View
Data Mart model
source
data model
Data Mart
transform
Providing Immediate Value of Loaded Data (1st Steps)
BW on HANA is targeting to provide immediate value i.e. Local/ operational
BI without obstracting EDW targets allowing to introduce incrementally a BW
data model and the LSA when it shows value.
Incremental definition
of Data Model &
Architecture
LSA++ More Flexibility Free EDW Core from Colestherol
Open Operational Data Store
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 are not modeled using BW InfoObjects but 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
Acqusition Layer functionality like request handling serving as source-layer
for the EDW Layer
Immediate querying** on data arrived via
SAP extraction (SAPI)
Data Services for non-SAP sources
Real time replication via SLT
(*on the same HANA instance) (** BW managed Open ODS planned SP8)
LSA++ Agile BI
LSA++ Target Architecture (Planning BW730 SP8)
Virtual Data Mart Layer - Overview
Applications: EPM , BO BI ....
Open Open
Operational Operational
DataStore DataStore
c
e
n
t
r
a
l

B
I
L
S
A
+
+

f
o
r

B
W

o
n

H
A
N
A
V
i
r
t
u
a
l

D
a
t
a

M
a
r
t
s
BW Queries
HANA Model
Composite Provider
Table
r
e
f
e
r
e
n
c
e
Composite Provider
Agile DMs/
BW
Workspaces
Analytic
Index
V
i
r
t
u
a
l

P
r
o
v
i
d
e
r
O
n

H
A
N
A

M
o
d
e
l
s
d
e
p
a
r
t
m
e
n
t
a
l

B
I
EDW Layer EDW Layer
Archi tected Data Archi tected Data
Marts Marts
MultiProvider
Operational
DSO*
T
r
a
n
s
i
e
n
t

P
r
o
v
i
d
e
r
Stable Persi stent EDW Core & Virtual Extensions Overview
HANA Model
PSA
* planned SP8
Virtual Data Marts: Virtual Wrapping & Combining Data
EDW context data
Operational Operational
Extension Extension
operational,
source context
data
LSA++ LSA++
Flexible Consistent Flexible Consistent
Core Core
Agile Agile
Extension Extension
agile/
ad hoc
context data
L
S
A
+
+

f
o
r

B
W

o
n

H
A
N
A

V
i
r
t
u
a
l

W
r
a
p
p
i
n
g

&

C
o
m
b
i
n
g

D
a
t
a
Virtual Wrap Virtual Wrap
Virtual Combination Virtual Combination
Query Query
V
i
r
t
u
a
l

D
a
t
a

M
a
r
t
s
LSA++ for BW on HANA Value Scenarios
Virtual Data Marts on Open ODS and/ or EDW/ ADM
Persistent EDW
consistency standardized
integration standardized
robustness, avaiability standardized
reproducability standardized
latency, freshness - standardized
Persistent Open ODS
consistency - source dependent
integration - source dependent
robustness, avaiability - source dep.
reproducability - source dependent
latency, freshness load dependent
Reporting on
Open ODS data
Mixed reporting on
Open ODS &
EDW data
Reporting on
EDW data
Virtual Data Marts
flexibility
time-to-market
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.
LSA++ Virtual Data Mart Layer Structuring
Virtual Wrapping & Composition Layer - Naming
Source-level
HANA view
Persistent EDW
Core InfoProvider
Transient
Provider
Source-level
HANA view
Virtual
Provider
Open ODS
EDW Core
Multi
Provider
(Virtual) Wrap
Layer
Composite
Provider
(Virtual )
Composition
Layer
V
i
r
t
u
a
l

D
a
t
a

M
a
r
t
L
a
y
e
r
I
W
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 & J oined Virtual Data Marts !
LSA++ Agile BI
LSA++ Agile Extensions - Central IT Agile Data Marts
Value & Prerequisites
Rapid Prototyping
Ad hoc single time solutions
Ad hoc - temporary solutions
LSA++ Flexible Consistent Core & Extensions
Need of Organization & BI Process Adoption (BI CC)
EDW
A
g
i
l
e

D
a
t
a

M
a
r
t

L
a
y
e
r
C
e
n
t
r
a
l

A
g
i
l
e

E
x
t
e
n
s
i
o
n
B
W

W
o
r
k
s
p
a
c
e
(
L
a
y
e
r
)
D
e
p
a
r
m
e
n
t
a
l
A
g
i
l
e

E
x
t
e
n
s
i
o
n
Open Operational Data Store
Operational Extension
LSA++ LSA++
Flexible Consistent Flexible Consistent
Core Core
Architected
Data Marts
L
S
A
+
+

f
o
r

B
W

o
n

H
A
N
A

M
a
i
n

L
a
y
e
r
Enterprise BI
Operational BI
D
e
p
a
r
t
m
e
n
t
a
l
A
g
i
l
e

B
I
E
n
t
e
r
p
r
i
s
e

B
I

a
n
d

O
p
e
r
a
t
i
o
n
a
l
/
A
g
i
l
e

B
I
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
Thank you
Contact information:
J uergen Haupt
CSA Architect
juergen.haupt@sap.com
2012 SAP AG. Alle Rechte vorbehalten.
Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu
welchemZweck und in welcher Formauch immer, ohne die ausdrckliche schriftliche
Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen
knnen ohne vorherige Ankndigung gendert werden.
Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte knnen
Softwarekomponenten auch anderer Softwarehersteller enthalten.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight und Visual Studio sind
eingetragene Marken der Microsoft Corporation.
IBM, DB2, DB2 Universal Database, Systemi, Systemi5, Systemp, Systemp5, Systemx,
Systemz, Systemz10, 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 und Smarter Planet sind Marken oder eingetragene Marken der IBM Corporation.
Linux ist eine eingetragene Marke von Linus Torvalds in den USA und anderen Lndern.
Adobe, das Adobe-Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene
Marken von Adobe Systems Incorporated in den USA und/oder anderen Lndern.
Oracle und J ava sind eingetragene Marken von Oracle und/oder ihrer
Tochtergesellschaften.
UNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group.
Citrix, ICA, ProgramNeighborhood, MetaFrame, WinFrame, VideoFrame und MultiWin
sind Marken oder eingetragene Marken von Citrix Systems, Inc.
HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des 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 und Xcode sind Marken oder eingetragene Marken der Apple Inc.
IOS ist eine eingetragene Marke von Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry
Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook und BlackBerry App
World sind Marken oder eingetragene Marken von Research in Motion Limited.
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 und Android sind
Marken oder eingetragene Marken von Google Inc.
INTERMEC ist eine eingetragene Marke der Intermec Technologies Corporation.
Wi-Fi ist eine eingetragene Marke der Wi-Fi Alliance.
Bluetooth ist eine eingetragene Marke von Bluetooth SIG Inc.
Motorola ist eine eingetragene Marke von Motorola Trademark Holdings, LLC.
Computop ist eine eingetragene Marke der Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, SAP HANA und weitere im Text erwhnte SAP-Produkte und -Dienst-
leistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der
SAP AG in Deutschland und anderen Lndern.
Business Objects und das Business-Objects-Logo, BusinessObjects, Crystal Reports,
Crystal Decisions, Web Intelligence, Xcelsius und andere imText erwhnte Business-
Objects-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken
oder eingetragene Marken der Business Objects Software Ltd. Business Objects ist ein
Unternehmen der SAP AG.
Sybase und Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere und weitere imText
erwhnte Sybase-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind
Marken oder eingetragene Marken der Sybase Inc. Sybase ist ein Unternehmen der
SAP AG.
Crossgate, m@gic EDDY, B2B 360 , B2B 360 Services sind eingetragene Marken
der Crossgate AG in Deutschland und anderen Lndern. Crossgate ist ein Unternehmen
der SAP AG.
Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen
Firmen. Die Angaben imText sind unverbindlich und dienen lediglich zu Informations-
zwecken. Produkte knnen lnderspezifische Unterschiede aufweisen.
Die in dieser Publikation enthaltene Information ist Eigentumder SAP. Weitergabe und
Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchemZweck und
in welcher Formauch immer, nur mit ausdrcklicher schriftlicher Genehmigung durch
SAP AG gestattet.

LSA++ Positioning

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LSA++ Positioning

Uploaded by

Copyright:

Available Formats

LSA++

Layered Scalabl e Architecture for BW on HANA

EDW Propagation Layer EDW Propagation Layer

: provided by OLAP Engine

EDW Propagation Layer EDW Propagation Layer

You might also like