Multidimensional Modeling

 SAP BW Architecture
 InfoObjects
 InfoCube Design
 Data Sourcing
 Meta Data Model
 Data Staging
 Download from Infocube

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 1

Business Information Warehouse Architecture I

Business
Explorer 3rd party OLAP
clientclient

BAPI

OLAP processor Business

InfoCubes Information
Administrator Meta Data
Workbench Repository Warehouse
Staging Engine ODS Server

BAPI

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 2

Business Information Warehouse Architecture II

Browser

3rd party OLAP Analyzer

client (hosted by MS Excel)
Business Explorer
BAPI

Administrator
OLAP Processor
Workbench
Administration Meta Data InfoCubes
Repository Meta Data Manager Data Manager
Scheduling
Business Information Staging Engine Operational
Monitor Warehouse Server Data Store
BAPI

Non R/3 Production Production Data OLTP

Data Extractor Extractor Reporting

Non R/3 OLTP Applications R/3 OLTP Applications

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 3

Operational vs. Decision Support Environments

Operational Environment SEM Environment

 Detailed, transaction data  Often summarized data

 Current data with minimal history  Significant history required
 Changing with business events  Fixed as of a specific point in time
 Minimally integrated with data from  Significant integration with data from
other modules/applications other modules/applications
 Highly normalized for performance  Often highly denormalized or
restructured for queries
 Update/Insert/Delete  2-7 years of data
 30-60 days of data  Data not associated with an application,
but rather integrated from various
 Only data for specific function of
applications
application

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 4

What is an InfoObject?

 The various OLTP data models are unified for BW

 Business objects / table fields become Data Sources

R/3
OLTP BW Extractor

Table of costcenters
CO
KOSTL ...
Controlling InfoObject
Data Sources “0COSTCENTER”

HR Table of employees
Human EMPLO COST_CENTER ...
Resources
InfoObjects are unique across
application components!
 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 5
InfoObject within BW

 Generic term for Business Evaluation Object

 Definition includes technical information and business logic
 InfoObject components:
 Technical Definition (such as length, format, check routines,
etc.)
 Master Data, Texts
 Attributes
 Hierarchies
 Compound Information

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 6

Types of InfoObjects

 Characteristics: evaluation groups like “Costcenter”,

“Product group”, “Material”
 Have discrete values stored in their master data tables (e.g. the
characteristic “Region” has the values “North”, “South”, ...)
 Special types of characteristics:
 Time characteristics like “Fiscal period”, “Calendar year”, ...
 Unit characteristics which comprise currencies and units of
measure like “Local currency” or “Sales quantity”
 Keyfigures: continuously valued numerical fields like
amounts and quantities (e.g.: “Revenue” and “Sales
quantity”)

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 7

InfoCube Concept 2.0

Summarized Data Infocubes

Consolidated Details ODS

Transactional Details Data Sources

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 8

InfoCube Design

 Central data stores for reports and evaluations

 Contains two types of data
 Key Figures
 Characteristics
 1 Fact Table and 16 Dimension Tables
 3 Dimensions are predefined by SAP
 Time
 Unit
 Info Package

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 9

Star Schema in BW 1.2

(1) Facttable
(2) Dimension
(3) SID Char
(4) Master
(5) SID Attr

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 10

Star Schema in BW 2.0

(1) Fact Table

(2) Dimension
(3) time-independent-SID
time-dependent-SID
traditional SID Char
(4) SID Attr

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 11

Data Sources

How do Data Sources get into the BW Server:

Manual
Delivery of InfoObject
Business maintenance
SAP Content in BW

BAPI
Upload Meta Data

R/3 3.1 OLTP System R/3 4.0 OLTP System Non R/3 OLTP System

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 12

Data Extraction 2.0A

InfoCubes

Business Information Update Rules

Warehouse Server
Staging Engine
InfoSource
Communication Structure

Transfer Rules Transfer Rules

DataSource
(Replikat)
Transfer Structure Transfer Structure

Transfer Structure Transfer Structure

DataSource Extract Structure Extract Structure

Source System 1 Source System 2

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 13

Data Extraction 2.0A
Data Staging
Business Information
Warehouse Server InfoCubes
Staging Engine
Update Rules

InfoSource
DataSource Communication structure

Transfer Structure Transfer Structure Transfer Structure

Transfer Structure Transfer Structure Transfer Structure

Extract Source Structure Extract Source Structure

Extract Source Structure

OLTP System 1 OLTP System 2

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 14

BW 2.0A Data Source

 DataSource
 Source System related Structure of fields
 not related to InfoSources or InfoObjects in the BW System
 InfoSource
 defined by InfoObjects
 can be related to many data sources of one ore many Source
Systems
 Data upload now related to:
InfoSource-Source System-DataSource
 InfoObjects are not designed in the Source System any longer
InfoObjects are global definitions in BW 2.0

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 15

New Meta Data Model (OLTP)

 InfoSources on OLTP are renamed into DataSources

 No InfoObjects on OLTP anymore (!)
 OLTP meta data just contains what is necessary
 No difference between DataSources for master- and
transaction data
 One table for all DataSources
 Transport connection for DataSources
 SAP content version for DataSources

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 16

New Meta Data Model (BW)

 Simple meta data upload

 just replication of DataSources
 no creation of global meta data
 Transfer structures and Update Rules for Texts
 All assignments / update rules in BW
 single point of entry
 Decentralised content development
 1:N assignment for DataSources to InfoSources / InfoObjects
 support for IBU DataSources

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 17

Transfer Rules

 1.2B
 transactional InfoSources
 master data but only for attributes

 2.0A
 available for all DataSources
 transactional Data Sources
 Text
 Attriubtes
 Hierarchies

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 18

 Meta Data Upload 2.0
BW Server

Global InfoSources InfoObjects

Meta Data Transaction Data Attributes Texts Hierarchies Generated
InfoSources

Assignment
2LIS*
InfoSources / InfoObjects InfoObjects
(Transfer Rules)
MATNR
“Content”
DataSources Fields
0MATERIAL
EXIT
DataSources OLTP System 1 OLTP System 2 OLTP System 3 InfoObject
(Replication) creation
0CO_CCA_INI 0CO_CCA_INI 0CO_CCA_INI
0MATERIAL_TEXT 0ARTICLE_TEXT ....
0MATERIAL ATTR 0ARTICLE_ATTR

OLTP System 1 OLTP System 2

Data Source Types Extract Structures
0CO_CCA_INI Transaction data F1 F2 F3 ...
0CO_CCA_DELTA Transaction data F1 F2 F4 ...
2_LIS_S555 Transaction data F5 F6 F7 ...
0MATERIAL_ATTR Master data F5 F8 F9 ...
0MATERIAL_TEXT Texts
F5 T1 T2 ...
0MATERIAL_LGEN_HIER Hierarchies H1 H2 H3...
 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 19
Data Staging Process 2.0 Master Data
BW Server
InfoObject 0MATERIAL
Properties: TYPE = ‘CHAR’
LENGTH = ‘18’
etc. .....

Master Data Table Text Table Hierarchy Table

0MATERIAL 0MAT_TYPE ... 0MATERIAL 0TXTSH HIEID NODEID

Transfer Transfer
Transfer
Rules Rules
Rules
DataSource DataSource
DataSource 0MATERIAL_TEXT
0MATERIAL_ATTR 0ARTICLE_ATTR
Transfer structure Transfer structure Transfer structure Extract structure
F1 F3 F4 ... F1 F5 F7 ... F1 T1 T2 ... H1 H2 H3 ...

OLTP System Core OLTP System Retail

DataSource DataSource DataSource DataSource
0MATERIAL_ATTR 0MATERIAL_TEXT 0MATERIAL_LGEN_HIER 0ARTICLE_ATTR

Transfer structure Transfer structure Transfer structure

Extract Structures
F1 F3 F4 ... F1 T1 T2 ... F1 F5 F7 ...
Extract Structure Extract Structure H1H2 H3 H4 Extract Structure

F1 F2 F3 F4 ... F1 T1 T2 T3 ... H5H6 H7 H8 F1 F5 F6 F7 ...

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 20
Enhancements Data Staging Process

 Delta Upload for Multiple BW Systems

 Multiple Init Selections
 Scheduler - Subsequent Processing
 Event Chains
 Download from InfoCube
 Additional Delete Features
 Scheduler - Data selection
 Update data for Infocube
 Roll up and Compress InfoCubes

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 21

Download from InfoCube

 Download:
 DB table
 Frontend
 Excel
 Word
 Lotus 1-2-3
 ASCII
 DBASE
.
.
.

 SAP AG 2000 SEM 210 2/2000 (Ulrich Hauke) / 22