My Oracle Support Banner

How To Plan The Number Of Processes Required By PO Document Approval Manager After R12 (Doc ID 735474.1)

Last updated on APRIL 19, 2023

Applies to:

Oracle Purchasing - Version 12.0 to 12.3 [Release 12 to 12.3]
Information in this document applies to any platform.
Information in this document applies to any platform.



In Release 12, most of the 'PO Document Approval Manager' transaction manager code has been rewritten from pro*c to pl/sql.  Before Release 12, PO/Requisition approval workflow used to initiate a call to the 'PO Document Approval Manager' using fnd_transaction.sync() API. In Release 12, fnd_transaction call has been eliminated with direct calls to pl/sql code. It means, even if we terminate the 'PO Document Approval Manager' (via Administer concurrent manager --> 'System Administrator') , the PO and Requisition approval will still work fine in Release 12.

Given the above situation, it brings us to the vital question about the use of administering 'PO Document Approval Manager' through system administrator concurrent manager administration. Prior to Release 12, we used to control the number of processes of 'PO Document Approval Manager' based on the demand for the 'PO Document Approval Manager' based on the number of instances of PO and requisition approvals during peak loads and the capacity of CPU resource available.


In Release 12, how do we decide the number of processes required by the 'PO Document Approval Manager'? Do we still need to keep this manager active?


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

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