If you correctly set up your vendor records and vendor contracts/accounts, Horizon can more easily match vendors with electronic orders, responses, and invoices. Horizon uses the EDI Article Number (EAN) or Standard Address Number (SAN) as the unique identifier to match electronic orders and uploaded EDIFACT invoices or order responses with the vendors from which they came. Horizon can also use the customer number/account number to identify vendors.
EDIFACT and BISAC orders also use the EAN and SAN as a unique number to identify the parties involved in a transaction. EDIFACT orders use the EDI Article Number (EAN) or the Standard Address Number (SAN). BISAC orders use only the SAN. You should assign one or both of these numbers to each of the vendors you will send electronic orders to. Before you create EDIFACT or BISAC orders, make sure you have entered these numbers for your vendors, as necessary.
For your vendor records and vendor contracts/accounts that you use for electronic orders, responses, and invoices, each vendor record must have a unique EAN or SAN. Horizon uses the EAN or SAN as the unique identifier to match uploaded EDIFACT invoices or order responses with the vendors from which they came.
The setup that is the simplest for your library and for Horizon to use is to have one vendor record on Horizon per vendor; each vendor record has its own unique EAN or SAN.
However, your library is more likely to have one of these setup situations:
• | You have several vendor records for the same vendor, but for different locations of the same vendor. |
• | You have several vendor records for the same vendor and the same location, but for different customer/account numbers with the vendor. |
If you have one of the more complex setup situations, you must use one of these setup solutions:
If you have this setup situation |
Use this setup solution |
If your uses one vendor record for each different location for the same vendor |
Enter the unique EAN or SAN for that vendor location on its vendor record. You cannot have the same EAN or SAN as the main vendor location or the same EAN or SAN as the vendor location from which you receive your items on all vendor records. Each vendor record must have a unique EAN or SAN. |
If your library uses one vendor record for the same vendor and the same location, but for different customer/account numbers (in other words, you have the same EAN or SAN number for each vendor record) |
Use the customer/account numbers to make the vendor records unique. This means that you need a unique customer/account number set up on the vendor contracts/accounts between vendor records. Since Horizon needs a unique identifier to match uploaded EDIFACT invoices or order responses with the vendors from which they came, you must use the customer/account numbers to make the vendor records unique. You do this in the vendor contract/account on each vendor record. When you set up the vendor contract/account, you must be sure that the customer/account numbers are set up correctly. This means that you must be sure that a customer/account number is not on another vendor record with the same EAN or SAN. However, you can have the same customer/account number on different vendor contracts/accounts on the same vendor record |
As you make sure your vendor records are set up correctly, you can also set up vendor enhanced services. This lets you send item information (collection, item type, and location) to the vendor in an EDIFACT electronic order. The vendor then adds the information to the MARC bib records they send to you (usually in the 949 tag or other tag your library uses for holdings information). When you receive and import the MARC bib records, Horizon creates item records with the appropriate information from the MARC bib records. Horizon also replaces any temporary item records with the new item records.
If you want to create or edit a vendor contract/account, see Vendor Contracts/Accounts.
This section explains these topics:
• | Entering the EAN or SAN for a Vendor |
• | Using Vendor Enhanced Services |
© 1998-2017 Sirsi Corporation