SAP Business Information Warehouse-Based Enterprise Data Warehouse - More Than a Vision Jürgen Haupt SAP NetWeaver RIG, SAP AG SAP AG 2003, BW254, Jürgen Haupt/ 2 Learning Objectives As a result of this workshop, you will be able to: Understand basic architecture aspects of a corporate BW implementation approach See the basic differences between a Data Mart driven BW implementation and a BW implementation based on a enterprise data warehousing strategy Examine an existing BW Landscape from a corporate point of view
38
Embed
SAP Business Information Warehouse-Based Enterprise Data Warehouse … · 2019-11-12 · SAP Business Information Warehouse Staging Area Cleansing Transform Master Reference Data
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
SAP Business Information Warehouse-BasedEnterprise Data Warehouse- More Than a Vision
Jürgen HauptSAP NetWeaver RIG, SAP AG
SAP AG 2003, BW254, Jürgen Haupt/ 2
Learning Objectives
As a result of this workshop, you will be able to:
Understand basic architecture aspects of a corporate BW implementation approachSee the basic differences between a Data Mart driven BW implementation and a BW implementation based on a enterprise data warehousing strategyExamine an existing BW Landscape from a corporate point of view
Successful Data Warehousing means ‘Controlled Redundancy’ !Successful Data Warehousing means ‘Controlled Redundancy’ !Successful Data Warehousing means ‘Controlled Redundancy’ !
Successful Data Warehousing means ‘Controlled Redundancy’ !Successful Data Warehousing means ‘Controlled Redundancy’ !Successful Data Warehousing means ‘Controlled Redundancy’ !
A Real Life
BW Landscape ExampleImpacts of non-existing corporate BW guidelines:
•Redundant Data Flows•Redundant Extraction•Redundant Development•Redundant Models•......
It is not the task of the scope oriented Data Mart Layer to anticipate any kind offuture arising needs – this would overload the schemas and corrupt performanceIt cannot be expected that the data mart project teams have the 360° corporate view
to guarantee:extract once deploy manycontrolled redundancysingle point of truthflexible structures
Make the result of the data transformation and cleansing process persistentin a way that is:
Customer Activ From CustomerGroupA 20020101 X after 2nd LoadA 20020401 Y
Customer CustomerGroupA X 1st Load: 20020101A Y 2nd Load: 20020401
InfoObject Master Data Table
DWH ODS-Object
SAP AG 2003, BW254, Jürgen Haupt/ 24
Data Processing in the BW DWH Layer
DWH layer data processing means:
All data has to pass this layer on it’s path from the source to the Architected Data Marts
The data is not aggregated.
The data is not manipulated to please specific project scopes
Old versions are not overwritten or changed but useful information may be added
Data is integrated as far as possible
The data is normally not the primary target for reporting and analysis
Data is extracted only once and deployed many
Define BW Data Warehouse Layer General GuidelinesCorporate Guidelines must be set up and an administrator must beestablished to achieve benefits from a BW Data Warehouse layer.
Create new analysis data marts without extracting data once againA potential fall back line to cover single time unexpected end-user needs (kind of basic ad hoc reporting/ analysis)
Reliability, Audit Trail A Single Point of Truth All data from the source systems have to path this layer on their way to the end-user
Complete History/ Versions
Consistency, Controlled RedundancyData is extracted only once and deployed many timesRedundant staging processes are avoidedRealization of the corporate integration strategy is not a matterof a departmental project team
Integrationsemanticalcommon coding
The BW Data Warehouse Layer is the corporate memory, thecorporate information repository
SAP AG 2003, BW254, Jürgen Haupt/ 26
Vertical Consistency
Real World
InformationRequirements
(grouped to Scopes)
Modelling
InfoCubes
EDW
Extraction
Sources
Business Rules
Transformation
BW Application Project Team
EDW
Admin
Team
• Controlled Redundancy• Extract once – Deploy many• Single Point of Truth
• Controlled Redundancy• Extract once – Deploy many• Single Point of Truth
If BW Data Warehouse layer functionality is established at corporate level you can think of the BW Data Warehouse
as your corporate memory,
your corporation’s information repository.
This is the reason that this layer is often called the
Enterprise Data Warehouse.
SAP AG 2003, BW254, Jürgen Haupt/ 28
BW Persistent Staging Area (PSA)
StagingStagingArea:Area:PSAPSA
CleansingCleansingTransformTransform
BW Data BW Data WarehouseWarehouse
Extra
ctio
n /
Ope
n St
agin
g
BW ODSBW ODSany
sour
ce
Makes a BW DWH Layer the PSA obsolete?
The answer is : just partly
1. Backup for ‘non-mature’ applications2. Uncouple extraction from BW
processing
Best Practice: Reduce Space Requirements Introducing a PSA Lifecycle Concept
The role of the PSA as backup is limited if a BW Data Warehouse layer is used. For backup purposes of mature applications, the PSA is no longer needed. Thus, PSA-element entries could be deleted normally after 2 to 4 weeks. Not deleting the entries may lead after short time to significant disk space usage
Near Real Time Data Warehousing (BW Vers. 4) –BW Operational Data Store
Finance
Logistic Ope
n D
istri
butio
n
SAP Business Information WarehouseSAP Business Information Warehouse
StagingStagingAreaArea
CleansingCleansingTransformTransform
MasterReference
Data
Data Data WarehouseWarehouse
ODSODS
PrimaryPrimaryData Data
ManagementManagement
Extra
ctio
n /
Ope
n St
agin
gDataData
AcquisitionAcquisitionData Data
DeliveryDelivery
any
targ
et
Ext
ende
d St
ar S
chem
asE
xten
ded
Star
Sch
emas
Flow Control Flow Control
MetaMeta DataData
any
sour
ce TransactionData
ArchitectedArchitectedData MartsData Marts
SAP AG 2003, BW254, Jürgen Haupt/ 30
A Matter of Information Perspective –Classic Data Warehousing and Operational Reporting
An information perspective can be classified by4 Granularity 4 Historical background 4 Latency or Load Frequency 4 Reliability (Auditing)4 Target group 4 Information Retrieval Behavior
Information Perspective:Strategic – Tactical - Operational
Be careful using the same InfoCube for operational and tactical reporting:if the transactional volume is highif you want to report on atomic data
last load
1 year old data
2 years old data
1/2 year old data
day
wee
k
mon
thqu
arte
rye
argranularity
tactical/ strategic
tactical/ strategichistory
notnotusedused
operational
operational
Granularity X
Granularity X
Granularity X
Source
PSA
DWHODS-Object
InfoCube
1:1
1:1
most atomicGranularity X
SAP AG 2003, BW254, Jürgen Haupt/ 34
Operational Reporting and Classic DWH – Issues II
Solution A:
Granularity X
Granularity X
Granularity < X
Source
PSA
DWHODS-Object
InfoCube
1:1
Aggregation
most atomicGranularity X
Operational reporting could be done on the DWH-ODS-Object if just list reporting is desired.Tactical reporting is done on the InfoCube, which keeps aggregated dataDrill thru from InfoCube to atomic DWH-ODS-Objectis possible
Issues:• Responsibility ?• DWH-ODS-Object must be reporting enabled• Remember the guidelines for the BW DWH Layer
BW Enterprise Data Warehouse:BW Data Warehouse layer as ‘single point of truth’ for the entire corporation
EnterpriseBW
BW EnterpriseBW EnterpriseDataData
WarehouseWarehouseScenarioScenario
SpokeBW
SpokeBW
SAP AG 2003, BW254, Jürgen Haupt/ 52
EDW Patterns
Organization is centralizedHeadquarter or division headquarter or even regional divisionheadquarter oriented companies
Often a single line of businessMaster data integration exist or at least a strategy to achieve itAwareness of the important role of Consistent Information is high
i.e. bad experience led to the conclusion that a data warehouse is more than a sexy front-end
‘Simply building a central single data warehouse does not address the size and complexity of the problem posed by the need for integrated, historical easily accessible data across a complex global enterprise.’W.H. Inmon ‘Managing Multiple Data Warehouse Development‘
‘Simply building a central single data warehouse does not address the size and complexity of the problem posed by the need for integrated, historical easily accessible data across a complex global enterprise.’W.H. Inmon ‘Managing Multiple Data Warehouse Development‘
SAP AG 2003, BW254, Jürgen Haupt/ 56
Corporate Data Warehouse Landscape based on BW Local and Global Data Warehouses
Enterprise Data Warehousing BasicsControlled Redundancy
BW Architecture AspectsData Layer Data ModelLandscape
Further Aspects of a Corporate BW StrategyApplication Development Data Integration
Exercise
Discussion
Summary
SAP AG 2003, BW254, Jürgen Haupt/ 64
Master Data and Integration
0MATERIAL 0MATTYPE4711 A4712 B4713 A123 B124 B
MATNR MATTYPE MATNR MATTYPE MATNR MATTYPE4711 A 123 B 4711 C4712 B 124 B
0MATERIAL Master Data Table
R/3 system 1 -data already integrated
R/3 system 2 -data already integrated
R/3 system 3 -data not integrated but
mapping exist
apply mapping:MATNR: 4711 -> 4713MATTYPE: C -> A
The ideal world that anticipates the source systems either offer already integrated master data or that the master data can be mapped to common coded values during staging.
A major deliverable of data warehousing is integrated data regardless whether we talk about Architected Data Marts, ODS or the Data Warehouse layer itself.
Entity values from source systems are not integrated and cannot be mapped atload time to common coded values
The most common reason is the lack of a corporate master data strategyOnly a delayed integration is possible i.e. at load time integrated values are not available until after a certain time spanDue to mergers and acquisitions new, not harmonized (common coded) sources
may appear
Best Practice: Discuss the Status and Strategy of Corporate Common Coding Efforts
The strategy and the status of corporate master data common coding shouldbe discussed at an early stage because of the huge influence to the BW information model and thus all scope implementations.
Checking InfoObject Integration Status
InfoObject Common Coded at Source Sites?
Integration in BW possible at load
time?0MATERIAL PARTLY NO0CUSTOMER NO NO0MATTYPE NO YES0COSTCENTER YES NO ACTION
Please complete your session evaluation anddrop it in the box on your way out.
Feedback
Thank You !
The SAP TechEd ’03 Basel Team
SAP AG 2003, BW254, Jürgen Haupt/ 76
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, R/3, mySAP, mySAP.com, xApps, xApp and other SAP products and services mentioned herein as well astheir 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 the trademarks of their respective companies.