Reload of Migrated Data for Activities

If you want to migrate activity data to a new application, then use Siebel Enterprise Integration Manager (EIM). For more information, see Siebel Enterprise Integration Manager Administration Guide.

The following fields are critical for migrating the activity data:

• Earliest Start

• Lock Schedule

• Service Region

• Duration

• Owner

• Status

• Latest Start

• Planned End

• Travel Time

• Lock Assignment

• Planned Start

• Work Time

When you load the ABS after migration, activities are scheduled according to the employee and service region schedule. If an activity can be scheduled for its original owner, planned start, and planned end, then no change is made to the activity data and the employee is scheduled for the activity. If the activity cannot be scheduled in this way, then the activity is rescheduled by using its Earliest Start and Latest Start fields. The Planned Start field, Planned End field, Owner field (if such a change is required), and Status field are updated for the activity.

To make sure that the migrated activities can be loaded into ABS and scheduled for the original owner, planned start, and planned end, the following conditions must apply:

• The Planned End field less the Planned Start field must equal the Duration field.

• The Work Time field plus the Travel Time field must equal the Duration field.

  Travel time is the average travel time for the service region, not the activity.

• No doublebooking of the original activities occurs.

  If doublebooking occurs, then an overbooked activity is rescheduled, unless both the Lock Assignment and Lock Schedule check boxes are selected for the activity.

• Original activities do not violate any of the constraints for the service region.

• Original activities can fit into the service region schedule and employee working hours.