Modeling the Enterprise Data Warehouse 

You use this variant to implement and monitor your enterprise data warehouse. It covers data modeling (modeling InfoProviders), data acquisition (defining sources and transfer mechanisms), the transformation of data including data distribution, and also enables metadata and document management.

This variant allows you to integrate heterogeneous source systems into one Enterprise Data Warehouse. Not only can heterogeneous technical platforms be interfaced, different master and transaction data semantics can also be consolidated. 

Flexible structures and layers allow you to adapt quickly to new business challenges (such as changed objectives, mergers and acquisitions).

Scenario Variant Architecture

The following graphic provides an overview of the architecture of the variant:

IT Processes for the Scenario Variant

This scenario variant comprises the following IT processes:

Process	Description
Data Modeling	In this process you create highly flexible and differentiated data models. You use these data models to model different enterprise data warehouse layers.
Metadata and Document Management	In this process you manage metadata and documents, search in them or exchange them with other BI systems, and create documentation on metadata.
Data Acquisition	In this process you connect your BI system to heterogeneous source systems either directly or using SAP NetWeaver XI. The process also supports direct access to data in source systems.
Transformation	In this process you consolidate, cleanse and integrate data. You can semantically synchronize data from heterogeneous sources.
Data Distribution	In this process you distribute data from your data warehouse to other data warehouses, if you are operating several data warehouses.

Required and Optional Installable Units

In order to use this scenario variant, you need the following installable units:

System with activated usage types:

●     Business Intelligence (BI)

●     BI Java components (BI Java)

●     Enterprise Portal (EP)

●     Application Server ABAP (AS ABAP)

●     Application Server ABAP (AS ABAP)

●     Process Integration (PI)

and the standalone engine:

●     TREX

For more information on the required system landscape, see the Master Guide.