| Data element |
Definition |
ACCOUNTING_PERIOD
Indexed - yes
Format - char (6)
May be null? yes |
The Accounting_Period within which the Check_Date falls. It should be possible to recognize entries for a given fiscal year by doing a comparison on this date. For example, a check date of July 2, 1999 corresponds to the JUL-99 Accounting_Period, within fiscal year 2000. The Accounting Period is stated in MON-YY format. MON is the calendar month (stored in upper case), and YY is the calendar year. Note that the beginning and ending dates of an accounting period are not necessarily the same as the first and last day of the calendar month.
Example: JUL-99 (July 1999, which occurs in fiscal year 2000)
Source: Derived from ACCT_CHECK_DATE, during data load.
|
ACCT_CHECK_DATE
Indexed - yes
Format - date
May be null? yes |
The Check Date of the Payroll Run for the transaction; indicates the month of posting to the General Ledger.
Source: #XPAR-CHECK-DATE
|
| CALENDAR_MONTH
Indexed - yes
Format - char (2)
May be null? yes |
The number that identifies the calendar month (of the accounting period).
Example: 01 (January); 11 (November).
Values:
01 January
02 February
03 March
04 April
05 May
06 June
07 July
08 August
09 September
10 October
11 November
12 December
13 Adjustment period
Source: Derived from ACCT_CHECK_DATE, during data load. |
| CALENDAR_YEAR
Indexed - yes
Format - char (4)
May be null? yes |
The calendar year for the ACCOUNTING_PERIOD. The calendar year begins January 1 and ends December 31. Example: 1999 (the CALENDAR_YEAR for ACCOUNTING_PERIOD JUL-99).
Source: Derived from ACCT_CHECK_DATE, during data load.
|
DISTRIBUTION_PERIOD
Indexed - no
Format - date
May be null? yes |
The pay period end date associated with the payment.
Source: #XPAR-DIST-PER |
EARNINGS_AMOUNT
Indexed - no
Format - number(9,2)
May be null? yes |
The amount of the earnings paid to the employee. Credits to the account, for reallocations or cancellations, will appear as negative amounts.
Source: #XPAR-EARN-AMT |
EARNINGS_HOURS
Indexed - no
Format - number(5,2)
May be null? yes |
If there is time is associated with the earnings type (e.g., REG - weekly regular time), EARNINGS_HOURS contains the hours worked. For earnings types based on dollars only (e.g., RMO-monthly regular time) no hours will be present.
Source: #XPAR-TIME |
EARNINGS_TYPE
Indexed - yes
Format - char(3)
May be null? no |
A 3-character code indicating the type of earnings.
Earnings of the 'CTU' and 'CTX' types (representing 'CPUP Taxable Tuition' and 'CPUP Taxable Other') represent tax adjustments, and are not used for payments. Therefore, records with these earnings types will not be found in the EMPLOYEE_PAYMENT table.
Examples: RMO (regular monthly pay); OT2 (overtime at double time)
Values:
Refer to the DWPAY.PAYROLL_EARNINGS table for values.
Source: #XPAR-EARN-TYPE |
EXTRACT_DATE
Indexed - yes
Format - date
May be null? no |
The date the record was extracted from the Payroll system and loaded into the Warehouse.
|
FISCAL_MONTH_SEQ
Indexed - yes
Format - char (2)
May be null? yes |
The month (or accounting period) of the fiscal year. This field is used for sorting.
Examples: 01 (July); 11 (May). See also FISCAL_YEAR
Values:
01 July
02 August
03 September
04 October
05 November
06 December
07 January
08 February
09 March
10 April
11 May
12 June
13 Adjustment period
Source: Derived from ACCT_CHECK_DATE, during data load. |
FISCAL_YEAR
Indexed - yes
Format - char (4)
May be null? yes |
The financial year within which the Accounting_Period falls. Penn's fiscal year begins July 1 of one calendar year and ends June 30 of the next calendar year.
Example: for a Check_Date of December 1, 1999, 2000 (fiscal year that began July 1, 1999, and ended June 30, 2000)
Source: Derived from ACCT_CHECK_DATE, during data load. |
HOME_DEPT_ORG
Indexed - yes
Format - char(4)
May be null? no |
The 4-digit number that represents the organization that owns the employee's record and is responsible for its maintenance. An organization is a subdivision of the University created for management purposes. An Organization belongs to only one School or Responsibility Center, and its organization code is unique. (The code set is from the University's General Ledger, and has been in use since July 1, 1996.)
Examples: 0104 (CHEMISTRY); 0001 (GEN UNIVERSITY)
Values:
Refer to the DWADMIN.ORG_CODES table for values.
Source: #XPAR-DEPT-NO |
HOME_SCHOOL_CTR
Indexed - yes
Format - char(2)
May be null? no |
A 2-digit number used to identify the school or center that owns the employee's record and is responsible for its maintenance. The code set is from the University's General Ledger, and has been in use since July 1, 1996.
Example: 40 (School of Medicine)
Values:
Refer to the DWADMIN.ORG_CODES table, for values where
Home_School_Ctr = Center_Code.
Source: #UDPT-REPORTING-LVL(2,2) |
HOURS_ADJUSTMENT_IND
Indexed - no
Format - char(1)
May be null? yes |
Indicates if hours balances associated with the earnings type should be adjusted.
Values:
Null (blank) Adjust the hours associated with the earnings type.
A Earnings are prorated over the entire pay period. The
hours associated with the earnings type are not adjusted.
Source: #XPAR-HRS-IND |
JOB_CLASS
Indexed - yes
Format - char (6)
May be null? yes
|
Key to the job classification table where the job attributes are listed. Refer to the JOB_CLASS or JOB_CLASS_GENERAL tables to find the title, grade, personnel class or other job attributes which currently correspond to the Job_Class.
Example: 226010 (Associate Professor C-E)
Values:
Refer to the DWADMIN.JOB_CLASS table for values.
Source: #XPAR-JOB-CLASS |
PAR_ERN_SEQUENCE_NUMBER
Indexed - no
Format - number(5)
May be null? yes |
The sequence number identifying each earnings record within the PAR record; assigned during the extract process. |
PAR_SEQUENCE_NUMBER
Indexed - no
Format - number(5)
May be null? no |
The sequence number for PAR record, assigned during the data extract process. |
PAY_CYCLE
Indexed - yes
Format - char(2)
May be null? no |
The pay cycle.
Values:
W1 – weekly cycle
M1 – monthly cycle
M2 – monthly exec cycle
XX – W2 adjustment cycles
Source: #XPAR-PAY-CYCLE
|
PAY_END_DATE
Indexed - yes
Format - date
May be null? no |
Date through which the transaction was made to the employee.
Source: #XPAR-PAY-END-DATE
|
PAY_SCHEDULE
Indexed - yes
Format - char(3)
May be null? no |
Three digit schedule indicating the pay within the month.
Values:
001 – first weekly pay
002 – second weekly pay
003 – third weekly pay
004 – fourth weekly pay
005 – fifth weekly pay
006 – monthly pay
007 – monthly Executive Pay
998 – W-2 Executive adjustment cycle
999 – W-2 adjustment cycle
Source: #XPAR-SCHEDULE |
PENN_ID
Indexed - yes
Format - char (8)
May be null? yes |
The 8-digit identification number assigned to an individual by Penn Community system. For example: 77777777. No two persons have the same Penn ID. Note that Penn IDs created in and assigned by Penn Community begin at 10000000. Within the Data Warehouse, the numeric range from 00000000-00999999 is used for individuals who do not yet have a Penn ID in Penn Community, to allow for reliable joins between tables using the PENN_ID column. When a Penn ID appears for the individual appear in Penn Community, it will replace the assigned value throughout the Data Warehouse.
Source: Determined by mapping SSN to Penn_ID
|
POSTED_COA_ACCOUNT
Indexed - no
Format - char (26)
May be null? yes
|
The 26-digit account number from the present General Ledger accounting structure (in use at Penn since July 1, 1996) indicating the source of the payment to the employee. The Posted_COA_Account consists of seven segments:
Posted_COA_CNAC
Posted_COA_Org
Posted_COA_BC
Posted_COA_Fund
Posted_COA_Object
Posted_COA_Program
Posted_COA_Center_Ref
See also the definitions for Posted_COA_CNAC, Posted_COA_Org, Posted_COA_BC, Posted_COA_Fund, Posted_COA_Object, Posted_COA_Program, and Posted_COA_Center_Ref.
Source: #XPAR-ACCT
|
POSTED_COA_BC
Indexed - no
Format - char (1)
May be null? yes
|
The budgetary control character that represents the level at which funds availability checking occurs for the salary expense. Posted_COA_BC is the third segment of the Posted_COA_Account.
Example: 1 (CNAC/ORG/FUND Year-To-Date)
Values:
0 Project-To-Date for capital projects
1 CNAC/ORG/FUND Year-To-Date
2 CNAC/ORG/FUND/CREF Year-To-Date
4 CNAC/ORG/FUND/CREF Project-to-Date
Source: Derived from POSTED_COA_ACCOUNT |
POSTED_COA_CENTER_REF
Indexed - yes
Format - char (4)
May be null? yes
|
The Center Reference Code. A 4-character identifier uniquely defined by each School or Center. Posted_COA_Center_Ref is used to record information that is important to a school or center but is inappropriate for any other segment of the Posted_COA_Account. The value of the Posted_COA_Center_Ref is unique within a school or center. Posted_COA_Center_Ref is the seventh and last segment of the Posted_COA_Account.
Examples (for center 02): 4045 (Graduate Programs); 4091 (SAS Newsletter)
Values:
Refer to the DWADMIN.CENTER_REF_CODES table for values.
Source: Derived from POSTED_COA_ACCOUNT
|
POSTED_COA_CNAC
Indexed - yes
Format - char (3)
May be null? yes
|
The 3-character Center Net Asset Class. The first two positions of the Posted_COA_CNAC identify the school or center. The last position identifies the Net Asset Class: 0 (Unrestricted); 1 (Temporarily Restricted); 2 (Permanently Restricted). Posted_COA_CNAC is the first segment of the Posted_COA_Account.
Examples: 880 (Medical School, Unrestricted); 921 (Human Relations, Temporarily Restricted)
Values:
Refer to the DWADMIN.CNAC_CODES table for values.
Source: Derived from POSTED_COA_ACCOUNT
|
POSTED_COA_FUND
Indexed - yes
Format - char (6)
May be null? yes
|
The 6-character fund code. A fund is the unique identifier for a specific set of financial resources that needs tracking or management. Posted_COA_Fund is the fourth segment of the Posted_COA_Account. If your organization is the Responsible_Org for the fund (even if it is not the Posted_COA_Org, the Home_Dept_Org, or the Job_Dept_Org) you will have access to the record.
Examples: 000000 (General Unrestricted Fund); 010201 (SAS: GEN FUND 1)
Values:
Refer to the DWADMIN.FUND_CODES table for values.
Source: Derived from POSTED_COA_ACCOUNT |
POSTED_COA_OBJECT
Indexed - yes
Format - char (4)
May be null? yes
|
The 4-character Object Code that identifies the asset, liability, revenue, or expense. Posted_COA_Object is the fifth segment of the Posted_COA_Account. The Payroll system was rewritten to accept that 26-digit account code combination in place of legacy 9-digit account numbers for fiscal year 1999. Effective June 28, 1998, all Payroll transactions that require an account are completed using the 26-digit account code combination. For records prior to fiscal year 1999, in cases where the Requested_Account could not be converted, Posted_COA_Account is a suspense account, and 9501 is the value for the Posted_COA_Object. In cases where the subcode section of the Requested_Account could not be translated to an Object_Code, OBJT will be the value for Posted_COA_Object.
Examples: 5220 EXTERNAL OFFICE SUPPLIES); 1149 (CASH SUSPENSE)
Values:
Refer to the DWADMIN.OBJECT_CODES table for values.
Source: Derived from POSTED_COA_ACCOUNT |
POSTED_COA_ORG
Indexed - yes
Format - char (4)
May be null? yes
|
The 4-character code identifying the Organization. This is a subdivision of the University created for management purposes. An Organization belongs to only one responsibility center, and its Organization code is unique. That is, no two Organizations will have the same values for Posted_COA_Org. Posted_COA_Org is the second segment of the Posted_COA_Account.
Examples: 0702 (Wharton Finance); 0705 (Wharton Legal Studies)
Values:
Refer to the DWADMIN.ORG_CODES table for values.
Source: Derived from POSTED_COA_ACCOUNT
|
POSTED_COA_PROGRAM
Indexed - yes
Format - char (4)
May be null? yes
|
The 4-character code indicating the program. This is an activity or work process commonly defined across the University for tracking a program's activity across Schools and Centers (or across organizations within a school or center). Posted_COA_Program is the sixth segment of the Posted_COA_Account.
Examples: 7311 (ALUMNI RELATIONS); 0001 (DISCRETIONARY)
Values:
Refer to the DWADMIN.PROGRAM_CODES table for values.
Source: Derived from POSTED_COA_ACCOUNT |
RESPONSIBLE_ORG
Indexed - yes
Format - char (4)
May be null? yes
|
The 4-character code for the organization responsible for managing the Posted_COA_Fund. Many organizations may use the same fund, but only one organization -- the Responsible_Org -- is accountable for managing the fund. Those who are authorized to access records for the Responsible_Org for the fund may access all records for the fund, regardless of the value of the Posted_COA_Org in the Posted_COA_Account for the record.
Values:
Refer to the DWADMIN.ORG_CODES table for values.
Source: Derived from POSTED_COA_ACCOUNT |
SSN
Indexed - yes
Format - char (9)
May be null? no |
The 9-digit Social Security Number of the employee. A Social Security Number is a unique number assigned to an individual by the federal Social Security Admininistration.
Values in this column will only be displayed to individuals with access to employee SSN data; all other users will retrieve nulls in this column.
Source: #XPAR-ID-NO
|
