Activity - Work Order Data Flow

Here's how the activity schedule information from Oracle Fusion Field Service is updated in Oracle Maintenance using the accelerator.

After you've created the activities, Oracle Fusion Field Service can route the activities to appropriate mobile workers under the maintenance organization bucket with the help of routing. After running the routing plans, activities are scheduled and assigned to the right mobile workers. The accelerator updates the activity schedule information, which includes the activity start time, end time, and resource (mobile worker) to the work order operation.

Activity start date is updated as the actual start date of the operation resource.
Activity end date is updated as the actual end date of the operation resource.
Mobile Worker is updated as Labor resource instance of the work order operation resource.
When there are multiple resources associated with an operation, the operation's start date is the start date of the first operation resource (based on the sequence number). The end date of the operation is the end date of the last operation resource (based on the sequence number).
If there's no resource associated with the operation, the activity start date is updated as the actual start date of the operation, and the activity end date is updated as the actual end date of the operation.
When a resource instance is created in Maintenance Cloud without mapping HCM person ID, accelerator will sync the resource instance as Oracle Fusion Field service resource with labor instance ID as external ID.
When a resource instance is created in Maintenance Cloud mapped with HCM person ID, accelerator will sync the resource instance as Field service resource with CRM-party ID as the external ID.
When field service resource information is linked via the Oracle HCM-Oracle Field Service accelerator, the sync from Oracle Maintenance Cloud to Oracle Fusion Field Service ensures that corresponding field resource data is updated with the resource instance ID, preventing any duplication of information.
The resource integration flow now supports the resource instance update to Oracle Field Service, even when the resource instance is mapped with an HCM Employee in the Oracle Maintenance Cloud.
The integration will update Field service resource with the maintenance cloud resource instance id as a new resource separate property if the field service resource is created from HCM using partyID as external ID.
For multi-segment activities:
- The start date and time of the first segment are mapped as the operation/resource start date and time. Similarly, the end date and time of the last segment are assigned as the operation/resource end date and time.
- The mobile worker assigned with individual segments is assigned as the resource instance of the work order operation resource. If different mobile workers are assigned to different segments, multiple resource instances are created in Oracle Maintenance against the same resource.
If the activity was rescheduled or moved manually by a user in Oracle Fusion Field Service, the new start date, end date, and mobile worker information are updated to the work order operations.

Optimization of Activity to Work Order Data Flow

A new lookup called EventsForWOUpdate has been introduced in the accelerator to manage updates to work orders based on various activity events in Field Service. This lookup accepts the following activity event values: activityCreated, activityStarted, activityUpdated, activityMoved, activityNotDone, and activityCanceled. By default, this lookup is empty, and the accelerator updates only the work order during the activity completion event. To receive updates based on other activity events, you can configure the lookup with the appropriate activity events.

For example, if you want to receive work order updates when an activity is created or started (in addition to completion event), you can add activityCreated and activityStarted to the lookup.

Additionally, another lookup called ActivityMoveConditions has been introduced to manage activity move scenarios. You can use this lookup to control work order updates for specific activity move conditions. If no value is specified in the lookup, the accelerator allows only bucketToResource and resourceToBucket conditions by default. This lookup accepts the following values:

bucketToResource
resourceToResource
resourceToBucket
bucketToBucket

For instance, if you want to receive work order updates when an activity is moved from one bucket to another, you can add the bucketToBucket value to the ActivityMoveConditions lookup. For details about supported activity events, see Activity Events.

Note: If you are an existing user of the accelerator, ensure these lookups are present in the latest version. If these lookups are not available, the accelerator updates the work order only during the activity completion event.

To configure the events in the accelerator, create the following entries in the ORCL-BRT-MNT-OFS-CONFIG lookup and specify the required activity events and move conditions to enable work order updates:

Name	Descritpion
EventsForWOUpdate	Enter one or more Field Service activity events, separated by commas. Supported values include, activitySuspended, activityMoved, activityStarted, activityNotDone, activityCanceled, activityCreated, and activityUpdated.
ActivityMoveConditions	Enter one or more move conditions, separated by commas. Supported values include, bucketToResource, resourceToBucket, resourceToResource, and bucketToBucket. If no value is specified, only bucketToResource and resourceToBucket will be handled by default.

Default behavior:

The EventsForWOUpdate lookup does not contain any values by default. As a result, the accelerator updates the work order only during the activity completion event.
The ActivityMoveConditions lookup also does not contain any values by dault. In this case, the accelerator updates the work order only for the bucketToResource and resourceToBucket move conditions.

Optimization of Meter Reading Updates to Activity

Asset meter synchronization update from Maintenance Cloud to Field Service can be controlled using the EventsForMeterUpdate lookup. This lookup accepts the following activity event values:

activityCreated
activityStarted
activityUpdated
activitySuspended

For example, if you want to sync the latest meter readings from Maintenance Cloud only when an activity is created or started, you can update the lookup with the values activityCreated and activityStarted.

To configure the events in the accelerator lookup, create the following entry in the ORCL-BRT-MNT-OFS-CONFIG lookup and specify the required activity events to enable the work order updates:

Name	Description
EventsForMeterUpdate	Enter one or more Field Service activity events, separated by commas. Supported values include, activitySuspended, activityStarted, activityCreated, and activityUpdated.

By default, meter readings are updated in Field Service as part of the activity creation event if the EventsForMeterUpdate lookup does not contain any values. For more information on supported activity events, see Activity Events.

Optimization of Descriptive Flexfield (DFF) Updates to Work Orders

Descriptive Flexfield (DFF) updates from Field Service to Maintenance Cloud occur automatically as part of the activity completion process. If you want to receive DFF updates for other activity events, you can configure the EventsForDFFUpdate lookup. This lookup accepts the following activity event values:

activitySuspended
activityStarted
activityNotDone
activityCanceled
activityCreated
activityUpdated

To enable DFF updates for specific activity events, add the corresponding values to the lookup. For example, to receive updates when an activity is started or updated, set the lookup to include activityStarted and activityUpdated. For more information on supported activity events, see Activity Events.

You can receive updates for both Work Order (header, operation, and operation resource levels) and Asset DFFs using this lookup. For more details on supported activity events, see OFSC Activity Events.

To configure the events in the accelerator lookup, create the following entry in the ORCL-BRT-MNT-OFS-CONFIG lookup and specify the required activity events:

Name	Description
EventsForDFFUpdate	Enter one or more Field Service activity events, separated by commas. Supported values include, activitySuspended, activityStarted, activityNotDone, activityCanceled, activityCreated, and activityUpdated. If the lookup is empty, DFF updates will occur only on the activityCompleted event.

By default, the EventsForDFFUpdate lookup does not contain any values. In this case, the accelerator updates DFF data in Maintenance Cloud only during the activity completion event.

Note:

If multiple resource instances are scheduled as part of Oracle Fusion Field Service routing, but one or more resource instances aren't defined for that resource, then the integration doesn't update any resource instance details in the work order.
If there is no value configured for this look up accelerator will take the value of the ORCL-BRT-MNT-OFS-CONFIG->SkipWOResInstanceUpdate as false. And the resource instance details will get updated into the work order when an activity is assigned to a field resource from Oracle Fusion Field Service.
If you do not want to update the resource instance to a work order operation, for OIC Gen 2 or package customers, you can configure the flag SkipWOResourceReplace as True in the ORCL-BRT-MNT-OFS-CONFIG lookup table.