Breaks Are Overlapping With Order 's Start Time And Complete Time In CLOSE_ALL_SHIFTS_RESPONSE In ORS v1
(Doc ID 2577048.1)
Last updated on MAY 02, 2022
Applies to:Oracle Real-Time Scheduler - Version 4.5.22 and later
Information in this document applies to any platform.
**Examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
ORS - Oracle Real-Time Scheduler
SP - Service Pack
On : 4.5.22 version, Mobile Communications Platform
Breaks are overlapping with order 's start time and complete time in CLOSE_ALL_SHIFTS_RESPONSE
In close all shift response for the shift ID, saw that order' start time and complete time is overlapping with the breaks start time and break end time. that's why breaks are not appearing in the routing sheet.
3 breaks planned for this shift but 2 of them are overlapping with orders start time and complete time.
Furthermore, order start time and complete time in ORS Database is not matching what is mentioned in close all shift response.
for example:- for order 82378732, start time -16:22 and complete time-16:30 in ORS DB but in close shift response , start time is 16:29 and complete time is 16:37.
STEPS TO RE-PRODUCE
- running processes: rmgw, smauto, plannerSwitch, 2 webservices ( rts_ws );
- webservice 1 sends request to delete a stop;
- at the same time webservice 2 sends request CLOSE_ALL_SHIFTS;
- last update in the database was prior to stop deletion ;
- as a result of STOP_DEL request a stop was deleted from a shift, shift re-optimized (breaks start time possibly changed it this point)and updates for a shift were sent by the scheduler to the switch;
- however updates for the shift were rejected by the Gateway as at this time the shift was updated in the database ( set to CLOSED as a result of CLOSE_ALL_SHIFTS request) and locked from the scheduler update
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