Siebel Innovation Pack 2015: IMapping Run-Time Parameters

This topic describes how to edit the SBL_ORS_Parameter_Definition DVM. This integration uses this DVM as the configuration file to extract parameters in the run-time environment. This DVM provides a lookup source for default values, endpoint configuration, and so forth. This integration uses all flows that map run-time parameters.

Columns You Use to Map Run-Time Parameters

Entries You Must Include to Map Parameters

Table 80 lists the entries you must include in the SBL_Expertise_Code_Definition DVM. You must use the case and spaces for each parameter as they appear in Table 80. You cannot change the case, and you must include the spaces.

Table 80. Entries You Must Include in the SBL_ORS_Parameter_Definition DVM
Parameter	Description
ORS-Request Slot MaxCost	Used to book an appointment. If this integration requests a slot for an activity from Siebel CRM, then it sends the value of this parameter as the maximum allowed cost for that activity. The value can be any decimal number greater than 0.1. 999999 is an example value of the ORS-Request Slot MaxCost parameter.
ORS-No of Slots	Defines the number of slots to display on a slot request from Siebel CRM. The value can be any integer greater than 1. 15 is an example value of the ORS-No of Slots parameter.
ORS-Confirm Slot MaxCost	Used to confirm an appointment. If the cost to confirm an activity for a particular shift is greater than the cost specified in ORS-Confirm Slot MaxCost, then Oracle Real-Time Scheduler does not allow the activity. The value can be any decimal number greater than 0.1. 999999 is an example value of the ORS-Confirm Slot MaxCost parameter.
ORS-FindShift	If the ORS-Confirm Slot MaxCost parameter value is too high, then the scheduler rejects it and then examines the ORS-FindShift parameter to determine if the scheduler must locate another shift that meets the maximum cost that the ORS-Confirm Slot MaxCost parameter specifies. The value for the ORS-FindShift parameter is YES or NO. If the value is YES, then the scheduler attempts to find a suitable shift for that activity that costs less than the value in the ORS-Confirm Slot MaxCost parameter. NO is an example value of the ORS-FindShift parameter.
ORS Default Service Area with Srv Regn	Determines if this integration forces Oracle Real-Time Scheduler to associate with a Service Area, and only that Service Area, the same name as the service region. If the ORS-Default Service Area with Srv Regn parameter is: YES, then when this integration synchronizes the employee to Oracle Real-Time Scheduler from Siebel Service, it associates the Service Area with the request. NO, then this integration does not send the Service Area mapping from Oracle Fusion Middleware to Oracle Real-Time Scheduler. You must use the Oracle Real-Time Scheduler user interface to map the Service Areas. This integration retains any mapping you do in the Oracle Real-Time Scheduler user interface even when it performs a resynchronization from Siebel Service. YES is an example value of the ORS-Default Service Area with Srv Regn parameter.
ORS-Relative Rank of DEFAULT Expertise	Specifies the relative rank of the default expertise level. If this integration creates a new attribute in Oracle Real-Time Scheduler from Siebel Service, even if no expertise level is specified for the attribute, then it creates a proficiency named default for the attribute. The value in the parameter specifies the relative value of the proficiency. If this integration sends the attribute with proficiency at some point in the future, then it compares the rank of this default expertise to other expertise ranks in order to determine whether the default proficiency is lower in precedence or higher in precedence. For more information, see Mapping Oracle Real-Time Scheduler Expertise to Siebel CRM Skills. The value 900 is an example value of the ORS-Relative Rank of DEFAULT Expertise parameter.
Siebel_ID_of_MWM_Base_TimeZone	Specifies the ROW_ID of the Timezone in Siebel CRM corresponding to the Base Timezone at Oracle Real-Time Scheduler. It gets the ROW_ID of the Timezone in Siebel CRM which corresponds to the Base Timezone defined in Oracle Real-Time Scheduler and place that value here. For example, if the Base timezone in Oracle Real-Time Scheduler is PST, then gets the ROW_ID of the Pacific Time Zone record from Siebel CRM.

Optional Entries You Can Include to Map Parameters

Table 81. Optional Parameters for SBL_ORS_Parameter_Definition DVM
Parameter	Description
ORS-Request Slot MaxCost-ServiceRegionName	Defines parameters for the service region. For example: ORS-FindShift-ServiceRegionName where: ServiceRegionName is the name of the service region. For example: ORS-FindShift-New York City. If you do not configure these service region parameters on the DVM, then this integration uses the default parameters that are described in Entries You Must Include to Map Parameters. Any service region parameter that you define on the DVM modifies the default parameter. Note the following examples: 9990 is an example value for the ORS-Request Slot MaxCost-ServiceRegionName parameter 20 is an example value for the ORS-No of Slots-ServiceRegionName parameter. 7777 is an example value for the ORS-Confirm Slot MaxCost-ServiceRegionName parameter. YES is an example value for the ORS-FindShift-ServiceRegionName parameter. NO is an example value of the ORS-Default Service Area with Srv Regn-ServiceRegionName parameter.
ORS-No of Slots-ServiceRegionName
ORS-Confirm Slot MaxCost-ServiceRegionName
ORS-FindShift-ServiceRegionName
ORS-Default Service Area with Srv Regn-ServiceRegionName
Default Batch Size - Employee	Sets the number of records that this integration groups before it saves them to the Siebel database. For more information, see About the Default Batch Size - Employee Parameter. 100 is an example value of the Default Batch Size - Employee parameter.
Default Batch Size - Activity	Determines the synchronization batch size for activities. This usage is similar to the Default Batch Size - Employee parameter. For more information, see About the Default Batch Size - Employee Parameter. The value 100 is an example value of the Default Batch Size - Activity parameter.
Default Batch Size - Address	Determines the synchronization batch size for addresses. This usage is similar to the Default Batch Size - Employee parameter. For more information, see About the Default Batch Size - Employee Parameter. The value 100 is an example value of the Default Batch Size - Address parameter.
Default Batch Size - Geocoding	Determines the batch size to retrieve geocodes for multiple addresses. The batch geocoding flow waits until the number of geocodes that this integration holds in memory reaches the value in the Default Batch Size - Geocoding parameter, and then saves them in the Siebel database. This usage is similar to the Default Batch Size - Employee parameter. For more information, see About the Default Batch Size - Employee Parameter. The value 100 is an example value of the Default Batch Size - Geocoding parameter.

About the Default Batch Size - Employee Parameter

During a service region data transfer, this integration extracts employees from the Siebel database and attempts to synchronize them with Oracle Real-Time Scheduler, one record at a time. It stores the status of the synchronization in the Siebel database, along with the timestamp of the synchronization operation. This status describes whether the synchronization is successful, not successful, and the reasons for any failed synchronization.

To set the number of records that this integration groups before it saves them to the Siebel database, you can use the Default Batch Size - Employee parameter. For example, if Default Batch Size - Employee is 100, then the service region data transfer flow waits until the synchronization status in memory is 100 records, and then writes these records to the Siebel Database.

If the overall total number of records is less than 100, then this integration saves the records to the Siebel database when it reaches the total.

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