EDI Invoice Loader

Tags: intermediate , edi , ftp , loader
Last Updated: Oct 30, 2009 00:48

Author: Christine Moulen
Additional author(s):

Institution:
Massachusetts Institute of Technology
Year: 2008

License: MIT License
Short description: Use, modification and distribution of the code are permitted provided the copyright notice, list of conditions and disclaimer appear in all related material.
Link to terms: Detailed license terms

*Skill required for using this code:*intermediate

Description
State
Screen captures
Author(s) homepage
Download
Working example
Using the following Ex Libris API
Changes

Version 1.0
Version 1.1

Release notes
Output
Dependencies
Installation instructions
TO DO list
Known issues
Comments

Description

The serials EDI invoice loader retrieves EDI files from the specified vendor, and loads it into Aleph using p_edi_09 and p_edi_10 services.
Logs are emailed to specified Acquisitions and Systems staff.
The loader is available from the Acquisitions client Services menu, as MIT Custom -> Serial EDI Invoice Load (custom-01).
This is used for our serial EDI invoicing, but would probably be applicable to many monographs vendors as well.

Most recently used with Aleph version 18. Changes will be coming to implement new batch features with version 19.
May work with earlier Aleph versions. Earlier versions of these scripts have been used with Aleph 16 and 14.2.

State

Stable

Screen captures

Author(s) homepage

http://libraries.mit.edu

Download

Individual files:

All in one:

edi.tar

Working example

Using the following Ex Libris API

p_edi_09

p_edi_10

Custom service capabilities

Changes

Version 1.0

Aug. 29, 2008. Initial posting to EL Commons. Scripts have previously been shared with other customers.

Version 1.1

Sept. 3, 2008. Minor correction to Perl scripts. After adding in license text, #!/usr/bin/perl declaration still needed to be the first line of the file.

Release notes

EL Commons 1.0

For those who have seen previous versions, this download uses a single processing script, and not one for each vendor. FTP details for the vendor are no longer hard-coded into the script, but are queried from the vendor's EDI address in the Aleph database.

Output

invoice_load_vendor-code_timestamp

Log information, including parameters, any errors, and the EDI log number. This file can be found in the ADM library's $data_print directory, and as part of the standard output from the Aleph service in $alephe_scratch.

email

An email indicating that an EDI download was done is sent to specified Acquisitions and Systems staff.

Dependencies

DBI.pm

ENV.pm

Installation instructions

These scripts assume the following placement of the files. If you put them elsewhere, you may need to edit some pathnames within the scripts.

/export/home/barton/mit_opts.csh
/export/home/barton/mit_env.csh
/export/home/barton/<version>/edi.get-edi
/export/home/barton/<version>/bin/get_vendor_edi.pl
/export/home/barton/<version>/bin/last_edi_log.pl
$aleph_proc/p_custom_01
$alephe_root/pc_b_eng/p-custom-01.xml
$alephe_root/pc_b_eng/menu-acq.xml

$alephe_root/pc_b_eng/p-custom-01.html

The script is normally run as a service, but here is the syntax should it need to run at the command line.

./get-edi -v 18 -- vendor-code filename
OR
$aleph_proc/p_custom_01 MIT50,vendor-code,filename

TO DO list

Upgrades coming soon for Aleph 19.

Known issues

Comments