lsa++ english version

Mauricio Cubillos OcampoStrategic Analytics AdvisorSAP – MultiCountry South (August.2014)

LSA++ Architecture

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.

© 2013 SAP AG or an SAP affiliate company. All rights reserved. 2This 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.

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.

Disclaimer

Agenda

What is LSA and LSA++ ?

Implementation

Design Recommendations


What is LSA y LSA++ ?

LSA architecture is a set of models or construction guides for building Datawarehouse (EDW), that SAP has adopted on its EDW product: Business Warehouse (BW).

Its purpose is to provide an effective and efficient storage, quering, analysis and data access solution

Data Acquisition

Quality and Harmonization

Data PropagationCorp.

Memory

Business Transformation

Reporting

Ope

ratio

nal D

ata

LS

A



These architectures are based on Layers concept, which leads to build objects over objects, thus assures data integrity (Single Version of Truth) and resources efficiency (Extract Once, Deploy Many).

Data Acquisition

Quality and Harmonization

Data PropagationCorp.

Memory

Business Transformation

Reporting

Ope

ratio

nal D

ata

LS

A



LSA architecture applies when working on SAP BW (vers.<=7.3) running on top of any data base.

LSA++ architecture applies when working on SAP BW running on top of SAP HANA.

RDBMS

SAP NetWeaver BWSAP NetWeaver BW

Data ModelingData Modeling

PlanningPlanning

Data ManagementData Management

OLAPOLAPPro

ce

ss

O

rch

es

tra

tio

nP

roc

es

s

Orc

he

str

ati

on

SAP BW on HANASAP BW on HANA

Data ModelingData Modeling

PlanningPlanning

Data Management

Data Management

OLAPOLAPPro

ce

ss

O

rch

es

tra

tio

nP

roc

es

s

Orc

he

str

ati

on

Push Down

LSA

LSA++



ARCHITECTED DATAMART• Consolidated, part of EDW and LSA,

It supports decision making on corporate data.

• IT managed, standarized data models on corporate data

• Long term requeirements, high stability and consistency.

• Aggregated data, usually by time.

OPERATIONAL DATAMART• Real time and timely delivery focus• It reports on big volume, highly

granular transactional data• It supports business operation• High data volatility

AGILE DATAMART• No-IT managed, no EDW• Máxium modeling flexibility and data

sourcing for LOB• It supports LOB´s strategic decisión

making• no-persitent and historic data within

flexible data models

LSA++Openness: BW managed and

Non-BW managed data.

Flexibility: lesser Data FootPrint



ER

P (

So

urce

Sys

.)

SLT

Ext

ract

or

HANA Table

BW Inbound

No-

BW

BW Ope

n D

SO

Replication

Extraction

LSA++Openness: BW managed and Non-BW managed data.Flexibility: lesser Data FootPrint

Virtualization

BW on HANA BW on HANA Data Models



• Faster Data Loads.

• Less Memory usage (Data Footprint).

• Simpler Data Models.

• More flexible Data Models.

• Less Administration, less TCO.

• More functionality for users.

• Real-Time Reporting .

LSA++Openness: BW managed and NO-BW managed data.Flexibility: lesser Data FootPrint

Agenda


Implementation

Design Recommendations


Implementation - LSA (1/4)

LSA and LSA++ are guides and suggestion, thus every project must find their own layers to use and how to use them.

* proposed LSA architecture for an important customer in Colombia

LAYERS

* Scope: Architected DataMarts

CorporateMemory

Data Adquisition Layer

Enterprise DataWarehouse

Architected DataMarts

Reporting

Data Acquisition Layer


Implementation - LSA (2/4)

Repositories


Different repositories are created in each layer. More granular data: DSO’s. More enriched, aggregated data: Infocubes


Ejemplo de Implementación LSA (3/4)

InfoAreas

Layers are also reflected in InfoAreas. This will allow a very structured and more easily to maintain Data warehouse



Ejemplo de Implementación LSA (4/4)

Process Chains


Process Chains can be built to load data Layer by Layer. This approach will allow smaller process chains to maintain and also changes in the process chains will not impact scheduling


Implementation - LSA++

Optimized / Simpler Data Model

• Only ODS’s (no Infocubes), No Aggregates, No RollUp, No Change Run, Less data footprint (no duplicidad)

• “Serialized” Corporate Memory

• Corporate Memory on NLS

* proposed LSA++ architecture for an important customer in Colombia

Corporate Memory

EDW

Agenda


Implementation

Desing Recommendations


Design Recommendations (LSA++ 1/4)

BW data flows uses two repositories: InfoCubes and DSO’s.

DSO’s are usually used to store highly granular data, and Infocubes are used to store enriched more aggregated data.

LSA++ objectives:o Reduce # of persistent repositories.o Persitent repositories optimized design

and implementation.o Reduced impact on persitent

repositories.

…


Design Recommendations (LSA++ 2/4)

Architected DataMart (Reporting) layer can be virtualized, when infoobjects are mapped 1:1 .

Source:Jurgen Haupt, CSA SAPLSA ++ for SAP Netweaver BW on SAP HANA


Recomendaciones de Diseño (LSA++ 3/4)

Business transformation layer can be virtualized when infoobjects are mapped 1:1.



Recomendaciones de Diseño (LSA++ 4/4)

Architected Data Mart (Reporting) layer can be either Non-Persistent (Virtual) or Persistent. Use virtual whenever possible.



© 2013 SAP AG or an SAP affiliate company. All rights reserved.

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.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP 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.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx

lsa++ english version

Data & Analytics