Enterprise Wide Data Warehousing with SAP BW. SAP NetWeaver Regional Implementation Group -BI SAP AG

Size: px

Start display at page:

Download "Enterprise Wide Data Warehousing with SAP BW. SAP NetWeaver Regional Implementation Group -BI SAP AG"

Clara Tate
6 years ago
Views:

1 Enterprise Wide Warehousing with SAP SAP NetWeaver Regional Implementation Group -BI SAP AG

Layers Guarantee Reliability and Flexibility Corporate

2 Content Content Enterprise Wide - Background Elements of a Corporate Strategy The Model Prevents Silos Layers Guarantee Reliability and Flexibility Corporate Landscape Patterns SAP AG 2004, Enterprise Wide, J. Haupt / 2

3 Enterprise Wide Background Continuously increasing number of installations Steady growth and coverage of installations High degree of customer-satisfaction with Broad analyst acceptance of and the packaged solution approach In general a renaissance of data warehousing Introduce an enterprise wide Strategy and Guidelines that guarantees : Flexibility Reliability at low costs What offers to help you realizing an enterprise Warehouse Strategy? What are the elements of an enterprise Strategy? SAP AG 2004, Enterprise Wide, J. Haupt / 3

4 Enterprise Perspective on Enterprise perspective on : Higher level organizational units want to harmonize the lower level initiatives Architecture-based implementation from the very beginning Stabilize a mature landscape (Overhaul the architecture) Division A Division A Division B Division B Group Group Division C Division C Division D Division D Retail Retail Business Business Marketing Marketing Europe Europe Americas Americas Asia/ Asia/ Pacific Pacific Germany Germany Spain Spain UK UK France France Nordic Nordic SAP AG 2004, Enterprise Wide, J. Haupt / 4

5 Multiple Implementations Challenges Source Source Local Source Unit 1 Unit 2 Stream C Consistency issues: Uncontrolled data flows Source Source Multiple extractions of same data Costly development Local Not aligned data models Danger of high level Silos Group Stream A Local Source Source Local Source Local Source Stream B Source Source Successful Warehousing means: controlled redundancy! SAP AG 2004, Enterprise Wide, J. Haupt / 5

Local Implementation Challenges Observations: Incremental set up Solution-Focus ( Marts) Departmental view Project is responsible for the entire Warehouse Process Potential consequences: Departmental

6 Local Implementation Challenges Observations: Incremental set up Solution-Focus ( Marts) Departmental view Project is responsible for the entire Warehouse Process Potential consequences: Departmental islands (silos) Consistency problems Completeness not sufficient Flexibility restricted Trace back not possible... Project Team Real World Information requirements Schema- Modeling Marts- InfoCubes Business Rules Transformation Extraction Sources Successful Warehousing means: controlled redundancy! SAP AG 2004, Enterprise Wide, J. Haupt / 6

7 Corporate Warehousing Strategy Missing corporate strategy and guidelines Means: Uncontrolled Redundancy Limited Solution Focus Potential consequences: Silo solutions Doubtful reliability 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, J. Haupt / 7

8 Who needs a Corporate Strategy? All, but the prerequisites are different! Group Headquarter Region A Region B Region C countries Organization, Business Stream A Stream B Stream C Stream D... Retail Business Marketing... Regions/ countries Necessity of a corporate Strategy Architecture-, SAP-based, single Instance OLTP landscape Legacy Legacy R/3 Legacy Legacy Legacy R/3 SAP AG 2004, Enterprise Wide, J. Haupt / 8

9 Content Content Enterprise Wide - Background Elements of a Corporate Strategy The Model Prevents Silos Layers Guarantee Reliability and Flexibility Corporate Landscape Patterns SAP AG 2004, Enterprise Wide, J. Haupt / 9

Elements of a Corporate Strategy Think of: Building a Corporate Information Factory * - Avoid Silos Enterprise Warehousing Decision Areas Architecture Application Development Integration Strategy

10 Elements of a Corporate Strategy Think of: Building a Corporate Information Factory * - Avoid Silos Enterprise Warehousing Decision Areas Architecture Application Development Integration Strategy Support Layer Model Landscape Operational Decision-Making Tactical/ Strategic Decision-Making *The Corporate Information Factory: introduced by Inmon, Imhoff SAP AG 2004, Enterprise Wide, J. Haupt / 10

11 The Role of a Consistent Warehouse Model Inconsistent Warehouse Models Island-solutions (silos, stovepipes) Consistent Warehouse Model long term success?? A challenge for Warehouse consistency Material Management OLTP Sales OLTP Not aligned operational Models HR OLTP Consistent corporate Model SAP AG 2004, Enterprise Wide, J. Haupt / 11

12 The Warehouse Model offers as part of the Business Content a predefined expandable Warehouse Model Warehouse Model for SAP und other applications (InfoObjects & InfoSources) Consistent mapping of operative data models For all SAP applications For SAP industrial solutions (e.g. Retail, Utilities..) For non SAP application Ascential Partnership Siebel, Oracle... SAP Corporate Model Legacy Models SAP AG 2004, Enterprise Wide, J. Haupt / 12

13 Extended Star Schema built on the Model 0CUSTOMER 00CUSTGR... 0MATERIAL 0MATGR 0MATTYPE... 0SALESPERS 0SALESORG... 0CUSTOMER 0MATERIAL 0AMOUNT InfoObject Master : Shared/ Conformed Dimensions Extended Star Schemas built on Model InfoCube: scope-specific BCT InfoSources Subject Areas 0MATERIAL 0MATGR 0MATTYPE Master 0DOCNO 0CUSTOMER 0SALESPERS 0MATERIAL 0AMOUNT Model defined by Business Content Transaction BCT Extractors/ Sources MaterialType Materialgroup Sales ORG Customer Material Sales Person Corporate Model: SAP Components Sales Transaction SAP AG 2004, Enterprise Wide, J. Haupt / 13

14 Extended Star Schemas Prevent Silos Local Part of Material Dimension Material_Dimension_ID SalesOrg_Dimension_ID Time_Dimension_ID Customer_Dimension_ID Sales Amount Quantity FACT Table Material_Dimension_ID 0MATERIAL Material Dimension Table InfoCube A Conformed, Shared Part of Material Dimension Material Master Table Bezirk 1 0MATERIAL Material Type Material Text Table 0MATERIAL Language Code Material Name Material Hierarchy Table Region 1 Bezirk 2 Vertriebsorganisation Region 2 Bezirk 3 Gebiet 1 Gebiet 2 Gebiet 3 Gebiet 3a Gebiet 4 Gebiet 5 Gebiet 6 Gebiet 7 Gebiet 8 Material Dimension: local & conformed part Material_Dimension_ID 0MATERIAL 0PROD_HIER Material Dimension Table InfoCube B Local Part of Material Dimension Material_Dimension_ID..._Dimension_ID...Dimension_ID...Dimension_ID Key figure 1 Key figure 2 FACT Table Conformed dimensions enable virtual MultiProvider scenarios Bezirk 4 Region 3 Bezirk 5 SAP AG 2004, Enterprise Wide, J. Haupt / 14

15 DWH Model and Enterprise Wide The Warehouse Model is the glue, which ties everything together! It protects against silos ( stove pipe solutions, islands ) Within a Instance Within a Landscape It is the basis for communication Drill Thru between solution structures (InfoCubes, ODS-Objects) within a Instance within distributed Instances Drill Thru between solution structures and SAP applications Between people Enterprise Strategy: Usage of delivered DWH data model whenever possible Central controlled guidelines for modifications and expansions SAP AG 2004, Enterprise Wide, J. Haupt / 15

16 Content Content Enterprise Wide - Background Elements of a Corporate Strategy The Model Prevents Silos Layers Guarantee Reliability and Flexibility Corporate Landscape Patterns SAP AG 2004, Enterprise Wide, J. Haupt / 16

Introducing a Layer Architecture to Guarantee Reliability and Flexibility SAP Business Information Warehouse and the Corporate Information Factory (CIF)* Acquisition Staging Area Cleansing Transform

17 Introducing a Layer Architecture to Guarantee Reliability and Flexibility SAP Business Information Warehouse and the Corporate Information Factory (CIF)* Acquisition Staging Area Cleansing Transform Primary Management Warehouse Delivery Architected Marts any source E xtracti on / Open Staging * Source: Bill Inmon SAP AG 2004, Enterprise Wide, J. Haupt / 17 Operational Store Master Reference Transaction Finance Logistic Open D is tribu ti on any target The Mart is customized and/or summarized data derived from the data warehouse

18 Architected Mart Layer: The Departmental Layer What can we expect? 0CUSTOMER master 0CUSTOMER InfoCube A 0CUSTOMER InfoCube B 0CUSTOMER InfoCube C Extended Star Schema: InfoCubes InfoObject Master ( conformed dimensions ) 0MATERIAL 0MATERIAL 0MATERIAL master The Mart Layer based on the Model and a proper Project Method offers Consistency within the Marts (InfoCubes, ODS-Objekte) Control of data redundancy (MultiProvider, Queries) All desired historical views... SAP AG 2004, Enterprise Wide, J. Haupt / 18

19 Architected Mart Layer: The Departmental Layer Corporate Needs? It is not the task of the scope-oriented 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 Flexibility, Completeness Reliability, Consistency if we concentrate ourselves just on Marts. Warehouse Layer the corporate layer SAP AG 2004, Enterprise Wide, J. Haupt / 19

20 The (Enterprise) Warehouse Layer: The Corporate Layer SAP Business Information Warehouse and the Corporate Information Factory (CIF)* Acquisition Staging Area Cleansing Transform Primary Management Warehouse Deliver Architected Marts any source E xtracti on / Open Staging SAP AG 2004, Enterprise Wide, J. Haupt / 20 Operational Store Master Reference Transaction Finance Logistic Open D is tribu ti on any target The result of the data transformation and cleansing process is stored persistently: Subject oriented Integrated Granular Non volatile (historical) * Source: Bill Inmon Not scope-specific (not flavored)

21 The (Enterprise) 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 Staging (transformation, cleansing) 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 are integrated (as far as possible) Realization of the corporate data integration strategy... The Warehouse Layer is the corporate memory, the corporate information repository SAP AG 2004, Enterprise Wide, J. Haupt / 21

22 Introducing the Warehouse Layer Ownership Corporate Guidelines must be defined and administrators must be established to achieve the goals of a Warehouse layer Set up Incremental set up in parallel with data marts guarantees buy in from business users Technology ODS-Objects Expanded InfoSources define ODS-Object structures flexible staging for Master Project Team (E)DW Admin Team Web templates, Reports Queries Business Logic Marts (InfoCubes) Business Logic (E)DW Layer (ODS-Objects) Objects) Staging- Transformation, Cleansing Extraction Sources 1 Increment SAP AG 2004, Enterprise Wide, J. Haupt / 22

23 and Operational Decision-Making SAP Business Information Warehouse and the Corporate Information Factory (CIF)* Acquisition Staging Area Cleansing Transform Primary Management Warehouse Deliver Architected Marts any source E xtracti on / Open Staging Operational Store Master Reference Transaction Finance Logistic Open D is tribu ti on any target * Source: Bill Inmon SAP AG 2004, Enterprise Wide, J. Haupt / 23

24 Operational, Tactical and Strategic Decision-Making in Traditional Implementations Most customers do not distinguish between strategic/ tactical and operational decision-making using features: Precalculated aggregates of InfoCubes (aggregation awareness) Drill thru Marts operational on detailed, slightly summarized data: ODS-Object Standard Collections InfoCube with precalculated aggregates SAP AG 2004, Enterprise Wide, J. Haupt / 24 Two InfoCubes with Drill Thru InfoCube and ODS-Object with Drill Thru Architected Marts tactical/ strategic on summarized data:

25 Flexibility of Architected Marts: Marts & Standard Collections Focus of traditional implementations: support the known support the unknown data mart scenarios InfoCubes summarized standard collections detailed, slightly summarized InfoCubes, ODS-Objects edw base tables granular complete history ODS-Objects tactical / strategic decision-making operational decision-making, flexibility flexibility & reliability SAP AG 2004, Enterprise Wide, J. Haupt / 25

Limits of Using the Traditional Way: Introducing Operational Stores The traditional usage of (with or without dwh-layer), which supports all kinds of decision-making using Architected Marts has its

26 Limits of Using the Traditional Way: Introducing Operational Stores The traditional usage of (with or without dwh-layer), which supports all kinds of decision-making using Architected Marts has its limits If we want to provide event-level or close to event-level operational reporting ( near real time data warehousing ) and/ or If we are confronted with high data volumes (e.g. Retail) Operational Store InfoCub e Granul arity X OD S- Obj ect PSA InfoCub e DWH OD S- Obj ect several -> event loads d aily-w eekly Marts Granul arity > X DWH Granul arity >=X Granul arity X Dedicated ODS-Objects (or InfoCubes) with granular data support operational decision making Directly loaded from PSA Short life cycle of data ( Archiving, Near line Storage) They build a Operational Store Sou rce Granul arity X SAP AG 2004, Enterprise Wide, J. Haupt / 26

27 Abstract Layer Architecture and the Reality of as Packaged Solution Focus of traditional implementations: support the known support the unknown support low latency & high volume data mart scenarios InfoCubes summarized standard collections detailed, slightly summarized InfoCubes, ODS-Objects edw (base tables) granular complete history ODS-Objects Operational Stores ods / PIPE for retail others most granular tactical / strategic decision-making operational decision-making & flexibility flexibility, reliability & data mining operational decision-making & data mining SAP AG 2004, Enterprise Wide, J. Haupt / 27

28 Content Content Enterprise Wide - Background Elements of a Corporate Strategy The Model Prevents Silos Layers Guarantee Reliability and Flexibility Corporate Landscape Patterns SAP AG 2004, Enterprise Wide, J. Haupt / 28

29 Enterprise Warehouse as Single Point of Truth The Corporate Information Factory* Departmental Marts Acctg Finance Marketing Sales DSS Applications ERP ERP ERP ETL CRM Changed Staging Area EDW ecomm. Bus. Int. ERP Corporate Applications local ODS Global ODS Oper. Mart Granularity Manager Exploration warehouse/ data mining Cross media Storage Management Session Analysis Near line Storage Internet Dialogue Manager Cookie Cognition Preformatted dialogues Web Logs Archives * Source: Bill Inmon SAP AG 2004, Enterprise Wide, J. Haupt / 29

30 Basic Landscape Types The ideal corporate landscape that supports all kind of decision-making needs? Hub & Spoke Enterprise Warehouse Enterprise Others Spoke Spoke Spoke Others Local Local Local Outside-IN Multiple Hubs & Global Global 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 landscape! SAP AG 2004, Enterprise Wide, J. Haupt / 30

31 Some Influencers of a Corporate Landscape More and more operational, low-latency decision-making using operational decision making tactical/ strategic decision making operational Objects edw & edw managed data marts Mission critical applications in business critical applications mission critical applications Local interests local freedom central governance Flexibility for time of migration and future acquisitions SAP AG 2004, Enterprise Wide, J. Haupt / 31

32 Single Corporate Wide Instance Parameters Company time zones Mission critical dominates others Workload from operational reporting Scalability PSA Staging Area EDW External Marts Architected Marts Standard Collections Marts latency: >= 1 day mission critical business critical others ODS latency: near real time mission critical business critical SAP AG 2004, Enterprise Wide, J. Haupt / 32

33 Handling Mission Critical and Operative Decision-Making Separately Parameters Company time zones Mission critical dominates EDW Migration path from single Instance EDW separated from majority of data marts Parameters Company time zones EDW close to majority of data marts ODS mission critical strategic EDW mission critical strategic ODS ODS business critical others business critical others EDW ODS SAP AG 2004, Enterprise Wide, J. Haupt / 33

34 Multiple Central Managed Local s to Support Business Critical Scenarios Asia Europe Americas Local Local Local business critical others business critical others business critical others ODS ODS ODS Parameters Scalable Mission critical dominates EDW EDW separated from majority of data marts Global mission critical strategic EDW ODS SAP AG 2004, Enterprise Wide, J. Haupt / 34

35 Summary 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 strategy. SAP AG 2004, Enterprise Wide, J. Haupt / 35

36 Questions Any Questions? SAP AG 2004, Enterprise Wide, J. Haupt / 36

Further Information Public Web: www.sap.com > Solutions > SAP NetWeaver SAPNet: Use ALIAS: / SAP Service Marketplace: www.service.sap.com/bw InfoIndex Modelling InfoIndex Enterprise Warehousing InfoIndex ODS Functions EDW Whitepaper : http://service.

37 Further Information Public Web: > Solutions > SAP NetWeaver SAPNet: Use ALIAS: / SAP Service Marketplace: InfoIndex Modelling InfoIndex Enterprise Warehousing InfoIndex ODS Functions EDW Whitepaper : E/EnterpriseDWOverviewEN.pdf PDE1 Enterprise Wide Warehousing with SAP (Workshop - 2 days) SAP AG 2004, Enterprise Wide, J. Haupt / 37

38 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 base, 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, J. Haupt / 38

SAP BW in a Growing Landscape - Increasing the Benefit of Your BW Implementation - SAP NetWeaver Regional Implementation Group -BI SAP AG

SAP BW in a Growing Landscape - Increasing the Benefit of Your BW Implementation - SAP NetWeaver Regional Implementation Group -BI SAP AG SAP in a Growing Landscape - Increasing the Benefit of Your Implementation - SAP NetWeaver Regional Implementation Group -BI SAP AG Content Overview Content Extend the Reach of Integrate new Non-SAP data