/LSA310/ LSA Scalability – Flow Split and InfoSources
Background
With the new Data Flow Template feature it is now possible describing LSA standards directly in BW.
With BW 7.30 there comes a set of 10 LSA data flow templates as an initial offering.
This blog describes the LSA Data Flow Template LSA310 that illustrates the power of InfoSources increasing transparency as Transformation rules are always located between InfoSources.
For general information about LSA Data Flow Templates please refer to
- SAP NetWeaver BW 7.30: LSA Data Flow Templates Series - I. Introduction
- SAP NetWeaver BW 7.30: LSA Data Flow Templates Series - II. LSA Basics for LSA Data Flow Templates
Description
For the sake of transparency and flexibility, the LSA advocates shielding all persistent InfoProviders with InfoSources. Using InfoSources increases transparency as Transformation rules are always located between InfoSources. Using InfoSources increases flexibility by introducing semantic partitioning or making it possible to add semantic partitions later on. It also reduces redundancy (of coding & transformation) as transformations for all semantic partitioned InfoProviders are stored in one location.
LSA310 is based on LSA300 and illustrates the most consistent way of using InfoSources. In LSA300 already, it can be seen that the SPO automatically generates an InfoSource as Inbound InfoSource (and an Outbound InfoSource, which is not shown in the graphic).
Using the InfoSource – especially in the early stages of an implementation - might seem a bit excessive. Experience shows that the abstraction from persistent InfoProviders using InfoSources is worthwhile in the long run, as it reduces maintenance costs and increasing overall flexibility. More pragmatic use of InfoSources is shown in the LSA315 flow. A further extension of InfoSource usage dealing with multiple sources is provided in LSA410.
Picture 1: LSA310 conceptual view
Picture 2: LSA310 - EDW Layers in BW 7.30
Picture 3: LSA310 continued - Data Mart Layers in BW 7.30
Target Group
Large BW implementations built for flexibility, maintainability and growth.
Implementation Details
Acquisition Layer
- Inbound and Outbound InfoSources are used for all persistent InfoProviders of any layer.
- Inbound and Outbound InfoSources are generated automatically using the BW 7.30 SPO feature.
Note: For more details, see the previous LSA data flow templates
Harmonization & Quality Layer
- Inbound and Outbound InfoSources are used for all persistent InfoProviders of any layer.
- Inbound and Outbound InfoSources are generated automatically using the BW 7.30 SPO feature.
Note: For more details, see the previous LSA data flow templates
Corporate Memory Layer (CM)
- Inbound and Outbound InfoSources are used for all persistent InfoProviders of any layer.
- Inbound and Outbound InfoSources are generated automatically using the BW 7.30 SPO feature.
Note: For more details, see the previous LSA data flow templates
Propagation Layer
- Inbound and Outbound InfoSources are used for all persistent InfoProviders of any layer.
- Inbound and Outbound InfoSources are generated automatically using the BW 7.30 SPO feature.
Note: For more details, see the previous LSA data flow templates
Business Transformation Layer
- Inbound and Outbound InfoSources are used for all persistent InfoProviders of any layer.
- Inbound and Outbound InfoSources are generated automatically using the BW 7.30 SPO feature.
Note: For more details, see the previous LSA data flow templates
Reporting Layer
- Inbound and Outbound InfoSources are used for all persistent InfoProviders of any layer.
- Inbound and Outbound InfoSources are generated automatically using the BW 7.30 SPO feature.
Note: For more details, see the previous LSA data flow templates
Virtualization Layer
Note: For more details, see the previous LSA data flow templates
1 Comment