Master Data Synchronization from Oracle Maintenance to Oracle Fusion Field Service
The maintenance organization defined in Oracle Maintenance is created as a bucket in Oracle Fusion Field Service as part of the integration. You can configure the organization codes in the Parent Resource's field mwo_resource_sync_orgs. Based on this configuration, the accelerator syncs the relevant Maintenance Organizations into Oracle Fusion Field Service, as follows:
- Maintenance Resources are created as work skills.
- Maintenance work centers are created as work zones.
- Maintenance labor resource instances are created as mobile worker.
- [Oracle Field Service only] The synchronization process from Oracle Maintenance Cloud to Oracle Fusion Field Service ensures that Human Capital Management (HCM) employees created as 'resource instances' in Oracle Maintenance Cloud are updated as field resources in Oracle Field Service.
- There are scenarios regarding 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. Accelerator should update the work order operation resource as
described below.
- If a work order operation is created without a resource but assigned to a technician with a maintenance resource code mapped (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 mapping table given here lists the mapping between Labour
Instance in Oracle Maintenance Cloud and Oracle Field Service as configured
in the accelerator.
Fusion Object Oracle Fusion Field Service Object LaborInstance.PartyId ExternalID LaborInstance.LaborInstanceId ExternalID (If partyID is absent),
mwo_resource_instance_id
LaborInstance.ResourceCode mwo_inst_resource_code
- Maintenance Operations sync as activity types in Oracle Fusion Field Service. This table describes the field-level mapping between operation and activity type.
A mapping table is available in the accelerator for configuring these attributes:
| STANDARD_OPERATION_CODE | ACTIVITY_LABEL | ACTIVITY_NAME | SEGMENTABLE | SEGMENT_MIN_DURATION | SEGMENT_MAX_DURATION | Default_Flag |
|---|---|---|---|---|---|---|
| DRAIN_OIL | drain_oil | Drain oil | False | True | ||
| CHANGE_OIL | drain_oil | Drain oil | False | False | ||
| REP_ENG | repair_engine | Repair Engine | True | 30 | 120 | True |
Here are the details for the table:
- STANDARD_OPERATION_CODE - The Standard Operation Code defined in Oracle Maintenance.
- ACTIVITY_LABEL - Activity type label to be mapped in Oracle Fusion Field Service against the Operation Code.
- ACTIVITY_NAME - Name of the activity type to be created in Oracle Fusion Field Service if the activity type doesn't exist.
- SEGMENTABLE - Whether this activity type is segmentable or not.
- SEGMENT_MIN_DURATION - Minimum Duration for segmentable activity type.
- SEGMENT_MAX_DURATION - Maximum duration for the segmentable activity type.
- Default_Flag: The accelerator uses this flag while creating a follow-up activity from Oracle Fusion Field Service. There can be scenarios where multiple operation codes are mapped against the same activity type. Based on the default flag value, the accelerator identifies the standard operation code and creates a new operation under the work order in Oracle Maintenance. Here's an example: The standard operation code 'DRAIN_OIL & CHANGE_OIL is mapped to the activity type 'drain_oil' as shown in the earlier table. When a user wants to create a follow-up activity from Oracle Fusion Field Service of type 'drain_oil', they can select the activity type as 'drain_oil'. The accelerator creates a new operation, 'DRAIN_OIL', under the current work order in Oracle Maintenance, because the default flag for the standard operation, DRAIN_OIL, is set to 'True'.
If the work order contains a new operation that isn't mapped in the earlier table, it's synced as a default activity.
Field Mapping : Standard Operation to Activity Type
| Oracle Maintenance Field | Description | Oracle Fusion Field Service Field | Field Type | Description | Mandatory |
|---|---|---|---|---|---|
| Operation Description | Human readable description of Standard Operation Code, mapped against activity type group name | Activity type group name | Name of the activity type group | M | |
| Operation Type | Classification of Standard Operations in Oracle Maintenance, mapped against activity type group which serves a similar purpose against activity types | Activity type group label | Label of activity type group | M | |
| Standard Operation Code | Internal unique code used as identifier for activity types | Activity type label | Label of the activity type | M | |
| Standard Operation Name | Readable name displayed in the user interface for activity types | Activity type name | Name of the activity type | M | |
| Status of the activity type can be identified based on the inactive date | Status | Status of the activity (active or not) | M |
Field Mapping : Resource Instance to Oracle Fusion Field Service Resource
| Oracle Maintenance Field | Description | Oracle Fusion Field Service Field | Field Type | Description | Mandatory |
|---|---|---|---|---|---|
| Resource Instance Id | Resource Id | The unique identifier of the resource in Oracle Field Service. | M | ||
| Resource Instance Name | Resource Name | The name of the resource. | O | ||
| Resource Code | Work Skill Label | The label of work skill which is assigned to the mobile worker representing the Resource. | M | ||
| Resource identifier | user login | Identifier used for user sign in. | |||
| Status | Status | Allowed Values: active, inactive |
Field Mapping : Work Center to Oracle Fusion Field Service Resource
| Oracle Maintenance Field | Description | Oracle Fusion Field Service Field | Field Type | Description | Mandatory |
|---|---|---|---|---|---|
| Work Center code | Unique code of the work center | Resource Id | The unique identifier of the resource in Oracle Fusion Field Service. | M | |
| Work Center Name | Name of the work center | Resource Name | The name of the resource. | O | |
| Status of the work center can be identified based on the inactive date. | Status | Allowed Values: active, inactive |
M |
Field Mapping : Equipment to Oracle Fusion Field Service Resource
| Oracle Maintenance Field | Description | Oracle Fusion Field Service Field | Field Type | Description | Mandatory |
|---|---|---|---|---|---|
| Work Center code | Parent Resource Id | The unique identifier of the parent resource. | O | ||
| Resource instance name | Name of the resource instance (Equipment type) | Resource Name | The name of the resource (tool). | O | |
| Resource instance identifier | Identifier of the resource (Equipment type) | Resource Id | The unique identifier of the resource in Oracle Fusion Field Service. | M | |
| Business Unit | Organization (Organization Unit) | The label of an organization unit under this resource that needs to be mapped. | O | ||
| Resource type | The type of the resource - Tool. | M | |||
| Status of the resource instance can be identified based on the inactive date. | Status | Allowed Values: active, inactive |
M |