Our Need

37
Exlibris: Developers Meet Developers Feb. 1-2, 2010 Voyager To NUFinancials(peoplesoft) System (for Invoice Payment) Michael North Northwestern University [email protected]

description

Exlibris : Developers Meet Developers Feb. 1-2, 2010 Voyager To NUFinancials ( peoplesoft ) System ( for Invoice Payment ) Michael North Northwestern University [email protected]. Our Need. University financial system implemented a new Peoplesoft Financial System. - PowerPoint PPT Presentation

Transcript of Our Need

Page 1: Our Need

Exlibris: Developers Meet DevelopersFeb. 1-2, 2010

Voyager To NUFinancials(peoplesoft) System(for Invoice Payment)

Michael NorthNorthwestern University

[email protected]

Page 2: Our Need

Our Need

University financial system implemented a new Peoplesoft Financial System.

Need a method to transfer Voyager acquisition data (invoices) to this new system so Library does not have to "cut checks."

3 year project that finished last year.Programming Team: Steve DiDomenico (heavy

lifter) and Michael North.

Page 3: Our Need

Issues to Consider

Object Oriented Programming techniques Perl is not a OOP language but used OOP techniques - provides modularity !

Matching "payment" vendor address. (remit_sequence_nbr in line5 of payment address – matching Voyager payment address

to the address in Peoplesoft)

Accounting Chart String (peoplesoft). Stored in institution ID of FUND record.

Running Script Options Production (batch), test (no sending), Individual Invoice (or list of invoice numbers)

Allow for Memo Voucher – "do not send"Built-in Error CheckingFile LockingRunDate TrackingLog File log the xml sent to Peoplesoft server

Page 4: Our Need

Peoplesoft Vendor Code and Remit Seq Address Link

PS Vendor Code

Remit Seq Address

Page 5: Our Need

Peoplesoft Chart String Link

Page 6: Our Need

RunDate Tracking, File Locking, Log FileFiles other than Perl programs

• timefile.config - a configuration file containing the lastrundate and nextrundate, which determines if the script should run, and how far back it should query the database for invoices

• lockfile.lock - a lockfile which, when locked, prevents other instances of the script from running. The presence of the lockfile doesn't determine locking; the *locking* of the lockfile does.

• log.txt - a log of the script's activity

Page 7: Our Need

Testing Plan

Page 8: Our Need

Voyager Interface Process Overview

Page 9: Our Need
Page 10: Our Need

Process Overview

Page 11: Our Need
Page 12: Our Need
Page 13: Our Need
Page 14: Our Need

Perl Programs Size

Page 15: Our Need

Voyager to Peoplesoft Mapping

Page 16: Our Need

Voyager to Peoplesoft Mapping (continued)

Page 17: Our Need

Voyager Interface "TESTING"

Page 18: Our Need
Page 19: Our Need

Additional Perl Modules (other than those which come with Voyager install)

Installed second Perl install to minimize impact of Voyager upgrades.

Need to add the following Perl modules:XML::Writer - Perl extension for writing XML documents. XML::Writer is a helper module for Perl programs that write an XML document.

LWP::UserAgent - Web user agent class The LWP::UserAgent is a class implementing a web user agent. LWP::UserAgent objects can be used to dispatch web requests.

HTTP::Request - HTTP style request message HTTP::Request is a class encapsulating HTTP style requests, consisting of a request line, some headers, and a content body.

HTTP::Response - HTTP style response message Response objects are returned by the request() method of the LWP::UserAgent:

Page 20: Our Need

Component Parts of Voyager Interface

Voycafe.pl (can run as prod, test, or using a list of invoice ID's)

Café.pmVoyDatabase.pmVoucher.pmVoucherLline.pmDistribLine.pmSend.pmReport.pmtimefile.conf (stores lastrundate and nextrundate)

Log<date>.txtLockfile.lock

Page 21: Our Need

System Analysis Flow Chart

Page 22: Our Need
Page 23: Our Need
Page 24: Our Need
Page 25: Our Need
Page 26: Our Need
Page 27: Our Need

Peoplesoft Error Reports

Page 28: Our Need

Invoice Info

Page 29: Our Need

Payment Info

Page 30: Our Need

Log File – first part

Test Run – we normally have 300+ invoices with fewer errors

Page 31: Our Need

Log File – middle part

Page 32: Our Need

Log File – end part

Page 33: Our Need
Page 34: Our Need

Email Notification

Page 35: Our Need

Email Notification - continued

Page 36: Our Need

Invoice Reconciliation(used for troubleshooting "feeds")

Page 37: Our Need

Thank you !