Please click here to view a short video on how to create a purchase order.
...
- From the Transaction menu select 'Purchase Orders'
- Click
Enter desired information into the purchase order
Info Purchase Orders by default do not require a vendor number. No vendor means the user hasn't assigned one yet or that it will be used as a 'multi-vendor' purchase order (non-vendor specific). The creation of multi-vendor vendor numbers is no longer needed in the redesign.
- Click on the
to add line items. - Click
or 
to move item up or down in listing of line items. - Click on the
to copy line items.- The
allows the user to split items by quantity and the 
allows the user to split by price
- The
- Click on the
- Click on
to post the purchase order to the system, click on Cancel to not post the purchase order and return to the Purchase Order grid.
...
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.
Classic USAS Requisition Approval functionality
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 an 'Approval Status' 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 statustransmitted" boolean Custom Field on the PO so that an outside purchasing system may optionally tell USAS whether the PO was already transmitted to the vendor.
...