ACQ: ASN issues with multi-branch systems

[Samantha O'Connor]

Evergreen 3.11.1

When Baker & Taylor sends a DESADV message via EDI to create a container barcode for ASN, the message is structured to create a separate EDI segment for each billing account. In a multi-branch system, this results in multiple segments with the same container code (see parsed EDI message below). Evergreen only creates a scannable container code for the first code in the message. When the library scans the barcode, only the line items attached to the first instance of the container code appear as receivable.

GIN+BJ+00016921005023327009 ---> This is the container code
LIN+00001+[phone]:EN ---> This is the ISBN for the line item
QTY+12:1
RFF+ON:211489 ---> This is the PO

GIN+BJ+00016921005023327009 ---> The container code repeats
LIN+00001+[phone]:EN ---> The following line items will not scan as receivable
QTY+12:1
RFF+ON:211901 ---> This is a different PO
LIN+00002+[phone]:EN
QTY+12:1
RFF+ON:211901
LIN+00003+[phone]:EN
QTY+12:1
RFF+ON:211901
LIN+00004+[phone]:EN --->e.g. this line item was ordered twice with two different funds.
QTY+12:1
RFF+ON:211901

GIN+BJ+00016921005023327009 ---> The container code repeats
LIN+00001+[phone]:EN ---> The following line items will not scan as receivable
QTY+12:1
RFF+ON:211901 ---> Same PO but line items are billed to a different fund
LIN+00002+[phone]:EN ---> The second copy on a fund owned by a different
                                   branch appears in a different segment
QTY+12:1
RFF+ON:211901

GIN+BJ+00016921005023327009 ---> The container code repeats
LIN+00001+[phone]:EN ---> This line item will not scan as receivable
QTY+12:1
QTY+12:1
RFF+ON:211901 ---> Same PO but line items are billed to a different fund

If I compare this message with a DESADV message for a container made up of all materials purchased from funds owned by the same branch, there is a single container code followed by all the line items. When this code is scanned, all items show as receivable.

The potential bug appears to be in the way that Evergreen creates the container codes to be scanned. Only the first code and related line items scan. A similar issue occurred when a DESADV message contained multiple container codes. Only the first code was scannable.