|
|
Cooperative Extension Service |
 |
|
|
|
|
Agricultural
Experiment Station |
|
|
|
|
|
U of A Board Policies
Dale Bumpers College
|
Information Technology
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 1. | Outstanding action items from last meeting. | |
|
ACTION ITEM – Steve will investigate the options of 1) adding a
disapprove column to the time sheet approval form or 2) adding
information on the approval form to point managers to the other time
sheet form when disapprovals are required. He will report back to the
group at a future Banner meeting for discussion and decision. Done. ACTION ITEM: Linda will verify exactly what appears in her finance approval queue when she approves in Self Service and report back to the committee if the form is displaying items for which she in not the next approver. Done; the queue is functioning properly. ACTION ITEM: Steve and Bruce will work with Angela, Diane and Kyleen to help troubleshoot their problems performing a screen print while in Banner. Steve has applied the patch that corrected the problem. Users can now update to the latest version of Java. |
||
| 2. | Audit | |
| Mark Barnhard set up Kristy Waters of the UA Systems Office with a VPN so that they could begin a long term monitoring of our Banner tables. UALR is also being monitored in this manner. Bruce was very helpful in getting Kristy’s connection working. | ||
| 3. | Projects | |
| a) | Disaster Recovery – The standby database is live. Steve recently discovered that there was a problem with the logs being updated on the standby database. This has been corrected. The secondary server still needs to be configured and shipped to UAFS; this has been delayed as we coordinate with UAFS on when they intend to upgrade to Oracle 10g. We will need to also perform the upgrade before we configure the server for shipping. | |
| b) | P-Card Invoice Import – The process is working well. Currently, a maximum of 10 entries are required each month. The committee agreed that the project can be considered successfully completed. Unless the number of transactions grows, no work will be done to further automate it. | |
| c) | Accounts Receivable – A Form Fusion invoice will need to be created. A/R will contract with eVisions to create the form. | |
| d) | Argos – Mark has begun working with Argos to create a purchase orders by buyer report. The plan is to move all of purchasing’s static Access reports to Argos so that they may begin to become comfortable with the software and identify ad hoc reporting needs. | |
| e) | Fixed Assets – The trigger that would prevent value-based accounting for fixed assets (will pop up error if the dollar value of $1 is entered for a fixed asset account type) will not work for this purpose. This change will require a coding change to two forms, which will then have to be updated with each new release of Banner. The committee decided to table this request. The incidence of the problem occurring is infrequent and Steve has a process to correct it when it occurs. The amount of labor involved in correcting it is far less than what would be required if the two forms were modified. | |
| f) |
Bank Reconciliation Automation – The committee decided to remove this item from the project list. The bank reconciliation process is working well and reconciliations are up to date. This was not the case when the project was first proposed. |
|
| 4. | Banner updates/patches installation process. Who is responsible for identifying them? Who approves them? | |
Patches are discovered in the following manners:
The patch is tested in PREP or other test instance of Banner. Once the results are satisfactory, the patch is applied to ACES. The unit director is kept informed of the process via copies of the e-mail traffic between IT and FS/HR, and scheduling of the patch installation is coordinated between the two departments involved. During discussion, it was determined that the Banner Application Review Form should be completed, if a patch will alter any financial data when applied. |
||
| 5. | Other Business | |
|
Steve asked for more information so that he can complete the NSF
disapproval notice email project that was started before Kyleen left.
Sheryl was able to provide some of the information to help Steve
identify when a disapproval is due to NSF and who the ‘sender’ of the
e-mail should be. The e-mail should go to both the financial manager and
the requestor. Linda reported that Intellicheck is being upgraded. She will review the notes concerning the upgrade and forward the e-mails she received from eVisions to Steve. |
||
|
© 2006 |
|
|
University of Arkansas • Division of Agriculture |
Mission
•
Disclaimer
•
EEO
•
|
