Mapping Definitions That Synchronize a Shift, Break, or POU
The following table describes mapping definitions that synchronize a shift, break, or POU. The Siebel CRM fields in the table reside in the Integrated Shift Break POU business component. The Oracle Real-Time Scheduler fields reside in the Shift, Break, or POU component.
Siebel CRM | Oracle Real-Time Scheduler | Description | |
---|---|---|---|
Field Name |
Parent Element |
Field Name |
|
EntityReferenceID |
ShiftID |
||
Status |
boStatus |
||
Shift |
ShiftID |
||
crewName |
TechnicianID |
||
DueDate |
startDateTime |
||
EndTime |
completionDateTime |
||
EntityReferenceID |
taskId |
||
Type |
Value is hardcoded as SHIFT_BREAK in FMW. |
||
languageCode |
Value is set in FMW after looking up in the DVM. |
Siebel CRM | Oracle Real-Time Scheduler | Description | |
---|---|---|---|
Field Name |
Parent Element |
Field Name |
|
Entity Reference Id |
BREAK_COMPLETE |
BREAK |
If the STATUS is COMPLETE, then this integration maps these Siebel CRM fields to the BREAK_COMPLETE parent element. |
Due Date |
DATE |
||
This integration maps the following fields:
|
TIME |
||
Entity Reference Id |
BREAK_START |
BREAK |
If the STATUS is START, then this integration maps these Siebel CRM fields to the BREAK_START parent element. |
Due Date |
DATE |
||
This integration maps the following fields:
|
TIME |
Siebel CRM | Oracle Real-Time Scheduler | Description | |
---|---|---|---|
Field Name |
Parent Element |
Field Name |
|
Entity Reference Id |
POU_ARRIVED |
STOP_ID |
No more information available. |
This integration maps the following fields:
|
RSRC_ID |
Technician Id~Technician First Name Technician Last Name |
|
Shift |
SHIFT_ID |
No more information available. |
|
Due Date |
DATE |
This integration uses the following format: YYYYMMDD |
|
Start Time, UTC Offset |
TIME |
This integration uses the following format: HHMMZ+-HHMM |
|
Entity Reference Id |
POU _ COMPLETED |
STOP_ID |
No more information available. |
This integration maps the following fields:
|
RSRC_ID |
Technician Id~Technician First Name Technician Last Name |
|
Shift |
SHIFT_ID |
No more information available. |
|
Due Date |
DATE |
This integration uses the following format: YYYYMMDD |
|
End Time, UTC Offset |
POU _ DESPATCHED |
TIME |
This integration uses the following format:HHMMZ+-HHMM |
Entity Reference Id |
STOP_ID |
No more information available. |
|
Shift |
SHIFT_ID |
||
Entity Reference Id |
POU _ ENROUTE |
STOP_ID |
No more information available. |
This integration maps the following fields:
|
POU _ ENROUTE |
RSRC_ID |
Technician Id~Technician First Name Technician Last Name |
Shift |
SHIFT_ID |
No more information available. |
|
Entity Reference Id |
STOP_ID |
||
This integration maps the following fields:
|
POU _ STARTED |
RSRC_ID |
Technician Id~Technician First Name Technician Last Name |
Shift |
SHIFT_ID |
No more information available. |
|
Due Date |
DATE |
||
Start Time, UTC Offset |
TIME |
Z+- HH MM |
|
Entity Reference Id |
POU _ ACKNOWLEDGED |
STOP_ID |
No more information available. |
This integration maps the following fields:
|
No more information available. |
Technician Id~Technician First Name Technician Last Name |
|
Shift |
SHIFT_ID |
No more information available. |