Capture Workflow Rejection Reasons

Workflow approvers can now select one or more rejection reasons when rejecting the workflow from the change object, in-app notification and overview page. This feature is supported for change orders, change requests, problem reports, and corrective actions. The selected reasons will be displayed in the History tab and the workflow history.

Rejection Reason When Signing Off from the Object

Rejection Reasons When Signing Off from the In-App Notification

Rejection Reason Captured in History Tab

Rejection Reason Captured in the Workflow History

You can also add this attribute to your OTBI report for approval details.

Rejected Reason Attribute in Change Order Approval Details Subject Area

An Example of a Change Order Report for Specific Rejected Reasons

The following list outlines the feature benefits for your business:

• You can define a standardized process to capture the rejection reasons values at a workflow type level. This allows for better reporting and analysis of the workflow rejections.
• Users can select one or more rejection reasons as part of the workflow.

Steps to Enable

• You must must modify ChangeOrderApprovalTask in BPM to Require reasons for rejection.

             Configure Require Reasons For Rejection in BPM

• You must modify the Manage Workflow Rejection Reasons lookup to add values that can be added to different Workflow Types.

            Create Rejection Reason Lookup Values

• After the lookup values are added, you can add the rejection reasons to the workflow type that it applies to.

Associated Rejection Reasons to Change Type

Tips And Considerations

• You can't specify rejection reasons from your email notification.
• Inheritance of the reasons for the type will be honored in the change type.

Key Resources

• Oracle Fusion Cloud SCM Using Product Development Guide, available on the Oracle Help Center.
• Oracle Fusion Cloud SCM Using Product Master Data Management Guide, available on the Oracle Help Center.
• Oracle Fusion Cloud SCM Implementing Product Management Guide, available on the Oracle Help Center.

Access Requirements

Users who are assigned configured job roles that contain these privileges are able to access this feature:

You should have Approve Item Change Order (EGO_APPROVE_ITEM_CHANGE_ORDER_PRIV), (Monitor Product Management Workflow Objects (ACA_MONITOR_PRODUCT_MANAGEMENT_WORFLOW_OBJECTS_PRIV) and one of the following privileges:

For change orders:

• View Change Order (ACA_VIEW_CHANGE_ORDERS_PRIV) or
• Manage Change Orders (ACA_MANAGE_CHANGE_ORDERS_PRIV)

For change requests:

• View Change Request (ACA_VIEW_CHANGE_REQUESTS_PRIV)
• Manage Change Requests (ACA_MANAGE_CHANGE_REQUESTS_PRIV)

For problem reports:

• View Problem Report (ACA_VIEW_PROBLEM_REPORTS_PRIV)
• Manage Problem Report (ACA_MANAGE_PROBLEM_REPORT_PRIV)

For corrective and preventive actions: 

• View Corrective Action (ACA_VIEW_CORRECTIVE_ACTIONS_PRIV)
• Manage Corrective Action (ACA_MANAGE_CORRECTIVE_ACTION_PRIV)

These privileges were available prior to this update.