Page Comparison

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

...

• What if the employee has a new position in USPS ? If that is eligible for leave? Do I need to update the Employee External ID 1 in AESOP?

  • Yes, 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? I can’t add more than one position in the Employee External ID 1 field in AESOP, correct?

  • That is correct. If they are multiple buildings assigned to their employee record in AESOP and they can create absences for any of these buildings and do not want to limit to one position (in USPS), they will leave the ‘Employee External ID 1’ field blank in the AESOP employee record. Instead,

    • When creating the absence in AESOP, they are required to select a building(s). If all USPS positions have the same building (IRN

    in (USPS/ESS

    • ), it 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) .

  • If all positions have different IRNs

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

      When creating the absence in AESOP, if they select more than one building to charge the absence to (morning in building A and afternoon in building B), if the USPS position have the same building IRNs, it will apply the absence to the first position it encounters containing that building IRN in ESS (whether it’s active or inactive, non-archived or archived position). So in this case, it will create two leave requests in ESS, one for the AM for the position tied to building A and one for the PM for the position tied to Building B.

Issue: The ‘School’ grid under Synced Absence Management Data contains rows of mismatched data. How do I troubleshoot these?

...

• If ‘Is Matched’ contains an ‘X', the AESOP Master Data>School>General Information ‘External Number’ doesn’t match the ESS Building Code’s IRN. On the grid above, AESOP’s External Number is displayed in the ‘External ID’ column. ESS schools are linked through the USPS Building Code>Building IRN property (which is synced to ESS when a position is synced).

• Resolution: User should ensure the External ID matches the USPS Building Code’s Building IRN. The numbers must be identical (leading zeroes need to be accounted for). If an update is made in USPS, the position sync in ESS must be performed.

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

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