OLIB acquisitions can be used for the automatic emailing of orders using the EDI protocol. Once enabled, the workflow is slightly different from other orders that go from Pre-Order to Outstanding: with EDI they progress from Pre-Order to Authorised. The background process then moves the status on to Outstanding once the order is sent. The following lists the configuration necessary, however Technical assistance may be required from OCLC Support to ensure correct set up.
From OLIB 9 Service Pack 8 OLIB calls a PL/SQL package for the EDI processing. This replaces the EDI Driver server process, that used to be enabled in System Admin> Server Process Config.
EDI is enabled on a supplier-by-supplier basis. Enter the following settings in the supplier record to enable EDI transmission:
Note: EDI Email Address is no longer used for this data. Once OLIB 9 Service Pack 8 is installed, check that the email address is correctly set in Email Address for Orders.
If you have multiple locations, you can enter different party ID codes for each Location for the same Supplier. This allows the same supplier to be aware that the orders are from different Locations and should be delivered to those Locations. If the User who is placing the order has a location specific party ID code then that is used when placing the order; if they do not then the above default EDI Party ID Code is used.
If in future you need to remove a location's party ID code, tick the box of the Location and Party ID code displayed, and from Actions select Delete location-specific setting.
Set the ARTEmail Prefix if required for British Library ordering:
When this is not set, OLIB sends ‘XXXXX’ as the Sender ID in the Header-UNB-Sender ID field.
This address information is connected to the logged in User who is to place the orders. An Address Type of O must be associated with that User's Location, or with that User's own User record. If the address of Type O exists in the User's own User record, this takes precedence over the one in the Location record; if the O type address does NOT exist in the User's record, the one in the User's Location record will be used instead.
The Edifact standard, around which OLIB’s EDI facility has been modelled, stipulates that ISO currency codes should be used when specifying the currency in an EDI message. In OLIB, the currency record’s Key ID is included as the currency code in an EDI message. You should therefore ensure that the default currency for an EDI supplier in OLIB is one of the currencies which has an ISO currency code in the Key ID field, e.g. Pound Sterling, Key ID GBP.
If you do not set a default currency for your suppliers, the currency will have to be set when entering the order. Again, you should ensure that you use a currency with an ISO code in the Key ID field.
Once enabled, the operation of EDI orders is almost identical to non-EDI orders. You can also re-transmit the order if it fails on the first attempt.