Skip to Content

/LSA320/ LSA Scalability Entire Data Flow Split

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 LSA320 that illustrates how to deal with situations where load performance issues are caused by a single data flow. Guaranteeing report availability is the main challenge.

For general information about LSA Data Flow Templates please refer to

Description

LSA320 illustrates how to deal with situations where load performance issues are caused by a single data flow. Guaranteeing report availability is the main challenge.

If load performance issues occur for a specific data flow, the LSA suggests splitting the entire flow at the earliest possible point in time – on top of the PSAs. All InfoProviders in the flow are homogeneously semantically partitioned using the same organizational criteria, 0COMP_CODE for example.

As the semantic partitioning applies only to a specific data flow, the LSA also refers to this as a tactical semantic partitioning, unlike to the strategic, general semantic partitioning defined by the LSA Data Domains for ‘all’ flows (see LSA 400).

Picture 1: LSA320 conceptual view

Picture 2: LSA320 – EDW Layers in BW 7.30

Picture 3: LSA320 continued – Data Mart Layers in BW 7.30

Note: The corporate memory DataStore objects are usually not semantic partitioned!

For a better understanding another more conceptual representation:

 

Picture 4: LSA320 entire data flow split 

 

Note:  The data transfers are split – not the logic! The logic is bundled using Transformation Rules that are only located between InfoSources!

Target Group

 LSA320 addresses dedicated (high volume) data flows causing load performance issues

Please note:

If it is difficult in general to achieve service levels (report availability, performance or robustness). A strategic semantic partitioning approach implementing LSA domains should be considered (see LSA400).

 

Implementation Details

Acquisition Layer

Note: For more details, see the previous LSA data flow templates

Harmonization & Quality Layer

  • The semantic partitioning is modeled homogeneously for all InfoProviders of the data flow
  • The semantic partitioning is performed using organizational criteria  – not a time characteristic

Note: For more details, see the previous LSA data flow templates

Corporate Memory Layer (CM)

In general, an InfoSource is not required in front of a CM DSO, as semantic partitioning of CM DataStore objects is not recommended.

Note: For more details, see the previous LSA data flow templates

Propagation Layer

  • The semantic partitioning is modeled homogeneously for all InfoProviders of the data flow
  • The semantic partitioning is performed using organizational criteria  – not a time characteristic

Note: For more details, see the previous LSA data flow templates

Business Transformation Layer

  • The semantic partitioning is modeled homogeneously for all InfoProviders of the data flow
  • The semantic partitioning is performed using organizational criteria  – not a time characteristic

Note: For more details, see the previous LSA data flow templates

Reporting Layer

  • The semantic partitioning is modeled homogeneously for all InfoProviders of the data flow
  • The semantic partitioning is performed using organizational criteria  – not a time characteristic

Note: For more details, see the previous LSA data flow templates

Virtualization Layer

Note: For more details, see the previous LSA data flow templates

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply