Enterprise Wide Data

Warehousing with SAP BW

SAP NetWeaver Regional Implementation Group -BI

SAP AG
 Content

Content

ƒ Enterprise Wide BW - Background

ƒ Elements of a Corporate BW Strategy
ƒ The BW Data Model Prevents Silos
ƒ BW Data Layers Guarantee Reliability and Flexibility
ƒ BW Corporate Landscape Patterns

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 2

 Enterprise Wide BW

Background
z Continuously increasing number of BW installations
z Steady growth and coverage of BW installations
z High degree of customer-satisfaction with BW
z Broad analyst acceptance of BW and the packaged solution approach
z In general a renaissance of data warehousing

Introduce an enterprise wide BW Strategy and Guidelines that guarantees :

z Flexibility
z Reliability
at low costs

What offers BW to help you realizing an enterprise Data

Warehouse Strategy ?
What are the elements of an enterprise BW Strategy ?

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 3

 Enterprise Perspective on BW

Enterprise perspective on BW:

z Higher level organizational units want
to harmonize the lower level BW initiatives
z Architecture-based BW implementation Group
Group
from the very beginning
z Stabilize a mature BW landscape DivisionAA
Division DivisionBB
Division DivisionCC
Division DivisionDD
Division
(Overhaul the architecture)

Business
......
...... Retail
Retail Business .......
.......
Marketing
Marketing

Asia/
Europe Americas Asia/
Europe Americas Pacific
Pacific

Germany
Germany
Spain
Spain
UK
UK
France
France
Nordic
Nordic

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 4

 Multiple BW Implementations – Challenges

Source
Consistency issues:
„ Uncontrolled data flows
Source Source
„ Multiple extractions of same data
Source
Unit 1
„ Costly developmentLocal
BW
„ Not aligned data models
BW
Source
Î Danger of ‘high level’ Silos
Stream C
BW Local
Local
Source BW
BW Group
Unit 2
BW Stream A
BW
BW

Local
BW Stream B
Source
Local BW
BW
Source
Source
Source
Source

Successful Data Warehousing means: controlled redundancy !

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 5
 Local BW Implementation – Challenges

Observations: Real World

„ Incremental set up
„ Solution-Focus (Data Marts) U V W .... Information
requirements
„ Departmental view

BW Project Team
„ Project is responsible Schema-
for the entire Modeling
Data Warehouse Process Data Marts-
InfoCubes

Potential consequences: Business Rules

„ Departmental islands (silos)
„ Consistency problems Transformation

„ Completeness not sufficient Extraction

„ Flexibility restricted
Sources
„ Trace back not possible

Successful Data Warehousing means: controlled redundancy !

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 6
 Corporate Data Warehousing Strategy

Missing corporate strategy and guidelines

Potential consequences:
Means: „ Silo solutions
„ Uncontrolled Redundancy „ Doubtful reliability
„ Limited Solution Focus „ Restricted flexibility
„ High costs

Prerequisites to set up a proper strategy:

„ Awareness
about accepted data warehousing concepts and their benefits

„ Support of corporate management (Sponsorship)

If there is no organizational momentum toward a common goal, then the best

“ architecture, the best framework in the world is bound to fail.
W.H. Inmon

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 7

 Who needs a Corporate BW Strategy?
All, but the prerequisites are different!
Group

Headquarter Stream A Stream B Stream C Stream D

Organization,
Region A Region B Region C
Business
Business
...... Retail ......
Marketing
countries

Regions/ countries

Necessity of a corporate BW Strategy

Legacy
Architecture-,
Legacy
SAP-based, OLTP landscape
‚single Instance‘ Legacy R/3

Legacy Legacy R/3

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 8

 Content

Content

ƒ Enterprise Wide BW - Background

ƒ Elements of a Corporate BW Strategy
ƒ The BW Data Model Prevents Silos
ƒ BW Data Layers Guarantee Reliability and Flexibility
ƒ BW Corporate Landscape Patterns

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 9

 Elements of a Corporate BW Strategy

Think of: Building a ‘Corporate Information Factory’ *

- Avoid Silos

BW Enterprise Data Warehousing

Decision Areas

Integration
Application
Architecture Development
Strategy
Support

Data Layer Data Model Landscape

Tactical/
Operational
Strategic
Decision-Making
Decision-Making

*The Corporate Information Factory: introduced by Inmon, Imhoff

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 10

 The Role of a Consistent Data Warehouse Data Model

Inconsistent Data Warehouse Data Models Consistent Data Warehouse

⇒ Island-solutions (silos, stovepipes) Data Model ⇒ long term success

?
?
A challenge for
Data Warehouse
consistency

Material Sales HR
Management OLTP OLTP
OLTP
Not aligned operational Consistent corporate Data Model
Data Models

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 11

 The BW Data Warehouse Data Model

BW offers as part of the BW Data Warehouse Data

Business Content Model for SAP und other
a predefined expandable applications
(InfoObjects & InfoSources)
Data Warehouse Data Model

Consistent mapping of operative

data models
ƒ For all SAP applications
ƒ For SAP industrial solutions
(e.g. Retail, Utilities..)
ƒ For non SAP application SAP Corporate
Data Model
ƒ Ascential Partnership
ƒ Siebel, Oracle ....
Legacy
Data Models

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 12

 BW Extended Star Schema
built on the BW Data Model

0MATERIAL
0CUSTOMER 0SALESPERS 0CUSTOMER
0MATGR
00CUSTGR 0SALESORG
0MATTYPE 0MATERIAL
...... .....
...... 0AMOUNT

BW InfoObject Master Data: BW InfoCube:

BW Extended Star Schemas
Shared/ Conformed scope-specific
built on BW Data Model
Dimensions

BCT InfoSources ≡
0MATERIAL 0MATGR 0MATTYPE 0DOCNO 0CUSTOMER 0SALESPERS 0MATERIAL 0AMOUNT
Subject Areas
Master Data BW Data Model defined Transaction Data
by Business Content

BCT Extractors/ DataSources

Materialgroup Sales
MaterialType
ORG

Customer Sales Person

Corporate Data Model:
Material SAP Components

Sales
Transaction

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 13

 BW Extended Star Schemas Prevent Silos
Conformed, Shared
Part of
Local Part of Material Dimension Local Part of
Material Dimension Material Dimension
Material Master Table
0MATERIAL
Material Type
Material_Dimension_ID Material_Dimension_ID

0MATERIAL Material Text Table 0MATERIAL

Material Dimension 0PROD_HIER
Table 0MATERIAL Material Dimension
Table
Language Code
Material_Dimension_ID Material Name
Material_Dimension_ID
SalesOrg_Dimension_ID
Material Hierarchy ..........._Dimension_ID
Time_Dimension_ID
.............Dimension_ID
Customer_Dimension_ID Table .............Dimension_ID
Vertriebsorganisation

Sales Amount Region 1 Region 2 Region 3

Key figure 1
Quantity InfoCube Bezirk 1 Bezirk 2 Bezirk 3 Bezirk 4 Bezirk 5 InfoCube
Key figure 2
A Gebiet 1 Gebiet 2 Gebiet 3 Gebiet 3a Gebiet 4 Gebiet 5 Gebiet 6 Gebiet 7 Gebiet 8
B
FACT Table
Material Dimension: FACT Table

local & conformed part

Conformed dimensions enable virtual BW MultiProvider scenarios

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 14

 BW DWH Data Model and Enterprise Wide BW

The BW Data Warehouse Data Model is the glue,

which ties everything together!
It protects against ‘silos’ (‘stove pipe solutions‘, ‘islands’)
„ Within a BW Instance
„ Within a BW Landscape

It is the basis for communication

„ ‘Drill Thru’ between BW solution structures (InfoCubes, ODS-Objects)
‹ within a BW Instance
‹ within distributed BW Instances
„ ‘Drill Thru’ between BW solution structures and SAP applications
„ Between people

Enterprise BW Strategy:
„ Usage of delivered BW DWH data model whenever possible
„ Central controlled guidelines for modifications and expansions

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 15

 Content

Content

ƒ Enterprise Wide BW - Background

ƒ Elements of a Corporate BW Strategy
ƒ The BW Data Model Prevents Silos
ƒ BW Data Layers Guarantee Reliability and Flexibility
ƒ BW Corporate Landscape Patterns

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 16

 Introducing a BW Layer Architecture to Guarantee
Reliability and Flexibility

SAP Business Information Warehouse and

the Corporate Information Factory (CIF)*
Data Primary Data
Acquisition Data Delivery
Staging Cleansing Management
Area Transform
Data Architected
Warehouse Data Marts
E xtracti on / Open St agi ng

Master
Reference
Data

Open D is tribu ti on
Finance
any source

any target
Transaction
Data

Logistic

Operational
Data
Store
‘The Data Mart is customized and/or
summarized data derived from the
data warehouse’
* Source: Bill Inmon
© SAP AG 2004, Enterprise Wide BW, J. Haupt / 17
 BW Architected Data Mart Layer:
The Departmental Layer – What can we expect?

0CUSTOMER
master

BW Extended Star Schema:

„ InfoCubes
0CUSTOMER 0CUSTOMER 0CUSTOMER „ InfoObject Master Data
(‘conformed dimensions’)
InfoCube A InfoCube B InfoCube C

0MATERIAL 0MATERIAL

0MATERIAL
master

The BW Data Mart Layer based on the BW Data Model and a

proper Project Method offers
„ Consistency within the Data Marts (InfoCubes, ODS-Objekte)
„ Control of data redundancy (MultiProvider, Queries)
„ All desired historical views
„ ...

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 18

 BW Architected Data Mart Layer:
The Departmental Layer – Corporate Needs ?
„ It is not the task of the scope-oriented Data Mart layer to anticipate
all kinds of future arising needs – this would overload the schemas
and corrupt performance

„ It cannot be expected that the data mart project teams have the 360°
corporate view

Æ We are limited from a corporate perspective in terms of

z Flexibility, Completeness
z Reliability, Consistency
if we concentrate ourselves just on Data Marts.

Æ BW Data Warehouse Layer – the corporate layer

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 19

 The BW (Enterprise) Data Warehouse Layer:
The Corporate Layer

SAP Business Information Warehouse and

the Corporate Information Factory (CIF)*
Data Primary Data
Acquisition Data Deliver
Staging Cleansing Management
Area Transform
Data Architected
Warehouse Data Marts
E xtracti on / Open St agi ng

Master
Reference

Open D is tribu ti on
Data
Finance
any source

any target
Transaction
Data

The resultLogistic
of the data transformation
Operational and cleansing process is stored
Data persistently:
Store „ Subject oriented
„ Integrated
„ Granular
„ Non volatile (historical)
* Source: Bill Inmon
© SAP AG 2004, Enterprise Wide BW, J. Haupt / 20 „ Not scope-specific (not flavored)
 The BW (Enterprise) Data Warehouse Layer
The Corporate Layer – What can we expect?
Reliability, Trace back – Prevent Silos
„ ‘Single point of truth’
„ All data have to pass this layer on it’s path from the source to the summarized
edw-managed data marts

Controlled Extraction and Data Staging (transformation,

cleansing)
„ Data are extracted only once and deployed many
„ Merging data that are commonly used together

Flexibility, Reusability, Completeness

„ The data are not manipulated to please specific project scopes (unflavored)
„ Coverage of unexpected ad hoc requirements (Support the Unknown)
„ The data are not aggregated
„ Old versions are not overwritten or changed but useful information may be added

Integration
„ Data are integrated (as far as possible)
„ Realization of the corporate data integration strategy
...

The BW Data Warehouse Layer is the corporate memory, the

corporate information repository
© SAP AG 2004, Enterprise Wide BW, J. Haupt / 21
 Introducing the BW Data Warehouse Layer

Ownership
Corporate Guidelines must be defined
and administrators must be established Web templates,
to achieve the goals of a Data Reports

Project Team
Warehouse layer Queries
Business Logic

1 2 Data Marts
(InfoCubes)

Set up Business Logic

Incremental set up in parallel
with data marts guarantees 1 2
buy in from business users (E)DW Layer

Admin Team
1 1 (ODS-
(ODS-Objects)

(E)DW
Technology Staging-
Transformation,
„
„
BW ODS-Objects
Expanded InfoSources
1 1 Cleansing
define ODS-Object Extraction
structures
„ BW flexible staging for Sources
Master Data
1 Increment

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 22

 BW and Operational Decision-Making

SAP Business Information Warehouse and

the Corporate Information Factory (CIF)*
Data Primary Data
Acquisition Data Deliver
Staging Cleansing Management
Area Transform
Data Architected
Warehouse Data Marts
E xtracti on / Open St agi ng

Master
Reference

Open D is tribu ti on
Data
Finance
any source

any target
Transaction
Data

Logistic

Operational
Data
Store

* Source: Bill Inmon

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 23
 Operational, Tactical and Strategic Decision-Making in
‘Traditional’ BW Implementations

Most BW customers do not distinguish between strategic/

tactical and operational decision-making using BW features:
‰ Precalculated aggregates of InfoCubes (aggregation awareness)
‰ ‘Drill thru’

BW Architected Data Marts

tactical/ strategic
on
summarized data:
Data Marts

operational
ODS-Object
on detailed, slightly
summarized data:
Standard Collections
InfoCube with Two InfoCubes InfoCube and
precalculated with ‘Drill Thru’ ODS-Object
aggregates with ‘Drill Thru’

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 24

 Flexibility of BW Architected Data Marts:
Data Marts & Standard Collections
Focus of traditional
BW implementations:

support data mart tactical / strategic

the known scenarios decision-making
• InfoCubes
• summarized

operational
standard collections decision-making,
•detailed, slightly summarized
• InfoCubes, ODS-Objects flexibility
support
the unknown edw base tables flexibility &
• granular reliability
• complete history
• ODS-Objects

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 25

 Limits of Using BW the Traditional Way:
Introducing BW Operational Data Stores
The traditional usage of BW (with or without dwh-layer), which supports all
kinds of decision-making using Architected Data Marts has its limits
z If we want to provide event-level or close to event-level operational
reporting (‘near real time data warehousing’) and/ or
z If we are confronted with high data volumes (e.g. Retail)

BW
Operational Data Marts Dedicated ODS-Objects (or
I nf oCub e
Data Store G ranu l arity > X InfoCubes) with granular data
I nf oCub e
support operational decision making
d aily-w eek l y…
z Directly loaded from PSA
OD S- DWH
Ob j ect
DWH z Short life cycle of data
OD S-
Ob j ect (ÎArchiving, Near line Storage)
G ranu l arity X G ranu l arity >=X
z They build a BW Operational Data
Store
P SA G ranu l arity X

s ev er al -> ev ent l oad s

Sou rce G ranu l arity X

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 26

 Abstract Layer Architecture and the Reality of BW as ‚Packaged
Solution‘

Focus of traditional
BW implementations:

data mart tactical / strategic

support
scenarios decision-making
the known
• InfoCubes
• summarized
operational
standard collections decision-making
•detailed, slightly summarized & flexibility
• InfoCubes, ODS-Objects
support
edw (base tables) flexibility,
the unknown
• granular reliability &
• complete history
• ODS-Objects data mining

support Operational Data Stores operational

low latency & • BW ods / BW PIPE for retail decision-making
• others
high volume • most granular & data mining
© SAP AG 2004, Enterprise Wide BW, J. Haupt / 27
 Content

Content

ƒ Enterprise Wide BW - Background

ƒ Elements of a Corporate BW Strategy
ƒ The BW Data Model Prevents Silos
ƒ BW Data Layers Guarantee Reliability and Flexibility
ƒ BW Corporate Landscape Patterns

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 28

 Enterprise Data Warehouse as ‘Single Point of Truth’

DSS Applications
The Corporate Departmental Data Marts
Acctg Finance
Information Factory* Marketing Sales
ERP
ERP
ERP
CRM
ETL

Staging Area
Changed
eComm.
Data
EDW Bus. Int.

Exploration
Global warehouse/
ODS data mining
ERP
Corporate Oper.
Applications
Mart Cross media
local Granularity
ODS Manager Storage Management
Session Near line
Analysis
Storage
Dialogue
Manager
Cookie Archives
Cognition Web Logs
Preformatted
Internet dialogues * Source: Bill Inmon
© SAP AG 2004, Enterprise Wide BW, J. Haupt / 29
 Basic Landscape Types

The ideal corporate BW landscape that supports all kind

of decision-making needs ?

Hub & Spoke Others Others Outside-IN

BW Enterprise Multiple Hubs &
Data Warehouse Spoke Global BW
‘Local’
BW BW
Enterprise
Spoke Global
BW ‘Local’
BW BW
BW
Spoke
‘Local’
BW
BW

Select the [IT] approach that fits most closely with corporate
“ strategy Prof. Sethi, University of Texas
Information&Management, 2/01

There is no ‘one size fits all’ BW landscape!

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 30

 Some Influencers of a Corporate BW Landscape

z More and more operational, low-latency decision-making using BW

operational tactical/ strategic

decision making decision making

operational edw &

BW Objects edw managed
data marts

z Mission critical BW applications in BW

business critical mission critical

applications applications

z Local interests
local freedom central governance

z Flexibility for time of migration and future acquisitions

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 31

 Single Corporate Wide BW Instance

Parameters
z Company time zones
z Mission critical dominates others
z Workload from operational reporting External Data Marts
z Scalability
PSA BW
Architected Data Marts
Standard Data
Collections Marts
latency: >= 1 day

Staging Area
BW EDW
• mission critical
• business critical
• others

BW ODS
latency: near real time
• mission critical
• business critical

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 32

 Handling Mission Critical and Operative Decision-Making
Separately

Parameters
• mission critical • business critical
z Company time zones • others
• strategic
z Mission critical dominates
EDW
BW EDW
z Migration path from single

BW ODS
BW ODS
Instance
z EDW separated from
majority of data marts
Parameters
z Company time zones • mission critical • business critical
• strategic • others
z EDW close to majority of
data marts
BW EDW

BW ODS

BW ODS
© SAP AG 2004, Enterprise Wide BW, J. Haupt / 33
 Multiple Central Managed Local BWs to Support
Business Critical Scenarios

Asia Europe Americas

Local BW Local BW Local BW

• business critical • business critical • business critical

• others • others • others

ODS

ODS
ODS
Global BW
Parameters • mission critical
z Scalable • strategic
z Mission critical dominates
EDW EDW

z EDW separated from ODS

majority of data marts

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 34

 Summary

BW offers a wide range of features that support

enterprise wide data warehousing needs.

Nevertheless a strategy and an organizational momentum

must exist to realize an enterprise wide BW strategy.

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 35

 Questions

Any
Questions?

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 36

 Further Information

Î Public Web:
www.sap.com > Solutions > SAP NetWeaver

Î SAPNet:
Use ALIAS: /BW

Î SAP Service Marketplace:

www.service.sap.com/bw
z BW InfoIndex – Data Modelling
z BW InfoIndex – Enterprise Data Warehousing
z BW InfoIndex – ODS Functions
z EDW Whitepaper :
http://service.sap.com/~sapidb/011000358700003703
852003E/EnterpriseDWOverviewEN.pdf
www.service.sap.com/education
z PDEBW1 ‘Enterprise Wide Data Warehousing with
SAP BW’ (Workshop - 2 days)
© SAP AG 2004, Enterprise Wide BW, J. Haupt / 37
 Copyright 2004 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of
Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries,
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic
ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix
product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other
product and service names mentioned are trademarks of their respective companies.

© SAP AG 2004, Enterprise Wide BW, J. Haupt / 38