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

The posting routines


Dynamics NAV has one big key word (among others), called post. If you read the word post anywhere in an application or see the following icon, it means that if you click on the button, a routine will be run and this will lead to posted documents and posted entries that are on their last stage. It is the trusted data that won't change anymore. This is important for many IT and accounting audits.

As explained in The data model section of this chapter, Dynamics NAV has some tables called Entries (G/L Entries, Cust. Ledger Entries, Vendor Ledger Entries, Item Ledger Entries, and so on) that correspond to transactions related to master data. The only way to insert data into entry tables is through the posting routines. Numerous validations are carried out during posting routines as the system has to check whether all data is correct and that no inconsistencies exist.

One unique posting process usually creates multiple entries, and all of the entries are related and consistent...