SAP MDM - Central Master Data Management Landscape Configuration

SAP NetWeaver MDM Central Master Data Management Landscape Configuration Ready Reference
Applies to:
SAP NetWeaver 2004s / MDM 5.5 SP04 Patch 01+
Summary
This document attempts to address the need to design and configure a landscape for central master data management using SAP NetWeaver MDM as a hub for all master data management from multiple source systems like ERP, SRM and CRM. This document attempts to consolidate the configuration steps in the respective source systems as well as SAP XI in the sequence in which they were performed in one such landscape configuration. Author(s): Sudhendu Pandey Company: SAP Created on: 16 January 2007
Author Bio
Sudhendu Pandey joined SAP India, Global Delivery Center (GDC) as an Associate Consultant in Feb 2005. He is a member of the MDM Practice in GDC and has been working in MDM since December 2005 with Indian as well as global customers. He also has a background in SAP XI and BI. He holds a bachelors degree in Electrical Engineering and a Masters in Systems and Marketing Management.
SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG
BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 1
Table of Contents
Background ................................................................................................................................ 3 Assumptions ............................................................................................................................... 3 Business Requirements .............................................................................................................. 3 Landscape Details ...................................................................................................................... 3 ERP System Configuration Steps ................................................................................................ 4 Configuration Steps - XI for ERP to MDM Communication ......................................................... 10 SRM System Configuration Steps ............................................................................................. 34 XI Configuration for Communication with SRM System.............................................................. 37 CRM System Configuration Steps ............................................................................................. 45 XI System Configuration for Communication with CRM System ................................................. 47 Appendix................................................................................................................................... 54 Copyright .................................................................................................................................. 55
Background
The purpose of this document is to serve as a ready reference, start up document or troubleshooting for MDM consultants while configuring a homogenous landscape comprising SAP Systems only. 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 and from the central MDM system. Additionally, the FTP location should be defined and available for file import into the MDM Server before the configuration steps can work.
Assumptions
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 and from the central MDM system The FTP location should be defined and available for file import into the MDM Server before the configuration steps can work. 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
Business Requirements
The MDM central hub can be interfaced with an SAP Business Intelligence (using the same instance of XI in the landscape) for better quality and accurate analytics based on Data from any of the mentioned source systems. It can also be integrated with an Enterprise Portal for a unified front end for master data creation, maintenance and enterprise wide access to master data using a browser. BI 7.0 onwards utilizes Web Services interface to connect to an XI system. Relevant details are available under the appropriate configuration guide in the BI Section of SDN / Service Marketplace.
Landscape Details
The figure below represents the hardware arrangement of the landscape used as reference in this document. System IDs would differ for the readers respective landscape and would need to be suitably addressed as per individual requirements.
SP-TIVM16 P163036
MDM 5.5 SP04
CRM 5.0
P163038
SRM 5.0
SAP XI 7.0 E1N
ERP 2005
E1S
8GB RAM / 2x 3.2GHz Xeon Processor/400GB HDD
EP 7.0 BI Java BW 7.0 E1P

8GB RAM/ 2x 3.2GHz Xeon Processor/400GB HDD
System Type ERP (ECC 6.0) SRM Server 5.5 CRM 5.0 XI 7.0 MDM 5.5 SP04
System ID E1SCLNT200 E1RCLNT200 E1QCLNT210 E1NCLNT001 Sp-tivm16
Client 200 200 210 001
Purpose Master Data Client Material Master Data Master Data Client Business Partner Master Data Master Data Client Customer Master Data Process Integration Central Master Data Management Hub
ERP System Configuration Steps

In all these configuration steps it is assumed that the user is familiar with login to an SAP system and also has the relevant authorizations to carry out the listed transactions. In the absence of authorizations the same can be requested from the landscape / system administrator before proceeding with the configuration steps. Information is primarily shared as screen shots without the use of detailed description of every step. The presented screen shots include the settings and values for the required fields that were tested to be working for the transfer of master data from the source systems to MDM.
1. RFC Destination Creation (Transaction sm59) a. Initial Screen Create RFC Destination
b. Settings / Relevant Values Technical Settings
c.
Settings / Relevant Values Logon and Security
d. Settings / Relevant Values MDMP and Unicode
e.
Settings / Relevant Values Special Options
2. Partner Profiles Creation - Transaction WE20 a. Initial Screen Creation of Partner Profiles Create New Entry MDM55
b.
Settings / Relevant Values for MDM System
c.
Settings / Relevant Values for XI System
d.
Settings / Relevant Values Outbound Parameters for XI system
e. Settings / Relevant Values Message Control
f.
Settings / Relevant Values Post Processing Permitted Agent
Configuration Steps - XI for ERP to MDM Communication

1. System Landscape Directory Entries for all the Source and Destination systems in the landscape MDM system is registered as a third party system in the SLD with relevant System ID and host names
2. Addition of ERP, SRM and CRM Systems to RFC Connections in XI - Transaction SM59
a. Adding the ERP Master Data Client System
3. Port maintenance in iDOC Adapter - Transaction IDX1
4. Metadata OverView for IDOC Adapter - Transaction IDX2 Additional metadata types might be necessary in case a greater variety of master data needs to be exchanged.
5. XI Design Time Integration Builder The relevant MDM business content For XI has been imported in the XI system before the following screen becomes visible as presented, Content to be imported MDM554_Inbound and MDM554_Outbound. The integration scenarios presented in the following pages are available as part of standard content and need not be configured.
6. XI Configuration Integration Builder The screens presented below appear by default after import of relevant business content within XI as mentioned in the previous step. These serve as the starting point for configuration of different Components in XI.
a. Communication Channel Configuration in XI for ERP System (ERP > MDM Inbound)
b. Receiver Channel Configuration in XI for MDM System Material Master Data from ERP (ERP > MDM Inbound)
c. Interface Determination in XI for MDM System Master Data from ERP (ERP > MDM Inbound)
d. Receiver Determination in XI for MDM System Master Data from ERP (ERP > MDM Inbound)
e. Receiver Agreement in XI for MDM System Master Data from ERP (ERP > MDM Inbound)
f.
Communication Channel Configuration in XI for ERP System Master Data to ERP (MDM > ERP Outbound)
g. Communication Channel Configuration in XI for MDM System Master Data to ERP (MDM > ERP Outbound)
h. Interface Determination in XI for MDM System Master Data to ERP (MDM > ERP Outbound)
i.
Receiver Determination in XI for MDM System Master Data to ERP (MDM > ERP Outbound)
j.
Sender Agreement in XI for MDM System Master Data to ERP (MDM > ERP Outbound)
k.
Receiver Agreement in XI for MDM System Master Data to ERP (MDM > ERP Outbound)
SRM System Configuration Steps

1. PROXY Generation - Transaction SPROXY Product and Business Partner Master Data to MDM
2. RFC Destination Configuration SRM System
XI Configuration for Communication with SRM System

1. RFC Connection Configuration XI System Transaction SM59 a. Initial Screen
b. RFC Destination Configuration XI System Technical Settings
c.
RFC Destination Configuration XI System Logon and Security
d.
RFC Destination Configuration XI System MDMP& Unicode
e.
RFC Destination Configuration XI System Special Options
2. Proxy Generation in XI System for Communication with SRM System - Transaction SPROXY
3. Integration Builder Communication Channel configuration for SRM System
4. Integration Builder Communication Channel configuration for MDM System
5. Receiver Determination Product Master Data from SRM System (SRM > MDM Inbound)
6. Interface Determination Product Master Data from SRM System (SRM > MDM Inbound)
7. Receiver Agreement Product Master Data from SRM System (SRM > MDM Inbound)
For the SRM system, only the inbound scenario is configured in this case. The MDM > SRM Outbound scenario can be configured in a way similar to that for the ERP System in case required.
CRM System Configuration Steps

1. Proxy Generation Transaction SPROXY
2. RFC Connection Configuration - Transaction SM59 a. Initial Screen
b. RFC Destination Configuration Technical Settings
XI System Configuration for Communication with CRM System

1. Integration Builder Communication Channel Configuration for CRM System (CRM > MDM Inbound)
2. Integration Builder Communication Channel Configuration for MDM System (CRM > MDM Inbound)
3. Interface Determination for CRM System (CRM > MDM Inbound)
4. Receiver Determination for CRM System (CRM > MDM Inbound)
5. Receiver Agreement for CRM System (CRM > MDM Inbound)
Appendix
Summary of Relevant Transaction Codes
Systems ERP (R/3), XI, SRM, CRM ERP ERP ERP ERP ERP ERP ERP ERP ERP ERP XI XI CRM, SRM CRM, SRM ERP ERP ERP, XI
Transaction Code SM59 BD10 BD12 BD14 BD16 BD11 BD13 BD15 WE20 WE05 WE19 IDX1 IDX2 MDM_CLNT_EXTR: BUPA_EXTRACT2 MDM_CLNT_EXTR: COM_MATERIAL_EXTRACT MDM_CLNT_EXTR: CUSTOMER_EXTRACT MDM_CLNT_EXTR: CREDITOR_EXTRACT SLDCHECK
Purpose RFC destination creation Send Material Send Customers Send Vendors Send Cost Center Get Material Get Customers Get Vendors Partner Profile Creation IDoc List Port Maintenance Port Maintenance in Idoc Adapter Metadata Overview of Idoc Adapter Extraction of Business partners Extraction of Material Extraction of Customers Extraction of Vendors Checking the connection to SLD
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 MDM - Central Master Data Management Landscape Configuration

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP MDM - Central Master Data Management Landscape Configuration

Uploaded by

Copyright:

Available Formats

SAP NetWeaver MDM Central Master Data Management Landscape Configuration Ready Reference

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 1

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 2

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 3

EP 7.0 BI Java BW 7.0 E1P

System ID E1SCLNT200 E1RCLNT200 E1QCLNT210 E1NCLNT001 Sp-tivm16

Client 200 200 210 001

ERP System Configuration Steps

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 4

b. Settings / Relevant Values Technical Settings

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 5

Settings / Relevant Values Logon and Security

d. Settings / Relevant Values MDMP and Unicode

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 6

Settings / Relevant Values Special Options

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 7

Settings / Relevant Values for MDM System

Settings / Relevant Values for XI System

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 8

Settings / Relevant Values Outbound Parameters for XI system

e. Settings / Relevant Values Message Control

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 9

Settings / Relevant Values Post Processing Permitted Agent

Configuration Steps - XI for ERP to MDM Communication

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 10

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 11

a. Adding the ERP Master Data Client System

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 12

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 13

3. Port maintenance in iDOC Adapter - Transaction IDX1

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 14

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 15

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 16

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 17

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 18

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 19

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 20

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 21

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 22

SAP DEVELOPER NETWORK | sdn.sap.com 2007 SAP AG