The Book X12 Orders (Bookorderx12) report creates EDI purchase order files to be sent to a vendor.
The SirsiDynix Symphony Workstation server needs to be running to schedule and run this report, or the report will fail. Do not halt the SirsiDynix Symphony Workstation server until the report displays on the finished list.
The Book X12 Orders report contains the following tabs.
| • | Basic Tab: Reports |
| • | Order Selection Tab |
| • | Output Options Tab |
| • | Print Order Tab |
| • | Style Sheet Tab |
| • | Vendor Selection Tab |
| • | Vendor Cycle Selection Tab |
EDI book purchase orders are created using the Book X12 Orders report. Book orders created for EDI are created to use a vendor or jobber that typically deals with monographic materials. The order must have either an ISBN or ISSN in the ISBN/ISSN field or a catalog number in the additional line information for each orderline to be selected by the EDI reports. When an ISBN is assigned for a title using the order map file in the 850: field of the REC_TRANS EDI Address entry (or bookorder.map if no file is specified), the standard title ID in the orderline is used to set the ISBN in the electronic order. If the ISBN/ISSN field in the orderline is empty, the ISBN is extracted from the bibliographic record, if possible. If no ISBN is present, then the catalog number must be specified for the line item under Additional Orderline Information (orderline extended information fields). After an order has been created in SirsiDynix Symphony, the Book X12 Orders report is used to create the purchase order files to be sent to the vendor.
When the Book X12 Orders report starts to run, the report validates the vendor EDI address fields. If no errors are found, the report log will contain the following messages.
The vendor EDI address will be checked for entries XFER_ADDR, XFER_USER, and XFER_PASS.
0 vendors had missing EDI address entries.
If any of the vendor addresses to be processed by the report is missing the EDI address entries that the report requires, messages similar to the following display in the report log. Supply the missing information, and run the report again.
The vendor EDI address will be checked for entries XFER_ADDR, XFER_USER, and XFER_PASS.
**vendor ID: MAIN|FCT missing required entry XFER_ADDR
**vendor ID: MAIN|FCT missing required entry XFER_USER
**vendor ID: MAIN|FCT missing required entry XFER_PASS
1 vendor record(s) considered.
1 vendors had missing EDI address entries.
The Book X12 Orders report is similar to other SirsiDynix Symphony purchase order reports, but instead of a printed purchase order, the report produces a file that is X12 compliant for use with EDI. The report creates an X12 transaction file in the SirsiDynix Symphony server’s outgoing EDI directory. The purchase order numbers are printed in the report output.
If you decide to select the Count as a Notice check box on the Output Options tab, the Date Mailed field in the order record is updated.
For an EDI purchase order to be successful, an order map file must be used. The report checks the vendor’s EDI address REC_TRANS entry for an order map file name in the 850: value. If no map file is specified, the bookorder.map file is used by default.
If the library’s name exceeds the maximum 35 character limit for library names in the EDI standard, the library name will automatically be truncated to 35 characters.
This report imposes a single record size limit of 5 MB per order. Orders that produce X12 output larger than 5MB will not be processed, but will be written to the error log. The following message will appear in the report log.
Mem Alloc failed!! Size of 5242880 exceeded!****ERROR reading input record
To reduce the risk of sending duplicate EDI purchase orders, the Date Mailed field on the Order Selection tab always defaults to NEVER, and the Count as a Notice Sent field on the Output Options tab is selected by default.
For information about creating vendor holding code tables for EDI output, see the Holding Code Table for EDI wizard topic.
Related topics