My Oracle Support Banner

PO_PO_EMAIL does not Consider Parameters Entered on Run Control Page and All Transaction in the PO_EMAIL_QUEUE are Dispatched (Doc ID 2035463.1)

Last updated on DECEMBER 12, 2019

Applies to:

PeopleSoft Enterprise SCM Purchasing - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.


The PO_EMAIL_QUEUE record could not be cleaned if by various reasons, the run control is not finished with success or canceled by user.  The next time when run PO_PO_EMAIL is executed, it is dispatching all the transactions in the PO_EMAIL_QUEUE record, even if the user has one PO selected.  Checking the stdout file, it can be seen that the system is trying to dispatch any file with Email dispatch method found in PO_EMAIL_QUEUE record, even the run control indicates one PO ID selected for dispatch.


If user has canceled the PO_PO_EMAIL Application Engine, a part of PO’s were dispatched and emails sent and other part of PO’s were not dispatched. When re-dispatch all the deleted records will be rollbacked, but it can’t call the email back. Canceling the process is a conscious action and should be avoided.


The PO_PO_EMAIL Process doesn’t consider the input parameters passed in the run control page and dispatching all the PO’s in the Email Queue PO_EMAIL_QUEUE record.

The email process is a kind of subsequent process, in another words, to dispatch by email, user first needs to run the PO Dispatch/Print process to create the output files and to update the PO Email queue table. Then user runs the Email process. Therefore, the workaround is to run PODISP job that is using first the POPO005.SQR process then PO_PO_EMAIL Application Engine.




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.