Glossary Of Terms

A

Application: A complete, self-contained program that performs a specific function for the user.

B

Budget Check: The process of ensuring that a pending expenditure is covered by budgeted funds

Business Process Redesign: (BPR) Changing the business processes to be more efficient and/or to adapt to the requirements of a new software.

C

Chart of Accounts: The foundation of the PeopleSoft accounting system providing unique identification and a common language for identifying finance transactions.

Configuration: Set-up of the PeopleSoft system, including selecting options and entering set-up data. (This is different from customization that means changes are made to the PeopleSoft application.)

Conversion: The process of loading data from the existing system to the new system. The conversion process involves identifying the data that must be brought to the new system, mapping the data to PeopleSoft fields, translating old codes into PeopleSoft codes and loading the clean and compatible data into PeopleSoft.

Crosswalk: The translation of a legacy value to a PeopleSoft value.

D

Dialog Box: A box that appears on screen that asks the user for input, or relays information to the user.

Drill Down: To move from the general to the specific. By “drilling down” you can examine the data underlying any summarized form of information in your PeopleSoft system.

M

Modules: Groupings of software programs that collectively support a specific business function.

Milestone: A milestone refers to the point at which you reach a significant point in the PS project activities.

U

User Productivity Kit (UPK): The User Productivity Kit (UPK) is a multifaceted authoring platform that allows the University to develop highly-effective task specific training products for functional and end users. Training guides, job aids and business process guides can be developed using this training tool.

V

Vanilla: Term that describes the base or standard software package that PeopleSoft delivers “out of the box”. Modifications and customizations can be made to the vanilla package to meet unique processing requirements of the organization. Modifications and customizations require a high level of on-going maintenance and should be kept to a minimum.