Acq: Line Items and Purchase Orders cannot be cancelled

Bug #1053015 reported by Jennifer Pringle
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Undecided
Unassigned

Bug Description

Evergreen 2.3beta1

When an attempt is made to cancel any line item or purchase order the system returns the message "Event: 10102:ACQ_NOT_CANCELABLE -> The object is not in a cancelable state. lineitem 215."

My tests were on line items and purchase orders for which the purchase order had been activated. On-order should be a cancelable state.

Individual copies can be cancelled through the Copies page on line items that refuse to cancel.

Revision history for this message
Bill Erickson (berick) wrote :

Hi Jennifer, can you provider more details on how you set up your order? How many lineitems? Anything out of the ordinary? I tried a simple PO with one lineitem in Evergreen master and was able to cancel the PO after activating it. If you could provide specific steps to create the problem, that would be ideal.

Changed in evergreen:
status: New → Incomplete
Revision history for this message
Erica Rohlfs (erohlfs) wrote :

Hello!

Jennifer, I do not know the steps that you took to create the PO and produce the cancellation error. Here are the steps that I took to recreate the error messages.

It took quite a bit of testing for me to finally trigger an error.

I first tested this in version 2.3.2 (since you submitted the ticket for 2.3beta1). I then tested my findings on version 2.5.0 with the same results.

If one or more lineitems are already marked as Received, I could not cancel the entire PO. I suspect it would not be desirable to cancel a PO if one or more lineitems has been received. Perhaps there is a use case in favor for having this ability. Interestingly though, if I paid for the received items and then tried to cancel the entire PO, I received an error message letting me know that a debit had already occurred for the received item(s).

Similar held true for selected lineitems that I tried to cancel. If I had more than one copy on order for a particular lineitem and marked a few of those copies as received, then Evergreen would return an error if I tried to cancel that selected lineitem. I needed to go back into the copy information and un-receive those copies in order to cancel the selected lineitem.

I’m not suggesting that this is the only possible scenario that causes the error. This was just the only way I was able to recreate the errors.

Perhaps a more detailed error message could be included alerting staff to the fact that copies have been received, thus not in a proper state of cancelation.

Attached is an image of the error message for attempting to cancel a selected lineitem with copies marked received.

Revision history for this message
Leslie St. John (lstjohn-deactivatedaccount) wrote :

I have run into the error Event: 10102:ACQ_NOT_CANCELABLE -> The object is not in a cancelable state.
lineitem 1083. The purchase order is a single line item with 2 copies ordered, the state is on-order. EDI messages have been received and processed. No items have been received, no invoice is created. 2 line items are related to the same bib - the other line item is in a state of order-ready.

We are on version 2.5.1

Revision history for this message
Leslie St. John (lstjohn-deactivatedaccount) wrote :

On a PO with 2 line items, one cancels one gets the error message that it is not in a cancellable state. Click on the copies link for the item with the error and the copy shows cancelled. However, this status does not display on the PO and the PO cannot be cancelled.

Revision history for this message
Tiffany Little (tslittle) wrote :

Has anyone seen this recently? I have not, but I also haven't cancelled anything recently. I have run into it before, though, and trying to test for it is frustrating because for me it's never consistent when the error would happen.

tags: added: acq-lineitem acq-po
Revision history for this message
Tiffany Little (tslittle) wrote :

Marking Won't Fix based on discussion at the February AIG meeting.

Changed in evergreen:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.