PAR_MAIN Table - Data Element Index   Tables and Data Elements   Salary Management Home   Data Warehouse Home

PAR_MAIN Table

Note: This table is no longer updated, following the retirement of the mainframe Personnel/Payroll system and the implementation Workday@Penn in July 2019.

Explanation
Contains data on employee payments from the Penn Payroll system, and the gross amounts that comprise those payments.

Common Uses
To determine the assorted gross amounts and other check details by employee and pay cycle.

PAR_SEQUENCE_NUMBER
PAY_CYCLE
PAY_END_DATE
PAY_SCHEDULE
SSN

ACCOUNTING_PERIOD
ACCT_CHECK_DATE
CALENDAR_MONTH
CALENDAR_YEAR
CHECK_ADVICE_INDICATOR
CHECK_DATE
DEDUCTION_SCHEDULE
EXTRACT_DATE
FISCAL_MONTH_SEQ
FISCAL_YEAR
HOME_DEPT_ORG
HOME_SCHOOL_CTR
PAR_NAME
PAR_SEQUENCE_NUMBER
PAY_CYCLE
PAY_END_DATE
PAY_SCHEDULE
PENN_ID
SEPARATE_CHECK_PAY_END_DATE
SSN
TRANSACTION_CODE

COMP_PERSON (DWCOMP)
EMPLOYEE (DWADMIN)
PAR_DOLLAR_GTN_ADJUSTMENTS (DWPAY)
PAR_EARNINGS (DWPAY)
PAR_GROSS_TO_NET (DWPAY)
PAR_HOUR_ADJUSTMENTS (DWPAY)
PAR_TAX_ACH_BENEFITS (DWPAY)

Cautions

• During a single payroll process (uniquely identified by pay end date, pay schedule and pay cycle), an employee may have a number of PAR records. They can have up to 10 current activity records (transaction code 85) that will all be combined into a single pay stub, as well as multiple expense transfers/reallocations (transaction code 65), multiple hand-drawn checks (transaction code 80), multiple cancellations (transaction code 70), and multiple overpayments (transaction code 75). Each employee (unique SSN) record within this payroll process is given a sequence number (the PAR_Sequence_Number) that will identify it. Related records in other PAR tables (PAR_EARNINGS, PAR_GROSS_TO_NET, PAR_HOUR_ADJUSTMENTS, and PAR_TAX_ACH_BENEFITS) may be found by joining on the PAR_Sequence_Number and SSN. The other tables have additional internal sequencing, that serves to order the related records within the PAR_Sequence_Number.

• Employee attributes, such as name, employment status and dates, and so on, are included in the PAR_MAIN table. Note that these columns in PAR_MAIN reflect the values of the data at the time the PAR record was created, and will not be updated if the information changes in the EMPLOYEE or COMP_PERSON tables.

• If you are trying to look at PAR data specifically for weekly- or month-paid individuals, use the PAR_MAIN.Deduction_Schedule to determine the pay type (M1 or W1). You can then refer to the PAR_MAIN.Employee_Type to see what type of monthly or weekly paid staff the individual is. Note that the Employee_Type may be incorrect if the individual has been paid off-cycle (e.g., a monthly-paid person with a payment during a weekly cycle, or vice versa). The Employee_Type should be reliable if the individual is paid in the correct cycle.

• You can access a PAR_MAIN record only if you are authorized to access data for the employee's home school or organization. To access basic biographic/demographic data for all employees, use the unsecured EMPLOYEE_GENERAL table. Keep in mind that records for executive paid individuals are not accessible to end-users in the Data Warehouse. Access to SSN is further restricted to specifically authorized individuals.

• The Data Warehouse is updated with PAR, payments and encumbrance data directly following Salary Management, which may actually be a couple days in advance of BEN Financials. To pull matching data from BEN Financials, Salary Management and the Data Warehouse at the end of a period you'll need to run your system reports and Warehouse queries between the Tuesday after payroll runs, producing the last weekly check for the month, and before the Monday of the following week. By that last Tuesday, monthly payroll has already been run, so those actuals and updated encumbrances will be correct. This limits the risk of retrieving data from Salary Management or the Warehouse for the last weekly pay of the month which may, in fact, be posted to the next BEN Financials Accounting Period. (For example, for AUG-99, reports would have to have been run between August 27 and August 30th.)

• The PAR_MAIN table can be found in the DWPAY schema.

PAR_MAIN Table - Data Element Index   Tables and Data Elements   Salary Management Home   Data Warehouse Home