Siebel Field Service Guide > Scheduling Using Oracle Real-Time Scheduler Version 1.0 > About Employee Administration >

Sending Employee Data to Oracle Real-Time Scheduler 1.0

Employee data is sent to Oracle Real-Time Scheduler 1.0 in the following cases:

• When the employee is associated with a service region that Oracle Real-Time Scheduler 1.0 configured for scheduling, and
• When the employee has Start Home Address and End Home Address data that is populated with addresses that are associated with geocodes.

  NOTE:  When employee data is sent to Oracle Real-Time Scheduler 1.0, the employee's Can Work and Preferred zones are the same as the employee's service region. The employee is associated with an Oracle Real-Time Scheduler 1.0 view that has the same name as the service region.

If you change an employee's name in the Siebel application, then a new employee (driver) record is created in Oracle Real-Time Scheduler 1.0. The unique key for an employee record in Oracle Real-Time Scheduler 1.0 contains the employee name. The unique key has the following format: SiebelEmpRowID~FirstNameLastName (the Siebel employee's row ID concatenated with the employee's last name and first name, with the tilde (~) symbol between them). The business administrator must manually end-date the earlier employee record in Oracle Real-Time Scheduler 1.0 to avoid confusion stemming from multiple records for the same employee.