[Ronald McVicar]

Where does one find the “stuff” core to the design and best practice of NAV?
In the past, at least for me starting way back to the early 90’s many of the then “Accounting Software” packages had this stuff in the documentation (manuals, certification training, and in the dialog of those who used the software and code day to day). Many of these systems though had very solid accounting: GL, AP, AR, etc. had key areas that were very industry solid.  Not only driven by the certified cost accountants and industry but from manufacturing, inventory management, etc.

So for NAV what about Inventory? what are the core business  rules that it adheres to?  So if some asks are locations essential? Or what about costing mechanisms? (e.g., LIFO, FIFO, Average, etc.)?  As now a customer and hearing on this forum, we will hear threads like “… our partner said locations are not necessary, or never use average cost or can you?  Or No one uses Lotted and Serialized inventory or can you?

Years ago these were the elements that said well if you want that Use this system or that?  Like in the mid-90’s if you wanted one of the better project and cost accounting solution you used “Solomon or Dynamics SL” .  Then came along Olympic System Project / Cost Accounting for Great Plains (Dynamics GP) and so you had another solid solution that adhered to sound best practice.  Then (at least here in the US), we found new life in General Ledger in Navision but it (then) had it’s own database; and then it had everyone else’s new database (Microsoft SQL Server) that did not run very fast especially if you had serialized inventory.

No of course like raising children, people do all sorts of things and do just fine.  That is why in the 60’s and 70’s in San Francisco you could take a job in a office that had no chair or chairs were large bouncy balls; and today still no chairs at all and you just stand at a desk that if you set down your chin is up against the table top.  

So sometimes it is good to have old school not to shame people but to provide roots and best practice which can allow sanity (can).

This being said, how about locations in NAV? If you don’t use them what does that mean if you are a business that lives on inventory (e.g., consumption or sales, etc.)? Is it a costing thing, does it ensure if you have locations on then this or that works; and if you done it won’t? 

ps. I know this is not a Twitter feed but a little color, spice, etc. helps though I do drink my coffee straight up but it has to be solid (robust) coffee not tea.

——————————
Ronald McVicar, IT Software Mgr
NSP (Quality Meats)
nspproteins.com
——————————

[Cynthia Priebe]

unfortunately I couldn’t agree with you more that software documentation has changed over the years.

Your current best source of “standard” NAV documentation (considered to be equivalent to the manuals of the past) is Microsoft Docs. However, if you have purchased a vertical solution that has modified the standard, this documentation may not apply and you may not even be aware of it.

As for system “best practices,” some are indicated in Microsoft Docs, more can be found by following Microsoft MVPs, while others come from practice (experience.) Choosing a partner that has this practice and experience (not just the organization as whole but the members of your specific implementation and support team) is very important. Your partner should be someone that you can rely on to bridge the gaps in the standard documentation and help you make the proper decisions.

For example, there is nothing that says you must define a location in NAV, however if you don’t you will be more limited in the standard features available to you. For example, you can still cost based on the various methods, however if you suddenly add another physical location and want to track inventory (including cost) separately by your now 2 locations, you need to configure your system to use locations and you have a project on your hands. If you would have setup one location from the start, adding the new location would be a relatively simple task, not so much a project. However, because setting up a single location when “you don’t need it” can add minor complexity that may provide no value now or in the near future, so no location in NAV may be the right answer for you. All pros and cons must be weighed. I recommend if you are using inventory you consider using one location, but not every company decides to do it. Whatever decision is made, it is my job to make certain the ramifications are understood. 

When it is an option in NAV and someone tells you “never” or “no one”, I would question it. Some settings are for legacy brought forward, so “not today” would be a better answer. Other settings may not pertain to your local requirements, so “not for this local version” would be a better answer. Or maybe your consultant does not have experience in a setup, so “not in my experience” is a better answer. “Never”, “No one,” and “Always” should be replaced with “For your requirement/local/company I don’t recommend.” This is hard to do when a customer may be looking for a decisive answer. Your consultant needs to be strong enough to admit “I don’t know,” “I need to find out,” or “we will need to test.” 

And finally, Dynamics Communities and some of the YouTube videos posted by MVPs, Microsoft and VAR’s are your best source for general training depending on whether you are looking for something interactive or not. For anything more targeted, your partner should be your best bet. Your partner should become familiar with your organization and your implementation and be able to meet this need. I have seen organizations be penny wise and pound foolish when it comes to paying for partner services (yes, I work for a partner.) If your partner is experienced in implementing, training and supporting your solution, they should be your most efficient thus affordable option for targeted training and support. 

Hopefully you find this perspective helpful.

——————————
Cynthia Priebe MCP, DCP
Senior Analyst and Project Manager
Liberty Grove Software

Join us at User Group Focus in Houston, March 13-14, 2019.

Woo-hoo! There is a track for Business Analysts this year.

Join me and my co-panelists and presenters at the following sessions:
BAN75 – Ask the Analysts
CFO90 – Ack! My A/P Person Just Left, What Do I Do Now?

Not for you, check out the other great content at https://www.ugfocus.com/focus/locations/houston/houston2
——————————
——————————————-