Accounting and NAD

With Advanced Distribution the location handling is so much better than standard Navisions (assuming what I am looking at in Solutions 3.0 mirrors NAD). Does anyone have different geographical location processing in place in one company with the accounts being formulated by location? It seems to me that the location field is not written back to the GL Entry table so this would not be possible, but has anyone done it? Steve

Hi Steve, I did this once for FIFO costing method. It is not very difficult. Later we found that we do not need this as far we can print inventory valuation report by location. Sometimes it is better use separate companies for each location and use inter-company transfer function. (PS: Solution 3.0 does not mirrors NAD) Valentin Gvozdev BMI Inc.

On a related matter we had problems with the Department Codes and the Project Codes since these codes are nowhere on the Warehouse Journal or the Phys Inventory Journal. Unfortunately at one site we had these fields as Mandatory in the GL Therefore posting a Stock Take or Warehouse Journal Stock Adjustment was not possible until the fields were added to the tables and the forms and the codeunits.

With thoughtfull structuring of Location Code you can get what you want. Prefix the location with the Location reference 01-Main 01-Holding 01-Stock 02-Main 02-Holding 03-Stock Then just filter for Inventory valuation by locations 01* Inventory can show what you have and where it is, also where it has been sold from. Buy stock in to a Department or project Code relating to the warehouse Then use standard Customers Departments and Projects for Geographic “Regions and districts” G/L Reports to show turnover for the region etc: David Cox MindSource (UK) Limited Navision Solutions Partner Email: Web: Edited by - David Cox on 2001 Apr 18 08:18:36

Good point David That would work well but the problem we found was that if Warehouse Management is enabled then the Warehouse journal automatically creates and tries to post an Item Journal for you. Which it cant if the Department Code is mandatory. This is probably a discussion for another thread but we seemed to find that a lot of things worked fine with some tweaking until Warehouse Management was turned on. Simon

The database related to inventory is totally re-written in 3.0. We were involved in the design exercise and you will probably find that there is a major change in the inventory. It is much more location-centric (as contrasted with the current item-centric orientation in NF), somewhat along the lines of NAD. This has allowed Navision to address the serious weaknesses in pricing, costing, lot/serial, etc. that exist in all the databases. It apparently will also address landed cost (I’ll believe that when I see it!), physical inventory (stocktaking), and the department/project issue noted above. If you have a user who needs location centric inventory, I’d wait if you can. Otherwise, try to come up with a very low impact scheme or be prepared to tell your user that 3.0 has been delayed until 2004! Allen Beck President Beck Consulting Alameda, CA & Bellevue, WA 800-456-8474

I hope that everybody is satisfied with this thread, and that nobody will be upset if I lock it.