General Information
What is an interface?
An interface is an electronic connection between two
computer systems that replaces the need for paper documents.
Your department may have many interfaces. The information
contained in these pages applies only to data interfaced
directly or indirectly to CUFS, the University financial
system. If you are uploading financial documents (IV's, IX's,
PO's, PV's, etc), then you're interfacing with CUFS. (Some
organizations, such as financial aid, pass their documents to
a second system, such as STARS, before the documents finally
end up in CUFS.)
What is the CUFS Interface Automation methodology?
A comprehensive methodology was developed to aid the
process of developing and implementing a new interface. The
methodology starts with a request packet and ends with an
implementation checklist, defining exactly who is responsible
for each step of the process.
While the methodology won't guarantee a surprise free
interface implementation, it will highlight commonly
overlooked areas and reduce the chance of unanticipated
problems slowing down the project at a critical time. For
this reason, it's imperative that the methodology be reviewed
early in the interface development process, preferably during
requirements definition.
Who should I call to discuss a new interface?
Call Financial Systems Support at (612) 624-1617, and ask
to speak with someone about an interface to the financial
system.
Why are there so many procedures surrounding interfaced
transactions?
Automated transactions, once properly controlled, have the
least risk to the organization. However, automated
transactions, not properly controlled, have the greatest risk
to the organization.
A paper document that has been improperly coded will post
incorrectly to one account. Most interfaced documents have
codes that are automatically assigned; if the coding is
incorrect, all transactions will be posted incorrectly.
Additionally, interfaced transactions are often "out
of sight, out of mind." Monitoring procedures must be
established to ensure transmission and data errors will be
caught and corrected.
Finally, interfaced transactions follow a different
security path than on-line transactions under the assumption
of a more controlled, predictable process. Therefore,
measures must be taken to verify and maintain that
environment.
What do I have to do about Year 2000 changes?
You are responsible for your own system changes. The
actual file that is sent to CUFS should remain in the same
format as is currently required.
If you have concerns about your Year 2000 readiness, please call for assistance at (612) 624-1617. (You'd be a little late at this point in the game.)
Return to CUFS Interfaces
|
Return to: Controller's Office : U of M Home
