EDI Order message sent by ALEPH is lacking the NAD+BY segment
- Article Type: General
- Product: Aleph
- Product Version: 21, 22, 23
Description
The vendor reported that the EDI Order message sent by Aleph is lacking the NAD+BY segment identifying the sender of the message.
Even though ./xxx50/tab/tab35 includes a row with the relevant sublibrary and Vendor Code combination, the customer's EDI Code from column 3 is not included in the outgoing EDI message header.
Resolution
The Send List of Orders to a Vendor service (acq-14) was run with 'All' checked for Sublibrary in the submission form, which means that the NAD+BY segment to not be included, as it is for all sublibraries and not a specific sublibrary with a name and address.
Specify the individual sublibrary, as defined in tab35, when running acq-14. This will cause the <sub-library-edi-code> section to appear in the XML, which then generates the NAD+BY section in the outgoing EDI Order message.
Additional Information
Alternatively, adding a line to tab35 with the ADM library code (xxx50) in column 1 will allow the running of Send List of Orders to a Vendor (acq-14) with 'All' checked. However, this mode of operation requires that all sublibraries in the ADM share the same Customer EDI Code.
Category: Acquisitions
Subject: EDI
- Article last edited: 11/20/2013