Explanation of Callouts

1. Receives input from Siebel CRM.

2. Determines if the Exception Id is present in the input data and then does one of the following:

   • If the Exception Id is present, then it refers to the cross reference table to verify whether the Exception has been transferred to Oracle Real-Time Scheduler.

   • If not, then the integration will call the Siebel Inbound web service to get the Exception Details along with Exception hours and transfer the Exception to Oracle Real-Time Scheduler by invoking another composite. An entry will be made in the Cross Reference table for this Exception Id.

3. Calls M1-ShiftWeeklyTemplateMaintenance Service to create Shift Weekly Template in Oracle Real-Time Scheduler based on the following logic:

   • For each day, integration will consider the Shift Start time of the record with Shift Start Flag set to Y and consider the Shift End Time of the last record of that same day.

   • Any time gap between the same day records will be considered as Breaks and the Shift Weekly Template will be updated accordingly at Oracle Real-Time Scheduler.

4. Sends the output from the M1-ShiftWeeklyTemplateMaintenance Web Service to Siebel CRM.

The following illustrates the integration flow to update or insert a work calendar. This flow uses Simple Object Access Protocol (SOAP) over Hypertext Transfer Protocol (HTTP) for all interactions with Siebel CRM and Oracle Real-Time Scheduler.