Is There A Best Practice To Avoid Errors Prior To An Approval Rule Maintenance? (Doc ID 2295612.1)

Last updated on AUGUST 23, 2017

Applies to:

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

Goal

Manage Requisition Approvals

Question 1: Is there a best practice to avoid errors prior to approval rule maintenance?

Approval rules were changed and after they were changed every requisition that was related to the rule got stuck in Pending Approval status. If you attempt to review the approval history, and error was being returned:
Error
Error occurred while displaying History tree table. Error in task {0}. Please correct the error.

Error
oracle.bpel.services.workflow.task.impl.RoutingSlipEvaluationException: oracle.bpel.services.workflow.task.impl.RoutingSlipEvaluationException: ORABPEL-30103 Ruleset didnt return any results. Ruleset HeaderHierarchy3Rules didnt return any results. Model the ruleset so that it returns a list builder specification.


Only after the requisition was changed and submitted to approval , the error message disappeared.

 

Question 2: Is there a batch process to 'refresh' action details in all orders that have been already entered and are either incomplete or pending approval status?
 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms