Siebel Field Service Integration to Oracle Real-Time Scheduler Implementation Guide > How the Connector Synchronizes Activity and Related Data from Siebel CRM to Oracle Real-Time Scheduler > Integration Flows That Synchronize a Status from Siebel CRM to Oracle Real-Time Scheduler >

Integration Flow That Synchronizes Activity and Related Data from Siebel CRM to Oracle Real-Time Scheduler

The integration flow to synchronize activity and related data from Siebel CRM to Oracle Real-Time Scheduler is the same as the flow illustrated in Figure 7, with the following differences:

• If the status update is for activity data, then Siebel CRM makes a Web service call to the Update_Activity_Status method of the StatusUpdatesService Web service.
• The mediator forwards the request to the BPEL flow that handles status updates for activities.
• Instead of formatting received parameters, this flow uses a DVM to determine the status. For more information, see DVM That Synchronizes Activity and Related Data from Siebel CRM to Oracle Real-Time Scheduler.
• The BPEL flow calls the M1-ActivityStatusUpdatesFromHost Web Service.

DVM That Synchronizes Activity and Related Data from Siebel CRM to Oracle Real-Time Scheduler

Because the status in Siebel CRM does not necessarily map to the same status in Oracle Real-Time Scheduler, this integration keeps the mapping in a DVM in the middle tier. This integration chooses the Web service after it transforms the status to an Oracle Real-Time Scheduler status.

Table 30 describes the DVM to synchronize activity and related data from Siebel CRM to Oracle Real-Time Scheduler. For more information, see Configuring Domain Value Maps.

WSDL Operation That Synchronizes Activity and Related Data from Siebel CRM to Oracle Real-Time Scheduler

Siebel Field Service Integration to Oracle Real-Time Scheduler uses the Update_Activity_Status WSDL operation to synchronize activity and related data from Siebel CRM to Oracle Real-Time Scheduler.

For more information, see Integration Services.