Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Issue: AESOP absence is not reflecting the correct ESS (USPS) position when the absence is pulled into ESS.

  • Listed below are the chain of events that take place to make this determination:

    1. When ESS pulls in the absence, it will first look to see if there is a (USPS) position # in the ‘Employee External ID 1’ in the employee’s AESOP employee record. If there is, it will apply the absence to that position # in ESS.

    2. If ‘Employee External ID 1’ is blank in AESOP, ESS will then look at the AESOP school building (IRN) assigned to the employee’s absence and will apply the absence to the first position it encounters for the employee containing that building IRN in ESS (whether it’s active or inactive, non-archived or archived position) .

    3. If there is no building IRN tied to that position in (USPS) ESS, ESS will apply the absence to the #1 (USPS) position (active or inactive, non-archived or archived) for that employee in ESS.

  • Resolution: Enter the USPS position number in the user’s employee record in AESOP.

Only employees who are having an issue with the AESOP absence being applied to an incorrect position should be corrected by entering the position # in the ‘Employee External ID 1’ of the AESOP employee record. ESS-995 will improve the behavior on how the AESOP absences are being applied to the position in ESS.

  • What if the employee has a new position in USPS? If that is the only position eligible for leave, please update the ‘Employee External ID 1’ field in their AESOP employee record so that the absence pulled from AESOP will reference the correct USPS position.

  • What if the employee has more than one position in USPS that is eligible for leave?

Issue: Absence Management Data Import View Grid - Processed Message Errors

  • Error creating leave request with conf #xxxxxxxxx;Employee not found.

    • There are 3 properties used from Absence Management to determine the length of an absence (if daily or hourly conversion is required)

      • Shift Type

        • Full Day

        • Half Day AM / PM

        • Custom

      • Employee Hours Per Day

      • Duration Absence

      • If any of these fields are missing, an error will be added to the Process Message on the Absence Management Sync view

    • Flow of Processing is now

      • If Shift Type is Full Day AND Unit is Daily

        • Leave Request will be created for 1 day of leave

      • If Shift Type is Full Day AND Unit is Hourly

        • Leave Request will be created for employee hours per day

      • If Shift Type is Half Day AM/PM AND Unit is Daily

        • Leave Request will be created for 0.5 day of leave

      • If Shift Type is Half Day AM/PM AND Unit is Hourly

        • Leave Request will be created for duration

      • If Shift Type is Custom AND Unit is Daily

        • duration / employee hours per day

          • If result > 1 day, 1 day will be created

      • If Shift Type is Custom AND Unit is Hourly

        • Leave Request will be created for duration

  • No labels