Siebel Field Service Integration to Oracle Real-Time Scheduler Implementation Guide > How the Connector Performs a Service Region Data Transfer >

Integration Flow That Performs a Service Region Data Transfer

Figure 14 illustrates the integration flow that performs a service region data transfer. For more information, see the following topics:

• Integration Services
• Hook Points That Update Employee Data

Figure 14. Integration Flow to Perform a Service Region Data Transfer

Explanation of Callouts

The integration flow that performs a service region data transfer includes the following steps:

1. Siebel CRM calls the Web service that starts the process. It supplies to this Web service the Id of the service region that this integration must transfer. This Id is the ROW_ID of the service region in the Siebel database. Siebel CRM uses Simple Object Access Protocol (SOAP) over Hypertext Transfer Protocol (HTTP) to make this call.
2. The Business Process Execution Language (BPEL) flow sets the value of the Synchronization Status field of the service region record to Migration to ORS in progress. To perform this work directly on the Siebel database, it uses a database adapter that is connected to the Siebel database.
3. The BPEL flow extracts the name and description of the service region from the Siebel database. To query the Siebel database, it uses a database adapter that is configured in query mode and it uses the service region Id as the query specification.
4. To create an Oracle Real-Time Scheduler Service Area, the BPEL flow makes Web Service calls to Oracle Real-Time Scheduler.
5. Extracts all data that is related to the employee from the Siebel database. To extract all employee data, this flow joins all the relevant Siebel database tables. This data includes details of the start address, end address, associated skills, associated time zone, and so forth. It does not extract the following employee records:
   • Employee records that contain Y in the ORS sync flag
   • Employees records that contain a scheduling availability end date that occurs prior to the next day of the system time that is in effect during the data transfer
6. Reads the first employee record and determines the start address and end address based on the Start Shift From and End Shift At employee fields. If the values for these fields are Home, then the integration will consider the Home address. If the value of these fields is Depot, then the integration will consider the Depot address.

   The integration also validates whether the start and end address have latitude and longitude values.

7. If the address records are not present, then this integration does not synchronize the employee record in the Siebel database with the ORS database. Instead, it saves a synchronization error in the employee record in the Siebel database. This error states that the start address and the end address are missing.
   1. This integration will insert the Employee record along with Start and End Address, Employee Skills, and Employee Exception Hours into the ORS database by calling the UPSERT_EMPLOYEE method of the AdminDataManagement_EBF composite.
8. Repeats Step 6 for each subsequent employee record until it finishes processing all employee records.
9. After this flow processes all employee records, the BPEL flow gets the activity records and associated data from the Siebel database, except for activities that meet any of the following conditions:
   • Any activity in the service region whose ORS synchronization status is N and the status is not Done, Cancelled, or Completed.
   • Any activity that is expired. An activity is considered not to have expired if any of the following situations are true:
     • The latest start date for the activity will occur at any time in the future.
     • The latest start date is null.
     • The planned end date will occur in the future.
     • The planned end is null.

       This integration considers any time that occurs after the system time that is in effect during the data transfer as a future date.

10. To write data for each activity record to the ORS database, it uses the Upsert_Activity operation of the AppointmentBookingSystemSBLORS_EBF composite. This flow uses a native binding to the AppointmentBookingSystemSBLORS_EBF composite.
11. Saves the result of the synchronous call in the Siebel activity record.
12. Saves the overall status of the data transfer in the Synchronization Status field of the Service Region. It uses the following logic:
    • If this flow successfully transfers all employees, addresses, and activities, then it does the following work:
      • Sets the Synchronization Status field to the following value:

    >>>>>Successfully migrated to ORS

    • Inserts the following value in the Engine field:

    >>>>>ORS

    • If this flow cannot successfully transfer at least one employee, address, or activity, then it does the following work:
      • Sets the Synchronization Status field to the following value:

    >>>>>Partially migrated to ORS

    • Inserts the following value in the Engine field:

    >>>>>ORS

    • If this flow encounters an exception, then it does the following work:
      • Sets the Synchronization Status field to the following value:

    >>>>>Transfer to ORS aborted due to exception

    • Does not change the value in the Engine field