Maintenance management workflow approval stuck at manager level in ofc-22d

ERP Oracle Fusion Cloud
, , , , , , , ,
1

We’re experiencing a critical issue with our maintenance management workflow in Oracle Fusion Cloud 22d. Maintenance work orders requiring manager approval are getting stuck at the approval step and not progressing beyond that point.

The workflow configuration shows the approval step is set to route to the asset manager role, but notifications aren’t being sent and the workflow status remains ‘Pending Manager Approval’ indefinitely. We’ve verified the manager assignments are correct in the system and the notification settings appear properly configured in the workflow builder.

This is causing significant delays in our asset maintenance operations as urgent work orders are sitting in the queue for days without any action. Has anyone encountered similar workflow approval issues with maintenance management? We need to understand if this is a configuration problem with the approval step setup or a notification settings issue.

system 2

Based on all the symptoms you’ve described, I believe this is a multi-faceted configuration issue affecting your maintenance workflow. Let me walk you through a systematic resolution approach that addresses all three key areas: workflow configuration, approval step setup, and notification settings.

Workflow Configuration Analysis: First, navigate to Setup and Maintenance > Search ‘Manage Maintenance Work Order Workflow’ and open your current workflow definition. The issue likely stems from the approval step configuration where the routing rules aren’t properly evaluating the manager assignment. Check the following:

  1. Verify the approval step’s participant type is set to ‘Role’ and specifically points to ‘Asset Manager’ or your custom maintenance manager role
  2. Ensure the assignment logic is ‘Any’ not ‘All’ - this is critical because ‘All’ requires every person in the role to approve
  3. Check that the approval step has a proper timeout configured (recommend 3-5 days) with an escalation path to a backup approver

Approval Step Troubleshooting: The core problem appears to be in how the approval step resolves the approver. In BPM Composer, examine the approval task’s human task definition:

  • Open the .task file in your workflow project
  • Check the participant assignment logic in the ‘Assignment’ tab
  • Verify the XPath expression used for manager resolution is correctly referencing the work order’s asset manager attribute
  • Common issue: The expression might be looking for ‘AssetManagerId’ but your data model uses ‘MaintenanceManagerId’

Run this diagnostic query to verify manager assignments:

SELECT work_order_number, asset_id, manager_id, manager_name
FROM maintenance_work_orders
WHERE approval_status = 'PENDING'

If manager_id is NULL, that’s your problem - the workflow can’t route to a null value.

Notification Settings Resolution: For notifications, you need to verify three layers:

  1. System Level: Setup and Maintenance > Manage Administrator Profile Values > Search ‘Workflow Notification’ - ensure the mailer is configured and running
  2. Role Level: Setup and Maintenance > Manage Workflow Notifications > Select ‘Asset Manager’ role - verify ‘Email Notification’ is enabled
  3. User Level: Each manager must have notifications enabled in their user preferences (Navigator > My Account > Notification Preferences)

Additionally, check the BPM notification template. Navigate to Enterprise Manager > SOA Infrastructure > Business Rules > Notification Rules. Ensure the ‘MaintenanceApprovalNotification’ rule is active and the email template is correctly configured with the manager’s email attribute.

Immediate Fix: To unblock your stuck workflows, you can manually reassign them:

  1. Log into BPM Worklist as a workflow admin
  2. Go to Administration > Task Configuration
  3. Search for stuck tasks by status ‘ASSIGNED’ and age > 2 days
  4. Use ‘Reassign’ to push them to the correct managers

For a permanent fix, update your workflow configuration to include a catch-all error handler that automatically escalates to a maintenance supervisor role if the manager assignment fails. This prevents future workflows from getting stuck.

After making these changes, test with a new maintenance work order and monitor the workflow progress in the BPM Worklist. The combination of proper approval step configuration and notification settings should resolve your issue completely.

This draft is based on general Oracle Fusion Cloud knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.

3

I’ve seen this before with maintenance workflows. First thing to check is the notification preferences for the manager role. Go to Setup and Maintenance > Manage Workflow Notifications and verify that the asset manager role has notifications enabled for approval tasks. Sometimes the role is configured correctly but individual users have disabled email notifications in their preferences.

4

Thanks for the suggestion. I checked and notifications are enabled at the role level. However, I noticed in the workflow configuration that the approval step has a timeout setting of 0 days. Could this be causing the workflow to skip the approval entirely or get stuck? Also, the escalation path seems to be pointing to a generic admin role rather than a specific escalation manager.

5

The timeout setting of 0 days shouldn’t cause it to get stuck, but it means there’s no automatic escalation happening. What I’d recommend is checking the BPM worklist directly. Log in as one of the managers and navigate to the BPM Worklist application to see if the approval tasks are actually appearing there. Sometimes the workflow engine routes tasks correctly but the notification email fails, so the tasks are waiting in the worklist but users don’t know about it. Also verify your SMTP configuration is working properly for outbound notifications.

robert_user 6

Tested this on OFC-22D and navigating to Manage Maintenance Work Order Workflow, then correcting the manager assignment routing rules, immediately resolved our stuck approval issue.

7

We had a similar issue last year. In our case, the problem was with the approval step configuration itself. The workflow was trying to route to a role that had multiple assignees, but the assignment logic was set to ‘All’ instead of ‘Any’. This meant every person in that role had to approve, and if even one person was inactive or didn’t have proper access, the workflow would hang. Check your approval step’s participant assignment and make sure it’s configured correctly for your use case.

8

Another thing worth checking - in 22d there was a known issue with workflow notifications when the approval hierarchy wasn’t properly synced with HCM data. If your managers are defined in HCM and you’re using position-based approvals, make sure the ‘Synchronize Approval Hierarchy’ scheduled process is running regularly. We had to manually trigger it to fix stuck workflows.

10

Good point about the hierarchy sync. Also check if there are any custom approval rules or AMX extensions modifying the standard workflow behavior. Sometimes customizations can interfere with the notification trigger.