I've heard that due to all the bugs in Inventory Adjustment, Inventory Costing is not used in Germany by localisation, there simply some reports and then G/L Posting of Inventory Value / COGS is done by hand.
Maybe this is a good idea - it has some drawbacks but at least it surely works. Better have a bycicle that works than an airplane that crashes.
I wonder whether we could use this idea at other countries too?
My idea is the following:
- Put all your Items on Standard Costing. It will work right 99% of the time, you will only have problems in that rare case if there are two different purchases in your stock, on different costs. You simply take note of these cases and deal with such issues at the end of the financial year like revaluating etc.
- At the end of the financial year, run a report that does "backwards FIFO calculation". That report would be simple and therefore hopefully bugless. It tells you how much your Inventory Value is. Then you subtract it from the starting Inventory Value of the finanial year + Purchases and then you have your COGS, and can happily post in the G/L and make the statements.
- This simplified FIFO report would simply take current inventory at hand (summed up in all Locations) and just list the oldest Purchase/Pos Adj/Output entries with a typical double loop, exiting the loop when either the total qty. equals current inventory or all positive entries are used up.
What do you think of it?
0
Comments
Some companies even use multiple costing methods like manufacturing division use ABC or standard, raw material uses FIFO, finished goods use LIFO (based on inflation rate consideration).
Have you corrected your blog that you wrote there FEFO, meanwhile in Navision, there is no FEFO ? your blog that explains about inventory, you posted it several days ago.
Rgds,
Johnson
sea-navision-community-subscribe@yahoogroups.com
detail in:
http://sea-navision-community.blogspot.com
to me it's like, for whole year you don't know what is your actual whole inventory value, profit....
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
I have not corrected it, because FEFO is not an inventory costing method but a picking method, and I quite clearly wrote that Navison does not support it. I wrote about because I want to make people know it's important in the food/chemical industry.
Deadlizard:
Are you joking? I have spent at least 30 days from Navi 3.6 to 4.0 figuring out different bugs in Inventory Adjustment... want some examples? Roundings by several millions. Transfers not getting actual cost, only expected. Error message complaining about Bin Code. Endless loops. "Another user has modified the record". Stupid valuation date for Manufacturing with average costing therefore completely idiotic costs. BOM Journal not getting adjusted. And so on.
Oh yeah, those problems.. But other than that, it's working great!
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book