OTIP MPL Result FTE Enhancement Process Overview

OTIP MPL Result FTE Enhancement Process Overview

GOAL: To provide a wholistic overview of the setup, workflow and outcome of using the Result FTE to automate FTE – Leave FTE to improve the accuracy of reporting on the OTIP Position File. 

This enhancement applies for Benefit Provider = OTIP/CUPE/EWAO/OCEW/RBC 

Link to Forum Topic: https://support.edsembli.com/en/support/discussions/topics/8000017204 

Link to Community Feedback Forum: https://support.edsembli.com/en/support/discussions/topics/8000017222 

Process Overview:

BOARD CONTROL > GENERAL TABLES > SITE CONFIGURATION

**Configure ‘Use Result FTE for OTIP MPL’ = Yes**

IMPORTANT NOTE: Upon installation of the patch, this value will be defaulted to N, so that boards who do not wish to make use of this automation require no action. 

Whereas boards who desire this automation simply make a one-time config change. 

BENEFIT > BENEFITS > IMPORT/EXPORT > GENERATE HRIS FILE > OTIP

**Benefit Provider = OTIP > File Type = Test > Submit**

Note: The purpose of generating this file is to establish a baseline before new changes are made. Here we can see how EID’s needing to be changed generated in the first place. 

PROCESS > COMPLETED > MEMBER FILE

Sample EIDs: xxxxxx, yyyyyyy, zzzzzzzz, xyzxyzx, yzxyzxy

PROCESS > COMPLETED > POSITION FILE

Sample EIDs: xxxxxx, yyyyyyy, zzzzzzzz, xyzxyzx, yzxyzxy

EMPLOYEE POSITIONS

select EMPLOYEE_ID, EMP_GROUP_CODE, POSITION_START_DATE, POSITION_END_DATE, ACTUAL_FTE, BENEFIT_PLAN from EC_EMPLOYEE_POSITIONS

where EMPLOYEE_ID in ('xxxxx', 'yyyyyy', 'zzzzzz', 'xyzxyzx')

and POSITION_START_DATE > '2021-09-01'

**All 5 Employees have 1.0 FTE on Current Position with Benefit Plan = OTIP**

STAFFING > APPROVED LEAVE > EID

**Configure various Approved Leaves for the Sample EIDs mentioned above**

Note: The Reason Code used for the Approved Leaves must be defined under Benefit Provider Configuration > OTIP/CUPE/EWAO/OCEW/RBC > Code Type = LEAVE or else it will not be considered in the MPL File. 

Approved Leaves

select EMPLOYEE_ID, EMP_GROUP_CODE, JOB_CODE, REASON_CODE, LEAVE_FTE, LEAVE_START_DATE, LEAVE_END_DATE * from EC_EMPLOYEE_LEAVES

where EMPLOYEE_ID in ('xxxxx', 'yyyyyy', 'zzzzzz', 'xyzxyzx')

and LEAVE_START_DATE > '2023-09-01'

**All 5 Employees now have their Approved Leaves entered**

Board Control > Benefits > Benefit Provider Configuration > OTIP

**The applicable Reason Codes to choose when testing Approved Leaves**

BENEFIT > BENEFITS > IMPORT/EXPORT > GENERATE HRIS FILE > OTIP

PROCESS > COMPLETED > MEMBER/POSITION/LEAVE FILE

MEMBER

**All Work Status + Effective Dates updated. Bottom Example EID was 0.00 Leave FTE entry, no change is expected**

POSITION

**All FTE has updated accordingly. Example EID #2 removed from POS File since ‘Result FTE’ = 0 **

LEAVE

**All Leave Reason, Effective Dates and Leave FTE generate accordingly**

OUTCOMES:

SAMPLE EID 1: FTE = 1, LEAVE FTE = 0.75. Result FTE = 1-0.75 = 0.25

SAMPLE EID 2: FTE = 1, LEAVE FTE = 1. Result FTE = 1-1 = 0

SAMPLE EID 3: FTE = 1, LEAVE FTE = 0.5. Result FTE = 1-0.5 = 0.5

SAMPLE EID 4: FTE = 1, LEAVE FTE = 0.95. Result FTE = 1-0.95 = 0.05

SAMPLE EID 5: FTE = 1, LEAVE FTE = 0.00. Result FTE = 1-0 = 1

IMPORTANT NOTE: This procedure functions the exact same for CUPE, OCEW, EWAO and RBC Benefit Provider configuration. 

Simply repeat the above steps for Employees under a different Benefit Provider to see the results.