Pro-Card Feed

Pro-Card Feed

PURPOSE:

These steps will access and process the latest Pro-Card data into the Banner Finance System.

SCRIPT NAMES AND LOCATIONS:

On BSCBANNER, within /u05/sct/banprod/links:

fprocard.shl – the user (Purchasing) will run FPROCARD from Job Submission (GJAPCTL) to process the file.

On BSCBANNER, within /u05/sct/banprod/scripts:

pcfeed.ctl – this loads the actual flat file into a temp table for processing.

procard.sql – this loads the data from the temp table into the GURFEED table.

pcfeed_cleanup.sql – this empties the temp table and sends a report on the number of records processed to the user.

FREQUENCY AND TIMING:

Run controlled by user and is done on request although usually by the 15th of every month.

PREREQUISITES/DEPENDENCIES:

User must log into and follow instructions for downloading and unzipping file into proper directory (\\Boyden_pdc\purchsng\procard).

OTHER RESOURCES:

Process utilizes the following tables:

fimsmgr.pc_feed_initial – temporary holding table for raw transaction data.

general.gurfeed – feed table that gets loaded.

Process utilizes the following functions:

fimsmgr.f_cvt_curcval – the crosswalk function.

fimsmgr.f_get_feed_seqn – function to get next document number.

PROCESS DESCRIPTION:

The user will begin the process by running FPROCARD from Job Submission (GJAPCTL). The process will ftp a file that the user has downloaded onto the Unix server into /u05/sct/dataload/finance/procard.dat (with previous files getting backed up). Then, it will load the flat file into the pc_feed_initial table using SQL loader. Next, it runs the procard.sql to load the GURFEED table with the records. The process will check the object code to see if the first character is 7 and if it is will use the old FRS account and the crosswalk function to get the new Banner account, otherwise, it will just use the expense account given along with the old account as the index. After that records are written to the GURFEED table with the absolute value of the amount and a corresponding ‘D’ebit (for positive numbers) or ‘C’redit (for negative numbers), the process will create a “control”/header record with the total (absolute value) amounts of all the records read in. A report will be created for control purposes and emailed to the user and Asst. Controller with the actual number of records and total amount paid.

Once the user receives the email, they should then verify the numbers and FURFEED will be run overnight.

POSSIBLE PROBLEMS:

There is a possibility that the input file is incorrect due to missing accounts. The Asst. Controller will identify the problem accounts and make the proper corrections either in FGAJVCD or by deleting the feed and running the process again.