Booking Grid: Overadvertisement/Miscalculation?
(Doc ID 2961605.1)
Last updated on JULY 17, 2023
Applies to:
Oracle Fusion Cloud Field Service - Version 23.B.07 and laterInformation in this document applies to any platform.
Symptoms
Incorrect response of Booking Grid API.
In a sample scenario, the Booking Grid API response seems to be over advertising the available capacity in the bucket on a given date for a certain capacity area.
The Available Capacity screen in OFS shows that there is 1.07 hours available 08:30 - 12:00 and 1.45 hours available 12:30 - 16:30.
The Booking Grid API call is asking for 90min Duration and 40min Travel, equaling 130min or 2.1hrs (not including travel home).
Looking at the Dispatch Console, filtered to the group of Engineers that are being considered, the estimations on the 'Available Capacity' screen appear accurate. But those available hours are at opposite ends of the day and neither are large enough to allow a 2.1hr activity to fit in.
The Booking Grid, in this example, is returning available capacity for the 09:00 - 16:00, 09:00 - 12:30 and 12:30 - 16:00 time slots, when there isn't actually 2.1hrs of in all of them.
> 09:00 - 16:00 = Arguably there is 2.5hrs "available" capacity, but realistically there's not.
> 09:00 - 12:30 = 1.07 hrs... can't fit 2.1hrs
> 12:30 - 16:00 = 1.45 hrs... can't fit 2.1hrs
Why is the API offering all 3 timeslots when at least 2 of them cannot support the activity?
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |