IL AROE Report
Overview
The Teachers’ Retirement System of the State of Illinois requires the Annual Report of Earnings
Report Frequency
Due annually, in mid-August. Specific Date may vary from year to year.
Selection Criteria
Records are selected from the BP Performance screen (HREEPF). Selection of records is done.
BusinessPLUS Setup
State ID. The credential holder’s IEIN field holes the evaluator’s and evaluatee’s state IDs.
Setup
Before a report can be generated, the reporting interface must be accessed and necessary data set up completed. This configuration information is used by the Load and Submission processes.
The following options need to be configured under the ‘Setup’ menu:
Site Profile
Crosswalk
Code Value
Additional Setup
For detailed information about the report screens/tabs, see the ‘Overview of Regulatory Reporting’ document. The document explains the items in common for all reports.
Site Profile
Click Setup > Site Profile to define entities and their details. At least one Site Profile record is required. All of the IL regulatory reports utilize this same table so data will rarely need to be changed once it has been entered. In the following example, sensitive information has been blocked.
To add details about a ‘Site’, enter data in the fields as described below.
Field | Description |
Entity* | ID of the entity/employer. The entity should be a valid entry as defined in BusinessPLUS. Once saved, the value cannot be changed. |
Employer Name* | Name of the employer for whom the entity is defined. |
Employer Address* | First line of the employer’s address. |
Employer Address (2) | Second line of the employer’s address. |
Employer City* | City in which the employer is located. |
Employer State* | State in which the employer is located. Click for the list of states. |
Employer Zip Code* | Numeric zip code of the employer’s location. This field accepts only five numeric characters and does not allow all five characters to be zeroes. |
Employer Zip Code Extension | Numeric zip code extension of the employer’s location. This field accepts only numeric characters of 4 digits or less. |
Ledger Profile
The Setup > Ledger Profile tab provides the ability to map/validate code values between the finance system and the regulatory report requirements. The predefined code items appear as a list when the ‘Crosswalk’ screen is loaded.
Crosswalk Mapping
The Setup > Crosswalk tab provides the ability to map/validate code values between the finance system and the regulatory report requirements. The predefined code items appear as a list when the ‘Crosswalk’ screen is loaded.
Code Item | Description |
ILEVALCODE | Maps client Eval Ratings with Report Eval Ratings |
Code Value
Click Setup > Code Value to define reporting code value. This information is used by the Load process. These tables define the reporting values for the Items listed in the Crosswalk screen.
Additional Setup
Click Setup > Additional Setup to define the reports configuration details. This information is used by the Load process.
The following table describes each of the additional setup features’ purpose and setup.
Setup Description | Value/Type | Purpose |
Valid Position Numbers(s) | Character, CSV string, max length 2000. | Only evaluations with a position code, who’s CBEDS value is in this list are reported. |
Select By (DATE, FY, or BOTH) | Character, max length 4. | Determines selection criteria of by either the record’s eval date or a miscellaneous string representing the fiscal year. |
Misc Field for Eval Year String | Character, max length 200. | Determines which miscellaneous field holds the eval year string. Enter 1 thru 4. |
Excluded Eval Types | Character, CSV string, max length 200. | Performance records with an eval type in this list are excluded from the report. |
Use Eval Rating Crosswalk Table (Y/N) | Character, max length 1, default “N” | Toggles the use of the eval rating crosswalk table. |
Instance
Click Instance to configure the report instances for each report to be created. Report instances need to be configured for the Load Process. Think of the Report Instance as an identification of the time period for each report/file to be created.
Load
Click Load to select the Report Instance for which to extract and load the eligible records into the maintenance table. See the Submission File Layout for the source of the reported data.
To launch the Load Process, select the appropriate data and, if necessary, refer to the Overview of Regulatory Reporting guide for additional information.
To load data for an instance of a report, enter data in the fields as described below.
Field/Button | Description |
---|---|
Report Instance* | Click for the list of report instances. Select the report instance to load data. |
Notes | Enter a note related to report instance or load that needs to be performed. |
Entity* | Click to select a specific entity for which the load will be performed. Select ‘ALL’ to extract records of all entities. |
Employee ID(s) | Reports only the specific employees listed. Useful for running the report after the initial submission in order to report newly hired employees, or employees who’ve changes positions. |
Purge Existing Data | If all the existing data for the selected ‘Report Instance’ in the maintenance table needs to be deleted, this checkbox should be checked. This action will also remove new maintenance records added previously using the maintenance screen for the ‘Report Instance’. |
Load (Button) | Click to load maintenance records into maintenance table. |
Maintenance
Click Maintenance to view Load Process results. The load will include any generated errors and will display those in the bottom half of the screen. Data manipulation is allowed on the extracted employee data.
Long-term data correction must be done in the other report screens or in BusinessPLUS itself. Data entered or updated in a report instance is good only for that instance.
Possible Error & Warning Messages
The grid at the bottom of the Maintenance page displays error messages logged during the load extract/submission package execution. The errors include invalid/missing mandatory field values. These values can be corrected by selecting the record from the error log grid and clicking on the ‘Filter Selected Record’ checkbox although the long-term data fix would need to occur in BusinessPLUS or the report setup type screens. On clicking this option, only the invalid record is filtered in the maintenance grid, which can then be corrected and saved. On clicking the checkbox again (clearing the field) all the maintenance records are again displayed on the maintenance grid.
The potential Error/Warning Messages are described in the table below. How to resolve the errors is also provided. In some cases, the message may be informational only and should not significantly affect the Submission Process. See the Submission File Layout section regarding the fields in question to verify if they are required.
To generate a separate error report that can be printed or used for reference for either the Load or Submission type errors, make the appropriate selection in the ‘Error Log By Last’ drop down and click on the generate report icon to the far right of the ‘Error Log By Last’ field.
Type | Error / Warning Message | Resolution |
---|---|---|
Load | position <pos> (<date> – <date>) removed due to low fte (<fte>) | FTEs less than 0.1 are not to be reported. If this position should be reported, check the employee’s Position Assignment ‘Calc Dates’, ‘PCN FTE’, and ‘Actual Days’ values. |
Load | (TERMINATED) position <pos> (<date> – <date>) removed due to low fte (<fte>) | Signifies that not only was the position removed due to low FTE, but that the employee has also been terminated. Employees that receive this warning may need to have their employment end dates manually updated on the ISBE EIS. |
Load | has work location code <loc> not configured in crosswalk. Setting it to: BLANK | Add the work location code to the cross walk. Or, if not using the crosswalk, set the Setup Value “Use crosswalk for Work Location RCDTS” to ‘N’ in order to suppress the warnings. |
Load | has Work Location <rrcccddddttssss> at District. | Check Position Definition to ensure that it has the appropriate CBDS and Location codes. Check the setup item “Positions Requiring RCDTS at School Level” for missing position codes. Manually assign the employee a school level work location (Note that this will not affect the employee’s data in BusinessPLUS.) |
Load | has Employment End Date before Position Start Date! | The terminated employee may still have an active position assignment in BusinessPLUS that needs to be closed. A rehired employee may still have a termination date in the Employee Master screen. |
Load | has Position State Date > Report End Date! | An employee position assignment may have Calc Date inconsistencies or may have the wrong Fiscal Year. |
Load | has FTE total <XX.XXX> for timeframe <XX> | If using AutoFTE, check the employee’s position assignments’ Calc Dates, PCN FTE, and Actual/Default Days errors. Also check the associated Position Definitions’ Timeframe codes, as a summer position without the timeframe code may cause this. If not using Auto FTE, check the position assignments’ PCN FTEs, or change the employee’s FTEs on the maintenance screen. |
Load | has employment termination code <XX> not configured in crosswalk. Setting it to Blank. | Add the termination code to the TERMCODES crosswalk table. |
Load | has employment termination code <XX> but no termination date. | Check the Employee Master page, Term Info Tab for missing Term Cd’s and Term Dt for errors. |
Load | has no employment termination code but has a termination date <date>. | Check the Employee Master page, Term Info Tab for missing Term Cd’s and Term Dt for errors. |
Load | has no grade level set for position <pos> Setting it to “” | Check the Position Definition to ensure it has a valid grade level assignment. |
Load | has position grade level ‘<XXXXX>’ not configured in crosswalk. Setting it to “” | Add this missing grade level code to the crosswalk table. |
Load | has <X> primary locations. Location “<rrcccddddttssss>” will be marked as Primary. | Primary Position Assignments are limited to 1 at a time, so this will only occur if there has been a position transfer during the year. (Suppressed. You should not see this message.) |
Load | has no primary locations. | Check employee pay assignments for accuracy. |
Load | has 999 position with < 1.0 FTE! | Occurs when there is only the 999 record to report for the employee, but its FTE is less than 1.0. If the employee has had another position removed due to low FTE, adjust the 999 record’s FTE to 1.0 or replace the 999 record with the non-999 record, setting the FTE to 0.1. If the employee has not had another position removed due to low FTE, check the employee’s master screen for a termination date. If it exists remove the 999 record from the report and update the ISBE EIS manually with the employee’s termination data. |
‘Load’ indicates the message appears during the Load Process, on the bottom of the Maintenance screen
‘Sub’ indicates the message appears on the Submission report
Submission
After verifying the maintenance data, click Submission to create the file to be submitted to the reporting agency.
To create a report file for submission, data is entered in the fields as described below as well as in the Overview of Regulatory Reporting guide.
Field / Button | Description |
File Name | Enter the name of the file to be produced. Use the file extension “.txt” The filename should follow the format: RCDTS or District NAME + _ + Date (mmddyyyy) + _ + File Identifier + .txt File Identifier is used when submitting multiple files, for the batch files produced be this report it should always be ‘001’ E.g.: 500821040020000_06222015_001.txt |
Submission File Layout
The following table shows the field numbers, field names, and source within BusinessPLUS.
Position | Field | Req. | Type | Size | Source Table | Source Column | Description/Business Logic |
---|---|---|---|---|---|---|---|
1 | Letter Code | Y | N | 1 | hr_credholdr | seid | The Illinois Educator Identification Number is for each reported employee. If no IEIN is found for an employee, an IEIN will be generated for the employee. |
2-10 | SSN | N | A | 9 | hr_empmstr | ssn | The Social Security Number will be used for matching purposes, along with Last Name, First Name, Date of Birth, and Gender. |
11-40 | Name | Y | A | 30 | hr_empmstr | lname | Employee’s Legal Last Name. (No periods or apostrophes) |
41 | Gender | Y | A | 1 | hr_empmstr | fname | Employee’s Legal First Name. (No periods or apostrophes) |
42-49 | Date of Birth | Y | A | 8 | hr_empmstr | mname | Employee’s Legal Middle Name or first initial of Middle Name. (No periods or apostrophes) |
50 | Type of Employment | N | A | 1 | hr_empmstr | former | Employee's Maiden Name. (No periods or apostrophes) |
51-53 | Number of Days in Employment Agreement | Y | D | 3 | hr_empmstr | bdt | Employee’s Date of Birth. MM/DD/YYYY |
54-56 | GENDER | Y | A | 3 | hr_empmstr | gender | Sex (Male or Female) ‘M’ or ‘F’ |
57-66 | RACE | Y | N | 10 | hr_emp_race | race_cd | Race/Ethnicity. Use the EIS Race/Ethnicity Codes. |
67-76 | SCHOOL YEAR | Y | A | 10 |
|
| School Year of the data being reported. Determined form Instance definition. |
77-86 | EMPLOYER RCDTS | Y | N | 10 |
|
| District RCDTS code. Taken from Report Entity Definition. |
87-96 | WORK LOCATION RCDTS | Y | N | 10 | hr_pcntble | location | Work location RCDTS. PCN location replaces the ssss component of the Employer REDTS code. Report value determined through crosswalk table. |
Data Types
A/N - Alpha Numeric, left justified, and blank.
N - Numeric, right justified, zero, unsigned without decimal point, cents, and dollars.
N 1,2 – Numeric, include decimal point, 1=number of digits before decimal, 2=number of digits after decimal.
D – Date, following the format MM/DD/YYYY
Record Length: 250 bytes/characters plus one character for carriage return and one character for line feed
Submission Report
The submission file report can be obtained by clicking Generate Report or View Report buttons on the ‘Submission’ window.
About
The About screen displays system level information about the report such as the version, report name and database details.