MDM BuPa Content Information

SAP NetWeaverMDM Content

MDM Business Partner Content

Applicable Releases:

SAP NetWeaver MDM 5.5

SAP NetWeaver MDM 7.1

Topic Area:Information ManagementSAP Note 1035773

Capability:Master Data Management

Summary:The MDM Business Partner (BuPa) content can be used to consolidate and harmonize BusinessPartners, Customers and Vendors from SAP CRM, SRM and ERP systems. This documentdescribes the different parts of the MDM Business Partner content. Furthermore it contains sometips and tricks how to use the content as well as some links to additional information.

NoteThe SAP MDM Business Partner content supports the generic MDM scenarios Consolidationand Harmonization only. You cannot use this content for a central maintenance of businesspartner data. If you want to do this, please contact SAP.

Version 1.10

February 2010

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The information containedherein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPoint areregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, 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 aretrademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Readerare either trademarks or registered trademarks of AdobeSystems Incorporated in the United States and/or othercountries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registeredtrademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C®, World Wide WebConsortium, 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 andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAPNetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world.All other product and service names mentioned are thetrademarks of their respective companies. Data containedin 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 affiliatedcompanies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAPGroup shall not be liable for errors or omissions withrespect to the materials. The only warranties for SAPGroup products and services are those that are set forth inthe express warranty statements accompanying suchproducts and services, if any. Nothing herein should beconstrued as constituting an additional warranty.

These materials are provided “as is” without a warranty ofany kind, either express or implied, including but notlimited to, the implied warranties of merchantability,fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind includingwithout limitation direct, special, indirect, or consequentialdamages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links or other items containedwithin these materials. SAP has no control over theinformation that you may access through the use of hotlinks contained in these materials and does not endorseyour use of third party web pages nor provide any warrantywhatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplifythe product implementation. While specific productfeatures and procedures typically are explained in apractical business context, it is not implied that thosefeatures and procedures are the only approach in solving aspecific business problem using SAP NetWeaver. Shouldyou wish to receive additional information, clarification orsupport, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)included in this documentation are only examples and arenot intended to be used in a productive systemenvironment. The Code is only intended better explain andvisualize the syntax and phrasing rules of certain coding.SAP does not warrant the correctness and completeness ofthe Code given herein, and SAP shall not be liable forerrors or damages caused by the usage of the Code, exceptif such damages were caused by SAP intentionally orgrossly negligent.

Disclaimer

Some components of this product are based on Java™. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is onlyto be used by SAP’s Support Services and may not bemodified or altered in any way.

Document HistoryDocument Version Description

1.10 MDM 7.1 SP4 Patch 0






1.04 MDM 7.1 SP1 Patch 1 & MDM 5.5 SP6 Patch 4





Typographic ConventionsType Style Description

Example Text Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.Cross-references to otherdocumentation

Example text Emphasized words orphrases in body text, graphictitles, and table titles

Example text File and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database tools.

Example text User entry texts. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

IconsIcon Description

Caution

Note or Important

Example

Recommendation or Tip

GlossaryAbbreviation Description

BuPa Business Partner cMDM Central Master Data Maintenance defines the required processes for the

central creation of various types of master data in an interactive mannerin MDM and the distribution of the data into a heterogeneousenvironment. It includes leveraging the results to perform enterprise-wideanalytics (e.g. global spend analyses). The common process consists ofthe steps:- create master data centrally in MDM- distribute master data to remote systems to create new or update existing records in the systems- distribute related key and/or grouping information to BW for analyticscMDM requires usually the execution of the MDH scenario at least onceto initialize the central MDM system with the already existing master dataof the current environment.

DBMS Database Management System EhP Enhancement Package LT Lookup Table MDC Master Data Consolidation defines the required processes for cleansing

various types of master data in an interactive manner in particular within aheterogeneous environment. It includes for example leveraging theresults to perform enterprise-wide analytics (e.g. global spend analyses).The common process consists of the steps:- load master data - including its related reference data - into MDM- enrich and cleanse master data in MDM- distribute related key and/or grouping information to BW for analytics

MDC does not include the re-distribution of master data records into theiroriginal source systems.

MDIS Master Data Import Server MDH Master Data Harmonization defines the required processes for cleansing

and distribution of various types of master data in an interactive manner inparticular within a heterogeneous environment. It includes leveraging theresults to perform enterprise-wide analytics (like global spend analyses).The common process consists of the steps:- load master data - including its related reference data - into MDM- cleanse and enrich master data in MDM- re-distribute master data back to the original source systems- distribute related key and/or grouping information to BW for analyticsMDH means that you can only update already existing master datarecords in their original source systems. You can neither create newmaster data records in any source system based on the consolidated datanor create new records centrally in MDM.

MDM Master Data Management MDS Master Data Server MDSS Master Data Syndication Server MT Main Table QLT Qualified Lookup Table VAT Value Added Tax: tax that is added on to the value of a product when it

is manufactured and is paid by the customer at the time of purchase

Table of Contents

1. MDM Business Partner Content ......................................................................................1

2. MDM Business Partner Repository .................................................................................32.1 MDM Repository Files ...............................................................................................32.2 Predefined Repository Structure ...............................................................................32.3 Predefined Users and Roles .....................................................................................32.4 Predefined Repository Values ...................................................................................4

2.4.1 Tables ..........................................................................................................42.4.2 Validations ....................................................................................................42.4.3 Matching Content .........................................................................................72.4.4 Workflows .....................................................................................................7

2.5 Predefined Import and Syndication Content ..............................................................7

3. MDM Business Partner PI Content .................................................................................93.1 Overview ..................................................................................................................93.2 Download and Installation .........................................................................................93.3 Software Component Versions for Remote System Message Types ........................ 10

3.3.1 Business Scenario: MDM555_Inbound ....................................................... 113.3.2 Business Scenario: MDM555_Outbound ..................................................... 143.3.3 Business Scenario: MDM710_Inbound ....................................................... 173.3.4 Business Scenario: MDM710_Outbound ..................................................... 19

4. Performance Tuning ...................................................................................................... 224.1 Key Mapping ........................................................................................................... 224.2 Keyword and Sort Indices ....................................................................................... 22

5. Sample Data ................................................................................................................... 24

6. Import of Reference Data .............................................................................................. 256.1 Business Partner Roles ........................................................................................... 256.2 Genders.................................................................................................................. 256.3 Regions .................................................................................................................. 266.4 Tax Numbers and Tax Types .................................................................................. 266.5 Transportation Zones .............................................................................................. 26

7. Import of Master Data .................................................................................................... 277.1 From R/3 and ERP.................................................................................................. 27

7.1.1 Field Melting ............................................................................................... 277.1.2 Logical Checks and Transformations .......................................................... 277.1.3 Special Segment and Field Handling........................................................... 27

7.2 From CRM and SRM .............................................................................................. 287.2.1 Field Melting ............................................................................................... 287.2.2 Multi-Valued Fields ..................................................................................... 287.2.3 Logical Checks and Transformations .......................................................... 287.2.4 Special Segment and Field Handling........................................................... 28

7.3 MDIS Usage ........................................................................................................... 29

8. Syndication of Master Data ........................................................................................... 308.1 Completion of the delivered Map Templates ............................................................ 308.2 To R/3 and ERP ...................................................................................................... 30

8.2.1 Required Default Values in MDM ................................................................ 318.2.2 Field Split ................................................................................................... 318.2.3 Message Split ............................................................................................. 31

8.3 To CRM and SRM................................................................................................... 318.3.1 Required Default Values in MDM ................................................................ 318.3.2 Field Split ................................................................................................... 328.3.3 Task Codes ................................................................................................ 32

8.4 To BI....................................................................................................................... 328.5 MDSS Usage .......................................................................................................... 32

9. Upgrade from MDM 5.5 to MDM 7.1 .............................................................................. 339.1 Verify Repository .................................................................................................... 339.2 Import Maps............................................................................................................ 339.3 Validations .............................................................................................................. 33

10. Known Issues and Limitations...................................................................................... 3410.1 MDM 7.1 PI Adapter Usage .................................................................................... 3410.2 CRM and SRM Remote Keys .................................................................................. 3410.3 Time Dependency ................................................................................................... 3410.4 International Address versions ................................................................................ 3410.5 Multiple Addresses.................................................................................................. 34

11. Change History .............................................................................................................. 3611.1 MDM 7.1 ................................................................................................................. 3611.2 MDM 5.5 ................................................................................................................. 37

12. Related Content ............................................................................................................. 39


February 2010 1

1. MDM Business Partner ContentMDM Content is used here as a synonym for “content for SAP NetWeaver MDM Server”. MDMcontent shipped by SAP covers all MDM related development artifacts (e.g. repository definition,workflows, mappings etc.) that are specific for a master data object type (like Business Partner orMaterial). MDM content does neither include MDM core nor generic MDM service deliverables.MDM content is not only related to MDM software components. It also covers client systemconnectivity, i.e. everything that is needed for connecting SAP remote systems to a MDM server inorder to send or receive data from or to MDM.The MDM Business Partner content consists of:

SAP Note 1035773MDM Business Partner Content (current document)Content Strings – an excel file containing all Business Partner field and table stringstranslated in all supported languagesField Mapping and Check Tables – an excel file showing the fields of the repository andhow they relate to the supported SAP remote systemsMatch and Merge Business Partners – a detailed guide about the predefined matchingcontent of the Business Partner repository

MDM Business Partner repository MDM Business Partner specific PI content MDM Business Partner specific Portal content MDM Business Partner specific Web Services (only for MDM 5.5) MDM Business Partner specific content for the remote system extractors MDMGX and

MDM_CLNT_EXTR Sample Data

The BuPa content is useable for both MDM versions 5.5 and 7.1. Although the naming is differentrelated to the MDM release, the content (e.g. tables and fields, XSLT mappings, and so on) isidentical.You can download the content from SAP Software Distribution Center.For MDM 5.5 choose in the menu on the left side “Download Support Packages and PatchesEntry by Application Group”. Then continue on the main web page “SAP NetWeaver SAP MDMSAP MDM 5.5 Master Data Server MDM Business Content 5.5”.

NoteThe Business Content package contains the complete content for all pre-delivered SAPobject. You have to unzip this package and use the specific BuPa content.

For MDM 7.1 the business content is either part of the full MDM delivery (in case of supportpackages with patch level 0) or part of the MDM component delivery (in case of a patch for a supportpackage).To download the business content as part of the full MDM delivery, choose in the menu on the leftside “Download Installations and Upgrades Entry by Application Group”. Then continue on themain web page “SAP NetWeaver SAP MDM SAP NETWEAVER MDM 7.1”.

NoteThe Business Content is part of the full MDM delivery. You have to unzip this packageand then navigate to the specific Business Partner content within the“MDM\Business_Content” folder.

http://service.sap.com/notes/1035773

http://service.sap.com/swdc


February 2010 2

To download the business content as part of the MDM Component delivery, choose in the menu onthe left side “Download Support Packages and Patches Entry by Application Group”. Thencontinue on the main web page “SAP NetWeaver SAP MDM SAP MDM 7.1 Master DataServer MDM Business Content 7.1”.

NoteThe Business Content package contains the complete content for all pre-delivered SAPobject. You have to unzip this package and use the specific Business Partner content.


February 2010 3

2. MDM Business Partner RepositoryThe repository is the SAP NetWeaver MDM specific part of the complete MDM BuPa content. Itconsists of: The MDM repository files (*.a2a) A predefined repository structure (tables, fields) Predefined users and roles Predefined repository values Predefined validations, matching strategies and workflows Predefined import and syndication content

NoteThe BuPa repository is release dependant. You can use the repository only with itsrelated MDM release. If you apply an older version of a repository to a new MDMrelease, you have to update the repository first. You cannot use a repository that wasbuilt with a newer MDM release on an older MDM release.

2.1 MDM Repository FilesThe BuPa repository is part of the downloadable MDM content. The current versions are:

“MDM55650_BUSINESS_PARTNER.a2a” for MDM 5.5 SP6 Patch 5“MDM71400_BUSINESS_PARTNER.a2a” for MDM 7.1 SP4 Patch 0

If you require different versions of the repository, please contact SAP.

2.2 Predefined Repository StructureThe repository structure is a template. You can modify the structure so that it fits exactly to yourspecific requirements. Details about the repository structure are available in an additionaldocumentation attached to this note:

“MDM 5.5 & 7.1 - Field Mapping and Check Tables Business Partner.xls” (Excel File) – the fileis valid both for MDM 5.5 and MDM 7.1.

2.3 Predefined Users and RolesThe repository contains some predefined users and roles. Both are used for the user mapping of thegeneric Portal content. Nevertheless the users and roles are templates that you can adjust accordingto your needs.

CAUTIONPlease do not change the user & role “sapsupport”. Both are used to guarantee an easy,read-only access to your repository in case of errors.


February 2010 4

Role Name Role Description Assigned UserAdmin This is the administrative role providing full access to all

SAP MDM and repository functions.Admin

Business Expert This role provides read-only access to the MDM data and itsdistribution functions.

User

Default This is an automatic generated role that is currently notused.

Not used

Distributor This role provides access to the distribution functions(import & syndication) only.

Distributor

Master Data Expert This role provides full access to the MDM data and itsdistribution functions.

Expert

sapsupport This is a read-only role used by SAP support. sapsupport

RecommendationThe MDM 5.5 repository users do not have a password assigned. This changes withMDM 7.1 as a predefined password is now mandatory. Each user has the samepassword sapmdm assigned. The user detail setting “User must change password” isset to No. It is recommended that you change these settings according to your needs. Ifyou change the password for user “sapsupport” make sure to mention it in the SecureArea of OSS messages.

2.4 Predefined Repository Values

2.4.1 Tables

Lookup table “Address Usages”The address usage for the common SAP address type ”Standard Address” is predefined with itsaccording key mapping ”XXDEFAULT” for each SAP remote system.

Taxonomy lookup “Categories”The BuPa main table field “Category” is linked to a taxonomy lookup. The categories and theirattributes are predefined. There are three categories with codes and according key mapping for eachSAP remote system:

Category Name Person Organization GroupCategory Code 1 2 3Key Mapping Value 1 2 3Linked Attributes Academic Title,

Correspondence Language,Country of Origin,Gender,Nationality

Industry Sector,Is Natural Person,Legal Form

Group Type

The “Organization” attribute “Is Natural Person” is predefined with values “Yes” and “No” including thecorresponding key mapping (“Yes = TRUE”, “No = FALSE”) for each SAP remote system.

2.4.2 ValidationsYou can use MDM Data Manager to have a look at the predefined validations.


February 2010 5

MDM Calculate Full AddressThis validation is used as a function for the calculated field Full Address in the BuPa main table:

IF(IS_NOT_NULL(House Number),House Number&” “,”“) &

IF(IS_NOT_NULL(Street),Street&”, “,”“) &

IF(IS_NOT_NULL(Apartment),”Apt “&Apartment&”, “,”“) &

IF(IS_NOT_NULL(City),City&”, “,”“) &

IF(IS_NOT_NULL(Region.Name),Region.Name&”, “,”“) &

IF(IS_NOT_NULL(Postal Code),Postal Code&”, “,”“) &

IF(IS_NOT_NULL(Country.Name),Country.Name)

MDM Calculate Full NameThis validation is used as a function for the calculated field Full Name in the BuPa main table:

Branch(Category)

As the name depends on the BuPa Category, the validation uses the Branch function to calculate thenames correctly. The Branch calls the related calculations automatically:MDM Calculate Full Name [Organization]

IF(IS_NOT_NULL(Partner Title.Name),Partner Title.Name&” “,”“) &

IF(IS_NOT_NULL(Name 1/Last Name),Name 1/Last Name&” “,”“) &

IF(IS_NOT_NULL(Name 2/First Name),Name 2/First Name,”“)

MDM Calculate Full Name [Person]IF(IS_NOT_NULL(Partner Title.Name),Partner Title.Name&” “,”“) &

IF(IS_NOT_NULL(Name 2/First Name),Name 2/First Name&” “,”“) &

IF(IS_NOT_NULL(Name 3/Middle Name),Name 3/Middle Name&” “,”“) &

IF(IS_NOT_NULL(Name 1/Last Name),Name 1/Last Name,”“)

MDM Check Complete Address [Main Table]Check the maintenance status of an address. The validation ensures that a) mandatory fields aremaintained by calling validation MDM Check Address [Main Table] and b) the address usage isdefined as Standard Address by calling validation MDM Check Address Usage [Main Table]:

MDM Check Address [Main Table] AND

MDM Check Address Usage [Main Table]

MDM Check Address [Main Table]Check if an address has values for Street, Postal Code, City and Country:

IS_NOT_NULL(Street) AND

IS_NOT_NULL(Postal Code) AND

IS_NOT_NULL(City) AND

IS_NOT_NULL(Country.Name)

MDM Check Address Usage [Main Table]Check that the main address usage is Standard Address. This is mandatory for syndication:

IF(FIND(UPPER(Address Usage.Name),”STANDARD ADDRESS“)>0,TRUE,FALSE)


February 2010 6

MDM Check Complete Address [Address Lookup]Check the maintenance status of an address. The validation ensures that a) mandatory fields aremaintained by calling validation MDM Check Address [Address Lookup] and b) the address usage isnot defined as Standard Address by calling validation MDM Check Address Usage [Address Lookup]:

MDM Check Address [Address Lookup] AND

MDM Check Address Usage [Address Lookup]

MDM Check Address [Address Lookup]Check if an address has values for Street, Postal Code, City and Country:

IS_NOT_NULL(Address.Street) AND

IS_NOT_NULL(Address.Postal Code) AND

IS_NOT_NULL(Address.City) AND

IS_NOT_NULL(Address.Country.Name)

MDM Check Address Usage [Address Lookup]Check that all additional addresses are not used as Standard Address.

IF(FIND(UPPER(Addresses.Address Usage.Name),

”STANDARD ADDRESS“)>0,FALSE,TRUE)

Sample Mandatory Field CheckCheck if the field Search Term 1 has a value:

IS_NOT_NULL(Search Term 1)

TipThis validation shows how-to create validations for mandatory checks. Use it as atemplate for your own fields.

Sample VAT Number Format CheckA more complex example: Depending on the maintained Country ISO Code the VAT RegistrationNumber is checked according to the country specific format. If the country this Germany (DE), thevalidation calls the executable validation Sample German VAT Number Format Check. If the countrythis France (FR), the validation calls the executable validation Sample French VAT Number FormatCheck:

IF(Country.ISO Code=”DE“,Sample German VAT Number Check,

IF(Country.ISO Code=”FR“,Sample French VAT Number Check))

Sample German VAT Number Format CheckCheck the format for a German VAT Registration Number. The number must be 11 characters long. Ithast to start with DE. All other characters must be numeric:

LEN(VAT Registration Number)=11 AND

LEFT(VAT Registration Number,2)= ”DE“ AND

HAS_ALL_CHARS(MID(VAT Registration Number,3),0,9)

Sample French VAT Number Format CheckCheck the format for a French VAT Registration Number. The number must be 13 characters long. Ithast to start with FR. All other characters must be numeric:

LEN(VAT Registration Number)=13 AND

LEFT(VAT Registration Number,2)= ”FR“ AND

HAS_ALL_CHARS(MID(VAT Registration Number,3),0,9)


February 2010 7

2.4.3 Matching ContentMatching content (transformations, rules and strategies) is predefined in MDM Data Manager for allthree business partner categories. You can use the available content as template for your own, morespecific content. See the use case document Matching and Merging Business Partner Data that isattached to this note for more details.

2.4.4 WorkflowsYou can use MDM Data Manager to have a look at the predefined workflows.

MDM_ADDRESS_VALIDATION

This is a sample workflow that can be started directly with an Import Map or manually in MDM DataManager. The workflow performs a checkout of the records and runs through the predefined validationMDM Check Complete Address [Main Table].

NoteThe predefined import maps for BuPa import do not launch the workflow automatically.You have to change the import maps first using MDM Import Manager. After loading themap, choose Configuration Options in the top menu. Change propertyCheckout/Workflow and select the workflow you want to start automatically after a dataimport.

MDM_ORGANIZATION_MATCH

This is a sample workflow that can be started manually in MDM Data Manager. The workflow performsa check out of the records and runs through the predefined MDM_ORGANIZATIONS matchingstrategy using Records vs. Records as Match Records Scope. It requires manual interaction tomerge the records. Finally the workflow checks in the records.

MDM_SYNDICATION

This is a sample workflow usable to distribute records with MDM Data Manager. By adding recordsmanually to this workflow and executing it, you trigger the syndication via a configured port (in thiscase it is the port that sends Generic Customers to a BW system). Ensure that the MDSS is runningfor a successful distribution.

2.5 Predefined Import and Syndication ContentImport and syndication content consists of: Remote System templates within the repository for SAP BW, SAP CRM, SAP SRM and SAP R/3

and ERP. XML Schemas usable for data import and syndication. The XSD files are delivered additionally as

a part of the downloadable content, too.


February 2010 8

“GenericCustomer BW” describes the message structure for sending generic Customerrecords to SAP BW.“GenericVendor BW” describes the message structure for sending generic Vendor recordsto SAP BW.“ReferenceData CRM” describes the message structure for importing reference data beingextracted with MDMGX from a SAP CRM system.“ReferenceData R/3 & ERP” describes the message structure for importing reference databeing extracted with MDMGX from a SAP R/3 or ERP system.“ReferenceData SRM” describes the message structure for importing reference data beingextracted with MDMGX from a SAP SRM system.“SAP MDM Business Partner” describes the message structure for importing transformedMDM Business Partner records being extracted with MDM_CLNT_EXTR from a SAPremote system respectively for sending MDM Business Partner records to a SAP remotesystem.

Import and Syndication maps to ensure the import of reference and master data respectively thedistribution of master data. The import and syndication maps are delivered additionally as a part ofthe downloadable content, too.

Import and Syndication ports for automated import and distribution using the MDIS respectivelyMDSS.


February 2010 9

3. MDM Business Partner PI Content

3.1 OverviewThe PI content for MDM delivers interfaces, interface mappings and communication channel templates tailored to the supported SAP remote system and theshipped MDM repositories. In addition it delivers integration scenarios that reduce the manual effort required to define the communication between MDM andthe SAP remote systems.The “Software Component Versions for Remote System Message Types” section lists the additional software component versions needed in PI to processIDoc and/or XML Proxy messages from SAP remote systems.The “Business Scenario” sections list the interfaces, interface mappings and communication channel templates contained in the PI content for MDM totransform the message from remote system format to the expected MDM XML format and vice versa.The following MDM PI Content versions are available:Namespace: http://sap.com/xi/MDEApplicationContentSoftware Component Versions: MDM BUSINESS CONTENT 5.5 (usable for MDM 5.5 with SAP XI 3.0 (NetWeaver 2004)) MDM BUSINESS CONTENT 5.5 7.00 (usable for MDM 5.5 with SAP PI 7.0 (NetWeaver 7.0)) MDM BUSINESS CONTENT 7.1 (usable for MDM 7.1 with SAP PI 7.0 and 7.1 (NetWeaver 7.0 and 7.1))

3.2 Download and InstallationYou can download the MDM PI Content from SAP Software Distribution Center.For MDM 5.5 choose in the menu on the left choose “Download Support Packages and Patches Entry by Application Group”. Then continue on themain web page “SAP NetWeaver SAP MDM SAP MDM 5.5 XI Content”. You’ll see two entries:

“XICONTENT MDM BUS. 5.5 7.00” that is usable for MDM 5.5 combined with a SAP NetWeaver PI 7.0 system“XICONTENT MDM BUSINESS 5.5” that is usable for MDM 5.5 combined with a SAP NetWeaver XI 3.0 system

For MDM 7.1 PI content is either part of the full MDM delivery (in case of support packages with patch level 0) or part of the MDM component delivery (incase of a patch for a support package).To download the PI Content as part of the full MDM delivery, choose in the menu on the left “Download Installations and Upgrades Entry by ApplicationGroup”. Then continue on the main web page “SAP NetWeaver SAP MDM SAP NETWEAVER MDM 7.1”.

http://sap.com/xi/MDEApplicationContent

http://service.sap.com/swdc


February 2010 10

NoteThe PI Content is part of the full MDM delivery. You have to unzip this package and then navigate to the specific PI content within the“MDM\XI_Content” folder.

To download the PI Content as part of the MDM component delivery, choose in the menu on the left “Download Support Packages and Patches Entryby Application Group”. Then continue on the main web page “SAP NetWeaver SAP MDM SAP NETWEAVER MDM 7.1”.Deploy the MDM PI Content (TPZ file) into the PI repository. For XI 3.0 and PI 7.0 use the Integration Repository tool. For more information see Importing Process Integration Content on the SAP Help Portal. For PI 7.1 use the Enterprise Services Builder tool (ESR). For more information see Importing ESR Content on the SAP Help Portal.

3.3 Software Component Versions for Remote System Message TypesSAP remote system IDoc (sent to MDM) IDoc (received from MDM)

CREMDM DEBMDM CREMAS DEBMAS ADRMASR/3 4.6C1 PI 2004_1_46C PI 2004_1_46C SAP APPL 4.6C SAP APPL 4.6C SAP APPL 4.6CR/3 Enterprise 4.72 PI 2004_1_470 PI 2004_1_470 SAP APPL 4.7 SAP APPL 4.7 SAP ABA 6.20ERP 2004 / ECC 5.0 PI 2004_1_500 PI 2004_1_500 SAP APPL 5.0 SAP APPL 5.0 SAP BASIS 6.40ERP 2005 / ECC 6.0+ EhP 2+ EhP 3+ EhP 4+ EhP 5

SAP APPL 6.0SAP APPL 6.02SAP APPL 6.03SAP APPL 6.04SAP APPL 6.05




SAP BASIS 7.00SAP BASIS 7.00SAP BASIS 7.00SAP BASIS 7.01SAP BASIS 7.02

1 Releases R/3 4.6C, SRM 6.0, CRM 5.1 and NW 2004 BI are supported by MDM 5.5 only2 Extension Set 1.10 or 2.00

http://help.sap.com/saphelp_nw2004s/helpdata/en/44/5755451622311ee10000000a155369/frameset.htm

http://help.sap.com/saphelp_nwpi71/helpdata/en/44/5755451622311ee10000000a155369/frameset.htm


February 2010 11

SAP remote system Proxy XML structures (sent to MDM) Proxy XML structures (received from MDM)ABABusinessPartnerOut

GenericCustomerOut

GenericVendorOut

ABABusinessPartnerIn

GenericCustomerIn

GenericVendorIn

SRM 4.0 SAP ABA 6.40 SAP ABA 6.40SRM 5.0 SAP ABA 7.00 SAP ABA 7.00SRM 6.01 SAP ABA 7.00 SAP ABA 7.00SRM 7.03 SAP ABA 7.01 SAP ABA 7.01CRM 4.0 SAP ABA 6.20 SAP ABA 6.20CRM 5.0 SAP ABA 7.00 SAP ABA 7.00CRM 5.11 SAP ABA 7.00 SAP ABA 7.00CRM 2007³ SAP ABA 7.00 SAP ABA 7.00CRM 7.0³ SAP ABA 7.01 SAP ABA 7.01NW 2004 BI1 BI CONT 3.53 BI CONT 3.53 BI CONT 3.53 BI CONT 3.53NW 2004s BI BI CONT 7.03 BI CONT 7.03 BI CONT 7.03 BI CONT 7.03

If the required message type is not available in your PI Content of the software component version, you have to: Either download and install the latest version of the PI Content for the corresponding software component from Service Market Place. Or import the IDoc or XML Proxies manually.

3.3.1 Business Scenario: MDM555_InboundMDM 5.5 Inbound Processing – SAP remote system sending data to MDM ServerMDS Receives Data MDM 5.5Sender Communication Channel Template [none]

3 Releases SRM 7.0, CRM 2007 and CRM 7.0 are supported by MDM 7.1 only


February 2010 12

Systems based on NW2004

MDCSends Data

Outbound Interface Interface Mapping Inbound Interface Receiver CommunicationChannel Template

R/34.6C

CREMDM.CREMDM03PI 2004_1_46C

Cremdm03ToMDMBuPa555InMDM BUSINESS CONTENT 5.5 (7.00)

MDMBusinessPartnerInMDM BUSINESS CONTENT 5.5 (7.00)

FTP_MDMBusinessPartner_MDMInMDM BUSINESS CONTENT 5.5 (7.00)

DEBMDM.DEBMDM05PI 2004_1_46C

Debmdm05ToMDMBuPa555InMDM BUSINESS CONTENT 5.5 (7.00)



R/347x110

CREMDM.CREMDM04PI 2004_1_470

Cremdm04_470ToMDMBuPa555InMDM BUSINESS CONTENT 5.5 (7.00)



DEBMDM.DEBMDM06PI 2004_1_470

Debmdm06_470ToMDMBuPa555InMDM BUSINESS CONTENT 5.5 (7.00)



R/347x200









ERP 2004 CREMDM.CREMDM04PI 2004_1_500








CRM 4.0 ABABusinessPartnerOutSAP ABA 6.20

ABABuPa_620ToMDMBuPa555InMDM BUSINESS CONTENT 5.5 (7.00)



SRM 4.0 ABABusinessPartnerOutSAP ABA 6.40





February 2010 13

Systems based on NW 7.0

MDCSends Data


ERP 2005 CREMDM.CREMDM04SAP APPL 6.0




DEBMDM.DEBMDM06SAP APPL 6.0





















February 2010 14

3.3.2 Business Scenario: MDM555_OutboundMDM 5.5 Outbound Processing – MDM Server sending data to SAP remote systemMDS Sends Data MDM 5.5Systems based on NW2004

MDCReceivesData

Outbound Interface Sender Communication ChannelTemplate

Interface Mapping Inbound Interface Receiver CommunicationChannel Template

R/3 4.6C MDMBusinessPartnerOutMDM BUSINESS CONTENT5.5 (7.00)

FTP_MDMBusinessPartner_MDMOutMDM BUSINESS CONTENT 5.5 (7.00)

MDMBuPa555ToCremas03_46COutMDM BUSINESS CONTENT 5.5 (7.00)

CREMAS.CREMAS03SAP APPL 4.6C

IDOC_Receiving_MDMOutMDM BUSINESS CONTENT 5.5(7.00)

“ “ MDMBuPa555ToDebmas05_46COutMDM BUSINESS CONTENT 5.5 (7.00)

DEBMAS.DEBMAS05SAP APPL 4.6C


“ “ MDMBuPa555ToAdremas02_46COutMDM BUSINESS CONTENT 5.5 (7.00)

ADRMAS.ADRMAS02SAP APPL 4.6C


R/34.7x110

MDMBusinessPartnerOutMDM BUSINESS CONTENT5.5 (7.00)


MDMBuPa555ToCremas04_470OutMDM BUSINESS CONTENT 5.5 (7.00)

CREMAS.CREMAS04SAP APPL 4.70


“ “ MDMBuPa555ToDebmas06_470OutMDM BUSINESS CONTENT 5.5 (7.00)

DEBMAS.DEBMAS06SAP APPL 4.70


“ “ MDMBuPa555ToAdremas02_470OutMDM BUSINESS CONTENT 5.5 (7.00)

ADRMAS.ADRMAS02SAP ABA 6.20


R/34.7x200







February 2010 15

MDCReceivesData



“ “ MDMBuPa555ToDebmas06_470OutMDM BUSINESS CONTENT 5.5(7.00)





IDOC_Receiving_MDMOutMDM BUSINESS CONTENT 5.5

(7.00)

ERP2004












(7.00)

CRM 4.0 MDMBusinessPartnerOutMDM BUSINESS CONTENT5.5 (7.00)


MDMBuPa555ToABABuPa_620OutMDM BUSINESS CONTENT 5.5 (7.00)

ABABusinessPartnerInSAP ABA 6.20

XI_20_Receiving_MDMOutMDM BUSINESS CONTENT 5.5(7.00)

SRM 4.0 MDMBusinessPartnerOutMDM BUSINESS CONTENT5.5 (7.00)





NW2004BI

GenericCustomerOutBI CONT 3.53

FTP_GenericCustomer_MDMOutMDM BUSINESS CONTENT 5.5 (7.00)

GenericCustomerInBI CONT 3.53

HTTP_Receiving_MDMOutMDM BUSINESS CONTENT 5.5(7.00)

GenericVendorOutBI CONT 3.53

FTP_GenericVendor_MDMOutMDM BUSINESS CONTENT 5.5 (7.00)

GenericVendorInBI CONT 3.53



February 2010 16


MDCReceivesData



ERP2005










ADRMAS.ADRMAS03SAP Basis 7.00


(7.00)





















NW2004sBI




HTTP_Receiving_MDMOutMDM BUSINESS CONTENT 5.5

(7.00)






February 2010 17

3.3.3 Business Scenario: MDM710_InboundMDM 7.1 Inbound Processing – SAP remote system sending data to MDM ServerMDS Receives Data MDM 7.1Sender Communication Channel Template [none]Systems based on NW2004

MDCSendsData


R/347x110

CREMDM.CREMDM04PI2004_1_470




DEBMDM.DEBMDM06PI2004_1_470




ERP2004


















February 2010 18


MDCSendsData


ERP2005

CREMDM.CREMDM04SAP APPL 6.0




DEBMDM.DEBMDM06SAP APPL 6.0








CRM2007

ABABusinessPartnerOutSAP ABA 7.00

















February 2010 19

3.3.4 Business Scenario: MDM710_OutboundMDM 7.1 Outbound Processing – MDM Server sending data to SAP remote systemMDS Sends Data MDM 7.1Systems based on NW2004

MDCReceivesData



R/34.7x110

MDMBusinessPartnerOutMDM BUSINESS CONTENT 7.1(7.00)




IDOC_Receiving_MDMOutMDM BUSINESS CONTENT7.1 (7.00)







ERP2004











IDOC_Receiving_MDMOutMDM BUSINESS CONTENT

7.1 (7.00)

CRM 4.0 MDMBusinessPartnerOutMDM BUSINESS CONTENT 7.1(7.00)




XI_20_Receiving_MDMOutMDM BUSINESS CONTENT7.1 (7.00)


February 2010 20

MDCReceivesData



SRM 4.0 MDMBusinessPartnerOutMDM BUSINESS CONTENT 7.1(7.00)






MDCReceivesData



ERP2005










ADRMAS.ADRMAS03SAP Basis 7.00

IDOC_Receiving_MDMOutMDM BUSINESS CONTENT

7.1 (7.00)






CRM2007











SRM 5.0 MDMBusinessPartnerOutMDM BUSINESS CONTENT 7.1

FTP_MDMBusinessPartner_MDMOut


ABABusinessPartnerIn

XI_30_Receiving_MDMOutMDM BUSINESS CONTENT


February 2010 21

MDCReceivesData



(7.00) MDM BUSINESS CONTENT 7.1 (7.00) SAP ABA 7.00 7.1 (7.00)

SRM 7.0 MDMBusinessPartnerOutMDM BUSINESS CONTENT 7.1(7.00)





NW2004sBI




HTTP_Receiving_MDMOutMDM BUSINESS CONTENT7.1 (7.00)




HTTP_Receiving_MDMOutMDM BUSINESS CONTENT

7.1 (7.00)


February 2010 22

4. Performance TuningThere are a few settings in MDM Console in regard to the data model that have impacts on therepository’s performance (e.g. loading time, syndication, and so on).

4.1 Key MappingThe current repository uses key mapping for the main and the lookup tables. During data distribution(import and/or syndication) the messages that are sent to MDM or sent by MDM to a remote systemusually contain a lot of codes instead of texts. Especially for lookup tables key mapping is used toensure that the correct code is used for the same value.

ExampleYour system landscape consists of two remote systems. In remote system A the country“Germany” has a code “GER”; in remote system B the same country has code “DE”.During the import of reference data you create a single record for country “Germany” withtwo remote keys (“GER” for remote system A and “DE” for remote system B). Thisensures that during the import of master data the code that is used in the message ismapped to the correct lookup value.

Key mapping itself has some impacts on the loading of the repository and the syndication. It takesmore time to create additional indices for key mapping. The distribution of key mapping is slower thanthe distribution of lookup values.If you are sure that your reference data is 100% identical in your remote systems (following theexample above: each of your remote system uses “DE” as code for country “Germany”) you couldthink about including the key mapping codes as single fields of the lookup table and disable the “KeyMapping” option of the table in MDM Console.

NoteThe predefined import and syndication maps are built using the key mapping on lookuptables. If you change the settings in MDM Console, you have to redefine the mapsaccordingly.

4.2 Keyword and Sort IndicesEach field of a MDM repository can be added to the keyword and/or sort index. The keyword indexenables the keyword search for this specific field. The sort index enables sorting all repository recordsupon the field (refer to the MDM Console Reference Guide for details). Both settings can be donewhen defining a field in the “Field Detail” pane in MDM Console.Creating keyword and sort indices require a specific amount of time during the repository load. Thetable below shows the enabled fields:

Table Field Sort KeywordBusiness Partners MDM Partner ID XBusiness Partners Partner Number X XBusiness Partners Full Name X XBusiness Partners Full Address X XBusiness Partners Name 1 / Last Name X XBusiness Partners Name 2 / First Name X XBusiness Partners Street X XBusiness Partners House Number XBusiness Partners City X XBusiness Partners Postal Code XBusiness Partners Search Term 1 X XBusiness Partners Search Term 2 X XBusiness Partners VAT Registration Number X

http://service.sap.com/installmdm


February 2010 23

Table Field Sort KeywordAddresses Street X XAddresses House Number XAddresses City X XAddresses Postal Code XTax Numbers Tax Number Type XTax Numbers Tax Number XAs the fields listed above are only a proposal, you should check if you require more or less fields forkeyword search and/or sorting.

RecommendationIf a field has the type “Lookup [flat]”, it is not necessary to activate the sort index on thisfield as lookups are prepared for sorting by MDM anyways. If you want to use a specificfield within a matching rule, you have to set the Sort Index to “Normal”.


February 2010 24

5. Sample DataThe BuPa content contains a file named “Data.zip”. This MDM Business Partner Data Packagecontains two types of data files.All files within the "MasterFiles" folder are those XML files that have been used by SAP to create theImport Maps. If you need to rebuild the maps you can use those files. The master files MUST NOT beused within a productive environment. You may use these files for (re-) building the import maps only.All files within the "SampleData" folder are samples useable for data import. The sample files MUSTNOT be used within a productive environment. You may use the files for demo purposes only.Both folders contain batch files that copy the files into the related port folders. To enable the batchfiles, you have to copy the parent folders into the repository’s distribution root folder. The "MasterFiles"respectively "SampleData" folder has to exist on the same level as the repository’s "Inbound" and"Outbound" folders. Otherwise the batch files are not able to find the correct path to the port folders.The batch files have been built on a windows environment. If you want to execute the files on a sharedMDS folder, please check http://support.microsoft.com/kb/156276/en for details.

http://support.microsoft.com/kb/156276/en


February 2010 25

6. Import of Reference DataYou extract customizing data from SAP remote systems using the generic customizing data extractorMDMGX (see MDMGX Documentation for details). The configuration files “MDMGX_55650_BuPa.txt”respectively “MDMGX_71400_BuPa.txt” are available in the downloadable Business Content.If you use the Business Partner Repository to consolidate R/3 or ERP systems with CRM and/or SRM,it makes sense to check and add some key mapping information for some of the Business Partnerlookup tables. The reason is that the object models from R/3 and ERP differ from CRM and SRM. Thatmeans that the reference data is different, too, and thus should be checked and corrected beforeloading any object data.The predefined import maps use the customizing values for matching (the names/descriptions but notthe keys/codes). That means if you load reference data from multiple remote systems, MDIS checks ifthe value already exists depending on name. If yes, it updates the key mapping information of theexisting record. If not, it creates a new record. MDIS is only able to identify perfect matches. Slightlydifferent values lead to different records. Most of the lookup tables therefore use unique constraintsupon the lookup codes. This prevents importing invalid names for the same codes. If the import failswith a value exception (like a “unique constraint violation”) you should check the values of yourcustomizing data.

CAUTIONUnique constraints are checked for all fields that are defined as unique and additionallyfor remote keys. If the related field is multilingual, each language layer is checked forunique values, too.

NoteThe following chapters describe some tips regarding the import of reference data. Thechapters are valid for both MDM releases 5.5 and 7.1.

6.1 Business Partner RolesR/3 and ERP do not know the Business Partner role concept. Therefore you cannot extract any rolesfrom the R/3 and ERP system. Incoming MDM Business Partner records have the roles for Customersand Vendors applied automatically. To prevent a value mapping during the import, you should add theremote keys for roles in MDM Data Manager manually....

1. Select the “Business Partner Roles“ qualified look up table2. Select role “Customer”, right-click on it and choose “Edit Key Mappings”.3. Having imported roles from CRM and SRM you should see entries for your CRM and SRM

system with key “CRM000”. Add a new entry with key “CRM000” accordingly for each of yourR/3 or ERP system. Do not forget to set the Default flag.

4. Repeat the same action for role Vendor with key “BBP000”.

TipThe role name depends on your SAP system customizing. If you cannot find “Customer”or “Vendor”, check table “TBZ0T” in your SAP system with keys “CRM000” and“BBP000” to retrieve the correct role name.

6.2 GendersGenders are only imported from R/3 and ERP systems. CRM and SRM are using checkboxes forgender selection and hard coded values during the distribution process of persons. The gender codesfor CRM and SRM systems are “Male” with key “2”, “Female” with key “1”, and “Unknown” with key ”0”.

https://service.sap.com/sap/support/notes/964991


February 2010 26

To prevent a value mapping during the import of MDM Business Partner messages from CRM andSRM, you should add the remote keys for roles in MDM Data Manager manually to the Genderattribute for Persons.

6.3 RegionsThe regions table in the Business Partner repository is a hierarchy lookup table. It is very helpful thatyou check this table after the automatic import since MDIS only matches on names. The name of aregion is a concatenation of region and country. This allows a lot of possible mismatches which maylead to the creation of duplicate data.

6.4 Tax Numbers and Tax TypesTax Numbers and their Tax types are handled differently by CRM and SRM versus R/3 and ERPsystems. CRM and SRM store this information as key-value pairs in tables. The semantic meaning ofa tax number in R/3 or ERP is defined by the field type itself. MDM follows the CRM and SRMapproach. Therefore you need to create manual key mappings for the country specific tax types 0 to 4for R/3 and ERP.

6.5 Transportation ZonesTransportation Zones use the lookup table Countries as member field. To ensure a correct processingof the reference data files in MDIS, MDMGX is using the Process Level 1 for Transportation Zones. Ifyou extract data from a remote system, you have to execute the reference data extraction twice: first run uses Process Level 0 second run uses Process Level 1

ImportantThe MDMGX extraction must not be started before MDIS has successfully imported allProcess Level 0 files.


February 2010 27

7. Import of Master DataYou extract master data from SAP remote systems using the generic master data extractorMDM_CLNT_EXTR (see MDM CLNT_EXTR Documentation for details). The import requires a correctsetup of the SAP remote systems and PI. Refer to the IT Scenario Configuration Guide available onSAP Service Market Place and chapter MDM Business Partner PI Content of this note for details.

7.1 From R/3 and ERPThe main task of the import from R/3 and ERP is the structural transformation of the two R/3 objectsCustomer and Vendor to the MDM Business Partner. R/3 and ERP send IDocs that have to betransformed into the MDM Business Partner XML before the data can be imported into MDM. This isdone by an Interface (XSLT) mapping on PI. The following chapters describe the transformation indetails.

7.1.1 Field MeltingThe MDM Business Partner model uses melted fields to store Business Partner data.Some address fields are merged. This is valid for the City and PO Box City, and the country and POBox country code. To enable the field merge, the address must have at least a maintained street orPO Box.

7.1.2 Logical Checks and TransformationsThe XSLT mapping includes logical data transformations and/or checks as well.Dates are transformed into the format YYYYMMDD. Furthermore it is checked if any date value is setto the SAP eternity (date value equals 00000000 or 00010101). If yes, these values are transformed tothe MSSQL compatible value 19000101.Phone and Fax Numbers are transformed into the format <Number>-<Extension>.

7.1.3 Special Segment and Field HandlingSome segments/fields of the Business Partner require a specific handling in regard to structural andvalue mapping.MDM does not support international address versions. Therefore addresses have to be filtered. Onlythe standard address version (the first address segment of the IDoc) is transported to MDM. It isstored directly in the main table. The address usage code XXDEFAULT for standard address is addedby XSLT.Customers and Vendors do not know the business partner role concept. Therefore incomingcustomers are enriched with the Customer role; Vendors are enriched with the Vendor role.Furthermore a default key for the number range / account group segment is set according to theobject type.Customers and Vendors do not know the business partner category concept. Therefore all objectsare defined as Organizations having category code 2.The tax number concept of customers and vendors is different compared to the Business Partner.They carry the tax number type in the semantic meaning of the IDoc field. The XSLT transforms thismeaning into the Tax Number Type and Tax Number Value concept used in the repository. The VATNumber is stored in a specific main table field.




February 2010 28

7.2 From CRM and SRMThe main task of the import from CRM and SRM is the structural transformation of the ABA BusinessPartner to the MDM Business Partner. The complex ABA Business Partner message is reduced to aslight MDM Business Partner XML. This is done by an Interface (XSLT) mapping on PI (refer tochapter MDM Business Partner PI Content for details). The following chapters describe thetransformation in details.

7.2.1 Field MeltingThe MDM Business Partner model uses melted fields to store Business Partner data.The different Name fields of the Business Partner (person names, organization names and groupnames) are melted into a single set of four fields in the repository. The XML message uses the PersonName fields for transport.The Foundation Date field for organizations and the Birth Date field for persons are merged into asinge field in the repository. The XML message uses the Organization Date fields for transport.Some address fields are merged. This is valid for the City and P.O. Box City, and the country andP.O. Box country code. To enable the field merge, the address must have at least a maintained streetor P.O. Box.

7.2.2 Multi-Valued FieldsSome fields of the MDM Business Partner are multi-valued. The default delimiter for multi-values fieldsin the main table is ‘, ‘ (comma + blank), for multi-valued attributes it is ‘; ‘ (semicolon + blank). TheXSLT concatenates the following information segments: Industry Sectors DUNS Number Social Security Number Address Usages Roles

7.2.3 Logical Checks and TransformationsThe XSLT mapping includes a logical data transformations and/or checks as well. If the incoming datadoes not fit to the checks and can not be logically transformed, the XSLT processing results in an errormessage on PI.The Category Code is mandatory. It must have one of the values 1 for Person, 2 for Organization or 3for Group. Different values trigger an error.Dates are transformed into the format YYYYMMDD. Furthermore it is checked if any date value is setto the SAP eternity (date value equals 00000000 or 00010101). If yes, these values are transformed tothe MSSQL compatible value 19000101.Phone and Fax Numbers are transformed into the format <Number>-<Extension>.

7.2.4 Special Segment and Field HandlingThe Business Partner address is stored in two different sections of the repository. The standardaddress is stored directly in the main table. Additional addresses are stored in a qualified look uptable. The XSLT extracts the standard address from the others.The MDM Business Partner contains only address dependent communication information.Additional address independent communication information is not stored and therefore discardedduring the XSLT mapping. The address dependent communication information is limited to the


February 2010 29

standard values only. Stored values are phone, mobile phone (only available in the main address),and fax number, as well as the email address. The XSLT extracts these values from the others.The MDM Business Partner stores a reduced set of Identification Numbers. Only the DUNS Numberand the Social Security Number are stored in the repository, each in a single main table field. Theaccording number field itself might be multi-valued (max. length is 255 characters).The MDM Business Partner stores the Tax Numbers in two different sections of the repository. TheVAT Number for the Business Partner is stored directly in the main table. Additional tax numbers arestored within a qualified look up. The XSLT extracts the VAT number from the other tax numbers.

7.3 MDIS UsageCurrently the inbound ports for importing MDM Business Partner XML messages are defined asmanual ports. This configuration setting has been made for some reasons. All predefined maps do notyet contain any value mapping. Using MDIS for import you only have the option to add or skipunmapped values. Furthermore the value mapping is importing for the import into qualified lookuptables (QLT), too. You have to define the fields MDM Import Manager and MDIS shall use foridentifying if records in the QLT shall be added or updated. This strongly depends on the data itself(e.g. which part of the qualified lookup record does identify the record so that it can be differentiatedbetween update or add record?) and therefore SAP cannot predefine any mapping.

NoteIn general field values will only be mapped automatically if:a) there is value mapping information stored in the import mapb) the source value is NULL and the map configuration option “Automatically map NULLvalues” is set to “yes”c) the destination field has the type lookup table with key mapping and the source valuesare the keys

The recommendation is to use the Import Manger at least once for having a full control of the valueand QLT mapping. As soon as you have saved the import map including your specific value and QLTmapping, you can switch to automatic import via MDIS by changing the corresponding portconfiguration in MDM Console.


February 2010 30

8. Syndication of Master DataThe syndication requires a correct setup of the SAP remote systems and PI. Refer to the IT ScenarioConfiguration Guide available on SAP Service Market Place, Tips and Tricks for MDM BusinessPartner Distribution and chapter MDM Business Partner PI Content of this document for details.

8.1 Completion of the delivered Map TemplatesAll delivered syndication maps are templates. You have to add some specific settings before you canuse them in a productive environment. Therefore open a syndication map with MDM Syndicator.Switch to tab "Map Properties".Check that property “Output Remote System” (MDM 5.5) respectively “Remote Key Override” (MDM7.1) is set to your remote system. This setting ensures that MDM Syndicator and MDSS use thecorrect key mapping information when creating the XML message.Check that property "Suppress Records without Key" is marked. This ensures that only those recordsare distributed back to the remote systems that were previously imported from the same system.Use properties “XML File Output” and “Max Records Per Output File” to control the amount of recordsto be distributed in one single XML message.Use property “Suppress Unchanged Records” to control if you want to send always all records orchanged records (delta distribution) only.Switch to tab “Destination Items”.The outbound maps for the business partner require the SLD Name of the target receiving system.You have to maintain this value manually for attribute “remoteSystem”. Enter the name as “StaticText”. Attribute “schemeVersionID” has to be set for maps to CRM and SRM only (see the chapterbelow for details).

Figure 1: MDM Syndicator - define remote system

8.2 To R/3 and ERPR/3 or ERP expect single IDocs for each of their objects (Customer or Vendor) and an additional IDoccontaining the address related information. Since MDM follows the SAP Business Partner ObjectModel, it is not possible to distribute those IDocs directly from MDM. The main task of the syndicationto R/3 or ERP is the structural transformation of the MDM Business Partner data model to the R/3 orERP Customer and Vendor model. Hence the MDM Syndicator is not powerful enough to fulfill allstructural transformation tasks; MDM distributes an MDM Business Partner XML message to PI. PIuses XSLT mappings to transform the MDM Business Partner into the Customer and Vendor includingthe required message split into single objects and additional address IDoc. PI sends the resultingIDocs to the ALE inbound interface of R/3 or ERP.

ImportantIt is absolutely mandatory that you configure PI in a correct way. Ensure that themessage split has the correct sequence. Address IDocs must be sent always before theCustomer or Vendor IDocs. Otherwise ALE will not be able to process the IDocscorrectly. MDM is using the message split to enable the Business Address Service (BAS)usage. BAS supports an additional amount of address fields as well as the possibility to





February 2010 31

define extended address checks. An additional bonus is that using the BAS ensures thatall address fields have exactly the same Meta Data (field length, customizing data, andso on) through all SAP systems. It’s strongly recommended to do the message split andto use BAS.

8.2.1 Required Default Values in MDMTo enable a successful syndication of Business Partners to R/3 or ERP Customers and/or Vendors,the MDM Business Partners must have the correct Business Partner role assigned in MDM DataManager: Customer (key mapping code CRM000) Vendor (key mapping code BBP000)

ImportantThe key mapping values CRM000 and BBP000 are the important information. Bothvalues are used to identify the business partner and to map it into the corresponding R/3or ERP object.

If the Business Partner has no roles assigned, the XSLT creates empty IDocs that are discarded bythe ALE Inbound processing in R/3 or ERP.In addition the Business Partners to be distributed must have the category Organization with keymapping code 2. Currently only the distribution of Organizations to R/3 or ERP is supported. If thisvalue is not maintained to the Business Partner, the XSLT results in an error message.

8.2.2 Field SplitAll fields that have been melted during the import of Customers and Vendors from R/3 or ERP have tobe split into their original structures. The same is valid for multi-valued MDM fields. Those fields haveto be split into the correct Customer and Vendor IDoc segments. For details refer to the correspondingimport chapter of this document.

8.2.3 Message SplitAs mentioned above the MDM Business Partner message that is sent from MDM to PI is split intodifferent IDoc messages depending on the business partner role. The resulting Customer (DEBMAS)and/or Vendor (CREMAS) IDocs carry one single record as the ALE inbound processing in R/3 or ERPis not mass capable. Furthermore the address information is sent to R/3 or ERP using a specific IDoc(ADRMAS).Some fields of the Customer (DEBMAS) and Vendor (CREMAS) IDoc are available in the addressIDoc, too. As the address IDoc is the first, leading IDoc the duplicate fields of the Customer andVendor IDocs are marked with the “No Data Sign” that is a slash “/”. ALE inbound is using the alreadyexisting values of the address IDoc instead (refer to SAP Note 384462 for details).

8.3 To CRM and SRMCRM and SRM expect ABA Business Partner XML messages. As MDM uses only a subset of thebusiness partner and the ABA Business Partner messages differs depending on the system releaseversion, MDM sends a generic MDM Business Partner XML to PI. PI uses XSLT mappings totransform the MDM Business Partner messages into the correct ABA Business Partner XML.

8.3.1 Required Default Values in MDMWhen defining the syndication map for the MDM Business Partner it is mandatory to set the correctsystem version of the target system. This is an attribute of the XML. Its value refers to the SAP Basis(ABA) version of the target system (refer to chapter MDM Business Partner PI Content of this



February 2010 32

document for details). To change this value switch to tab “Destination Items” select attribute“schemeVersionID” and define a static text. Supported values are 620, 640, 700 and 701. The XSLTmapping on PI uses this information to build the correct ABA Business Partner XML. Providing a validvalue is mandatory, otherwise the XSLT mapping will fail.

8.3.2 Field SplitAll fields that have been melted during the import of Business Partner Data from CRM and SRM haveto be split into their original structures. The same is valid for multi valued MDM fields. Those fieldshave to be split into multiple ABA Business Partner segments. For details refer to the correspondingimport chapter.

8.3.3 Task CodesMost of the Business Partner segments need task codes for the proxy inbound process. All task codesare defined within the XSLT mapping.

8.4 To BIIf you distribute data to a new BI system that uses a web service base data source for inboundprocessing, the XML file requires the correct by namespace. The namespace is defined in thesyndication map. The screenshot below shows the Generic Vendor map as an example.

8.5 MDSS UsageCurrently the outbound ports for distributing MDM Business Partner XML messages are defined asmanual ports. This configuration setting has been made for some reasons. The delivered syndicationmaps are not yet complete. You have to finish the maps according to your distribution scenario andfurthermore to add some system landscape specific information in the maps (see above). As SAPneither knows your distribution scenario nor your system landscape, these values cannot bepredefined. Use MDM Syndicator once to finish the maps. Then you can use MDM Console toconfigure the outbound ports for automatic processing.


February 2010 33

9. Upgrade from MDM 5.5 to MDM 7.1Refer to the Upgrade Guide available on SAP Service Market Place and follow the given instructionsto upgrade your Business Partner repository from MDM 5.5 to MDM 7.1.

9.1 Verify RepositoryEnsure to verify your upgraded repository before its first load. The business partner standardrepository that was released with MDM 5.5 SP6 Patch 4 shows:

“2 non-fatal” errors after the upgrade to MDM 7.1Use the “Verify Repository – Repair” option to repair those errors.

9.2 Import Maps Important

Upgrading from MDM 5.5 to MDM 7.1 requires an upgrade of the Import Maps, too. Theupgrade happens as soon as you start MDM Import Manager with your upgradedrepository for the first time. Ensure that you run the import map upgrade before using therepository with MDIS. Refer to the Upgrade Guide for details.

The latest Business Partner repository shows no errors after the import map upgrade.

9.3 ValidationsSome validations seem to be invalid after the upgrade. Ensure to check the validations with MDMData Manager. Refer to chapter Validations for further details.

http://service.sap.com/installmdm71


February 2010 34

10. Known Issues and Limitations

10.1 MDM 7.1 PI Adapter UsageStarting with MDM 7.1 a new, MDM specific PI Adapter can be used for the message distribution. Ifyou want to use the adapter in your scenario, you have to change some configuration settings.First of all the adapter requires the usage of MDIS and MDSS. You have to change the correspondingport configuration in MDM console to automatic processing.Secondly the current PI Integration Scenarios still use the FTP Adapter for the CommunicationChannels between PI and MDM. You have to choose the PI Adapter instead during the configurationof your system landscape on PI. Refer to the MDM 7.1 PI Adapter Guide for more details.

10.2 CRM and SRM Remote KeysMDM 5.5 and 7.1 store one or more keys per database record. The keys are unspecified as MDMdoes not know key types (so called “scheme IDs“). It is possible to define a “Default Key”. Object keysin CRM and SRM systems can consist of multiple fields. The Business Partner uses two key fields: theGUID which is a technical key that is mostly used internally and hidden for the user, and a Partner IDwhich is a common number that can be customized by the user. This ID is used for display, search,and so on.In a Harmonization scenario, the Business Partner does already exist in the remote systems. Usually itwas imported into MDM. Messages sent from CRM and SRM contain both keys. With the currentfunctionality of MDM it is only possible to store one key per import. The import mapping defines if thePartner ID or Partner GUID is used for key mapping. Usually the Business Partners are updated orenhanced with data in MDM and then syndicated for updates to CRM and SRM. This requires usingthe GUID as an identifier for the BP for updates in the target remote system. This means that MDMneeds to syndicate the BP GUID as default key mapping.Unfortunately this has an impact on the current iViews. Some of the search iViews use the Partner IDfor search. This is due to the fact that the iViews call a service of the target remote system thatrequires the ID for searching. The dilemma is that using the GUID as key mapping values, the usercannot use the search iViews. Otherwise using the Partner ID, the search iViews would work but theharmonization is not longer possible.To support the harmonization scenario, the Import Maps are defined to store the Business PartnerGUID. This disabled the search functionality of some iViews.

10.3 Time DependencyThe time dependency concept of SAP systems is currently not supported by the Business PartnerModel. This may lead to problems within the data syndication if there are multiple time dependentaddresses of the same address usage type.

10.4 International Address versionsInternational Address versions are currently not supported by the BuPa content.

10.5 Multiple AddressesCRM and SRM remote systems allow multiple addresses for a single Business Partner record. Thosecan be extracted from the remote systems and imported into MDM. The main address is stored in themain table whereas additional addresses are stored within the qualified lookup table Addresses. Usinga QLT for this has some implications that are in fact common MDM limitations.

https://service.sap.com/~sapidb/011000358700001890482008E


February 2010 35

Validations on QLT are not really supported. Using any validation on the address table can lead tounexpected and/or erroneous results. Therefore you should use validations for additional addressesvery carefully.Matching and merging QLT is very tricky as the MDM Data Manager displays only non-qualifiers inmatching mode. You can neither see nor explicitly select qualifiers in matching and merging.Merging Business Partners having additional addresses or merging additional addresses themselvescan lead to issues if you redistribute the changed records to their original system. The reason is thatCRM and SRM systems require key identifiers (GUIDs) for each address of a Business Partner.Unfortunately MDM does not allow storing key mapping information on QLT level so that thisinformation is currently stored as a QLT field. This has two impacts: If you merge two Business Partner Records having multiple addresses each, the information which

address belongs to which original Business Partner is lost. If you merge multiple addresses into a single QLT record, only one address key will survive, the

others are lost.In both cases MDM does not offer any standard solution for a correct redistribution of merged multipleaddresses.


February 2010 36

11. Change History

11.1 MDM 7.1SP4 Patch 0

New: SP4 introduces a Code field for Validations. The validations in the repository have beenadjusted accordingly.

Update: changed Role Business Expert to be read-onlySP3 Patch 1 Re-archived repository for MDM 7.1 SP3 Patch 1

SP3 Patch 0 New: Added chapter for BI Syndication as new systems require the XML namespace in the

messageSP2 Patch 0 New: Added Workflow MDM_ADDRESS_VALIDATION New: Added Turkish as new language

Updated Reference Data XSDs and Import MapsUpdated Master and Sample XML FilesUpdated Field and Table translations

New: Added Content Strings excel file to this note. The file contains all Business Partner field andtable names translated into all supported languages. Use this file if you need to fix any translationissue.

Update: Changed Workflow MDM_ORGANIZATION_MATCH to be executed manually in MDMData Manager only.

Update: Changed all Syndication Map’s property Max Records Per Output File to 100 Update: Saved and exported all Import and Syndication Maps in XML format. Additionally removed

all *.MAP and *.SYN files in the Import.zip respectively Export.zip files. Update: Fixed all VAT and Address related Validations (see chapter Validations for details) Update: Fixed several wrong translations to enable the repository schema export. See the

attached Content Strings excel file for details. All changes are marked with 7.1 SP2 P0 in the LastChange column.

SP1 Patch 1 Update: Re-imported Import Maps and saved Syndication Maps to ensure that both are stored in

XML format on the Database. This is mandatory to enable the repository schema export.SP1 Patch 0 Update: Changed Import Map _MDMBusinessPartner of remote system MDC R/3 & ERP.

Unmapped the mapping of multiple addresses to qualified lookup table Addresses in master dataimport map as ERP sends a single address only that is mapped to the main address fields.

Update: Renamed XML Schema for MDM Business Partner Import to SAP MDM Business Partner7.1.

Update: Added some master data sample records in Data.zipSP0 Patch 0 New: Added Import and Syndication Maps XML format in the Import.zip respectively Export.zip

files New: Added Passwords for all repository Users


February 2010 37

Update: Syndication maps for Business Partners require the manual maintenance of the remotesystem attribute

Update: Redefined settings for Keyword and Sort Indices (see chapter Performance Tuning fordetails)

Update: Fixed broken Import Maps that are unusable after the upgrade from MDM 5.5 (seechapter Upgrade from MDM 5.5 to MDM 7.1 for details)

Update: Fixed XSLT Mappings regarding the handling of Transportation Zones

11.2 MDM 5.5SP6 Patch 5 New: Added Turkish as new language

Updated Reference Data XSDs and Import MapsUpdated Master and Sample XML FilesUpdated Field and Table translations

New: Added Content Strings excel file to this note. The file contains all Business Partner field andtable names translated into all supported languages. Use this file if you need to fix any translationissue.

New: Added Workflow MDM_ADDRESS_VALIDATION New: Added chapter for BI Syndication as new systems require the XML namespace in the

message Update: Fixed the Configuration Guide for Business Partner Events in CRM and SRM systems. Update: Fixed several wrong translations to enable the repository schema export. See the

attached Content Strings excel file for details. All changes are marked with 5.5 SP6 P5 in the LastChange column.

Update: Changed Import Map _MDMBusinessPartner of remote system MDC R/3 & ERP.Unmapped the mapping of multiple addresses to qualified lookup table Addresses in master dataimport map as ERP sends a single address only that is mapped to the main address fields.

Update: Changed all Syndication Map’s property Max Records Per Output File to 100 Update: Syndication maps for Business Partners require the manual maintenance of the remote

system attribute Update: Changed Workflow MDM_ORGANIZATION_MATCH to be executed manually in MDM

Data Manager only. Update: Fixed all VAT and Address related Validations (see chapter Validations for details) Update: Redefined settings for Keyword and Sort Indices (see chapter Performance Tuning for

details) Update: Added some master data sample records in Data.zip

SP6 Patch 4 Update: Unmapped the mapping of multiple addresses to qualified lookup table “Addresses” in

master data import map “_MDMBusinessPartner” of remote system “MDC R/3 & ERP” as ERPsends a single address only that is mapped to the main address fields

Update: Renamed XML Schema for MDM Business Partner Import to “SAP MDM BusinessPartner 5.5”

Update: Syndication maps for business partner require the manual maintenance of the remotesystem attribute

Update: Added some master data sample records in “Data.zip” for sample data import


February 2010 38

Update: Redefined settings for Keyword and Sort Indices (see chapter “Performance Tuning” fordetails)

Update: Fix in the Configuration Guide for Business Partner events in CRM and SRM systems.SP6 Patch 3 Update: Fix for Hungarian Language in Import Maps Update: Fixed for wrong field translations. See the attached Content Strings excel file for details.

All changes are marked with 5.5 SP6 P3 in the Last Change column. New: sample validations for VAT Numbers & mandatory fields New: sample syndication workflow

SP6 Patch 0 New: Support User and Role to allow read-only remote access Update: Sort Index and Keyword Settings for Flat Look Up Fields to improve Load performance

SP5 Patch 2 New: address fields in Main Table and Qualified Lookup Addresses table

c/o nameBuildingFloorDistrictTransportation Zone (including Lookup Flat table)Jurisdiction CodeCommunication Type (including Lookup Flat table)

New: ports and import maps for the new Lookup Flat tables Update: import and syndication maps for Business Partner Update: activated and corrected XSLT Mappings

MDMBuPa555ToAdrmas.xslMDMBuPa555ToCremas.xslMDMBuPa555ToDebmas.xsl

Update: changed field length of Country Name field (look up flat Countries) to 60 characters tocover ISO country names

SP5 Patch 1 New: support of Master Data Harmonization scenario for CRM and SRM New: field PO Box Postal Code in Main and Qualified Lookup Addresses table New: Hungarian as additional language Update: Language dependent Import Maps for Reference Data Update: added missing translations

SP5 Patch 0 First release of the SP05 Business Partner Repository New: simplified data model for Master Data Consolidation New: calculated fields for name and address (usable in matching) New: standard address in main table New: VAT Number, DUNS Number and Social Security Number in main table


February 2010 39

12. Related ContentMDM Content Information (SAP SDN)MDM Documentation (SAP Service Marketplace)MDMGX Documentation (SAP Note)MDM CLNT_EXTR Documentation (SAP Note)Tips and Tricks for MDM Business Partner Distribution (SAP Note)

https://www.sdn.sap.com/irj/sdn/nw-mdm?rid=/webcontent/uuid/2077a6dd-7768-2c10-6b9f-ab8c6e0d0632





www.sdn.sap.com/irj/sdn/howtoguides

MDM BuPa Content Information

Documents

Transcript of MDM BuPa Content Information