Currently Being Moderated

/LSA410/ LSA Scalability & Data Domains – Strategic Semantic Partitioning of Entire BW (Collect)

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 LSA410 that addresses challenges across the DWH (e.g, with global BWs) by introducing Data Domains. Here we collect (organize) data from multiple sources.

For general information about LSA Data Flow Templates please refer to

Description

If BW has to process data from multiple source systems for the same business processes as with multiple SAP ERP sources across the globe, LSA recommends introducing data domains. These then define the criteria collecting data for the same DataSource from multiple source systems into semantically partitioned InfoProviders throughout the entire BW.

  • Data domains collecting data flows for the same DataSource but from different source systems will keep the BW manageable and transparent.  The more source systems you have, the truer this becomes.
  • Be careful and do not create bottlenecks!
  • Splitting and collecting data into domains can be performed for the same DataSource

 

Picture 1: LSA410 conceptual view

 

Picture 2: LSA410 conceptual view (DTPs & Corporate Memory)

 

Picture 3: LSA410 - EDW Layers in BW 7.30

 

Picture 4: LSA410 continued - Data Mart Layers in BW 7.30

 

Target Group

  • For all large BWs with geographically spread source systems.
  • Often relevant when multiple BWs are consolidated  into a single corporate/divisional BW

Implementation Details

Acquisition Layer

The same implementation details apply as for LSA400.

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)semantic 

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 of 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 of 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 of 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: