My Oracle Support Banner

Requisition Approval Rules Erroring After Being Cloned (Doc ID 2435606.1)

Last updated on AUGUST 15, 2018

Applies to:

Oracle Fusion Self Service Procurement Cloud Service - Version 11.13.18.02.0 and later
Oracle Fusion Self Service Procurement - Version 11.13.18.02.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.13.18.02.0 version, Approve Requisition

Issue reported that none of the approval rules are working after recently migrating rules from PROD to DEV during a P2T refresh, or after cloning rules between test environments.
If you are getting the below error when following steps below and attempting to review Manage Approvals for Requisition and you have DFF rules setup.

Error occurred while displaying History tree table. Error in evaluating routing slip.
Check the underlying exception and correct the error in the routing slip.

1. Create Requisition
2. First Check Manage Approvals - encounter error
3. Submit for Approval
4. Requisition is rejected

If you have tried the following with no success:
   - Attempted to disable all rules and created a simple rule (Rule always applies).
   - Attempted to Synchronize the rules.
   - Verified the same rules are working in all other instances.

If you are still getting the error after trying the above, it's possible you have a KFF/DFF mismatch between the two environments.

When DFF schema and rules facts are out of sync, dictionary gets corrupted.  If a DFF rule was removed in the cloned environment,  the base rule dictionary will still look for the flex field definition and this causes the issue.
Example:  If customer defined Line DFF with context, and then deleted the context but did not sync the rules schema after that, it could cause the issue.

 

Changes

If a DFF rule was removed in the cloned environment,  the base rule dictionary will still look for the flex field definition and this causes the issue.
Example:  If customer defined Line DFF with context, and then deleted the context but did not sync the rules schema after that, it could cause the issue.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.