Siebel Field Service Integration to Oracle Real-Time Scheduler Implementation Guide > How the Connector Performs a Service Region Rollback >
Integration Flow That Performs a Service Region Rollback
Figure 14 illustrates the integration flow that performs a service region rollback.
Figure 14. Integration Flow to Perform a Service Region Rollback
|
Explanation of Callouts
The integration flow that performs a service region rollback includes the following steps:
- Sets the rollback progress:
- Sets the synchronization description field of the service region record in the Siebel database to the following value:
>>>Rollback from ORS in progress
- Gets the name of the service region from the Siebel database.
- Extracts all employees who belong to the service region whose scheduling availability end date does not occur prior to the system time and date that is in effect at the point of the rollback.
- For each employee that this flow extracts, calls the Upsert_Employee operation of the AdminDataManagement_EBF composite.
- 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.
- If the Upsert_Employee operation returns a success, then this flow does the following in the employee record in the Siebel database:
- Extracts all activities in the service region. It uses the same rules that it uses during a data transfer to identify the activities to extract from the database. The activity cannot occur in the past, and it cannot have already been serviced.
- For each activity extracted, calls the Cancel_Appointment operation of the AppointmentBookingSystemSBLORS_EBF composite.
- If the cancellation is successful, then this flow sets the following fields of the activity:
- Synchronization status to Activity Cancelled in ORS
- Sync Success flag to N
- Sets the service region status to the following value and sets the engine name to iLog:
Rollback from ORS complete
This flow uses a direct database update or query for all interactions with the Siebel database.
|