Book Image

Microsoft Dynamics NAV 2009 Application Design

By : Marije Brummel
Book Image

Microsoft Dynamics NAV 2009 Application Design

By: Marije Brummel

Overview of this book

Dynamics NAV 2009 is an Enterprise Resource Planning (ERP) software product from Microsoft that can be used for variety of business needs. It is part of the Microsoft Dynamics family, and intended to assist with finance, manufacturing, Customer Relationship Management, supply chains, analytics, and electronic commerce for small and medium-sized enterprises. This book is a focused tutorial on Microsoft Dynamics NAV application development, so you can develop complete applications and not just application outlines. It will show NAV developers how to create different kinds of applications. Different kinds of application are vital in different industries like fashion, automobile, retail, books (education), and other industries. It starts off by introducing the supply chain that you will be using throughout the book. You will implement the Microsoft Dynamics NAV ERP suite and learn how it is set up and customized for various industries. You will be able to customize Dynamics NAV to suit the different aspects of a business such as Financial Management, Relationship Management, Production, Jobs, Trade, Storage, Logistics, and so on. The book will take you through these Microsoft-designed application features and show you how to customize and extend them safely. Thus, you will be able to create a structure of your own in Microsoft Dynamics NAV.
Table of Contents (13 chapters)
Preface
11
Thank you for buying Microsoft Dynamics NAV 2009 Application Design

Sales and purchasing

Traditionally, salespersons are used to working with paper order forms. They would write down the customer name and address, and the items or services required.

In Microsoft Dynamics NAV the paper document is replaced by a sales and purchase document using a header for the general order information and lines to register the items and services.

The posting process breaks down the information in the document into the journals, and posts them so that the end user does not have to worry about this. The application reuses the same posting routines as we discussed in earlier chapters.

Let's look at how the documents and journals tie together by drawing the table and transaction scheme for this:

The first step is creating the document. When we create this Sales Document (Sales Header and Sales Line) nothing is posted. We are only entering information into the system that can be changed at any time.

When we start the Sales Post (Codeunit 80...