The first XML file that is created contains the OrganizationEmployment object. The process reads thru the Master List of employees generated by the Initial Process. Key fields (elements):
|
Element |
How data is extracted |
|---|---|
|
Person ID |
Certificate Record - Teaching Certificate Number Teaching Certificate Defined from User Specific Parameters Profile – Field “Teaching Certificate Type/Class/Code” |
|
Birth Date |
HR Demographics – Birth Date |
|
Last Name |
HR Demographics – Last Name |
|
First Name |
HR Demographics – First Name |
|
Middle Name |
HR Demographics - Middle Name |
|
|
HR Demographics – Email with domain from HR Master Profile if email does not already contain domain |
|
Gender |
HR Demographics – Gender |
|
Aboriginal Status |
HR Demographics – Ethnic Code. If blank, extract will report code 02 (choose not to declare) |
|
Phone Number |
HR Demographics – Phone 1 and 2. Process will define Phone 1 as Type of “Home” and Phone 2 as Type of “Mobile” Process will define formats of both phone numbers as ‘NA’ (North America). |
|
Contract Identifier |
Builds a Contract Identifier based on the employee no, and contract type and iteration of that contract type in the case of multiple contracts.
Examples: Suzy Q. (employee 12345) has 2 assignments:
Identifiers would look like 12345_01_01 and 12345_02_01
Johnny B. (employee 67890) has 2 assignments:
Identifiers would look like 67890_02_01 and 67890_02_02 |
|
Contract Type |
Assignment Type > Translation Table |
|
Percent Time Employed |
Location FTE |
|
Start Date |
Start date is set as either the start date from asof prompt or the assignment start date if it occurs after the asof assignment start date prompted value. For example, the assignment asof start date prompt was defined to September 1, 2023 and the employee’s assignment started September 1, 2015. The employee’s start date will be extracted as September 1, 2023. Another example, if the employee’s assignment started October 1, 2023. The employee’s start date will be extracted as October 1, 2023. |
|
End Date |
Assignment end date. |
|
Separation Reason |
Assignment Ending Reason > Translation Table |
|
Affiliation |
Assigned Position Bargaining Unit > Translation Table |
|
Employment Position |
Assigned Position > Translation Table |
|
Position Subtype |
Assigned Position > Position User Defined field “Subtype” |
|
Classification |
Assignment Salary > 3rd and 4th digits of the most recent salary grid that falls within EEP extract date range specified.
If assignment bargaining unit is translated to 03, then the classification prints 08. |
|
Step |
Assignment Salary > last 2 digits of the most recent salary grid that falls within EEP extract date range specified. If assignment bargaining unit is translated to 03, then the classification prints blank. |
|
Salary |
Annual salary related to the assignment salary amount, calculated based on position pay cycle and pay type. |
|
Assessment Coordinator |
Assigned Position > Position User Defined field “Coordinator?” |
Note about accented characters: Accented characters will be allowed. The XML will be valid and run as is. But the matching names may have issues. Since the identification is based on person id and birthdate, when districts import to MOE, the process may give users a warning as “Educator names cannot be changed via XML. Contact SPTRB to change the name”. You could ignore them for these specific cases. Opening the XML with accented characters will give an error but can be viewed/edited in notepad.
The process excludes any assignments where system is expecting to be translating the data and cannot find a translation. This is reported in a spreadsheet which contains all the employee assignments that belonged to employees that were on the master list, but which had a combination of location, position or contract type, bargaining unit, assignment ending reason not mapped to the MOE values. For many cases, this is valid information to be bypassed (i.e. an assignment with a position of Noon Hour Supervision would not be reported).