Currently Being Moderated

/LSA400/ LSA Scalability & Data Domains – Strategic Semantic Partitioning of Entire BW (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 LSA400 that addresses challenges across the DWH (e.g, with global BWs) by introducing Data Domains. Simply speaking, this means that we do not mix American transactional data with European or Asian transactional data.

For general information about LSA Data Flow Templates please refer to

 

Description

For large/global BWs, keeping to service level agreements (report availability, time-zones, robustness of operations etc.) is generally something of a challenge. For global BW, you have to be aware that there is no maintenance window (24x365) applicable to all data.

The LSA addresses these challenges by introducing Data Domains. Simply speaking, this means that we do not mix American transactional data with European or Asian transactional data. From a modeling perspective, defining data domains means providing a standard (strategic) concept for semantically partitioning the InfoProviders across your BW:

  • Which domains? e.g. APJ, EMEA, AMS, US and so on 
  • What are the standard criteria for semantically partitioning the data? e.g. 0COMP_CODE for sales data, 0CO_AREA for controlling data and so on
  • What criteria values define the domains? i.e. assigning 0COMP_CODE values to APJ or EMEA or AMS and so on

In addition to the layers, LSA domains achieve clear structuring of the transactional data in your BW. As the semantic partitioning applies to all or a wide range of data flows and InfoProviders, the LSA calls this way of using the semantic partitioning pattern ‘strategic’.

Consistent distribution of transactional data is crucial, and can be highly automated using SPO functionality. 

If we look at a single data flow, we observe that the visualization is the same as the tactical semantic partitioning introduced in LSA320 - Entire Data Flow Split.

Note that LSA domains do not apply in the corporate memory layer!

 

Picture Picture 1: LSA400 conceptual view

 

Picture 2: LSA400 - EDW Layers in BW 7.30

 

Picture 3: LSA400 continued - Data Mart Layers in BW 7.30

A conceptual representation shows how data domains work filled by a split for all SD flows using the same criteria:

Picture 4: LSA400 - Extract Once - Deploy Many

 

Target Group

 LSA400 is a standard flow template for all larger BWs that typically have a large geographical spread

Implementation Details

Acquisition Layer

The same implementation details apply as for LSA320.

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

Harmonization & Quality Layer

The same implementation details apply as for LSA320.

  • The semantic partitioning is modeled homogeneously for all InfoProviders in the data flow
  • In terms of the customer LSA Domain concept , the semantic partitioning is performed homogeneously by an organizational criteria (characteristic) 

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

Corporate Memory Layer (CM)

The same implementation details apply as for LSA320. The customer LSA Domain concept does not apply to CM DataStore objects.

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

Propagation Layer

The same implementation details apply as for LSA320.

  • The semantic partitioning is modeled homogeneously for all InfoProviders in the data flow
  • In terms of the customer LSA Domain concept , the semantic partitioning is performed homogeneously by an organizational criteria (characteristic)semantic

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

Business Transformation Layer

The same implementation details apply as for LSA320.

  • The semantic partitioning is modeled homogeneously for all InfoProviders in the data flow
  • In terms of the customer LSA Domain concept , the semantic partitioning is performed homogeneously by an organizational criteria (characteristic)semantic

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

Reporting Layer

The same implementation details apply as for LSA320.

  • The semantic partitioning is modeled homogeneously for all InfoProviders in the data flow
  • In terms of the customer LSA Domain concept , the semantic partitioning is performed homogeneously by an organizational criteria (characteristic)semantic

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

Virtualization Layer

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

Comments

Actions

Filter Blog

By date: