Security Codes

The AP Security Codes (APOHUPCD) page is used to define security codes used by the various subsystems within the AP module:

• AP Open Hold Create/Update Set (APOHBTUB)
• AP Invoice Entry (APOHININ)
• AP Create/Update IP Set (APIPBTUB)
• AP Create/Update TR Set (APTRBTUB)

When security codes are defined, a Workflow model can be designed that will automatically route 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. For example, when attempting to distribute an invoice that holds a security code using APOHINVP, an approval will be required in order to distribute. If there is not a security code on the record, the invoice will process without an approval code.

The security code works similarly to those in the PO module. When the security code is present, approvals are enforced. 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 and are based on which PO Security Codes the user is given access to in the Common Security for handling PR/POs in his or her role. Security codes for purchasing are defined in POUPSC.

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.