FTE for Conf/Alloc shows a different value in allocation workbench than allocation on resource planIssue For users allocated for 1 FTE, their Conf/Alloc on the allocation workbench is showing 1.05 for June, even though on their resource plan their allocations all show 1. The allocation workbench calculates on-the-fly the values derived from Rest API. FTE takes the SUM by booking_type of the Allocated Hours for the GlideAggregate Resource Allocations under the Resource Plan, and divides by the working hours.CauseResource Workbench / Allocation Workbench will calculate the FTE On-The-Fly when it gets loaded. The calculation is: Resource Allocation Confirmed and Allocated Hours / (Average Daily FTE Property * Working Days in the Month) A more granular breakdown for each component example: Resource Allocation Confirmed and Allocated Hours: Looking at RPLNxxxxxx, the Resource Allocation for June 2022 is RALLOCxxxxxxxThe Confirmed/Allocated Hours field has a value of 167.2 Average Daily FTE Property: This comes from the User's average_daily_fte field. For user "TEST USER", this is not populated so we use the value defined on the "com.snc.resource_management.average_daily_fte" System Property This value is 7.6 Working Days in the Month: This comes from the User Schedule. "Stefan Milutinovic" does not have one so the Default of called "ABC Schedule" is used. The Default comes from the "com.snc.resource_management.default_schedule" System Property There are 21 available days in the Schedule Normally it would be 22 but there is a Child Schedule that blocked out 6-20-2022 for Juneteenth. The Resource Allocation and Resource Allocation Dailies for June were added on 2022-01-06 The Juneteenth child schedule entry was added after the fact on 2022-01-18 So, when the Resource Plan was allocated, the number of Working Days was considered to be 22 FTE = 167.2 / (7.6 * 22) FTE = 167.2 / 167.2 FTE = 1 In the allocation workbench it considers the update to the schedule: FTE = 167.2 / (7.6 * 21) FTE = 167.2 / 159.6 FTE = 1.0476190476 This rounds to 1.05 which you are seeing on the Allocation WorkbenchResolutionUsers should ideally finalize their schedule before allocating resources to prevent this issue. Since users were already allocated for Juneteenth, they will have to zero out the Resource Allocation Daily record for that date.