Use the EMIS Staff Report - Load page to load Ohio EMIS staff demographic (CI records) and employment (CK records) data from HR/Payroll tables into the EMIS reporting tables. This automated process eliminates manual data entry by fetching employee information directly from the district's HR system.
-
On the EMIS Staff Report page, select Load.
-
Refer to the Field descriptions and enter or select the required load criteria.
-
Select Load, and then Yes.
-
If data for the selected criteria is loaded, select Yes to delete and reload the data.
-
Save the Load Summary report file and select OK.
-
If certain conditions are met, the OH EMIS Staff Sick/Non-EMIS Leave Report is created. The default file name is EMIS Staff Banked Leave_<MMDDYYYY_hhmmss>.pdf. Save the report file and select OK.
-
If errors are encountered, save the Load Error log and select OK.
-
Navigate to the file location.
-
Inspect the files. Update data if necessary.
-
Repeat these steps until no errors are encountered and all required data is loaded.
Field descriptions
The following table describes the fields on the EMIS Staff Report - Load page.
|
Field |
Description |
|---|---|
|
Reporting Period |
The current EMIS Staff reporting period. Determines which reporting period the loaded records will be associated with. The field value is retrieved from the Staff Reporting Period field on the EMIS Profile page. This field is view-only. |
|
Start Date |
The start date of the current reporting period. Used as a reference for the date range during which employee data is evaluated for loading. The field value is retrieved from the Staff Start Date field on the EMIS Profile page. This field is view-only. |
|
End Date |
The end date of the current reporting period. Used as a reference for the date range during which employee data is evaluated for loading. The field value is retrieved from the Staff End Date field on the EMIS Profile page. This field is view-only. |
|
Fiscal Year |
The current EMIS Staff fiscal year. All loaded records will be created for this fiscal year. The field value is retrieved from the Staff Fiscal Year field on the EMIS Profile page. This field is view-only. |
|
Clear All Reporting Period Records for Fiscal Year |
Indicates whether to delete all existing EMIS staff demographic and/or employment records for the specified fiscal year and reporting period before loading new data, regardless of employee selection criteria. |
|
Clear Only Reporting Period Records for Start/End Dates of Fiscal Year |
Indicates whether to delete only existing records that match the specified load criteria (such as selected employees or date ranges) before loading new data, preserving other records. |
|
Staff Demographics Records |
Indicates whether to load only CI (Staff Demographic) records that contain personal information such as name, SSN, birth date, education level, ethnicity, and years of experience. |
|
Staff Employment Records |
Indicates whether to load only CK (Staff Employment) records that contain position-related information, such as position code, building IRN, FTE, salary, and fund sources. |
|
Both Demographic and Employment Records |
Indicates whether to load both CI (Staff Demographic) and CK (Staff Employment) records in a single load process. This is the default selection. |
|
Calculate Attendance |
Calculates and populates attendance-related fields (Attendance Days, Absence Days, Long Term Illness) during the load process. When this option is not selected, these fields are left blank. |
|
Sick Leave Bank Date |
This option excludes sick leave bank contributions made on a specific date from the absence days calculation. This prevents banked leave from inflating absence totals. |
|
Attendance Start Date |
This option specifies the start date of the date range used to identify attendance records with remarks starting with "NON-EMIS" that should be excluded from the absence days calculation. Used for custom attendance processing. |
|
Attendance End Date |
This option specifies the end date of the date range used to identify attendance records with remarks starting with "NON-EMIS" that should be excluded from the absence days calculation. Used for custom attendance processing. |
OH EMIS Staff Sick/Non-EMIS Leave Report
The OH EMIS Staff Sick/Non-EMIS Leave Report serves as an audit/verification report generated during the EMIS Staff data load. Specifically, it is used to:
-
Document attendance days excluded from EMIS reporting:
During the load, two categories of days are subtracted from an employee's calculated absence days before the data is submitted to EMIS:-
Banked Leave Days: Absence days credited to the Sick Leave Bank on the specified Sick Leave Bank Date.
-
Non-EMIS Days: Absence days within the attendance date range where the attendance record's Remarks field is marked NON-EMIS (applies to GHIL custom districts).
-
-
Provide a record of adjustments for review:
The report lists each affected employee's number, name, Sick Leave Bank Date, total Banked Leave Days, and total Non-EMIS Days, along with grand totals. This gives administrators visibility into which employees had days excluded and how many. -
Support district-level verification before submission:
Because these exclusions directly affect the attendance and absence day counts reported to the Ohio Department of Education via EMIS, the report allows HR/payroll staff to confirm that the correct days were excluded before the data export is finalized.
In short, it is a tool for transparency and reconciliation. It shows exactly which sick bank and non-EMIS leave days were removed from the EMIS attendance calculation during the load, so the district can verify the adjustments are accurate before submitting state data.
The OH EMIS Staff Sick/Non-EMIS Leave Report is created if certain conditions are met:
-
In the Load Options section, Both Demographic and Employment Records must be selected.
-
In the Other Options section, select Calculate Attendance and select dates in the following fields:
-
Sick Leave Bank Date
-
Attendance Start Date
-
Attendance End Date
-
This causes the report to be produced automatically at the conclusion of the load.
Currently, a blank report is generated regardless of whether the customization is implemented. This is being evaluated based on customer feedback.