PICOF Extract Fails With java.lang.ClassCastException When a Payee Cannot Be Included
What it means
During a PICOF (Payroll Interface Change Object Feed) run, one payee's data cannot be included in the extract, and instead of a clear business error, Workday surfaces a raw Java ClassCastException. This usually means the payee's underlying data does not match the type the interface expects for one of the fields being extracted, rather than a genuine software defect.
Troubleshooting
- Identify the specific payee flagged in the run's error detail (the ClassCastException reference is tied to one worker's record, not the whole extract) and open that worker's payroll interface preview in isolation.
- Check whether the payee has an unusual combination of data for the fields mapped in this interface, such as a compensation, tax, or additional-data element that is null, multi-valued, or of a different type than the rest of the population (for example, a field expecting a single value that has multiple instances for this worker).
- Compare the flagged payee against a similar payee who extracts successfully, field by field in the interface's field mapping, to isolate which mapped field triggers the cast failure.
- If a recent business process or data load changed this worker's record, check whether that event left an inconsistent or unexpected value in one of the interface's source fields.
Temporarily exclude the flagged payee from the run (or fix the specific out-of-shape data element identified in troubleshooting) so the rest of the population extracts successfully, then reprocess that one payee separately.
Add a validation or audit step before each PICOF run that flags workers whose interface-mapped fields have null, multi-valued, or type-mismatched data, so a single malformed payee record surfaces as a data-quality warning before the run instead of a cryptic ClassCastException during extract.