This page (revision-11) was last changed on 26-Nov-2021 10:22 by Karen Parrott

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
11 26-Nov-2021 10:22 10 KB Karen Parrott to previous
10 26-Nov-2021 10:22 8 KB Karen Parrott to previous | to last
9 26-Nov-2021 10:22 8 KB kparrott to previous | to last
8 26-Nov-2021 10:22 8 KB kparrott to previous | to last
7 26-Nov-2021 10:22 8 KB kparrott to previous | to last
6 26-Nov-2021 10:22 7 KB mmcfarland to previous | to last
5 26-Nov-2021 10:22 8 KB khiggs to previous | to last
4 26-Nov-2021 10:22 8 KB khiggs to previous | to last
3 26-Nov-2021 10:22 3 KB rthiruppathy to previous | to last
2 26-Nov-2021 10:22 3 KB JMyers to previous | to last
1 26-Nov-2021 10:22 3 KB JMyers to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed 2 lines
!!!Equal Employment Opportunity - EEO1 Report\\
!!!Equal Employment Opportunity - EEO1 Report
At line 6 changed 9 lines
REEO1 provides capability for users to generate an interface file to report the EEO-1 Equal Employment Opportunity Data to the US Equal Employment Opportunity Commission. This is a report that may be required for U.S. private companies. The REEO1 process supports the filing of both a single-Establishment Employer and Multi-Establishment Employer.
\\ \\
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 EEO-1 Data File is generated. The user needs to login to the following EEO website to upload the file to the government.\\ \\
http://www.eeoc.gov/eeo1survey/index.html
The REEO1 report generates an interface file to report the EEO1 Equal Employment Opportunity Data to the US Equal Employment Opportunity Commission. This report may be required for private U.S. organizations. The REEO1 process supports the filing for both single-Establishment Employers and Multi-Establishment Employers. \\ \\
At line 7 added one line
Please refer to the following EEO web sites for government instructions: http://www.eeoc.gov/index.html \\ \\
At line 9 added one line
The EEO-1 Data File format can be obtained in the following website: http://www.eeoc.gov/eeo1survey/datafile.html \\ \\
At line 18 changed one line
!!EE0-1 Single and Multi-establishment Required Set Up
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
At line 13 added 26 lines
__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|
!!EE01 Single and Multi-establishment Required Set Up
![IEID] – Maintain Identity Information
Ethnicity is used in EEO reporting as another major categorization of data for equal opportunity reporting. The employee’s ethnic category is set up on Maintain Identities Information ([IEID]). Ethnicity is predefined using the fixed lexicon [X_US_ETHNICITY] in the field US Ethnicity.
At line 21 changed one line
The REEO1 utalizes system created user defined fields on found on both the [P2K_CM_LOCATIONS] and [P2K_CM_ENTITY_DETAILS] tables.
The REEO1 report utilizes system created user defined fields on found on both the [P2K_CM_LOCATIONS] and [P2K_CM_ENTITY_DETAILS] tables.
At line 23 changed one line
These fields will be created the first time [REEO1] is launched. Users should therefore run the REEO1 first prior to completing the additional required set up.
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.
At line 27 changed 5 lines
|EEO1_FIRST_TIME_REPO|EEO1 First Time Reporting|[P2K_CM_LOCATIONS]|Char|[X_Y_OR_N]
|EEO1_Q_B_2_C|EEO1 Question B.2.C|[P2K_CM_LOCATIONS]|Char|[X_Y_OR_N]
|EEO1_Q_C_1|EEO1 Question C.1|[P2K_CM_LOCATIONS]|Char|[X_Y_OR_N]
|EEO1_Q_C_2|EEO1 Question C.2|[P2K_CM_LOCATIONS]|Char|[X_Y_OR_N]
|EEO1_Q_C_3|EEO1 Question C.3|[P2K_CM_LOCATIONS]|Char|[X_Y_OR_N]
|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]
At line 37 changed 2 lines
There must be a tax jurisdiction defined for the EEO-1 report. The jurisdiction must be defined at the county level
as this will be the county name to report on the EEO-1 Data File.
A tax jurisdiction must be defined for the EEO1 report. The jurisdiction must be defined at the County level as this will be the county name to report on the EEO1 Data File.
At line 41 changed 2 lines
Each location to be reported for EE0-1 must have a [JURISDICTION_NAME] associated that has been defined at the county level.
*The following user defined fields can be populated if needed
Each location to be reported for EE01 must have an associated [JURISDICTION_NAME] that has been defined at the County level.\\
The following user defined fields can be populated, if required.
At line 54 changed 4 lines
The [LOCATION_CODE] associated to Entity must have a tax jurisdiction defined at the county level on [IDTX].
The EEO1 Company Number user field must be populated as it is required in the EE01 data file.
The location code associated to entity must be one of the locations defined with the county Jursidiction.
The EEO1 Company Number user field must be populated as it is required in the EE01 data file.
The [LOCATION_CODE] associated to an Entity must have a tax jurisdiction defined at the County level on [IDTX].\\
* The EEO1 Company Number user field must be defined as it is required in the EE01 data file.
* The location code associated to an entity must be one of the locations defined with the county Jursidiction.
* The EEO1 Company Number user field must be defined as it is required in the EE01 data file.
At line 59 removed 3 lines
![IDEN] - Define Entities
The [LOCATION_CODE] associated to Entity must have a tax jurisdiction defined at the county level on [IDTX].
The EEO1 Company Number userfield must be populated as it is required in the EE01 data file.
At line 66 changed one line
!!EE0-1 Multi-Establishment Required Set Up
!!EE01 Multi-Establishment Required Set Up
At line 68 changed 2 lines
This set up is only required if you are a multi-establishment employer.
Records will need to be created on the [IDOL] screen with the following [ORG_LEVEL_TYPE] found on the lexicon [X_ORG_LEVEL_TYPE]
__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]
At line 74 changed one line
If you have only the single location to report, this set up is not required.
If your organization has only a single location to report, this set up is not required.
At line 77 changed one line
*EEO Headquarter - User must enter one entry with this Org Level Type (typically this will be the location code found on the IDEN)
__EEO Headquarter__: Users must enter one entry with this Org Level Type (typically this is the location code found on the IDEN)
At line 80 changed 4 lines
|Org Level Code|Enter your own organization level code, may be your company name
|Description|Enter your own description
|Parent Entity|Must enter the Entity Name that this EEO Headquarter is reporting for
|Parent Org Level|Leave this blank for 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
At line 85 changed 3 lines
Must list all Departments that have a matching location code to be reported.
\\ \\
*EEO Locn Establishment - For each additional location to be reported,users must create an entry with this type
* Users must list all Departments that have a matching location code to be reported.\\ \\
__EEO Locn Establishment__: For each additional location to be reported, users must create an entry with this type
At line 90 changed 2 lines
|Org Level Code|Enter your own organization level code. The EEO Location code must also be entered on the IDLN
|Description|Enter your own description
|Org Level Code|Enter your organization's level code. The EEO Location code must also be defined on IDLN
|Description|Enter a description
At line 93 changed one line
|Parent Org Level|Enter the Org Level Code from IDOL EEO Headquarter above
|Parent Org Level|Enter the Org Level Code from IDOL EEO Headquarter (above)
At line 95 removed one line
user must list all Departments that belong to this EEO Locn Establishment
At line 97 changed 17 lines
!!Report Parameters & Filters
||Report Parameters||
|Entity|Mandatory, LOV Available\\This field limits the report to a single entity.
|Date Range From/To|Date, LOV Available\\This date range will be used to identify the dates that the employees will be pulled from to generate the report. Employees who are active within this date range will be included in the report.
|As Of|Date, LOV Available\\This date indicates the date that the employee's demographic records will be examined “as of”. It should be set to the Date Range To value, to ensure consistency of data.
|Sort People By|Optional, LOV Available\\This field indicates how the information will be sorted.
|Pay Period Used|Mandatory, Manual. Enter pay period number.
|Certified Title|Mandatory, Manual\\This field displays the title of the individual who has certified the information in the report.
|Certified By|Mandatory, Manual\\This field indicates the name of the individual who has certified the information in the report.
|Telephone Number|Mandatory, Manual\\This field provides a telephone number for the individual who certified the report information.
|Create Errors File|Optional, Yes or No, LOV available
|Create Dump File|Optional, Yes or No, LOV available
|Details in Dump File|Optional, Yes or No, LOV available
|Directory Name|Optional Manual
|EEO1 File Name|Optional Manual
|User Comment|Optional, Text\\This field holds the user-supplied comment which will appear in the header of all pages of the report.
|Exception Level|Mandatory, LOV available\\You may select the level of logging desired: ‘Exceptions Only’, ‘User Trace’, ‘Internal Level’ ‘Legislation’, ‘UserCalc Trace’, ‘Program Trace’ or Utility Trace.
* Users must list all Departments that belong to this EEO Locn Establishment \\
At line 115 removed 10 lines
||Report Filters||
|People List Code|Optional, Multiple Selection Available, LOV Available\\This field will limit the report to the people lists selected.
|Person Code|Optional, Multiple Selection Available, LOV Available\\This field will limit the report to the people selected.
|Org Level Type|Optional, Lexicon Available\\This will limit the report to the organization level type selected.\\Note:Org Level Type MUST be specified IF you are using the Sort Option of Org Level OR if you want to filter by Org Levels.
|Org Level|Optional, Multiple Selection Available, LOV Available\\This will limit the report to the organization levels selected.
|Department|Optional, Multiple Selection Available, LOV Available\\This will limit the report to the departments selected.
|Authorization|Optional, Multiple Selection Available, LOV Available\\This will limit the report to the authorization levels selected.
|Unit|Optional, Multiple Selection Available, LOV Available\\This field will limit the report to the units selected.
|Group|Optional, Multiple Selection Available, LOV Available\\This field will limit the report to the groups selected.
|Status Types|Optional, Multiple Selection Available, LOV Available\\This field will limit the report to the status types selected.
At line 114 added 11 lines
!!REEO1 Report Parameters
||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|
At line 126 added 36 lines
|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
!!REEO1 Report Filters
||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.
!!Processing
EEO1 File Name
- 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.