TitleLeaf doesn’t have functionality to generate and transmit EDI files. Publishers commonly use third-party solutions to do so. Per Bowker, such an EDI solution requires a Standard Address Number (SAN) when transmitting order data via any Book Industry Systems Advisory Committee EDI format.
To facilitate the correlation of TitleLeaf’s ONIX product metadata transmissions with third-party EDI order transmissions, TitleLeaf can store a publisher’s SAN identifier associated with their EDI solution:
If the EDI SAN is defined, TitleLeaf outputs it in the Header composite of ONIX 2 and ONIX 3 packages:
In this way, recipients of TitleLeaf’s ONIX files (eg, Follett) can link the product metadata contained therein to the EDI order data received separately.
Reference: