LSA++ Architecture 
Mauricio Cubillos Ocampo 
Strategic Analytics Advisor 
SAP – MultiCountry South (August.2014) 
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 
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. 
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. 2
Agenda 
What is LSA and LSA++ ? 
Implementation 
Design Recommendations
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 
Reporting 
Business Transformation 
Data Propagation 
Quality and Harmonization 
Data Acquisition 
Corp. 
Memory 
Operational Data 
LSA 
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. 5
What is LSA y LSA++ ? 
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). 
Reporting 
Business Transformation 
Data Propagation 
Quality and Harmonization 
Data Acquisition 
Corp. 
Memory 
Operational Data 
LSA 
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. 6
What is LSA y LSA++ ? 
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. 
SAP NetWeaver BW 
Data Modeling 
Planning 
OLAP 
Data Management 
RDBMS 
Process 
Orchestration 
SAP BW on HANA 
Data Modeling 
Planning 
OLAP 
Data 
Management 
Process 
Orchestration 
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. 7
What is LSA y LSA++ ? 
LSA++ 
Openness: BW managed and 
Non-BW managed 
data. 
Flexibility: lesser Data 
FootPrint 
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. 
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 
OPERATIONAL DATAMART 
• Real time and timely delivery focus 
• It reports on big volume, highly 
granular transactional data 
• It supports business operation 
• High data volatility 
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. 8
What is LSA y LSA++ ? 
Replication 
ERP (Source Sys.) 
Extractor SLT 
Openness: BW managed and Non-BW managed data. 
Flexibility: lesser Data FootPrint 
HANA 
Table 
BW 
Inbound 
LSA++ 
BW No-BW 
Open DSO 
Extraction 
Virtualization 
BW on HANA BW on HANA Data Models 
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. 9
What is LSA y LSA++ ? 
LSA++ 
Openness: BW managed and NO-BW managed data. 
Flexibility: lesser Data FootPrint 
• 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 . 
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. 10
Agenda 
What is LSA and LSA++ ? 
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. 
Reporting 
Architected DataMarts 
Enterprise DataWarehouse 
Data Data Adquisition Acquisition Layer 
Layer 
* Scope: Architected DataMarts 
Corporate 
Memory 
* proposed LSA architecture for an important customer in Colombia 
LAYERS 
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. 12
Implementation - LSA (2/4) 
Different repositories are 
created in each layer. More 
granular data: DSO’s. More 
enriched, aggregated data: 
Infocubes 
Repositories 
* proposed LSA architecture for an important customer in Colombia 
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. 13
Ejemplo de Implementación LSA (3/4) 
Layers are also reflected in 
InfoAreas. This will allow a 
very structured and more 
easily to maintain Data 
warehouse 
InfoAreas 
* proposed LSA architecture for an important customer in Colombia 
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. 14
Ejemplo de Implementación LSA (4/4) 
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 
Process Chains 
* proposed LSA architecture for an important customer in Colombia 
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. 15
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 
EDW 
Corporate 
Memory 
* proposed LSA++ architecture for an important customer in Colombia 
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. 16
Agenda 
What is LSA and LSA++ ? 
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. 
… 
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. 18
Design Recommendations (LSA++ 2/4) 
Architected DataMart (Reporting) 
layer can be virtualized, when 
infoobjects are mapped 1:1 . 
Source:Jurgen Haupt, CSA SAP 
LSA ++ for SAP Netweaver BW on SAP HANA 
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. 19
Recomendaciones de Diseño (LSA++ 3/4) 
Business transformation layer 
can be virtualized when 
infoobjects are mapped 1:1. 
Source:Jurgen Haupt, CSA SAP 
LSA ++ for SAP Netweaver BW on SAP HANA 
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. 20
Recomendaciones de Diseño (LSA++ 4/4) 
Architected Data Mart (Reporting) 
layer can be either Non-Persistent 
(Virtual) or Persistent. Use virtual 
whenever possible. 
Source:Jurgen Haupt, CSA SAP 
LSA ++ for SAP Netweaver BW on SAP HANA 
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. 21
Thanks 
Mauricio Cubillos Ocampo 
Strategic Analytics Advisor 
mauricio.cubillos@sap.com 
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
© 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. 
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. 23

LSA++ english version

  • 1.
    LSA++ Architecture MauricioCubillos Ocampo Strategic Analytics Advisor SAP – MultiCountry South (August.2014) 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.
  • 2.
    Disclaimer This presentationoutlines 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. © 2013 SAP AG or an SAP affiliate company. All rights reserved. 2
  • 3.
    Agenda What isLSA and LSA++ ? Implementation Design Recommendations
  • 4.
    Agenda What isLSA and LSA++ ? Implementation Design Recommendations
  • 5.
    What is LSAy 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 Reporting Business Transformation Data Propagation Quality and Harmonization Data Acquisition Corp. Memory Operational Data LSA 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. 5
  • 6.
    What is LSAy LSA++ ? 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). Reporting Business Transformation Data Propagation Quality and Harmonization Data Acquisition Corp. Memory Operational Data LSA 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. 6
  • 7.
    What is LSAy LSA++ ? 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. SAP NetWeaver BW Data Modeling Planning OLAP Data Management RDBMS Process Orchestration SAP BW on HANA Data Modeling Planning OLAP Data Management Process Orchestration 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. 7
  • 8.
    What is LSAy LSA++ ? LSA++ Openness: BW managed and Non-BW managed data. Flexibility: lesser Data FootPrint 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. 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 OPERATIONAL DATAMART • Real time and timely delivery focus • It reports on big volume, highly granular transactional data • It supports business operation • High data volatility 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. 8
  • 9.
    What is LSAy LSA++ ? Replication ERP (Source Sys.) Extractor SLT Openness: BW managed and Non-BW managed data. Flexibility: lesser Data FootPrint HANA Table BW Inbound LSA++ BW No-BW Open DSO Extraction Virtualization BW on HANA BW on HANA Data Models 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. 9
  • 10.
    What is LSAy LSA++ ? LSA++ Openness: BW managed and NO-BW managed data. Flexibility: lesser Data FootPrint • 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 . 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. 10
  • 11.
    Agenda What isLSA and LSA++ ? Implementation Design Recommendations
  • 12.
    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. Reporting Architected DataMarts Enterprise DataWarehouse Data Data Adquisition Acquisition Layer Layer * Scope: Architected DataMarts Corporate Memory * proposed LSA architecture for an important customer in Colombia LAYERS 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. 12
  • 13.
    Implementation - LSA(2/4) Different repositories are created in each layer. More granular data: DSO’s. More enriched, aggregated data: Infocubes Repositories * proposed LSA architecture for an important customer in Colombia 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. 13
  • 14.
    Ejemplo de ImplementaciónLSA (3/4) Layers are also reflected in InfoAreas. This will allow a very structured and more easily to maintain Data warehouse InfoAreas * proposed LSA architecture for an important customer in Colombia 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. 14
  • 15.
    Ejemplo de ImplementaciónLSA (4/4) 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 Process Chains * proposed LSA architecture for an important customer in Colombia 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. 15
  • 16.
    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 EDW Corporate Memory * proposed LSA++ architecture for an important customer in Colombia 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. 16
  • 17.
    Agenda What isLSA and LSA++ ? Implementation Desing Recommendations
  • 18.
    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. … 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. 18
  • 19.
    Design Recommendations (LSA++2/4) Architected DataMart (Reporting) layer can be virtualized, when infoobjects are mapped 1:1 . Source:Jurgen Haupt, CSA SAP LSA ++ for SAP Netweaver BW on SAP HANA 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. 19
  • 20.
    Recomendaciones de Diseño(LSA++ 3/4) Business transformation layer can be virtualized when infoobjects are mapped 1:1. Source:Jurgen Haupt, CSA SAP LSA ++ for SAP Netweaver BW on SAP HANA 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. 20
  • 21.
    Recomendaciones de Diseño(LSA++ 4/4) Architected Data Mart (Reporting) layer can be either Non-Persistent (Virtual) or Persistent. Use virtual whenever possible. Source:Jurgen Haupt, CSA SAP LSA ++ for SAP Netweaver BW on SAP HANA 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. 21
  • 22.
    Thanks Mauricio CubillosOcampo Strategic Analytics Advisor mauricio.cubillos@sap.com © 2013 SAP AG or an SAP affiliate company. All rights reserved.
  • 23.
    © 2013 SAPAG 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. 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. 23