How to fix PO's getting stuck in PO Approval Workflow under 'in-process' status?

Workflow Errors Reported

Document Manager Failed With Error Number while processing Standard Purchase Order 6044

Error Number 3 = Unknown Error.
The Document Manager failed with error number .

ORA-06512: at line
Wf_Engine_Util.Function_Call(PO_REQAPPROVAL_ACTION.DOC_COMPLETE_CHECK, POAPPRV, 111398-518763, 807792, RUN)

3103: Attribute 'DOCUMENT_ID' does not exist for item 'POAPPRV/111400-518765'.
PO_REQAPPROVAL_ACTION.Doc_complete_check(POAPPRV, 111400-518765, PO_REQAPPROVAL_ACTION.Doc_complete_check: 01) Wf_Engine.GetItemAttrNumber(POAPPRV, 111400-518765, DOCUMENT_ID) Wf_Engine_Util.Function_Call(PO_REQAPPROVAL_ACTION.DOC_COMPLETE_CHECK, POAPPRV, 111400-518765, 807792, RUN)

Solution

A. Recommended Solution

1. After spending a good amount of time on this, I found the root cause of this issue was the Invalid objects lying in the database for Contracts module (starts with OK). The contracts documents were not getting generated (which were associated with the PO).

2. These objects were a couple of Libraries (.pll) and Package Body.

3. First start with recompiling the libraries (See more info here Error in adpatch worker for OKL libraries (Patch 9239090))

4. Then recompile the database Invalid objects (See more info here How to recompile INVALID objects in Oracle EBS Database?)

5. Now retry the Workflow from front-end and the PO will go through the Approval. As a second test, create a new PO and submit for approval.

B. Other Solutions

5. You can search on MOS for fixes or patches, but in my case none of them could fix the issue, but recompiling invalid objects worked.

6. If nothing works then you may want to raise an SR.

 

Environment

  • Oracle E Business Suite Release 12.1.x
  • Oracle Purchasing -> PO Approval Workflow (Create a new PO and Submit for Approval)
How to resolve the error 'Legal Entity Manager is ...
How to recompile INVALID database objects that are...