• CAMPUS_MAIL_CODE
• CPUP_JOB_INDICATOR
• CURRENT_DIST_INDICATOR
• CURRENT_JOB_INDICATOR
• CURRENTLY_EMPLOYED
• EMAIL_ADDRESS
• EMPLOYMENT_DATE
• EMPLOYMENT_STATUS
• EMPLOYMENT_STATUS_DATE
• FIRST_NAME
• FULL_PART_TIME
• HOME_DEPARTMENT
• HOME_DEPT_ORG
• HOME_SCHOOL
• HOME_SCHOOL_CTR
• LAST_ACTION_DATE
• LAST_NAME
• LAST_PAY_PROCESSED_DATE
• LAST_PERSONNEL_ACTION
• LAST_EXTRACT_DATE
• MIDDLE_NAME
• MINIMUM_RECORD
• NAME
• NAME_FLIPPED
• NAME_PREFIX
• NAME_SUFFIX
• PENN_ID

• PENNKEY
• PREVIOUS_SSN
• PRI_ACAD_APPT_BEGIN_DATE
• PRI_ACAD_APPT_END_DATE
• PRI_ACAD_APPT_JOB_CLASS
• 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_DEPARTMENT
• PRIMARY_DEPT_ORG
• PRIMARY_JOB_CLASS_ENTRY_DATE
• PRIMARY_JOB_LINK_ID
• PRIMARY_SCHOOL_CTR
• PRIMARY_UNIV_POSITION_NUMBER
• PROFESSIONAL_NAME
• PROFESSIONAL_NAME_FLIPPED
• PROFESSIONAL_NAME_PREFIX
• PROFESSIONAL_NAME_SUFFIX
• REG_OR_TEMP
• REHIRE_DATE
• SSN
• SSN4
• TERMINATION_DATE

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.
      

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      

CURRENTLY_EMPLOYED

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

Values:

Y     Employee is currently employed by the University

N     Employee is no longer employed by the University

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

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

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

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

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_GENERAL 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). 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_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 - 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.

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

An indicator that indicates that the employee record is complete. Note: older records for employees who have been purged from Payroll may have null values 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 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 - no
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

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 - char (8)
May be null? yes

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

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_general.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_general.t.html.

The 6-digit job class code indicating the employee's primary academic appointment. Key to the job classification table where the job attributes are listed. To find the Job_Title associated with the Primary_Appt_Job_Class, join to the JOB_CLASS_GENERAL table using the Job_Class column.

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_general.t.html.

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

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

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_general.t.html.

PRI_ACAD_JOB_LINK_ID

Indexed - yes
Format - number (9,0)
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_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_general.t.html.

[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_general.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 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, athttps://provider.www.upenn.edu/computing/da/dw/salmgt/employee_general.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 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_general.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_general.t.html.

Values:

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

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

[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_general.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_general.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 
Primary_School_Ctr = Center_Code.
    

[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_general.t.html.

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.

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

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

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

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.

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.

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

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

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.