Acq Wishlist: Ability to Update the Provider on a PO in the Staff Client

[Jennifer Pringle]

Evergreen 2.10

Every now and then staff accidentally select the wrong provider when creating their purchase order. Currently staff have to abandon the purchase order and start a new one (which can be a pain depending how much work they've done before noticing) or have a tech update the provider in the database.

Ideally we'd like staff to have the ability to edit the provider on a pending purchase order. (If an order gets activated and sent to the wrong provider staff should have to cancel that order and start again.) An Edit button beside the provider name on the PO could allow staff to chose a new provider.

[Jennifer Pringle (jpringle-u)]

Confirming this is still an issue in 3.8.

[Sarah Childs (sarahc)]

Very much would like to be able to edit providers on a P.O.

And I would add the caveat that if EDI is not involved this would be useful even with Activated POs.

I ran into a case to today where we had a PO created for one provider instead of another. Since we use EDI with neither, we didn't notice until we had received most of the order. I don't really have the option to cancel the order and start again, since the order was submitted with this PO number.

[Ruth Frasur Davis (redavis)]

This is something that we might investigate rolling into Sprint C of the Angular Acquisitions project sponsored by ECDI. Watching this space.

[Tiffany Little (tslittle)]

We discussed this at the AIG meeting at the conference this morning.

The general consensus is that we see no issue with changing the provider on a pending purchase order. For activated purchase orders, you should only be able to change the provider if: (1) the old provider does not use EDI and (2) the new provider does not use EDI.

Ruth also had the good thought that if you are changing the provider on an activated order, it should probably change the provider on any associated invoices.

[Jennifer Pringle (jpringle-u)]

+1 to the consensus from the AIG meeting

[Jennifer Pringle (jpringle-u)]

Just noting that this is still an issue in 3.11 and still a desired feature.