Legacy-to-Workday Field Mapping (Illustrative Examples) 

 

EBS Legacy Field 

Legacy Logic 

Workday Field 

Functional Notes 

EMPLOYEE_TYPE 

Translation layer using csuh_empl_type2; based on p_people_group_id and status 

CF EEB Employee Type for ODS 

Preserves legacy codes (F, GA, SP, Etc..) using Job Family Group, Job Profile, and other attributes. 

ASSIGNMENT_NUMBER

Legacy format: <Employee_ID>-<Job #> 

CF CT Worker Employee ID_Position ID 

Combines Employee ID and Position ID to simulate legacy assignment number. 

ASG_START_DATE / ASG_END_DATE 

Used placeholder date 31-DEC-4712 for ongoing assignments 

CF ASG Start Date and default Position End Date Fields 

Workday uses effective-dated records; no placeholder dates like 31-DEC-4712. 

ASSIGNMENT_STATUS 

Granular statuses like Active, LWOP, Retirement, Emeritus 

CF EEB Position Assignment Status 

Reproduces legacy status using multiple Workday fields. 

EMPLOYMENT_STATUS 

Derived from assignment status and employee type; codes A/L/P/T 

CF EEB Employment Status Code 

Maintains A/L/P/T codes using assignment status and employee type logic. 

ASG_POSITION / TITLE 

Free-text titles and manually  

Position Object / Business Title 

Replaces legacy titles and versions with structured Workday position model. 

PER_HR_NUMBER / PIDM / NetID / CSU_ID 

PER_HR_NUMBER was the internal Oracle key; PIDM and NetID used for identity resolution and remain active. CSU_ID was used as a system-wide identifier. 

Employee_ID / WD Username (NetID) / Other IDs (PIDM, CSU_ID) 

Only PER_HR_NUMBER is retired. PIDM and NetID are stored in Workday as Other ID and Workday Username respectively; both remain active. CSU_ID becomes the Universal ID and is created in Banner and stored in Workday. 

Identification Field Information

 

  • Oracle’s ASSIGNMENT_ID (also referred to as ASSIGNMENT_NUMBER) is retired. In Workday, this is replaced by a calculated field that concatenates Employee_ID and Position_ID to form a unique assignment identifier.  

  • Position and title data are now sourced from Workday’s unified Position Object. Legacy fields like ASG_POSITION, EMPLOYEE_TITLE, TITLE3, and POSITION_VERSION are retired and replaced by structured Workday fields such as Business Title, Position ID, and effective-dated history. 

  • Identity fields. PIDM, NetID, and CSU_ID remain active and are stored in Workday as Other IDs. CSU_ID becomes the Universal ID, created in Banner and stored in Workday.  PER_HR_NUMBER, in regard to the Internal Oracle person ID, is retired.

Identifier

Legacy Source

In Workday

Authoritative System

Summary

PER_HR_NUMBER 

Oracle EBS internal key 

No 

ODS Crosswalk 

Retired. Legacy-only for audit and record matching. 

EMPLOYEE_ID 

EBS visible ID 

Yes 

Workday 

ID ranges: <200k FC, 200–299k Pueblo, ≥300k new hires. Not continuous.  

CSU_ID 

Banner / IAM 

Yes (Other ID, Universal_ID) 

Workday + IAM + Banner 

9-digit system-wide person ID. Primary CSU identifier. 

PIDM 

Banner internal key 

Yes (Other ID) 

Banner 

Source of CSU_ID. Used for joins and validation. 

NetID 

IAM 

Yes (Other ID) 

IAM (Midpoint) 

Derived from CSU_ID. Legacy NetIDs retained for login continuity.