EOS Issues

Owned by Kevin Stevenson
Mar 18, 2019
2 min read
  1. Default Earnings End date - NBAJOBS
  • TPT Default Earnings, when applying data from EOS into Banner, the default Earnings End date is not entered into Default Earning tab.  We must go into the record and manually enter the end date after the job record has applied into Banner.
    • Wait time is approximately three to five minutes before we can manually update.
    • It does not impact other employees types the ePAF was simply built incorrectly as it does not reflect current data entry practices for TPT.
    • This occurs regardless of the job change reason (NHIRE, RHIRE, ADDJB etc.)
    • This was attempted to be fixed prior to implementation but was refused by IT due to the short window to go-live.

Solution:  Add Default Earnings End Date to current ePAF


2.  PEAEMPL

Setting up an employee that has prior employment history: EAs have to go manually update several fields. If the eClass is not updated, a Vital Error will be created (eClass on PEAEMPL does not match Job record). Question: (Does the workflow change the terminated status to active?)

    • This currently automated for new hires only
    • Specific fields are I-9 received date which is two-fold: choose from drop down (not received, received, temporary) and enter date manually.
    • Not sure if this can be automated if a value already exist for rehires, also adjunct are often hired into other departments and changes may or may not be needed.


3. PEAEMPL Record ERB Code

ERB Code is not entered when applying the demographic form information Banner, the Suggestion: Is it possible to develop a script to check, FTE and E-Class to see what the code would be? 

    • ERB CODE is entered for new hires (first time to UNM) only based on FTE.


4. TPT Job Record Error

If the base job record was used prior to the start date of the assignment being applied through EOS, an error occurs.  “Job Begin Date does not match original Job Begin Date”.  To correct the error we look at the error in EOS to get the epaf transaction number.  We then go into Lobo Web, look up the epaf number, click on “return to originator”, click on the Update button, change the Job Begin Date to match the value in the Current Value column, click the Save button and then click the Submit button. 

Solution: Match the logic in the current RHIRE ePAF.


5. UNMJobs to EOS Workflow

If the hire date on the Onboarding page passes before we can change the applicant status from “Recommend for Hire” to “Hired”, UNMJobs changes the Type field to “Internal”.  If we change the Applicant Status to “Hired”, the information does not feed over to EOS.  We must then manually enter the information into Banner.