Update HCM Resource Instance from Oracle Maintenance Cloud to Oracle Fusion Field Service

Oracle Fusion Field Service 25A now provides an enhanced version of Oracle Maintenance Cloud Accelerator for Oracle Fusion Field Service. Oracle Maintenance Cloud Accelerator for Oracle Fusion Field Service now supports:

  • Resource Instance Update
  • Enhancement in Work Order Update Data Flow
  • Asset Meter Reading Update

Resource Instance Update

  • When a resource instance is created in Oracle Maintenance Cloud without mapping the HCM person ID, the accelerator syncs the resource instance as a Oracle Fusion Field Service resource with the labour instance ID as the external ID.
  • When a resource instance is created in Oracle Maintenance Cloud and mapped with the HCM person ID, the accelerator syncs the resource instance as an Oracle Fusion Field Service resource with the CRM-party ID as the external ID.
  • When field service resource information is linked via the Oracle Fusion Field Service with the Oracle HCM Cloud Accelerator, the sync from Oracle Maintenance Cloud to Oracle Fusion Field Service ensures that the corresponding mobile worker data is updated with the resource instance ID, preventing duplication of information.
  • The resource integration flow now supports updating the resource instance to Oracle Fusion Field Service, even when the resource instance is mapped with an HCM Employee in Oracle Maintenance Cloud.
  • If an Oracle Fusion Field Service resource is created from HCM using the party ID as the external ID, the integration will update the Oracle Fusion Field Service resource with the Oracle Maintenance Cloud resource instance ID as a new resource separate property.
  • In scenarios involving work order operations and resource assignments between Oracle Fusion Field Service and Oracle Maintenance Cloud, where a technician is assigned in Oracle Fusion Field Service but not present as an instance in the Oracle Maintenance Cloud, the accelerator should update the work order operation resource as follows: 
    • If a work order operation is created without a resource but assigned to a technician with a mapped maintenance resource code (e.g., "maintenance tech B"), the work order update flow from Oracle Fusion Field Service to Oracle Maintenance Cloud will update the operation with "maintenance tech B" as the resource, leaving the resource instance field blank.
    • Similarly, if a work order operation is created with a resource ("maintenance tech A") but the actual technician present in Oracle Fusion Field Service is mapped with a different maintenance resource code ("maintenance tech B"), the work order update flow will update the operation with "maintenance tech B" as the resource, leaving the resource instance field blank.

The following new integration has been added to support the Resource Instance Update functionality:

ORCL-BA-OFS_MNT_EXTNL_RES_HLPR (Oracle OFS Maintenance External Resource Helper): Sub-integration to create Resource in Workorder for technicians that does not exist in Maintenance.

NOTE: Make sure the Oracle Fusion Field Service Resource property mwo_inst_resource_code is updated with the appropriate resource code value in Oracle Fusion Field Service Resource. The integration is unable to update the resource information in operation in the absence of this value. Make sure that the Oracle Fusion Field Service Resource property mwo_inst_resource_code is updated with the correct resource code value in Oracle Fusion Field Service Resource. Without this value, the integration is unable to update the resource information during operations.

NOTE:  1. The accelerator allows the update of a resource instance to a work order when an activity is assigned to a technician or when an activity is completed from Oracle Fusion Field Service. To enable the update of the resource instance as part of activity completion, set the lookup configuration ORCL-BRT-MNT-OFS-CONFIG -> SkipWOResInstanceUpdate to True.   This is the recommended flow if you are performing bulk operations such as activity assignment, movement, or rescheduling from Oracle Fusion Field Service. 2. If no value is configured for this lookup, the accelerator will default ORCL-BRT-MNT-OFS-CONFIG -> SkipWOResInstanceUpdate to False. 3. As a result, the resource instance details will be updated into the work order when an activity is assigned to a field resource from Oracle Fusion Field Service. 3. In the Gen2 version of the accelerator, the lookup is named ORCL-BRT-MNT-OFS-CONFIG -> SkipWOResourceReplace .

Enhancement in Work Order Update Data Flow

During the synchronization process for work order activities, the attributes "Work to be accomplished code" and "Repair transaction code" is synchronized with Oracle Fusion Field Service. Any changes made to these values during activity completion is updated in the Oracle Maintenance Cloud work order operation.

Two new custom properties have been added in Oracle Fusion Field Service to store the "Work to be accomplished code" and "Repair transaction code" synced from Oracle Maintenance Cloud to Oracle Fusion Field Service and vice versa:

  • When the value is provided at the maintenance operation level, it is synced to Oracle Fusion Field Service.
  • If values are explicitly provided at the resource level, they take precedence over the maintenance operation level during the sync from Oracle Maintenance Cloud to Oracle Fusion Field Service.
  • If the technician updates these fields during each activity completion:
    • The updates are shown in Oracle Maintenance Cloud resource and the operation level.
    • If there is more than one resource, the last updated value is stored at the operation level.

The Oracle Maintenance OFS Upsert Activity Helper [ORCL-BA-MNT_OFS_UPSERT_ACT_HELP] has been modified to sync the "Work to be accomplished code" and "Repair transaction code" from Oracle Maintenance Clous to Oracle Fusion Field Service.

The Oracle OFS Maintenance Operation Completion Helper [ORCL-BA-OFS_MNT_OP_CMPLT_HELPER] has been modified to sync the values captured in the custom fields in Oracle Fusion Field Service [mwo_repair_trans_code, mwo_work_accomp_code] to Oracle Maintenance Cloud upon activity completion.

Asset Meter Reading Update

The meter reading value is updated with the "Displayed Meter" value instead of "life to date" from Asset Meter to Oracle Fusion Field Service. This is because assets can sometimes replace meter readers or acquire assets that already have meters recorded, making the life to date value potentially inaccurate.

Business Benefit

This enhancement provides the next version of the Oracle Maintenance Cloud - Oracle Fusion Field Service accelerator with the following key functionalities:

  • Support the work order resource update flow with the resource instance ID if a work order is created without resources from the Oracle Maintenance Cloud.
  • Improve the performance of the inventory synchronization data flow.
  • Enhance the Oracle Maintenance Cloud accelerator resource data synchronization flow to update the field resource with the resource instance ID if employees are already updated via HCM.

Steps to Enable

Make sure you have updated the latest accelerator from OIC.

Tips And Considerations

Entity Level Mappings and API Mappings

For more information, refer to the documentation.

Using Oracle HCM - Oracle Field Service Accelerator & Oracle Field Service - Maintenance Cloud Accelerator together

Best practices for syncing user/resource information in Oracle Fusion Field Service using the Oracle HCM-Field Service accelerator and Oracle Fusion Field Service-Maintenance Cloud accelerator are as follows:

  1. Make sure you create Organizations and Buckets in the Oracle Fusion Field Service dispatch view in line with your business structure.
  2. Define buckets that correspond to the maintenance organization within Oracle Fusion Field Service.
  3. Use the maintenance organization ID as the external ID for the respective bucket.
  4. Map the HCM lookup table "Oracle_HCM_OFS_Resource_Bucket_Lookup" and link the external ID of the designated bucket where the employee should be updated as a mobile worker.
  5. Run the Oracle HCM-Field Service accelerator to initiate the HCM Employee sync data flow. This process generates mobile workers under the specified buckets in Oracle Fusion Field Service.
  6. Map the HCM Employee as a resource instance in the Oracle Maintenance Cloud.
  7. Run the Oracle Maintenance Cloud accelerator resource instance integration flow. This operation updates the existing Field Resource (HCM employee) with below properties in Oracle Fusion Field Service
    • mwo_resource_instance_id - Labour resource instance id from Oracle Maintenance Cloud
    • external_id_identified_by - Auto-generated value to indicate the source system that updates the property "mwo_resource_instance_id". The values can be ('FUSION_PARTY_ID' or 'MAINTENANCE_LABOUR_IDENTIFIER ' )
  8. Make sure that all incremental updates from HCM to Oracle Fusion Field Service continue to follow the current workflow.

By adhering to these best practices, the synchronization of user/resource information between Oracle HCM, Oracle Maintenance Cloud, and Oracle Fusion Field Service is optimized and streamlined.