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!} 

Opens the selected record for editing. If a record is not selected, the page will either not open or will open the first record (depending on how the page was coded). 

 Exports the contents of the grid to an Excel file that will automatically download. The contents that export are those that are visible to the user. Therefore, if the user has filtered the view, or excluded columns, only the contents in the grid will be exported. 

 Clicking on the star icon when it is an outline, adds the page to the 'My Shortcuts' tab and fills in the star. Clicking on the star icon when it is filled in (solid color), removes the page from the 'My Shortcuts' tab and returns the icon to an outline. 

 Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.

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

• GL Date: A date field that defaults to "(No Change)", but also allows users to select a date from the calendar. Assigns the selected date to the selected/filtered transactions when the 'Apply' icon is clicked.
• Pmt./Apply Hold: A single-select lookup that defaults to "(No Change)", but also has options for (blank) and "Yes". Assigns the selected value to selected/filtered transactions when the 'Apply' icon is clicked.
• Status: A single-select lookup that defaults to "(No Change)", but also has options for "New", "Approved" and "Ready to Post". Assigns the selected Status to selected/filtered transactions when the 'Apply' icon is clicked.

 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: Transaction - opens the Transaction Record View in a new tab.
• RV: Purchase Order - Opens the record view of the Purchase Order. If there is not a linked PO, a message will appear indicating "There is no Purchase Order for this transaction."  
• View in PaperVision - This option is only visible when the preferences for PaperVision are configured.

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

• Invoice: A transaction to record a purchase you are making from a Vendor.
• Credit Memo: A transaction to record a return/refund you are getting from Vendor.

 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.

Displays the amount of the transaction, in the currency and currency format of the transaction. This is calculated from the sum of all transaction lines 'Amount'. This can only be edited by changing the quantity and/or price of one or more transaction lines.

Database Field: ERPx_APTransactionHeader.ExtendedAmount

Identifies the header comment/description of the transaction or batch. This can be edited from the 'Comment' field on the 'Home' tab of the Invoice/Credit Memo Record View. This is always editable, even after the transaction is Posted.

Database Field: ERPx_APTransactionHeader.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. 

Database Field: ERPx_APTransactionHeader.CreatedDate

Identifies the name of the user that created the record. 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. 

Database Field: ERPx_APTransactionHeader.CreatedBy

Identifies the Currency assigned to the transaction. This comes from the 'Currency' on the 'Properties' tab of the Invoice/Credit Memo 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_APTransactionHeader.CurrencySK

Identifies the date of the transaction. This can be edited from the 'Doc Date' on the 'Home' tab of the Invoice/Credit Memo Record View. This is always editable, even after the transaction is Posted.

Database Field: ERPx_APTransactionHeader.TransactionDate

Identifies the Doc No (document number) for the transaction. Unlike a Transaction ID that is system assigned based on the Transaction Class of the Transaction Type, this is a manually entered value. This can be edited from the 'Doc No' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the transaction/Invoice # assigned by your Vendor. This is always editable while the transaction is in a Status of New.

Database Field: ERPx_APTransactionHeader.DocNumber

Identifies the date the transaction posted (or will post) to the general ledger.  This is required and can be edited from the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View. If not manually edited, this will be automatically set to match the 'Doc Date' when the transaction is saved with a Status of either Approved or Ready to Post. This is always editable while the transaction is in a Status of New.

Database Field: ERPx_APTransactionHeader.GLDate

Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This is required and calculated using the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View. This can only be edited by changing the GL Date.

Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This is required and calculated using the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View. This can only be edited by changing the GL Date.

Identifies the Payment Terms assigned to the transaction. This can be edited from the 'Payment Terms' on the 'Properties' tab of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New.

Payment Terms identify the terms your company extends to your Customers and that your Vendors extend to you. Payment Terms are used to calculate aging and payment discounts.

Database Fields: ERPx_MFPaymentTerms.PaymentTermName, APTransactionHeader.PaymentTermSK

Identifies the Purchase Order number (PO number) entered for the transaction or transaction line item. This can be edited from the 'PO #' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the purchase order you used when making the purchase. This is always editable while the transaction is in a Status of New.

Database Field: ERPx_APTransactionHeader.PurchaseOrderID

Identifies the Status of the transaction. This is required and can be edited from the 'Status' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the status of the transaction. This is always editable while the transaction is in a Status of 'New' or 'Approved'.

Status is used to identify where a transaction, Purchase Order, Price List, BOM, or Master File record is in its life cycle. Records start in a Status of 'New' and progress sequentially through additional statuses until they are 'Posted' or 'Closed'. The list of potential Statuses changes depending on the transaction type.  The Statuses that apply to transactions 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.  

Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned.

Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled with the exception any fields that are always editable and updates the Transaction Status to "Posted".

Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APTransactionHeader.TransactionStatusSK

Identifies the unique Transaction ID for each transaction. Clicking on this link opens the AP Invoice / Credit Memo Record View for the selected record. This is a system assigned number that comes from the 'Transaction Class' and is not editable by users.

Transaction numbers are system assigned IDs to differentiate unique transactions. Transaction ID's are unique by the unique combination of 'Transaction Type' + 'Transaction Class'.

Database Field: ERPx_APTransactionHeader.TransactionID

The unique identifier of the Transaction Class. This comes from the 'Transaction Class' on the 'Properties' tab of the Invoice/Credit Memo 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_APTransactionHeader.TransactionClassSK

Identifies the Transaction Type for each transaction. This is required and comes from the Transaction Type selected when starting a new transaction. This is never editable.

Transaction Types are used to differentiate unique types transactions within the system. Transactions with the same Transaction Type share the same record view pages and business rules. Transaction Types can be further classified using Transaction Classes. Every transaction in the system is assigned a Transaction Type.

Database Fields: ERPx_APTransactionType.TransactionName, ERPx_APTransactionHeader.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 Invoice/Credit Memo Record View. Because this defaults from the Vendor it is not editable on the transaction.

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_APTransactionHeader.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 Invoice/Credit Memo 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_APTransactionHeader.VendorSK