• ACADEMIC_BASE_SALARY
• AFFILIATION_CODE
• BARG_UNIT_ELIG
• BENEFIT_BASE
• BIRTH_DATE
• CAMPUS_MAIL_CODE
• COUNTRY_OF_CITIZENSHIP
• CPUP_BENEFITS_INDICATOR
• CPUP_JOB_INDICATOR
• CURRENT_DIST_INDICATOR
• CURRENT_JOB_INDICATOR
• DISABILITY_STATUS
• EDUCATION_LEVEL
• EDUCATION_LEVEL_YEAR
• EMAIL_ADDRESS
• EMERGENCY_CONTACT
• EMERGENCY_CONTACT_PHONE
• EMERGENCY_CONTACT_RELATIONSHIP
• EMPLOYMENT_DATE
• EMPLOYMENT_STATUS
• EMPLOYMENT_STATUS_DATE
• EXEMPT_NONEXEMPT
• FIRST_NAME
• FULL_PART_TIME
• HOME_DEPARTMENT
• HOME_DEPT_ORG
• HOME_SCHOOL
• HOME_SCHOOL_CTR
• LAST_ACTION_DATE
• LAST_EXTRACT_DATE
• LAST_NAME
• LAST_PAY_PROCESSED_DATE
• LAST_PERSONNEL_ACTION
• LEAVE_REASON
• LEAVE_RETURN_DATE
• MARITAL_STATUS
• MIDDLE_NAME
• MILITARY_STATUS
• MINIMUM_RECORD
• NAME
• NAME_FLIPPED
• NAME_PREFIX
• NAME_SUFFIX
• NEXT_SALARY_REVIEW_DATE
• ORIGINAL_HIRE_DATE

• PAY_STATUS
• PENNKEY
• PENN_ID
• PREVIOUS_SSN
• PRI_ACAD_APPT_BEGIN_DATE
• PRI_ACAD_APPT_END_DATE
• PRI_ACAD_APPT_JOB_CLASS
• PRI_ACAD_APPT_SALARY
• PRI_ACAD_DEPT_ORG
• PRI_ACAD_JCLS_ENT_DATE
• PRI_ACAD JOB LINK ID
• PRI_ACAD_UNIV_POS_NO
• PRIMARY_APPT_BEGIN_DATE
• PRIMARY_APPT_END_DATE
• PRIMARY_APPT_JOB_CLASS
• PRIMARY_APPT_SALARY
• PRIMARY_DEPARTMENT
• PRIMARY_DEPT_ORG
• PRIMARY_JOB_CLASS_ENTRY_DATE
• PRIMARY_JOB LINK ID
• PRIMARY_SCHOOL_CENTER
• PRIMARY_UNIV_POSITION_NUMBER
• PRIOR_PAY_DATE
• PROFESSIONAL_NAME
• PROFESSIONAL_NAME_FLIPPED
• PROFESSIONAL_NAME_PREFIX
• PROFESSIONAL_NAME_SUFFIX
• PROVOST_STAFF_MINUTES_DATE
• PUBLICATIONS_MAIL_CODE
• REG_OR_TEMP
• REHIRE_DATE
• SENIORITY_DATE
• SEPARATION_REASON
• SEX
• SSN
• SSN4
• TENURE_PROBATION_DATE
• TENURE_STATUS
• TENURE_STATUS_DATE
• TERMINATION_DATE
• VISA
• VISA_EXPIRATION_DATE
• WORK_PHONE1
• WORK_PHONE2

In general an Academic_Base_Salary is appropriate only for those individuals holding an academic primary appointment. In the PennWorks system, the academic base salary and the salary distributions are recorded on separate screens; the academic base salary is not linked to a particular job. When querying someone's Academic_Base_Salary, it is a good idea to confirm that the primary appointment job class for that person is a faculty job.

Academic_Base_Salary and other Faculty Compensation components are entered into PennWorks and fed nightly from there to the DWCOMP.COMP_PERSON_SALARY table, and then on to the EMPLOYEE table.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Academic_Base_Salary for employees whose data is updated from Workday will be 0.]

Values:

0-9,999,999.99

AFFILIATION_CODE

Indexed - no
Format - char (3)
May be null? yes

Example: A scientist is an adjunct professor at the University of Pennsylvania but works primarily at Merck, Sharp and Dohme. Therefore, M12 is the Affiliation_Code.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Affiliation_Code for employees whose data is updated from Workday will be null.]

Values:
Refer to the COMP_AFFILIATION_LIST table for values.

Indicates whether employee’s position is represented by a bargaining unit (union).

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Affiliation_Code for employees whose data is updated from Workday will be null.]

Values:
U         Union
null      Non-union

Benefits Base Salary is the amount used to calculate an employee’s Basic & Supplemental Life Insurance. Benefits Base includes the salary paid to the employee for the primary appointment at the University, including pre-tax retirement, health care and spending account contributions but excluding any bonus or overtime payments. If the employee is a faculty member with a full-time administrative appointment, Benefits Base means the annual salary paid for the primary appointment, including pre-tax contributions plus the salary for any administrative appointments. Benefits Base is determined prior to open enrollment (typically in March) and remains in effect for the entire upcoming plan year. It does not take into account pay received for services performed for CPUP (the Clinical Practices of the University of Pennsylvania).

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Benefit_Base for employees whose data is updated from Workday will be null.]

The birth date of the employee.

Following the implementation of Workday in July 2019, this column is updated with Birth_Date from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Indexed - yes
Format - char (4)
May be null? yes

The 4-digit intramural mail code associated with the location where the employee receives intramural mail. This is the University mail code. Note: This is not necessarily the same as the U.S. Postal Service zip-plus-four extension.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Campus_Mail_Code for employees whose data is updated from Workday will be null.]

Values:

Refer to the DWADMIN.MAIL_CODES table for values.

COUNTRY_OF_CITIZENSHIP

Indexed - yes
Format - char (2)
May be null? yes

Examples: JA (Japan), AC (Antigua and Barbuda)

Following the implementation of Workday in July 2019, this column is updated with the 2 character country of citizenship from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Values:

Refer to the DWADMIN.COUNTRY_CODES table for values.

Indicates (with Y) whether employee is part of the Clinical Practices of the University of Pennsylvania (CPUP). Note that this indicator is manually set by CPUP benefits office, is not cross-validated with job class information, and data entry may lag for new employees.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of CPUP_Benefits_Indicator for employees whose data is updated from Workday will be null.]

Values:

Y     Employee is part of CPUP
N     Employee is not part of CPUP

Indicates whether the person has a current CPUP job class.

Following the implementation of Workday in July 2019, this column is updated from Workday for faculty with a position in the Job Family of "CPUP", to support longitudinal and cross collection reporting.

For terminated employees, rows will remain in the table, and will no longer be updated. Before the implementation of Workday, this column was populated as follows:

Indicates (with Y/N) whether an employee has an current CPUP (grade CPU) job class, based on History Status = 'C' EMPLOYEE_JOB; the Appt_Begin_Date and Appt_End_Date are not considered in this logic.

Values:

Y     Employee has a current CPUP job
N     Employee does not have a current CPUP job

Indicates (with Y/N) whether there are any current Payroll distributions for the employee. The indicator is recalculated nightly, and inspects each distribution start and end date relative to the date on which the nightly jobstream began. The logic inspects each distribution with a History Status of 'C', for a job with History Status of 'C'.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Current_Dist_Indicator for employees whose data is updated from Workday will be null.]

Values:

Y     Employee has a current distribution
N     Employee does not have a current
      distribution

Indicates (with Y/N) whether there are any current Payroll jobs for the employee. The indicator is recalculated nightly, and appointment begin and end date relative to the date on which the nightly jobstream began.

Following the implementation of Workday in July 2019, this column is updated from Workday based on the existence of a current position for the worker, to support longitudinal and cross collection reporting.

Before the implementation of Workday, this column was populated based on inspection of each job with a History Status of 'C'.

Values:

Y     Employee has a current job
N     Employee does not have a current job

Indicates the disability status, if any, for the employee. Values in this column will only be displayed to individuals with access to disability information; all other users will retrieve nulls in this column.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Disability_Status for employees whose data is updated from Workday will be null. Refer to the Disabled_Flag in HCM_PERSON_V for information about disability status in Workday.]

Values:
A        Ambulatory
C        Coordination
H        Hearing
L        Learning
M        Mental/Psychological
P        Speech
S        Sight
null        No disability status

Examples: C (High School diploma or equivalent), G (Bachelor's Degree).

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Education_Level for employees whose data is updated from Workday will be null. Refer to the HCM_PERSON_EDUCATION table for information about worker education details in Workday.]

Values:

B     No academic credentials
C     High School diploma or equivalent
D     Trade certificate
E     Some college
F     Associate Degree
G     Bachelor's Degree
H     Master's Degree
I     Medical Doctorate (M.D., D.D.S., 
      D.V.M., V.M.D.)
J     Other doctorate (Dr of Educ.,
      Dr of Sct., LL.D.)
K     Doctor of Philosophy (Ph.D.)
L     Other

The year in which the employee obtained the Education_Level. See also EMPLOYEE / Education_Level.

Example: 1982.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Education_Level_Year for employees whose data is updated from Workday will be null. Refer to the HCM_PERSON_EDUCATION table for information about worker education details in Workday.]

Indexed - no
Format - char (60)
May be null? yes

Examples: DOE@ISC.UPENN.EDU; doe@sas.upenn.edu

EMERGENCY_CONTACT

Indexed - no
Format - char (30)
May be null? yes

Examples: ANN SMITH, DR & MRS JOHN DOE

Following the implementation of Workday in July 2019, this column is updated with preferred emergency contact information from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Example: 2156661111

Following the implementation of Workday in July 2019, this column is updated with preferred emergency contact phone number from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Indexed - no
Format - char (8)
May be null? yes

Example: HUSBAND, WIFE, MOTHER

Following the implementation of Workday in July 2019, this column is updated with preferred emergency contact relationship from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Indexed - no
Format - date (7)
May be null? yes

The employee's most recent date of hire by the home department. Example: Jane Doe is hired on January 1, 1989; therefore the Employment_Date is initially entered as 01/01/89. Jane Doe is terminated from the University of Pennsylvania on January 2, 1996, but is rehired one year later on January 2, 1997. The Employment_Date for Jane Doe is now January 2, 1997. In the case that an employee holds more than one job, the employment date is still controlled by the home department.

Following the implementation of Workday in July 2019, this column is updated with Hire_Date from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Indexed - no
Format - char (1)
May be null? yes

A 1-character code identifying the employee's current employment relationship with the University of Pennsylvania.

Following the implementation of Workday in July 2019, this column is updated based on the Employee_Status, Terminated, and On_Leave_Flag in HCM_PERSON_V to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated. Values are determined as follows: when Terminated = 1 then 'T'; when On_Leave_Flag=1 then 'L', otherwise when Employee_Status = 1 then 'A'.

A value of 'X' for Employment_Status denotes records for employees whose SSN has been changed in the legacy PennWorks or Payroll systems; records with an Employment_Status of X will contain incorrect values for SSN.

Values:

A     Active.  Eligible for benefits 
      within certain employee categories.

L     Leave of Absence Without Pay.  
      Benefits are suspended.  Employee 
      must arrange with the Benefits Office
      to pay for or waive benefits.

P     Leave of Absence with Pay.  Eligible
      for benefits.

T     Separated or Terminated.  No longer 
      eligible for University-paid benefits.

X     Indicates a cross-reference record.  
      This is automatically entered on the
      record with the old Social Security Number
      when HRIM/Records completes a Social
      Security Number change.

Indexed - no
Format - date (7)
May be null? yes

The date the employee's employment status went into effect.

Following the implementation of Workday in July 2019, this column is updated based on the Employee_Status, Terminated, and On_Leave_Flag in HCM_PERSON_V to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated. Values are determined as follows: when Terminated = 1 then Termination_Date is used; when On_Leave_Flag=1 then First_Day_of_Leave is used, otherwise when Employee_Status = 1 then Hire_Date is used.

Indexed - no
Format - varchar2 (1)
May be null? yes

Indicates whether the individual is an exempt or non-exempt employee.

Following the implementation of Workday in July 2019, this column is updated based on the Pay_Group of the worker's primary position to support longitudinal and cross collection reporting. Values are determined as follows: when Pay_Group = 'Weekly' then 'N'; when Pay_Group is 'Monthly' or 'Academic' then 'E'. For terminated employees, rows will remain in the table, and will no longer be updated.

Values:
E     Exempt  
N     Non-exempt

Indexed - yes
Format - varchar2 (30)
May be null? yes

The employee's legal first name, in uppercase.

Following the implementation of Workday in July 2019, this column is updated with Legal_First_Name from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Indexed - no
Format - char (1)
May be null? yes

A 1-character code indicating the salary status of the employee.

Following the implementation of Workday in July 2019, this column is updated based on a combination of fields to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated. Values for updates from Workday are determined as follows:

• If HCM_PERSON_V.Retiree_Flag = 1 then 'R'
• If HCM_PERSON_LEAVE_OF_ABSENCE.Leave_Type_ID = 'Disability->Long-term Disability' Then 'L' (indicating Long Term Disability)
• If Leave_Type_ID = 'Disability->Workers_Compensation' Then 'W' (indicating Workers Compensation)
• If HCM_PERSON_V.Employee_Type = 'Postdoctoral' then 'S'
• If Employee_Type = 'Temporary' then “T”
• If HCM_PERSON_V.Calculated_Total_FTE >= 87.5 then 'F'
• If Calculated_Total_FTE < 87.5 then 'P'

Indexed - yes
Format - char (5)
May be null? yes

Example: 17101 (Data Administration)

Values:

Refer to the DWADMIN.ORG_OLD_TO_NEW table for values.

Indexed - yes
Format - char (4)
May be null? yes

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)

Following the implementation of Workday in July 2019, this column is updated with Pri_Penn_Cost_Center from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated and values for Home_Dept_ORG may be null, as the person no longer occupies a positon.

Values:

Refer to the DWADMIN.ORG_CODES table for values.

Indexed - yes
Format - char (2)
May be null? yes

Example: 54 (School of Medicine)

Values:

Refer to the DWADMIN.ORG_OLD_TO_NEW table for values.

Indexed - yes
Format - char (2)
May be null? yes

Example: 40 (School of Medicine)

Following the implementation of Workday in July 2019, this column is updated with Pri_Penn_Sch_Center from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated, and values for Home_School_Center may be null, as the person no longer occupies a positon.

Values:

Refer to the DWADMIN.ORG_CODES table, for values where 
Home_School_Ctr = Center_Code.

Indexed - no
Format - date (7)
May be null? yes

The date of the last personnel action performed in the online Payroll system for the employee. Updates made via the batch cycle will not be reflected in this column.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Last_Action_Date for employees whose data is updated from Workday will be null.]

Indexed - no
Format - date (7)
May be null? yes

The date the EMPLOYEE record was extracted from the Payroll system and loaded into the Warehouse.

Following the implementation of Workday in July 2019, this column will be updated when information for current employees is loaded to the Warehouse. For terminated employees, rows will remain in the table, and will no longer be updated.

Indexed - yes
Format - varchar2 (30)
May be null? yes

The employee's legal last name, in uppercase.

Following the implementation of Workday in July 2019, this column is updated with Legal_Last_Name from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Indexed - no
Format - date (7)
May be null? yes

The date the employee last received pay or payroll processing dealing with benefits.

Following the implementation of Workday in July 2019, this column is updated with Last_Payment_Date from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Indexed - no
Format - char (2)
May be null? yes

Identifies the type of the last update made via the online Payroll system to an employee record (e.g., 01 INITIAL EMPLOYMNT).

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Last_Personnel_Action for employees whose data is updated from Workday will be null.]

Values:
Refer to the DWPAY.PAYROLL_ACTION_CODES table for values.

Indexed - no
Format - char (2)
May be null? yes

Example: 01 (Disability - Worker's Compensation only)

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Leave_Reason for employees whose data is updated from Workday will be null. Refer to the HCM_PERSON_LEAVE_OF_ABSENCE table for information about leave status in Workday.]

Values:
Refer to the DWCOMP.COMP_LEAVE_REASON_LIST table for values.

Indexed - no
Format - date (7)
May be null? yes

For an employee on leave of absence from work, the date of the first of the month when the employee expects to return to work.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Leave_Return_Date for employees whose data is updated from Workday will be null. Refer to the HCM_PERSON_LEAVE_OF_ABSENCE table for information about leave status in Workday.]

Indexed - no
Format - char (1)
May be null? yes

The 1-character code that indicates the employee's marital status.

Following the implementation of Workday in July 2019, this column is updated with Marital_Status from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Values:
S     Single
M     Married
D     Divorced
W     Widow or widower

Indexed - yes
Format - varchar2 (30)
May be null? yes

The employee's legal middle name, in uppercase.

Following the implementation of Workday in July 2019, this column is updated with Legal_Middle_Name from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Indicates the military (Veteran) status, if any, for the employee. Values in this column will only be displayed to individuals with access to military status information; all other users will retrieve nulls in this column.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Military_Status for employees whose data is updated from Workday will be null. Refer to the HCM_PERSON_V table for information about veteran-related data.]

Values:
Refer to the DWCOMP.COMP_MILITARY_LIST table for values.

Indexed - no
Format - varchar2(2)
May be null? yes

An indicator that indicates that the employee record is complete.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Minimum_Record for employees whose data is updated from Workday will be null.]

Values:
NO   Indicates that insufficient data has been 
     entered by the user. The employee will not 
     be paid.
TX   Necessary forms have not been received by 
     HRIM/Records office. The employee will not 
     be paid.
OK   Minimum record is satisfied, all necessary 
     forms were submitted and approved, and the 
     employee can be paid.

Indexed - yes
Format - char (30)
May be null? yes

The employee's full legal name, in uppercase, in the format: LASTNAME,FIRSTNAME MIDDLEINITIAL (Note that only a comma separates the last name from the first name. Blank space is not used in the separator.) This is the name used for Federal W-2 forms, for example. (See also Name_Flipped and Professional names.)

Following the implementation of Workday in July 2019, this column is updated with Legal_Name from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Examples: SMITH,JOHN A; SHERWOOD-FOREST,CORKIE S

Indexed - no
Format - char (30)
May be null? yes

The employee's full legal name, in uppercase, in the format: FIRSTNAME MIDDLEINITIAL LASTNAME. This is the name used for Federal W-2 forms, for example. (See also Professional_Name_Flipped, Name, Name_Prefix, and Name_Suffix.)

Following the implementation of Workday in July 2019, this column is updated with Legal_Name_Flipped from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Examples: JOHN A SMITH; CORKIE S SHERWOOD-FOREST

Indexed - no
Format - char (4)
May be null? yes

The optional title, entered without punctuation and in uppercase letters, used before the employee's name. (See also Name_Flipped and Name_Suffix.)

Following the implementation of Workday in July 2019, this column is updated with Legal_Name_Title from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Examples: MISS, MRS, MS, MR, DR

Indexed - no
Format - char (4)
May be null? yes

The modifier (if any) at the end of the employee's name. Name_Suffix is entered without any punctuation and in uppercase letters. (See also Name_Flipped and Name_Prefix.)

Following the implementation of Workday in July 2019, this column is updated with Legal_Name_Suffix from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Examples: JR, SR, III, ESQ, PHD

Indexed - no
Format - date (7)
May be null? yes

The date of the employee's next performance review.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Next_Salary_Review_Date for employees whose data is updated from Workday will be null.]

Indexed - no
Format - date (7)
May be null? yes

The employee's first date of hire with the University of Pennsylvania. This date can be the same as, or earlier than, the Employment_Date. Example: Jane Doe became a student worker on February 1, 1996. On January 1, 1997, she became a full-time Business Administrator; therefore, Jane Doe's Original_Hire_Date is February 1, 1996 and her Employment_Date is January 1, 1997. Once the Original_Hire_Date is entered, only the Benefits Office can change it (For example, it might be changed in order to bridge service. Bridging is the process by which periods of University service are joined).

Following the implementation of Workday in July 2019, this column is updated with Original_Hire_Date from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Indexed - no
Format - varchar2 (1)
May be null? yes

Indicates the pay status (hourly or salaried) for the employee.

Following the implementation of Workday in July 2019, this column is updated based on the Pay_Rate_Type of the worker's primary position to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Values:
H     Hourly  
S     Salaried

Indexed - no
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.

Indexed - no
Format - varchar2 (24)
May be null? yes

Indexed - yes
Format - char (9)
May be null? yes

The 9-character previous Social Security Number of the employee. If an employee record has been entered in the Payroll system with a temporary or incorrect Social Security Number, the HRIM/Records office can change/correct it by entering a new record for the employee. The new record will contain the correct Social Security Number as the value for SSN and the temporary or incorrect Social Security Number as the value for Previous_SSN. The old record (which will have the Employment_Status set to "X") will have the temporary or incorrect Social Security Number as the value for SSN, and the correct Social Security Number as the value for Previous_SSN. The SSN correction is made to all tables containing the employee's SSN; the temporary or incorrect value will appear only in this Previous_SSN column. (See also SSN.)

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.

Indexed - no
Format - date (7)
May be null? yes

The date of the beginning of the employee's latest appointment to the position listed as the primary academic appointment.

Following the implementation of Workday in July 2019, this column is updated based on the Acad_Appt_Start_Date of the worker's primary academic appointment to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

The logic used to determine an employee's primary academic appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Indexed - no
Format - date (7)
May be null? yes

Following the implementation of Workday in July 2019, this column is updated based on the Acad_Appt_End_Date of the worker's primary academic appointment to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

The logic used to determine an employee's primary academic appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Example: 226010 (Associate Professor C-E)

Following the implementation of Workday in July 2019, this column is updated based on the Job_Profile_ID of the worker's primary academic appointment to support longitudinal and cross collection reporting. This field is only populated for workers with a position linked to the appointment.  The value will be null for academic affiliates or for workers whose appointment is not associated with a position.

The logic used to determine an employee's primary academic appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Values:
Refer to the DWADMIN.JOB_CLASS or DWADMIN.JOB_CLASS_GENERAL
 table for values.

PRI_ACAD_APPT_SALARY

Indexed - no
Format - number (9,2)
May be null? yes

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Pri_Acad_Appt_Salary for employees whose data is updated from Workday will be null. Refer to the HCM_POSITION_COMPENSATION table for more information on salary plans associated with positions.]

The logic used to determine an employee's primary academic appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Values:

0 - 9,999,999.99

Indexed - yes
Format - char (4)
May be null? yes

Example: 1306 (Mechanical Engineering and Applied Mechanics)

Following the implementation of Workday in July 2019, this column is updated based on the Pri_Penn_AU_Cost_Center of the worker's primary academic appointment to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

The logic used to determine an employee's primary academic appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Values:

Refer to the DWADMIN.ORG_CODES table for values.

PRI_ACAD_JCLS_ENT_DATE

Indexed - no
Format - date (7)
May be null? yes

The date the employee started working in the track of the primary academic appointment. (This may differ from the Pri_Acad_Appt_Begin_Date because that date reflects the start of the latest appointment to the primary job.)

Following the implementation of Workday in July 2019, this column is updated based on the Track_Start_Date of the worker's primary academic appointment to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

The logic used to determine an employee's primary academic appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

PRI_ACAD_JOB_LINK_ID

Indexed - yes
Format - number (9,0)
May be null? yes

The unique sequence number that identifies the employee's primary academic appointment in the EMPLOYEE_JOB table.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Pri_Acad_Job_Link_ID for employees whose data is updated from Workday will be null.]

The logic used to determine an employee's primary academic appointment is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

The 7-digit number that identifies the employee's primary academic position at the University of Pennsylvania. A position is an assignment of a person to perform a specific job in a specific organization that is supported by specific funding source(s). Over time, the person, job classification, organization, and funding sources associated with a position may change. As of this writing (November, 2001), faculty, temporary workers, and student workers do not have a number. In instances where no number is available, the element Primary_Univ_Position_Number will be zero.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Pri_Acad_Univ_Pos_No for employees whose data is updated from Workday will be null.]

The logic used to determine an employee's primary academic appointment is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Indexed - no
Format - date (7)
May be null? yes

The date of the beginning of the employee's latest appointment to the position listed as the primary appointment.

Following the implementation of Workday in July 2019, this column is updated based on the Curr_Position_Filled_Eff_Date of the worker's primary position to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

The logic used to determine an employee's primary appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Indexed - no
Format - date (7)
May be null? yes

The date of the end of the employee's appointment to the position listed as the primary appointment. Note: If there is no definite end date, Primary_Appt_End_Date will default to the latest available date in the Warehouse, which is 12/31/9999 (while the default for appointments with no end dates is actually stored in Payroll as 9999/99/99).

Following the implementation of Workday in July 2019, this column is updated based on the Position_Vacated_Date of the worker's primary position to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

The logic used to determine an employee's primary appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Example: 226010 (Associate Professor C-E)

Following the implementation of Workday in July 2019, this column is updated based on the Job_Profile_ID of the worker's primary position to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

The logic used to determine an employee's primary appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Values:
Refer to the DWADMIN.JOB_CLASS or DWADMIN.JOB_CLASS_GENERAL
 table for values.

PRIMARY_APPT_SALARY

Indexed - no
Format - number (9,2)
May be null? yes

The estimated annual amount that the employee will be paid for the primary job appointment.

Following the implementation of Workday in July 2019, this column is updated to support longitudinal and cross collection reporting as follows: For individuals whose primary position Pay_Rate_Type = 'Salary', the Total_Base_Amount of the worker's primary position is used. For Hourly workers (Pay_Rate_Type of the primary positon = 'Hourly'), the Primary Appt Salary = Hourly_Rate * Default_Weekly_Hours * 52. For terminated employees, rows will remain in the table, and will no longer be updated.

Prior to the implementation of Workday, the Primary_Appt_Salary was determined as follows:

The value be 0 or null for Positive Paid employees. (For Positive Paid employees, the time worked during the pay period must be input before the employee is paid.) If the employee is monthly paid (pay cycle = M1 or M2) or salaried weekly (pay cycle = W1 and appointment employee type = 2), the Primary_Appt_Salary is the annual salary (entered on Payroll Screen 004). This figure is approximately correct, but may vary from the actual encumbered amount as Primary_Appt_Salary is not calculated to the level of distributions for the fiscal year. If the employee is hourly paid (pay cycle = W1 and appointment employee type = 3 or 5), the Primary_Appt_Salary is one of the following:

If hours = 0 and % full-time = 0, Then Primary_Appt_Salary = 0 (No data to form an opinion)

If hours = 0 and % full-time > 0, Then Primary_Appt_Salary = hourly rate * 35 * % full-time * 52

(When no hours are available, but % full-time is available, assume 35 hours a week, 52 weeks a year.)

If hours > 0 and hours < 35, Then Primary_Appt_Salary = hourly rate * hours * 52

(Ignore % full-time, base calculation on hours, and assume 52 weeks a year.)

If hours >= 35 and % full-time > 0, Then Primary_Appt_Salary = hourly rate * hours & % full-time * 52

(Use all available fields in calculation and assume 52 weeks a year.)

If hours >= 35 and % full-time = 0, Then Primary_Appt_Salary = hourly rate * hours * 52.

(When % full-time is not available, use hours and assume 52 weeks a year.)

For employees who do not meet any of the above criteria, the last method is used to calculate their Primary_Appt_Salary.

This method of calculation does not consider the week-by-week changes that might be made in actual payments; it is simply a rough estimate using the best data available.

The employee's primary job appointment is determined before the Primary_Appt_Salary is calculated. The calculation logic involves some data scrubbing, in part because of the various ways of implementing part-time status. For example, someone who is working half-time could have the number of hours set to 20 and have % full-time set to 50. If a workaround such as the above were not devised (for example, giving precedence to the number of hours), an employee would show a 25% salary rather than a 50% salary.

There may still be glitches in the data. For example, some employees may have % full-time expressed as a decimal value (say, 50% entered on Payroll System Screen 004 as 00.50, which is 0.50%). There is no way to challenge data entered at this level. Any absurd values for Primary_Appt_Salary are probably due to glitches in the data.

The logic used to determine an employee's primary appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Values:

0 - 9,999,999.99

Example: 17101 (Data Administration)

The logic used to determine an employee's primary appointment is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html..

Values:

Refer to the DWADMIN.ORG_OLD_TO_NEW table for values.

Indexed - yes
Format - char (4)
May be null? yes

Example: 9120 (Data Administration)

Following the implementation of Workday in July 2019, this column is updated with Pri_Penn_Cost_Center from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

The logic used to determine an employee's primary appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Values:

Refer to the DWADMIN.ORG_CODES table for values.

PRIMARY_JOB_CLASS_ENTRY_DATE

Indexed - no
Format - date (7)
May be null? yes

The date the employee started working in the position listed as the primary appointment. (This may differ from the Primary_Appt_Begin_Date because that date reflects the start of the latest appointment to the primary job.)

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Primary_Job_Class_Entry_Date for employees whose data is updated from Workday will be null.]

The logic used to determine an employee's primary appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

PRIMARY_JOB_LINK_ID

Indexed - yes
Format - number (9,0)
May be null? yes

The unique sequence number that identifies the employee's primary appointment in the EMPLOYEE_JOB table.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Primary_Job_Link_ID for employees whose data is updated from Workday will be null.]

The logic used to determine an employee's primary appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Indexed - yes
Format - char (2)
May be null? yes

Example: 40 (School of Medicine)

Following the implementation of Workday in July 2019, this column is updated with Pri_Penn_Sch_Center from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Values:
Refer to the DWADMIN.ORG_CODES table, for values where 
Home_School_Ctr = Center_Code.

The 7-digit number that identifies the employee's primary position at the University of Pennsylvania. A position is an assignment of a person to perform a specific job in a specific organization that is supported by specific funding source(s). Over time, the person, job classification, organization, and funding sources associated with a position may change. As of this writing (August, 1999), faculty, temporary workers, and student workers do not have a number. In instances where no number is available, the element Primary_Univ_Position_Number will be zero.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Primary_Univ_Position_Number for employees whose data is updated from Workday will be null.]

The logic used to determine an employee's primary appointment prior to the implementation of Workday is documented in the cautions for this table, at https://provider.www.upenn.edu/computing/da/dw/salmgt/employee.t.html.

Indexed - no
Format - date (7)
May be null? yes

The next to last date the employee received pay or payroll processing dealing with benefits.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Prior_Pay_Date for employees whose data is updated from Workday will be null.]

The name used by the employee for professional purposes (for example, in directories). The value will default to that of the Name column, unless another value has been designated. The name is stored in uppercase in the format: LASTNAME,FIRSTNAME MIDDLEINITIAL (Note that only a comma separates the last name from the first name; blank space is not used in the separator.) (See also Name and Professional_Name_Flipped.)

Following the implementation of Workday in July 2019, this column is updated with Preferred_Name from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

During the time in service of the PennWorks system, Professional name fields were entered into PennWorks and fed nightly from there to the DWCOMP.COMP_PERSON table, and then on to the EMPLOYEE table.

Examples: SMITH,JOHN A; SHERWOOD-FOREST,CORKIE S

Indexed - no
Format - char (30)
May be null? yes

The name used by the employee for professional purposes (for example, in directories). The value will default to that of the Name_Flipped column, unless another value has been designated. The name is stored in uppercase, in the format: FIRSTNAME MIDDLEINITIAL LASTNAME. (See also Professional_Name, Professional_Name_Prefix, Professional_Name_Suffix and Name_Flipped.)

Following the implementation of Workday in July 2019, this column is updated with Preferred_Name_Flipped from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

During the time in service of the PennWorks system, Professional name fields were entered into PennWorks and fed nightly from there to the DWCOMP.COMP_PERSON table, and then on to the EMPLOYEE table.

Examples: JOHN A SMITH, CORKIE S SHERWOOD-FOREST

PROFESSIONAL_NAME_PREFIX

Indexed - no
Format - char (4)
May be null? yes

Optional title used before the employee's professional name. Professional_Name_Prefix is entered without any punctuation and in uppercase letters. (See also Professional_Name_Flipped and Professional_Name_Suffix.)

Following the implementation of Workday in July 2019, this column is updated with Preferred_Name_Title from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

During the time in service of the PennWorks system, Professional name fields were entered into PennWorks and fed nightly from there to the DWCOMP.COMP_PERSON table, and then on to the EMPLOYEE table.

Examples: DR, REV, HON

The modifier (if any) at the end of the employee's professional name. Professional_Name_Suffix is entered without any punctuation and in uppercase letters. (See also Professional_Name_Flipped and Professional_Name_Prefix.)

Following the implementation of Workday in July 2019, this column is updated with Preferred_Name_Suffix from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

During the time in service of the PennWorks system, Professional name fields were entered into PennWorks and fed nightly from there to the DWCOMP.COMP_PERSON table, and then on to the EMPLOYEE table.

Examples: ESQ, PHD, MD

Indexed - no
Format - date (7)
May be null? yes

Indexed - no
Format - char (3)
May be null? yes

Example: K (Frankford)

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Publications_Mail_Code for employees whose data is updated from Workday will be null.]

Values:
Refer to the DWCOMP.COMP_PUB_MAIL_CODE_LIST table for values.
      

Indexed - no
Format - char (1)
May be null? yes

The 1-character code that indicates whether an employee is employed on a regular or temporary basis. Regular employees include full-time, part-time, and limited service workers. Temporary employees include temporary, occasional, and student workers. T

Following the implementation of Workday in July 2019, this column is based on with Employee_Type from Workday to support longitudinal and cross collection reporting. Workers with Employee_Type of 'Temporary' will have a value of 'T', all others updated from Workday will have a value of 'R'. For terminated employees, rows will remain in the table, and will no longer be updated.

Values:

R     Regular
T     Temporary

Indexed - no
Format - date
May be null? yes

The employee's date of rehire to the University of Pennsylvania. This date can be the same as, or later than, the Original_Hire_Date and Employment_Date.

Following the implementation of Workday in July 2019, this column is updated based on the Employee_Status and Termination_Date in HCM_PERSON_V to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated. Values are determined as follows: when Employee_Status = 1 and Termination_Date is not null, Hire_Date is used; otherwise, the value will be null.

Indexed - no
Format - date (7)
May be null? yes

The date an employee enters a University position that is represented by a bargaining unit (union). This date corresponds to the Bargaining Unit indicator.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Seniority_Date for employees whose data is updated from Workday will be null.]

Indexed - no
Format - char (2)
May be null? yes

Example: 01 (Position discontinued), 31 (Early retirement)

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Separation_Reason for employees whose data is updated from Workday will be null. Refer to the Termination_Reason column in HCM_PERSON_V for information about termination reasons in Workday.]

Values:

Refer to the DWCOMP.COMP_SEPARATION_REASON_LIST 
table for values.
      

Indexed - no
Format - char (1)
May be null? yes

The 1-character code that indicates the gender of the employee. This data is used in compliance with Federal reporting regulations.

Following the implementation of Workday in July 2019, this column is updated with Gender from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Example: F (Female), M (Male)

Values:
Refer to the DWCOMP.COMP_GENDER_LIST table for values.

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 Administration.

Following the implementation of Workday in July 2019, this column is updated with SSN from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

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.

Indexed - yes
Format - char (4)
May be null? no

The last four digits of the 9-digit Social Security Number of the individual. A Social Security Number is a unique number assigned to an individual by the federal Social Security Administration.

Following the implementation of Workday in July 2019, this column is updated with SSN4 from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

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.

Indexed - no
Format - date (7)
May be null? yes

For faculty members, the date of the first of the month in which their tenure review period begins.

Following the implementation of Workday in July 2019, this column is updated based on the Track_Start_Date of the worker's primary academic appointment to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Prior to the implementation of Workday, Tenure related fields were maintained in the Faculty Information System (FIS) and fed nightly from there to the DWFAC.FIS_FACULTY table, and then on to the EMPLOYEE table.

Indexed - no
Format - char (1)
May be null? yes

For faculty members, the 1-character code that indicates their tenure status, as determined by the Provost Staff Conference.

Following the implementation of Workday in July 2019, this column is updated based on the Tenure_Status of the worker's primary academic appointment to support longitudinal and cross collection reporting. For individuals with a Tenure_Status of 'Tenured' the value will be '1'; for those with a value of 'Tenure Track' the value will be '5'. Other values are no longer used. For terminated employees, rows will remain in the table, and will no longer be updated.

Prior to the implementation of Workday, Tenure related fields were maintained in the Faculty Information System (FIS) and fed nightly from there to the DWFAC.FIS_FACULTY table, and then on to the EMPLOYEE table.

Values:

1     Tenure has been granted.

2     Restricted tenure has been granted.  Tenure
      is limited to a specific title or to the 
      duration of specific funding.

3     Under consideration for tenure.  The 
      individual is in the final stage of the tenure
      track, during which the final decision to 
      grant or deny tenure is made.

4     Tenure has been considered and denied.

5     In tenure probationary status.  Accruing 
      tenure status.

6     Probationary status in either the research 
      faculty or the Clinician-Educator track.  
      Subject to mandatory review.

7     Not in tenure probationary status.

8     Senior Clinician-Educator track faculty member
      no longer subject to mandatory review.

9     Senior research faculty member no longer 
      subject to mandatory review.

Indexed - no
Format - date (7)
May be null? yes

For faculty members, the date of the first of the month in which the Tenure_Status is expected or was attained. For Clinician-Educators, this information is used for tenure tracking.

Following the implementation of Workday in July 2019, this column is updated based on the Tenure_Award_Date of the worker's primary academic appointment to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Prior to the implementation of Workday, Tenure related fields were maintained in the Faculty Information System (FIS) and fed nightly from there to the DWFAC.FIS_FACULTY table, and then on to the EMPLOYEE table.

Indexed - no
Format - date (7)
May be null? yes

The date on which the employee's employment relationship with Penn ends. This can be a date in the future. (See also Separation_Reason.)

Following the implementation of Workday in July 2019, this column is updated with Termination_Date from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Indexed - no
Format - char (2)
May be null? yes

The 2-character code that indicates the type of visa held by an employee who is not a U.S. citizen.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Visa for employees whose data is updated from Workday will be null. Refer to the HCM_PERSON_VISA table for information about visa status in Workday.]

Values:
Refer to the DWCOMP.COMP_VISA_LIST table for values.

Indexed - no
Format - date (7)
May be null? yes

For employees who are not U.S. citizens, the date when the visa expires.

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Visa_Expiration_Date for employees whose data is updated from Workday will be null. Refer to the HCM_PERSON_VISA table for information about visa status in Workday.]

Indexed - no
Format - char (15)
May be null? yes

The 15-digit primary telephone number at which the employee can be reached during working hours. The area code is included.

Following the implementation of Workday in July 2019, this column is updated with Primary_Work_Phone from Workday to support longitudinal and cross collection reporting. For terminated employees, rows will remain in the table, and will no longer be updated.

Example: 2158987200

Indexed - no
Format - char (15)
May be null? yes

Example: 2158987171

[Following the retirement of PennWorks and the mainframe Personnel/Payroll system in July 2019, this column is no longer updated, and values of Work_Phone2 for employees whose data is updated from Workday will be null.]