Siebel Field Service Integration to Oracle Real-Time Scheduler Implementation Guide > Appointment Booking Integration > Integration Flows That Book an Appointment >

Integration Flow That Books or Reschedules an Appointment

Figure 4 illustrates the integration flow to book an appointment. The flow to reschedule an appointment is same as the flow to book an appointment. The is a synchronous request and reply flow. It uses Simple Object Access Protocol (SOAP) over Hypertext Transfer Protocol (HTTP) for all interactions with Siebel CRM and Oracle Real-Time Scheduler. For more information, see Mapping Definitions That Book, Confirm, Insert, or Reschedule an Appointment.

Figure 4. Integration Flow to Book or Reschedule an Appointment

Explanation of Callouts

The integration flow to book or reschedule an appointment includes the following steps:

1. Receives input from Siebel CRM.
2. Siebel CRM makes a Web service call to the Book_Appointment method of the ABSService Web service.
3. The mediator forwards the request to the BPEL flow.
4. The decision diamond represents a case statement. If the flow is a book appointment flow, then this integration performs the flow illustrated in Figure 4. For other flows, see the appropriate topic in this book.
5. To get slots from Oracle Real-Time Scheduler, the BPEL flow calls the M1-RouteAppointmentRequestToScheduler Web service method of Oracle Real-Time Scheduler.
6. If there is a network error, then this integration automatically attempts to communicate again with the Web service. A network error indicates that this integration cannot establish communication with the Oracle Real-Time Scheduler Web service.
7. The BPEL flow formats the slots that Oracle Real-Time Scheduler returns and sends them back to Siebel CRM.

For more information, see Integration Services..

How This Integration Locks Assignments and Schedules

This integration locks assignments and schedules in the following ways:

• If the Lock Assignment flag is set in the Web service input that the BPEL flow receives, then this integration sets the ROW_ID of the employee at the Allowed Crew Name field while sending the request to Oracle Real-Time Scheduler.
• If the Lock Schedule flag is set in the input, then this integration does not set the period of the request from the earliest start field and latest start field that the input specifies. Instead, it uses the planned start and planned end fields of the input. This integration uses a tolerance of plus or minus ten minutes for the duration of the time period.

Domain Value Map That Books or Reschedules an Appointment

A domain value map (DVM) is an SOA utility that facilitates the mapping of a list of values from one application to another application. In this integration, the Siebel application provides source values to Oracle Real-Time Scheduler. For example, assume the State value in a list of values includes the following values:

• CA in Siebel CRM
• California in Oracle Real-Time Scheduler

The DVM maps CA to California.

Table 3 describes the DVM that occurs in the book and reschedule appointment flow. This integration assumes that all DVMs are stored on the Oracle Meta Data Services (MDS). The Oracle MDS is a shared area in Oracle Fusion Middleware. It can reference a database or files. To support access to the same DVMs and cross references for multiple composites, this integration assumes Oracle MDS references a database. For more information, see Configuring Domain Value Maps.