I entered an Enhancement Request for this and I would really appreciate it if anyone is also experiencing this issue and could go endorse my request. Its ER #89976.
I originally opened this as a help desk ticket but they tell me the system is working as designed, however here is my problem. Its been a BIG problem the whole time we've had Infor and has lead to numerous duplicate orders and considerable extra expense to our organization.
The problem is, if a buyer creates a PO and does the initial issue, then they have to make a change and re-issue to the vendor the PO then sits with the REISSUE method on the PO. That's all fine until the buyer has to make another change that doesn't need transmitted (ie: adjust pricing to clear an invoice, change it from Special to Service, whatever internal change is needed). At this point, the Issue Method on the header still sits there with the REISSUE method (ie: EDI, FAX, EMAIL). It never changes to paper again after the second issue is made. So when the buyer enters the PO the third (or fourth, and so forth) time to make a change the PO will see it is Revised and the Issue Method sits there currently as whatever the Reissue Method is set to on the Vendor file. The system will retransmit the PO again and again if changes continue to be made by the buyer. The only way we know this happens is when the Vendor calls to say they got a dup, or our EDI carrier rejects the order. We have had PO's transmit 6 times causing duplicate orders and duplicate invoicing with no knowledge of the duplication on our side.
Currently we tell our buyers to remember to change the issue method back to Paper if they have had to reissue the PO to the vendor for any reason. Unfortunately, that rarely happens. I would like to see the system modified to automatically change the issue method to Paper immediately after transmission to prevent problems like this.
Please endorse my request if you agree or have experienced similar issues by clicking the link below. Thank you
Enhancement Request # 89976
