Deletes the transaction or master file record. When clicked, users will be prompted with: "Are you sure you want to delete this record?". Click "OK" to confirm, or "Cancel" to return without deleting. 

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

Opens a new blank record for data entry. Users can select the type of transaction they want to add. The drop-down includes: Adjustment (all Adjustment Classes), Balance Transfer, and Payment Receipt.

 Opens the Notes dialog, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the record. This icon is always enabled.  

Identifies the date the transaction posted (or will post) to the general ledger.  This defaults to the current date but can be edited while the transaction is set to a status of 'New.' This is required and must be within a Fiscal Period open to both Purchasing and Financial.

Database Field: ERPx_APTransactionHeader.TransactionDate 

An editable field that identifies the Doc No (document number) such as a Vendor's Invoice # or a reference number that you assign for the transaction. This defaults to blank, not required, and is always editable, even after the transaction is posted. If entered, it must be <= 50 characters and be unique across all Balance Transfer transactions.

Database Field: ERPx_APTransactionHeader.DocNumber

A single-select lookup to identify the Status of the transaction. This defaults to "New" but can be edited until the transaction is Posted. 

Identifies the Status of the transaction. This is required and can be edited while 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

A non-editable text box to identify the name of the user that created 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.

Database Field: ERPx_APTransactionHeader.CreatedBy 

A non-editable text box to identify the Created 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.

Database Field: ERPx_APTransactionHeader.CreatedDate 

Identifies the Currency assigned to the transaction. This defaults to the Home Currency of the company and is not editable. 

Database Field: ERPx_APTransactionHeader.CurrencySK