Evergreen

Bug #1257915
Comment #10

Comment 10 for bug 1257915

Revision history for this message

Leslie St. John (lstjohn-deactivatedaccount) wrote on 2017-04-05: Re: [Bug 1257915] Re: Acq: purchase orders stay "on-order" with some lineitems received and the rest canceled

#10

on test, po 844. Created list placed order received 3 of the 4 items. 4th I
can't cancel - i get Event: 10102:ACQ_NOT_CANCELABLE -> The object is not
in a cancelable state.
lineitem 37900
so I can't do the test!
Leslie

Leslie St. John
*PINES Services Specialist*
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345-4304
404-235-7129 tel
404.235.7201 fax
www.georgialibraries.org
www.gapines.org

On Wed, Apr 5, 2017 at 11:24 AM, Chris Sharp <email address hidden>
wrote:

> Working branch here: http://git.evergreen-
> ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/
> user/csharp/lp1257915_mark_po_received_with_canceled_lineitems
>
> I have tested by un-receiving an already received lineitem on a PO with
> canceled items, then re-receiving the lineitem's copies. The PO should
> then be marked "received".
>
> What I haven't yet tested is what happens when you cancel an item that
> is the only un-received/non-backordered item on a PO.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1257915
>
> Title:
> Acq: purchase orders stay "on-order" with some lineitems received and
> the rest canceled
>
> Status in Evergreen:
> Confirmed
>
> Bug description:
> Seen both in Evergreen master and 2.3.4, purchase orders can get
> "stuck" in the "on-order" state even when all the lineitems belonging
> to it have a more final status.
>
> It's simple enough to reproduce.
>
> - Create a purchase order with, say, 3 lineitems and 2 copies on each of
> these.
> - Receive the first two lineitems outright.
> - Receive one of the copies on the last lineitem and cancel the other.
>
> You'll see the PO's own state is still "on-order" when "received"
> would make more sense.
>
> I'm pretty sure "received" would make more sense even in cases where
> you had a 100 item PO with 1 item received and 99 canceled.
>
> Does anybody have a case to make for the current behavior or for a
> third way?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1257915/+subscriptions
>

On Wed, Apr 5, 2017 at 11:24 AM, Chris Sharp <1257915@bugs.launchpad.net>
wrote:

> Working branch here:  http://git.evergreen-
> ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/
> user/csharp/lp1257915_mark_po_received_with_canceled_lineitems
>
> I have tested by un-receiving an already received lineitem on a PO with
> canceled items, then re-receiving the lineitem's copies.  The PO should
> then be marked "received".
>
> What I haven't yet tested is what happens when you cancel an item that
> is the only un-received/non-backordered item on a PO.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1257915
>
> Title:
>   Acq: purchase orders stay "on-order" with some lineitems received and
>   the rest canceled
>
> Status in Evergreen:
>   Confirmed
>
> Bug description:
>   Seen both in Evergreen master and 2.3.4, purchase orders can get
>   "stuck" in the "on-order" state even when all the lineitems belonging
>   to it have a more final status.
>
>   It's simple enough to reproduce.
>
>   - Create a purchase order with, say, 3 lineitems and 2 copies on each of
> these.
>   - Receive the first two lineitems outright.
>   - Receive one of the copies on the last lineitem and cancel the other.
>
>   You'll see the PO's own state is still "on-order" when "received"
>   would make more sense.
>
>   I'm pretty sure "received" would make more sense even in cases where
>   you had a 100 item PO with 1 item received and 99 canceled.
>
>   Does anybody have a case to make for the current behavior or for a
>   third way?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1257915/+subscriptions
>