ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Manufacturing >> PO-C Big Problem
http://www.istechforum.com/YaBB.pl?num=1144940271

Message started by gtladmin on 04/13/06 at 06:57:51

Title: PO-C Big Problem
Post by gtladmin on 04/13/06 at 06:57:51

:o When we rec'd a PO yesterday that had some make from parts on it, the computer did something weird and kept receiving parts over and over again--it was like the program was stuck in a loop. We should have rec'd 12 and it rec'd 1240 of one of the parts. It is a strange thing, and now we have six pages of entries in the GL-O that have to be deleted.

We are guessing that is what has to be done, but we know whatever we do in the GL it will not fix the inventory, so how do we fix the inventory, too? The OH quantity is also incorrect.

Another receiving went crazy too, creating a duplicate receipt of an item, and doubling the amount that went into rebni on the second receipt. That is now out of balance too. We did a negative receipt to the PO which fixed the amount on hand in the inventory, but now on paper, we didn't receive anything. Uh oh! We need help!

Firstly, how to we correct these problems? We are desperately trying to close our month, and we've temporarily put a hold on alot of daily tasks so we don't make this worse than it is.

Secondly, how do we track down what's going on? Is this a program issue? Could someone be running something else in DBA at the same time that's causing these glitches?

There are absolutely no network errors logged in any of my error logs, no one getting any weird network issues to suggest its a network resource or other issue, and no other log files have any recorded errors recently.

???

Val

Title: Re: PO-C Big Problem
Post by JNAPIER on 04/13/06 at 08:39:57

I would do a negative PO and receive it. Does the PO receiver have the 1240 units and value for them. If so the neg PO will reverse everything and you don't want to delete any of the GL-O entries. You would also want to pick to pay the bad trans. and print the voided check so your vendor won't see any of the trouble.

John

Title: Re: PO-C Big Problem
Post by JEMM on 04/13/06 at 09:01:52

Val,

What version of POC are you running? I thought we fixed this looping make-from part bug last summer.

Mike

Title: Re: PO-C Big Problem
Post by gtladmin on 04/13/06 at 09:31:27

John, we'll give that a try in our test company, not sure if that will do it or not.

Mike, we are running 2005.1 version with 5/17/05 update.

Val

Title: Re: PO-C Big Problem
Post by JEMM on 04/13/06 at 10:32:44

If you update to a newer version of POC, it should fix the repeating make-from bug. (It was fixed June 8, 05).

Mike

Title: Re: PO-C Big Problem
Post by gtladmin on 04/13/06 at 12:45:55

Thanks, Mike, we'll do that.

Regards,

Val

Title: Re: PO-C Big Problem
Post by gtladmin on 04/14/06 at 08:52:03

Ok, here's where we stand on this:

No PO receiver - report does not show this PO.
Inventory UOH is overstated.
Not showing in RNI

We deleted all the entries in GL-P. Nothing showed up in
INVTXN or BKAPHPO OR BKAPHPOL.

So, how do we correct the overstated UOH? (What are all the transactions we need to do clean this completely).

Once we fix that, can we simply re-receive the PO and hope for the best?

Val

Title: Re: PO-C Big Problem
Post by JNAPIER on 04/17/06 at 07:21:47

Well if you deleted the GL-O transactions and you didn't raise the GL Value for the inventory, you could do an inventory adjustment to get the UOH correct. You would also want to delete the GL-O transactions again so you would not affect your inventory and cost of goods.

John

Title: Re: PO-C Big Problem
Post by gtladmin on 04/20/06 at 12:21:44

Hi John,

Thanks for your input. It was really a mess, but we were finally able to fix. It turned out there was definitely an issue with that PO (and also as it turns out someone had turned on serial control for the part--but that didn't cause the problem). We ended up deleting the PO and recreating it, fixing the serial number issue, re-received the PO and all is finally well. What a fiasco! ;-)

Val