[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Purchase orders and partially received shipments
- Subject: Purchase orders and partially received shipments
- From: Charley Tiggs <..hidden..>
- Date: Tue, 16 Oct 2007 19:17:47 -0500
I've finally had some time to pay attention to some odd behavior that
showed up in 1.2.6 that wasn't present in 1.2.5. Today, I got enough
additional information to finally know where to look.
In 1.2.5, I could do the following:
1) Create a purchase order with several widgets on it, 10 each.
2) Receive five each of those widgets against that PO via
Shipping->Ship->Receive
3) Find the purchase order via Order Entry->Reports->Purchase Orders and
click on the "Vendor Invoice" button.
4) Post the invoice (without paying).
5) Search for the same PO and the original PO is still open as there are
still items that need to be received in.
In 1.2.6 and beyond, the behavior changed after step 2:
3) Find the purchase order via Order Entry->Reports->Purchase Orders and
click on the "Vendor Invoice" button.
4) Post the invoice (without paying).
5) Search for the same PO and the original PO is closed and a new one
has been created for the remaining amount due.
This is a little confusing for the warehouse doing the receiving. When
they go to look up the numbers they have received, they see two purchase
orders, one of which is only partially received and the other has
nothing received against it. They can't tell in any way whether the
second purchase order is an order that was tacked on to the original or
if they should ignore the original. At any rate, it makes it difficult
for the person doing the receiving to figure out what has already been
received against that purchase order. This client has instances where a
PO may be received against 5 or more times since they order large
quantities of items and expect to receive them in installments. A
search for such a purchase order would be tedious to manage in terms of
finding out when certain items where delivered.
So, is this a bug? If it's not a bug, can someone explain the logic
behind having purchase orders behave this way?
Thanks,
Charley