Embed Size (px)
Citation preview
Microsoft Dynamics AX Technical ConferenceFebruary 3–5, 2014Bellevue, WA
Data synchronization to multiple instances of Microsoft Dynamics AX using master data managementBigyan RajbhandariProgram Manager
IntroductionWe are excited to share Microsoft Dynamics AX 2012 R3 with you…• This presentation contains Microsoft confidential information• Dynamics AX 2012 R3 is pre-release software and subject to change• Microsoft provides no license, express or implied, in this presentation• Please review and respect the disclaimer included in all printed
and electronically distributed materials
Agenda
Overview of master data management
framework
Configuring data synchronization
across deployments
Enabling record management
scenarios using single/multi master
modes
Central conflict detection and
resolution
“Business process reliability and efficiency requires high
quality data that is complete and non-redundant”
ScenarioContoso – Global
company with distributed
systems
Interested in sharing
master data
Reduce multiple copies of
outdated data
Set clear process for record
creation and management
Customers Contoso HQ
Regional Site 1
Regional Site 2
Regional Site 3
Customers
Customers
Customers
Reliably and efficiently share master data across systems
Master data management overview
Contoso HQ
Regional Site 1
Regional Site 2
Regional Site 3
Central data store(SQL MDS)
Data synchronization by leveraging
SQL MDS
AX and non-AX systems
as spoke
Single/multi master modes
Central conflict
management
Policy based selective
synchronization
First step towards holistic
data governance
High level data flowAX 1 SQL MDS
Customer MDS entity
Data sync batch
job
MDM
MDM UX
MDM Client Configuratio
n UX
MDM Provisionin
g UX
Customer Entity
Customer Address Entity
import job staging
Data Import/Export
1. Change tracking
4. Invoke import
job
2. Push
3. PullCustomer entity
subscription view
Change tracking &
conflict detection
AX 2
Non – AX system
Key points
Capabilities supported out of box
•AX to AX master data mgmt. enabled through configuration•Most requested entities enabled for MDM - Customers, Vendors, Employees, Global address book, Product•Automatic conflict detection & manual conflict resolution•Selective data synchronization during push/pull
Possible with customization
•Possible to do MDM between AX & non-AX systems with adapter development•Existing DIXF entities or new ones could be enabled for MDM with minor customizations
Dependencies
•Hub requires SQL Server 2012 MDS feature (Enterprise SKU only)•Available in AX 2012 R3•Support will be extended to AX 2012 R2 CU7
Overview of master data management
framework
Configuring data synchronization
across deployments
Enabling record management
scenarios using single/multi master
modes
Conflict detection and resolution using SQL
MDS
Data synchronization
[AX instance 1]Customer entity
[SQL MDS]Customer entity
[AX instance 2]Customer entity
Rec ID Account Number
Customer Name
161 A111 Fabrikam
162 A222 MSFT Corporation
163 A333 Contoso LLC
Rec ID Account Number
Customer Name
251 A222 Microsoft Corporation
252 A111 Fabrikam
253 B444 Adventure works
Account Number
Customer Name
Last Modified
A111 Fabrikam Ax 1
A222 Microsoft Corporation
Ax 2
A333 Contoso LLC
Ax 1
B444 Adventure works
Ax 2 254 A333 Contoso LLC
1.
2. 2.
1.
Microsoft Corporation
Demo
Configuring data synchronization
Overview of master data management
framework
Configuring data synchronization
across deployments
Enabling record management
scenarios using single/multi master
modes
Conflict detection and resolution using SQL
MDS
Data management scenariosSQL MDS
AX Instance 1 AX Instance 2
Customers
Customers Customers
Push/Pull Push/Pull
Multi master
Products
Products
ProductsPush/Pull Pull Only
Single master
Create/modifyRead only
MDS
Data management modes
Single master
•Only one instance is allowed to write to MDS•All other instances are read only. MDS records overwrite any changes in other instances. •Mode can be defined at entity level•Enforce by customizing security and defined business process
Multi Master
•Any instance is allowed to create/modify records•Conflicts are automatically detected in MDS at record level.•Conflict resolution is done manually by data stewards using MDS excel add-in
Overview of master data management
framework
Configuring data synchronization
across deployments
Enabling record management
scenarios using single/multi master
modes
Conflict detection and
resolution using SQL MDS
Conflict resolution in multi-master
[AX instance 1]Customer entity
[SQL MDS]Customer entity
[AX instance 2]Customer entity
Rec ID Account Number
Customer Name
161 A111 Fabrikam
162 A222 MSFT Corporation
Rec ID Account Number
Customer Name
251 A222 Microsoft Corporation
252 A111 Fabrikam
Account Number
Customer Name
Last Modified
A111 Fabrikam Ax 1
A222 Microsoft Corporation
Ax 2
1.
2. 2.
1.
Microsoft Corporation
Microsoft
Account Number
Customer Name
Has conflict?
A222 Microsoft Corporation
True
Conflict illustration
Microsoft
Display conflict count
Microsoft Corporation
Update
Demo
Conflict detection and manual resolution
Implementing MDM
•Identify topology and data assets that you would like to share across your organizationsPlan & Strategize
•Define clear processes on how and who creates and manages data
Define business process
•Deploy MDM components, MDS and provision AX entities
Deploy MDM components
•Depending on your business need choose single or multi master modes
Choose single/multi master mode
•Configure selective synchronization, schedule and conflict management alerts
Configure additional capabilities
QUESTIONS?Focus Room: CottonwoodTime: 2:30PM – 4:00PM
THANK YOU for attending! Your feedback is extremely important, please complete an evaluation using one of the following options:
• On the fly from the mobile event app• Communications Kiosks located in the Evergreen Foyer, Grand
Ballroom Foyer and Regency Foyer
• Via the Dynamics AX Technical Conference website: www.microsoft.com/dynamics/axtechconference
DisclaimerThis presentation contains Microsoft Confidential Information. Microsoft may use any suggestions, comments, or other feedback that you provide for any purpose without obligation. This presentation is provided for informational and training purposes only. It represents Microsoft’s view as of the presentation date. Microsoft cannot guarantee the accuracy of any information after the presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted as a commitment on Microsoft’s part. This presentation is provided “as-is”.
Microsoft Dynamics AX 2012 R3 is pre-release software under development. All dates, features, and descriptions specified are preliminary, are based on current expectations, and are subject to change at any time without notice.
Sample code included in this presentation is made available AS IS. THE ENTIRE RISK OF THE USE OR THE RESULTS FROM THE USE OF ANY SAMPLE CODE REMAINS WITH THE USER.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. NO LICENSE (EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE) TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS PRESENTATION.
© 2014 Microsoft Corporation. All rights reserved.
Resources
• Dynamics AX Server Team Blog• SQL Master data services capacity guide
line• 7 Building Blocks for a Successful Maste
r Data Management Plan• The cost of poor data quality
THE END
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
