You are on page 1of 6

Coordinates a team or programmer analyst in the analysis, design, development, training, implementation, and maintenance for all custom

software development including file server based database applications, client server based applications, and intranet/web based applications. MDM 7.1 Upgrade Consultant Required skills: Proficient in defining\configuring MDM approval workflow. Proficient in configuring and implementing MDM Import server. Ability to document all work done and provide documentation in a clear, detailed, and easy to follow format. Desired skills Experience with MDM CLIX (OS level scripting type MDM tool that allows you to write OS level scripts to perform various MDM tasks such as archiving repositories, etc.) Proficient MDM data modeling experience in order to review our current repositories and recommend any performance improvements

SAP MDM Administrator

SAP MDM Admin resource with 3+ years of MDM administration experience. Must have - Understanding of MDM application landscape - Understanding of MDM integrations with other systems - experience of MDM Server Installation and Upgrade activities - experience of MDM Server monitoring - Basic MDM application skills

Integrate Different Source systems using MDM

You can export data from R/3 using IDOCs, Proxy etc and then using PI (Middleware) convert this data to XML file format and then data can be imported into MDM using XML file format. Now when you have to syndicate data out of MDM you can export it in the form of Text file, XML file which then through PI (Middleware) get converted into IDOC, Proxy structure of R/3 system and then can imported into R/3 systems. Oracle can export and import data in the form of External file, you can either use this File format to import data into MDM or you can directly connect to Oracle database through Import Manager. Now during syndication data out of MDM you can send this data in the form of text files and then can import data into Oracle or you can also make use of PI (Middleware) to convert your MDM data Flat/XML file into Oracle structure (using JDBC Adapter) and then import data into Oracle. Note: Data is imported into MDM using MDM Import Manager where you can select type as XML file, flat file etc, you can also

select there Type as Oracle directly to import data into MDM using MDM import Manager.

SAP Remote System Integration

Link to this Page Link Tiny Link OK Wiki Markup Cancel Close Click to select the Move Page SA Search Error reading the Set Page Location Move Recently View ed

There w ere no re Know n Location You must make a

The specified pag Brow se Failed to retrieve MDM Content & P Back Cancel Reorder Close

You could try relo HTTP Status Move failed. Ther SAP Master Data Unknow n user or 168722568

There w ere no pa Show ing <b>{0}< SAPMDM Move Save

You cannot move SAP Remote Sys You cannot move Page Ordering Page Restrictions Editing restricted


Page restrictions apply Added by Deepak Gupta, last edited by Michael Theis on Mar 16, 2010 (view change) show comment hide comment

Comment: layout

Steps that are required to integrate MDM with a SAP Remote System

The various steps below are needed to make a integration between ERP/CRM/SRM, PI and MDM. These are not the universal steps and can be modified. 1. Activation of Standard Business Content. 2. SAP ERP/CRM/SRM - SAP PI integration settings. 3. SAP PI - SAP MDM integration settings. 4. Creation / Import of source Structure and Target Structure. 5. Extraction of Check Table Data, e.g. using MDMGX 6. Extraction of Main Table Data, e.g. using MDM_CLNT_EXTR 7. Conversion of IDOC to XML (usually done by SAP PI) 8. Import of Check Table and Main Table Data in MDM.

9. Setting up matching strategy for de-duplication 10. Running a matching strategy. 11. Duplicate record merging. 12. Data enrichment. 13. Syndication of Consolidated Master records by MDM. 14. Conversion of XML to IDOC-Posting (usually done by SAP PI) 15. Check and use consolidated Record in SAP System. The steps are applicable if we are dealing with some specific Master Data object like vendor, customer, and so on, and by doing all these we are making the Consolidation and Harmonization of Master Data which is coming from ECC and PI as a Middleware and operated at MDM.

Note 1412742 - MDM Customer Content Information (Release MDM 7.1+)

Summary Symptom Your goal is the consolidation and/or harmonization of Customer Master data from one or more SAP R/3 respectively SAP ERP system(s). You use SAP NetWeaver MDM for this purpose. You're looking for pre-defined business content (like MDM repositories, import and syndication maps, portal content, and so on) that helps you to reach your goal. Other terms Addresses, ADRMAS, Customer, DEBMAS, DEBMDM, Master Data Consolidation, Master Data Harmonization, MDC, MDH, MDM, MDMGX, MDM_CLNT_EXTR Reason and Prerequisites Using the MDM Business Content for Customer Master Data requires at least the SAP NetWeaver MDM release 7.1 SP4. The content as described in this note does not support older MDM releases. The MDM 5.5 version of the customer content is described in note 1252884. If a new version of MDM will be released in future, the content will be updated accordingly. Solution The MDM 7.1 Customer content features the latest MDM 7.1 modelling capabilities. Tuples are used to replace the Qualified Lookup Tables as tuples offer much more flexibilty and features for data modeling. Multiple Main Tables and lookups to main tables are used to enrich and simplify the data model (e.g. the new main table for Bank Master data). This note consists of several documents that are available as attachments. If you want to use the MDM 7.1 Customer content, it is strongly recommended to get familiar with each of the documents: MDM 7.1 Customer Content MDM 7.1 Customer Match and Merge MDM 7.1 Customer Field Mappings and Check Tables MDM 7.1 Customer Content Strings

Usage of the MDM Content

The SAP MDM Customer content supports the generic MDM scenarios Consolidation and Harmonization only. You cannot use this content for a central Maintenance of Master Data. If you want to do this, please contact SAP or your SAP Consultant. MDM 7.1 Customer Content MDM 7.1 Customer Content is a PDF Document that contains the documentation of the predefined business content. Its table of contents is listed below: 1. MDM Customer Content 2. MDM Customer Repository 2.1 MDM Repository Files 2.2 Repository Structure: Overview, Tables and Fields 2.3 Users and Roles 2.4 Repository Values: Validations, Matching Content, Workflows 2.5 Import and Syndication Content 2.6 Performance Settings 3. MDM Customer PI Content 3.1 Overview 3.2 Download and Installation 3.3 Software Component Versions for Remote System Message Types: MDM710_Inbound and MDM710_Outbound 4. MDM Web Dynpro Configuration 4.1 Deliverables 4.2 Usage 5. Sample Data 6. Import of Reference Data 6.1 Banks 6.2 Lookup Hierarchy Tables 6.3 Unique Constraints 6.4 Import Sequence 7. Import of Master Data 7.1 Message Flow 7.2 Interface (XSLT) Mappings 7.3 Field Mappings 7.4 Value Mappings 7.5 Import of Lookup Main Relationships: Bank Details and Main Table Customers 7.6 Import of Tuples 7.7 MDIS usage

8. Syndication of Master Data 8.1 Message Flow 8.2 Interface (XSLT) Mappings 8.3 Field Mappings: Bank Details & Bank Master 8.4 Predefined Field Values for DEBMDM06: Begin & Segment Attributes, Message Function & Address Element 8.5 Predefined Field Values for GenericCustomer 8.6 Completion of the delivered Map Templates 8.7 MDSS usage 9. Known Issues and Limitations 9.1 Data Modeling: Communication Comments, International Address Versions, Payment Transactions, Time Dependency, Schema Transport & Validation Groups 9.2 Data Distribution: Import/Syndication from/to CRM and SRM, Import into Tuples, Out of Memory issues during Import, MDM PI Adapter Usage 9.3 Data Processing Merge of Records with Lookup Main Relationships, Portal Maintenance for Main Table Banks, Hierarchy table Validations 10. Change History 11. Related Information 12. MDM 7.1 vs. MDM 5.5 Customer 13. SAP ERP Customers MDM 7.1 Customer Match and Merge MDM 7.1 Customer Match and Merge is a PDF document that describes the predefined Customer matching content using the available sample data. You can use this document for an out of the box demonstration of MDM capabilities without having the need to configure a full system landscape. Its table of contents is listed below: 1. Introduction 1.1 MDM Customer Repository 1.2 MDM Data Manager 2. Transformations 2.1 Special Characters 2.2 Organization Abbreviations and Names 2.3 Address Abbreviations and Names 2.4 Customer Transformation: Company Name 2.5 Customer Transformation: Full Name 2.6 Customer Transformation: Full Address 2.7 Customer Transformation: Search Term 3. Rules 3.1 Customer Rule: Full Name

3.2 Customer Rule: Full Address 3.3 Customer Rule: Search Term 1 3.4 Customer Rule: Search Term 2 3.5 Customer Rule: VAT Registration Number 4. Strategies 4.1 Customer Strategy: Full Customer Matching 5. Matching and Workflows 5.1 Workflow Definition 5.2 Workflow Execution 6. Matching the Customer Sample Data 6.1 Setting up the Sample Data Scenario 6.2 Matching with the Sample Data 6.2.1 Overview 6.2.2 Matching & Match Results 6.2.3 Calculation of the Matching Score 6.2.4 Merge Records (I) 6.2.5 Merge Tuples 6.2.6 Merge Records (II) 6.2.7 Check Key Mapping 7. Related Information MDM 7.1 Customer Field Mappings and Check Tables MDM 7.1 Customer Field Mappings and Check Tables is an Excel File that contains all tables and fields of the MDM repository. The list shows all related tables and fields in a SAP ERP remote system as well as in the DEBMDM IDoc. MDM check tables (lookup tables) are mentioned with their related SAP ERP remote system fields and tables. MDM 7.1 Customer Content Strings MDM 7.1 Customer Content Strings is an Excel file that contains all strings (field and table names) used within the MDM repository. The strings are translated into all supported languages. Use this file to keep your MDM Customer repository updated with the latest translation.

Note 1355137 - MDM Material Content Information (Release 7.1+)