PO Printing

Use POPO to print a Purchase Order form. The POPO process relieves any prior encumbrances and re-encumbers the Purchase Order amount. The record created on the POUPPR page is only a Purchase Requisition until it is printed. The system prints a record by its Purchase Request number the first time the POPO process is submitted. The requisition must be fully approved before it will print. This allows the user to print all fully approved purchase requests by simply accepting the default settings and launching the job. All requests are printed when the Purchase Request Number field is left empty.

Format

The Purchase Order format is defined within POUPFO; one record per Format ID. The default Format ID will be displayed within the question "PO Format" and may be customized per that question (Question No: PO0D) within NUUPJBQS.

Request Date

Typically, the Request date and the date of printing need to occur within the same fiscal year. So, printing a pre-encumbered Purchase Request during the current fiscal year--yet the Request date says the PO was created "last year"—the printing process will be blocked with a message:
"Block: Failed to print PR # number. Requested date 20150527 in Fiscal Year 2015 is different from Printed date 20160107 in Fiscal Year 2016."

This message may be changed from an error that blocks printing to a warning (enabling the user to continue printing) by defining common code POPO/FYDT.

Reprint

When a reprint of a Purchase Order is needed, change the value you would like to print the Purchase Order to PO and enter the Purchase Order number. It is possible to enter multiple numbers separated by commas without spacing (P000204,P000210,P000222) or to enter a range of numbers (P000250-P000260). Do not leave the field empty when printing by PO number otherwise the system will reprint all Purchase Orders.

Security

Purchase order printing allows for the printing of purchase orders even when security is set with WRITE/UPDATE restricted and EXECUTE/READ permissions granted. This allows printing access for restricted users, other than the original creator of the purchase order.

A sample of the Nucleus User Common Security Settings on the Purchasing Application is:
PO READ ACCESS = pop_sec_cd = 'XXXX'
PO WRITE ACCESS = pop_sec_cd = 'XXXX' and pop_status = 'PR'
PO UPDATE ACCESS = pop_sec_cd = 'XXXX' and pop_status = 'PR'
PO EXECUTE ACCESS = pop_sec_cd = 'XXXX'
(Example XXXX represents an arbitrary security code. Client values will differ).
Additionally, "UPDATE" permission may need to be granted to the PO Security Code Update column for the initial print of the PR to occur.

Note: The tail sheet error " ** ERROR ** - [PR Number] Incomplete approval for requisition" is related to common code POPO/SECURITY. Resolve the message by approving the order in the Workflow Task List before proceeding with the printing; and thereby relieving any pre-encumbrance(s) on the order's Requisition (PR#) and encumbering the Purchase Order Number. This process is automated and can be reviewed within the EN Direct Update (ENUPTR) page (use the PR # field to search/find all related records).