OARS System and Module Descriptions

Three systems provide M-Pathways data:

This page describes the M-Pathways systems and the modules within these systems. It also describes the corresponding data sets in the U-M Data Warehouse, which provides convenient access to the data in a reporting environment.

Financials System

The M-Pathways Financials system consists of the following integrated modules, which provide information to and rely on information from one another: Accounts Receivable, Billing, General Ledger, and Procurement. The M-Pathways Physical Resources system is part of the Financials system. It consists of three modules: Asset Management, Inventory, and Space Management.

Financials Modules

  • Accounts Receivable & Billing (two modules): Allow the university to bill, record, and track payments for sponsored research and centralized general receivables.
  • General Ledger: Used to record all of the university's financial transactions. Users can view and maintain budget data, as well as add and maintain unit-defined commitments.
  • Procurement: Involves all processes used to request, order, audit, and pay for goods and services.

Physical Resources Modules

  • Asset Management: Used to track and maintain information about the university’s assets, including their identification, acquisition data, current status, and financial data. This module allows users to update the description, location, and unit contact information for assets belonging to their department(s).
  • Inventory: Used by some university units to order, replenish, and track the supplies that they warehouse.
  • Space Management: Used to maintain and update data about university buildings, rooms, and facilities. This module allows users to add and change their department’s space data in order to authorize and submit the annual Space Survey, as well as submit space data changes, identify and report on departmental data, and track room elements throughout the year.

Financials and Physical Resources Data Sets (U-M Data Warehouse)

  • Financials Data Set: Contains General Ledger, Budget, and Procurement data as of July 1998, and Accounts Receivable and Billing data as of November 2003.*
  • Legacy Financial Data Set: Contains five years of revenue and expenditure data through June 1998, summarized at the account balance and account/financial class levels, with drill-down capability into Statement of Account detail and Service Unit Billing detail data.
  • Asset Management Data Set: The Property Disposition Office provides information about disposing of assets.*
  • Space Management Data Set *

Refresh Information: U-M Data Warehouse Data Sets provides specific refresh times.

Human Resource Management System (HRMS)

The M-Pathways Human Resources Management System (HRMS) provides a single source of information about U-M employees, prospective employees, and retirees. It consists of the following four highly integrated modules, which provide information to and rely on information from one another: Benefits Administration, Human Resources, Payroll and Time & Labor.

Human Resources Management System (HRMS) Modules

  • Benefits Administration: Used by the Benefits Office staff to manage benefit services for U-M faculty and staff and retired faculty and staff.
  • Human Resources: Provides a single source of information about employees and applicants. U-M units use the Human Resource module to communicate changes to employment records to Human Resource Records Information System (HRRIS) including: job data changes, salary distribution changes, additional pay, effort certification, leaves, terminations, Form Gs, and instructional hiring.
  • Payroll: Used by the Payroll Office staff to maintain payroll data and manage the payroll processes. It captures employee attendance and timekeeping information, produces checks and statements of earnings (paystubs), distributes salary and fringe benefits to staff and retirees, processes remittances to government agencies for whom deductions are taken, and creates required tax documents.
  • Time & Labor: Provides a resource for managing all aspects of time and labor tracking.

HRMS Data Sets (U-M Data Warehouse)

  • Benefits Data Set: Contains information about people enrolled in benefits at U-M, including employees and retirees. Information includes demographic, job, benefit enrollment, benefits billing and benefit remittance data for anyone eligible to be enrolled in U-M benefit plans. Historical information is available from June 6, 2001, forward, and a snapshot of Legacy data is available for June 2001, December 2000, and January 2000. Access to this data set is restricted to staff in Human Resources Records and Information Services (HRRIS) and the Benefits Office.*
  • Human Resource Data Set: Contains information about all regular and temporary U-M employees. Information includes demographic data, job data, regular pay data, and additional pay data relating to each employee's job. Information is available from July 1, 2001, forward, and will carry all history from that date forward. Also includes access to the Human Resource Snapshot data set.*
  • Legacy Human Resource Data Set: Contains faculty and staff data, including appointments, funding, job classes, leaves, terminations, tenure, and employment history from 1978 to June 2001.
  • Payroll Data Set: Contains information about any payments made by, or recorded in, the U-M Payroll system. These payments include payroll payments; student financial payments; miscellaneous payments made outside of the university Payroll system that must be recorded for calendar year-end reporting; and the university contribution to any deductions, benefits, or taxes associated with the payments. Information is available in these tables for payrolls run from July 1, 2001, forward.*
  • Time and Labor Data Set: Contains information about time reported to the U-M Time and Labor module and how that information is incorporated into the Payroll system. It also contains information about leave accruals, missing and no variance time, Time and Labor leave plan enrollment, and a calendar to identify holidays and days of the week. Information in these tables is available for payrolls run beginning July 1, 2001, to the present, with the exception of the Payable Time and Reported Time tables that contain data for the current month and prior 24 months.*
  • Legacy Payroll Data Set: Contains detailed and summarized gross pay data and university contributions to fringe benefits from the legacy Payroll system, including prior year correction payroll transactions that occurred after the July 1, 2001 implementation of M-Pathways HRMS. The Payroll legacy data set contains payroll report data from July 1, 1995, through June 30, 2001.

Refresh Information: U-M Data Warehouse Data Sets provides specific refresh times.

Student Administration System

The M-Pathways Student Administration system provides a single source for information about students and the administrative data that supports learning and teaching at U-M. It consists of the following six highly integrated modules, which provide information to and rely on information from one another: Academic Advising, Curriculum, Financial Aid, Recruiting/Admissions, Student Financials, Student Records, and Campus Community.

Student Administration Modules

  • Campus Community: Spans the Student Administration System and the Human Resource Management System (HRMS). It stores demographic information about all members of the university community in one location, eliminating the need to re-enter data when an individual changes his or her status.
  • Financial Aid: Enables U-M staff to establish eligibility for federal, state and institutional need-based aid and for merit-based aid; evaluate and monitor aid-related communications; provide per-event and cumulative fiscal management reporting for all aid programs; and manage student work-study employment.
  • Student Financials: Supports university staff who manage student accounts and information. It also supports admissions activities by processing application fees and enrollment deposits, and it interfaces with the Financial Aid module.
  • Recruiting/Admissions: Captures personal information when a prospective student first communicates with U-M. This initial record is modified when an individual's relationship with U-M changes (such as from prospect to applicant, to student, to financial aid recipient, to graduate, to professional school applicant, or to employee).
  • Student Records: Used to capture and maintain data related to students' academic endeavors and performance. Key processes supported by the Student Records module include: student academic program maintenance, academic advisement, enrollment (a.k.a. registration), curriculum maintenance, grading, and graduation.

Student Administration Data Sets (U-M Data Warehouse)

  • Recruiting and Admissions Data Set: Designed to meet nearly all ad hoc reporting needs, the 59 tables in this data set contain all current and future prospects and applicants, as well as three years of historical records. Also includes access to the Admissions Snapshot data set and the Admissions Roster data set.*
  • Student Records Data Set: Contains academic data for students who have matriculated at UM-Ann Arbor. The data includes students' personal information (bio/demo data), enrollment, courses, grades, degrees, transfer credit, degree audit, and more.*
  • Financial Aid/Student Financials Data Set: Designed to meet the ad hoc reporting needs of Financial Aid and Student Financials users. The Financial Aid data includes all financial aid awards and disbursements made to U-M students. The Student Financials portion includes service indicator data, student receivables aging data, collection data, and Graduate Student Assistant Waiver data. Additionally, Student Financial transaction detail tables contain Chartfield information that is included in Statement of Activity and reconciliation reports. Student Financial detail is available only for items that have been journalized in the General Ledger. Some data is shared between Financial Aid and Student Financials, such as Residency and Ethnicity data. Some tables are from the Student Records and Recruiting and Admissions data sets (e.g., Adm Appl Eval).*
  • Third Week Count Data Set: Contains snapshot data for each term of classes, beginning with the Summer 2000 term. Each snapshot gives student data including personal biodemographic, academic record, enrollment, and class data that pertained to that term. The snapshot for a given term is taken the night after the end of the third week of classes. After the snapshot is taken for the current term, the data are appended to the data from previous terms. The data are used for official reporting purposes.*
  • Student Retention and Completion Data Set: Intended for producing student retention (from one year to the next, how many students return to continue their studies) and completion (how many students complete degrees and how long they take) reports. The tables in this data set are populated from a snapshot the night after the end of the third week of classes every Fall term. Access to this data set is currently restricted to central offices.*
  • Legacy Official Third Week Count Data Set: Contains program, election, field of study, demographic, and registration information from the summer of 1990 to July 2000. Used for matching the Registrar's Office official counts for Federal and state reporting and replicating counts from the term enrollment and minority reports published by the Registrar's Office.
  • Legacy Student Data Set: Information about students from 1982 to June 2000, including program, registration, field of study, demographic, and grade data, as well as election information from June 1999 to June 2000. Degree data for students registered in fall 1993 forward is also included. Used to answer questions such as: What is the grade distribution for a course section? Who is registered in a specific unit or course in a particular term? How many students are first-year students this fall? How many student credit hours were generated in a unit?

Refresh Information: U-M Data Warehouse Data Sets provides specific refresh times.