Transcript BRK444 - How to approach your upgrade

•
How to upgrade to Microsoft Dynamics AX 2012 with reduced business disruption and cost
•
•
Key considerations for planning and executing a Microsoft Dynamics AX 2012 upgrade
Best practices for a successful upgrade
•
What’s new in Microsoft Dynamics AX 2012 R3 for Upgrade
Upgrade
project
overview
Sourceto-Target
&
In-Place
Upgrade
best
practices
Source version
Supported Upgrade Path
Microsoft Dynamics AX 4.0 SP 2
Direct upgrade using the source-to-target model.
Microsoft Dynamics AX 2009 SP1 (without Retail
components)
Direct upgrade using the source-to-target model.
Microsoft Dynamics AX 2009 for Retail R1 &
Microsoft Dynamics AX 2009 for Retail R2
Indirect upgrade. You must first upgrade to Microsoft Dynamics
AX 2009 for Retail R2 Refresh.
Microsoft Dynamics AX 2009 for Retail R2 Refresh
Direct upgrade using the source-to-target model.
Microsoft Dynamics AX 2012 (without Retail components)
Microsoft Dynamics AX 2012 Feature Pack
Microsoft Dynamics AX 2012 R2
In-place upgrade on a single system.
No source-to-target workflow is used.
In-place upgrade on a single system.
No source-to-target workflow is used.
In-place upgrade on a single system.
No source-to-target workflow is used.
What is the
upgrade
project value?
What are my
goals?
Goals
Define the customer’s
benefits from the new
version
Functional design
must be approved by
the customer
Functional data
analysis
Upgrade all ERP data
to Microsoft Dynamics
AX 2012 or just a
subset (master data
and balances)?
What is the data
volume and do you
need it all?
How many virtual
companies are there
and what are the data
sharing goals?
Independent
companies or crosscompany?
Do you want to merge
AX implementations or
companies?
What are the number
and types of
customization? Are
they replaced? Should
you re-implement or
upgrade?
What partner (ISV/VAR)
involvement do you
need?
• Functional Analyst and Technical Engineers who understand the
Upgrade Framework and AX 2012 are key!
• Functional specifications for moving/deleting/changing of
customizations (eg. Date Effectivity, Office Addin, Financial
Dimensions)
• Lifecycles Services for Project Estimation
• Work with Business leaders to implement a Code Freeze strategy
close to the end-game
Process
• Always follow the checklist steps and upgrade Data Dictionary ->
Code -> UI
• Always upgrade layer-by-layer
• Many Forms and Reports will be rewritten
• Always use a Baseline Database
Gotcha’s
• Never do preprocessing then import the AOD’s for code upgrade
• If you use xpo export/import for upgrades make sure you keep
IDs
• Never delete Data Dictionary elements; use SYSDeletedObjects
Production
Production Active
active on
3/AX 4Ax4
AX AX
AX2009/
Production
Preprocessing
Upgrade
operations
Delta
Data Copy
preprocessing
Upgrade
operations
100%
80%
Live on production
Single user
Post
Processing
processing
Production Active
active
on AX
on
AX 2009
2012
Upgrade
operations
Production
20%
Downtime
Downtime
• Merging companies / splitting data should be done separately before
upgrade
• Clearly Define downtime window requirements
• Ensure appropriate Hardware is budgeted and purchased well in advance
• Determine how much upgrade script development is required.
• Consult with your VARs and ISVs to check if they have upgrade scripts in
place
• Always follow the checklist
• Perform Upgrade Readiness in production AFTER a successful complete end to
end test run
• Use the State transfer tool to reuse work
• Several cycles to update the data: scripts for customized tables, unique data
tuning, and repeating until the required time window
• Multiple iterations are required (including a least 2 successful iterations)
• Run through cleanup routines in some Periodic menus and IDMF
Source-to-target
Upgrade In Place
From Microsoft Dynamics AX 4.0/2009
From Microsoft Dynamics AX 2012
Bulk copy program (BCP)
No BCP (ie. In Place)
~2600 target scripts
~110 upgrade scripts
Can upgrade into multiple partitions
Only upgrade into a single partition
Fast database synchronization
Longer database synchronization
Create test system
Create
development
system
Upgrade
customer model
Duplicate existing
production
system to create
the test system
Duplicate test
system to create
the development
system
Upgrade the
code in other
models for each
higher layer
Run AX 2012 R3
setup on the test
system and
backup
Import prepared
R3 ISV models
into development
system
Import upgraded
model store into
the test system
Test data
upgrade
Perform data
upgrade on the
test system
Upgrade
production
system
Back up the
database
Upgrade the core
production
system
Upgrade other
server
components and
clients
Code Upgrade
• Understand the bootstrapping steps
• Load new Microsoft Dynamics AX 2012 R3 license
• Have ~ 100 GB of temporary hard disk space spare
Data Upgrade
• SYSDeletedObjects62 is for In-place upgrade
Performance Analyzer
for Dynamics
SQL Profiler and Microsoft
Dynamics AX Performance
Analyzer are useful for
debugging performance
slowdowns
http://archive.msdn.microsoft.co
m/DynamicsPerf
Backups
Back up database after each
step!
Data purging and
archiving
Do not purge/leave behind
companies, upgrade all
companies at once
Purge and archive data via
intelligent data management
framework before upgrade
User acceptance test
Trainings
Core business processes and
key scenarios on upgraded
database with your data and
custom code in place
User trainings are very
important steps and user
acceptance tests can be used as
part of that
Business scenarios that must be
supported after the upgrade in
order to make a go/no-go
decision
Security
Multiple iterations
Additional time for designing
and testing security setup
Plan at least two full test runs
that are successful prior to
running the live upgrade
Create a list of post-upgrade
validation tasks and plan how
they will be tested
Post-upgrade tasks
Data verification
Static post-upgrade data
analysis
Identify your key business
processes/scenarios that must
be supported by your Microsoft
Dynamics AX 2012 instance
Rely on data upgrade test
iterations to bring data forward
to Microsoft Dynamics AX 2012
and test code upgrade
Freezing
Troubleshooting
Freeze for existing master
data for preprocessing period
is required
Data consistency issues
during upgrades
http://blogs.msdn.com/b/axsu
pport/archive/2012/11/05/tro
ubleshooting-dataconsistency-issues-duringupgrades.aspx
All tests should have a high
level of data validation testing
20% increase in application size from R2
Existing AX 2012 Customizations
Data Upgrade
• Changes to Work Breakdown Structure and Resource Assignment (Project
Management/Resource Management modules)
• Changes to Warehouse and Transportation sets limitations that regular
warehouses do not. Dimensions might not work with WAX items.
• New Call Center Module impacted Order Management and Financials
Code Upgrade
Data Upgrade
Create Baseline DB by default
Auto Method Merge
Major Version Upgrade ~100 new scripts
Minor Version Upgrade ~60 new scripts
6.2 -> 6.3 ~60 scripts
or //B conflict
Changed by partner
B`
Added by partner
C
C
C
D
//B
Changed by Microsoft
D
6.2
6.3
Added by Microsoft
• How long does an upgrade take?
• Should I upgrade or migrate?
• I am currently in an ‘in flight’ upgrade. Should I continue
or move to R3?
• Can I upgrade earlier databases into an already upgraded
DB?
Check customer
motivation
Plan your upgrade
project
Analyze your source
Check functional
requirements
Purge or archive
historical data
Check and tune
performance
Make backups for
every step
Test the result
http://go.microsoft.com/fwlink/?LinkId=238709
http://www.microsoft.com/enza/download/details.aspx?id=14599
http://blogs.msdn.com/b/axsupport/archive/2011/12/11/planning-your-data-upgrade-to-microsoftdynamics-ax-2012.aspx
www.microsoft.com/dynamics/axtechconference