Workday · Global data readiness
Getting HCM data ready across 60 countries.
Collection templates and country-specific validation gave HR teams a structured way to prepare HCM data for a global Workday program. The process made it easier to provide the data the conversion team needed.
- countries in scope
- 60
- for HR teams collecting data
- Less effort
What the project needed
The program covered 60 countries and needed a consistent way to collect HCM data while accounting for local requirements for names, addresses, contact details, and other fields. HR teams needed to know what to provide, and the conversion team needed a way to identify issues in what came back.
How data collection worked
EIB templates and Workday Web Services field definitions provided the structure for the collection workbooks. Country-specific rules accounted for local differences within that shared structure.
Validation and exception reports showed the team what needed attention during data preparation. The tooling also checked field dictionary versions and generated draft EIB files for conversion preparation.
-
Start with the definitions
Use EIB templates and Workday Web Services field definitions.
-
Build collection files
Generate workbooks for the project scope and country requirements.
-
Validate the data
Check the collected data against the relevant country rules.
-
Review & prepare
Report exceptions and generate draft EIB files.
A shared collection structure, with checks for local requirements.
What it meant for the project
The structured collection process cut down the time HR teams spent gathering data. The work covered 60 countries, with country-specific validation and exception reports supporting the team’s data preparation and review.
Tools & methods (5)
- Python
- Workday EIB
- Workday Web Services
- Excel collection workbooks
- Country-specific validation