Table 2. Design Assumptions for Mastering Data
Entity |
Operation |
Master |
Synchronization Direction |
Descriptions |
Activity |
Create |
Siebel CRM |
One way |
Not applicable |
Update |
Siebel CRM and Oracle Real-Time Scheduler |
Two way |
Not applicable |
Delete |
Not applicable |
Not applicable |
Not allowed |
Employee |
Create |
Siebel CRM |
One way |
Not applicable |
Update |
Not applicable |
Delete |
Not applicable |
Not applicable |
Not allowed |
Employee Addresses |
Link or unlink |
Siebel CRM |
One way |
Not applicable |
Employee Skills |
Link or unlink |
Not applicable |
Addresses |
Create |
Not applicable |
Update |
Not applicable |
Delete |
Not applicable |
Not applicable |
Not applicable |
POU |
Create |
Siebel CRM |
One way |
Not applicable |
Update |
Siebel CRM and Oracle Real-Time Scheduler |
Two way |
Delete |
Not applicable |
Not applicable |
Break |
Create |
Siebel CRM |
One way |
This integration sends the break actual start, actual end date, and break status from the mobile application to Oracle Real-Time Scheduler. |
Update |
Siebel CRM and Oracle Real-Time Scheduler |
Two way |
Not applicable |
Delete |
Not applicable |
Not applicable |
Shift Template |
Create |
Siebel CRM |
One way |
Not applicable |
Update |
Delete |
Not applicable |
Not applicable |
Leaves |
Create |
Siebel CRM |
Not applicable |
Not applicable |
Update |
Delete |
Slot Group |
Create |
Oracle Real-Time Scheduler |
Replication |
This integration does not synchronize slot groups to Siebel CRM. You must manually recreate the slot group in Siebel CRM as a LOV. |
Update |
Delete |
Slots |
Create |
No synchronization occurs. |
Siebel CRM does not require this data. |
Update |
|
Delete |
Cost Profile |
Create |
Update |
Delete |
Service Region |
Create |
Siebel CRM |
One Way |
Oracle Real-Time Scheduler does not require this data. |
Update |
Delete |