Comment 0 for bug 1172373

Evergreen 2.3+

EDI Invoices from book vendors have a segment where we try to parse out a number that's supposed to point to the purchase order related to a PO. There are problems with this.

1) Invoices usually reference lineitems that came from many different POs, and there's only ever at most one PO # in this field in practice. (And I'm not addressing this problem for now, just noting it for the record).

2) Some vendors put alphanumeric strings in here instead of the PO id. And I mean values that aren't the PO's name field, either. In some cases, the string is just the vendor's name!

It's problem 2 I'm addressing for now. Since the existing code wants to match these numbers to a PO in the system, I'm still leaving that in place as long as the string given by the vendor is all digits. If the string is not all digits, then we just proceed without looking for a PO or setting any value in the purchase_order column of the acq.edi_message row we're creating.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/senator/acq-edi-po-field-unreliable