Debugging and Troubleshooting

This topic let's you resolve some common errors that might occur while integrating Oracle Fusion Field Service with Oracle Maintenance using the accelerator.

This topic lists the errors, their symptoms, and solutions to resolve the errors:

• Work Order Sync from Oracle Maintenance to Oracle Field Service
• Schedule updates from Oracle Field Service to Oracle Maintenance
• Inventory Reservations from Activity Installed Inventory
• Operation Completion
• Resource Sync or Organization Sync

Work Order Sync from Oracle Maintenance to Oracle Fusion Field Service

Symptom: Work Order isn't synced to Oracle Fusion Field Service

Error: NA

Solution: Make sure all the prerequisites for work order sync are done and the work order statuses to be synced to Oracle Fusion Field Service are added in the lookup, ORCL-BRT-MNT-OFS-CONFIG with key, WOStatusToSyncOFSActivity.

Schedule updates from Oracle Fusion Field Service to Oracle Maintenance

Symptom: Activity schedules aren't updated

Error: Work Order Update failed due to Lock issue in Oracle Maintenance Work Order/Work Order Operation update API

Solution: The accelerator includes the retry logic for all the schedule updates from Oracle Fusion Field Service to Oracle Maintenance. The integrations in which retry is implemented are as follows:

Integration	Default Retry Count	Default Delay in milliseconds
Oracle OFS Maintenance Activity WO Sync Helper	3	5000
Oracle OFS Maintenance WO Operation Update Helper	3	5000
Oracle OFS Maintenance Work Order Update Helper	3	5000
Oracle OFS Maintenance Create Res Copying Helper	3	5000
Oracle OFS Maintenance Update WO Status	3	5000
Oracle Maintenance Op Material Update Helper	3	5000

Try to increase the delay between the retries by changing the integration property "delayInMilliseconds" in the listed integration. Use these steps and rerun the integration from OIC:

1. Navigate to Monitoring > Integrations > Integrations.
2. Click the integration that's showing the error and resubmit it as shown in the screenshot.

   

3. Click the Resubmit button.

   

Inventory Reservations from Activity Installed Inventory

Inventory Reservation fails intermittently

Error:

When inventory is reserved simultaneously, it can trigger locks on the API.

Solution: The accelerator includes the retry logic for all the schedule updates from Oracle Fusion Field Service to Oracle Maintenance, the API is called a maximum of three times with an interval of 5 seconds between each attempt.

Operation Completion

Operation is not completed, after the last activity in the operation is completed in Oracle Fusion Field Service.

Error:

• There could be a resource transaction or material transaction error during the completion of any activity in the operation.

• The Source System defined in the lookup code "MNTSourceSystemCode" isn't available in Fusion.

• There was an error in a previous operation due to the errors listed earlier.

Solution:

• Review the resource and material transactions corresponding to the operation in Oracle Maintenance and complete it manually.
• Verify/create the Source System in Oracle Sales. For more information, see Set Up Source Systems.

Resource Sync or Organization Sync

Resource Instances and Oracle Maintenance Organizations aren't present in Oracle Fusion Field Service

Error: The Resource Type for Oracle Maintenance Organization and/or the Resource Instance isn't configured in the lookup

Solution: Make sure BucketResourceType and LaborResourceType values are configured in the lookup.

Resource Instances and Oracle Maintenance Organizations aren't present in Oracle Fusion Field Service

Error: The ParentResourceId is not configured in the lookup

Solution: Make sure ParentResourceId is configured in the lookup and it corresponds to a resource that can contain child resources in Oracle Fusion Field Service.