How To End/disable An Engineer In ORS Through The Siebel-ORS Connector
(Doc ID 2000026.1)
Last updated on MARCH 01, 2018
Applies to:Siebel CRM Integration to Oracle Realtime Scheduler - Version 126.96.36.199.11 [IP2013] and later
Information in this document applies to any platform.
What is the suggested/correct approach for removing an engineer from being scheduled by ORS?
Currently we have employed 2 approaches:
1) move the Employee to a different Schedule; an empty one that has no planned work days. This is useful if we want to add ad-hoc Shifts to the engineer at a later stage.
2) set the end-date on the Employee; this ends the Shift Weekly subscription in ORS
However, if after doing one of these changes we wish to move the engineer to a non-ORS Service Region, or remove the engineer from a Service Region all together, the Mobile Worker and Crew will still be active in ORS as there is no integration message sent if the Employee does not belong to an ORS Service Region.
If we perform a Service Region rollback it appears that the Mobile Worker/Crew is disabled in ORS:
From the Siebel-ORS Connector Implementation Guide(...)
The Upsert_Employee operation sets the Employee Enable to DSBL for all the Crews and
Resources belong to the Service Area at Oracle Real-Time Scheduler.
How can we achieve the same for a specific Engineer without rolling back the entire Service Region?
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|