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

 If a Payment Receipt that has been fully or partially applied is deleted (prior to posting), all applications will be automatically removed. 

Allows users to select the type of transaction or record they want to add. The list contains:

• Adjustment
• Additional Adjustment Transaction Classes (if any)
• Balance Transfer
• Payment Receipt

Identifies the checkbook where the receipt will be deposited into. This is a single-select standard lookup that is required. This defaults using the following logic:

1. If a value is assigned to the "Default Fisherman Checkbook ID" Settlement Default Preference then the Checkbook lookup on the Payment Receipt will default from the Preference, else
2. It defaults to the first Checkbook in the lookup

This is required to Approve and/or Post, or to open the Apply Fishing Transactions list view. This field is enabled and only editable while the transaction Status is "New". 

Checkbooks represent individual bank accounts (checking, savings, petty cash) that have funds deposited into, or payments made out of, that are reconciled to a bank statement. They are used in the Financial, Fisherman Accounting, Grower Accounting, Purchasing, and Sales Functional Areas to support receiving payments from customers, making payments, deposits, and other bank transactions.

The lookup contains a list of all the 'Active' Checkbooks where the Currency is USD.

Database Fields: ERPx_MFCheckbook.CheckbookID, ERPx_APTransactionHeader.CheckbookSK

Identifies the name of the Fisherman, Fisherman & Tender, Tender or Loan. This is a single-select standard lookup to select who the payment is coming from. It defaults to blank, but is required. If not assigned, the message "Received From is required." will be displayed. This field is only editable while the transaction Status is "New" and the 'Applied Amount' is blank or 0.00.

The lookup contains the current assigned value and a list of all the 'Active' Fishermen, Fishermen & Tenders, and Tenders and Loans that have not been excluded from the "Cash Receipt" Transaction on the 'Excluded Transaction' tab of the Fisherman & Tender Record View.

Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK

Identifies the Status of the transaction. This is a single-select standard lookup that defaults as 'New' and is required. 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