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

Integration Flow That Confirms an Appointment


The integration flow to confirm an appointment is the same as the flow to book or reschedule an appointment illustrated in Figure 4 except for the following differences:

  • Siebel CRM makes a Web service call to the Confirm_Appointment method of the ABSService Web service.
  • To confirm the chosen slot, the BPEL flow calls the M1-MaintainActivityByHost Web service method of Oracle Real-Time Scheduler.
  • The BPEL flow sends the reply that it receives from Oracle Real-Time Scheduler to Siebel CRM. The reply from Oracle Real-Time Scheduler can be a success or failure.

For more information, see Integration Services and Mapping Definitions That Manage an Appointment.

DVM That Confirms an Appointment

Table 4 describes the DVM to confirm an appointment. For more information, see Configuring Domain Value Maps.

Table 4. DVM That Confirms an Appointment
DVM
Description

SBL_ORS_Parameter_Definition.dvm

This integration uses the following DVM parameters:

  • ORS-Confirm Slot MaxCost
  • ORS-Confirm Slot MaxCost-<SRV_REGION_NAME>

    If SRV_REGION_NAME is missing, then this integration uses only ORS- Confirm Slot MaxCost.

  • ORS-FindShift
  • ORS-FindShift-<SRV_REGION_NAME>

    If SRV_REGION_NAME is missing, then this integration uses only ORS-FindShift.

DVM- SBL_ORS_Endpoint_Definition.dvm

This integration uses the Activity Maintenance DVM parameter.

 

Siebel Field Service Integration to Oracle Real-Time Scheduler Implementation Guide Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.