MDM 71 Vendor Content Information

(1)

MDM Content

MDM 7.1 Vendor Content

Applicable Releases:

SAP NetWeaver MDM 7.1 SP3 (and newer)

Topic Area:

Information Management

SAP Note 1318478

Capability:

Master Data Management

Summary:

The MDM Vendor content can be used to consolidate and harmonize Vendors from SAP ERP systems. This document describes the different parts of the MDM Vendor content for the SAP NetWeaver MDM Release Version 7.1. Furthermore it contains some tips and tricks how to use the content as well as some links to additional information.

Note

The SAP MDM Vendor content supports the generic MDM scenarios Consolidation and Harmonization only. You cannot use this content for a central maintenance of Vendor data. If you want to do this, please contact SAP.

Version 1.06

October 2011

(2)

© Copyright 2011 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.

SAP NetWeaver “How-to” Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting.

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.

Disclaimer

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

(3)

Document History

The following table highlights the changes in the document. Ensure to read chapter Change History thoroughly to obtain the complete information about content changes in the different release versions.

Document Version Description

1.06 MDM 7.1 SP8 Patch 0

Refined Payment Methods, Recipient Types, Withholding Tax Codes and Withholding Tax Countries for Company Code Data (SAP Note 1619538)

Rebuilt the archive

Added Dunning Data support (SAP Note 1451228) Added Web Dynpro Configuration

Updated the Performance Tuning chapter that is now a subchapter of the MDM Repository chapter

Added Company Code Data & Purchasing Organization support (SAP Notes 1403879, 1404964, and 1407978)

Added Regional Structure File support for Addresses

Added explanation of the port length issue in R/3 4.7 (SAP Note 1391292)

Added Web information (e.g. Homepages, FTP) support for

Communication Data

Added some information about possible „Out of Memory“ issues during import

Unified definition for flat and hierarchy lookup tables Resolved limitation for Instruction Key

Updated Validations & Main Table Banks

Resolved limitation for EU Tax Numbers (SAP Note 1381987) 1.00 MDM 7.1 SP3 Patch 0 – first delivery of the new content

(4)

Icons

Icon Description Caution Note or Important Example Recommendation or Tip

(5)

Glossary

Abbreviation Description

BAPI Business Application Programming Interface 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 manner in MDM and the distribution of the data into a heterogeneous environment. It includes leveraging the results to perform enterprise-wide analytics (e.g. global spend analyses). The common process consists of the 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 analytics

cMDM requires usually the execution of the MDH scenario at least once to initialize the central MDM system with the already existing master data of the current environment.

DBMS Database Management System

EhP Enhancement Package for SAP ERP remote systems LT Lookup Table is a MDM specific data structure

MDC Master Data Consolidation defines the required processes for cleansing various types of master data in an interactive manner in particular within a heterogeneous

environment. It includes for example leveraging the results 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

MDC does not include the re-distribution of master data records into their original 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 in particular within a heterogeneous environment. It includes leveraging the results 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

MDH means that you can only update already existing master data records in their original source systems. You can neither create new master data records in any source system based on the consolidated data nor create new records centrally in MDM.

MDM Master Data Management

(6)

Abbreviation Description

MDSS Master Data Syndication Server

MT Main Table is a MDM specific data structure

NW NetWeaver

PI (XI) Process Integration (eXchange Infrastucture)

QLT Qualified Lookup Table is a MDM specific data structure

UI User Interface

VAT Value Added Tax is a 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

XML eXtensible Markup Language is the file format used by the MDM standard repositories for data exchange with SAP remote systems

XSLT eXtensible Stylesheet Language Transformations is used by the MDM PI content to transform XML messages both structurally and sometimes for the contained values

(7)

1. MDM Vendor Content

MDM Content is used as a synonym for “content for SAP NetWeaver MDM Server”. MDM content shipped by SAP covers all MDM related development artifacts (like repository definition, workflows, mappings, and so on) that are specific for a master data object type (like Vendor or Material). 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 system connectivity, in example everything that is needed for connecting SAP remote systems to a MDM server in order to send or receive data from or to MDM.

The MDM Vendor content consists of:

SAP Note 1318478

MDM 7.1 Vendor Content (current document)

Content Strings – an Excel file containing all field and table strings translated into all

supported languages

Field Mapping and Check Tables – an Excel file showing the fields of the repository and

how they relate to the supported SAP remote systems

MDM Vendor Match and Merge – a how-to guide in PDF format explaining the Vendor’s

Matching content using the Sample Data. The guide is usable for demo purposes, too. MDM Vendor repository

MDM Vendor specific PI content MDM Vendor specific Portal content

MDM Vendor specific Web Dynpro Configuration

MDM Vendor specific content for the remote system extractors MDMGX and

MDM_CLNT_EXTR

Sample Data

Important

The Vendor content as described in this document is useable for MDM version 7.1 SP 3 and newer. If you want to use the Vendor content with a lower SP of MDM 7.1, it is strongly recommended to upgrade your MDM landscape to the latest MDM 7.1 SP first. The Vendor content for MDM 5.5 is described in SAP Note 1252883.

You can download the content from SAP Software Distribution Center.

The business content of MDM 7.1 is either part of the full MDM delivery (in case of support packages with patch level 0) or part of the MDM component delivery (in case of a patch for a support package). To download the business content as part of the full MDM delivery, choose in the menu on the left side “Download Installations and Upgrades Entry by Application Group”. Then continue on the

main web page “SAP NetWeaver SAP MDM SAP NETWEAVER MDM 7.1”.

Note

The business content is part of the full MDM delivery. You have to unzip this package and then navigate to the specific Vendor content within the “MDM\Business_Content” folder.

(11)

To download the business content as part of the MDM Component delivery, choose in the menu on the left side “Download Support Packages and Patches Entry by Application Group”. Then

continue on the main web page “SAP NetWeaver SAP MDM SAP MDM 7.1 Master Data Server MDM Business Content 7.1”.

Note

The business content package contains the complete content for all pre-delivered SAP objects. You have to unzip this package and use the specific Vendor content.

(12)

2. MDM Vendor Repository

The repository is the SAP NetWeaver MDM specific part of the complete MDM Vendor content. It consists of:

The MDM repository file (*.a2a)

Predefined repository structures (tables, fields) Predefined users and roles

Predefined validations, matching strategies and workflows Predefined import and syndication content

Note

The Vendor repository is release dependant. You can use the repository only with its related MDM release. If you apply an older version of a repository to a new MDM release, you have to update the repository first. Refer to chapter Change History to get an overview about all changes of the Vendor content in the different MDM releases. You cannot use a repository that was built with a newer MDM release on an older MDM release.

2.1 MDM Repository Files

The Vendor repository is part of the downloadable MDM content. The current version is: “MDM71800_VENDOR.a2a” for MDM 7.1 SP6 Patch 0

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

2.2 Repository Structure

2.2.1 Overview

The repository has been built following the maximize approach: it intends to cover all fields of the supported views that are available for Vendor creation in SAP ERP (see chapter SAP ERP Vendors

and/or the attached excel file Field Mapping and Check Tables Vendor.xls for details). Nevertheless the repository structure is considered as a template. You can modify the structure (e.g. add specific fields, deleted not required tables, and so on) so that the final repository fits exactly to your specific requirements.

Important

All tables and fields in the repository have been defined to support the Harmonization scenario. In this case it is important that an IDoc segment is completely covered by the related MDM data model as SAP ERP remote systems interpret missing and/or empty IDoc elements as a deletion of existing values!

Example

The ERP Vendor and the Vendor repository include four name fields. If you’d delete two of them in the MDM repository, you might delete data during distribution. You would send four names to MDM, but MDM is only capable to handle two. If you send the same record back to ERP, the IDoc would contain only two names. Those would be stored by ERP in the Vendor data; the missing names would be deleted!

(13)

2.2.2 Main Table & Tuple Fields

This chapter describes only special data modeling and settings of the repository.

Main Table Vendors

Main table Vendors contains a field Instruction Key. This field as modeled as a text field in MDM although it relates to a customizing table in SAP ERP systems. Unfortunately the CREMDM IDoc does not contain enough information to create the correct customizing key so that modeling the field as a lookup field is not possible in MDM.

Tuple Company Code Data

Tuple Company Code Data contains a field Payment Method. This is a multi-valued lookup field to the hierarchy table Payment Methods. In ERP payment methods are related to the country of the current company code. Since this information is not known in the MDM repository, the payment methods depend on the company code directly. During maintenance the selection is automatically reduced. Still you can select one or more payment methods.

Tuple Web

Tuple Web reflects the SAP ERP FTP and URL addresses that are part of the communication data. In SAP ERP web addresses may have only 132 characters if they are maintained in the UI. Longer addresses (up to 2048 characters) can be added using a BAPI. The Web tuple consists of several URI fields. Field URI is related to the 132 character screen field in ERP. Fields URI (Part 1 to 9) reflect the 2048 characters URI. The long URI is separated in the MDM repository as this structure is the same as in the CREMDM IDoc.

2.2.3 Lookup Tables

All lookup tables of the repository follow a specific modeling approach. All display fields of the lookup tables are defined with the Sort Index property Normal to speed up the record matching during the import of data into the tables.

Flat lookup tables usually consist of a Name and a Code field. The name field reflects the related customizing text field (not all customizing tables have texts). It can be multilingual according to its source. The code field is a clone of the remote key – the value used in the CREMDM IDoc. It is set as a unique field to ensure a high quality of your lookup table data.

Note

Lookup table Languages does not use the unique constraint for its Code field. The reason is that the unique checks are not case sensitive. Instead the ISO Code field of a language is used.

Hierarchy lookup tables use the same modeling approach. As a hierarchy consists of two or more code fields, related fields are added to the hierarchy table as lookup fields.

Example

A region usually consists of a region code and a related country. In the MDM repository, the country is added as an additional flat lookup field in the Region hierarchy lookup table.

(14)

Note

Lookup table House Banks uses different fields. Instead of the Name field it contains a field Bank Key. This is a concatenation of the House Bank ID and its Bank Number. Additionally the Bank Country is part of the hierarchy table.

2.3 Users and Roles

The repository contains some predefined users and roles. Both are used for the user mapping of the generic Portal content. Nevertheless the users and roles are templates that you can adjust according to your needs.

CAUTION

Please do not change the user & role sapsupport. Both are used to guarantee an easy, read-only access for SAP Support to your repository in case of errors.

The table below lists the predefined users and roles:

Role Name Role Description Assigned User

Admin This is the standard administrative role in MDM providing full access to all SAP MDM and repository functions.

Admin

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

User

Default This is a standard role in MDM but not used by MDM content. Not used

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

Distributor

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

Expert

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

Important

MDM 7.1 delivers all users with predefined passwords. Each user has the same

password sapmdm assigned. The user detail setting User must change password is set to No. It is recommended that you change these settings (except for user sapsupport) according to your needs.

If you change the password for user sapsupport, too, ensure to mention the new password in the secure area of OSS messages.

(15)

2.4 Repository Values

2.4.1 Validations

You can use MDM Data Manager to have a look at the predefined validations. Validations are visible for their related main table and/or tuple only. Ensure to select the correct main table and/or tuple.

Tip

Each predefined validation has to be executed manually in MDM Data Manager. If you want to automate the execution, set the validation property Automatic Execution either to Error or to Warning. This activates the validation checks when saving one or more records.

Note

The major part of validations within a SAP ERP remote system is actually system customizing. Validations in the repository do not guarantee that they exactly fit to your remote system. The predefined validations use the settings of the latest SAP ERP release. Nevertheless it might be possible that your SAP ERP remote system uses different settings, e.g. for mandatory fields. Adjust the validations in the MDM repository according to your needs.

ERP Mandatory Fields (Validation Group)

This validation group consists of several single mandatory field checks. It checks all MDM repository fields for values that are marked as mandatory in a common SAP ERP remote system. Checks are performed for the fields:

Table / Tuple Fields

Vendors Vendor Number, Account Group, Language, Name 1, Search Term 1, Country Bank Details Bank, Bank Account Number

Company Code Data Company Code Dunning Data Dunning Procedure

E-Mail Addresses Is Standard E-Mail Address, Sequence Number EU Tax Numbers Country

Fax Numbers Is Standard Fax Number, Fax Country, Sequence Number

Phone Numbers Is Standard Number, Phone Country, Phone Number Type, Sequence Number Purchasing

Organization Data

Order Currency

Web Is Standard URI, URI Type, Sequence Number

Tip

This example shows how validation groups can be used. Anyways you can create a single validation that checks for all mandatory fields in one run, too.

(16)

MDM Execute All Validations (Validation Group)

This validation group simply collects all existing validations of the repository. This allows the execution of all validations in a single action.

MDM Hierarchy Lookup Consistency (Validation Group)

This validation group consists of several single consistency checks for hierarchy lookup tables. It checks all MDM repository hierarchy fields for their related lookup values to ensure the consistency of the hierarchies.

Example

A region usually consists of a region code and a related country. In the MDM repository, the country is added as an additional flat lookup field in the Region hierarchy lookup table. Nevertheless the actual Country and Region are independent fields of the main table. The validation checks if the actual country and the region’s country are identical.

Checks are performed for the fields:

Vendors Region, Region for PO Box, Regional Structure Additional City, Regional Structure City, Regional Structure District, Regional Structure PO Box City, Regional Structure Street, Transportation Zone

Company Code Data Accounting Clerk, House Bank, Payment Methods, Recipient Types, Reconciliation Account, Tolerance Groups, Withholding Tax Codes, Withholding Tax Countries

MDM Calculate Full Address

This validation is used as a function for the calculated field Full Address in the Vendors main table:

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

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

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

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

MDM Calculate Full Bank Address

This validation is used as a function for the calculated field Bank Address in the Banks main table:

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

(17)

MDM Calculate Full Name

This validation is used as a function for the calculated field Full Name in the Vendors main table:

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

IF(IS_NOT_NULL(Name 2),Name 2&” “) & IF(IS_NOT_NULL(Name 3),Name 3&” “) & IF(IS_NOT_NULL(Name 4),Name 4)

MDM Check Bank Master Mandatory Fields

This validation is used to check the Banks main table for mandatory fields.

IS_NOT_NULL(Bank Country.[Record], Bank Name, Bank Key)

MDM Check Company Code Numeric Fields

The MDM data types differ from the SAP ERP data types. Some ERP data types (like NUMC, numeric characters) are not known in MDM. Those fields are usually using the text type in MDM. This

validation is used to check if affected Company Code Data tuple fields use numbers only: Check Cashing Time, Personnel Number

HAS_ALL_CHARS(Check Cashing Time, “0” , “9”) AND HAS_ALL_CHARS(Personnel Number, “0” , “9”)

MDM Check Company Code Payment Advice

This validation is used to check the Company Code Data tuple for the Payment Advice fields. You can either send Payment Advices by EDI or XML only.

IS_NOT_NULL(Payment Advice by XML.[Record], Send Payment Advices by

EDI?.[Record])

MDM Check Delivery Service

This validation is used to check the Vendors main table fields Delivery Service Number and Delivery

Service Type. If a delivery service is maintained, SAP ERP requires values for both fields.

IF(IS_NOT_NULL(Delivery Service Number)

OR IS_NOT_NULL(Delivery Service Type.[Record]), IS_NOT_NULL(Delivery Service Number)

AND IS_NOT_NULL(Delivery Service Type.[Record]))

MDM Check Dunning Data Numeric Fields

validation is used to check if affected Dunning Data tuple fields use numbers only: Dunning Level

HAS_ALL_CHARS(Dunning Level, “0” , “9”)

MDM Check E-Mail Address Format

This validation is used to check if the E-Mail Addresses tuple field E-Mail Address has the correct format. It checks if the string contains at least a “@” and “.” character.

(18)

MDM Check E-Mail Address Sequence Number

This validation is used to check if the E-Mail Addresses tuple field Sequence Number has the correct format. It checks if the string consists of exactly three digits.

HAS_ALL_CHARS(Sequence Number, ”0“ , ”9“) AND LEN(Sequence Number) = 3

MDM Check Fax Number Sequence Number

This validation is used to check if the Fax Number tuple field Sequence Number has the correct format. It checks if the string consists of exactly three digits.

MDM Check Phone Number Sequence Number

This validation is used to check if the Phone Number tuple field Sequence Number has the correct format. It checks if the string consists of exactly three digits.

MDM Check PO Box vs. Company Postal Code

This validation is used to check the Vendors main table fields PO Box Postal Code and Company

Postal Code. SAP ERP allows the maintenance of either a PO Box Postal Code or a Company Postal

Code only.

IS_NOT_NULL(PO Box Postal Code, Company Postal Code)

MDM Check PO Box vs. Delivery Service

This validation is used to check the Vendors main table fields PO Box, Delivery Service Number and

Delivery Service Type. SAP ERP allows the maintenance of either a PO Box or a Delivery Service

only.

IS_NOT_NULL(PO Box) AND

(IS_NOT_NULL(Delivery Service Number)

OR IS_NOT_NULL(Delivery Service Type.[Record]))

MDM Check PO Box vs. PO Box w/o Number

This validation is used to check the Vendors main table fields PO Box and PO Box without Number. If the flag PO Box without Number is set, the PO Box must not have a value.

IS_NOT_NULL(PO Box) AND PO Box without Number = ‘X’

MDM Check Purchasing Organization Incoterms

This validation is used to check the Purchasing Organizations tuple fields Incoterms (Part 1) and

Incoterms (Part 2). If an Incoterm is maintained, SAP ERP requires values for both fields.

IF(IS_NOT_NULL(Incoterms (Part 1).[Record]) OR IS_NOT_NULL(Incoterms (Part 2)),

IS_NOT_NULL(Incoterms (Part 1).[Record]) AND IS_NOT_NULL(Incoterms (Part 2)))

MDM Check Purchasing Organization Numeric Fields

validation is used to check if affected Purchasing Organization Data tuple fields use numbers only: Planned Delivery Time in Days, Staging Time in Days

(19)

HAS_ALL_CHARS(Planned Delivery Time in Days, “0” , “9”) AND HAS_ALL_CHARS(Staging Time in Days, “0” , “9”)

MDM Check Purchasing Organization Transportation Chain and Staging Time

This validation is used to check the Purchasing Organizations tuple fields Transportation Chain and

Staging Time in Days. If one of the fields is maintained, SAP ERP requires values for both fields.

IF(IS_NOT_NULL(Transportation Chain.[Record]) OR IS_NOT_NULL(Staging Time in Days),

IS_NOT_NULL(Transportation Chain.[Record]) AND IS_NOT_NULL(Staging Time in Days))

MDM Check Purchasing Organization Vendor Service Level

This validation is used to check the Purchasing Organizations tuple field Vendor Service Level. The field is a decimal field in SAP ERP having one decimal place. The value format must be <nnn>.<n>, e.g. 100.0 or 44.8. The validation checks first if the characters up to the dot are numeric. The dot itself must be placed at the penultimate position of the value. The last character must be again numeric.

HAS_ALL_CHARS(LEFT(Vendor Service Level,

FIND(Vendor Service Level, “.”) – 1), “0”, “9”) AND

FIND(Vendor Service Level, “.”) = LEN(Vendor Service Level) – 1 AND HAS_ALL_CHARS(RIGHT(Vendor Service Level, 1), “0”, “9”)

MDM Check Vendor Numeric Fields

validation is used to check if affected Vendors main table fields use numbers only: Int. Location Number 1, Int. Location Number 2, Check Digit

HAS_ALL_CHARS(Int. Location No. 1, “0” , “9”) AND HAS_ALL_CHARS(Int. Location No. 2, “0” , “9”) AND HAS_ALL_CHARS(Check Digit, “0” , “9”)

MDM Check Web Sequence Number

This validation is used to check if the Web tuple field Sequence Number has the correct format. It checks if the string consists of exactly three digits.

MDM Check Web URI

This validation is used to check if the Web tuple field URI has the same characters as the field URI

(Part 1). It checks the first 132 characters.

IF(IS_NOT_NULL(URI) OR IS_NOT_NULL(URI (Part 1)) IS_NOT_NULL(URI) AND IS_NOT_NULL(URI (Part 1)) AND

URI = LEFT(URI (Part 1), 132))

MDM Sample Check Mandatory Field

Check if the field Vendors main table field Vendor Number has a value:

(20)

Tip

This validation shows how-to create validations for mandatory checks. Use it as a template for your own fields.

MDM Sample Check VAT Registration Number

This validation is used to check the format of the VAT Registration Number in the Vendors main table. First the country of the current record is identified. Depending on the country, the related specific VAT check is executed.

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

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

MDM Sample Check French VAT

This validation is used to check the format of a French VAT Registration Number in the Vendors main table. The number must be exactly 13 characters long, start with the French Country Code and must not contain any blanks.

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

LEN(VAT Registration Number) = 13 AND

FIND(VAT Registration Number, “ ”) = 0 MDM Sample Check German VAT

This validation is used to check the format of a German VAT Registration Number in the Vendors main table. The number must be exactly 11 characters long, start with the German Country Code and must not contain any blanks.

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

LEN(VAT Registration Number) = 11 AND

FIND(VAT Registration Number, “ ”) = 0

2.4.2 Matching Content

Matching content consists of transformations, rules and strategies. The Vendor repository contains several transformations, rules and a single matching strategy:

Transformations for Company and Full Names, Addresses and Search Terms Rules for Full Names, Addresses, Search Terms and the VAT Registration Number Full Vendor Matching strategy

Note

The predefined matching content is a template only. It is created in relation to the Vendor Sample Data. Use these templates for creating your own, more specific matching

content. Refer to the Vendor: Match and Merge how-to guide that is attached to this note for more details.

2.4.3 Workflows

MDM Full Vendor Matching

This sample workflow can be started manually in Data Manager. The workflow performs a check out of the records and runs through the predefined Full Vendor Matching strategy using Records vs.

(21)

Records as Match Records Scope. It requires manual interaction to merge the records. Finally the workflow checks in the records.

MDM Mandatory Fields Validation

This sample workflow can be started directly with an Import Map or manually in Data Manager. The workflow performs a checkout of the records and runs through the all validations of the group ERP

Mandatory Fields. It indicates records that do not have all mandatory fields maintained. Before those

can be checked in, the user has to correct the issues.

Note

The predefined import map for Vendor import does not launch the workflow

automatically. You have to change the import map first using the Import Manager. After loading the map, choose Configuration Options in the top menu. Change property Checkout/Workflow and select the workflow you want to start automatically after a data

import.

MDM Syndication

This is a sample workflow usable to distribute records with the Data Manager. By adding records manually to this workflow and executing it, you trigger the syndication via a configured port. Ensure that MDSS is running for a successful distribution.

2.5 Import and Syndication Content

Import and syndication content consists of:

Remote System templates within the repository for SAP BI and SAP ERP.

XML Schemas usable for data import and syndication. The XSD files are delivered additionally as a part of the downloadable content, too.

GenericVendor describes the message structure for sending generic Vendor records to

SAP BI.

“ReferenceData R/3 & ERP describes the message structure for importing reference

data being extracted with MDMGX from a SAP R/3 or ERP system.

“CREMDM04 describes the message structure for importing MDM Vendor records being

extracted with MDM_CLNT_EXTR from a SAP remote system respectively for sending MDM Vendor records to a SAP remote system. The structure itself is synchronized with the related SAP ERP IDoc.

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

Import and Syndication ports for automated import and distribution using MDIS respectively MDSS.

(22)

2.6 Performance Tuning

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

2.6.1 Key Mapping

The 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 system usually contain a lot of codes instead of texts. Especially for lookup tables key mapping is used to ensure that the correct code is used for the same value.

(23)

Example

Your 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 with two remote keys (GER for remote system A and DE for remote system B). This ensures that during the import of master data the code that is used in the message is mapped to the correct lookup value.

Key mapping itself has some impacts on the loading of the repository and the syndication. It takes more time to create additional indices for key mapping. The distribution of key mapping is slower than the distribution of lookup values.

If you are sure that your reference data is 100% identical in your remote systems (following the example above: each of your remote system uses DE as code for country Germany) you could think about including the key mapping codes as single fields of the lookup table and disable the Key

Mapping option of the table in MDM Console.

Note

The predefined import and syndication maps are built using the key mapping on lookup tables. If you change the settings in MDM Console, you have to redefine the maps accordingly.

2.6.2 Keyword and Sort Indices

Each field of a MDM repository can be added to the keyword and/or sort index. The keyword index enables the keyword search for this specific field. The sort index enables sorting all repository records upon the field (refer to the MDM Console Reference Guide for details). Both settings can be done when 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. The table lists all fields with enabled properties for the Vendor repository:

Table / Tuple Field Sort Keyword

Vendors ID X Vendor Number X X Full Name X X Search Term 1 X X Search Term 2 X X Full Address X X City X

City Postal Code X

PO Box X

PO Box Postal Code X

VAT Registration Number X

Banks Bank Key X X

(24)

Table / Tuple Field Sort Keyword

Bank Address X X

Bank Details Bank X

Bank Account Number X

Account Holder X

Company Code Data Company Code X X

Payment Terms X X

Dunning Data Dunning Area X

Dunning Procedure X

E-Mail Addresses E-Mail Address X

Purchasing Organization Data ABC Classification X

Payment Term X X

Purchasing Organization X X

Web URI X

As the fields listed above are only a proposal, you should check if you require more or less fields for keyword search and/or sorting.

Recommendation

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

2.6.3 Search Tabs

Search Tabs are defined on field level. They are useable for lookup (flat & hierarchy) fields only. The property activates the Search Tab in the Search Parameters pane of MDM Data Manager.

The following list shows all fields having an activated Search Tab:

Vendors Account Group, Central Posting Block, Central Purchasing Block, Central Deletion Flag, Country, Gender, Industry Sector, Forwarding Agent Freight Group, Language, Natural Person, PO Box Country, Region, Region for PO Box, Tax Number Type, Tax Type, Title, Transportation Zone

Banks Bank Country

Company Code Data Company Code

Dunning Data Dunning Area, Dunning Procedure

Phone Numbers Phone Number Type

(25)

Web URI Type

As the fields listed above are only a proposal, you should check if you require more or less fields using the Search Tab in MDM Data Manager.

(26)

3. MDM Vendor PI Content

3.1 Overview

The PI content for MDM delivers interfaces, interface mappings and communication channel templates tailored to the supported SAP remote system and the shipped MDM repositories. In addition it delivers integration scenarios that reduce the manual effort required to define the communication between MDM and the SAP remote systems.

The “Software Component Versions for Remote System Message Types” section lists the additional software component versions needed in PI to process IDoc 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 to transform 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/MDEApplicationContent

Software Component Versions: 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 Installation

You can download the MDM PI Content from SAP Software Distribution Center.

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 (in case 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 Application Group”. Then continue on the main web page “SAP NetWeaver SAP MDM SAP NETWEAVER MDM 7.1”.

Note

The 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 Entry by 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 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.

(27)

3.3 Software Component Versions for Remote System Message Types

SAP remote system IDoc (sent to MDM) IDoc (received from MDM)

CREMDM CREMAS ADRMAS

R/3 Enterprise 4.71 PI 2004_1_470 SAP APPL 4.7 SAP ABA 6.20 ERP 2004 / ECC 5.0 PI 2004_1_500 SAP APPL 5.0 SAP BASIS 6.40 ERP 2005 / ECC 6.0 + EhP 2 + EhP 3 + EhP 4 + EhP 5 SAP APPL 6.0 SAP APPL 6.02 SAP APPL 6.03 SAP APPL 6.04 SAP APPL 6.05 SAP APPL 6.0 SAP APPL 6.02 SAP APPL 6.03 SAP APPL 6.04 SAP APPL 6.05 SAP BASIS 7.00 SAP BASIS 7.00 SAP BASIS 7.00 SAP BASIS 7.01 SAP BASIS 7.02

SAP remote system Proxy XML structures (sent to MDM)

Proxy XML structures (received from MDM) GenericVendorOut GenericVendorIn

NW 2004s BI 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.

1

(28)

3.3.1 Business Scenario: MDM710_Inbound

MDM 7.1 Inbound Processing – SAP remote system sending data to MDM server

MDSReceivesData MDM7.1

Sender Communication Channel Template [none] Systems based on NW2004

MDC Sends Data

Outbound Interface Interface Mapping Inbound Interface Receiver Communication Channel Template R/3 47x110 CREMDM.CREMDM04 PI 2004_1_470 Cremdm04_470AddressFilterIn MDM BUSINESS CONTENT 7.1 (7.00) CREMDM.CREMDM04 PI 2004_1_470 FTP_CREMDM_MDMIn MDM BUSINESS CONTENT 7.1 (7.00) ERP 2004 CREMDM.CREMDM04 PI 2004_1_500 Cremdm04_500AddressFilterIn MDM BUSINESS CONTENT 7.1 (7.00) CREMDM.CREMDM04 PI 2004_1_500 FTP_CREMDM_MDMIn MDM BUSINESS CONTENT 7.1 (7.00) Systems based on NW 7.0 MDC Sends Data

Outbound Interface Interface Mapping Inbound Interface Receiver Communication Channel Template ERP 2005 CREMDM.CREMDM04 SAP APPL 6.0 Cremdm04_600AddressFilterIn MDM BUSINESS CONTENT 7.1 (7.00) CREMDM.CREMDM04 SAP APPL 6.0 FTP_CREMDM_MDMIn MDM BUSINESS CONTENT 7.1 (7.00)

(29)

3.3.2 Business Scenario: MDM710_Outbound

MDM 7.1 Outbound Processing – MDM Server sending data to SAP remote system MDS Sends Data MDM 7.1

Systems based on NW2004

MDC Receives Data

Outbound Interface Sender Communication Channel Template

Interface Mapping Inbound Interface Receiver Communication Channel Template R/3 4.7x110 CREMDM.CREMDM04 PI2004_1_470 FTP_CREMDM_MDMOut MDM BUSINESS CONTENT 7.1 (7.00) Cremdm04_470ToCremas04_470Out MDM BUSINESS CONTENT 7.1 (7.00) CREMAS.CREMAS04 SAP APPL 4.70 IDOC_Receiving_MDMOut MDM BUSINESS CONTENT 7.1 (7.00) “ “ Cremdm04_470ToAdremas02_470Out MDM BUSINESS CONTENT 7.1 (7.00) ADRMAS.ADRMAS02 SAP ABA 6.20 IDOC_Receiving_MDMOut MDM BUSINESS CONTENT 7.1 (7.00) ERP 2004 CREMDM.CREMDM04 PI2004_1_500 FTP_CREMDM_MDMOut MDM BUSINESS CONTENT 7.1 (7.00) Cremdm04_500ToCremas04_500Out MDM BUSINESS CONTENT 7.1 (7.00) CREMAS.CREMAS04 SAP APPL 5.0 IDOC_Receiving_MDMOut MDM BUSINESS CONTENT 7.1 (7.00) “ “ Cremdm04_500ToAdremas03_500Out MDM BUSINESS CONTENT 7.1 (7.00) ADRMAS.ADRMAS03 SAP ABA 6.40 IDOC_Receiving_MDMOut MDM BUSINESS CONTENT 7.1 (7.00)

(30)

Systems based on NW 7.0

MDC Receives Data

Outbound Interface Sender Communication Channel Template

Interface Mapping Inbound Interface Receiver Communication Channel Template ERP 2005 CREMDM.CREMDM04 SAP APPL 6.0 FTP_CREMDM_MDMOut MDM BUSINESS CONTENT 7.1 (7.00) Cremdm04_600ToCremas05_600Out MDM BUSINESS CONTENT 7.1 (7.00) CREMAS.CREMAS05 SAP APPL 6.0 IDOC_Receiving_MDMOut MDM BUSINESS CONTENT 7.1 (7.00) “ “ Cremdm04_600ToAdremas03_600Out MDM BUSINESS CONTENT 7.1 (7.00) ADRMAS.ADRMAS03 SAP Basis 7.00 IDOC_Receiving_MDMOut MDM BUSINESS CONTENT 7.1 (7.00) NW2004s BI GenericVendorOut MDM BUSINESS CONTENT 7.1 (7.00) FTP_GenericVendor_MDMOut MDM BUSINESS CONTENT 7.1 (7.00) GenericVendorIn BI CONT 7.03 HTTP_Receiving_MDMOut MDM BUSINESS CONTENT 7.1 (7.00)

(31)

4. Web Dynpro Configuration

Starting with MDM 7.1 SP4 there is a new tool to create Java Web Dynpro UIs based upon a MDM repository. The new MDM Web Dynpro Configurator (see section Development and Customization

MDM Web Dynpro Components) supports you to fulfill this task. The existing documentation helps to include the new Web Dynpro UIs in a MDM project.

4.1 Deliverables

The current MDM content contains a predefined XML file for importing in the Web Dynpro

Configurator. The file is located in the business content ZIP file, next to the actual MDM repository. It is named MDM71800_VENDOR_WDC.xml.

The predefined UI consists of the following Web Dynpro Components for the both main tables: Search

Result Set Item Details

Note

All predefined Web Dynpro Components are templates only. You can change all components so that they fit exactly to your project requirements. Nevertheless it is not possible to combine two main tables into a single component.

4.1.1 Search

The search UI highlights both a Free-Form and a Lookup Search. You can change both according to your project needs.

4.1.2 Result Set

The result set defines a table displaying all records of a resulting search. The predefined result set uses the fields ID, Account Group, Full Name, Full Address, Company Code Data, and Purchasing

Organization Data. It allows the export of the result records as XML. You can change the fields and

settings according to your project needs.

4.1.3 Item Details

The item details component consists of all main table fields and tuples. The sorting of the fields and tuples into the different tabs is similar to the UI layout in SAP ERP remote systems. Nevertheless you can change the full UI according to your project needs.

4.2 Usage

The Web Dynpro Configuration is currently not used by any consumer. It is a stand-alone delivery that shall support you to create your own Web Dynpro based applications on the repository. Refer to the

Web Dynpro Component How-to Guide (see section Development and Customization MDM Web Dynpro Components) for details.

If you have setup the Web Dynpro Components with the predefined default values, you can immediately check the Vendor UI with the following link:

http://<host>:<port>/webdynpro/dispatcher/sap.com/tc~mdm~wdcomps~master~wd/MASTER?proj= VENDOR&rs=VENDOR_RESULT&s=VENDOR_SEARCH&id=VENDOR_DETAILS

(32)

5. Sample Data

The Vendor content contains a file named “Data.zip”. This MDM Vendor data package contains two types of data files.

All files within the "MasterFiles" folder are those XML files that have been used by SAP to create the import maps. The master files MUST NOT be used for data import 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 MUST NOT 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 batch files, 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 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 shared MDS folder, please check http://support.microsoft.com/kb/156276/en for details.

(33)

6. Import of Reference Data

You extract customizing data from SAP remote systems using the generic customizing data extractor

MDMGX (see MDMGX Documentation for details). The configuration file “MDMGX_71800_Vendor.txt” is available in the downloadable Business Content.

CAUTION

SAP remote system R/3 4.7 has a limitation regarding the length of the MDMGX port. Its name must not exceed 30 characters. You have to adjust the following ports by both renaming the port in the MDMGX text file and changing the related port code in the repository. Affected ports are:

Activity Codes For Social Insurance (34) Interest Calculation Frequencies (32) Interest Calculation Indicators (32) Price Determination Date Controls (33) Profiles For Material Data Transfer (34) Regional Structure Check Status (31) Refer to SAP Note 1391292 for details.

If you use the Vendor repository to consolidate more than one R/3 or ERP system, it makes sense to check and add some key mapping information for some of the Vendor lookup tables. The reason is that the customizing values you extract from the various systems might differ. This should be checked and corrected before loading any object data.

The predefined import maps use the customizing values for matching (the names/descriptions but not the keys/codes). That means if you load reference data from multiple remote systems, MDIS checks if the value already exists depending on its name. If yes, it updates the key mapping information of the existing record; if not, it creates a new record. MDIS is only able to identify perfect matches. Slightly different values lead to different records.

Note

The following chapters describe some tips regarding the import of reference data.

6.1 Banks

Main table Banks contains the Bank Master Data (like name of the bank, bank address, and so on). Although the data is designed as a main table, it is used a lookup for each Vendor record only. The link between the Vendors and the Banks main table is established in the Vendor’s tuple Bank Details. The import of Bank Master Data happens with MDMGX. Related customizing entries are maintained in the MDMGX text file. The import of Bank Details is part of the Vendor import.

CAUTION

The Bank Master Data in the repository has been enhanced to cover more information from the related ERP Bank Master table BNKA. The enhancement includes an update of the related MDMGX Bank Details extractor, too. Ensure that you have applied SAP Note 1349089 to your ERP system before you start the load of reference data into your repository!

(34)

6.2 Lookup Hierarchy Tables

Starting with the release of MDM 7.1 SP4 the MDMGX content of the Vendor uses the new function module MDM_ERP_MULTI_HIERARCHIES_EXTR to extract customizing data for its hierarchy lookup tables. The default configuration does not use the parameter SHOWMISSINGTRANSLATION.

The Name field of a hierarchy is usually built upon the combination of texts (e.g. the Region shows the Country Name and the Region Name). MDMGX needs to deliver a concatenated text so that Import Manager respectively MDIS are able to split the text into a hierarchy during import. As the texts are usually extracted from different customizing tables, there are a few combinations possible regarding the multilingual definition of the hierarchy name field:

MDM Console Source Parent Source Child MDMGX action Name field is multilingual Text is multilingual Text is multilingual

Extract and concatenate parent and child texts in multilingual versions Name field is multilingual Text is not multilingual Text is multilingual

Extract the default text of the parent and concatenate it with the multilingual version of the child. This is the case for all multilingual hierarchies that relate to the Company Code or Plant as neither the company code nor the plant text is not multilingual

Name field is not multilingual Text is not multilingual Text is not multilingual

Extract and concatenate parent and child texts in the default versions

Name field is not multilingual Text is multilingual Text is not multilingual

Extract the parent text in the logon language of the user that performs the extraction.

Concatenate the default version of the child text. This is the case for the hierarchy lookup tables Payment Methods, Regional Structure

Districts and Withholding Tax Codes. You can

control the language version of the parent text by logging on to the SAP remote system with a different logon language.

CAUTION

Ensure that you have applied SAP Notes 1403879, 1404964 and 1407978 to enable the import of the new lookup hierarchy tables in your ERP remote system.

6.3 Unique Constraints

Flat and hierarchy lookup tables use unique constraint for their specific code fields. The code is usually a clone of the record’s remote key. The unique constraint ensures a high quality of your reference data.

When you import reference data for multiple remote systems, MDM Import Manager and/or MDIS check the unique constraints. This prevents importing invalid names for the same code values. The import fails with the structural or value exception “Unique constraint violation” so that you can check your customizing values accordingly.

(35)

Example

Your system landscape consists of two remote systems. System A contains a country Germany having the code DE. System B contains country Gremany having the code DE. The import of System A’s reference data works fine. The import of System B’s reference data fails due to a unique constraint violation.

The reason is that MDM Import Manager respectively MDIS match on the Country name. In this case Germany differs from Gremany. MDM Import Manager respectively MDIS try to create a new record for Gremany. This new record would have the Code DE – but this code already exists in the repository. To indicate this issue, the unique constraint

violation is thrown.

To clean up the issue, you can either adjust the mapping in MDM Import Manager or correct the wrong customizing entry in your remote system and re-extract the correct values (which is the recommended solution, of course).

CAUTION

MDM Import Manager and MDIS check all fields for unique constraints that are defined as unique fields in MDM Console. If the unique field is multilingual, each language layer is checked independently for unique constraints. Additionally remote keys must be unique, too.

6.4 Import Sequence

Each lookup table of the MDM Vendor repository can be imported automatically using MDIS. Related ports are part of the repository. Importing reference data requires a specific sequence as some of the lookup tables depend on each other. To ensure a correct sequence of importing, the Vendor content uses the MDMGX Process Level concept. The lists below show the ports using process levels 0 to 2.

CAUTION

You have to execute MDMGX three times: one time for each process level. Before you start the extraction of process level 1, make sure that MDIS has successfully imported all files of process level 0.

Process Level 0 Port Port LT_AccountGroups LT_ActivityCodesForSocialInsurance LT_ActivityProfiles LT_ActualQMSystems LT_BlockFunctions LT_BusinessTypes LT_CommunicationTypes LT_CompanyCodes LT_ConfirmationControlKeys LT_Countries LT_Currencies LT_DeliveryServiceTypes LT_DMEIndicators LT_DunningBlocks LT_DunningNoticeGroupingKeys LT_DunningProcedures LT_ExemptionAuthorities LT_FactoryCalendars LT_FreightGroups LT_Genders LT_GroupsForCalculationSchema LT_Incoterms

(36)

Port Port LT_IndustrialSectors LT_IndustryTypes LT_InterestCalculationFrequencies LT_InterestCalculationIndicators LT_Languages LT_MinorityIndicators LT_PaymentAdvicesByXML LT_PaymentBlocks LT_PaymentGroupingKeys LT_PaymentMethodSupplements LT_PaymentTerms LT_PeriodicAccountStatements LT_PhoneNumberTypes LT_PlanningGroups LT_Plants LT_PODIndicators LT_PrepaymentRelevances LT_PriceDeterminationDateControls LT_PriceMarkingAgreements LT_ProfilesForMaterialDataTransfer LT_PurchasingGroups LT_PurchasingOrganizations LT_RegionalStructureCheckStatus LT_RegionalStructureGroupings LT_ReleaseApprovalGroups LT_RestrictionProfiles LT_ServiceAgentProcedureGroups LT_ShippingConditions LT_SortCriteriaForMaterials LT_SortKeys LT_SubsidyIndicators LT_TaxBases LT_TaxNumberTypes LT_TaxTypes LT_TimeZones LT_Titles LT_TransportationChains LT_TransportationServiceAgents LT_UndeliverableReasons LT_UnitOfMeasureGroups LT_URITypes LT_YesNoIndicator Process Level 1

Port Dependent Port

LT_Clerks LT_CompanyCodes LT_CustomsOffices LT_Countries LT_DunningAreas LT_CompanyCodes LT_HouseBanks LT_CompanyCodes LT_ModesOfTransport LT_Countries LT_PaymentMethods LT_CompanyCodes LT_PlanningCalendars LT_Plants LT_RecipientTypes LT_CompanyCodes LT_ReconciliationAccounts LT_CompanyCodes LT_RegionalStructureCities LT_Countries

(37)

Port Dependent Port LT_RegionalStructureStreets LT_Countries LT_Regions LT_Countries LT_RoundingProfiles LT_Plants LT_ToleranceGroupsBupaGl LT_CompanyCodes LT_ToleranceGroupsInvoice LT_CompanyCodes LT_TradingPartners LT_Countries LT_TransportationZones LT_Countries LT_WithholdingTaxCodes LT_CompanyCodes LT_WithholdingTaxCountries LT_CompanyCodes Process Level 2

Port Dependent Port

LT_BankDetails LT_Regions

(38)

7. Import of Master Data

7.1 Message Flow

You extract master data from SAP ERP remote systems using the generic master data extractor

MDM_CLNT_EXTR (see MDM CLNT_EXTR Documentation for details). The import requires a correct setup of the SAP remote systems and PI. Refer to the IT Scenario Configuration Guide available on

SAP Service Market Place and chapter MDM Vendor PI Content of this note for details.

The (recommended) message flow between SAP ERP remote systems and MDM is realized with the CREMDM IDoc type. MDM_CLNT_EXTR is able to collect ERP vendor records into this IDoc. The IDoc is transferred via the IDoc Adapter from ERP to PI. PI is responsible for the transformation of the IDoc into a XML format (see Interface (XSLT) Mapping) and the correct routing to MDM. The transfer from PI to MDM is either done via FTP or the MDM PI Adapter.

7.2 Interface (XSLT) Mappings

The Vendor repository is able to import XMLs having the same structure as the CREMDM IDoc. The Interface (XSLT) Mappings provided by the Vendor PI content do not perform any changes regarding the message structure.

Nevertheless the mapping is mandatory as some segment specific values mappings are happening on PI.

International Address Versions of the segments <E1BPAD1VL> (address data) and <E1BPAD_REM>

(address notes) are filtered on PI.

The value for the Payment Methods in segment <E1LFB1M/ZWELS> needs to be re-formatted so that Import Manager respectively MDIS is able to import the data into the multi-valued hierarchy lookup table. The data in the IDoc is a single string consisting of the remote keys of the payment methods. The required format is a coma-separated string including the related company code for each payment method.

Example

A record for Company Code 0001 in ERP has four payment methods 1, 7, A, and C. The

<BUKRS> element in the company code data segment <E1KNB1M> carries the value

0001. The payment method element <ZWELS> in the same segment carries the value 17AC. The XSLT mapping on PI transforms the <ZWELS> value into the required format 00011, 00017, 0001A, 0001C. Import Manager respectively MDIS are now able to map the single field to the corresponding entries of the hierarchy lookup table.

7.3 Field Mappings

Field mappings are generally listed in the attached Excel file Field Mapping and Check Tables

Vendor.xls. In a few cases the Vendor Import Map uses partitions and/or cloned fields to concatenate

and/or duplicate some values:

Dest. Table / Tuple Destination Field Source Field(s)

Vendors Remote Key Clone: <E1LFA1M> LIFNR

Region Partition: <E1BPAD1VL> COUNTRY <Clone> + REGION

MDM 71 Vendor Content Information

MDM Content