Please refer to the following EEO web sites for government instructions: http://www.eeoc.gov/index.html
The EEO-1 Data File format can be obtained in the following website: http://www.eeoc.gov/eeo1survey/datafile.html
After REEO1 is run, an EEO1 Data File is generated. Users need to login to the following EEO website to upload the file to the government: http://www.eeoc.gov/eeo1survey/index.html
Changes As of 2019
The Equal Employment Opportunity Commission now requires the EEO-1 Form to collect compensation data. This change has been documented by the EEOC as 'Collection of 2017 and 2018 EEO-1 Component 2 Compensation Data'.
The REEO1 function has been updated to now create a data file in a CSV file format with the new required data.
In the ‘Component 2 EEO-1’ upload file layout (CSV File), job category, demographic group (defined by race, ethnicity, and gender) and annual salary as reported by pay band are columns in the file along with number of employees and hours worked. Each record in the upload file represents a unique combination of “job category by demographic group by pay band” for each establishment.
New UDFs required for Users to setup: These fields will be created the first time REEO1 is launched. Therefore, users should run the REEO1 first prior to completing the additional required set up.
User field Name | Prompt | Table | Field Value Type | Lexicon | |
---|---|---|---|---|---|
EEO1_USER_ID | EEO1 Comp 2 User ID | P2K_CM_ENTITY_DETAILS | Char | ||
EEO1_Q_D_2 | EEO1 Question D.2 | P2K_CM_LOCATIONS | Char | X_YES_NO |
These fields will be created the first time REEO1 is launched. Therefore, users should run the REEO1 first prior to completing the additional required set up.
User field Name | Prompt | Table | Field Value Type | Lexicon |
---|---|---|---|---|
EEO1_UNIT_NUMBER | EEO1 Unit Number | P2K_CM_LOCATIONS | Char | |
EEO1_FIRST_TIME_REPO | EEO1 First Time Reporting | P2K_CM_LOCATIONS | Char | X_YES_NO |
EEO1_Q_B_2_C | EEO1 Question B.2.C | P2K_CM_LOCATIONS | Char | X_YES_NO |
EEO1_Q_C_1 | EEO1 Question C.1 | P2K_CM_LOCATIONS | Char | X_YES_NO |
EEO1_Q_C_2 | EEO1 Question C.2 | P2K_CM_LOCATIONS | Char | X_YES_NO |
EEO1_Q_C_3 | EEO1 Question C.3 | P2K_CM_LOCATIONS | Char | X_YES_NO |
EEO1_DUN_BRADSTREET_NR | EE01 Dun & Bradstreet Number | P2K_CM_LOCATIONS | Number | |
EEO1_NAICS_CODE | EEO1 Naics Code | P2K_CM_LOCATIONS | Number | |
EE01_COMPANY_NUMBER | EEO1 Company Number | P2K_CM_ENTITY_DETAILS | Char |
User field Name | Prompt | Mandatory | Details |
---|---|---|---|
EEO1_UNIT_NUMBER | EEO1 Unit Number | No | |
EEO1_FIRST_TIME_REPO | EEO1 First Time Reporting | No | |
EEO1_Q_B_2_C | EEO1 Question B.2.C | No | |
EEO1_Q_C_1 | EEO1 Question C.1 | No | |
EEO1_Q_C_2 | EEO1 Question C.2 | No | |
EEO1_Q_C_3 | EEO1 Question C.3 | No | |
EEO1_DUN_BRADSTREET_NR | EE01 Dun & Bradstreet Number | No | |
EEO1_NAICS_CODE | EEO1 Naics Code | No |
User field Name | Prompt | Mandatory | Details |
---|---|---|---|
EE01_COMPANY_NUMBER | EEO1 Company Number | No |
This set up is only required if you are a multi-establishment employer. Records need to be created on the IDOL form with the following ORG_LEVEL_TYPE found on the lexicon X_ORG_LEVEL_TYPE
Saved Value | Displayed Value |
---|---|
E1 | EEO Headquarter |
E2 | EEO Locn Establishment |
If your organization has only a single location to report, this set up is not required.
IDOL Field | Details |
---|---|
Org Level Type | EEO Headquarter |
Org Level Code | Enter your organization's level code, can be your company name |
Description | Enter a description |
Parent Entity | The entity that this EEO Headquarter is reporting for must be defined. |
Parent Org Level | Leave this field blank for EEO Headquarter |
Managing Position | Not required for this report |
EEO Locn Establishment: For each additional location to be reported, users must create an entry with this type
IDOL Field | Details |
---|---|
Org Level Type | EEO Locn Establishment |
Org Level Code | Enter your organization's level code. The EEO Location code must also be defined on IDLN |
Description | Enter a description |
Parent Entity | Blank |
Parent Org Level | Enter the Org Level Code from IDOL EEO Headquarter (above) |
Managing Position | Not required for this report |
Field | Description |
---|---|
Entity | Mandatory. Defines the entity to report on. Users can select from the LOV. |
Date Range From/To | Defines the date range to report on. Employees who are Active within this date range will be included in the report. Users can select from the calendar icon (F9) |
As Of | Defines the date that the employee's demographic records will be examined “as of”. It should be set to the same 'Date Range To' value, to ensure consistency of data. Users can select from the calendar icon (F9) |
Sort People By | This field defines how the employee information will be sorted. Users can select from the LOV. |
Pay Period Used | Mandatory. Defines the pay period number. |
Certified Title | Mandatory. This field defines the title of the individual who has certified the information in the report. |
Certified By | Mandatory. This field defines the name of the individual who has certified the information in the report. |
Telephone Number | Mandatory. This field defines the telephone number for the individual who certified the report information. |
Email Address |
EEO1 Component | Mandatory. Must contain 'Component 2 EEO-1' |
*Salary Pay Element | This is the pay element for capturing Annual Salary |
*Hours Worked Pay Element | This is the pay element for capturing Hours worked |
EEO1 File Name | Defines the name of the EEO1 file. |
Create Errors File | When set to YES, an errors file will be generated. Users can select from the LOV. |
Create Dump File | When set to YES, a dump file will be generated. Users can select from the LOV. |
Details in Dump File | When set to YES, details will be included in the generated dump file. Users can select from the LOV. |
User Comment | Users can enter text that will appear on the header of all pages of the report. |
Exception Level | Mandatory. Defines the level of detail to be printed on the exception report. Options are: * Exceptions Only * User Trace * Internal Level * Legislation * UserCalc Trace * Program Trace * Utility Trace |
Field | Description |
---|---|
People List Code | Users can define one or more people lists to report on. Users can select from the LOV. |
Person Code | Users can define one or more person codes to report on. Users can select from the LOV. |
Org Level Type | Defines a specific Organization level to report on. Note: The Org Level Type MUST be defined IF using the Sort Option of Org Level OR if a user wants to filter the report by Org Levels. |
Org Level | Defines specific Organization levels to report on. Users can select one or multiple levels from the LOV. |
Department | Defines specific Departments to report on. Users can select one or multiple departments from the LOV. |
Authorization | Defines specific Authorization levels to report on. Users can select one or multiple Authorization levels from the LOV. |
Unit | Defines specific Units to report on. Users can select one or multiple Units from the LOV. |
Group | Defines specific Groups to report on. Users can select one or multiple Groups from the LOV. |
Status Types | Defines specific Status Types to report on. Users can select one or multiple Status Types from the LOV. |
- If "EEO1 File Name" is not provided, program will use UploadFileyyyyCCCCCCCC_mex.csv as file name (where 'yyyy' is the survey year, 2017 or 2018, and "CCCCCCC" is the 8-digit User ID provided by NORC.
Date Range From/To
- Defines the date range to report on. Employees who are Active within this date range will be included in the report. Employers will select a pay period between October 1 and December 31 of the reporting year, known as the workforce snapshot period. The workforce snapshot period for the 2017 EEO-1 report would be an employer-selected pay period between October 1, 2017 and December 31, 2017.The workforce snapshot period for the 2018 EEO-1 report would be an employer-selected pay period between October 1, 2018 and December 31, 2018.
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation