<mods:mods version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><mods:titleInfo><mods:title>EDI invoicing for monographs, in spite of ALEPH's limitations</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Christine</mods:namePart><mods:namePart type="family">Moulen</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:name type="personal"><mods:namePart type="given">Jason</mods:namePart><mods:namePart type="family">Fleming</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Christine Moulen, (Massachusetts Institute of Technology) and Jonathan Rothman, (University of Michigan); Jason Fleming (University of Florida), Moderator.&#13;
&#13;
Loading monographic invoices through EDI isn't practical unless the orders originated in ALEPH. P_file_96 doesn't create invoices, but there's invoice data in many vendor records. One answer: build and load "pseudo-EDI" invoices from the vendor data. Applications for both approval plans and firm orders will be discussed.</mods:abstract><mods:classification authority="lcc">Aleph</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2006-06-05</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>