Connector name: Workday HCM

Additional details:

1. Payroll - Associates may work in multiple positions during a pay period, so our payroll data must support position-level reporting. While COST_CENTER_WORKTAG, JOB_PROFILE_WORKTAG, and LOCATION_WORKTAG provide the worked cost center, job profile, and location, we also require the following data elements:
1. Position for Global Payroll Result Line
2. Hours Worked – there are a couple of Hours fields in the Payroll Result Line Business Object that we would benefit from. Picture Attached.
3. Retro Period
4. Code Descriptions – PAYROLL_LINE_PAY_COMPONENT has earning and deduction codes, but we also need the description for these codes.
5. Business Object Value for Pay Group Detail
2. There are multiple places where FiveTran has ‘Reference ID’, but we need the ‘Business Object Value’ tied to the Reference ID for the data to be useful. The current workaround for this is to get each Reference ID – Business Object Value Mapping periodically through RaaS, which is not ideal.
1. Management Level Code in WORKER_POSITION, WORKER_POSITION_HISTORY, POSITION_JOB_PROFILE and CANDIDATE. There is a ‘management_level_descriptor’ in the first three tables, but it is null for all rows.
2. Primary_termination_reason in WORKER and WORKER_HISTORY. This one also has a descriptor field that has only null values.
3. Applicant_source_code in JOB_APPLIED_TO and CANDIDATE
4. Background_check_status in PRE_HIRE_BACKGROUND_CHECK_STATUS
5. Recruiting_disposition_code in JOB_APPLIED_TO
6. Possibly more fields that we haven’t discovered yet
3. Manager History of Worker - WORKER_POSITION_MANAGER gives the current snapshot but for predictive modelling purposes, we need to know manager details at a certain point of time going back 2-3 years.
4. Union History of Worker – there is union_code in JOB_PROFILE, but we have cases where a worker could be in a union Job Profile and technically not have a union membership.