Book Image

Implementing Microsoft Dynamics NAV - Third Edition

By : Alex Chow
Book Image

Implementing Microsoft Dynamics NAV - Third Edition

By: Alex Chow

Overview of this book

Microsoft Dynamics NAV 2016 is an Enterprise Resource Planning (ERP) application used in all kinds of organizations around the world. It provides a great variety of functionality out-of-the-box in different topics such as accounting, sales, purchase processing, logistics, or manufacturing. It also allows companies to grow the application by customizing the solution to meet specific requirements. This book is a hands-on tutorial on working with a real Dynamics NAV implementation. You will learn about the team from your Microsoft Dynamics NAV partner as well as the team within the customer’s company. This book provides an insight into the different tools available to migrate data from the client’s legacy system into Microsoft Dynamics NAV. If you are already live with Microsoft Dynamics NAV, this books talks about upgrades and what to expect from them. We’ll also show you how to implement additional or expanding functionalities within your existing Microsoft Dynamics NAV installation, perform data analysis, debug error messages, and implement free third-party add-ons to your existing installation. This book will empower you with all the skills and knowledge you need for a successful implementation.
Table of Contents (19 chapters)
Implementing Microsoft Dynamics NAV Third Edition
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Defining the internal processes


Once the goals of the project are clear, and when the company knows what they want to accomplish with their brand new ERP, it's time to go into details and write down all the company processes one by one that will have to be done or supported by Microsoft Dynamics NAV.

When you think about your processes, don't just expose what they should theoretically be. Ask the people who are actually carrying out those processes about what they really do. Also ask about the exceptions to the processes, as handling exceptions for a normal process usually requires more time from end users.

You may want to take this opportunity to eliminate exceptions for a normal process by changing how the process works. Exceptions are basically processes that are created to do something that a normal process does not accommodate. So essentially, the user has to pay special attention and spend extra time to handle these exceptions. What's worst if they start building exception processes...