Acq: Do we need a feature to resend EDI purchase orders?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Hypothetical at this time, for Evergreen master.
I recently helped somebody who needed to resend a PO by EDI after changing some fields in the acq.provider row related to the PO. They knew to delete the the right row from acq.edi_message where message_type = 'ORDERS' and purchase_order = <PO ID>, but there are more steps if you want the message content to actually get regenerated.
Specifically, you want to regenerate certain Action/Trigger template output that is fed into the EDI translator before new rows in acq.edi_message get created. Like this:
SELECT atev.id FROM action_
Then you'd follow that with :
UPDATE action_
And finally with srfsh you'd need to issue this method call:
request open-ils.trigger open-ils.
Presumably, the user who was doing this had had some communication with the vendor so that they expected the resend, or at least the user had some other way of knowing that there should be no trouble from sending the same order twice (slightly adjusted the second time, of course).
** The point **
Is this a common situation for sites out there getting into serious EDI use with Evergreen, and should there be a way to handle this in the interface?
Changed in evergreen: | |
status: | New → Triaged |
tags: |
added: acq-edi removed: edi |
Yes, I believe there should be a way to resend a PO within the interface. We have had instances were a PO fails to be received by the vendor. This can be due to an issue on the vendor's side, a connectivity issue, etc. Being able to resend a PO would definitely be cleaner and more efficient than recreating the PO and sending it again. Testing is another instance where resending a PO would be highly desirable. I have had a number libraries ask if it was possible to resend a PO.