This document contains entity-relationship diagrams and descriptions for tables related to employee, phone, address, and personal data. There are tables for phone data with two phone numbers per record, address data with one address per record, and linking tables to connect employees to multiple phone numbers and addresses. Additional tables include data on employee jobs, biographical information, and campus addresses.

1. Relationship connectors and their meanings
This indicates a one-to-zero-or-many relationship
This indicates a one-to-one relationship
This indicates a one-to-zero-or-one relationship
This indicates a one-to-one-or-many relationship
phone_data
PK,FK1 id INTEGER
PK phone_key TINYINT
phone1_intl VARCHAR(10)
phone1_area CHAR(3)
phone1_exch CHAR(3)
phone1_ext CHAR(4)
phone1_extension CHAR(5)
phone1_fmt VARCHAR(35)
phone2_intl VARCHAR(10)
phone2_area CHAR(3)
phone2_exch CHAR(3)
phone2_ext CHAR(4)
phone2_extension CHAR(5)
phone2_fmt VARCHAR(35)
start_date DATETIME
stop_date DATETIME
process_date DATETIME
address_data
PK id INTEGER
PK address_key TINYINT
line1 VARCHAR(30)
line2 VARCHAR(30)
city VARCHAR(20)
state CHAR(2)
zip CHAR(5)
zip_suffix CHAR(4)
country CHAR(3)
province VARCHAR(30)
foreign_zip VARCHAR(7)
start_date DATETIME
stop_date DATETIME
process_date DATETIME
phone_key
PK,FK1 id INTEGER
PK,FK1 phone_key TINYINT
PK,FK2 type CHAR(2)
process_date DATETIME
address_key
PK,FK1 id INTEGER
PK,FK1 address_key TINYINT
PK,FK2 type CHAR(1)
process_date DATETIME
phone_type
PK type CHAR(2)
type_tr VARCHAR(30)
campus_addr
PK,FK1 id INTEGER
I1 building CHAR(10)
room CHAR(6)
building2 CHAR(10)
room2 CHAR(6)
process_id INTEGER
process_date DATETIME
address_type
PK type CHAR(1)
type_tr VARCHAR(30)
typetypetypetype type_trtype_trtype_trtype_tr
1
2
3
C
E1
E2
F
Permanent Address
Mailing Address
Tax Residency Address
Campus
Emergency Contact 1
Emergency Contact 2
Fax
(actual data)
where type in
{1, 2, 3 }
min 1 → max 3
where type in
{1, 2, 3 }
min 1 → max 3
min 1 → max 7
min 1 → max 7
contains
contains7 rows
emp_master
PK,FK1 id INTEGER
chk_dist_no CHAR(4)
dir_title VARCHAR(40)
empl_status CHAR(1)
empl_date DATETIME
ft_pt_ind CHAR(1)
loa_type CHAR(1)
loa_begin DATE
loa_end DATETIME
loa_process_date DATETIME
home_dept CHAR(6)
last_pay DATETIME
pay_cycle CHAR(1)
relationship CHAR(1)
term_type CHAR(2)
termination DATETIME
union_code CHAR(2)
union_senior DATETIME
life_ins_bs FLOAT
life_bs_over CHAR(1)
life_ins_val FLOAT
annual_sal FLOAT
tenure_code CHAR(1)
tenure_date DATETIME
grant_elig CHAR(1)
remiss_elig CHAR(1)
ben_elig CHAR(1)
ben_elig_date DATETIME
plan_group CHAR(4)
dir_home_ph CHAR(1)
dir_hm_addr CHAR(1)
dir_home_ph2 CHAR(1)
rehire_flag CHAR(1)
flsa_ind CHAR(1)
jcc_code CHAR(4)
jcc_location CHAR(3)
work_location CHAR(3)
shadow_payroll_ind CHAR(1)
emp_type CHAR(2)
pay_currency CHAR(3)
intl_asn_begin DATETIME
intl_asn_end DATETIME
intl_asn_length CHAR(2)
sum_sal_1 CHAR(1)
sum_sal_2 CHAR(1)
sum_sal_3 CHAR(1)
program_code CHAR(2)
pay_company CHAR(5)
oracle_payroll_id TINYINT
process_date DATETIME
bio
PK id INTEGER
U1 ssn CHAR(9)
I1 last_name VARCHAR(30)
I1 first_name VARCHAR(20)
middle_name VARCHAR(20)
suffix VARCHAR(5)
title VARCHAR(5)
asuffix VARCHAR(10)
birthdate DATETIME
sex CHAR(1)
visa_type CHAR(3)
country_code CHAR(3)
visa_expdate DATETIME
us_entry_date DATETIME
tax_province CHAR(2)
race CHAR(1)
veteran CHAR(1)
handicapped CHAR(1)
computer_id VARCHAR(30)
andrew_id VARCHAR(12)
domain VARCHAR(15)
guid VARCHAR(36)
cmu_id CHAR(9)
process_date DATETIME
Person
HRIS ERD GROUP 01: EMPLOYEE, PHONE & ADDRESS
PREPARED BY
DANIEL L. REMLER, INGRES
APPROVED BYPROCESS
HRIS – ENTITY-RELATIONSHIP DIAGRAM
DATE
02/21/2008
DATE
CLIENT
CMU COMPUTING SERVICES 1 OF 2
PAGE