Is it still required to load locationUniqueKey to locations for EEO-1 reporting? — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Is it still required to load locationUniqueKey to locations for EEO-1 reporting?

edited Mar 4, 2024 5:04PM in Payroll and Global Payroll Interface (GPI) 3 comments

Summary:


Content (please ensure you mask any confidential information):

Hi,

Has the bug with locationUniqueKey(PER_LOCATION_LEG_EFF=HRX_US_REPORTING_INFORMATION) been resolved related to EEO-1 reporting? This attribute does not show in the UI but must have a value for the location to appear in EEO reporting. Hence we loaded an HDL file to support. Will this be required going forward as well?

Thanks,

Alex

Version (include the version you are using, if applicable):


Code Snippet (add any code snippets that support your topic, if applicable):

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!