Security Codes - POUPSC

The Purchasing (PO) Security Codes (POUPSC) page is used to define security codes used by the Purchasing subsystem and enforced through security definitions for role, user, or vendor identities. If security codes are defined, a workflow model can be designed that will automatically create the required approvals for each invoice. The codes are used to enforce approvals and restrict access to records. They may or may not be used in the approval routing process. In 7.9, the GL account background parts are what typically drive approvals.

For example, if the POUPPR page does not have a security code entered, approvals are not required in order to print the PO. If there is a security code on the record then it will not print until an approval code of APRV is on the record. The GL account number (background part of Key or Object code), the PO or item total, and PE ID are commonly used to determine approval routing. User Security roles identify which PR/POs a user can see based on which PO Security Codes they are given access to in the Common Security for PO in their role. For AP, the presence of the security code also prevents the invoice from posting until it is approved. Most often, there is only one AP security code as it is not typically necessary to limit access to invoice records, as entry is usually not decentralized like the entry of a purchase requisition. Security codes for AP are defined in APOHUPCD.

Security Code: Enter a code of up to four characters. These codes will appear in the drop-down list on purchasing data entry pages that contain a Security Code field.
Description: Enter up to 30 characters that describe the security code.