• Article Type: General
• Product: Voyager
• Product Version: 8.1.2

Description:
Bug Report Form for Issue 16384-16097

Module(s): Acquisitions
Server platform(s) affected: Solaris/all
PC OS (if applicable): n/a
Browser & version (if applicable): n/a
Release(s): reported in 7.1; replicated in 8.0

Expected results: Any EAN in the bib record should be included in the message created when sending the PO via EDI.

Actual results: Whether the EAN is in the 020 or the 024, if it is prefaced by anything other than 978 or 979, the EAN will not be in the EDI message.

Workflow implications: Some vendors will not be able to process the EDI messages.

Replication steps:
Create a bib record that has an 020 $a or 024 $a that begins with anything other than 978 or 979 (5060126870838, for example).
Create a PO and add a line item that links to this bib.
Go to File>Send via EDI.
Go to EDI>Outgoing and search for messages created today.
In the Message Number field, click in the far right corner – you’ll get an ellipsis, and when clicked, this will allow you to view the EDI message for the PO you just created. Note the absence of a LIN segment with the EAN in it. If you edit the bib record such that the EAN now begins with a 978, add that line to a new PO and then send that PO via EDI and view it, you’ll see that the EAN is sent in an LIN segment.

Resolution:
Fixed in the Acquisitions client and server for 8.1.2.

• Article last edited: 3/18/2015