1. Field Service Integration to Oracle Real-Time Scheduler Implementation Guide
  2. Explanation of Callouts

Explanation of Callouts

This integration performs the following work for most hook points:

  1. Hook Point 1. The input for hook point 1 is the Siebel request message. For example, the Siebel input for the appointment booking flow is absInput. The output of hook point 1 is the extended Siebel request message.

  2. Hook Point 2. The input for hook point 2 is the extended Siebel request message to the composite and the Oracle Real-Time Scheduler request message for the operation. The composite that calls the hook point determines this operation. The output for hook point 2 is the Oracle Real-Time Scheduler requested message for the called operation. For more information, see Hook Point Operations That This Integration Calls.

  3. Hook Point 3. The input for hook point 3 is the Oracle Real-Time Scheduler response message. The composite that calls the hook point determines this output. For example, the Siebel output for the appointment booking flow is absReply. The output for hook point 3 is the Siebel response message.

  4. ORS Web Service. The external Web service that the composite calls.