FL Additional Jobs Assignments
Overview
This format of the Additional Job Assignment should be reported during reporting periods 2 and 3 when a staff member performs additional job assignments.
Report Frequency
This report is due during reporting periods 2 and 3 when a staff member performs additional job assignments. For example, if a teacher of Language Arts, Middle/Junior (Job Code 51027) is also a teacher of gifted students, the additional job code 52008 should be reported in this format.
Selection Criteria
All employees, including contracted employees, with additional job assignments.
Setup
Before a report can be generated, the reporting interface must be accessed and the necessary data set up completed. This configuration information is used by the Load and Submission processes.
Note: For detailed information about the report screens/tabs, see the “Overview of Regulatory Reporting” document. This document explains the items in common for all reports.
The following options need to be configured under “Setup” menu:
· Site Profile
· Ledger Profile
· Crosswalk
· Code Value
· Additional Setup
Site Profile
Click Site Profile to define the entities and their details. This information is used by the Load and Submission processes for the defined entities. At least one Site Profile record is required. All of the Florida regulatory reports utilize this same table so data will rarely need to be changed once it has been entered.
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 accept if all the five characters are 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. |
Department of * Education District Number | The two-digit number for the district in which the staff member is currently employed |
Note: Columns marked with * are required fields.
Ledger Profile
The Ledger Profile page provides the ability to map/validate code values between the finance system and the regulatory report requirements.
Crosswalk
The Crosswalk page 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 | Description |
FLDOESCHOOL | FL DOE School Building Numbers |
FLDOEJOBCODE | FL DOE Job Codes |
FLDOEFUNDSRC | FL DOE Fund Source |
Code Value
Click Code Value to define valid codes. Codes that are defined on this page can be used on the Maintenance page.
Additional Setup
Click Additional Setup to define the entity’s optional details. This information is used by the Load and Submission processes.
Code | Description |
FLDOERECTYPES | Record Types for Primary Pay Assignments |
FLDOESUPPAYCLASS | Supplemental Pay Class |
FLDOELEDGER | Default Ledger for this entity |
FLDOELOCALID | Include the Employee ID as local ID |
Note: This screen will not be present for a particular report where no setup requirements need to be configured.
Instance
Click Instance to configure the report instances for each report to be created. Report instances need to be configured for the extract process.
Enter data in the fields as described below.
Field | Description |
Name* | Name of the report instance as defined by the user. |
Survey Period* | Survey Period |
Fiscal Year* | Fiscal Year for which submission will occur- “YYYY-YYYY” format. |
‘As of’ Start Date* | Survey Start Date - “MM/DD/YYYY” format. Once the instance is created and saved, the ‘As of’ Start Date’ value cannot be changed. |
‘As of’ End Date* | Survey End Date - “MM/DD/YYYY” format. Once the instance is created and saved, the ‘As of’ End Date’ value cannot be changed. |
Note: Columns marked with * are required fields.
Load
Click Load to extract and load records into the maintenance table. See the Submission File Layout for the source of the reported data.
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 desired report instance. |
Notes | Enter a note related to report instance or load that is 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) | If specific IDs are to be refreshed or reported on, enter on this line, separated by commas. |
Purge Existing Data | If all the existing Maintenance table data, for the selected Report Instance, needs to be deleted this checkbox should be checked. This action would also remove new Maintenance records added previously using the Maintenance screen. |
Load (Button) | Click to load maintenance records into the Maintenance table. |
Note: Columns marked with * are required fields.
After clicking Load, the Information window appears to indicate that the Load Process has begun. Click the “OK” button to proceed.
The selected report instance details appear as described below.
Field | Description |
Report Instance Details | Details of the selected Report Instance. |
Last Load for the Selected Report Instance | The date (Last Load) and user (Created By) who performed the last load and any note entered for the selected Report Instance. If the report is loaded for the first time for the selected Report Instance, this information is blank. |
Maintenance
Click the Maintenance link 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.
The following actions are available:
· Data changes (to data extracted from the report instance into the Maintenance table)
· Adding records
· Deleting records
Select Report or Specific Records
Field | Description |
Report Instance | Click to select a specific instance. |
Filter By Criteria | Filter the maintenance records based on Employee ID or Employee Last Name. Enter data then click the Apply Filter button. Clear the fields and click the Apply Filter button again to view all the results. |
Total Record Count | Indicates the total number of Maintenance records in the grid. |
Error Log By Last | Click to select the type of errors/messages to view. Options are Load or Submission. |
Filter Selected Record | Filters the selected Maintenance record in the records area above. |
Generate Report (Button) | Runs the “Error Log” to a report. |
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 click of “View All Records”, all the maintenance records are 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” button.
Type | Error / Warning Message | Resolution |
| <EMP ID>: has invalid Location <location> for Job Code <Job Code>. Setting to 0000 | Map the location in Crosswalk screen with FLDOESCHOOL code |
| <EMP ID>: Fund <Fund Source> not found in crosswalk | Map the Fund Source in Crosswalk screen with FLDOEFUNDSRC code |
| <EMP ID>: has invalid Job Code <job code> Setting to 00000 | Map the Job Code in Crosswalk screen with FLDOEJOBCODE code |
Notes:
· “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
· The report instances drop-down list is loaded only with report instances for which the load has happened.
· Inserting and deleting records are not allowed if there are unsaved changes in the grid.
· If there are unsaved changes in the grid, sorting and filtering of the grid are disabled.
· If there are unsaved changes in the grid, a prompt to save the existing changes will be shown, if trying to navigate to another screen.
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, enter data in the fields as described below.
Field | Button | Description |
Report Instance* | Click for the list of report instances. Choose the report instance which is to be submitted. |
Notes | Any notes applicable to the submission job. |
Filename* | System generated or user defined file name for the submission file. The filename should always end with the “.txt” extension. The filename cannot contain these characters ‘\:/*?”<>|’ Note: The path where the file is saved is already configured in the application and should not be entered here. In some reports the report name is auto-generated and hence the text filename cannot be changes for such reports. Example: DPS43.GU.F61029.Y09102 |
Entity* | Click for the list of entities. If the maintenance records for all the entities are to be submitted then “ALL” should be selected. |
Report Instance Details | Details for the selected “Report Instance”. |
Last Submission for the Selected Report Instance | The date (Last Submission) and user (Created By) who performed the last submission and the note that was entered for submitting the selected Report Instance. |
Double Arrow (Button) | Regenerate the filename. |
Generate Report (Button) | Create report file with data from maintenance table. |
View Report (Button) | View the submission file report. |
Notes:
· Columns marked with * are required fields.
· Only if the Load is performed on the report instance, the report instance will appear in the Report Instance drop-down list.
· If the mandatory fields are empty or have an invalid value, an error is logged which can be corrected from the Maintenance screen.
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-2 | District Number | Y | N/R | 2 | rr_site_profile | district_no | The two-digit number for the district in which the staff member is currently employed. For employees who serve multiple districts, this is the fiscal agent district number. Also, the district number is for the district submitting the in-service education component. |
3-12 | Social Security Number | Y | A/N/L | 10 | hr_empmstr | ssn | The number assigned to an individual by the Social Security Administration (left justified). NOTE: For contracted or charter school staff for whom the school district cannot obtain a Social Security Number, the district must assign a Staff Number Identifier for the employee using the following method: CS The first two positions in the Social Security Number field must be coded with the letters “CS”. NNNNNNN The last seven positions must be numeric. NOTE: The district-defined Staff Number Identifier must result in a unique staff number within the district. |
13-13 | Survey Period Code | Y | N | 1 | rr_run_def_ | survey_period | A code representing one of the state reporting periods. |
14-17 | Fiscal Year | Y | N | 4 | rr_run_def_ | fiscal_year_ | The state fiscal year running from July 1 through June 30 for which the reported data are applicable. |
18-21 | School Number, Primary/Home | N | N/R | 4 | hr_pcntble | location | The state assigned four-digit school number (0001-9899) which indicates the primary administrative reporting unit to which the individual is assigned. The school number which indicates the primary school to which this individual is assigned for the reported job code. For staff members who operate out of the county office, the school number to be used in this field is 9001. |
22-26 | Job Code, Additional | Y | N | 5 | hr_pcntble | jobcode | The code associated with each primary job assignment of the employee. This code is submitted in reporting periods 2, 3, and 5. In Survey 5, primary job code for the job the employee held during the regular school year is reported. |
27-29 | Job Code FTE | N | N/R | 3 | hr_emppay | pcn_fte | The full-time equivalency of the job assignment (to the nearest whole percent). For one full-time equivalency, the employee’s services are required each working day at least the number of hours equal to the number of hours of a regular working day for that job. |
30-30 | Job Code Fund Source 1 | N | A | 1 | hr_earndist | gl_key | A code to identify up to three fund sources (and corresponding percentages) from which the employee’s salary is paid: This element identifies up to three fund sources from which the employee is paid at the time of the survey for the primary job reported. |
31-33 | Job Code Fund Source 1 Percent | N | N | 3 | hr_earndist | percent | |
34-34 | Job Code Fund Source 2 | N | A | 1 | hr_earndist | gl_key | |
35-37 | Job Code Fund Source 2 Percent | N | N | 3 | hr_earndist | percent | |
38-38 | Job Code Fund Source 3 | N | A | 1 | hr_earndist | gl_key | |
39-41 | Job Code Fund Source 3 Percent | N | N | 3 | hr_earndist | percent | |
42-42 | Transaction Code | N | A | 1 |
|
| . |
43-43 | Qualified Paraprofessional | N | A | 1 | hr_licncert | licntype | A code to indicate the qualification status of a paraprofessional in relation to No Child Left Behind (NCLB) requirements. |
44-48 | Filler |
| A/N | 19 |
|
|
|
49-62 | Florida Education Identifier | Y | A/N | 14 | pya_assoc_dtl | pya_assoc_desc | A code issued by the Florida Department of Education used to uniquely identify a person in Florida’s education data system. Example: FL123456789012 Florida Education Identifier (FLEID) for an employee. Proposed automated process to retrieve and populate state IDs to BPlus database |
63-72 | Staff Number Identifier, Local | N | A/N/L | 10 | hr_empmstr | id | A ten-character code used by the school district locally to uniquely identify an employee. This staff identifier must be different than the Social Security Number or the district-defined number used in lieu of a social security number provided in the Social Security Number data element field. Note: This element is optional. If the district reports this identifier on a data format submitted to the Automated Staff Data Base, this identifier will be included on designated print reports, available from the system, in place of the Social Security Number or data provided in the Social Security Number data element field. |
73-80 | Error Codes | N | A/N | 8 |
|
| This field is used by the Department to report to districts the specific errors found in the record during the state edit process. This field should contain filler (spaces, blanks) when the record is transmitted to the Department. |
Data Types
A/N: Alpha Numeric, left justified, and blank.
N: Numeric, right justified, zero, unsigned without decimal point, cents, and dollars.
Record Length: 80 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.