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 not open.

Export the contents of the list view 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 only the filtered contents will be exported. 

Opens the Saved Grid Layout menu that allows the user to select another saved layout, create a new layout, save changes to a layout, or assign a saved layout as the default for the page. Once changes are made to a grid, such as columns are added or removed, the user can click the Saved Grid Layout icon and save the changes to the grid layout and name the new layout. The new layout can also be set as the default, instead of the System View. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific).

 The bolded view is the default view, which will determine the view will automatically display in when opened. 

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

• GL Date: A date picker that defaults to "(No Change)". Assigns the selected GL Date to selected/filtered transaction(s) when 'Apply' is clicked. 
• Site: A single-select standard lookup that defaults to "(No Change)", but also contains a list of all active Sites configured on the Sites List View that assigns the selected Site to selected/filtered transaction(s) when 'Apply' is clicked; and an option "(Clear Value)" that when selected and 'Apply' is clicked will remove the Site assigned to the selected transaction(s). 
• Status: A single-select standard lookup that defaults to "(No Change)", but also has options for "New", "Approved" and "Ready to Post". Assigns the selected Status to selected/filtered transaction(s) when 'Apply' is clicked. 

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

• Void/Correct: Opens the Void/Correct Fish Ticket utility to allow users to void or correct one or more posted Fisherman Sale or Tender Resale transactions.

Allows users to select the class for the transaction they want to add. The list contains: 

• Fisherman Sale: A Fisherman Sale is a transaction used to record sales from the company to a Fisherman, Tender or Loan Account. These transactions can be settled against Fish Ticket balances.
• Tender Resale: A Tender resale is a transaction used to record sales transactions made between Tenders and Fishermen. These may include line items that the Tender owns and/or line items that the company owns. Line items for Tender owned products create a balance transfer event between the Tender and Fisherman. They have no financial impact on the company and show up on the Fisherman Statement for both the Tender and Fisherman. Line items for Company owned products create a sale between the company and fisherman. These line items only show on the Fisherman Statement for the Fisherman and can be settled against Fish Ticket balances.

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 is required and is not editable.

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. This is required and is not editable.

Database Field: ERPx_APTransactionHeader.CreatedBy

Identifies the date of the transaction. This can be edited from the 'Doc Date' on the 'Home' tab of the Record View. 

Database Field: ERPx_APTransactionHeader.TransactionDate

Identifies the header comment/description of the transaction or batch. This is a text box to assign a description to the Fisherman Sale transaction. 

Database Field: ERPx_APTransactionHeader.Description

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 Record View and is used to enter a unique identifier from a pre-printed book of receipts. The Doc No value must be unique by transaction type. No two Fisherman Sale or Tender Resale Doc No values may be the same.

Database Field: ERPx_APTransactionHeader.DocNumber

Identifies the ID of the Fisherman, Fisherman & Tender or Tender associated with the transaction. 

Identifies the name of the Fisherman, Fisherman & Tender or Tender associated with the transaction. This is a single-select standard lookup that identifies the fisherman who purchased the item(s). This defaults to blank and is required. If missing, the message "Please select a Fisherman or Tender." will be displayed on Save. This field can only be edited while the transaction is set to a Status of New.

A Fisherman is an Account Type used to identify someone that catches fish and sells them to a processing facility.

A Tender is a vessel that is attendant to other vessels and is used to transport or ferry unprocessed fish or shellfish received from another vessel to a shoreside processor or mothership.  Tender vessels operate, in most circumstances, as an agent for a specific processor and take deliveries from harvesting vessels.

A Fisherman & Tender is an Account Type used to identify someone that catches fish during one season and provides Tendering services during another.

Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This is required for the transaction to be approved or posted. It is not directly editable.  It can be changed by editing the 'GL Date' field on the 'Properties' tab of the Fish Ticket Record View. This field is not stored in the database.

Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This is required for the transaction to be approved or posted. It is not directly editable.  It can be changed by editing the 'GL Date' field on the 'Properties' tab of the Fish Ticket Record View. This field is not stored in the database.

Displays the total amount for all line items before taxes. This is a calculated field that is not directly editable. It can be changed by editing the 'Weight', 'Weight Modifier', 'Price' or 'Premium Rate' for a line item in the Items grid on the Fish Ticket Record View.

Database Field: ERPx_APTransactionHeader.GrossAmount

Price Lists are used to store a group of Items with pre-defined prices and effective dates.

Database Fields: ERPx_MFPriceListHeader.PriceListID, ERPx_APTransactionHeader.PriceListHeaderSK

Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. This is required and can be edited from the 'Site Processed' field on the 'Home' tab of the Fish Tickets record view.

Database Fields: ERPx_MFSite.SiteName, ERPx_APTransactionHeader.SiteProcessedSiteSK

Identifies the Status of the transaction. This is required and can be edited from the 'Status' field on the 'Home' tab of the Fish Ticket Record View.

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