My Oracle Support Banner

How To Diagnose Purchase Order And Requisition Workflows in Deferred Status? (Doc ID 884391.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Purchasing - Version 11.5.10 to 12.2.7 [Release 11.5 to 12.2]
Information in this document applies to any platform.
FORM:POXDOFDO.FMB - Forward Documents



Purpose

Background for the reader

When attempting to approve purchase orders and requisitions in some cases workflow activities become deferred. In some cases this is standard behavior, while in other cases this might be a known bug. This note describes:

- Known cases in which it is inevitable that the workflow becomes deferred
- Known bugs causing the approval to get deferred
- Solutions to both cases

Troubleshooting Steps

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
Purpose
 Background for the reader
Troubleshooting Steps
 SUMMARY
 DIFFERENT SCENARIOS IN WHICH CASE IT IS STANDARD FUNCTIONALITY THAT WORKFLOW IS GET DEFERRED
 A. Profile option PO:Workflow Processing Mode is set to Background
 B. The approval authority is delegated
 C. Purchasing document is forwarded through the Forward Documents form
 D. Documents are approved when using granted worklist access
 E. Requisitions Using Find Notification Form
 F. When Approving Requisitions In Succession Some Requisitions Get Deferred
 G. Approval deferred whenever the notifications are approved from the default worklist/full list or homepage
 HOW TO PROGRESS THE DEFERRED WORKFLOW PROCESSES?
 RECOMMENDED PATCHES TO PREVENT UNNECESSARY DEFERRING
 DEFERRED ACTIVITIES NOT BEING PICKED UP WHEN RUNNING WORKFLOW BACKGROUND PROCESS AFTER RDBMS UPGRADE TO 10G
References

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