Siebel Field Service Guide > Scheduling Using Oracle Real-Time Scheduler Version 2.1 > About Appointment Booking for Siebel Field Service Integration to Oracle Real-Time Scheduler 2.1 >

User Interface Elements for Activity Schedule Detail View

Some fields and other user interface features for this integration are included in the Activity Schedule Detail view, or developers can add these interface elements to this view and other views. Some of these fields are available only in business components. When these fields apply to your company's requirements, developers can display the fields in the application user interface and populate field values.

The user interface elements for this integration include the following items:

• Time Zone. The time zone of the service region. This time zone must also be the time zone of the specified account address. Values sent to Oracle Real-Time Scheduler 2.1 must represent UTC (Universal Time Coordinated) offsets, adjusted accordingly to the daylight saving time, such as UTC - 8 for Pacific Standard Time and UTC - 7 during Daylight Saving Time). (This field is only available in the business component.)
• Slot Group. The group of slots. For more information about slots, see the documentation for Oracle Real-Time Scheduler 2.1 in About Documentation for Oracle Real-Time Scheduler 2.1.
• Account Address Pick Applet. A MVG applet that includes the Latitude and Longitude fields. Oracle Real-Time Scheduler 2.1 has geocode requirements. For more information about addresses, see Administering Addresses.
• Error Reason. The reason for the error. If a job is disabled in Oracle Real-Time Scheduler 2.1, then the error reason is populated in this field. This field maps to the Warn Text field for a stop in Oracle Real-Time Scheduler 2.1.
• Latitude and Longitude. The geocode coordinates. Oracle Real-Time Scheduler 2.1 has geocode requirements. For more information about addresses, see Administering Addresses.
• Min Offset. The minimum offset in minutes required from start of the parent activity to start the child activity for bound jobs. For more information about bound jobs, see Scheduling Appointments with Bound Jobs.
• Max Offset. The maximum offset in minutes required from start of the parent activity to start the child activity for bound jobs. For more information about bound jobs, see Scheduling Appointments with Bound Jobs.
• Parent Activity Id. The row ID of the Parent activity for bound jobs. For more information about bound jobs, see Scheduling Appointments with Bound Jobs.