Liquidity, Cost Accounting and Kitting

  • Post comments:5 Comments
  • Reading time:7 mins read

It’s hardly any news for the lucky 21 countries which have had them by default for about two years, but for other 18 which haven’t, there is an alarmingly low awareness about three interesting NAV functionalities: Liquidity, Cost Accounting and Kitting.

These three have been named Local Functionality, which means they are a part of a localized version in some of the countries. For other countries, this functionality is not available by default, but it doesn’t mean it can’t be licensed or implemented for customers in other countries as well.

(more…)

Continue ReadingLiquidity, Cost Accounting and Kitting

Natural selection: death of dataports

  • Post comments:2 Comments
  • Reading time:4 mins read

image It’s the survival of the fittest game, that stuff that happened to the dataports. You know dataports? That class of NAV objects that’s used to move data back and forth in text format?

It’s really funny what has been going on with them lately. They evolved, then degenerated. Today, they are an endangered species. A release or two, and they might be gone for good. Just like dinosaurs.

(more…)

Continue ReadingNatural selection: death of dataports

History of Microsoft Dynamics NAV

  • Post comments:7 Comments
  • Reading time:11 mins read

This was a part of Chapter 1 in the first draft of my book Implementing Microsoft Dynamics NAV 2009. It was cut to keep page count down and preserve the environment, but I figure that a few electrons pushed through the optical labyrinths of The Internet won’t hurt anyone, so here you get it, in its original form: The History of Microsoft Dynamics NAV.

(more…)

Continue ReadingHistory of Microsoft Dynamics NAV

5th rule of agile ERP: interface where possible

  • Post comments:3 Comments
  • Reading time:6 mins read

imageOne of the biggest absurdities about ERP systems springs from the very word we use so often when describing ERP: integrated.

ERP is an integrated system: it integrates all data and processes into a single application. Different modules look over different aspects of data and processes, but a change in one module automatically reflects in all others.

A fantastic concept. When it was invented, it streamlined processes, boosted productivity and eliminated overhead and error.

So, whenever a new functionality is needed by a company, it should be integrated into the ERP, to benefit from the integrated system. Right?

Wrong.

(more…)

Continue Reading5th rule of agile ERP: interface where possible