E1:08: 2019 EEO-1 Component 2 - New Reporting Functionality is Available
(Doc ID 2576794.1)
Last updated on MARCH 16, 2020
Applies to:JD Edwards EnterpriseOne Human Resources Management - Version 9.1 to 9.2 [Release 9.1 to 9.2]
Information in this document applies to any platform.
The JD Edwards EnterpriseOne Human Resource product has been enhanced to comply with the 2019 EEO-1 changes. Employers are responsible for filing the new EEO-1 Component 2 Report by September 30, 2019.
The changes includes revised data collection for the EEO-1 report. This revised data collection has two components:
- Component 1 - Component 1 collects the same data that is gathered by the currently approved EEO-1: Specifically data about employees' ethnicity, race, and sex,by job category. (No change from current reporting and functionality)
- Component 2 - Component 2 collects data on employees' W-2 earnings and hours worked,which EEO-1 filers already maintain in the ordinary course of business.Component 2 will collect aggregate W-2 data in 12 pay bands for the 10 EEO-1 job categories. Employers will simply count and report the number of employees in each pay band. Component 2 will also collect the total number of hours worked by the employees included in each EEO-1 pay band cell. (New reporting and functionality)
For more details visit, https://www.eeoc.gov/employers/eeo1survey/index.cfm
- UDC 05U|PT - allow certain pay types to be excluded from the hours being reported
- UDC 05U|PB - EEO Pay Bands (data provided with ESU)
- R058515A - EEO-1 Report Component 2
- F05850 - EEO-1 Annual Data
- P05850 - EEO-1 Annual Data
- R89058515A EEO-1 Report Data File (Component 2)
The employees' W-2 earnings reported in Box 1 of the W-2 form are used as a reference to categorize the employees into the 12 pay bands or salary compensation bands defined for each of the 10 EEO-1 job categories. Enter the Year-End ID from P07810 in Processing Option #10.
R058515A Processing Options
Processing Options #10 and #11 are new for Component 2 Reporting:
#10 pertains to the Year-End ID for the year being reported. Refer to the Year-End Workbench, P07810 to obtain the correct value for this processing option.
#11 pertains to how the report retrieves the hours worked. Actual hours worked will look at the timecard historical file, F0618. If you choose this option, you can also tell the system what pay types to omit by utilizing UDC 05U
Year-End ID (P07810)
The Year-End ID that is used for W2 and 1099 reporting for payroll is used to report the employee wages.
EEO-1 Component 2 Reporting Examples
U.S. Government Employee Count form examples
JD Edwards EnterpriseOne Employee Count Report example
U.S. Government Hours Worked Report example
JD Edwards EnterpriseOne Hours Worked Report example
This application is populated after the R058515A UBE is run. The report populates the table F05850 and also creates the PDF report.
Magnetic Media File
R89058515A creates the magnetic media file as a simple CSV file.
- The file contains header rows with column names
- Job Categories are numbered 1-10
- Race, ethnicity and gender classification have letter codes A-N
- Pay band is called ANNUALSALARY in the CSV, numbered 1-12
Mag Media File Example
Steps to process the EEO-1 Component 2 Reports
Before processing the EEO-1 Component 2 report, ensure that you have payroll history and year-end IDs set up for the years being reported.
- Access batch versions (BV) for R058515A. Ensure that all of the processing options are setup including #10 (Year-End ID) and #11 (proxy or actual hours).
- Review information in P05850 and verify the EEO-1 Component 2 report
- Run R8905815A to create the mag media file
Apply the ESU for the release listed below to receive the new functionality.
Column names are required and should only be reported in the first record of the upload file and not repeated for each establishment. The functionality for the column names is not available via the first ESU (listed above). A new ESU will be required.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document