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:
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.
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) .
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.
| Info |
|---|
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. |
...
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.
...
An error indicates the AESOP absence did not pull in successfully into ESS, meaning, in this example, you won’t be able to view the leave request in ESS until we determine the error and once resolved, the next scheduled job will then pull it in successfully, allowing the user to view the leave request in ESS. Possible error messages include:
'Error creating leave request with conf #xxxxxxxxx;Employee not found'
The employee was not found in ESS. Look at the associated employee identifier field and determine why the employee is not in ESS. Possible reasons could be the employee isn’t in USPS, the (user) wasn’t added in ESS, or the user in ESS has the wrong employee identifier attached to it.
‘Error creating leave request with conf #xxxxxxxxx;No Leave data found for Employee’
This is an indication. User created an OT (other) absence in AESOP and it is not pulling into ESS.
This may indicate that leave data has not been synced with ESS. If you sync the leave data and it still doesn’t resolve the issue, please ensure the employee is eligible for leave in USPS. The leave balances must exist in USPS. Even though if the employee may not be eligible for leave, it is a requirement that leave data information must exist for the employee in ESS (set it up with 0 balances if this employee is not eligible for leave). In USPS>Core>Leaves-New, create the default leaves with 0 balances. Once the (template) leave balances exist in USPS, sync leave in ESS and then the AESOP OT absence will pull in successfully.