Siebel 2018:

Bookshelf Home | Contents | Index | PDF

Siebel Field Service Integration to Oracle Real-Time Scheduler Implementation Guide > Mapping Definitions > Mapping Definitions That Manage an Appointment >

Table 86. Mapping Definitions That Synchronize a Shift, Break, or POU
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.

Table 87. Mapping Definitions That Synchronize a Break
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: End Time UTC Offset		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: Start Time UTC Offset		TIME

Table 88. Mapping Definitions That Synchronize a POU
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: Technician Id Technician First Name Technician Last Name		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: Technician Id Technician First Name Technician Last Name		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	No more information available.
Entity Reference Id	POU _ ENROUTE	STOP_ID	No more information available.
This integration maps the following fields: Technician Id Technician First Name Technician Last Name	POU _ ENROUTE	RSRC_ID	Technician Id~Technician First Name Technician Last Name
Shift		SHIFT_ID	No more information available.
Entity Reference Id		STOP_ID	No more information available.
This integration maps the following fields: Technician Id Technician First Name Technician Last Name	POU _ STARTED	RSRC_ID	Technician Id~Technician First Name Technician Last Name
Shift		SHIFT_ID	No more information available.
Due Date		DATE	No more information available.
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: Technician Id Technician First Name Technician Last Name		No more information available.	Technician Id~Technician First Name Technician Last Name
Shift		SHIFT_ID	No more information available.

Siebel Field Service Integration to Oracle Real-Time Scheduler Implementation Guide		Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.