Current PECOS Purchase Orders and Goods Receipts Process
An automatic AMOR process (owned by Lockhead Martin) extracts purchase orders, purchase order changes, goods receipts and goods returns from PECOS twice a day
The data is loaded to an AMOR server, where another automated process coverts the data to xml
An automated ABS CIBR process downloads the xml files from the AMOR server to the UoE Finance application server
The CIBR process then loads the data into the eFinancials CLINK tables
The CIBR process than loads the data directly into eFinancials by calling POPR47 and POPR59 routines
The CIBRr process emails FIS if there has been an issue with the process
A seperate interface send details of purchase order to Saffron for stock purposes
Current SciQuest Purchase Orders Process
SciQuest automatically put the purchase order data onto a UoE server (Fireworks) on a daily basis in xml format
An automatic UoE cron job then temporarily copies the files to a database server and removes them from the Fireworks server
The cron job then converts the files to the correct format and puts them into temporary loading tables
The cron job then puts the data into the eFinancials CLINK tables
The cron job then send emails to FIS to confirm whether process was successful or not
Staff in Finance then manually load the data into eFInancials or the PECOS cibr process picks them up by default when it runs automatically
Current PECOS Financial Codes & Users Process
An automatic ABS process extracts users & their authorised valid financial code combinations from eFinancials and transfers them to the AMOR server
An automatic UoE cron process transfers the data to PECOS
Current SciQuest Financial Codes & Users Process
An automatic UoE process extracts new & updated cost centres & job codes from eFinancials audit tables and creates xml files on the database server
The process then copies the files to the Finance Application server
An automatic UoE process reformats the data & transfers the files to SciQuest
Users are manually created in SciQuest
Issues with the current processes
Purchase orders from SciQuest are sometimes rejected by eFinancials as invalid or unpostable as SciQuest only holds the individually valid elements not the valid combinations
Users have to be manually set-up in SciQuest which can result in delays and/or data errors
Users have to enter goods receipt details onto both SciQuest (for stock purposes) & eFinancials (for invoicing purposes)
Current Process Maps
Current Purchase Order Interface Process
Current Financial Codes and Users Interface Process
