Module 10

Master Data Services

Module Overview

• Introduction to Master Data Services

• Implementing a Master Data Services Model
• Managing Master Data
• Creating a Master Data Hub
Lesson 1: Introduction to Master Data Services

• The Need for Master Data Management

• What Is Master Data Services?
• Master Data Services and Data Quality Services
• Components of Master Data Services
 The Need for Master Data Management

CRM
Customer ID Name Address Phone
1235 Ben Smith 1 High St, Seattle 555 12345

Order Processing System Marketing System

Account Customer Address Phone Contact Name Address Phone
531 Benjamin Smith 1 High St, Seattle 555 12345 22 B Smith 5 Main St, Seattle 555 54321
 What Is Master Data Services?

CRM
Customer ID Name Address Phone
1235 Ben Smith 1 High St, Seattle 555 12345

Master Data Hub

Customer ID Account No Contact No Customer Address Phone

1235 531 22 Ben Smith 1 High St, Seattle 555 12345

Master Data Services

Other consumers
(e.g. Data Warehouse ETL)

Order Processing System Marketing System

Account Customer Address Phone Contact Name Address Phone
531 Benjamin Smith 1 High St, Seattle 555 12345 22 B Smith 5 Main St, Seattle 555 54321
Master Data Services and Data Quality Services

Data Quality Services Master Data Services

• Domain-Focused
• Applicable to any dataset that
contains domains in the KB
• Is “Seattle” a valid value for City?
Entity-Focused
Applicable to specific instances of
business entities
What is the correct name, address, and
phone number for customer 1235?

Use Data Quality Services to:

Cleanse data before importing into master data hub
Apply matching policies to find duplicate master data entities
Components of Master Data Services

• Master Data Services database

• Contains the objects that support Master Data Services
• Master Data Manager Web application
• Enables administrators to create and manage Master Data
Services objects, such as entities and attributes
• Enables data stewards to manage master data
• Master Data Services Configuration Manager
• Enables administrators to create the Master Data Services
database and Web application
• Master Data Services Add-In for Microsoft Excel
• Enables administrators and data stewards to manage master
data in Excel
Lesson 2: Implementing a Master Data Services
Model

• What Is a Master Data Services Model?

• Creating a Model
• Creating Entities and Attributes
• Adding and Editing Members
• Demonstration: Creating a Master Data Services
Model
• Editing a Model in Microsoft® Excel®
• Demonstration: Editing a Model in Excel
What Is a Master Data Services Model?

• A versioned data model for specific Customers Model

business item or area of the
business Version 1

Account Type Entity

• Contains definitions for entities
Member
• Code: 1
required in the business area Attributes:
• Code (string)
• Name: Standard

• Name (string) Member

 Often an entity with the same name •

•
Code: 2
Name: Premier
as the model, as well as related
entities

• Each entity has a defined set of Customer Entity Member

attributes Attributes:
•
•
Code: 1235
Name: Ben Smith
• Code (free-form text) • Address: 1 High St, Seattle
• Name (free-form text)
Phone: 555-12345
All entities have Code and Name
•
• Address (free-form text)
 • Phone (free-form text) • AccountType: 1
attributes •
•
AccountType (domain-based)
CreditLimit (free-form number)
• CreditLimit: 1000

 Attributes can be categorized in Contact Details Attribute Group

attribute groups

• Each instance of an entity is known

Version 2 Version 3
as a member
Creating a Model

• Use the Master Data Services Web application

• Specify a unique model name
• Optionally:
• Create an entity with the same name as the model
• Create an explicit hierarchy with the same name as the
model
• Make the explicit hierarchy mandatory
Creating Entities and Attributes

Creating an Entity
• Specify a unique name
• Optionally:
• Specify a staging table name
• Enable automatic code values
• Enable explicit hierarchies and collections

Adding Attributes
• Edit an entity to add leaf member attributes
• Specify attribute type:
• Free-form
• Domain-based
• File
Adding and Editing Members

• Use Explorer in the Master Data Services Web

application
• Add, edit, and delete members for each entity in
the model
• Add annotations to document transactions
Demonstration: Creating a Master Data Services
Model

In this demonstration, you will see how to:

• Create a Model
• Create an Entity
• Create Attributes
• Add and Edit Members
Editing a Model in Microsoft® Excel®

• Use the Master Data Services Add-In for Excel to

connect to a model
• Create entities
• Add columns to create attributes
• Edit entity member data in worksheets
• Publish changes to Master Data Services
Demonstration: Editing a Model in Excel

In this demonstration, you will see how to:

• Connect to a Master Data Services Model in Excel
• Add a Member
• Add a Free-Form Attribute to an Entity
• Add a Domain-Based Attribute and Related Entity
Lesson 3: Managing Master Data

• Hierarchies and Collections

• Creating Derived Hierarchies
• Creating Explicit Hierarchies
• Creating Collections
• Finding Duplicate Members
• Validating Members with Business Rules
• Demonstration: Creating and Applying Business
Rules
Hierarchies and Collections

• Derived Hierarchies
Account Type Member
• Code: 1
• Name: Standard Customer Member

• Natural hierarchical groupings •

•
•
Code: 1235
Name: Ben Smith
Account Type: 1
based on domain-based Customer Member

relationships •
•
Code: 1267
Name: Amy Strande
• Account Type: 1

• Explicit Hierarchies •
Consolidated Member
Code: CustUS
• Name: US Customers
Hierarchical groupings of
Leaf Member
• • Code: 1235
• Name: Ben Smith
specific members Leaf Member
• Code: 1267
• Can be mandatory or non- Consolidated Member
• Name: Amy Strande

mandatory •
•
Code: CustEU
Name: European Customers Leaf Member
Code: 2214
• Collections
•
• Name: Sabina Schütz

• Non-hierarchical groupings of Leaf Member

specific members •
•
Code: 2600
Name: Andrew Sinclair

• Can include leaf and •

Leaf Member
Code: 1785

consolidated members from any • Name: Doris Krieger

hierarchy
Consolidated Member
• Code: Cust-EU
• Name: European Customers
Creating Derived Hierarchies

• Link hierarchy levels to define a named

hierarchy based on domain-based attribute
relationships
• Navigate the derived hierarchy in Explorer
Creating Explicit Hierarchies

• Enable explicit hierarchies and collections, and

create an explicit hierarchy
• Optionally, make the hierarchy mandatory
• Edit entities as required to:
• Create consolidated member attributes
• Create additional explicit hierarchies

• In Explorer, define the hierarchies

• Create consolidated members for levels
• Move leaf members to consolidated members
Creating Collections

• Enable explicit hierarchies and collections

• Edit entities to create collection attributes if
necessary
• In Explorer, create and edit collections
• Specify a name, code, and other collection attributes for
each new collection
• Add leaf members and consolidated members to the
collection
Finding Duplicate Members

• Create a Data Quality Services knowledge base

with domains for entity attributes
• Create a matching policy to identify possible
duplicates
• Match data in the Master Data Services Add-In for
Excel
Validating Members with Business Rules

• Define business rules with the business rule

expression editor
• Publish business rules
• Use business rules to validate entity member data
in:
• Explorer
• Excel
Demonstration: Creating and Applying Business
Rules

In this demonstration, you will see how to:

• Create Business Rules
• Publish Business Rules
• Apply Business Rules in Explorer
• Apply Business Rules in Excel
Lesson 4: Creating a Master Data Hub

• Master Data Hub Architecture

• Master Data Services Staging Tables
• Staging and Importing Data
• Demonstration: Importing Master Data
• Consuming Master Data with Subscription Views
• Demonstration: Using Subscription Views
Master Data Hub Architecture

CRM Other consumers

(e.g. Data Warehouse ETL)
SSIS
SSIS

SSIS

SSIS

Order Processing System

Data Steward Marketing System

• Users insert and update data in application data stores

• Application data is loaded into master data hub for
consolidation and management by data stewards
• Master data flows back to application data stores and
other consumers across the enterprise
 Master Data Services Staging Tables

• MDS generates a staging table for each:

• Leaf member
• Consolidated member
• Relationship

stg.EntityName_Leaf stg.EntityName_Consolidated stg.EntityName_Relationship

• ID • ID • ID

• ImportType • ImportType • RelationshipType

• ImportStatus_ID • ImportStatus_ID • ImportStatus_ID

• Batch_ID • Batch_ID • Batch_ID

• BatchTag • BatchTag • BatchTag

• ErrorCode • HierarchyName • HierarchyName

• Code • ErrorCode • ParentCode

• Name • Code • ChildCode

• NewCode • Name • SortOrder

• <AttributeName> • NewCode • ErrorCode

• <AttributeName>
Staging and Importing Data

1. Load data into staging tables

• Using SSIS, Import and Export Wizard, Transact-
SQL, and so on
2. Run staging stored procedures
• stg.udp.EntityName_Leaf
• stg.udp.EntityName_Consolidated
• stg.udp.EntityName_Relationship

3. View import status in Master Data Manager

4. Match data to identify any duplicates
5. Apply business rules to validate data
Demonstration: Importing Master Data

In this demonstration, you will see how to:

• Use an SSIS Package to Import Master Data
• View Import Status
• Validate Imported Data
Consuming Master Data with Subscription Views

• Create subscription views in Master Data Manager

• Formats:
• Leaf Attributes
• Consolidated Attributes
• Collection Attributes
• Collections
• Explicit Parent Child
• Explicit levels
• Derived Parent Child
• Derived Levels
Demonstration: Using Subscription Views

In this demonstration, you will see how to:

• Create a Subscription View
• Query a Subscription View
Lab: Implementing Master Data Services

• Exercise 1: Creating a Master Data Services Model

• Exercise 2: Using the Master Data Services Add-in
for Excel
• Exercise 3: Enforcing Business Rules
• Exercise 4: Loading Data into a Model
• Exercise 5: Consuming Master Data Services Data
Logon Information
Virtual machine: 20463C-MIA-SQL
User name: ADVENTUREWORKS\Student
Password: Pa$$w0rd

Estimated Time: 60 Minutes

Lab Scenario

The data warehousing solution you are building for

Adventure Works Cycles includes product data
from various systems throughout the enterprise.
You need to ensure that there is a single, consistent
definition for each product.
Module Review and Takeaways

• Review Question(s)