Does anyone have or done a work around until this bug is implemented into ORACLE? This issue has been previously clarified in Bug 2853506 by the Oracle development team. The Reservation Timefence profile option is based on Calendar Days and not Working Days. This is the standard and intended functioning of the application.
Enhancement Request Bug 6639191: RESERVATION TIME FENCE DOES NOT USE WORKING DAY CALENDAR
A new enhancement request has been submitted for consideration of expanded functionality around this behavior. Users are reporting the reserve orders process does not look at the organizational "working day" calendar when applying/calculating the reservation time fence. This results in inconsistent results when the time fence crosses non-working days. This enhancement request is submitted for consideration of expanding the Reserve Orders process to allow the Reservation Time Fence future benchmark date to be either "calculated" based on working days OR calendar days.