- Microsoft Dynamics AX Implementation Guide
- Table of Contents
- Microsoft Dynamics AX Implementation Guide
- Credits
- About the Author
- Acknowledgments
- About the Author
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Preparing for a Great Start
- 2. Getting into the Details Early
- 3. Infrastructure Planning and Design
- The Dynamics AX components and architecture
- Planning the system topology
- Cloud deployment
- Industry best practices and recommendations
- Summary
- 4. Integration Planning and Design
- Integration planning
- Integration technologies
- Integration design and development
- Best practices and recommendations
- Summary
- 5. Data Migration – Scoping through Delivery
- Managing scope – simplifying data migration through rightsizing the scope
- The design and development phase
- Data mapping and transformation
- Planning the data migration
- Selecting the tools for data migration
- The Data Import/Export Framework
- Data migration execution tips
- Initial templates for business
- Extracting source data into SQL tables
- Never rename/repurpose fields
- Considering premigration steps
- Considering postmigration steps
- Changing SQL to simple recovery mode
- Multithreading and max DOP
- Index and statistics maintenance
- Disabling the AX logging
- Considering SQL updates on migrated data
- The SQL import – through caution and expertise
- Managing configurations
- Configuration management simplified with DIXF
- Reviewing and deciding on the configuration
- Data validation
- A classic example of a data migration issue in projects
- Summary
- 6. Reporting and BI
- Gathering BI and reporting requirements
- Knowing about reporting tools
- Mapping reports and identifying gaps
- The custom report development
- Summary
- 7. Functional and Technical Design
- 8. Configuration Management
- Configuration planning
- Collecting the configuration data
- Configuration tools
- Configuration data management
- Summary
- 9. Building Customizations
- Getting ready for development
- The development process
- Conceptualization
- Data design
- The business logic
- The user interface
- Security
- Coding best practices
- The Application Lifecycle Management (ALM)
- Summary
- 10. Performance Tuning
- 11. Testing and Training
- 12. Go-live Planning
- 13. Post Go-live
- Initial stabilization
- Proactive preparation – what's coming
- Post-implementation review
- Why post-implementation review?
- Key factors to get the most out of PIR
- Preparing for PIR
- Pain points from experience
- Post-implementation review – an AX 2012 customer
- Current state – key challenges
- The unused potential of Dynamics AX
- Improvement opportunities – processes and systems
- New features from the next release
- Summary
- 14. Upgrade
- When to upgrade
- Upgrading options
- The Dynamics AX upgrade process
- Summary
- Index
With every iteration of data migration, you need to get progressively better. To achieve this, data validation needs to be a well-documented repeatable process and needs to start early on. Do not wait until the deployment stage to engage the business. Here are a few tips to make this process smoother:
Define validation test cases for both the business and IT validation.
- IT validation: This generally includes verifying record counts, totals, and referential integrity by running tools such as Consistency check (Consistency check is a tool available in Dynamics AX. It validates and fixes referential integrity issues. It can be found in System Administration module, periodic section). You need to acquire different types of validation scripts; it is a good idea to have scripts for validating extracts, if there was an issue in extraction, you can catch it sooner in the process.
- Business validation: The business owns the data, and it is critical to have the business involved to start data validation early on.
- Run the reports that the business is going to use. For example, comparing the AR aging reports between the old and the new system, verifying financial statements, and so on.
- Review the data on screen and use it in the processes for which the data is migrated. For example, running a check-run to verify whether you can pay your vendors and print correct information on payment advices.
- Usability of data for future transactions and reporting: validate your business processes that use the migrated data. Use migrated data in consequent rounds of CRP.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.