A new flavor to my feed
I have a humble request to all of you subscribing to my blog's feed. I've just configured a Feedburner feed for this blog, which will allow me track the blog…
Not-so-elementary costing: The Change
They say the only constant is change. I’d say that the only other constant is error. We humans tend to err. Give a repeatable task to a human, and they’ll mess it up every once in a while. Some call it the human factor.
One of the many repeatable tasks in Microsoft Dynamics NAV is setting up items. If you remember my rant about mandatory fields, and how I said they were baaad, there might be an even more baaad kind of fields: the default value fields. Because the system simply inserts a value into these fields without asking for your say, and if anything is easy, it’s only so easy to overlook these. Yep, you have a chance to voice your oppinion on these, but having got to hurry for a cup of coffe with Mary from accounting, admit it, you’re gonna leave that default FIFO costing method for an item every once in a while, even though it should really have been Average. Then you’ll start posting. Then your phone rings and starts screaming at you about a moron who screwed up items again.
Purchasing Services: Inventory Value Zero
I’ve stumbled recently upon a support request, where a partner asked if there was a possibility to register purchases of services in Microsoft Dynamics NAV. When it comes to selling services, such as consulting, or repairs, NAV is your true friend, because you can use Resources to register sales against them. However, purchase documents don’t offer a possibility of purchasing resources, so you are left to some workarounds.
Output journal confusion
A few days ago, I’ve got a question from a customer, about an alleged bug in Microsoft Dynamics NAV. According to online help, when you are posting output in manufacturing module, the last line of the type Output in the journal will actually adjust the inventory level. However, what is not explained is how the figure in this field is calculated, and why exactly that way.
When you decide to post an output of a production order, you specify the released production order for which you want to post the output, then call the function Explode Routing. After this function completes its chore, users unfamiliar with how manufacturing works can get quite confused, because two of the fields the procedure fills in contain unexpected values. These two fields are Output Quantity, and Scrap Quantity.
Scrap doesn’t just happen
In reality, if you need 1,000 of whatever product, the manufacturing process is rarely going to yield exactly 1,000 of it, even if you feed into the first operation the exact quantities of raw materials system calculated as gross requirements. The process may produce 980 or 1,020, but is hardly ever going to be exactly 1,000. If you didn’t take scrap into account, or you took incorrect scrap into account, your actual output from the process might be much more unpredictable, with huge variances. Variances are always a problem, only they don’t have to be that big a problem in all scenarios.
- Go to the previous page
- 1
- …
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- …
- 21
- Go to the next page