SAP NetWeaver BW: BW Layered Scalable Architecture (LSA) / Blog Series
last update June, 11th 2011
This blog bundles the information related to the SAP NW BW Enterprise Data Warehouse (EDW) Layered Scalable Architecture (LSA) the reference architecture for large scale BW DWHs/ EDWs.
The documents listed below describe different facets of the LSA. New documents about LSA will be added from time to time depending also on your feedback.
For a first rapid walk thru the LSA please refer to SAP NetWeaver BW Layered, Scalable Architecture (LSA) for BI Excellence – Webinar Presentation.
Please find the different links to the LSA documents below:
- Blog: SAP NetWeaver BW: What is the BW Layered Scalable Architecture (LSA) all about?
- Blog: SAP NetWeaver BW: BW Layered Scalable Architecture (LSA) Building Blocks
- Blog: SAP NetWeaver BW 7.30: SAP NetWeaver BW 7.30: LSA Data Flow Templates Series – I. Introduction
More details in my Teched 2009 presentation: The Layered Scalable Architecture for SAP NetWeaver BW on a Corporate Scale’ – lecture BI302
May be a more general presentation from SAPSKILLS 2008 is also of value for you: SAP NetWeaver BI: Data Infrastructure und BI-Maturity – Data Marts, Data Warehouses (DWH), Enterprise Data Warehouses (EDW), Appliances
(Don’t become confused only the first two slides are in German :-))
Firstly, thanks for the great articles. I think that a more structure framework for BI has been a long time in coming.
I have a question about the propagation layer and the corporate memory. Please could you explain a little more why the corporate memory is necessary. Normally, when extracting, one would keep all history in the propagation layer, which seems to render the corporate memory redundant. Are you suggesting that the data in the propagation layer can be deleted once it has been propagated?
Or, is it that one should only store that data that is required (e.g. just the key figures that are relevant at the relevant granularity) for propagation in the propagation layer?
Thanks!