Person Entitlement Detail Loader functionality

Below is the information on how the PersonEntitlementDetail can be loaded and how the
PersonEntitlementDetail values will be used and calculate the entitlement for a person.

Entitlement Detail loader will be loading how much absence entitlement is used by a person with
respect to a plan.

Example:

PersonEntitlementDetail.zip

METADATA|PersonEntitlementDetail|PersonNumber|PlanName|WorkTermsNumber|ProcdDate|
StartDate|EndDate|PayFactor|Value

MERGE|PersonEntitlementDetail|NPer105|SK_QUAL_CAL|NWorkTerm107|2016/04/11|
2016/04/11|2016/12/31|100|-5

As per the above MERGE line, person number NPer105 has used 5 hours of absence for a plan
SK_QUAL_CAL as of date April 11 2016 with 100% pay factor.

Please Note:

VALUE must be in negative when loading used entitlements. Start date and End date must be given.

The entitlement calculation will be based on both start date and end date.

End date for calendar year can be mentioned as Dec 31 2016. (Calendar year end date).

There is no UI as of now to check the values loaded in the PersonEntitlementDetail Loader.

The above information when loaded through HDL will be inserted into
ANC_PER_PLAN_ENTRY_DTLS

Query to confirm if the HDL data load is successful:

select * from fusion.ANC_PER_PLAN_ENTRY_DTLS order by creation_date desc

Query to check if the entitlement will be considered when recording an absence as of Date
June 01 2016 for a particular person id and plan id:

select *

FROM fusion.ANC_PER_PLAN_ENTRY_DTLS PersonAbsPlanEntryDtlEO

where

(PersonAbsPlanEntryDtlEO.PERSON_ID = 100100008757649 )

AND (PersonAbsPlanEntryDtlEO.PLAN_ID =300100073739364) AND

(PersonAbsPlanEntryDtlEO.END_DATE >= to_date('01-JUN-2016','DD-MON-YYYY') )

AND (PersonAbsPlanEntryDtlEO.START_DATE <= to_date('01-JUN-2016','DD-MON-YYYY') )

Test in the UI to check if the entitlement detail data loader information is
being considered and calculated accordingly:

Below screenshot show the absence plan SK_QUAL_CAL that is used in the dat file is of qualification
plan with entitlement of 15 hours for 100 % pay factor:
Below screenshot for a person number NPer105 on recording an absence of date April 25th –
April 26th 2016 and the plan use of the absence recorded. Record an absence after above
PersonEntitlementDetail loader is successful.

The above absence duration is of 17 hours.

The entitlement under plan use tab is showing

10 hours -> 100% pay factor

7 hours -> 0% pay factor

As you can see, the 5 hours of data loaded through PersonEntitlementDetail is also considered
during entitlement calculation.
MERGE|PersonEntitlementDetail|NPer105|SK_QUAL_CAL|NWorkTerm107|2016/04/11|
2016/04/11|2016/12/31|100|-5

For an absence that was recorded on April 25 – April 26. The number of hours that was recorded
was 17 hours. The entitlement of the plan was 15 hours of 100% pay factor. The first five hours of
absence that was loaded through HDL was considered with 100% pay factor. The pending hours for
100% pay factor will be 10 hours.

So the available 10 hours for April 25 – April 16 is using 100% pay factor and rest is zero pay factor.

Please note:

If the HDL person entitlement detail load was not uploaded then the plan use for April 25 – April
26 would have been as below:

15 hours - > 100% pay factor

2 hours -> 0% pay factor.

Alternate way for loading entitlement from source to fusion system:

1, Load all the absences within 1 year period of go live data (If the plan period is 1 year rollback
period). This will compute all the entitlements for each of those absences. There is no need to
separately load entitlement in this case PersonEntitlementDetail HDL.

2, Create a DFF under Person or Assignment and mention the entitlement in the new DFF.

Write a entitlement formula to consider the DFF and compute the calculation accordingly.