Appendix: Understanding Person Model Changes

This appendix discusses the changes to the core record structures for a Person, the Persons basic biographical data, and the relationships that the Person has with the organization. These record structures evolved in each of the releases from PeopleSoft 8.0 to PeopleSoft 8.9. Because the biggest changes occurred between PeopleSoft 8.0 and PeopleSoft 8.3 and between PeopleSoft 8.3 and PeopleSoft 8.9, these changes will be the focus of this appendix. The main goals of the changes were to: 1. Normalize the Person data structures as follows: o Remove the storing of a single address in 7 different tables. o Remove all redundant fields from PERSONAL_DATA. o Simplify the maintenance of names and addresses. 2. Separate the Person data structures into components by moving non-core data into distinct records. o This was done to minimize the amount of blank fields that had to be captured in a record. If a customer doesn't use a particular country, then no data has to be stored in those fields. o While this does increase the number of records in PERSONAL_DATA component, it allows us to separate the business logic and the processing. Eventually it will allow us to compartmentalize the actual component and only bring into the buffer the data that you need. o It also makes adding additional non-core fields easier to manage, as their addition will not break any usage of the core records. 3. Keep one ID for a person. This feature adds the ability to have a single ID for a Person regardless of how many different relationships to the organization that person has. This means that you no longer have to create a separate ID if someone was an employee and is now a contingent worker. 4. Allow a Person to be created without having to create JOB records. This change means that instead of having to create new EMPLIDs whenever a Person is both and Employee and a Non-employee, this model will allow a Person to have multiple organizational relationships. In addition, we are splitting the Non-employees into two categories: Contingent Workers and Persons of Interest. This allows us to be able to treat Employees and Contingent Workers as part of the workforce and the other Persons of Interest as not part of the workforce. The three organizational relationships that a Person can have are:
o o o

Employee (EMP) Contingent Worker (CWR) Person of Interest (POI)

Employees and Contingent Workers comprise the workforce and are required to have a JOB history. Persons of Interest might have a JOB record if certain products process them. POIs include Cobra Participants, Pension Payees, and Stock non-emps, Learning Solution Students needing a refund via NA Payroll, External Trainers, and External Students. Because processes are already built for these groupings that need information on the JOB record, those groups will need to have a JOB record. Currently, the only POI types that don't need a JOB record are the External Trainers and External Students (including the Applicants needing training prior to hire). The new model will allow a Person to be an Employee, a Contingent Worker, and/or a Person of Interest simultaneously or in succession using the same EMPLID. Each organizational relationship will be separated by EMPL_RCD meaning any one EMPL_RCD for a Person can only be for one organizational relationship history. But there is no intelligence in the actual EMPL_RCD number. The PeopleSoft 8.81 to 8.9 upgrade deals with creating the new structure that allows a single EMPLID to have more than one Relationship to the organization. In addition, the separation of the non-core data is finished. The main changes:

The upgrade process will not attempt to merge EMPLIDs. The current EMPL_RCDs assigned to an EMPLID will not change. No EMPL_RCDs will be deleted. Customers do not have to remove references to PERSONAL_DATA or EMPLOYMENT in their customized code.

Entity Relationship Diagrams

The following Entity Relationship Diagrams (ERDs) are designed to provide you with a visual representation of some of the key relationships Person records had in earlier PeopleSoft releases.

PeopleSoft 8.0 Diagram

The following ERD describes the interrelationships of the PERSONAL_DATA, PERS_DATA_EFFDT and other records where Addresses and Names are stored redundantly. Partial Entity Relationship Diagram for Person Data, Names, and Addresses.

PeopleSoft 8.3 and 8.8 Diagram

The following Entity Relationship Diagram shows the relationship of Core Records in Release 8.3 and 8.8.

Entity Relationship Diagram of the Core Records in PeopleSoft 8.3 and 8.8

PeopleSoft 8.9 Diagrams

Understanding PeopleSoft 8.9 Diagrams The following Entity Relationship Diagrams (ERDs) provide a visual representation of some of the key relationships the Person Object has with other records in PeopleSoft 8.9. Person Object Model The following Entity Relationship Diagram illustrates the Person Object Model, showing core requirements and optional core records as well as the type and number of extensions. Person Object Model ERD

Person and Organization Entities The following Entity Relationship Diagram shows the relationship between Person and Organizational Relationship entities. Person and Organizational Relationship ERD

While referencing the diagram above, keep in mind:

While EMPLOYMENT is replaced by a new record (PER_ORG_ASGN), this record maintains the same key structure that EMPLOYMENT had. EMPLOYMENT remains as a View returning most of the same information. The key structure of JOB, COMPENSATION, and so on, will not change A specific organizational relationship (Employee, Contingent Worker, POI) can be identified for each distinct EMPLID/EMPL_RCD. This relationship will never change for that ENPL_RCD. This is what allows us to keep the key structure of EMPLID, EMPL_RCD throughout the rest of the system without having to add an additional key for the PER_ORG. The PER_ORG_INST record is new, but it does represent a logical parent relationship that was already in the system. In order to keep the key structure of EMPLID and EMPL_RCD in tact for the rest of the system, we have created PER_ORG_INST as a

logical parent not a physical parent. The relationship is captured using the common ORG_INSTANCE_ERN field on PER_ORG_INST and PER_ORG_ASGN. Worker Entity The following illustrates the Worker entity relationships. Worker ERD

What Happens to PERSONAL_DATA While we are no longer using the PERSONAL_DATA record as a core transaction table, we are keeping it for reporting and batch. PeopleSoft added processes to keep the data up to date in realtime with changes made to PERSON, PERS_DATA_EFFDT, NAMES, ADDRESSES, and the Person Extension records.

There is a component post change PeopleCode that will capture changes made in real-time. There is an Application Engine that can be run nightly to capture the data that has just become effective and also captures any changes that happened during the previous day. Please refer to the Application Fundamentals for HRMS PeopleBook for more information. What Happens to EMPLOYMENT EMPLOYMENT is now a view that joins together the PER_ORG_ASGN, PER_ORG_INST, and current JOB row. It contains most of the same fields as the old EMPLOYMENT record and can still be used for reporting and online usage.

Record and Table Changes

This section discusses:

Record Changes Table Changes

Record Changes Record Changes from PeopleSoft 8.01 to 8.9 The following tables detail record changes from PeopleSoft 8.01 to 8.9: Fields deleted, added, moved Moved to PERSON Delete Delete Delete Delete Delete Move to PER_ORG_INST NAMES record created from PERS_DATA_EFFDT ADDRESSES record created from PERS_DATA_EFFDT ADDRESSES record created from PERS_DATA_EFFDT PERSONAL_PHONE created from PERS_DATA_EFFDT Replaced by PER_ORG_ASGN.PER_ORG

PERSONAL_DATA EMPLID NAMEGBL_NPC_SBR ADDRESS_SBR ADDR_OTR_SBR PHONE_SBR PER_STATUS ORIG_HIRE_DT

Conversion Rules

PERSONAL_DATA SEX AGE_STATUS MAR_STATUS BIRTHDATE BIRTHPLACE BIRTHCOUNTRY BIRTHSTATE DT_OF_DEATH HIGHEST_EDUC_LVL FT_STUDENT REFERRAL_SOURCE EMPL_REFERRAL_ID SPECIFIC_REFER_SRC HIGHLY_COMP_EMPL_P HIGHLY_COMP_EMPL_C RESUME_TEXT_FILE QDRO_IND_YN PER_TYPE

Fields deleted, added, moved Move to PERS_DATA_EFFDT Move to PERS_DATA_DEU Move to PERS_DATA_EFFDT Move to PERSON Move to PERSON Move to PERSON Move to PERSON Move to PERSON Move to PERS_DATA_EFFDT Move to PERS_DATA_EFFDT Move to PERS_APPL_INFO Move to PERS_APPL_INFO Move to PERS_APPL_INFO Move to BN_PERSON Move to BN_PERSON Move to PERS_DATA_APPL Deleted Move to PER_ORG_ASGN as

Conversion Rules

PERSONAL_DATA

Fields deleted, added, moved POI_TYPE

Conversion Rules

PERS_DTUSA_SBR PERS_DTCAN_SBR PERS_DTCHE_SBR PERS_DTGER_SBR PERS_DTFRA_SBR PERS_DTJPN_SBR PERS_DTUK_SBR PERS_DTITA_SBR PERS_DTESP_SBR LANG_CD YEARS_OF_EXP APPLID APP_DT ON_DM_EM_DOSAVENOW PERS_DTFED2_SBR

Move to PERS_DATA_USA Move to PERS_DATA_CAN Move to PERS_DATA_CHE Move to PERS_DATA_DEU Move to PERS_DATA_FRA Move to PERS_DATA_JPN Move to PERS_DATA_UK Move to PERS_DATA_ITA Move to PERS_DATA_ESP Move to PERS_DATA_EFFDT Move to PRIORWORK_SUM Move to PERS_APPL_INFO Move to PERS_APPL_INFO Delete Move to PERS_DATA_USF

PERSONAL_DATA ALTER_EMPLID ADDRESS1_AC ADDRESS2_AC ADDRESS3_AC CITY_AC

Fields deleted, added, moved Move to PERS_DATA_EFFDT Delete Delete Delete Delete

Conversion Rules

See PERS_DATA_EFFDT See PERS_DATA_EFFDT See PERS_DATA_EFFDT See PERS_DATA_EFFDT

PERS_DATA_EFFDT EMPLID EFFDT UPDATE_PERS_DATA ADDRESS_SBR ADDR_OTR_SBR MAR_STATUS SMOKER NAMEGBL_SBR ADDRESS1_AC ADDRESS2_AC ADDRESS3_AC CITY_AC

Fields deleted, added, moved

Conversion Rules

Delete Move to ADDRESSES Move to ADDRESSES As ADDRESS_TYPE = HOME As ADDRESS_TYPE = MAIL

Move to PERS_SMOKER Move to NAMES Move to ADDRESSES Move to ADDRESSES Move to ADDRESSES Move to ADDRESSES As NAME_TYPE = PRI As ADDRESS_TYPE = HOME As ADDRESS_TYPE = HOME As ADDRESS_TYPE = HOME As ADDRESS_TYPE = HOME

Record Changes for PeopleSoft 8.3x and 8.8x to 8.9 The PeopleSoft 8.8 x to 8.9 upgrade deals with creating the new structure that allows a single EMPLID to have more than one relationship to the organization. In addition splitting the non-

core data into components has been completed. Therefore the following will not be done during your upgrade:

The upgrade process will not attempt to merge EMPLIDs. The upgrade process will not assign the current EMPL_RCDs to an EMPLID change. No EMPL_RCDs will be deleted.

The upgrade converts EMPL_RCDs that are in EMPLOYMENT to PER_ORG_ASGN and PER_ORG_INST. All rows in EMPLOYEMNT will be moved to PER_ORG_ASGN. PER_ORG_INST will contain the relations hip between EMPL_RCDs in PER_ORG ASGN. Some EMPL_RCDs are considered Instances which actually creates a new employment instance. Others are additional assignments that the person may have over time but that should not be considered a hire action. See the reference below for more information on the differences between Instances and Assignments. See PeopleSoft Enterprise HCM Application Fundamentals 8.9 EMPL_RCDs that are Instances will also be in PER_ORG_INST. EMPL_RCDs that are true additional assignments will not be in PER_ORG_INST but will have a value in their PER_ORG_ASGN.ORG_INSTANCE_ERN that will connect them with an Instance. The following will occur during the upgrade:

EMPL_RCDs that were created with the HIR action will be created as separate Organizational Instances. EMPL_RCDs that were created with the ADL action will be created as additional assignments and will be related to an appropriate Instance. EMPL_RCDs that have Host assignments will be created as Instances. EMPL_RCDs that are Host assignments will be created as Assignments related to the HOME assignment. Japanese main appointments will be created as Instances. Japanese additional assignments will be created as assignments connect to the Main appointment.

If you want EMPL_RCDs that you created with the ADL action to be created as separate Instances, you should change that action to HIR in your source data prior to data conversion. PERSON PERSON EMPLID PER_STATUS Replaced by PER_ORG_ASGN.PER_ORG E = EMP N= See Chart 2 Upgrade Fields Deleted, Moved, Added Conversion Rules

PERSON

Fields Deleted, Moved, Added

Conversion Rules Conversion Chart below.

BIRTHDATE BIRTHPLACE BIRTHCOUNTRY BIRTHSTATE DT_OF_DEATH ORIG_HIRE_DT Moved to PER_ORG_INST Copied on each PER_ORG_INST row for a Person Only create a row where there is data in either field. Since HIGHLY_COMP_EMPL_P had a defaulted specified of N this should be treated as a blank value. Same as above Null

HIGHLY_COMP_EMPL_C

Moved to BN_PERSON

HIGLY_COMP_EMPL_P LAST_CHILD_UPDTTM PERS_DATA_EFFDT

Moved to BN_PERSON New field

PERS_DATA_EFFDT EMPLID EFFDT PER_TYPE MAR_STATUS MAR_STATUS_DT SEX AGE_STATUS

Fields Deleted, Added, Moved

Conversion Rules

Replaced by POI_TYPE

See Chart 2 below

Moved to

PERS_DATA_EFFDT

Fields Deleted, Added, Moved PERS_DATA_DEU

Conversion Rules

HIGHEST_EDUC_LVL FT_STUDENT LANG_CD LASTUPDDTTM LASTUPDOPRID YEARS_OF_EXP New field New field Moved to PRIORWORK_SUM Deleted In PERS_APPL_INFO Delete In PERS_APPL_INFO If the APPLID/APP_DT is not PERS_APPL_INFO already, insert of row See above %datetime PPLSOFT

APPLID

APP_DT ALTER_EMPLID BILINGUALISM_CODE HEALTH_CARE_NBR HEALTH_CARE_STATE GUARDIAN_CHE MILIT_SITUATN_ESP SOC_SEC_AFF_DT PERS_DTFED2_SBR ENTRY_DT_FRA MILIT_SITUATN_FRA CPAMID MILITARY_STAT_GER

PERS_DATA_CAN PERS_DATA_CAN PERS_DATA_CAN PERS_DATA_CHE PERS_DATA_ESP PERS_DATA_ESP PERS_DATA_USF PERS_DATA_FRA PERS_DATA_FRA PERS_DATA_FRA PERS_DATA_DEU

PERS_DATA_EFFDT EXPCTD_MILITARY_DT HR_RESPONSIBLE_ID MILITARY_STAT_ITA MILATRY_TYPE_ITA MILIATARY_RANK_ITA MILITARY_END_ITA HONSEKI_JPN US_WORK_ELIGIBILITY MILITARY_STATUS CITIZEN_PROOF1 CITIZEN_PROOF2 SMOKER MEDICARE_ENTLD_DT SMOKER_DT FP_ACTION_2 ACTION_REASON FP_ACTION_REQ FP_SUPDOC_REQ LAST_UPDATE_DATE NAMES

Fields Deleted, Added, Moved PERS_DATA_DEU PERS_DATA_DEU PERS_DATA_ITA PERS_DATA_ITA PERS_DATA_ITA PERS_DATA_ITA PERS_DATA_JPN PERS_DATA_USA PERS_DATA_USA PERS_DATA_USA PERS_DATA_USA PERS_SMOKER PERS_DATA_USA PERS_SMOKER PERS_DATA_FPS PERS_DATA_FPS PERS_DATA_FPS PERS_DATA_FPS PERS_DATA_FPS

Conversion Rules

NAMES EMPLID

Field Added

Conversion Rules

NAMES NAME_TYPE EFFDT COUNTRY_NM_FORMAT

Field Added

Conversion Rules

Prompt Table is now NAME_FORMAT_TBL. Some values will need to be set to a default format value. New field New field New field New field Casual formatted name which can be used on pages and reports. Formatting rules are based on the COUNTRY_NM_FORMAT. Formally formatted name which can be used for letters. Formatting rules are based on the COUNTRY_NM_FORMAT %datetime 'PPLSOFT'

NAME_DISPLAY

NAME_FORMAL

LASTUPDDTTM LASTUPDOPRID

PERSONAL_PHONE Field Added

PERSONAL_PHONE EMPLID PHONE_TYPE COUNTRY_CODE PHONE PREF_PHONE_FLAG

Conversion Rules

New field

Order used in the upgrade is HOME, BUSN, MAIN else first found.

EMAIL_ADDR EMAIL_ADDRESS EMPLID Field Added Conversion Rules

EMAIL_ADDRESS E_ADDR_TYPE EMAIL_ADDR PREF_EMAIL_FLAG EMPLOYMENT

Field Added

Conversion Rules

New field

Order is BUSN

EMPLOYMENT EMPLID EMPL_RCD BENEFIT_RCD_NBR HOME_HOST_CLASS HIRE_DT REHIRE_DT CMPNY_SENORITY_DT SERVICE_DT PROF_EXERIENCE_DT LAST_VERIFICATN_DT EXPECTED_RETURN_DT TERMINATION_DT LAST_DATE_WORKED LAST_INCREASE_DT OWN_5PERCENT_CO BUSINESS_TITLE

Replaced with a View based on new records Moved to PERS_ORG_ASGN Moved to PERS_ORG_ASGN Moved to PERS_ORG_ASGN Moved to PERS_ORG_ASGN Moved to JOB Moved to JOB as LST_HIRE_DT Data copied to PER_ORG_ASGN.SEN_PAY_DT_OVR and PER_ORG_ASGN.CMPNY_SENIORITY_DT Moved to PERS_ORG_ASGN Moved to PERS_ORG_ASGN Moved to PERS_ORG_ASGN Moved to JOB Moved to JOB Moved to JOB Moved to PERS_ORG_ASGN Moved to PERS_ORG_ASGN Moved to PERS_ORG_ASGN

Conversion Rules

EMPLOYMENT REPORTS_TO SUPERVISOR_ID PROBATION_DT SECURITY_CLEARANCE COUNTRY_CODE PHONE TIME_RPT_LOC JOB_REPORTING DED_TAKEN DED_SUBSET_ID GVT_SCD_RETIRE GVT_SCD_TSP GVT_SCD_LEO GVT_SCD_SEVPAY GVT_SECPAY_PRV_WRKS GVT_MAND_RET_DAT GVT_WGI_STATUS GVT_INTRM_DAYS_WGI GVT_NONPAY_NOA GVT_NONPAY_HRS_WGI GVT_NONPAY_HRS_SCD GVT_NONPAY_HRS_TNR

Replaced with a View based on new records Delete (was moved to JOB in PeopleSoft 8.0) Delete (was moved to JOB in PeopleSoft 8.0) Moved to PERS_ORG_ASGN Moved to PERS_ORG_ASGN Moved to PERS_ORG_ASGN Moved to PERS_ORG_ASGN as POSITION_PHONE Deleted not used Deleted not used Moved to DED_NA Moved to DED_NA Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF

Conversion Rules

EMPLOYMENT GVT_NONPAY_HRS_PRB GVT_TEMP_PRO_EXPIR GVT_TEMP_PSN_EXPIR GVT_DETAIL_EXPIRES GVT_SABBATIC_EXPIR GVT_RTND_GRADE_BEG GVT_RTND_GRADE_EXP GVT_NOA_CODE GVT_CURR_APT_AUTH1 GVT_CURR_APT_AUTH2 GVT_APPT_EXPIR_DT GVT_CNV_BEGIN_DATE GVT_CAREER_CNV_DUE GVT_CAREER_COND_DT GVT_APPT_LIMIT_HRS GVT_APPT_LIMIT_DYS GVT_APPT_LIMIT_AMT GVT_SUPV_PROB_DT GVT_SES_PROB_DT GVT_SEC_CLR_STATUS GVT_CLRNCE_STAT_DT GVT_ERN_PGM_PERM GVT_OCC_SERS_PERM

Replaced with a View based on new records Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF

Conversion Rules

EMPLOYMENT GVT_GRADE_PERM GVT_COMP_AREA_PERM GVT_COMPA_LVL_PERM GVT_CHANGE_FLAG GVT_SPEP GVT_WGI_DUE_DATE GVT_DT_LEI GVT_FIN_DISCLOSURE GVT_FIN_DISCL_DATE GVT_TENURE GVT_DETL_BARG_UNIT GVT_DETL_UNION_CD NEXT_REVIEW_DATE GVT_WELFARE_WK_CD TENURE_ACCR_FLG FTE_TENURE EG_GROUP FTE_FLX_SRVC CONTRACT_LENGTH APPOINT_END_DT NEE_PROVIDER_ID FA_PAY_PROGRAM FA_TYPE

Replaced with a View based on new records Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to PER_ORG_ASG_HP Moved to PER_ORG_ASG_HP Moved to PER_ORG_ASG_HP Moved to PER_ORG_ASG_HP Moved to PER_ORG_ASG_HP Moved to PER_ORG_ASG_HP Moved to PER_ORG_INST Moved to PER_ORG_ASG_FA Moved to PER_ORG_ASG_FA

Conversion Rules

EMPLOYMENT FA_ELIG_DT EDUC_LVVL_AD_BTD OFFICIAL_LANG RELAT_TO_OWNER_NLD INS_DAYS_BRA INS_MOTHS_BRA INS_YEARS_BRA JOB JOB EMPLID EMPL_RCD EFFDT EFFSEQ PER_ORG HR_STATUS GVT_EFFDT GVT_EFFDT_PROPOSED GVT_TRANS_NBR GVT_TRANS_NBR_SEQ GVT_WIP_STATUS GVT_STATUS_TYPE GVT_NOA_CODE

Replaced with a View based on new records Moved to PER_ORG_ASG_FA Moved to PER_ORG_ASG_JPN Moved to PER_ORG_ASG_BEL Moved to PER_ORG_ASG_NLD Moved to PER_ORG_ASG_BRA Moved to PER_ORG_ASG_BRA Moved to PER_ORG_ASG_BRA

Conversion Rules

Fields Added or Deleted

Conversion Rules

New New Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF

JOB GVT_LEG_AUTH_1 GVT_PAR_AUTH_D1 GVT_PAR_AUTH_D1_2 GVT_LEG_AUTH_2 GVT_PAR_AUTH_D2 GVT_PAR_AUTH_D2_2 GVT_PAR_NTE_DATE GVT_WORK_SCHED GVT_SUB_AGENCY GVT_ELIG_FEHB GVT_FEHB_DT GVT_PAY_RATE_DETER GVT_STEP GVT_RTND_PAY_PLAN GVT_RTND_SAL_PLAN GVT_RTND_GRADE GVT_RTND_STEP GVT_RTND_GVT_STEP GVT_PAY_BASIS GVT_COMPRATE GVT_LOCALITY_ADJ GVT_BIWEEKLY_RT GVT_DAILY_RT

Fields Added or Deleted Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF

Conversion Rules

JOB GVT_HRLY_RT_NO_LOC GVT_DLY_RT_NO_LOC GVT_BW_RT_NO_LOC GVT_MNLY_RT_NO_LOC GVT_ANNL_RT_NO_LOC GVT_XFER_FROM_AGCY GVT_XFER_TO_AGCY GVT_RETIRE_PLAN GVT_ANN_IND GVT_FEGLI GVT_FEGLI_LIVING GVT_LIVING_AMT GVT_ANNUITY_OFFESET GVT_CSRS_FROZN_SVC GVT_GREV_RET_COVRG GVT_FERS_COVERAGE GVT_TYPE_OF_APPT GVT_POI GVT_POSN_OCCUPIED GVT_CONT_EMPLID GVT_ROUTE_NEXT GVT_CHANGE_FLAG GVT_TSP_UPD_IND GVT_PI_UPD_IND

Fields Added or Deleted Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF

Conversion Rules

JOB GVT_SF52_NBR GVT_S113G_CEILING GVT_LEO_POSITION GVT_ANNUIT_COM_DT GVT_BASIC_LIFE_RED GVT_DED_PROPT_DT GVT_FEGLI_BASC_PCT GVT_FEGLI_OPT_PCT GVT_FEHB_PCT GVT_RETRO_FLAG GVT_RETRO_DED_FLAG GVT_RETRO_JOB_FLAG GVT_RETRO_BSE_FLAG GVT_OTH_PAY_CHG GVT_DETL_POSN_NBR ANNL_BEN_BASE_OVRD BENEFIT_PROGRAM UPDATE_PAYROLL GVT_PAY_PLAN GVT_PAY_FLAG GVT_NID_CHANGE WPP_STOP_FLAG SUPV_LVL_ID SETID_SUPV_LVL

Fields Added or Deleted Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF Moved to JOB_USF New Moved from JOB_JR Moved from JOB_JR

Conversion Rules

JOB ABSENCE_SYSTEM_FLG POI_TYPE AUTO_END_FLG HIRE_DT LAST_HIRE_DT TERMINATION_DT ASGN_START_DT LST_ASSGN_START_DT ASGN_END_DT LDW_OVR LAST_DATE_WORKED EXPECTED_RETURN_DT EXPECTED_END_DATE LASTUPDDTTM LASTUPDOPRID JOB_JR JOB_JR EMPLID EMPL_RCD EFFDT EFFSEQ CASUAL_IND New New

Fields Added or Deleted

Conversion Rules

Moved from JOB_JR Moved from EMPLOYMENT Moved from EMPLOYMENT Moved from EMPLOYMENT New New New New Moved from EMPLOYMENT Moved from EMPLOYMENT Moved from JOB_JR New New

Field Deleted, Added or Moved

Conversion Rules

Moved to JOB_AUS

JOB_JR SALARY_PACKAGED PAYROLL_STATE_AUS CLASSN_CURRENT_AUS WORK_SECTOR_AUS FUNCTION_AUS ANN_CNTACT_HRS_AUS TEACH_WEEKS_AUS CASUAL_TYPE_AUS TERM_TYPE_AUS TERM_LTD_AUS SUPV_LVL_ID EXPECTED_END_DATE AUTO_END_FLAG

Field Deleted, Added or Moved Moved to JOB_AUS Moved to JOB_AUS Moved to JOB_AUS Moved to JOB_AUS Moved to JOB_AUS Moved to JOB_AUS Moved to JOB_AUS Moved to JOB_AUS Moved to JOB_AUS Moved to JOB_AUS Moved to JOB Moved to JOB Moved to JOB

Conversion Rules

Chart 2 Upgrade Conversion Chart for PER_STATUS and PER_TYPE

If the PER_STATUS is N and there is no POI_TYPE, the employee will be loaded as a Contingent Worker.

Because of the previous model, it's assumed that all EMPLOYMENT records go with the PER_ORG based on the PER_STATUS. All EMPLOYMENT records belong to one PERSON_ORG. The one exception is for Pension Payees. If the Person has a PER_STATUS of E and the PER_TYPE of P then their last EMPL_RCD will be for their Pension data and should get a PER_ORG of POI. Since a Person can have different PERS_DATA_EFFDT.PER_TYPEs over time, it is possible for a person to have more than one row inserted into PER_ORG_ASGN. There are the PER_STATUS and PER_TYPEs that are added as system data. If you have added additional ones or if you are using the PER_TYPEs differently, you will need to determine which PER_ORG their values match to and modify your insert statements accordingly. If you are unsure, you can make the person a POI and change it later if needed.

Table Changes
PERSON Record PERSON is a new Record that serves as the parent to PERS_DATA_EFFDT, EMPLOYMENT, and all other records that used to use PERSONAL_DATA as the parent. The upgrade scripts will load this record with the information from PERSONAL_DATA. PERS_DATA_EFFDT Record The upgrade scripts will ensure that all PERS_DATA_EFFDT rows are updated with the data from PERSON for the fields moved from PERSONAL_DATA to PERS_DATA_EFFDT. NAMES This is the only source of Name data for a person in the record, PERSON. The upgrade scripts will ensure that a row is created in NAMES for any PERS_DATA_EFFDT row that had a name change for NAME_TYPE = PRI. The fields NAME_DISPLAY and NAME_FORMAL are new in this PeopleSoft release. To populate them, you must run the Application Engine process NAME_DISPLAY.. This process is called during data conversion. If the fields are not populated after data conversion you can run the Refresh Name Display Values process at any time. To run the Refresh Name Display Values process: Select Set Up HRMS, System Administration, Database Processes, Refresh Name Display Values.

To update all name formats check Update All Name Formats?. Otherwise, select a Name format Type. Be sure that the following checkboxes are selected:

Update NAMES record Update Dependants Update HS Non-Employees Update French Public Sector Update US Federal Names

ADDRESSES This is the only source of Address data for a person in the record, PERSON. The upgrade scripts will ensure that a row is created in ADDRESSES for any PERS_DATA_EFFDT row that had an address change for the ADDRESS_TYPE = HOME. The upgrade scripts will ensure that a row is created in ADDRESSES for any PERS_DATA_EFFDT row that had another address change for the ADDRESS_TYPE = MAIL. DEPENDENT_BENEF If the Address is the same as the employee's then the address data is not physically stored on the record, only the Address_type is. If the Address is not the same as the employee's, then the dependents address is directly stored on the record. If the Phone is the same as the employees, then the phone data is not physically stored on the record, only the PHONE_TYPE is. If the Phone is not the same as the employee's, then the dependents phone is directly stored on the record. There is now the ability to have the address be the same as the employees while the Phone is different. The Upgrade scripts will enter an Address_type of HOME and a Phone_Type of MAIN if the Same Address as Employee is Yes. The address and phone fields will then be cleared. No change will happen if the Same Address as Employee is No. EMERGENCY_CNTCT If the Address is the same as the employee's then the address data is not physically stored on the record, only the Address_type is. If the Address is not the same as the employee's, then the contacts address is directly stored on the record. If the Phone is the same as the employee's then the phone data is not physically stored on the record, only the PHONE_TYPE is. If the Phone is not the same as the employee's, then the contacts phone is directly stored on the record. There is now the ability to have the address be the same as the employees while the Phone is different.

The Upgrade scripts will enter an Address_type of HOME and a Phone_Type of MAIN if the Same Address as Employee is Yes. The address and phone fields will then be cleared. No change will happen if the Same Address as Employee is No. PAYROLL_DATA The Address fields were removed from PAYROLL_DATA. Any address used to send the paycheck or advice to must exist in ADDRESSES. However, the PAYROLL_DATA component allows the user to select the HOME or MAILING address or to enter a different CHECK address. The Upgrade scripts will create an ADDRESSES record with the data from PAYROLL_DATA with the appropriate ADDRESS_TYPE if this data does not exist in ADDRESSES. ABS_HIST_DET If the Address is the same as the employee's then the address data is not physically stored on the record, only the ADDRESS_TYPE is. If the Address is not the same as the employee's, then the address is directly stored on the record. The Upgrade scripts will enter an Address_type of HOME and a Phone_Type of MAIN if the Same Address as Employee is Yes. The address and phone fields will then be cleared. No change will happen if the Same Address as Employee is No. ADDRESS_TYPE This has been replaced by a table built from ADDRESSES. PERS_NAMES_TYPE This has been replaced by a table built from NAMES. New Views The following lists the new views that have been created. PERSON_NAME This view returns a Persons current Primary Name. One row per PERSON will always exist in this view. PERSON_ADDRESS This view returns a Persons current Address of each ADDRESS_TYPE. One row per Person per Address_type will exist in this view. Since Addresses are not required, this view will not return all People in PERSON.

PERSONAL_DT_FST This view is a combination of PERSON, current primary name from NAMES, and the current row from PERS_DATA_EFFDT. One row will exist for each person in PERSON.