Deletes the selected record(s). When clicked, users will be prompted with: "Are you sure you want to delete the selected records?". Click "OK" to confirm, or "Cancel" to return without deleting. 

_{WARNING: Records cannot be recovered once they are deleted!} 

Note: Users will not be able to delete a Freight Purchase Order record, the message “[PO#] is a Freight Purchase Order and therefore can not be deleted. Freight Purchase Orders can only be closed.” will be displayed when the button is clicked. 

Opens the mass update dialog, which allows to mass update the following properties: 

Status: A single-select lookup that defaults to "(No Change)". Assigns the selected Status to selected/filtered transactions when the 'Apply' icon is clicked. Options include:

• New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist.  

• Released: This status is used to signify that the transaction is ready to be released to production. While in the Status of 'Released', all editable fields are open for edit.
• Closed: Used to indicate that the record is no longer open to be used on other transactions. Closed records are only visible from inquiries, not list views.

 PO's cannot be 'Closed' if there are any unposted AP Invoices, Credit Memos or Inventory Receipts else the message "Purchase Orders referenced on unposted transactions cannot be closed. 

PO#: [PurchaseOrderID] - AP Invoice [TransactionID]

PO#: [PurchaseOrderID] - AP Credit Memo [TransactionID]

PO#: [PurchaseOrderID] - IM Receipt [TransactionID] 

 Displays a drop down menu of related actions. The list of options includes:

• IQ: PO Linked Transactions - Opens the "PO Linked Transactions" inquiry showing the Purchase Order and all AP Invoices, AP Credit Memos, and Inventory Receipts associated with it. 
• RV: Purchase Order - opens the Purchase Order Record View in a new tab.
• RV: Source Transaction - Opens the Transaction that the Freight Purchase Order was automatically created from, such as the Inventory Transfer, Sales Order or Return. This option is only applicable to Freight Purchase Orders, otherwise the message "

 Allows users to select the type of transaction or record they want to add.

 Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. 

When clicked, all the Reports that launch from the Print Dialog that are assigned to this page, and that the user has rights to (if Report Data Access is enabled) are displayed.

Identifies the header comment/description of the transaction or batch. This is not required and can be edited from the 'Comment' field on the 'Home' tab of the Purchase Order Record View. This is always editable even after the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.Description

Identifies the Created Date & Time of the record, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. This field is required but is not editable.

Database Field: ERPx_APPoHeader.CreatedDate

Identifies the Currency assigned to the transaction. This is required and comes from the 'Currency ID' on the 'Properties' tab of the Purchase Order Record View. This is not editable on the transaction.

The Currency identifies the kind of money used for transactions. For example, if a Customer or Vendor is setup with a Currency of "USD" then all transactions for them are stated in terms of US Dollars and all payments received or made must be in US Dollars.

Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_APVendor.CurrencySK

Identifies the date the Purchase Order will expire.This is required and can be edited from the 'Expire By' date field on the 'Home' tab of the Purchase Order Record View. This is editable until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.ExpireDate

Identifies the Last Updated Date & Time of the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. This field is required.

Database Field: ERPx_APPoHeader.LastUpdated

Identifies the name of the user that last updated the Transaction. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. This field is required.

Database Field: ERPx_APPoHeader.LastUser

Identifies the date of the transaction. This is required and can be edited from the 'Ordered' date field on the 'Home' tab of the Purchase Order Record View. This is editable until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.PODate

Identifies the Payment Terms assigned to the transaction. This is required and can be edited from the 'Payment Terms' field on the 'Properties' tab of the Purchase Order Record View. This is editable until the Purchase Order is Closed.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Payment Terms.

Database Fields: ERPx_MFPaymentTerms.PaymentTermName, APPOHeader.PaymentTermSK

Identifies the unique Transaction ID for each transaction. Clicking on this link opens the Purchase Order Record View for the selected record. This is required, and can be edited from the 'PO #' field on the 'Home' tab of the Purchase Order Record View. This is editable until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.PurchaseOrderID

Identifies the Reference entered for the transaction.  This is not required and can be edited from the 'Reference' field on the 'Home' tab of the Purchase Order Record View. This is always editable even after the Purchase Order is 'Closed'.

A Reference number is used to record an additional tracking number that associates this transaction to another system. For example, if a transaction was imported from a 3rd party system this could be used to store the unique identifier from that system's transaction. 

Database Field: ERPx_APPoHeader.Reference

Identifies the (source) requisition number that the Purchase Order belongs to.  This is not required and can be edited from the 'Requisition' field on the 'Home' tab of the Purchase Order Record View. This is always editable until the Purchase Order is 'Closed'.

A purchase requisition is a document used to inform department managers, or the purchasing officer, of the decision to purchase so that the purchasing department can start the purchase ordering process. A requisition can have one or more Purchase Orders. 

Database Field: ERPx_APPoHeader.Requisition

Identifies the unique Site ID (warehouse ID) of the Site the transaction, shipment, item, or lot is associated with. This is not required and can be edited from the 'Site Name' field on the 'Home' tab of the Purchase Order Record View. This is always editable until the Purchase Order is 'Closed'.

Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances.

Database Field: ERPx_MFSite.SiteID, ERPx_APPoHeader.SiteSK

Identifies the Status of the transaction. This is required and is always editable.

The Statuses that apply to Purchase Orders in this list view include:

New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist.  

Released: This status is used to signify that the transaction is ready to be released to production. While in the Status of 'Released', all editable fields are open for edit.

 Closed Purchase Orders are only visible from the Purchase Order History and/or Purchase Order Item History inquiries.

Database Fields: ERPx_APPOStatus.StatusName, ERPx_APPoHeader.POStatusSK

The unique identifier of the Transaction Class. This is required and comes from the 'Transaction Class' on the 'Properties' tab of the Purchase Order Record View. This is not editable.

Transaction Classes are used to differentiate transactions within a Transaction Type. For example, Transaction Classes of Fresh and Frozen can be setup for the Transaction Type of 'Sales Order'. Transaction Classes are used in all functional areas throughout the application.

Database Fields: ERPx_APTransactionClass.TransactionClassDescription, ERPx_APPoHeader.TransactionClassSK

Identifies the class that is assigned to the Vendor on the transaction. This is required and comes from the 'Vendor Class' assigned to the 'Vendor' that is selected on the 'Home' tab of the Purchased Order Record View. Because this defaults from the Vendor it is not editable on the transaction.

Vendor Class IDs are used as a short description and unique identifier for Vendor Class records.  Vendor Classes are used to identify default values that will be applied to new Vendor accounts and to group Vendor accounts together for reporting purposes. 

Database Field: ERPx_APVendorClass.ClassDescription, ERPx_APPoHeader.VendorSK

Identifies the ID of the Vendor account that is assigned to the transaction. This is required and represents the ID of the 'Vendor' on the 'Home' tab of the Purchase Order Record View. This is only editable by changing the Vendor assigned to the transaction.

Vendor IDs are used as a short description and unique identifier for Vendor records. They can be changed at any time to any alphanumeric value. If you do not have an existing strategy for Vendor IDs the 3-3-2 method would be recommended.

Database Fields: ERPx_APVendor.VendorID, ERPx_APPoHeader.VendorSK

Identifies the name of the Vendor assigned to the transaction or master file. This is set in the Vendor Record View.  This is required and represents the name of the 'Vendor' on the 'Home' tab of the Purchase Order Record View. This is only editable by changing the Vendor assigned to the transaction.

Vendor Names are used as a long description for Vendors.

Database Fields: ERPx_APVendor.VendorName, ERPx_APPoHeader.VendorSK