Moving to Standard Cost

aleix1979

Hi there,

I'm moving a database from Average to Standard Cost. The weird thing is that when trying to change the method to Standard for one item it tells me that I cannot do that because there are Item Ledger Entries for that Item.

I've totally emptied the stock for all items (in other words, there is no "Remaining Quantity" for any Item Ledger Entry lines) so I was a bit surprised about the message since it would imply you cannot ever change the costing method in your system :?

Any comments?

Alex_Chow

If you do a search on change costing method, there are a gazillion topics on how this should be done.

Kowa

Alex Chow wrote:

If you do a search on change costing method, there are a gazillion topics on how this should be done.

That is true, but in older versions (2.x) there was a check only for open ILE, now the function TestNoEntriesExist in the item table checks for any ILE for that item so bringing the inventory to zero does not work anymore unless you comment that out (and know what you are doing).

Alex_Chow

Kowa wrote:

unless you comment that out (and know what you are doing).

the and know what you are doing should be bolded.

Actually, i wouldn't even recommend to remove the code at all...

Kowa

MS recommends that the items get new item nos if the costing method is changed. This is an older topic on the same subject:
http://www.mibuso.com/forum/viewtopic.php?f=1&t=15161
But of course usually no customer likes to get used to using new item numbers, so that isn't very practical.

kine

Kowa wrote:

MS recommends that the items get new item nos if the costing method is changed. This is an older topic on the same subject:
http://www.mibuso.com/forum/viewtopic.php?f=1&t=15161
But of course usually no customer likes to get used to using new item numbers, so that isn't very practical.

Than renumber the old one and create new with same no. ;-)

Alex_Chow

kine wrote:

Than renumber the old one and create new with same no. ;-)

That is how MSFT recommends it.

Kowa

Alex Chow wrote:

kine wrote:

Than renumber the old one and create new with same no. ;-)

That is how MSFT recommends it.

That's okay as long as only a few items need to changed, but not on databases with thousands of items and millions of ILE.

Alex_Chow

Kowa wrote:

Alex Chow wrote:

kine wrote:

Than renumber the old one and create new with same no. ;-)

That is how MSFT recommends it.

That's okay as long as only a few items need to changed, but not on databases with thousands of items and millions of ILE.

We wrote a process that does this automatically at night time. Essentially, they put the old item number and the new item number in a table, and the process goes through each item and renames it to the new item.