280 likes | 380 Views
Making the FUPLOAD Process Work. Darrell MARTIN Tuesday October 28, 2003 Morning Session 1. Introduction. Review of the 5.4 Enhancement Discuss why the Wilkes Uni changes Show how to set up and use this new functionality Thanks to Gary Houck, SCT. Topics of Discussion.
E N D
Making the FUPLOAD Process Work Darrell MARTIN Tuesday October 28, 2003 Morning Session 1 WFUPLOAD
Introduction • Review of the 5.4 Enhancement • Discuss why the Wilkes Uni changes • Show how to set up and use this new functionality • Thanks to Gary Houck, SCT WFUPLOAD
Topics of Discussion • History and Overview • Set Up • Processing WFUPLOAD
History • Developed in conjunction with the University of Illinois • Referred to in release guide as ‘Internal Vendor Order Processing’ • Enhanced by Wilkes University to be more generally usable for any Journal data WFUPLOAD
Wilkes’ Changes • Minor Record Layout adjustment • Excel CSV input file format to WFUPLOAD • Five additional fields were added to allow for Budget Journals, Accrual Period processing and NSF checking WFUPLOAD
Overview • Create Excel data file and save in CSV • Optional unique document numbering • Optional Text record/s • FTP file to Banner accessible directory • Run WFUPLOAD to load GURFEED WFUPLOAD
Set Up WFUPLOAD
Set Up WFUPLOAD
Set Up WFUPLOAD
Processing • Create a comma separated formatted file of data – Needs: • Header record • Detail record • Summary record • Text records – Optional • Save formatted file in pre-defined directory as a .csv file WFUPLOAD
Spreadsheet Requirements • Can use only the following items • COA, Index, FOAPAL • Doc Reference number • Encumbrance Num, item, sequence, action • Encumbrance type must be “L” • Any rule class • Transaction description – 35 spaces • Document Code is optional WFUPLOAD
Spreadsheet Requirements • Must be in format specified in my Guide Notes (slightly altered to release notes) • Save as a .CSV file • Do NOT have row or column headings in CSV file or any blank rows (only shown in sample file as a guide) • May reference a General Encumbrance for liquidation WFUPLOAD
Processing WFUPLOAD
Processing WFUPLOAD
Processing WFUPLOAD
Processing WFUPLOAD
Processing WFUPLOAD
Processing WFUPLOAD
Processing (cont.) • Run FTP, or some other local process • to copy the saved CSV Excel file from the submitter’s PC to the Banner jobsub directory. WFUPLOAD
Processing (cont.) • Run WFUPLOAD – Finance Upload to GURFEED • Process - PARMS: • System ID – Req. • Location – Req. (Directory/Path) • File Name – Req. • Run Mode – Audit/Update WFUPLOAD
Processing (cont.) WFUPLOAD
Processing (cont.) • WFUPLOAD will: • Assign doc num from FOMFSEQ if not in file • Check for duplicate Doc numbers • Check for Gen Encumb. Document • Check for valid FOAPAL, Rule Class, • Rename file if it is properly processed • Populate GURFEED and GURTEXT WFUPLOAD
Processing (cont.) WFUPLOAD
Processing (cont.) WFUPLOAD
Processing (cont.) • Proceed as usual: • FURFEED • FGRTRNI • FGRTRNR • Fix errors on FGAJVCD or FGAJVCQ • Note: if JV option is checked for FA auto update GURFEED entries to a FA Expense will update Fixed Assets (same as a JV) WFUPLOAD
Summary • General Spreadsheet load to GURFEED • Use Excel CSV format • Save/FTP file to directory for WFUPLOAD • GURFEED now has header text capability for any internal interface • GURFEED reporting and deleting capabilities WFUPLOAD
Questions and Answers • Any Questions? WFUPLOAD
Thank You! Darrell Martin Finance Systems Analyst dmartin@wilkes.edu If you want the source code and instructions, please hand me your business card / email address WFUPLOAD