Book Image

Microsoft Dynamics AX Implementation Guide

By : Yogesh Kasat, JJ Yadav
Book Image

Microsoft Dynamics AX Implementation Guide

By: Yogesh Kasat, JJ Yadav

Overview of this book

Microsoft Dynamics AX is Enterprise Resource Planning (ERP) software that supports multi-site operations across various countries, providing international processing within the company. It is an ERP solution with a lot of features and functionality, and it provides support across the fields of financial, distribution, supply chain, project, customer relationship, HR, and field service management. This book is all about simplifying the overall implementation process of Dynamics AX. The purpose of this book is to help IT managers and solution architects implement Dynamics AX to increase the success rate of Dynamics AX projects. This all-in-one guide will take you through an entire journey of a Dynamics AX implementation, ensuring you avoid commonly-made mistakes during implementation. You’ll begin with the installation of Dynamics AX and the basic requirements. Then, you’ll move onto data migration, reporting, functional and technical design, configuration, and performance tuning. By the end of the book, you will know how to plan and execute Dynamics AX right, on your first attempt, using insider industry knowledge and best practices.
Table of Contents (23 chapters)
Microsoft Dynamics AX Implementation Guide
Credits
About the Author
Acknowledgments
About the Author
About the Reviewers
www.PacktPub.com
Preface
11
Testing and Training
Index

Best practices and recommendations


Here are a few considerations to keep in mind while designing your integration solution for Dynamics AX:

  1. Simplify the overall architecture and try to reduce the number of integrations between applications wherever possible. It is one of the areas that cause recurring issues in production.

  2. Define clearly the master system for each data element, even though you may have it stored at multiple places. In some cases, this may have to be defined at the field level. For example, a customer master is stored in CRM and Dynamics AX as well. CRM might be the master for all the customer information except credit limit.

  3. Ideally, you should avoid duplication of data across multiple systems, although in some cases you cannot avoid it for business reasons or for systems to work. For example, customer records are required in both, the CRM system and Dynamics AX. However, you can opt not to integrate the CRM-centric customer information that may not be needed in Dynamics AX...