ISTech Support Forum
http://www.istechforum.com/YaBB.pl Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> Reconcile Inventory Rounding Difference http://www.istechforum.com/YaBB.pl?num=1133453673 Message started by rmh148 on 12/01/05 at 08:14:33 |
Title: Reconcile Inventory Rounding Difference Post by rmh148 on 12/01/05 at 08:14:33 It appear to me that one of the reasons that we are having rounding errors when you run SM-J-C is that the decimal precision in BKARINVI_B.BKAR_INVI_PCOGS is only 2 decimals. This fields contains a per-unit-cogs-cost and should be 4 decimals to match the precision of the inventory transaction unit-cost. Additionally, quite some time ago I reported that the TOVAL on Type "N" items was being incremented and decremented. I do not believe that this has been fixed, yet. |
Title: Re: Reconcile Inventory Rounding Difference Post by rmh148 on 12/01/05 at 08:27:10 the previously reported incident was posted August 24, 2005. Inventory Transaction Type "C" error. It read, "as part of the reconcilation of book value, I have discovered the reason that many Non-Inventory item's (item type "N") book value is wrong. Non-inventory item, by nature should never have a book value in BKICMSTR.BKIC_PROD_TOTVL. I have discovered that any time there is an inventory transaction type "C", $ Change, DBa is incrementing or decrementing the book value. " |
Title: Re: Reconcile Inventory Rounding Difference Post by Lynn Pantic on 12/01/05 at 09:22:26 SM-J-C does not look at the COGS in the Invoice files so I am not sure what you are referring to when you say it is causing rounding errors. SM-J-C simply reconciles the inventory files to themselves in terms of total quantity and order status versus by Location. As for the C transaction, what version are you on? I just tested and a price change in AP-C does not touch the IN-A Book Value for type N part. This is using the IS Tech 11/18 update. |
ISTech Support Forum » Powered by YaBB 2.1! YaBB © 2000-2005. All Rights Reserved. |