Mdm100 master data_management

InternalUseSAPPartnerOnly
 SAPAG 2006
MDM100
THE BEST-RUN BUSINESSES RUN SAP
© SAP AG2007
MDM100
Master Data Management
NetWeaver 2004s
2006/Q2
Materialnumber: 50082547

 SAPAG 2006
Copyright
Copyright 2007 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in
any form or for any purpose without the express permission of
SAP AG. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Excel, 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, System i, System i5, System p, System p5, System x, System
z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER,
POWER5, 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.
The information in this document is proprietary to SAP. No part of this document may be reproduced,
copied, or transmitted in any form or for any purpose without the express prior written permission of
SAP AG.
This document is a preliminary version and not subject to your license agreement or any other
agreement with SAP. This document contains only intended strategies, developments, and
functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course
of business, product strategy, and/or development. Please note that this document is subject to change
and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the
accuracy or completeness of the information, text, graphics, links, or other items contained within this
material. This document is provided 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 have no liability for damages of any kind including without limitation direct, special, indirect,
or consequential damages that may result from the use of these materials. This limitation shall not apply
in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. 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.

 SAPAG 2006
Recommended Knowledge:
No prerequisites required
Course Prerequisites

 SAPAG 2006
This course is intended for the following audiences:
Project team member and Solution Consultants
needing knowledge of Master Data Management
Duration: 5 days
Target Audience
User notes
These training materials are not a teach-yourself program. They complement the explanations
provided by your course instructor. Space is provided on each page for you to note down additional
information.
There may not be sufficient time during the course to complete all the exercises. The exercises provide
additional examples that are covered during the course. You can also work through these examples in
your own time to increase your understanding of the topics.

 SAPAG 2006
Course Goals
This course will prepare you to:
Attain knowledge of the features and options to
support a customer implementation employing the
current version of MDM

 SAPAG 2006
Course Objectives
After completing this course, you will be able to:
Describe the features and options of MDM in the
implementation of a variety of IT or Business
Scenarios

 SAPAG 2006
Course Overview Diagram (1)
Unit 1 MDM Overview
MDM Introduction
MDM Data Manager
Unit 2 Data Modeling
Import Manager
Qualified Tables
Hierarchies
Taxonomy
Unit 3 Advanced MDM Features
Matching Mode
Workflow
Relationships
Syndicator
MDM Automation
Multilingual Support
Expressions
Import Manager Advanced
Console
Unit 4 Outputs

 SAPAG 2006
Course Overview Diagram (2)
Unit 6 Integration Scenarios within
SAP NetWeaver
Portal Integration
Open Catalog Integration
XI Integration
ECC Communication
BI Integration
Customer Data Integration
Master Data Harmonization
Rich Product Content
Management
Global Data Synchronization
Unit 7 IT & Business Scenarios
Security and Permissions
Performance
Directory Server Integration
Unit 5 Landscape
Computing Center
Management System

 SAPAG 2006
Main Business Scenario
Your company has a heterogeneous IT landscape with
several systems each containing the master data objects of
materials, customers, vendors, and employees. While
communicating material information to vendors and
customers, confusion has ensued where disparate and/or
contradictory data concerning the same materials have been
sent numerous times to the same vendor and customer.
Because of this, it has been very difficult to establish a
centralized web catalog of products searchable by
customers.
Further, poor data synchronization between your company’s
systems has resulted in slow and inaccurate partner and
supplier communications. Your company has decided that it
needs a Master Data Management solution to alleviate these
problems and would like to understand the capabilities of
SAP NetWeaver MDM.

(C) SAP AG MDM100 1-1
 SAPAG 2006
Unit 1: MDM Overview: MDM Introduction
Unit 1 MDM Overview
MDM Introduction
MDM Data Manager
Import Manager
Qualified Tables
Hierarchies
Taxonomy
Matching Mode
Workflow
Relationships
Syndicator
MDM Automation
Expressions
Console
Unit 4 Outputs

 SAPAG 2006
Contents:
Discussion of what is master data
Introduction to SAP NetWeaver MDM
Introduction to the IT and Business Scenarios which utilze
MDM
SAP NetWeaver MDM Introduction

 SAPAG 2006
SAP NetWeaver MDM Introduction: Unit Objectives
After completing this unit, you will be able to:
Understand the need for Master Data Management
Appreciate the value of SAP MDM
Introduction of the IT and Business Scenarios
See how MDM fits into the NetWeaver stack

 SAPAG 2006
SAP NetWeaver MDM Introduction: Business Scenario
Your company would like to compare the use of
SAP NetWeaver MDM to the use of mySAP ERP as a
master data repository.

 SAPAG 2006
Master Data Management Overview
IT and Business Scenarios
Architecture
Keys to Successful Projects

 SAPAG 2006
Inconsistent View of Business Data
Master data is generated and
trapped in silos YOUR BUSINESS
Call
Center
Jane Smith
4418 N. Str.
Chicago, IL
60611
Part: 2574
ERP
Jane Peters
199,3rd
Street
Palo Alto,
CA
Part: B7521
Every department has different information.
Your business today:
• Departmental silos create and perpetuate their own versions of master data.

 SAPAG 2006
Pervasive Challenges of Master Data Management
Enterprise Information Management Problem
JP Morgan Chase
“Without Master Data Management (MDM) capability, we believe it will be
challenging for any company to move to a services-oriented architecture.”
Pervasive Challenges of Master Data Management
Product Data Problem
Product to Market
Failure to capitalize on
market opportunity with NPI
Lacks real-time collaboration
with f ront off ice
Supplier Data Problem
Optimize Procurement
Lack of visibility into suppliers
and products
High spend costs
CEO / CFO / CIO
Create an IT f ramework that supports innov ation and growth with less budget
Eff ectiv ely manage all resources, including human capital, in a dy namic world of
mergers and acquisitions
Customer Data Problem
Sales and Marketing
Effectiveness
Lacks one v iew of customers
across all channels
Sub-optimal v iews impact
customer-f acing transactions
Inability to reduce procurement spend costs
• Inability to understand from whom and which products I buy worldwide
• Same suppliers and products classified in different categories, preventing easy comparison
Lack of customer insight to target each account with the right offer
• Impacts the ability to create longer, profitable customer relationships
• Lack of coherent data prevents anticipation of changing customer needs
Inability to collaborate by sharing information with key constituents
• Data silos prevent sharing information with customers, partners, suppliers, and so on
• No mechanism or process to share the same information internally and externally
Inability to modify or design new business processes
• Rigid connections to data sources
• Impedes innovation and differentiation
High integration costs with other key processes
• Heterogeneous landscape – lack of common infrastructure or technology platform
• Multiple point-to-point solutions with new islands of information

 SAPAG 2006
The Master Data Challenge
A problem experience by every company:
System A System B
Is this the same product represented in two different ways?
?Footwear
Prod # CategoryDescription
Safet yBootA124K
Master data describes key areas of your business
Customers (name, addresses, phone number)
Products (product attributes, list price)
Suppliers (parent entity, address, parts offered)
Employees (ID, name, title, address, organizational unit)
Master data is stored in multiple, disconnected systems/databases
Unmanaged master data is notoriously inaccurate, full of discrepancies,
incomplete, and leads to poor business decisions
Clothing
Prod # CategoryDescription
Safet yBootBR-2K
Inability to reduce procurement spend costs
• Inability to understand from whom and which products I buy worldwide
• Same suppliers and products classified in different categories, preventing easy comparison
Lack of customer insight to target each account with the right offer
• Impacts the ability to create longer, profitable customer relationships
• Lack of coherent data prevents anticipation of changing customer needs
Inability to collaborate by sharing information with key constituents
• Data silos prevent sharing information with customers, partners, suppliers, and so on
• No mechanism or process to share the same information internally and externally
Inability to modify or design new business processes
• Rigid connections to data sources
• Impedes innovation and differentiation
High integration costs with other key processes
• Heterogeneous landscape – lack of common infrastructure or technology platform
• Multiple point-to-point solutions with new islands of information

 SAPAG 2006
Inconsistent View of Partner Data
* Source: Global Commerce Study
YOUR VALUE CHAIN
Trading partners perpetuate their own views.
Master data is
generated and
trapped in silos
Trading partner
data introduces
yet another
version of data
ERP
Jane Peters
199, 3rd
Street
Palo Alto,
CA
Part: B7521
Call
Center
Jane Smith
4418 N. Str.
Chicago, IL
60611
Part: 2574
SRM
Part: 8975
VENDOR
ABC123
Logistics
VENDOR
XYZ456
Your trading partners:
• Trading partners perpetuate their own versions of master data. How do you share data?

 SAPAG 2006
SAP NetWeaver MDM
SAP NetWeaver MDM
One master data solution for all business processes
MANAGE CUSTOMER
W ho is my
customer?
VERIFY AVAILABILITY
Do I have the
right product?
IDENTIFY SUPPLIER
W ho is mybest
vendor?
TAKE ORDER
W hich employee
should we assign to?
One solution for ALL master data in your industry specific process

 SAPAG 2006
SAP MDM Uses
Fast searching of information
Formalizing and controlling master data management processes
Improving quality of reporting from multiple sources
Finding duplicate information
Mergers and migrations
Mass operations on data
Extending data accessibility
Improving and controlling data quality levels
Answering questions that were never asked
The MDM system is much more than a simple database application. Rather, it is an integrated system
for master data management that uses a database management system (DBMS), but completely bypasses
relational DB functions for almost all searching, sorting, and retrieving of information.

 SAPAG 2006
SAP NetWeaver MDM has …
UNIQUE FEATURES
MDM
Predefined and highly flexible object models
Pre-defined object models for customer, product, employee and supplier
Users can define their own model with a highly configurable schema
Rich repository handles both simple and complicated data taxonomy and
hierarchies
Content extraction and management
Import and rationalize data from any source
Comprehensive content and image management
Electronic and print publishing
Unbeatable performance, scalability, and flexibility
Handles simple and complex data seamlessly
Scales to millions of records
High performance parametric search
Easy to install and deploy
Easy installation and deployment within weeks
Ease to use, minimal training required
Multi-user collaboration

 SAPAG 2006
Consolidation
Ensure consistent master
data across systems
Actively Managing Master Data
Harmonization
Cleanse and distribute
across entire landscape
Central Management
Centrally create consistent
master data from the start
Data
Qualit y
Time
New Product
Launch
Master Data Management
Improve data quality in steps
M&A
Outsourcing
Consolidation
Harmonization
Central
MDMData
Qualit y
Time
Without consolidation,
doing business is
expensive
Automatically and continuously improve data quality
Business events continuously impact data quality.

 SAPAG 2006
Architecture

 SAPAG 2006
IT Scenarios with SAP MDM
Support of core IT scenarios and capabilities
Master Data Consolidation
Cleansing and de-duplication
Data normalization, including categorization and taxonomy
management
New interactive consolidation capabilities
Master Data Harmonization
Automated synchronization of globally relevant master data
information
New interactive distribution capabilities
Central Master Data Management
Central creation and maintenance of data
Ongoing master data quality

 SAPAG 2006
Core Business Scenarios with SAP MDM
Support of Core Business scenarios and capabilities
Rich Product Content Management (RPCM)
Powerful capabilities to load, aggregate, and search on parametric
product data
Intelligent image management and Web/print publishing
Global Data Synchronization (GDS)
Consistent trade item data exchange with retailers via data hubs
(for example, 1SYNC)
Customer Data Integration (CDI)
Consolidation and management of customer data from all available
sources
Customer data management capabilities such as matching,
standardization, and survivorship

 SAPAG 2006
SAP MDM: Key Concepts at a Glance
Delivers a single version of the truth, intra and inter-enterprise
Global Da ta
Synchronizati on
Intra-Enterprise
SAP NetWeaver (MD M)
An alytics
People Productivity
Inter-
Enterprise
Today’s Reality - Fragmented IT Systems
1. Mast er Data
Consolidation
Non-SAP SAP Legacy
Rich Produc t
Content
Ma nage ment
Customer
Data
Ma nage ment
Print/Online
Catalogs
2. Mast er Data
Harmonization/
Central Mgmt
Composite Applications
3. Process Enablement
Enterprise
Services
Repository
Platform
Process Components
Master data consolidation benefits: SAP MDM ensures data integrity with master data consolidation and
sets the stage for easy reuse via distribution or via business processes that directly leverage consolidated
data.
Master data harmonization benefits: SAP MDM ensures that as data changes in one application, other
business applications that depend on that data are updated with a consistent view of key data as it
changes in real time. This enables decision making based on accurate data.
Central master data management benefits: With SAP MDM, a central comprehensive repository can be
created with enriched content that can be used as the single source for all enterprise master data, both
inter-enterprise and intra-enterprise.

 SAPAG 2006
Publish
Benefits:
Complex product and
relationship management
Print/Web publishing, including
layout and production
GEAR
Parts
1038-GID
Example: Product information is
consolidated and enriched and
published internally or externally
Rich Product Content Management (RPCM)
A124K
Parts
GEAR
Gears
BR-2K
SPIDER
GEAR
One view of product information, anytime, anywhere
Using rich product-content management, companies can manage and exchange product data locally and
globally
• Manage internal content
• Search electronic catalogs
• Print customized catalogs
• Syndicate product catalog content via multiple channels (OCI, Web, print)
• Present role-based interfaces through a portal
Key capabilities
• High-performing load, aggregation and search of product data
• Multidimensional search
• Flexible taxonomy
• Intelligent imaging and Web/print publishing
• Application programming interfaces (APIs) for seamless, multiplatform integration
• Scalability (up to millions of products)

 SAPAG 2006
Data Pool
Global Data Synchronization (GDS)
Reduce supply chain costs
with a comprehensive solution
for consumer product
companies
Certified to publish enriched
product data to 1SYNC data
pools
Unidirectional communication
with SAP R/3
Data Pool
Global
Registry
SYNCHRONIZATION
Leverage master data consistency across the supply chain
Using global data synchronization, companies can manage and exchange product data locally and
globally:
• Reduce error-processing costs resulting from inconsistent product data
• Establish channels for exchanging standardized information with data pool (for example, 1Sync) for
further publication to trading partner
• Implement a quick but complete solution for complying with trading-partner requirements
• Integrate with mySAP ERP seamlessly and permanently
• Achieve a lower total cost of ownership, since global data synchronization (GDS) is based on your
existing landscape

 SAPAG 2006
Extensive matching
framework
Provides Web services for
customer data access
SAP and non-SAP integration
Analysis
Jane Smith
4418 N. Str.
Chicago, IL
60611
Customer Data Integration (CDI)
Jane Peters
199, 3r d
Street
Palo Alto, C A
94304
Jane Peters
Smith
4418 North St.
Chicago, IL
60610
One view of customer information, anytime, anywhere
CDI ensures that all relevant departments in the company have constant access to the most up-to-date
and complete view of customer data available.
CDI is an essential extension to Customer Relationship Management (CRM)

 SAPAG 2006
Understand your most
profitable products, best
customers, and cheapest/
most reliable vendors
Gain insights by integrating
transactional data from
heterogeneous systems with
master data for analysis
Improved Business Intelligence
+
TRANSACTION AL
DATA =MASTER
DATA
BUSINESS INSIGHT
Deliver unique insights with an integrated platform

 SAPAG 2006
Master Data Packages
Master data is key non-transactional information about your business.
Articles
Product attributes, dimensions,
weight
Color, shape, etc.
Business Partners
Supplier name, parent entity,
address
Phone numbers, other static
information
Customers
Customer name, addresses
information
Employees
Employee ID, name, title, address
Organizational unit, etc.
Materials
Material attributes, dimensions,
weight
Sales and location data
Products
Product attributes, dimensions,
weight
Color, shape, etc.
Suppliers
Supplier name, parent entity,
address
information

 SAPAG 2006
Architecture
Architecture

 SAPAG 2006
SAP MDM: Strategic Backbone of Enterprise SOA
Life Cycle Management
Legacy
System
Legacy
System
Third
Party
Third
Party SAPSAP
SAP NetWeaverSAP NetWeaver
An alytics
People Productivity
Composite Applications
Platform
Process Components
SAP NetW eaver MDM
Foundation for Enterprise SOA
MDM delivers an enterprise
information foundation for
Enterprise service-orientated
architecture
MDM enables flexibility and data
reusability through loosely
coupled business processes that
can access data easily
Business processes can leverage
MDM to automatically generate
data models
Enterprise Web services can
access SAP MDM seamlessly
SAP Analytics leverages MDM
and SAP NetWeaver Business
Intelligence
Enterprise
Services
Repository

 SAPAG 2006
First Steps to Enterprise SOA
Unify data
Unify customer, product, employee, supplier, and user-defined data
with one solution to build robust business processes
Industry insights
Supports 1SYNC, configurable for other industries
Easy deployment
Pre-built data models, mappings, and iViews
Accelerate new business processes with accurate master data

 SAPAG 2006
MDM Architecture: Major Building Block
Import Server
Parsing
Structural M appi ng
Value Mapping
Record Matching
KeyMapping
Thin Client
Search / Vi ew
Data Maintenance
OCI
User Interface
Rich Client
Console
Data Manager
Import Manager
Master Data Server
Core Ser vices
Memor yCache
Database Abstraction
Repositor yManagement
Syndication Server
Extraction
Structural M appi ng
Value Mapping
Number Assignment
KeyMapping
SAP NetWeaver XI SAP NetWeaver Application Server
Inbound Processing Outbound ProcessingAPI / Monitoring
SAP NetWeaver XI
Image M anager
Publisher
Syndicator
MDM

 SAPAG 2006
MDM
Server
MDM
Server
MDM User Interfaces
Data
Manager
Data
Manager
Image
Manager
Image
Manager
PublisherPublisher Import
Manager
Import
Manager
SyndicatorSyndicator
Language SelectorLanguage Selector
Console
PortalPortal
The MDM100 course will cover the MDM Server, Console, Data Manager, Import Manager,
Syndicator, and Language Selector. It will also discuss accessing MDM repositories using APIs via the
SAP Portal.
Image Manager and Publisher are covered in a different SAP course.

 SAPAG 2006
Portal Based Access
Multidimensional Search
Displaying Record Details
Fields
Attributes
Comparison
Relationships
Data Entry and Maintenance
Visualization of Key Mapping
Personalization (My Search, My Bags)
Integration to Universal Worklist
Inter-iView connectivity
Administrative options and utilities

 SAPAG 2006
Architecture

 SAPAG 2006
The Keys to Successful Projects
Partner / Customer / Projects
The right reason to start an MDM project
Corporate buy-in – business drivers
Cooperation of different lines of business (LOBs)
Proper scoping
Understanding technical and non-technical limitations

 SAPAG 2006
Scoping, Blueprinting, and Staffing
Defining scope is paramount
A blueprint should outline all requirements and challenges
It is hard to guestimate everything
Staffing requires more than one resource

 SAPAG 2006
Quick Deployment
Pre-built data models
Pre-built mappings
Pre-built iViews,
reports, and workflow
Easily configurable
Pre-built business content accelerates adoption
Consolidation
Harmonization
SAP
ERP
SAP
CRM
Non-SAP
Legacy
Applications
MDM
Data Manager
Central Ma ster Da ta
Ma nage ment
Portal (iVie ws)
Gui ded
proce dures, UW L,
reports
MDM Data Mana ger
Workflow
Validati on,
Ma tch/ merge,
Enrichme nt
Mas ter Data
Serv er
SAP XI MDM
Import
Serv er
MDM
Syndica tor
Serv er
Extractor
Mapping
Transactional system
Business Content

 SAPAG 2006
SAP NetWeaver MDM Introduction: Unit Summary
You should now be able to:
Understand the need for Master Data Management
Appreciate the value of SAP MDM
Introduction of the IT and Business Scenarios
See how MDM fits into the NetWeaver stack

 SAPAG 2006
MDM Data Manager
Unit 1 MDM Overview
MDM Introduction
MDM Data Manager
Import Manager
Qualified Tables
Hierarchies
Taxonomy
Matching Mode
Workflow
Relationships
Syndicator
MDM Automation
Expressions
Console
Unit 4 Outputs

 SAPAG 2006
Contents:
MDM Data Manager Application
Searching and modifying data
Saving searches
MDM Data Manager

 SAPAG 2006
MDM Data Manager: Unit Objectives
Explain the value of MDM Data Manager
Use MDM Data Manager record mode
Describe the detailed functions for
searching/creating records and adding data to the
existing repository

 SAPAG 2006
MDM Data Manager: Business Scenario
The user interface for the master data specialist is
the Data Manager and you would like to understand
the capabilities of this tool.

 SAPAG 2006
Introduction to Data Manager
Searches
Saving Searches
Changing Data
Summary
Check In/Out and Protect

 SAPAG 2006
MDM Data Manager: User Interface
MDM
server
MDM
server
Data
Manager
Data
Manager
Various modes
Record search
Record create/ modify /delete
Record compare
Record merge
Workflow create/ execute
Record assignments
Key Mapping
Matching
Validation/Assignments
Repository
This functionality can also be accessed thru the APIs or SAP Portal iViews.

 SAPAG 2006
Connecting to the Data Manager
Double-click Data Manager shortcut
Enter Repository, Language, and User
The repository must be loaded before logging on to the MDM Data Manager.

 SAPAG 2006
MDM Data Manager Modes
MDM Data Manager Modes
Record Mode
Hierarchy Mode
Taxonomy Mode
Matching Mode
Family Mode
Record mode: Allows you to search, view, and edit the records of any table in the repository. This is
the mode you will use most often, primarily to view and edit product records in the main table and
subtables.
Hierarchy mode: Allows you to view and edit the hierarchy tables in the repository, including regular
hierarchy tables, taxonomy tables, and the Mask table. Though you can also view and edit the records of
a hierarchy table in Record mode, Hierarchy mode specifically allows you to edit the parent/child
relationships and the sibling order of the hierarchy.
Taxonomy mode: Allows you to view and edit the taxonomy tables in the repository. You will use this
mode to create and maintain the category hierarchy used in the repository and to manage the attributes
associated with each category and subcategory. Though you can also view and edit taxonomy tables in
both Record and Hierarchy modes, Taxonomy mode is unique in that instead of focusing on the records
of the taxonomy table, it allows you to create and manage the pool of attributes associated with the
taxonomy table and to assign attributes to categories on a category-by-category basis.
Matching mode: Matching mode supports de-duplication, and is used to identify and eliminate
duplicate records within an MDM repository. The Matching Mode supports interactive, rule- and
strategy-based matching of records.
Family mode: Allows you to view and edit the Families table, which layers a hierarchy of families
upon the taxonomy hierarchy to further break down each category into smaller groups of products. Use
this mode to partition the categories of the taxonomy hierarchy by the values of other fields and/or
attributes, and then to associate family data (such as an image, a paragraph, and bullets) once with each
family of products rather than with each individual product.

 SAPAG 2006
Searches
Searches
Saving Searches
Changing Data
Summary

 SAPAG 2006
MDM Search Advantages
Search only for data that is available
Narrowed search results will only show remaining
available data
Drilldown searches
Multiple choice selections (both AND and OR conditions)
Entire
Catalog
Desired
Items
Single
Pinpoint
Exact
Partial Match Sim
ilar
Converge Diverge
Many Multiple
Most master data management systems use DBMS-style query forms to initiate a search and locate
specific records. Users start with nothing and often end up with nothing, blindly typing in values as
though looking for a needle in a haystack.
By contrast, the MDM system features a powerful and efficient search capability called drilldown
search. Drilldown search allows users to start with all of the items in the repository and then effortlessly
zoom in on items of interest.

 SAPAG 2006
Record Mode
Records/ search result
Search pane Record details
MDM Data Manager is a combined application where you can search
and view the data, as well as create new and maintain/edit existing data.
Additional
record
information

 SAPAG 2006
Table Selection
Select, from the dropdown list, which table you will be searching in.
Record mode is used to manage the records of any table in the repository, including the main table,
regular sub-tables, and object sub-tables. When you view a table in Record mode, MDM allows you to
search for, browse, and edit the table records.
Most of your work with the MDM Data Manager will probably be in Record mode, managing the
product records of the main table. The process of editing product records typically involves:
• Performing a search to narrow down the set of records to just the ones on which you want to work
• Editing the records one after another or as a group until done

 SAPAG 2006
Search Parameters
Flat lookup search tabs
Taxonomy lookup search tabs
Multilevel lookup search
Qualified lookup search
Free-Form Search
The search functionality in MDM has its own methodology.
The search starts on the full data set of the repository. Every time you change the level at the panel
(jump from one table or search option to another), the number of hits will be reduced.
This reduced data set will be the pool from which the next step is able to search. If you want to enlarge
the search criteria again, you have to release the previous restrictions and drill down again.
Release is not possible step by step; you have to release the entire search and start again.

 SAPAG 2006
Compare Records View
Lavender
Aqua
Yellow
All values
are Rose
except
where
marked.
Comparing Records
In Record mode, you can select multiple records in the Records pane and use the Compare Records
command to create a table that contains a side-by-side comparison matrix.
The Compare Records command provides another convenient way to compare multiple records. Use it
to open a pop-up window with the side-by-side comparison matrix that contains a column for each
selected record and a row for each of their fields and attributes (and family fields if the repository has a
family table). Like multi-record selection in the Records pane, SAP MDM highlights differences with
background shading to indicate records that have different or missing values:
• Yellow. The same value appears in all of the selected records (no missing values).
• Aqua. The same value or NULL appears in all of the selected records (one or more missing values).
• Lavender. Different values or NULL appear in the selected records (one or more missing values).
• Rose. Different values appear in the selected records but all the records have values (no missing
values).

 SAPAG 2006
Saving Searches
Searches
Saving Searches
Changing Data
Summary

 SAPAG 2006
Saving Search Results
Query
User who saved it
Data Manager
Local Search
Static dataQueryResults
All usersAll usersUser access
Console or Data ManagerData ManagerCreation location
MasksNamed SearchType of Saved Search
There are three ways to save a search
Named search: Saves search selection for all users
Local search: Saves search selection for current user
Masks: An accumulation of search results
The MDM Data Manager includes the ability to save all of the current search selections to a named
search in the Named Searches table and then restore them at a later time.
The MDM Data Manager includes the ability to save all of the current search selections to a local search
in the file system and then restore them at a later time.
Using MDM masks, you can slice a single master MDM repository of product information into an
effectively unlimited number of custom virtual repositories, dramatically simplifying the maintenance of
a single repository targeted at multiple audiences. Each virtual repository can contain a different subset
of products from the master and appears to the user as a completely private repository.
Unlike SQL views, product masks impose no performance penalty whatsoever and are defined at the
individual product level, rather than the query level. To the user of the MDM system, they appear as
simply another dimension of the multidimensional search; on the Web, a mask can be automatically
applied to the published electronic catalog upon site entry, so that each user sees only the slice of the
MDM repository that you want them to see.
Masks allow you to create multiple custom subset repositories from a single master repository without
duplicating the underlying product records. This guarantees consistency and synchronization of the data
across updates, since there is never more than one copy of each record.

 SAPAG 2006
Narrow the records displayed with as many or few search
parameters
Then go to Search Save as Named Search…
Enter a search name
To retrieve the search results at any time, go to Search
Restore Named Searches “your selection”
Named Search
Choose Save as Named Search… to store the search criteria.
Every item you add to the repository that matches the criteria will be added to the results when you
restore the saved search.
This search is available to other users.

 SAPAG 2006
parameters
Then go to Search Save as Local Search…
Enter a search name
To retrieve the search results at any time, go to Search
Restore Local Search “your selection”
Local Search
This search is ONLY available to the user who created.

 SAPAG 2006
Masks
parameters as desired
Select that the records that will be part of the mask
Right-click on selected
records and choose
Add to Mask “select a mask”
To retrieve mask results, go to
Masks and select your mask
Choosing Add to Mask will add the search results.
Records are added to the existing mask.
With this function, you could create customer-specific repositories to ensure that certain target groups
only see the items they are supposed to see and still keep additional maintenance at an acceptable level.

 SAPAG 2006
Searches
Saving Searches
Changing Data
Summary

 SAPAG 2006
Check In/Out
User centric Check Out – A user may check out a record. While it is checked
out, this user can modify the record. Other users see the original record and
cannotmodify it or check it out.
Join Check Out – After a record is initially checked out, other users may join
the check out This allows them to view and modify the checked out record.
Sometimes there is a need to allow one or more users to edit a copy of a record over an extended period
of time as part of a collaborative process without changing the original until you are ready to commit the
changes, and only then make them visible to users all at once. MDM allows you to do this with a
versioning mechanism known as check out. Checkouts can be performed only in Record mode on the
main table.
The Check Out can be performed with several options, depending on the menu selection:
Operation Description
• Check Out Exclusive => Checks out the selected records exclusively.
• Check Out Nonexclusive => Checks out the selected records nonexclusively.
• Check Out NewRecord Exclusive => Checks out a new record exclusively.
• Check Out New Record Nonexclusive => Checks out a new record nonexclusively.
• Join Checkout => Joins the selected checked out records.
• Unjoin Checkout => Unjoins the selected checked out records.
• Check In => Checks in the selected records to commit changes.
• Roll Back => Rolls back the selected records to discard changes.
• Modify Join Permissions => Specifies which roles and users can join the selected checked
out records.
• All Versions => Displays all versions of all checked out records.

 SAPAG 2006
Check In Check Out and Protect
Check in / check out
looked at from
different users.
1.“Check out” initiator
2.“Check out” partner
Checked out non-
exclusively
can be shared.
Checked out exclusively…
Checked out non exclusively.
Can be shared and unshared by
the check out partner = another user
Protected
Checked out
non-exclusively
Checked out
exclusively
The status of a record, whether it is checked out, Checked out exclusively, protected, etc. is displayed in
a separate column.
Working with checked out records: If you try to modify exclusively checked out records and you are not
the originator of the checkout, you will get an error message in a popup telling you that the record is
checked out by another person.

 SAPAG 2006
Changing Data
Searches
Saving Searches
Changing Data
Summary

 SAPAG 2006
Changing Data Values in Record Detail
Dropdown tree
Single value lookup cells
Multivalue lookup cell

 SAPAG 2006
MDM Data Manager: Qualified Tables
All qualified lookup and special tables are shown in the right column.
Each product record may be assigned to one or more qualified table records. The MDM Data Manager
includes a convenient “search-within-a-search” within the qualified lookup selector dialog for narrowing
down the set of qualified table records and assigning them to product records.
You can also use it to assign the values to their corresponding qualifiers. Qualified lookup fields appear
on the right side of the Record Detail tab.

 SAPAG 2006
Summary
Searches
Saving Searches
Changing Data
Summary

 SAPAG 2006
MDM Data Manager: Unit Summary
Explain the value of MDM Data Manager
Use MDM Data Manager record mode
Describe the detailed functions for
existing repository

SAP MDM Scenario: Data Manager Navigation Exercises
Unit: Data Manager Navigation
Topic: MDM Data Manager
At the conclusion of this exercise, you will be able to:
• Use MDM Data Manager record mode
• Describe the detailed functions for
existing repository
Purpose
This script walks through the MDM Data Manager. It introduces you the Data Manager
Application and gives you some “Search Practice”.
Prerequisites
• MDM Repository has been created.
• Data has been entered in the repository.
• MDM Server has been started.
1-1 Logon to Repository
Connect to MDM Repository
1-1-1 Start the SAP MDM Data Manager Application
1-1-2 Press and choose LOCALHOST (Server), select Repository: Exercise_Master
OK

1-1-3 Type User: mdmuser+Your_letter and password: training (all lowercase)
1-1-4 Then click OK.
2-2 Introducing MDM Data Manager
SAP MDM Data Manager Former name Client
2-2-1 The left hand side is the search area. Here you can use all parameters to drill down
into your repository content.
2-2-2 The upper pane shows all objects in the repository
2-2-3 The record detail pane give you all fields and attribute information for one or
multiple records

2-2-4 The status row contains the information how many records do exist and how many
are in the current search.
2-3 Data Manager Navigation

2-4 Search Exercises
2-4-1 Find out how many products are from the “Boss Holding, Inc.”?
Of the above, how many products are available in “Size” = “12” ?
{HINT: Size is an attribute in the Category table.}
Clear previous search.
2-4-2 How many products have an "Overall Length [Nom]" = "120.000 mm” ?
Or less than “120.000 mm”?
Clear previous search.
2-4-3 Which "Manufacture(s)" have a "Type" = "Activator" ?
Clear previous search
2-4-4 Which parent category contains “Tip Type” = “Pozidriv®” ?
2-4-5 How many products are in the “Mask” called “Convert ” ?
2-4-6 How many records have a “UNSPSC” that starts with the word “Tool” ?
{HINT: Use the Free-Form Search.}
2-4-7 What is the “Name” of the product whose "Temple Length" = "140.00 mm" ?
2-4-8 What is the "Sale Price" in "Germany" for “Part Number” = “3126” ?
2-4-9 How many items have a “Finish” which is “Metallic” AND “Matte”?
{Hint: The answer is NOT 104.}
2-4-10 What is the key mapping for “Part Number” = “2015” ?
2-4-11 What is the key mapping for “Part Number” = “15-000” ?
2-4-12 How many of the products that do NOT have "Image Details", but has a “Color”
= “White” ?
{HINT: Use Free-Form Search for Image Details then Attribute – color.}
Save your last search as a Search Save as Local Search... In the dialog box enter
the Search name: White with no Image Details.
2-4-13 We are now going to add search 4.12 to a Mask. Select all search results (Ctrl+A)
then right-click and Add to Mask Yourletter_White with no Image Details.

2-4-14 Right-click on one record and select Duplicate.
2-4-15 Run your Mask (open Masks sliding tab and select your mask) and note the number
of records?
2-4-16 Run your local saved search (go to Search Restore Local Search White with
no Image Details.) How does the total number compare to 4.13?
Why the difference in total records for Mask and Local Search, when you had
originally saved both with the same data?
Delete the record you just created.
2-4-17 How would you change the Item Status (from Active to Obsolete) for all products
for a specific region in one shot? (Do not change the status as other are running
queries.)

 SAPAG 2006
Unit 2: Data Modeling: Console
Unit 1 MDM Overview
MDM Introduction
MDM Data Manager
Import Manager
Qualified Tables
Hierarchies
Taxonomy
Matching Mode
Workflow
Relationships
Syndicator
MDM Automation
Expressions
Console
Unit 4 Outputs

 SAPAG 2006
Contents:
MDM Console
Connecting to MDM Server
Table and field description and creation
MDM Console

 SAPAG 2006
MDM Console: Unit Objectives
Explain the different table types in MDM Console
Explain the usage of the various tables and fields

 SAPAG 2006
MDM Console: Business Scenario
As part of this implementation, you want to know
how to handle MDM servers using the SAP MDM
Console.
In order to accurately model your master data in
MDM, you need to understand the available table
types.
In order to accurately model your master data in
MDM, you need to understand the available field
types.
As this product stores master data in online
repositories, it is important for you to understand
the repository handling capabilities of the MDM
Console.

 SAPAG 2006
MDM Console Introduction
Repository Tables
Field Types
Admin Folder
Summary

 SAPAG 2006
MDM Console User Interface
MDM
Server
MDM
Server
Console
Controls MDM Server
Repository creation
Table/ field creation
Data modeling
Handled by the administrator DB
The MDM Console allows the system manager to administer and monitor MDM Server software; to
create and maintain the structure of the repositories; and control access to them. Records are not entered
or managed within the MDM Console.

 SAPAG 2006
Connecting to the Console
Locally
Step 1:
Select server
Step 2:
Mount server
Startup steps to
configure a repository
Step 3:
Start server
The MDM Console provides you with information about the MDM servers and all repositories currently
connected to the servers. Each server and each repository has a colored status icon showing the current
status of the repository:
Green: Server or repository is running. Users can access the data in the repository.
Red: Server or repository is stopped. There is no access to the data.
Blue: Repository is currently loading.
Grey: Repository needs to be updated; this is often the case, for example, after applying a new build.

 SAPAG 2006
Repository Tables
Repository Tables
Field Types
Admin Folder
Summary

 SAPAG 2006
MDM Console: Repository Structure
An MDM repository consists of the following tables:
Main table:
Reflects the most important
object; in a product repository,
it would be the product
including a field for each
general valid piece of
information
Sub-tables:
Usually lookup tables (value
tables/customizing tables)
Object tables:
Include images/text blocks
and PDFs
Special tables:
Includes masks, families,
image variants, relationships,
and data groups (hidden)
Main Table: Every MDM repository has exactly one main table. The main table consists of object
information. It includes an individual record for each object in the repository and an individual field for
each piece of object information that applies to all of the records, such as SKU, product name, product
description, manufacturer, and price for the object product. Most of the time, you will be looking at
information in the main table.
Sub-tables: An SAP MDM repository can have any number of sub-tables. A sub-table is usually used as
a lookup table to define the set of legal values to which a corresponding lookup field in the main table
can be assigned; these tables hold the lookup information. For example, the main table may include a
field called Manufacturer; the actual list of allowed manufacturer names would be contained in a sub-
table. Only values that exist in sub-table records can be assigned to the value of the corresponding
lookup field in the main table.
Object tables: Object tables include the images, text blocks, and PDFs tables. An object table is a
special type of lookup sub-table, where each object table is used to store a single type of object, such as
images, text blocks, or PDF files. You cannot store an object directly in a main or sub-table field in an
SAP MDM repository. Instead, each object is defined or imported into the repository once and then
linked to a main or sub-table field as a lookup into the object table of that type.
Special tables: Special tables include the Masks, Families, Image Variants, Relationships, Roles, Users,
and Data Groups tables. Each special table has its own particular behavior with respect to how it is
created and how it is managed.

 SAPAG 2006
No maintenance allowed:
Workflows
Images
Text blocks
HTML texts
PDFs
Tables available:
Main table
Flat lookup
Hierarchies
Taxonomies
Qualifying tables
Masks
Families
Relationships
Images variants
Object List
Table types
A traditional SQL DBMS stores data in the records and fields (rows and columns) of a collection of flat
database tables. All tables have the same rectangular structure in SQL. A SQL database is relational
because of the relationships set up between the different tables.
In an relational DBMS (RDBMS), information about a single product can be combined from multiple
tables by relating values in matching columns. This helps to eliminate redundant data; beyond that,
however, an RDBMS does not support any additional structuring of the data itself.
By contrast, the MDM System supports a variety of different table types that are specifically suited for
storing, organizing, structuring, classifying, managing, and publishing product information in a product
repository, including efficient support for category-specific product attributes that are inherently non-
relational.

 SAPAG 2006
Flat and Qualified Lookup Table
A lookup table is used to store
values that are shared by many
records in other tables, and also
to act as a valid table that defines
the set of legal values of the
corresponding lookup field for
data entry and search.
Flat tables
Can be multi-valued
Qualified tables
Stores lookup records
Supports qualifiers
Always multi-valued
A flat table is always a sub-table. It has the standard, rectangular SQL structure consisting of records
and fields (rows and columns).
A qualified table in MDM stores a set of lookup records and also supports qualifiers, or sub-fields, that
apply not to the qualified table record by itself, but rather to each association of a qualified table record
with a main table record. MDM supports multiple simultaneous qualified tables.
Qualified tables can be used to support product applications and application-based search, and also to
store any large set of sub-table records that contains fields whose values are different for each main
table record, such as multiple prices for different quantities, divisions, regions, or trading partners;
cross-reference part numbers; and additional distributor/supplier/customer-specific information for
different distributors, suppliers, or customers.
All lookup tables in an SAP MDM repository are sub-tables, but not all sub-tables are used as lookup
tables. There are a number of subtle differences among the different types of lookup tables.
Note: SAP recommends using the singular for lookup field names (“Manufacturer”) and the plural for
table names (“Manufacturers”).

 SAPAG 2006
Hierarchy and Taxonomy Tables
Hierarchy
A hierarchy table is a sub-table
that organizes information in a
hierarchy, where each record is
related to a parent record and
may also be related to sibling
records and/or child records.
Taxonomy
A taxonomy is the classification
scheme that defines the
categories and subcategories
that apply to a collection of
objects.
A hierarchy table organizes information in a hierarchy, where each record is related to a parent record
(even if the only parent is the root) and may also be related to sibling records and/or child records. The
main table in an MDM repository typically contains some fields whose data may be hierarchical in
nature. For example, a Manufacturer field may need to accommodate division and subdivision
information for manufacturers. This hierarchical information is stored in a separate, hierarchy sub-table
associated with the Manufacturer lookup field in the main table.
Most of the hierarchy tables used in an MDM repository contain lookup information for fields in the
main table. Other hierarchy tables in MDM include taxonomy tables, the Masks table, and the Families
table. MDM supports hierarchies with an unlimited number of parent/child levels.
Note: a hierarchy table is useful even when it is flat (that is, only leaf nodes below the root), because it
stores the ordered sequence of sibling records, allowing you to override the unordered sequence of
values in a flat table and instead put the values in a fixed order.
A taxonomy is the classification scheme that defines the categories and subcategories that apply to a
collection of records. Categorizing records enables you to isolate subsets of records for various
organizing, searching, editing and publishing purposes. A taxonomy table in MDM stores a hierarchy of
categories and subcategories and also supports attributes, which are sub-fields that apply to particular
categories rather than to the entire collection of records. MDM supports multiple simultaneous
taxonomies.

 SAPAG 2006
Image, Sound, Video, PDF, and Binary Objects Tables
* Each object is stored as a record in the table.
All are single tables
Images: Stores image files
Image Variants: This special
table is used to define the
structure and format of each
of the variants for each image
PDFs:* Object table stores
PDF files
Single tables:
Images: Stores image files, where each image is stored as a record in the table.
Image Variants: Used to define the structure and format of each of the variants for each image. Each
variant is a modified version derived from an original image; the original image is never modified. This
table is managed in the MDM Console and is not visible in the MDM Data Manager.
Sounds: Stores sound files, where each sound file is stored as a record in the table.
Videos: Stores video files, where each video file is stored as a record in the table.
PDFs: Stores PDF files, where each PDF is stored as a record in the table.
Binary Objects: Stores other binary object files, where each binary object file is stored as a record in
the table.

 SAPAG 2006
Text Blocks, Copy Blocks, and Text HTML Tables
* Each object is stored as a record in the table.
Text Blocks:* Object table
stores blocks of text.
Copy Blocks:* This table
references other table’s
attribute values.
Text HTML:* Object table
stores blocks of text and
HTML tags for later
interpreted as HTML.
Text Blocks stores blocks of text, where each text block is stored as a record in the table.
Copy Blocks stores block of data that point to attribute values. Used for variant data for specific groups.
Text HTMLs stores blocks of text interpreted as HTML, where each text block is stored as a record in
the table.

 SAPAG 2006
Special Tables
Families: This table is used to
further partition the products in
each category into smaller
groups based upon the values of
other fields and/or attributes.
Masks: A mask is a snapshot of
the set of records that are
included in the mask.
Relationships: This table is used
to define each of the different
product-level relationships.
Workflows: This table stores all
created workflows.

 SAPAG 2006
Field Types
Repository Tables
Field Types
Admin Folder
Summary

 SAPAG 2006
Every table must have at least one Display Field.
Each field
name must be
unique within
a table.
Items can be
re-ordered.
Field Types
A Display Field for a table is a field whose value is used as:
The corresponding lookup field value for each record
The node name for the record in hierarchy trees
The name of the record in the Product Relationships dialog box
When a table has multiple Display Fields, the value that is used for each record is the value combination
among the Display Fields with each pair of values separated by a comma.
The Display Field can be changed, but a new field must be assigned a Display Field before removing the
previous field’s Display Field property.

 SAPAG 2006
Field Details
Properties will vary depending on the Type selected.
A traditional SQL DBMS has a standard set of relatively simple data types (such as text, integer, and
real) that allow you store a single element of unstructured data in each field. Beyond knowing how to
accept input of and properly store each type of data, SQL has no real understanding of the internal
structure of each data element.
By contrast, an MDM repository supports a variety of compound and structured data types which, like
the set of MDM table types, are specifically suited for managing information in a product repository.
Note: A Text Normalized field stores the actual text value, but uses the normalized value for sorting and
searching. The normalized value is an upper-case version of the original with non-alphanumeric
characters removed (including a-z, A-Z, and 0-9).
Note: A regular Text field is faster than a Text Large field; only use a Text Large field if you are certain
that some values will require over 4000 characters.

 SAPAG 2006
Name: a unique and descriptive field name
Code: a unique field code used within MDM APIs to reference object
Type: Defines the type of field and the available property details
Required: Is the field value required (Yes/No)?
Writable Once: Does the field become read-
only after the first save (Yes/No)?
Matrix: WebDynpro extendability
Sort Index: allows a field to be sortable in the
Records mode of the MDM Data Manager and
APIs
Keyword: Include the field in keyword
indexing/searches (None/Normal)?
Display Field: The field is displayed when
referencing this table (Yes/No)
Unique Field: Must contain a unique value for
each record (Yes/No)
Calculated: If yes, then enter Calculation
Width:Maximum number of characters
Sort Type: Case Insensitive, Case Sensitive, or
Numeric
Example of Field Detail for Text
Most objects within an MDM repository (e.g. tables and fields) have a Code property that is limited to
the following characters:
• A-Z
• a-z
• 0-9
• underscore
Required is only advisory and is used with validation expressions.
Even though a unique field generally prevents more than one record from having the same value (or
value combination in the case of a unique field combination), multiple records are permitted to have the
value NULL for the unique field. The reason for this is that while unique fields are used to distinguish
between multiple records, a unique field with the value NULL means the record has not yet been fully
defined and therefore should not conflict with other records that are also not yet fully defined.

 SAPAG 2006
Additional Information
Many table and fields properties cannot be changed after
creation:
Table type
Field type
Multilingual option
Lookup table
Multi-Valued
Null values are not blank values:
Null is considered when searching
0 is not considered null
Think about your data modeling before implementing it!
The multilingual option will be discussed in detail in the Multilingual Support lesson.

 SAPAG 2006
With MDM 5.5, SAP delivers the content / repositories
prefilled with schema information (empty tables) related to
an SAP R/3 object model:
Articles
Business Partner
Customer
Employee
Material
Product
Vendor
This ensures an easy, built-in connection to SAP R/3 and
mySAP Business Suite systems.
Predefined Repository Content
With SAP NetWeaver MDM 5.5 and above, data models are part of the standard delivery, meaning that
these object types can be used out of the box. Also included in the download of the predefined
repositories are tables, fields, and remote systems, along with import and export maps, which may be
edited.
This ensures an easy, built-in connection to SAP R/3 and mySAP Business Suite systems.
Articles is the newest repository. It incorporates the Matrix application, which uses Web Dynpro to
create product variants without creating a new product.

 SAPAG 2006
Admin Folder
Repository Tables
Field Types
Admin Folder
Summary
Also known as system tables. Additional Admin components are discussed in the Security lesson.

 SAPAG 2006
Remote Systems
Remote systems describe the name
and the process designed to
exchange data with another system.
This information will be important for
further communication.
Remote systems information is part of
key mapping.
What is key mapping?
What value does it add?
Where is it used?
Where is key mapping configured?
The Remote Systems table is a system table automatically created under the Admin node.
Each repository contains a default remote system (MDM), which is used from all MDM Data Manager
applications except the MDM Import Manager.
A key in MDM is a unique, remote-system-specific, and object-type-specific identifier. Different
remote systems have their own separate collection of keys.
Identification of the remote system in the MDM Import Manager and in the MDM Syndicator triggers
deployment of the correct key mapping during inbound and outbound processes. When starting the
Import Manager, you must select the specific remote system for the data transfer. In the Syndicator, you
have to select the remote system either during creation or execution of a syndication.
MDM can import data from remote systems and create or update master data objects using that data. A
remote system’s objects are mapped to master data objects within MDM using key mapping. A key
mapping maintains the relationship between the remote system’s identifier (or key) for an object and the
corresponding master data object in MDM.
At any time, master data objects can be distributed to all known remote systems through a process
known as syndication. This involves determining which master data objects need to be distributed and
converting them into a form that the remote system can understand. This is done using the key
mappings.
Different remote systems can have their own separate collections of keys.
Note: Key mappings are subject to the requirement that two different objects of the same type from the
same remote system cannot have the same key value.

 SAPAG 2006
Key Mapping: Setup
Remote systems must be defined in the
console
In order to use Remote systems, the table
must have Key Mapping set to Yes
Access through the Data Manager
For each record, one or many remote
systems and the remote keys can be
stored
Remote system objects are mapped to master data objects within MDM using key mapping. A key
mapping maintains the relationship between the remote system identifier (or key) for an object and the
corresponding master data object in MDM. A key in MDM is a unique, remote-system-specific, and
object-type-specific identifier. Different remote systems can have their own separate collections of keys.
Within a remote system, each type or collection of objects can have its own separate collection of keys
as well. Key mappings are subject to the requirement that two different objects of the same type from
the same remote system cannot have the same key value.
Remote system objects of a particular type can map only to MDM objects of a particular type. A key can
map to only one MDM object. However, an MDM object may map to multiple keys from the same
remote system. When an MDM object maps to multiple keys from the same remote system, one of the
keys is marked as the default key. The default key is the one that is used when syndicating a reference to
the mapped MDM object.
MDM uses the remote systems defined in the Remote Systems table within the MDM Console to store
and maintain key mapping information for each record or text attribute. The only time the key mapping
is viewed is by right-clicking a single record and selecting Edit Key Mapping.
Remote systems are created under the Admin node. A remote system consists of two key properties.
• Name: The display name has to be unique
• Type: Determines whether the remote system can supply data for import, receive data from
syndication, or both.

 SAPAG 2006
MDM Console: Exercise
General guidelines for designing an MDM repository
List all the fields to be included in the repository.
Decide what field type should apply to each field. If a particular field
should be a lookup field, decide if the lookup table should be flat,
hierarchical, taxonomy, or qualified.
For each field:
determine how the data should be represented and what data
type should be used;
how to store the data as numeric values (integers or real
numbers), currency, text, images, and so on;
whether the field should be single-valued or multi-valued; and
whether it should be a lookup field
Begin exercise by first reading the requirements defined for this
exercise.
Data modeling of your repository is an important element and should involve all business groups who
will be utilizing the data.
Each lookup field in the main table becomes a searchable dimension of the repository and automatically
appears in the SAP MDM Data Manager as a search tab in the Search Parameters pane in Record mode.
Each nested lookup field in a lookup table also becomes a searchable dimension of the repository,
appears in the Data Manager as a search tab when the current table is the lookup table and also appears
within the search tab for the main table lookup field when the current table is the main table for
multilevel search-within-a-search.

 SAPAG 2006
Summary
Repository Tables
Field Types
Admin Folder
Summary

 SAPAG 2006
Archive and Unarchive a Repository
Archive Repository – is a mechanism
that allows you to backup your
MDM repository in a DBMS which
is platform-independent format.
Unarchive Repository – allows you to
restore an MDM repository from
an MDM archive.
Export Repository Schema – saves
the table structure of the
repository as an XML file.
Import Repository Schema – Imports
a schema and merges it into the
selected MDM repository.
For most exercises, you will find a completed archive in the Archive Folder. If you are not able to
complete an exercise then unarchive the completed archive and you will be set for the next exercise.

 SAPAG 2006
MDM Console: Unit Summary
Explain the different table types in MDM Console
Explain the usage of the various tables and fields

MDM Scenario: Create a Repository Exercises
Unit: Create a Repository
Topic: MDM Console
At the conclusion of this exercise, you will be able to:
Explain the different table types in MDM
Console
Explain the usage of the various tables and
fields
Create a Repository
Purpose
This script walks through the process of creating a repository from scratch.
Trigger
The MDM tool comes empty. Repositories are available that can be unarchived and used for
demonstration and training purposes. However, if you are creating a customer demo or
implementing a new repository for a customer project, then you may find that an existing
repository does not meet your requirements. In this case you would follow this process to create
your own repository.
3-1 Design of a Repository
It takes time and input from many groups to properly design an appropriate repository. In
this course, as you learn more about SAP MDM, you will continually add to your repository.
3-1-1 Your customer is a distributor of household appliances and assorted supplies. They
would like to store their product details in MDM. They will supply you with
product details from both their New York and London offices.
3-1-2 You will store the following product information for each record:
Product ID, name, long description, purchased from country, manufactured in
country, sales price, is the item electric, and the weight.
3-1-3 You will also create 3 lookup tables for quicker and more reliable data entry:
Business Partners, Countries, and Divisions
3-1-4 You will begin with SAP’s default repository which contains only a main table and
the required standard tables which all repositories must contain whether they are
used or not.

3-2 Create a Repository
Create a new empty repository.
3-2-1 Right-click on the server name and select context menu item “Create Repository”
3-2-2 Log on to the DBMS server (Note – your user login is ‘sa’ with password
TRAINING).

3-2-3 After logging on to the DMBS server, the repository name and port fields will be
available for entry. Fill in the following fields.
Field Name Description
Repository
name
YourLetter_Case_Study
Port Number
Available Port Number – (between 2000 and 9999)
Please use 2100 for A, 2110 for B, 2120 for C, 2130 for D
Note the repository name is text and reference only – it can be any text you
choose as long as it is unique.
3-2-4 Then click Finish
3-3 View New Repository
Expand the Console Hierarchy to view the contents of your new repository
‘YourLetter_Case Study’. There is a default main table ‘Products’ and empty tables.

3-4 Create Divisions Table
In the MDM Console you will be fine tuning your repository structure.
Notice how the right hand side of the screen is divided into two sections. The top
section lists all of the tables that belong to the repository. The lower portion is the work area
for maintaining details on the table that is currently selected (highlighted in the upper
section).
3-4-1 In the Console Hierarchy pane highlight your repository, right-click the “Tables”
work area and select Add Tables or from the main menu select “Tables Add”
3-4-2 The first table will be a Lookup [Flat] table for your Divisions.
3-4-3 Type in the name of the table in the “Name” field type Divisions.
Click on Type next to determine the table type.
Pick from the drop down menu “Flat” as the Type.
Set Key Mapping = Yes
Shift+Enter to save the table. Notice the table information is updated in the upper
section of the screen.

3-5 Create Other Tables
Repeat the process in step 4.1 to 4.3 to create the tables Countries and Business Partners.
After this step you should have the following tables present.
Table Name Table Type
Countries Flat
Business Partners Flat
Result:

3-6 Add Fields
Next you will add fields to your countries tables. You have to highlight the appropriate table
in the left hand Console Hierarchy pane and the two right hand panes will change to the
detailed view of the highlighted table. The logic will remain. The upper pane shows all the
table fields and the lower pane shows the details of the field highlighted.
3-6-1 Select the Countries table and right mouse click on the Fields pane.
3-6-2 Enter the new field name in the appropriate space within the Field Detail section of
the screen.
3-6-3 See the image to the right for details on all the property values.
3-6-4 Click Shift+Enter to save the field.

3-7 Add Fields to the Main Table
Select Table Products and add the following fields.
3-7-1 Select the Products table and right mouse click on the Fields pane.
3-7-2 Enter the new field Name, Division, in the appropriate space within the Field Detail
section.
3-7-3 Select Type = Lookup [Flat]
3-7-4 Since this is a Lookup field, you must enter the table you want the field to lookup.
Select the table ‘Divisions’ as the Lookup Table.
3-7-5 Click Shift+Enter to save the field.

3-7-6 Continue by adding the following fields:
C
o
n
s
i
d
e
r
a
d
d
i
n
g
t
h
e
fol
Consider adding the following fields: Date modified and User who last modified
the record.
3-7-7 The Fields will be displayed in the MDM Data Manager in the order of appearance
in the console.
To reorder Fields right mouse-click in the fields table and select Reorder…
Field Name Code Field Type Extra Field Values
Purchase
Country
Purchase_Countr
y
Lookup [Flat] Lookup table = Countries
Multi-Valued = No
Manufactured
Country
Manufactured_Co
untry
Lookup [Flat] Lookup table = Countries
Multi-Valued = Yes
Sales Price Sales_Price Currency Symbol = $
Decimal places = 2
Show Fractions = No
Long Description Long_Description Text Large
Product ID ProductID Text Display Field = Yes
Unique Field = Yes
Width = 10
Electric Electric Boolean Display Field = Yes
True Value = Y
False Value = N
Weight Weight Real Decimal places = 3
Show Fractions = No

3-7-8 Highlight the field and drag it with the mouse to a new location in the list.
Move Product ID to the top of the list.
3-8 Create Remote System
You will now create a remote system ID which will identify the source of your records when
importing them into your repository
3-8-1 Expand the Admin folder and select Remote Systems.
3-8-2 Right-click on the Remote Systems and select Add Client System.

3-8-3 Enter the following information for your NewYork remote system:
3-8-4 Then Shift+Enter. The new remote system is now saved.
3-8-5 Create a second remote system called London.
3-8-6 Lastly, we want to utilize this remote system when importing data, so select the
Products table from the list of Tables and change Key Mapping to Yes.
3-8-7 Shift+Enter to save your change.

3-9 Load Repository
3-9-1 Right mouse click on “YourLetter_Case_Study” select Load Repository
Immediate as there is no need to load With Indexes as you have no data.
3-9-2 Start the SAP MDM Data Manager by double clicking on the icon on your desktop,
select Localhost using the
3-9-3 Select YourLetter_Case_ repository
3-9-3-1 User: Admin
3-9-3-2 OK

3-10 Check Your Results
You have created a repository from scratch and can now log on to the Data Manager and see
the structure.
Resume: In this Scenario you have created tables and fields in your repository. These
tables and fields can now either be populated using the import tool Import Manager or
manually on the Data Manager screen you see

 SAPAG 2006
Import Manager
Unit 1 MDM Overview
MDM Introduction
MDM Data Manager
Import Manager
Qualified Tables
Hierarchies
Taxonomy
Matching Mode
Workflow
Relationships
Syndicator
MDM Automation
Expressions
Console
Unit 4 Outputs

 SAPAG 2006
Contents:
MDM Import Manager
Basic import functionality
Steps required to preform an import of data
MDM Import Manager

 SAPAG 2006
MDM Import Manager: Unit Objectives
Explain the value of MDM Import Manager
List the six steps for data import with MDM
Import Manager
Explain the detailed functions for importing
and mapping data from various sources

 SAPAG 2006
MDM Import Manager: Business Scenario
In order to load master data into MDM you need to
use the Import Manager and understand its
functionality.
As part of this implementation, you want to know
what options are available in the Import Manager for
the transformation of data as it is loaded into your
repositories.
You are also interested in how to automate the
import process.

 SAPAG 2006
Import Manager Overview
Six Steps for Data Import
Summary

 SAPAG 2006
General Challenges of Managing Data
Business Challenges:
Time consuming
Resource-intensive
Expensive
Technical Challenges:
Raw and/or disparate data
Normalization
Incompatible data formats
Different classification schemas
Aggregation aggravation
Hundreds of sources and
destinations

 SAPAG 2006
Reasons to Use SAP MDM Import Manager
Data can be imported to the same repository from multiple
sources
Field-orientated processing rather than record-by-record
processing
Distinct value lists
Automatic data type conversion
Value conversions during import
Extended table types like hierarchies, taxonomy, and masks
Specific field types that can handle pdf, images, long text,
and sound
Key mapping based on the data source
Capability to sort and restructure data
Consistent view of source data

 SAPAG 2006
Parametric Import
Efficiency of parametric import versus parametric search:
Parametric search
Lists the complete set of distinct values for each field or
attribute in a repository. Selecting a value during a drilldown
search selects all of the underlying records containing that
value.
Parametric import
Lists the complete set of distinct values for each field in the
source data. Changing a value as part of the import (by
mapping or converting it) changes it in all of the underlying
records containing that value.
Patent-pending parametric import technology
Example – If the imported data has:
• 5000 input country records
• Two unique countries in the 5000 rows
The result will be:
• Record-at-a-time processes the countries 5000 times
• Field-at-a-time with distinct values process the countries twice
Processing gain in parametric import: 4098 fewer transformations of country!

 SAPAG 2006
Import
Manager
Import
Manager
MDM Import Manager User Interface
Data
Record upload
Record match
Data mapping
Value conversions
Saving of maps
MDM
Server
MDM
Server
Repository
Tables
Views
Files
Tables
Views
Files
The MDM Import Manager allows the import of data into an MDM repository from any tabular or XML
format with a consistent user interface and identical functional capabilities, regardless of the source file
format.

 SAPAG 2006
Data Import
Suggestions
Bad data in results in bad data out.
Limit the number of records to 10,000 or less for MDM Import
Manager.*
Value mapping and conversion must be completed
For every mapped field, each of its values must be properly
converted to the destination data type.
Alternately, each value must be mapped to an existing or
newly added destination data value.
Record matching
One or more unique fields must be identified.
The MDM Import Manager will determine whether to create
new records or update and replace existing destination
records.
* The limitations of the MDM Import Manager do not apply to the MDM Server.

 SAPAG 2006
Summary

 SAPAG 2006
Six Required Steps for Import Manager
1. Connect to repository
2. Connect to source
3. Select source and destination tables
4. Map fields/values
5. Match records
6. Import
Six steps of the MDM Import Manager:
• Connect to existing repository where the imported data will reside.
• Connect to the source data file or database to establish programmatic access from the MDM Import
Manager to the source schemas and data.
• Select the source and destination tables where the imported data will be transferred from and to.
• Map fields to identify the destination field for each source field and also the type of mapping and
conversion required for the underlying data values.
• Match records to specify the key fields for identifying existing records that match the source records
and whether new records should be created and existing records should be updated or replaced.
• Import records to transfer data from the file into the MDM Repository.

 SAPAG 2006
Select the target Repository
Click Add/Edit ( ) to change
repository server and select
a repository (by name)
Enter User name
Enter Password
Choose Next when desired repository is selected.
1. Connect to Repository
The MDM Server must be running and the selected repository must be loaded before choosing Next.

 SAPAG 2006
2. Connect to Source
The following database
types are available as
sources:
Read-only option:
Impacts how certain Import
Manager operations are
processed
Impacts whether or not
Import Manager can create
supporting tables in the
source repository when
needed or if it is forced to in-
memory/swapfile operations
on its server.
Connect to Source Type
Access, Excel and XML: “File name” becomes active
ODBC: “DSN” (Data Source Name), “User”, “Password” becomes active
SQL Server and Oracle: “DBMS server”, “Database” (name), “User”, “Password” become active
For RDBMS, the “Database server” is the TCP/IP hostname or address of the Database Server where
you will source data *from*.
“Database” is the name of the logical database within the RDBMS which you will be accessing for a list
of table/view names.
The Read-only option is enabled only for source types that can be updated (Access, Oracle, SQL Server,
and XML). It is disabled and checked for those that cannot be updated (Excel and ODBC).

 SAPAG 2006
3. Select Current Tables
Source Destination
You must select a current source table and a current destination table
before you can perform most of the MDM Import Manager operations.
The MDM Import Manager imports records:
From the current source table (left dropdown)
Into the current destination table (right dropdown)

 SAPAG 2006
3. Record Browsing Options
Sort ASC
Sort DESC
The MDM Import Manager allows you
to browse and become familiar with
source data in several different
ways.
Use the Source Preview tab to
browse all of the records and fields
of each table in a traditional
row/column grid.

 SAPAG 2006
4. Field Mapping
MDM Import Manager uses the top pair of field mapping grids to
display:
The set of source fields for the “current” source table
The set of destination fields, nested display fields, attributes, and
qualifiers of the current destination table as a list in the destination
fields grid
The Field mapping grid performs both field-level mapping and value-level operations as follows:
Field level
For each source field or field combination whose data values you want to import, you can use the top
pair of field mapping grids to map the field to the corresponding destination field.
Value level
For each mapped source field, you can use the bottom pair grids to map, convert, or create
measurements from the underlying field values, dependent upon the mapped destination field and data
type.
MDM Import Manager takes basic field mapping capability and extends it with a powerful value
mapping and conversion capability.

 SAPAG 2006
The first two columns in the destination field display are of particular
interest:
Mapped: Whether a source field is mapped to the destination field
F/D/Q/A: The field type
F: Standard destination field
D: Display field of a lookup with multiple display fields
Q: Qualifier
A: Attribute
4. Destination Field Details
Each column can be sorted. In the above image, the fields are listed by name. Typing the letter “s“ will
move the selection to the first name that starts with s.

 SAPAG 2006
4. Field Mapping: Automap
Outcome:
You can also search for matches one field at a time;right-click on the source
field and select Find Next Matching Destination Field.
If automap is used, each mapped field should be verified to make sure that the correct source data is
mapped to the correct destination.

 SAPAG 2006
4. Field Automap Configurations
Default automap field name
matching:
Performing a “contains”
comparison against the
destination field name
Normalizes (removes
punctuation characters
and spaces) both the
source and destination
field names before
performing the
comparison
Configuration options control how the matches are made
(Configuration Options Find matching field)

 SAPAG 2006
4. Manual Field Mapping
Note that source Description did not automap destination Long
Description.
Highlight both and choose Map.
Outcome:

 SAPAG 2006
4. Value Mapping
Value-level mapping of source values forces a user to normalize
source data, implicitly defining a precise set of transformation
rules, which:
Eliminates differences between source and destination values
Collapses multiple source value variations into a single
destination value
Allows for proper mapping of multiple delimited source values
into a multi-valued MDM field
Makes is it easy to explicitly add new values to the set of
destination domain values
All mapped fields of data types that require value mappings must
have their values mapped.
For each field, the MDM Import Manager collapses the set of all values down to the set of distinct
values.
Generally, the number of values will usually be dramatically smaller than the total number of records,
often by several orders of magnitude.

 SAPAG 2006
4. Value Mapping Requirements
Based upon the current table and the type of the mapped
destination field, the Map checkbox indicates whether or not
the current mapped source field requires value mapping. If
checked, you must map source to destination values.
The Map checkbox is:
Disabled and automatically checked when
value mapping is required
Disabled and automatically unchecked
when value mapping is neither required
nor permitted
Enabled for you to check manually when
value mapping is optional.
Value mapping is optional to fixed-width text fields that are: (1) promoted lookup table display fields
when the current table is the main table and the lookup table has multiple display fields; and (2) actual
display fields when the current table is the lookup table.
When value mapping is required:

 SAPAG 2006
4. Automap Values
The Value mapping area shows source values (left) and repository
domain values on the right (in this case, the repository has domain
values loaded).
Click Automap.

 SAPAG 2006
4. Manual Value Mapping: Automap
Automapping will map most – but not all – values.
You must manually map remaining individual values.
Status/progress is displayed in lower right of screen:

 SAPAG 2006
4. Manual Value Mapping: Add
CTRL+A
to select all
Source fields that have no values in the repository must be added. The
values can be loaded in the repository first (separate MDM Import
Manager “job”) or add the values here.
When value mapping is required, the value in the Converted Value column is most useful for adding
new destination values or hierarchies where it is used as the new item or node value. When mapping to
existing destination values, the converted value is just a convenience for automap since each value could
be manually mapped to any destination value regardless of its value.
The Add button is disabled if the display field of the destination lookup field is compound and the
source field is not compound or if the single destination display field is not of type Text, Text
Normalized, Text Block, Integer, or Measurement.

Mdm100 master data_management

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Viewers also liked

Viewers also liked (20)

Similar to Mdm100 master data_management

Similar to Mdm100 master data_management (20)

Recently uploaded

Recently uploaded (20)

Mdm100 master data_management