Friday Webinar Series Installing and Upgrading to SAP NetWeaver from a Data Unification Perspective Friday, March 09, 2007 Speaker: Klaus David, SAP NetWeaver.

Präsentation zum Thema: "Friday Webinar Series Installing and Upgrading to SAP NetWeaver from a Data Unification Perspective Friday, March 09, 2007 Speaker: Klaus David, SAP NetWeaver."—  Präsentation transkript:

1 Friday Webinar Series Installing and Upgrading to SAP NetWeaver from a Data Unification Perspective Friday, March 09, 2007 Speaker: Klaus David, SAP NetWeaver RIG

2  SAP AG 2007, Title / First Name Last Name / 2 Friday Webinar Series: 2007 - IT Practices Applied “IT Practices” Continuing with exploring 1 IT Practice “Theme” per month Goal is to promote an in-depth understanding how SAP NetWeaver supports our IT Practices 3-4 webinars in each “IT Practice theme” per month, –Week 1: IT Practice Overview and Introduction -What are the pain points? -How does this IT Practice address these pain points? -Sample customer references –Week 2: Upgrading to SAP NetWeaver -What is the release history related to this IT Practice? -How is upgrading accomplished and what are the key technological benefits? -Customer testimonials (if available) –Week 3: Powered by SAP NetWeaver (PBNW) -How is this IT Practice used in the mySAP Business Suite? -What examples can we show of customer/partners using this? -What are the key benefits this IT Practice provides to the mySAP Business Suite –Week 4: IT Practice Roadmap -How will SAP deliver additional value to our customers releases to come?

3  SAP AG 2007, Title / First Name Last Name / 3 IT Practice: Custom Development: This Week IT Practice: Data Unification March 2, 2007 –Overview: IT Practice Overview and Introduction - Data Unification –Speaker: Sunil Gupta, SAP NetWeaver Solution Marketing March 9, 2007 –Installing and Upgrading to SAP NetWeaver from a Data Unification Perspective –Speaker: Klaus David, SAP NetWeaver RIG March 16, 2007 –Powered By: Data Unification: Powered by SAP NetWeaver –Speaker: Douglas Roth, MDM Solutions and Business Development March 23, 2007 – Roadmap: Data Unification Roadmap – Speaker: Aaron Mahimainathan, SAP NetWeaver Product Definition March 30, 2007 – Topic: TBD – Speaker: TBD Today

4 Installing MDM Upgrading MDM What is a Support Pack, a Patch, a Hotfix What about Clients (ERP, SRM, MDM) What’s new for MDM-BI Integration

5  SAP AG 2007, Title / First Name Last Name / 5 Complete Installation Package The complete installation package One single archive containing all components Identical with CD shipped to customers Old download files are replaced by new version A new file for download is released for each Support Package  One single download for all required components in matching versions

6  SAP AG 2007, Title / First Name Last Name / 6 Complete Installation Package Complete Packages for new installations can be downloaded from SAP Support Portal. (Software Distribution Center – Installations) URL  http://service.sap.com/swdchttp://service.sap.com/swdc  Download  Installations and Upgrades  Entry by Application Group  SAP NetWeaver  SAP MDM

7  SAP AG 2007, Title / First Name Last Name / 7 Delivery of Updated MDM Components For updating an MDM installation, new components can be downloaded from SAP Support Portal. (Software Distribution Center – Support Packages and Patches) URL  http://service.sap.com/swdchttp://service.sap.com/swdc  Download  Support Packages and Patches  Entry by Application Group  SAP NetWeaver  SAP MDM  SAP MDM 5.5

8  SAP AG 2007, Title / First Name Last Name / 8 Structure of MDM Software Delivery The product MDM 5.5 consists of several components MDM Server 5.5 MDM GUI Clients 5.5 … Each components contains one or more modules MDM GUI Clients 5.5 –MDM Data Manager –MDM Import Manager –…  For detailed list see Info Page on SAP Support Portal (Located at the MDM download page on SAP Support Portal)

9  SAP AG 2007, Title / First Name Last Name / 9 MDM 5.5 Support Packages and Patches – Start Page Product Version SAP MDM 5.5 Software Components e.g. MDM Server 5.5 Info Page  List of Components & Modules

10  SAP AG 2007, Title / First Name Last Name / 10 Example: How to find MDM Server 5.5 SP02 P1 for Win32 Product: SAP MDM 5.5 1 1 Component: MDM Server 5.5 2 2 Platform: Windows IA32 3 3 Version: Support Package 2, Patch 2 4 4

11  SAP AG 2007, Title / First Name Last Name / 11 Information Supplied with a Released Component Title Component Name Version Support Package Patch Hot Fix 1 Info File Component Name, Build Number (for SP & Patches) Updated Module(s), Build Number (for Hot Fixes) Reference to fixed problem(s) via SAP Note(s) 2 Filename MDM|S|550|02|P_2|-nnnnnnnn.ZIP MDM Component Version 5.5Support Package 02Patch 2 Unique number for Component 3

12  SAP AG 2007, Title / First Name Last Name / 12 With SAP NetWeaver MDM 5.5 SP05 New installation option /s install.ini Automated software distribution Complete update with one single click Enhanced Support for Automated Installation (silent installation)

13 Installing MDM Upgrading MDM What is a Support Pack, a Patch, a Hotfix What about Clients (ERP, SRM, MDM) What’s new for MDM-BI Integration

14  SAP AG 2007, Title / First Name Last Name / 14 Upgrading from SP03 -> Sp04 Steps to perform Stop and backup your landscape Uninstall the old MDM 5.5 SP03 components Install the new MDM 5.5 SP04 installation packages Update the existing repositories Load repositories with index updating Optional : Update Portal content Optional : Update XI content Adapt custom developed API-programs (need to be done prior to upgrade) Perform all component specific activities Test former SP03 functionality in SP04

15  SAP AG 2007, Title / First Name Last Name / 15 Highly recommended : 2-Tier environment Ensures smooth upgrade in shortest time Transports support you, once upgrade in Dev-Environment was successful (e.g. objects, portal content)

16  SAP AG 2007, Title / First Name Last Name / 16 Compatibility of Repositories MDM Repositories use a certain database schema  Repository (DB schema) version and MDM Server version need to be compatible  DB schemas are easily updated with MDM Console to match the current server version However  DB schemas can not be downgraded to match an older MDM server version Hot Fixes typically do not require a DB schema update

17 Installing MDM Upgrading MDM What is a Support Pack, a Patch, a Hotfix What about Clients (ERP, SRM, MDM) What’s new for MDM-BI Integration

18  SAP AG 2007, Title / First Name Last Name / 18 What is a … Support Package? Provides corrections and enhancements for MDM Scenarios Is delivered as a complete installation package Only the latest Support Package level is available for download* Patch? Provides corrections Extends platform support Is delivered on a component base (e.g. MDM GUI Clients) Hot Fix? Contains urgent corrections (typically) for a single module (e.g. MDM Import Manager) For delivery the file of the complete component is updated with the new module Build Number? Used SAP internally for the production process and code maintenance. * Old SPs remain until full platform support is provided for the new SP

19  SAP AG 2007, Title / First Name Last Name / 19 Compatibility of Support Packages and Patches To ensure compatibility when upgrading, all modules need to be on the same Support Package level same Patch level Modules on different Hot Fix levels are typically compatible with each other and can therefore be applied independently.  The Build Number of modules may be different MDM Data Manager 5.5 SP4 Patch 1 MDM Server 5.5 SP4 Patch 2 MDM Data Manager 5.5 SP4 Patch 2 HF1  

20  SAP AG 2007, Title / First Name Last Name / 20 What is the meaning of Build Numbers and Support Packages ? Codeline / Branch: 5.5.35.x  Version & SP-Level: MDM 5.5 SP04 … 5.5.35.015.5.35.02 Codeline / Branch: 5.5.28.x  Version & SP-Level: MDM 5.5 SP03 … … Type of delivery 5.5.35.17 MDM 5.5 SP04 Patch 1 All components & all modules 5.5.35.19 MDM 5.5 SP04 Patch 1 Hot Fix 1 Only affected components & modules 5.5.35.00 MDM 5.5 SP04 All components & all modules Released as Build Number

21  SAP AG 2007, Title / First Name Last Name / 21 Numbering and Compatibility of Hot Fixes Hot Fixes are counted on product level Numbers are assigned sequentially for the updated components MDM 5.5 Server SP04 P1 HF1 MDM 5.5 GUI Clients SP04 P1 HF2 MDM 5.5 Import Server SP04 P1 HF2 MDM 5.5 Java API SP04 P1 HF3 Build 5.5.35.18 Build 5.5.35.22 Build 5.5.35.24 Hot Fix 1 Hot Fix 2 Hot Fix 3  Assumed this release sequence, there is no Hot Fix 2 for MDM Server

22 Installing MDM Upgrading MDM What is a Support Pack, a Patch, a Hotfix What about Clients (ERP, SRM, MDM) What’s new for MDM-BI Integration

23  SAP AG 2007, Title / First Name Last Name / 23 Remote System Connectivity to MDM MDS I N B O U N D I N T E R. O U T B O U N D I N T E R. SAP MDM 5.5 LOCALHOST REPOSITORY INBOUND CLIENT SYSTEM PORT ARCHIVE READY STATUS LOG Remote System (e.g., R/3) FTP Server SAP XI XML RFC, IDoc, etc. Import Server Syndication Server TCP/IP DB

24  SAP AG 2007, Title / First Name Last Name / 24 Communication in SAP ECC Distributing Master Data Consolidating Master Data Loading Master Data Client system (e.g., SAP ECC) MDM Data Manager MDM Import Manager SAP XI MDM Syndicator (2) Trigger extraction (3) System sends extracted objects to XI (5) System routes messages to file system (6) Load objects from file system (7) Transform, map, and match objects (8) Search and merge identical objects interactively (9) Change or add object data (11) System loads objects (12) System routes messages to target system; splits into CREMAS; ADRMAS etc. (10) Map, transform and save objects in file system (13) System receives messages (4) System transforms message to XML Typical communication in SAP ECC using SAP XI

25  SAP AG 2007, Title / First Name Last Name / 25 Customizing Transfer (ERP, CRM, SRM) Generic Extractor Framework Transaction MDMGX in the Client System Only relevant Check Tables are getting extracted

26  SAP AG 2007, Title / First Name Last Name / 26 Customizing Transfer (ERP, CRM, SRM) Sample Definition for BP

27  SAP AG 2007, Title / First Name Last Name / 27 Customizing Transfer (ERP, CRM, SRM) And the results structure of the ftp-server After sucessful extraction XML-Files are in these folders Use Import Manager to bring them into MDM

28 Installing MDM Upgrading MDM What is a Support Pack, a Patch, a Hotfix What about Clients (ERP, SRM, MDM) What’s new for MDM-BI Integration

29  SAP AG 2007, Title / First Name Last Name / 29 BI Data Quality Problems

30  SAP AG 2007, Title / First Name Last Name / 30 Integration Enhancements Overview Native Interoperability: Core integration between SAP NetWeaver MDM & SAP NetWeaver BI data and Meta data –Point to point connection between SAP NetWeaver MDM and SAP NetWeaver BI –SAP NetWeaver MDM repository is generated based on InfoObject as template Call SAP NetWeaver MDM during BI Data Staging: Look up of MDM data during BI Data Staging –MDM repository details are provided to BI workers without the need to leave their BI environment –Populate an entire characteristic domain from MDM Call SAP NetWeaver MDM during Enterprise Query and Analysis: Dynamically combine BI and MDM data at runtime without persisting MDM data in BI –Simplified ‘what if’ analysis –Reduces data load overhead

31  SAP AG 2007, Title / First Name Last Name / 31 Example: De-duplication Leads to Accurate Customer Rankings Prior to MDM, notice that Think Service, Inc. and Creative Intel are ranked #5 and #16, respectively. Notice that because of the integration with MDM, Think Service, Inc. and Creative Intel are the same sold-to party, thus their information is consolidated, moving them to #2 in the ranking.

32  SAP AG 2007, Title / First Name Last Name / 32 Additional Information Uses existing features and functions in BI and MDM Uses new set of APIs to integrate BI and MDM Currently accepting nominations for pilot projects

33  SAP AG 2007, Title / First Name Last Name / 33 Additional Information Uses new set of APIs to integrate BI and MDM Currently accepting nominations for pilot projects

34  SAP AG 2007, Title / First Name Last Name / 34 THANK YOU FOR YOUR ATTENTION ! QUESTIONS – SUGGESTIONS – DISCUSSION

35  SAP AG 2007, Title / First Name Last Name / 35 IT Practice: Custom Development: Next Week IT Practice: Data Unification March 2, 2007 –Overview: IT Practice Overview and Introduction - Data Unification –Speaker: Sunil Gupta, SAP NetWeaver Solution Marketing March 9, 2007 –Installing and Upgrading to SAP NetWeaver from a Data Unification Perspective –Speaker: Klaus David, SAP NetWeaver RIG March 16, 2007 –Powered By: Data Unification: Powered by SAP NetWeaver –Speaker: Douglas Roth, MDM Solutions and Business Development March 23, 2007 – Roadmap: Data Unification Roadmap – Speaker: Aaron Mahimainathan, SAP NetWeaver Product Definition March 30, 2007 – Topic: TBD –Speaker: TBD Next week

36  SAP AG 2007, Title / First Name Last Name / 36 Copyright 2007 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, Excel, Outlook, and PowerPoint 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C 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. MaxDB is a trademark of MySQL AB, Sweden. 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. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

37  SAP AG 2007, Title / First Name Last Name / 37 Copyright 2007 SAP AG. Alle Rechte vorbehalten Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Microsoft ®, WINDOWS ®, NT ®, EXCEL ®, Word ®, PowerPoint ® und SQL Server ® sind eingetragene Marken der 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower und PowerPC sind Marken oder eingetragene Marken der IBM Corporation. Adobe, das Adobe Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene Marken von Adobe Systems Inc. in den USA und/oder anderen Ländern. ORACLE ® ist eine eingetragene Marke der ORACLE Corporation. UNIX ®, X/Open ®, OSF/1 ® und Motif ® sind eingetragene Marken der Open Group. Citrix ®, das Citrix-Logo, ICA ®, Program Neighborhood ®, MetaFrame ®, WinFrame ®, VideoFrame ®, MultiWin ® und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc. HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C ®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA ® ist eine eingetragene Marke der Sun Microsystems, Inc. JAVASCRIPT ® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MaxDB ist eine Marke von MySQL AB, Schweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP ® -Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden. SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.