Monday, April 20, 2009

Aleph2Banner: The Problem

The Aleph2 Banner project is an attempt to automatically export book vendor payment information from Aleph into our Banner financial systems. Our current process has library staff enter this data into Aleph, then pass paperwork to the library business office where it is re-entered into Banner and then, entered one final time into an Access Database for reporting purposes. The work performed by our business person on these tasks is said to average about 20 hours per week. If we could automate this task, we stand to make a huge impact on our workload.

With some direction from FCLA, we've found a report (ACQ-16) that we believe can take the place of our Access database report but it will requrie Acquisitions and Serials to complete the budget information in Aleph. Up until now, they have not entered assigned budgets which meant that the report shows a negative balanace after the first payment.

Other issues include the use of library specific codes for the vendors that do not match Finance's vendor codes and the fact that purchases made with our PCard are automatically entered into Banner so they will have to be bypassed somehow in the export or import process.

The projet team includes Serials, Acquisitions and Systems with support from ITS, Fianance and FCLA. Our goal is to implement this new process for the start of the new fiscal year, July 1 2009. Over the next few weeks we hope to make subtantial progress which I will document here.

No comments: