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

The logistics application

Similar to Production Orders in the standard application, the processes in our logistics application are status driven rather than transaction driven. This is why this part of the application does not have a journal with entries. The tables can have archived copies but they are not part of a normal registering or posting routine.

For the examples in this part of the chapter, we should change the default Role Center to Logistics Role Center (123456700) in the Profile table (2000000072).

Designing the table and posting schema

If we look at the structure of the logistics application, we can see that the typical posting transactions are missing. The application uses a status-driven workflow based on events which are defined in the triggers of the tables.

The logistics shipment and shipment details have a lot of similarity with the shipments from the warehouse. Still we have chosen...