Glossary
-Jump to acronyms and abbreviations-
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z
| ABAP | Advanced Business Application Programming: the programming language of SAP's ERP software. |
| ABAP Query | A native SAP reporting tool. |
| Ad Astra | The company from whom Purdue purchased its event-management and room-scheduling software, Astra Schedule. |
| Adobe Connect | Previously known as Macromedia Breeze. |
| application developer | A member of a IT/Enterprise Application or local application-development team that provides second- and third-level resolution with system application incidents, problems and change requests. |
| Ariba | Purdue's legacy Web-based, electronic procurement system. It was replaced by SRM (Supplier Relationship Management), an SAP product. |
| as-is | Purdue business processes before switching to the SAP and Banner applications. |
| ASAP | Accelerated SAP: a methodology developed by SAP to speed up ERP-implementation projects and keep costs under control. |
| Ascential | A suite of tools used to convert data. |
| Astra Schedule | Event management and room scheduling software that replaced Purdue's Room Scheduling and Event Management legacy system. |
| Banner | A package of software modules from SunGard Higher Education that comprise the bulk of OnePurdue's new student systems. |
| Basis | The underlying technology base that allows SAP's functional applications and modules to interoperate. |
| business application user | A OnePurdue user who is using an application system to support the needs of the business. For example: ordering supplies, entering budget information, running reports, entering payroll changes, entering grades, etc. |
| Biller Direct | SAP's e-commerce module. |
| Blackboard Vista | Formerly called WebCT Vista, this is an online course environment that allows instructors to deliver class material, communicate with students, and create learning activities. It is an integral part of OnePurdue training. More information about this tool is available on ITaP's Web site. |
| blueprint | Also known as a “business blueprint,” this document basically defines what OnePurdue will look like once fully implemented. |
| Blueprint Phase | Phase 2 in the ASAP implementation process. |
| bolt-on | A separate application that can be integrated with the SAP or Banner software. |
| Brio | A business intelligence reporting tool currently used at Purdue. |
| browser | An application program that searches the Internet, interprets language and presents a Web page. Popular browsers include Mozilla's Firefox, Apple's Safari, Microsoft's Internet Explorer. |
| Business Blueprint | Phase 2 of the ASAP process; during this period, the finance and HR teams identified Purdue's organizational structures, designed new business processes, installed the new financial and HR software, and received training in it. |
| Business Explorer | A native SAP reporting tool. |
| business intelligence | Business intelligence (BI) is a broad term for software reporting tools that use the same databases as the SAP applications to generate customizable reports for administrators and other decision makers at Purdue. Basically, an ERP gets data into the system, while BI gets it out. |
| business warehouse | SAP's term for what Purdue has referred to as a “data warehouse,” where University data will be stored. |
| BW developer | BW Developers are members from the IT/Business Warehouse team and can help the BW super user in publishing, developing or changing queries. They are responsible for developing InfoCubes for meeting future reporting needs, including authorization objects that are key to query definitions. |
| BW power user | A Business Warehouse power user can create queries in the production environment and save them in his or her “Favorites” folder. This user's access is usually restricted to one management or functional area. |
| BW super user | A Business Warehouse super user is responsible for publishing or broadcasting (i.e., share with other users) queries into production and has access to all the functional areas. |
| CAPP | Curriculum, Advising and Program Planning is a degree-auditing tool in Banner that replaced the legacy progress reports in SSINFO. CAPP helps students navigate through course requirements to help them plan their academic careers. |
| CARS | The legacy accounts-receivable (AR) software at the West Lafayette campus that was replaced by SAP. |
| change management | The process of developing a planned approach to change in an organization, dealing primarily with the human aspect of change. |
| channel | A box of information in a myPurdue portal window. |
| CODO | Change of Degree Objective: the process by which a current student changes his or her major, the criteria for which are set by the student's specific major, school or program. |
| COEUS | A legacy application that provides pre-award functionality for sponsored programs. A bolt-on application that works in concert with SAP, it is primarily used to develop proposals to submit to sponsors for external funding. |
| Cognos | The new student systems’ reporting tool. |
| configuration | With OnePurdue, this refers to the process of setting up the SAP and Banner software — using their own built-in features — to best meet the needs of Purdue. |
| Course Reference Number |
A unique identifying number used to
track all activities for a course/section, including overrides, grade entry and how it’s listed in the course catalog, rosters and a student’s academic history. |
| Customer Information Control System | CICS was a part of the legacy application system that acted as a gatekeeper of sorts between the mainframe and databases; OnePurdue has eliminated the need for CICS. |
| Customer Relationship Management | CRM refers to methodologies and software that will lead to the coordination of information about Purdue's many contacts outside of the University, including businesses, prospective students, alumni and donors. |
| customer service center | A centralized help desk handling technical questions and problems. It provides call tracking and escalation to Application Support when a question or problem cannot be handled on first contact. |
| customization | Altering a system's software code to include functionality specifically wanted by an organization, although not originally included in the package itself. |
| data cleansing | The analysis and review of data that checks for incomplete records, invalid entries and duplicates. |
| data cube | See “InfoCube.” |
| data warehouse | See “business warehouse.” |
| DbConnect | An SAP utility that can connect with non-SAP databases and pull data from those sources. |
| Enterprise Applications | The division of ITaP that develops, installs and maintains the computer software and databases that support Purdue's core administrative processes and information needs. Commonly referred to as ITEA or EA, this department also provides general standards and guidelines for administrative software and consulting for departmental software development, installation and maintenance. |
| Enterprise Core Components | Called R3 in an earlier version of the mySAP ERP software, ECC is the underlying technology upon which all its individual parts are built. The name of this component was changed with the release of mySAP ERP 2005, which is the version Purdue initially installed in 2007. |
| ePlus | An electronic catalog product used in Ariba. |
| end user | Individuals who use OnePurdue tools for entering data, viewing sets of information, running reports and managing business processes, among other tasks. |
| Enterprise Resource Planning | Commonly referred to as simply “ERP,” this is a collection of software applications that use a common database to integrate an organization's business processes. |
| Final Preparation | Phase 4 of the project. During this time, OnePurdue's finance and human resource teams completed their last activities before each module went into production, including final testing of the new systems and training for those who use them. |
| FMIS | The legacy accounting system that was used by Purdue prior to SAP. |
| functional expert | A staff member within a functional business area designated to assist Self-Service Users and Business Application Users with business process questions, data entry questions and other functional support. (A more formal help desk may exist in some areas.) For example: My United Way deduction is incorrect; My grade was posted incorrectly; How do I complete the screen to process a cash document? |
| fsaATLAS | A reporting tool for international student offices. |
| gap analysis | A comparison of the “as-is” to the “to-be” processes that occurred during the Blueprint phase (Phase 2). Gap analyses helped the OnePurdue Team identify which processes from one did not fit with the other; the business blueprint at the end of Phase 2 offered proposals to resolve these issues. |
| Go-Live and Support | The fifth and final phase of the ASAP process. This is when the new financial and human resource systems were moved into actual production. At this point, most of Purdue’s financial and HR “legacy” software applications were retired and their counterparts in the new OnePurdue systems became fully functional. |
| InfoCube | Previously known as a “data cube”; both InfoCubes and Operational Data Stores are separate information stores (i.e., ways in which the business warehouse stores data). |
| Internet Native Banner |
A special Banner interface used by
some faculty and staff members with administrative duties. |
| IT administrator | A member of a IT/Infrastructure or Basis teams that provides second- and third-level resolution with IT system incidents, problems and change requests. |
| legacy applications | The numerous and dated computer programs that have been or will be replaced by the SAP and Banner ERP software. |
| linked course | The Banner term for what was called a
“sub-parted course” or lecture with a lab in the old (legacy) system. |
| local IT computer support | A local IT computer support area within a business or academic area that provides technical support (e.g., ECN, Business Services Computing, regional campus computing, etc.). |
| Maximo | The legacy software that was used at the West Lafayette campus to track work request orders prior to SAP. |
| metadata | A definition or description of specific data (i.e., data about data). |
| mock month | A quality assurance exercise that tested all the OnePurdue systems and processes needed to conduct a typical month of University business. |
| myPurdue | The Internet portal through which faculty and students access the new student systems. |
| mySAP ERP 2005 | The name of the product that includes SAP's financial and human resources ERP components. |
| NetWeaver | The SAP module that consists of infrastructure tools, including process infrastructure, the enterprise portal and business intelligence. |
| OnePurdue | The University’s three-year, systemwide initiative that is changing the way Purdue does business by integrating mission-critical enterprise data, information and business processes. OnePurdue applications are used by virtually everyone in the University. |
| Operational Data Store | Banner’s reporting database. |
| OPUS | OnePurdue User Support. This is a separate project led by ITaP in partnership with OnePurdue to plan for and deliver training and support for users of the new systems — both during and after their implementations. This support includes installing and running a help desk for OnePurdue-related questions and managing necessary desktop support for all Purdue computers to make sure they have everything they need to fully benefit from the new systems. |
| Pcard | Purchasing Card (i.e., a credit card used for making purchases for the University). |
| portal | A Web interface that serves as the point of entry to the new OnePurdue systems. The OnePurdue portal is used to access Employee Self-Service and the SAP financial and HR applications. Faculty and students use a separate portal, myPurdue, to access the new student systems. |
| Position Budget Control | An SAP process for managing and keeping track of salary budgets. |
| Project Preparation | Phase 1 of the ASAP processes, which concluded June 30, 2005. During this period, the project team was organized, various team-building activities took place, the project began (July 1, 2005), and initial planning began for OnePurdue. |
| PUID | Purdue University identification number, a unique ID code for each individual associated with the University. PUIDs replaced Social Security numbers as a means of identifying people at Purdue. |
| R/3 | Realtime System 3: the core component of earlier versions of SAP's ERP software upon which all its individual parts are built. The name was changed to ECC (Enterprise Core Components) with the release of mySAP ERP 2005. |
| Realization | Phase 3 of the ASAP methodology. During this time, the project team configured the finance and human resource modules and implemented processes defined in the “blueprints” developed during Phase 2. This is when Purdue's legacy financial and HR data were converted from their pre-OnePurdue location to a new database. |
| report user | Someone at Purdue who has access to and executes reports. |
| resident expert | A Business Application User within a departmental area who has been identified as someone who understands the system well enough to assist other users who need help with a particular function or business process in a OnePurdue application. |
| Resumix | Purdue's legacy job applicant tracking system; retired in 2007 and replaced by Taleo. |
| roadmap | A key component of the ASAP process, this defines a systematic approach that incorporates a project plan to an SAP implementation, in this case for OnePurdue's financial and human resource applications. The ASAP Roadmap is a step-by-step guide comprised of five specific phases: Project Preparation, Business Blueprint, Realization, Final Preparation, and Go-Live and Support. |
| RWD Info Pak | A suite of applications used by OnePurdue to develop documentation for user training. |
| sandbox | A safe, pre-development environment — a completely separate group of servers — where the OnePurdue team tests new software installations, features and upgrades to see how they function before adding them to the actual OnePurdue systems in production. |
| SAP | The ERP software vendor selected to provide OnePurdue's financial and human resource systems. (Although SAP's German name translates into five English words — Systems, Applications and Products in Data Processing — it is known simply as “SAP.”) |
| SAP GUI | The graphical user interface (GUI) application that allows users to access specific SAP software in the OnePurdue environment for human resource and financial functions. SAP GUI users, who comprise a small minority of the Purdue staff, launch it from within the OnePurdue (SAP) Portal. |
| Section | The Banner term for what was known as a “division” in the legacy system. |
| security role | Defined access to certain types of data in Banner based on one's position and duties. |
| scope | A measurable definition of OnePurdue's goals, resources, timing and desired outcomes. |
| self-service user | A OnePurdue user using Employee Self-Service for personal business needs. |
| Self-Service Banner |
The software behind the myPurdue portal. |
| stakeholder | A person, department of organization that has an interest in the success of a project. |
| STAR | Previously known as Day on Campus, Summer Transition, Advising and Registration (STAR) is Purdue's orientation program for new, domestic, first-year and transfer students. |
| statement of work | A document that sets forth services to be performed. |
| subject matter expert | A member of a OnePurdue team that provides second- and third-level resolution with configuration and business process incidents, problems and change requests. |
| SunGard Higher Education | The ERP vendor selected to provide OnePurdue's new student systems, a software package called Banner. |
| Supplier Relationship Management | The Web-based SAP module that replaced Purdue's legacy e-procurement system, Ariba. SRM includes contracting, bidding and requisitioning components. |
| SSINFO | A legacy system that allowed students to access course, grade, financial aid and other information online. It was replaced by the Banner Student systems in fall 2008. |
| system test | An implementation activity that tests the interfaces between sets of applications or functional areas in a new system. It verifies the ability of the system to handle data and operating requirements common to more than one area, and to verify the impacts from one department to another. |
| team lead | An individual who leads a OnePurdue team. |
| Term | Designation of a specific semester; for
example: fall 2008 = 200910, spring 2009 = 200920, and summer 2009 = 200930. |
| time ticket | Defined time periods during which students are allowed to enroll in courses for a given term. More |
| to-be | The new OnePurdue business processes. |
| unit test | A test used to verify the acceptable functionality of a single program, operation or process that does not test the impact and integration points with other applications or operations. |
| WebCT Vista | See Blackboard Vista. |
Acronyms and Abbreviations
| AA | Asset Accounting |
| ABAP | Advanced Business Application Programming |
| AD | Application Development |
| AIMS | Account Information Management System |
| AP | Accounts Payable |
| ASAP | Accelerated SAP |
| AVC | Availability Control |
| BAU | Business Application User |
| BEx | Business Expert |
| BI | Business Intelligence |
| BPR | Business Process Review |
| BPP | Business Process Procedure |
| BSAC | Business Systems Advisory Committee |
| BSSC | Business Systems Steering Committee |
| BW | Business Warehouse |
| CD | Collection and Disbursement |
| CAPP | Curriculum, Advising and Program Planning |
| CARS | Centralized Accounts Receivable System |
| CBT | Computer-Based Training |
| CICS | Customer Information Control System |
| CO | Controlling |
| CODO | Change of Degree Objective |
| CPTS | Construction Project Tracking System |
| CRM | Customer Relationship Management |
| CRN | Course Reference Number |
| CSC | Customer Service Center |
| CMT | Change Management and Training |
| CUL | Capacity Utilization Level |
| DMAC | Data Management Advisory Committee |
| DREF | Departmental Reference Number |
| EAI | Enterprise Application Integration |
| ECC | Enterprise Core Components |
| ERAC | Enterprise Reporting Advisory Committee |
| ERP | Enterprise Resource Planning |
| ESA | Enrollment and Student Affairs |
| ESS | Employee Self-Service |
| EUA | Enterprise User Administration |
| EWOTS | Electronic Work Order Transfer System |
| EUT | End-User Training |
| FA | Financial Accounting |
| FERPA | Family Educational Rights and Privacy Act |
| FI | Finance |
| FM | Funds Management |
| FMIS | Financial Management Information System |
| GM | Grants Management |
| GUI | Graphical User Interface |
| HIPAA | Health Insurance Portability and Accountability Act |
| HR | Human Resources |
| HRIS | Human Resources Information System |
| ICHE | Indiana Commission of Higher Education |
| ILT | Instructor-led training |
| IM | Inventory Management |
| IM/WM | Inventory and Warehouse Management |
| INB | Internet Native Banner |
| IRB | Institutional Review Board |
| IRM | Information Resource Management |
| ISSC | Information Steward Steering Committee |
| IT | Information Technology |
| ITaP | Information Technology at Purdue |
| ITCR | ITaP Customer Relations |
| ITEA | ITaP Enterprise Applications |
| ITI | ITaP Infrastructure |
| ITSP | ITaP Security and Privacy |
| LMS | Learning Management System |
| MIF | Multi-Institution Functionality |
| mPAC | myPurdue Portal Advisory Committee |
| ODS | Operational Data Store |
| OEC | Oversight Executive Committee |
| OLAP | Online Analytical Processing |
| OM | Organization Management |
| OPUS | OnePurdue User Support |
| PA | Personnel Administration |
| PBC | Position Budget Control |
| PERNR | Personnel Number |
| PI | Process Infrastructure |
| PM | Plant Maintenance |
| PMDES | Person Master Data Enterprise Services |
| PMO | Project Management Office |
| PS | Project Systems |
| PREMIS | Purdue Registration and Event Management Information System |
| PSCD | Public Sector Collection and Disbursement (long form of CD) |
| PSG | Purdue Student Government |
| PUID | Purdue University Identification Number |
| QA | Quality Assurance |
| QAS | Quality Assurance System |
| QRC | Quick Reference Card |
| RICE | Reports, Interfaces, Conversions and Enhancements |
| RIO | Real Internal Order |
| RMS | Resident Management System |
| ROI | Return on Investment |
| SAN | Storage Area Network |
| SAP GUI | SAP Graphical User Interface |
| SEVIS | Student Exchange Visitor Information System |
| SIO | Statistical Internal Order |
| SIS | Student Information System |
| SIT | System Integration Testing |
| SME | Subject Matter Expert |
| SOW | Statement of Work |
| SPS | Sponsored Programs Services |
| SRF | Service Request Form |
| SRM | Supplier Relationship Management |
| SSB | Self-Service Banner |
| SSU | Self-Service User |
| STAR | Summer Transition, Advising and Registration |
| SUS | Supplier Self-Service |
| TCO | Total Cost of Ownership |
| TR | Treasury |
| TV | Travel |
| UAT | User Acceptance Testing |
| UDO | University Development Office |
| VEPR | Voluntary Early Partial Retirement |
| WBS | Work Breakdown Structure |
| WBT | Web-Based Training |
| XI | Exchange Infrastructure (also known as Process Infrastructure, or PI) |


