1. Field Service Integration to Oracle Real-Time Scheduler Implementation Guide
  2. Mapping an Activity Status From Siebel CRM to Oracle Real-Time Scheduler

Mapping an Activity Status From Siebel CRM to Oracle Real-Time Scheduler

This topic describes how to edit the SBL_to_ORS_ActivityStatusMapping DVM. You can create and configure many different status values for activities in Siebel CRM. However, Oracle Real-Time Scheduler includes a fixed set of predefined status values, each of which Oracle Real-Time Scheduler designs for a particular stage in routing. You must map statuses from the Siebel environment to the corresponding statuses from Oracle Real-Time Scheduler in the middle tier. You can use DVMs to modify and commit changes without having to stop Oracle Fusion Middleware. You use an activity status mapping with status update flows. A field service technician can use the mobile application to change the status of an activity. During an update, this integration uses the appropriate status mapping in the DVM to map the change that the field service technician makes, and then calls Oracle Real-Time Scheduler.

Columns You Use to Map an Activity Status

To map an activity status, you use the following columns:

  • Column 1: Siebel

  • Column 2: ORS

Requirements for Mapping an Activity Status

If you use the SBL_to_ORS_ActivityStatusMapping DVM, then you must make sure your mapping meets the following requirements:

  • The data in the Siebel column must be unique. Multiple Siebel statuses can map to the same status in Oracle Real-Time Scheduler. However, there must not be more than one entry in the map with the same Siebel status.

  • The status is case-sensitive. If the Siebel status is ABC, then a DVM row must exist that includes a Siebel column value of ABC. This integration treats other values as different statuses. Example values include ABC, abc, or any other combination. The same rule applies for Oracle Real-Time Scheduler. Because all valid Oracle Real-Time Scheduler statuses are in upper case, the ORS column must use uppercase and valid status values. This integration treats a case mismatch between a domain value map (DVM) column and the data that the column corresponds to as a status mismatch. This situation can result in a rejected message. For lists of valid activity statuses, see the Documentation Sources for Configuring Oracle Real-Time Scheduler.

DVM Entries That Map an Activity Status

Siebel Column ORS Column

Schedule

M1SH

Dispatched

M1DS

Cancelled

M1CA

Declined

M1DC

Acknowledge

DISPATCHED

Enroute

M1EN

In Progress

M1ON

Done

M1CO