SAP Business Information Warehouse and SAP Master Data Management acting together
|
|
- Chester Fitzgerald
- 8 years ago
- Views:
Transcription
1 SAP Business Information Warehouse and SAP Master Data Management acting together Rainer Uhle Product Manager Product Line BI, SAP AG Learning Objectives As a result of this workshop, you will be able to: Understand how Master Data handling in SAP BW is impacted by SAP MDM Define several SAP MDM scenarios and their impact on SAP BW Master Data load processes Detail the value of SAP BW Consolidated Info Objects as ideal integration points for SAP MDM. SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 2
2 Agenda Introduction Application optimization example: mysap SRM Global Spend Analysis SAP BW Scenarios for Master Data load Scenario 1 Scenario 2 Scenario 3 Summary SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 3 Agenda Introduction Application optimization example: mysap SRM Global Spend Analysis SAP BW Scenarios for Master Data load Scenario 1 Scenario 2 Scenario 3 Summary SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 4
3 Global Spend Analysis in mysap SRM Purchase Orders Invoices SAP XI Purchaser XML Copy BI Global Spend XML Suppliers Global Spend Analysis Visualize global spend across organizational boundaries Compare vendor prices Minimize contract leakage Consolidate suppliers mysap SRM reduces total spend for continuous profitability Improved sourcing strategy Compressed cycle times Reduced process costs Lower unit prices SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 5 Today s Option - Point-To-Point Connection mysap SRM 3.0: One or multiple procurement systems, one SAP Business Information Warehouse (SAP BW Content 3.2 or higher) One Content Integrator*, that relies on a mysap SRM server basis Possible: Dun & Bradstreet Supplier Analytics for SAP BW All transactional and all master data are uploaded into SAP BW directly. Connection to SAP R/3 rel. 3.1I and higher, EBP 2.0 and higher is pre-configured, other procurement systems may be connected directly to SAP BW via Ascential s Datastage Key Mapping data are uploaded from CI into SAP BW Supplier data and product categories are consolidated by the Content Integrator Supplier data may be enriched with Dun & Bradstreet EBP Non R/3 R/3 R/3 * Requires SAP Content Integrator 2.0. Expected availability with mysap SRM service pack 2 BW D&B EBP CI SUS SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 6
4 Tomorrow s Option - Hub-Based Scenario Future (beyond mysap SRM 3.0) One or multiple procurement systems One SAP Business Information Warehouse One SAP XI One SAP Master Data Management (with Content Integrator ) Possible: Dun & Bradstreet Supplier Analytics for SAP BW Purchase Orders, PO Changes and Invoices (B2B messages) are routed into SAP BW CI MDM Key Mapping data are uploaded from D&B SAP MDM/CI into SAP BW Supplier data, product Supplier XI BW and product categories are consolidated by SAP MDM Supplier data may be enriched with Dun & Bradstreet EBP EBP XML R/3 R/3 Non R/3 Non R/3 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 7 Agenda Introduction Application optimization example: mysap SRM Global Spend Analysis SAP BW Scenarios for Master Data load Scenario 1 Scenario 2 Scenario 3 Summary SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 8
5 Overview SAP BW/MDM Scenarios and Benefits An SAP Customer with a productive SAP BW Environment wants to implement SAP MDM. Scenario I Minimal involvement of SAP MDM in SAP BW Master Data extraction for operational reporting needs Scenario II Global consolidation of SAP BW Master Data via SAP MDM for strategic reporting needs in SAP BW An SAP Customer without an SAP BW Environment wants to implement SAP MDM and SAP BW Scenario III Maximized and optimized embedding of SAP MDM in the SAP BW Master Data extraction process SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 9 Scenario I An SAP BW Customer has several SAP R/3 systems as the only source for SAP BW. The SAP R/3 system landscape grew steadily historically. A recent acquisition caused a significant jump in growth. Between the SAP R/3 systems (existing and acquired), Material Management number ranges for the Entity Material (MATNR-Domain) overlap. To accommodate this situation, the corresponding meta object in SAP BW, the InfoObject 0MATERIAL has been modeled as a concatenated key consisting of the two digit source system ID and the local material number. This technique guarantees a consistent view of the local data for operational reporting needs. In this scenario, SAP MDM complements SAP BW by assisting in the consolidation of the master data of the various R/3 sources. SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 10
6 Scenario I: Productive SAP BW Environment on Rel. 3.1 Content SAP BW 0MATERIAL IS: Material Overlapping Number Ranges for for Entity Material Material Number 4711 exists in in three SAP R/3 R/3 Systems Sources R/3 Material MATNR R/3 R/3 R/3 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 11 Master Data Situation in the SAP R/3 Source Systems Source System Material Number... Short Text R/3 S Hammer (150 g) R/3 S Hammer G150 R/3 S Screw Driver S 7a R/3 S Hammer 5.25 oz ( ca. 150gr) R/3 S Hammer G 450 R/3 S Hammer G 650 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 12
7 Scenario I: Concatenate Material and Source System 0MATERIAL Text SAP BW 0MATERIAL... Hammer (150 g) 0MATERIAL S Hammer G150 S Screwdriver S 7a IS: Material S Hammer 5.25 oz ( ca. 150gr) S Hammer G 450 S Hammer G 650 Sources R/3 Material S S1 S1 S2 S2 S3 S3 R/3 R/3 R/3 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 13 SAP MDM An Incremental Approach Content Consolidation 1 2 Master Data Harmonization Content Consolidation Cleanse, normalize data Aggregate, search, and cross reference data from connected systems Duplicate finding SAP MDM supports an incremental approach to a cohesive master data management in a distributed and heterogeneous environment Examples: Business-wide analyses (e.g., global spend Analysis), Creation of central catalogs (e.g., of supplier products) 3 Central Master Data Management SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 14
8 Master Data Consolidation with SAP MDM 2.0 Scenario 1 Client SAP Client non SAP MDM Load Content Consolidation Core Process Steps: 1. Loading identifying attributes of master data objects as they were maintained in their local applications (clients) Client non SAP Client SAP Client non SAP? Matching = ID Mapping 2. Matching of uploaded master data objects to identify duplicates 3. Providing ID Mapping Information based on matching results for subsequent usage (I.e., in Business Intelligence) Description of a master data object: Identifying Attributes SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 15 Other application specific data SAP MDM Implementation Step 1 BW 0MATERIAL CI Group ID IS: Material MATERIAL System S1 S2 S3 S1 S1 S1 0MATERIAL Text Hammer (150 g) Hammer G150 Screwdriver S 7a Hammer 5.25 oz ( ca. 150gr) Hammer G 450 Hammer G 650 CI Group ID Text Hammer G150 Screwdrivers Hammer 450 Hammer 650 Sources R/3 Material S1 S1 S2 S2 S3 S3 R/3 R/3 R/3 Load Content Integrator = ID Mapping? Matching SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 16 XI XI Description of a master data object: Identifying Attributes Other application specific data MDM
9 Available CI Extractors on the SAP MDM Server The right DataSource for our purpose: Grouped Key Mapping SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 17 SAP MDM Extractor: Product Key Mapping Information Matching Process System-ID S1-S3 Object Type 0MATERIAL Material Number 47*... Group-ID???? SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 18
10 SAP BW Scenario I: SAP MDM Implementation Step 2 0Material... Group ID SAP BW S MATERIAL S IS: Material IS: MDM Product ATTR+TEXT S S Sources R/3 Material SAP MDM R/3 R/3 R/3 Load = ID Mapping? Matching SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 19 XI XI Description of a master data object: Identifying Attributes Other application specific data Result: Analytic Output (Consolidated View) Tools Article Revenue Hammer G150 Hammer 450 Hammer 650 Hammer (150 g) Hammer G150 Hammer 5.25 oz ( ca. 150gr) SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 20
11 SAP BW Scenario I: SAP MDM Implementation in SAP BW Implementation steps in SAP BW: Implement SAP MDM as a source system in SAP BW Replicate the SAP MDM DataSources into SAP BW and create InfoSources Enhance 0MATERIAL with an additional attribute for Group ID Create an UpdateRule for 0MATERIAL based on the particular SAP MDM InfoSource Load SAP MDM Content Integrator information into SAP BW master data table for 0MATERIAL Reactivate Cubes with transactional data containing 0MATERIAL Additional Aggregates for CI Group ID might be useful Existing queries provide local views. SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 21 SAP BW Scenario I - Summary Harmonization of values for a single entity (here 0MATERIAL) with a clear defined semantic. No additional MetaData necessary except the InfoObject for Group-ID (0GROUPID available with SAP BW 3.0B BCT) No SAP MDM Business Content, InfoSources and UpdateRules have to be implemented manually Transactional Data Management is not affected SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 22
12 Agenda Introduction Application optimization example: mysap SRM Global Spend Analysis SAP BW Scenarios for Master Data load Scenario 1 Scenario 2 Scenario 3 Summary SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 23 Overview SAP BW/MDM Scenarios and Benefits An SAP Customer with a productive SAP BW Environment wants to implement SAP MDM. Scenario I Minimal involvement of SAP MDM in SAP BW Master Data extraction for operational reporting needs Scenario II Global consolidation of SAP BW Master Data via SAP MDM for strategic reporting needs in SAP BW An SAP Customer without an SAP BW Environment wants to implement SAP MDM and SAP BW Scenario III Maximized and optimized embedding of SAP MDM in the SAP BW Master Data extraction process SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 24
13 Scenario II An SAP BW Customer has several productive mysap Components. The SAP R/3 system landscape grew steadily historically. A recent acquisition caused a significant jump in growth. Business Content in SAP BW was activated according to best practices for each mysap component. Because these were activated independently, no globally consolidated view of master data is immediately available. The project team has opted to use the Consolidated InfoObjects (also called Cross Application Master Data) included in their upgrade to SAP BW 3.0B to accommodate new requirements for globally consolidated views of master data from SAP R/3 and mysap CRM components. The benefit of this approach is two-fold: It guarantees a consistent view of the local data for operational reporting needs It provides a global view for strategic reporting/analysis. SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 25 Master Data Situation in the SAP MDM Clients Source System Material Number... Short Text R/3 S Hammer (150 g) R/3 S Hammer G150 R/3 S Screw Driver S 7a R/3 S Hammer 5.25 oz ( ca. 150gr) R/3 S Hammer G 450 R/3 S Hammer G 650 CRM C Hammer Trini Lopez 150 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 26
14 Scenario II: Productive SAP BW Environment on Rel. 3.1 Content SAP BW Business Content for for various business areas 0MATERIAL 0_ORA 0BBP_PROD 0CRM_PROD IS: Material IS: ORA IS: BBP Prod IS: CRM Prod Sources R/3 Material ORA Service EBP Product CRM Product R/3 R/3 R/3 Oracle R/3 R/3 R/3 R/3 EBP R/3 R/3 CRM SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 27 Cross-Application Reporting: Product Data Flow 0PRODUCT Global and consolidated views on products Independent on source system 0MATERIAL 0SERVICE 0BBP_PROD IS: Material IS: Service IS: BBP Prod 0CRM_PROD IS: CRM Prod Analytics restricted to the view of one local application system R/3 Material R/3 R/3 Service R/3 EBP Product R/3 EBP CRM Product R/3 CRM Local Application Systems with individual data models DataSources SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 28
15 Consolidated InfoObjects: Status from SAP BW 3.0A Heterogeneous Master Data in SAP BW for: Products Product Categories Business Partner (Vendor / Customer) from different software components: SAP R/3 mysap SRM (EBP, SUS) mysap CRM mysap SCM Non-SAP... represented in BW with separate InfoObjects: e.g.: 0MATERIAL 0BBP_PROD 0ORA_PROD R/3 Material EBP Product Oracle Product SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 29 Product: Data Model in SAP BW - Composite Key (I) The key of all consolidated InfoObjects is composed of: Source System Information Represented by Infoobject 0SOURSYSTEM (Char 2) Object Type Defined in BW Customizing (Char 4). Predefined values will be delivered along with Business Content e.g., 1MAT Material, 1SER Service Key of Local View Original local key from object in source system SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 30
16 0Product : Consolidated Data Model in SAP BW The Goal One Instance For Global Attributes And Key Mapping Information The Solution Model 0PRODUCT Key The Problem System CRM C1 R/3 S1 R/3 S2 R/3 S1 Source System Obj.Type 1MAT 1MAT 1MAT 1MAT 0MATERIAL Key in R/3 System Loc. Key Description Trini Lopez 150 Hammer (150 g) Hammer G150 Hammer 5.25 oz 0CRM_PROD Key in CRM system Group ID Group ID CRM C1 1MAT 5711 CRM C R/3 S1 1MAT 4711 R/3 S R/3 S2 1MAT 4711 R/3 S R/3 S1 1MAT 4712 R/3 S SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 31 SAP MDM an incremental approach Master data harmonization All of Content Consolidation 1 PLUS Consolidation Central management and distribution of global attributes Post editing in client systems Controlled distribution of local changes Examples: Business Partner administration Central provision of sales articles Definition and administration of non-variable parts 2 Master Data Harmonization SAP MDM supports an incremental approach to a cohesive master data management in a distributed and heterogeneous environment 3 Central Master Data Management SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 32
17 Master Data Consolidation with SAP MDM 2.0 Scenario 2 + Local Completion + Client SAP Client non SAP Client SAP Client non SAP MDM Local Creation Central Creation =? Matching & ID Mapping Distribution Analytics = Master data harmonization Core Process Steps: 1. Central Creation of master data objects just covering the global information of the master data object 2. Local Creation within the master data environment of the application system (client) and distributing their global information to MDM 3. Continuous matching processes identify duplicates and result in ID Mapping between them 4. Distribution of global master data information to the various clients 5. Local Completion of master data within the local environment 6. Use of ID Mapping information for MDM Analytics like business-wide analyses etc. SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 33 Description of a master data object: Globally relevant Data (Client) specific Data What does this mean to SAP BW Master Data Loads? MDS CI CI Key Mapping Information Syst. CRM C1 C1 Product 5712 Syst. R/3 R/3 S1 S1 Product 4711 Syst. R/3 R/3 S2 S2 Product 4711 Syst. R/3 R/3 S1 S1 Product 4712 Matching Process Main Matching Process Product Sec. Matching Process Product MDM-BW Extractor for Key Mapping + Attributes 4 Result Records for one Product Record CRM C1 C1 Key Mapping + Attributes R/3 R/3 S1 S1 Key Mapping + Attributes R/3 R/3 S2 S2 Key Mapping + Attributes R/3 R/3 S1 S1 Key Mapping + Attributes MDS Master Data Record Product 0815 with Attributes SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 34
18 SAP MDM Extractors for Business Partner and Product SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 35 SAP MDM Extractor: Product Key Mapping Information System R/3-S1 Product-ID 4711 Group-ID 0815 SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 36
19 Extraction Result on the SAP MDM Server Site MDC MDM MDC MDM Global IDs MDM System and Object Information SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 37 Scenario II : Extracting Global SAP MDM Data SAP BW SAP MDM 0PRODUCT IS: Global Product strategic Common Identifying Data Global master data info 0MATERIAL 0_ORA 0BBP_PROD 0CRM_PROD IS: Material IS: ORA IS: BBP Prod IS: CRM Prod operational Clients R/3 Material R/3 R/3 R/3 ORA Service Oracle R/3 R/3 EBP Product R/3 R/3 EBP CRM Product R/3 R/3 CRM XI XI Distribution = ID Mapping + + Description of a master data object: Common Identifying Data master data info SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 38
20 Product: Global Attributes Best Practices Keep the consolidated InfoObjects very lean! Only attributes used for global reporting are relevant. Don t flood them with attributes of local views! Global attributes delivered by SAP can only be Consolidated InfoObjects InfoObjects with unified or standardized values in all source systems DUNS number, UNSPSC code, e-class, ISO codes Customer can add own standardized attributes depending on his master data model. SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 39 0PRODUCT - Key Concatenation in Update Rule Business Content Filling the Product Key via concatenation SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 40
21 0PRODUCT Filling the Local Key in Update Rule SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 41 0PRODUCT Filling the Source System SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 42
22 Consolidated InfoObjects: Transactional Data Flow InfoSource Master Data ODS object Info Cube InfoSource ODS object Consolidated InfoObjects (Example: 0PRODUCT) Info Cube Master Data InfoSource ODS object Info Cube Master Data Master Data InfoSource ODS object MDM Key Mapping Information Info Cube SAP R/3 object model (namespace 0*) Example: 0MATERIAL R/3 R/3 Sources R/3 R/3 Sources mysap CRM/EBP OM (namesp. 0CRM_*, 0BBP_*) Example: 0CRM_PROD EBP/CRM Oracle OM (namesp. 0ORA_*) Example: 0ORA_PROD Oracle R/3 Sources SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 43 SAP BW Scenario II - Summary A more complex challenge Main flow of Master Data into SAP BW is still coming from client systems Consolidated InfoObjects in SAP BW available as a kind of Business Content for SAP MDM (here 0PRODUCT) No further SAP MDM Business Content available, InfoSources and UpdateRules have to be implemented manually Additional flow of Master Data information on the Consolidated InfoObject level coming from SAP MDM has to be implemented in SAP BW Complex Master Data Harmonization in SAP BW does also affect the management of transactional data SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 44
23 Agenda Introduction Application optimization example: mysap SRM Global Spend Analysis SAP BW Scenarios for Master Data load Scenario 1 Scenario 2 Scenario 3 Summary SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 45 Overview SAP BW/MDM Scenarios and Benefits An SAP Customer with a productive SAP BW Environment wants to implement SAP MDM. Scenario I Minimal involvement of SAP MDM in SAP BW Master Data extraction for operational reporting needs Scenario II Global consolidation of SAP BW Master Data via SAP MDM for strategic reporting needs in SAP BW An SAP Customer without an SAP BW Environment wants to implement SAP MDM and SAP BW Scenario III Maximized and optimized embedding of SAP MDM in the SAP BW Master Data extraction process SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 46
24 Scenario III An SAP customer has several mysap components in productive use. There is no data warehouse solution implemented so far. SAP BW/MDM are implemented in one step in order to benefit from synergy between both solutions. The main goal of the project is to reduce the data flow between SAP MDM Clients and SAP BW to just transactional data. All master data distribution has to be realized via the SAP MDM. SAP BW will extract its master data from the SAP MDM Server only. SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 47 SAP MDM An Incremental Approach 1 Central Content Master Data Consolidation Management All of Content Consolidation PLUS All of Master Data Harmonization PLUS All master data information resides centrally One stop data maintenance 2 Examples: Master Data Definition of synergy parts Harmonization Central product data pool supplying product data to multiple locations for production, assembly, sales and distribution. SAP MDM supports an incremental approach to a cohesive master data management in a distributed and heterogeneous environment 3 Central Master Data Management SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 48
25 Master Data Consolidation with SAP MDM 2.0 Scenario 3 w/o Local Maintenance Client SAP Client non SAP Client SAP MDM Central Creation Distribution = ID Mapping Analytics = Central Master Data Management Core Process Steps: 1. Central Creation of master data objects covering the complete information as used later in the local application systems (clients) 2. Distribution of centrally maintained master data information as individual objects as they are defined in the local application systems 3. Use of master data within local application processes w/o local maintenance 4. Use of ID Mapping information for MDM Analytics like business-wide analyses etc. Description of a master data object: Common Identifying Data Complete master data info SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 49 Initializing SAP BW Master Data from Central SAP MDM SAP BW SAP MDM 0PRODUCT InfoSource: Global Product mandatory Common Identifying Data Global master data info 0MATERIAL 0_ORA 0BBP_PROD 0CRM_PROD IS: Material IS: ORA IS: BBP Prod IS: CRM Prod Clients R/3 Material ORA Service EBP Product CRM Product = R/3 R/3 R/3 Oracle R/3 R/3 + R/3 R/3 EBP R/3 R/3 CRM + XI XI Distribution ID Mapping Description of a master data object: Common Identifying Data master data info SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 50
26 SAP BW Scenario III - Summary Simplified Mater Data Handling in SAP BW Entire Master Data flow is shifted from SAP MDM Clients to the SAP MDM Server Identifying global and local Master Data Attributes are provided by the SAP MDM Server to cover the needs on strategic and operational reporting level in SAP BW. Transactional data flow into BW is not affected but relies on availability of consistent master data SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 51 Agenda Introduction Application optimization example: mysrm Global Spend Analysis SAP BW Scenarios for Master Data load Scenario 1 Scenario 2 Scenario 3 Summary SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 52
27 Summary: Master Data Flow Scenarios for SAP BW I SAP BW SAP MDM Business Content Areas Operational Reporting (localized, unified) 0MATERIAL 1 MATNR ERP Solutions MATNR MATNR MATNR mysap XI XI SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 53 Summary: Master Data Flow Scenarios for SAP BW II Strategic (global, consolidated) SAP BW 0PRODUCT SAP MDM All All Global Attr. Operational Reporting (localized, identified)... 0EBP_PROD 0CRM_PROD 0MATERIAL 2 Global and local Attributes MATNR mysap XI XI Global Attr. SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 54
28 Summary: Master Data Flow Scenarios for SAP BW III SAP BW 0PRODUCT Strategic SAP MDM... 0EBP_PROD 0CRM_PROD 0MATERIAL Operational MATNR mysap XI XI SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 55 SAP MDM 2.0: Relevant Objects for SAP BW Start Product Ramp-Up Q SAPPHIRE `02 Lisbon SAP MDM first announcement Development Closed Business Partner Product Master Scope of Delivery for SAP MDM 2003 Technical Asset Product Structure Documents Change Management SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 56
29 Further Information Public Web: SAP Customer Services Network: service.sap.com/mdm/ Consulting Contact Roy Wood, VP SAP NetWeaver Consulting Practice Related SAP Education Training Opportunities BW310, SAP BW Modeling Related Workshops/Lectures at SAP TechEd 2003 SRM102, Master Data Consolidation and Catalog Management..., Beginner MDM201, SAP MDM as a Key Technology of SAP NetWeaver, Intermediate BW205, Concept of Consolidated InfoObjects in SAP BW, Intermediate SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 57 Questions? Q&A SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 58
30 Feedback Please complete your session evaluation and drop it in the box on your way out. Thank You! The SAP TechEd 03 Basel Team SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 59 Copyright 2003 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 Server TM 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, SAP NetWeaver 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 the trademarks of their respective companies. SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 60
31 SAP TechEd `03 EMEA Online WATCH THE REPLAYS, DOWNLOAD THE SLIDES, AND READ THE TRANSCRIPTS. SAP AG 2003, TechED Basel 2003, BW206_EMEA, Rainer Uhle / 61