1 / 37

Our Need

Exlibris : Developers Meet Developers Feb. 1-2, 2010 Voyager To NUFinancials ( peoplesoft ) System ( for Invoice Payment ) Michael North Northwestern University m-north@northwestern.edu. Our Need. University financial system implemented a new Peoplesoft Financial System.

Télécharger la présentation

Our Need

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.


Presentation Transcript

  1. Exlibris: Developers Meet DevelopersFeb. 1-2, 2010Voyager To NUFinancials(peoplesoft) System(for Invoice Payment)Michael NorthNorthwestern Universitym-north@northwestern.edu

  2. 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.

  3. 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_nbrin 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 Checking File Locking RunDate Tracking Log File log the xml sent to Peoplesoft server

  4. Peoplesoft Vendor Code and Remit SeqAddress Link PS Vendor Code Remit Seq Address

  5. Peoplesoft Chart String Link

  6. 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

  7. Testing Plan

  8. Voyager Interface Process Overview

  9. Process Overview

  10. Perl Programs Size

  11. Voyager to Peoplesoft Mapping

  12. Voyager to Peoplesoft Mapping (continued)

  13. Voyager Interface "TESTING"

  14. Additional Perl Modules (other than those which come with Voyager install) 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 responsemessage Response objects are returned by the request() method of the LWP::UserAgent: Installed second Perl install to minimize impact of Voyager upgrades.

  15. Component Parts of Voyager Interface Voycafe.pl (can run as prod, test, or using a list of invoice ID's) Café.pm VoyDatabase.pm Voucher.pm VoucherLline.pm DistribLine.pm Send.pm Report.pm timefile.conf(stores lastrundate and nextrundate) Log<date>.txt Lockfile.lock

  16. System Analysis Flow Chart

  17. Peoplesoft Error Reports

  18. Invoice Info

  19. Payment Info

  20. Log File – first part Test Run – we normally have 300+ invoices with fewer errors

  21. Log File – middle part

  22. Log File – end part

  23. Email Notification

  24. Email Notification - continued

  25. Invoice Reconciliation(used for troubleshooting "feeds")

  26. Thank you !

More Related