Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel

Table of Contents

...

The position number that you see on the report can vary based upon whether an EMIS data collection has been performed on your data set or not.  When a collection is done, a local contract code is assigned to any compensations that will be reported.  For EMIS reporting purposes, each compensation is converted to a 'Position'.  There may be multiple compensations reported for a given position.  The local contract code is what uniquely identifies the compensation.  If a collection has been run, then the position number on the report will show something like 1a as the Position # / Local Contract Code.  This local contract code is also displayed when viewing the compensation on the compensation screen.  If an EMIS data collection has not been performed on your data set, then you will simply see the position number on the report.  We do NOT assigned local contract codes when running the report, so if one does not exist, we will provide the job number.

EMIS Data Collection Reports

Field Definitions:

Sort By

...

Click on  to create the Position Report

Example of EMIS Employee Reports  

Example EMIS Employee Report with Errors

How to research the Error

There is only 1 error that will appear on the report to let them know that this employee will NOT be reported to EMIS:

...

The district will need to contact their ITC to let SSDT know.   The SSDT will use the SYSTEM/MONITOR/APP Log, (click here for DEBUGGING instructions (ITC use only) or/ ERROR in Level column) to find out which line the error was showing and be able to tell the district what field was causing the error.



Example of EMIS Position Report

Example of EMIS Position Report with errors:

How to research the error

There is only 1 error that will appear on the report to let them know that this employee will NOT be reported to EMIS:

...

The district will need to contact their ITC to let SSDT know.   The SSDT will use the SYSTEM/MONITOR/APP Log, to find out which line the error was showing and be able to tell the district what field was causing the error.


EMIS Calculating of Days for Reporting purposes

Type of DaySymbolFromEffect on AttendanceEffect on Absence
Work DayWJob CalendarAdd 1No Adjustment
HolidayHJob CalendarNo AdjustmentNo Adjustment
CalamityCJob CalendarNo AdjustmentNo Adjustment
Make-upMJob CalendarAdd 1No Adjustment
AttendanceATAttendanceAdd LengthNo Adjustment
SubstituteSBAttendanceAdd LengthNo Adjustment
VacationVAAttendanceDeduct LengthNo Adjustment
SickSIAttendanceDeduct LengthAdd Length
PersonalPLAttendanceDeduct LengthAdd Length
Professional LeavePRAttendanceNo AdjustmentNo Adjustment
Dock UnitsDOAttendanceDeduct LengthAdd Length
Jury DutyJDAttendanceDeduct LengthAdd Length
MilitaryMIAttendanceDeduct LengthAdd Length
CalamityCAAttendanceDeduct LengthNo Adjustment
HolidayHOAttendanceDeduct LengthNo Adjustment
OtherOTAttendanceDeduct LengthAdd Length



How the Data collector counts Absence Days

Attendance Days   Calendar Date

Absence Days    Calendar Date

Absence Days - Long Term Illness Days are 15 "Consecutive Absence Days".  This total needs to be entered on the Employee "Long Term Illness" field and the Data collector will return this value.

Emis Absence Adjustments that fall within the fiscal year

Emis Attendance Adjustments that fall within the fiscal year



How the Data Collector includes Credential ID

If there are spaces in the Credential ID for the EMIS Soap Service, it will retrieve a ZID number for the employee.  If the EMIS ID is spaces, it will use the Credential ID. If there is a Credential ID or EMIS ID, it will always use what is in USPSR.  

The Data collector does NOT use the employee's SSN, it will insert all 999999999's in there place.

Fatal in the Staff Collector

Things to look for in Staff collection failures:

...