...
By default the system will not allow any purchase order to be deleted. However this is a bundled, non-mandatory rule, meaning it may be disabled under the Rules interface (see org.ssdt_ohio.usas.model.po.POPreventDelete). If the rule is disabled only purchase orders that do not have any other information tied to it such as an invoice, check, etc may be deleted.
...
Individual user purchase order processing is controlled by a variety of variables, such as User account where the Account Filter and Role (and the Permissions assigned to those Roles) are defined for each user, User Preferences, Rules, etc.
By default the system will give a warning if the budget's remaining balance will go negative. Remaining balance is either unencumbered balance or unencumbered balance - outstanding requisitions depending on whether the pre-encumbrance module is enabled and installed (see Admin/Modules) and on the specific rule(s) the district has enabled. However, this can be customized to suit the needs of the district (see rules org.ssdt_ohio.usas.model.po.DefaultBalanceCheckWarning and org.ssdt_ohio.usas.module.preencumbrance.POBalanceCheckWarningExcludePreencumbrances).
By default, the account codes must be active and function codes 7100-7499 are not allowed. The default rules affecting this behavior are org.ssdt_ohio.usas.model.po.PORequireActiveAccounts and org.ssdt_ohio.usas.model.po.PORestrictedFunctionCodes. Function codes 7200-7499 are reserved for Transfers and Advances, which must be entered via the Transfers/Advances option. Function code 7100 is a contingency account. Expenditures may not be made directly from a contingency account.
By default, the vendor must be active. The default rule affecting this behavior is org.ssdt_ohio.usas.model.po.POVendorActive. A warning will also be generated if the vendor does not have a default PO location defined. This behavior is optional and may be customized by disabling or copying the rule org.ssdt_ohio.usas.model.po.PoVendorDefaultPOAddress.
USAS-R contains an optional module to provide support for the optional Classic USAS Requisition Approval functionality. If this module is enabled, a Custom Field will be available on the requisition to indicate it's status, and requisitions may only be converted to a purchase order after the status has been set to approved by a user with the appropriate security. This module also activates an optional "transmission status" Custom Field on the PO so that an outside purchasing system may optionally tell USAS whether the PO was already transmitted to the vendor.