ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Manufacturing >> PO Item Receipt not added to Inventory
http://www.istechforum.com/YaBB.pl?num=1124917334

Message started by Vman on 08/24/05 at 13:02:14

Title: PO Item Receipt not added to Inventory
Post by Vman on 08/24/05 at 13:02:14

My purchaser came up to me with a single-line PO that she had received that did not get put into inventory. (I.E. we had 2 on hand, received 5 more, but total in IN-A was still 2). Inventory transactions showed the receipt of 5. PO shows as being closed for receiving purposes
I was able to edit the data file field with Maintain Database, but IN-A still showed only 2 O/H, unless you hit the locations button- then it showed 7 O/H in the default location (we only have one).
I updated the inventory book value for the part in question, and that fixed everything.
Anyone seen this before?

Title: Re: PO Item Receipt not added to Inventory
Post by Lynn Pantic on 08/24/05 at 15:23:10

Double check the PO - it is possible that the conversion factor on the line was 0.

Title: Re: PO Item Receipt not added to Inventory
Post by Vman on 08/25/05 at 04:06:48

Lynn,

Conversion factor is 1, as viewed on the receiver. It appears that when the PO was received, that it was partially processed, as the transaction was posted, but the O/H quantity in BKICLOC was not updated. Also, last price was set to 0.00.
The particular part on the PO used to have more than one location. We consolidated locations several months (at least) ago, and removed all locations except the default (blank). I ran SM-J-C in report only mode, and this would have fixed the problem by adjusting the O/H to match the transactions, but the program would have also re-created the other location for the item, so it was easier to fix it manually. I mention this because I have had problems in the past with other items that used to be in more than one location.
We seem to be having a more "burps" lately. A few days before the PO problem, we had a sales order entered with Features and Options that did not convert to work orders correctly (quantities were wrong, and some assemblies were not put on W/O's) when SO-N was run. We ended out cancelling every thing out and re-entering.