Requisition Approval Workflow Can Complete With A #Stuck Status (Doc ID 352672.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

The Requisition Approval Workflow can end in STUCK status because workflow activity PO_REQAPPROVAL_INIT1.Is_doc_preapproved activity does not have a result option = INVALID_AUTH_STATUS which is a possible result from procedure PO_REQAPPROVAL_INIT1.Is_doc_preapproved

The comments in PO_REQAPPROVAL_INIT1.Is_doc_preapproved say that if document is APPROVED, INCOMPLETE or REJECTED to "exit the workflow with an INVALID ACTION status" but this never happens. Since the Workflow file can not handle this result the workflow ends in Stuck status.

Some background on the issue is that a workflow can end with STUCK status if an activity has a value returned from the code used during that activity, but the actual workflow file does not have a corresponding result for the workflow to follow.  That is what happens in this case.  The value of the result = INVALID_AUTH_STATUS  but the only choices for Result are Yes or No.   If INVALID_AUTH_STATUS  is the result value then the workflow will end in STUCK status. 

Changes

Cause

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