SAP NetWeaver MDM-SRM Catalog Configuration for SAP NetWeaver XI Ready Reference

Transcription

1 SAP NetWeaver MDM-SRM Catalog Configuration for SAP NetWeaver XI Ready Reference Applies to SAP NetWeaver 2004s / MDM 5.5 SP04 Patch 01+, SAP XI 3.0+, SAP SRM 5.0+ Summary The contents of this document attempt to present the configuration settings to be performed for SAP Exchange Infrastructure (XI) for process integration between the source SRM system and MDM system for transfer of MDM SRM Catalog relevant data from SRM to MDM. MDM system is being proposed as the backend for all the rich content relevant to a product catalog including Text, HTML, Images as well as specification sheets (PDFs etc.). Author: Sudhendu Pandey Company: SAP Created on: 09 Feb 2007 Author Bio Sudhendu Pandey joined SAP Global Delivery Consulting (GDC), SAP consulting in Feb He is a part of the MDM Practice in GDC and has been working on MDM since December 2005 with Indian as well as global customers. He also has a background in SAP XI and BI. He holds a bachelor s degree in Electrical Engineering and a Master s in Systems and Marketing Management SAP AG 1

2 Table of Contents Applies to... 1 Summary... 1 Author Bio... 1 Background... 3 Assumptions... 3 Landscape Details... 3 Configuration Steps System Landscape Directory Configuration - Technical Systems SRM System Settings Technical Systems XI System Settings Business Systems MDM System Settings Business Systems SRM System Settings Business Systems XI System Settings XI Integration Builder Design Time Business Content Preview XI Integration Builder Design Time Integration Scenario (Swim Lane diagrams) XI Integration Builder Configuration Business Systems and related communication channels SRM (D2T) and MDM (sp-tivm85) XI Integration Builder Configuration Scenarios XI Integration Builder Communication Channel - MDM Inbound (SRM > MDM) XI Integration Builder Communication Channel SRM Related Content Copyright SAP AG 2

3 Background The purpose of this document is to serve as a ready reference, start up document or troubleshooting for MDM / SRM / XI consultants while configuring a process integration landscape comprising SAP SRM, XI and MDM systems. Information has mostly been presented in the form of screen shots as encountered in different systems within the landscape. This information assumes that all the technical steps related to installation, physical connectivity and business content deployment have been completed before an attempt is made to configure the different systems in the landscape for master data transfer to the MDM system. Assumptions All technical steps related to installation, physical connectivity and business content deployment have been completed before an attempt is made to configure the systems in the landscape for master data transfer to MDM system. For details on the installation and business content deployment, the related content section at the end of this document can be referred The FTP location has been defined and available for file import into the MDM Server The user of this document is assumed to have basic knowledge on the use of SAP Systems, hence logon procedure and other details have been excluded from this document Landscape Details The table below represents the details of landscape used as reference in this document. System IDs would differ for the reader s respective landscape and would need to be suitably addressed as per individual requirements. System Type System ID Client Purpose SRM Server 5.5 D2T 200 Master Data Client Product Catalog Master Data XI 7.0 D2V 001 Process Integration MDM 5.5 SP04 Sp-tivm85 Product Catalog Master Data Management 2007 SAP AG 3

4 Configuration Steps 1. System Landscape Directory Configuration - Technical Systems SRM System Settings The essential and minimal settings for the systems relevant to this configuration are presented below starting with the SRM system. After adding the SRM system as a Web AS ABAP type technical system in the SLD, the tabs in the window below are used to review the system generated information as well as correct / supplement any information that might be necessary. Most of the values for the General tab presented below are assumed when the SRM System is first defined in the SLD SAP AG 4

5 The Appropriate client (in this case 200) should be mentioned in the list of available clients for the connected source system in the Clients tab. In case the same is not found, it can be added using the Add New Client button in the same tab as shown above. The Installed Products tab can be used to review / add new clients to the existing technical System in the SLD. The Valid SRM Server version 5.5 is displayed in the list of available installed products above SAP AG 5

6 The screen shot above shows the link between the SRM source system and the landscape to which it is connected. Since the landscape referred to in this document includes a comprehensive list of systems and their interconnections, this tab is presented. It may be different for individual landscapes. 2. Technical Systems XI System Settings The XI system managing the communication between the Source SRM and the destination MDM System is registered as a WebAS type ABAP System in the SLD as shown below. The following screens are presented to enable review and correction in case of an error in configuration of the same SAP AG 6

7 3. Business Systems MDM System Settings The MDM System (sp-tivm85) is registered as a Third Party system in the SLD as it is neither of the type WebAS JAVA or ABAP. The relevant options for a third party system type are presented in the list of tabs below the list accordingly SAP AG 7

8 The XI System under consideration is selected as the related integration server for the MDM system as shown above. Transport settings are maintained in case of a three tier landscape which is out of scope of the current document SAP AG 8

9 All the Products installed on the MDM system would be recognized and displayed in the appropriate tab for confirmation. It also helps to review the preliminary connectivity between the systems as intended. 4. Business Systems SRM System Settings Business systems are registered and configured in the SLD after ensuring that the technical systems relevant to the integration scenario under consideration have been registered and configured properly. The same is presented below for the SRM Source system SAP AG 9

10 The XI System mentioned for MDM is also the related integration server for SRM. 5. Business Systems XI System Settings The XI system is also similarly configured as a Business System in the landscape with integration support for the communication between the SRM and the MDM Systems SAP AG 10

11 6. XI Integration Builder Design Time Business Content Preview After completing all relevant configurations in the system landscape directory, the details are imported into the integration builder design time from the SLD. The XI standard Business content for SRM MDM catalog is assumed to be deployed and available for configuration in the XI system under consideration. In case it is required, the same can be down loaded from the SAP Service Marketplace ( under downloads section and then deployed. The screen shots below present an overview of the imported standard content for SRM MDM within the XI Integration Builder. Only the relevant components out of these would be used for further configuration SAP AG 11

12 2007 SAP AG 12

13 7. XI Integration Builder Design Time Integration Scenario (Swim Lane diagrams) A high level preview of the SRM MDM Integration scenario is available in the same namespace as the other components. This provides a validation as well as a starting point for further configuration. Both reference data as well as related Master Data that would be exchanged between the MDC and MDS are listed in the swim lanes. The availability of standard content reduces the time and effort required to configure the integration scenario SAP AG 13

14 2007 SAP AG 14

15 8. XI Integration Builder Configuration Business Systems and related communication channels SRM (D2T) and MDM (sp-tivm85) Communication channels relevant for Product Categories, IDs, Supplier Part Numbers, Product Data are configured within the integration builder for appropriate entries related to the connected source (SRM) and the destination (MDM) system SAP AG 15

16 9. XI Integration Builder Configuration Scenarios Each of the systems (SRM and MDM) involved in communication is defined as Business Systems under Service without Party in the Integration Builder and appropriate communication channels are selected for the respective Systems in the configuration scenario definition. The number of entries at this stage would depend on the type of reference and master data to be exchanged between the systems SAP AG 16

17 2007 SAP AG 17

18 10. XI Integration Builder Communication Channel - MDM Inbound (SRM > MDM) This stage of the configuration requires a careful observation and placement of appropriate entries for each of the Systems. The success or failure of the communication between the source and destination systems would depend to a large extent on the accuracy of the entries at this stage. The screens below present the relevant entries for the SRM to MDM Communication. The input type for MDM has been selected as XML and the target directory is the same as the one created on the MDM System by the MDM console corresponding to the SRM MDM Catalog repository. The Inbound > Ready folder of the hierarchy is the final target to place the output XML file from XI. The MDM Import Server Service should be running on the MDM System to automatically import the incoming XML file from the SRM source system. Also the related FTP service should be running on the MDM system to respond to files from the SRM System. The MDM configuration guide on the SAP Service marketplace can be referred for more details 2007 SAP AG 18

19 2007 SAP AG 19

20 Only one Communication Channel settings have been displayed above and rest are based on it. 11. XI Integration Builder Communication Channel SRM Configuration settings for Communication Channel, Receiver Determination etc. for outgoing communication from SRM to MDM has been presented in the screen shots below. Since only SRM > MDM communication is considered in this scenario, hence the steps for Configuration for MDM > SRM Communication have not been mentioned here SAP AG 20

21 2007 SAP AG 21

22 2007 SAP AG 22

23 Related Content MDM 5.5: Generic extractor for Customizing data (SAP Note) 3d f e543d c f4e4e554d3d } SRM-MDM Catalog 1.0 Installation & Configuration (SAP Note) 3d f e543d c f4e4e554d3d } 2007 SAP AG 23

24 Copyright 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, 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, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, 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. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is 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 not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. 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. Any software coding and/or code lines/strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent SAP AG 24