A Fisherman Sale is a transaction used to record sales from the company to a Fisherman or Tender. These transactions can be settled against Fish Ticket balances.

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.

The purpose of this inquiry is to view, add, edit, delete, void or correct Fisherman Sale and Tender Resale transactions. Additionally, users may void or correct transactions. From this list view, users may also mass update values for several fields, print available reports or export the contents of the grid to Excel.

This list view also contains columns for each Attribute that is set up for the 'Fisherman Accounting - Transactions' attribute type. However, because these attributes are user defined, they are not included in the help documentation.

Software Version: 2023.08.31 and newer

Page Header

Toolbar Icons	Description
Excel	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.
Favorites	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.
Grid Layout	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.
Help	Opens the online WIKI help page for the current page. This icon is only visible on pages that are documented in the online help.
Inquiry Criteria	Opens Inquiry Criteria window where users can define the following criteria: Date From Date To Status
Journal Details	Opens the Journal Detail for all the rows selected.
More Actions	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.
Print	Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed.
Refresh	Re-queries the contents of the grid/page based on the Inquiry Criteria parameters or the default parameters for grids that do not support Inquiry Criteria.
Fields	Description
Checkbox	Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Doc Date	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
Doc Description	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
Doc No	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
Fisherman	Identifies the ID of the Fisherman, Fisherman & Tender or Tender associated with the transaction. Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.VendorSK
Fisherman Name	Identifies the name of the Fisherman, Fisherman & Tender or Tender associated with the transaction. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK
GL Date	Identifies the date the transaction posted (or will post) to the general ledger. Database Field: ERPx_APTransactionHeader.GLDate
GL Period	Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This field is not stored in the database.
GL Year	Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This field is not stored in the database.
Price List ID	Identifies the ID of the Price List that is assigned to the transaction. 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
Site Name	Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. Database Fields: ERPx_MFSite.SiteName, ERPx_APTransactionHeader.SiteSK
Status	Identifies the Status of the transaction. 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". Posted: Signifies the transaction has been posted and/or applied to a transactions (e.g. Payment Receipt). When a transaction is posted, it updates the General Ledger and/or On Hand Item Balances. While in the Status of 'Posted' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. Void: Signifies a previously posted transaction has been voided. This status is only available for transactions that support voiding posted records (not all transactions support this). Voided transactions remain in the database and can be viewed from history inquiries. Deleted: Signifies the transaction has been deleted. When a user deletes an open transaction, in some instances the transaction is not removed from the database but is changed to a Status of 'Deleted'. Deleted transactions are not visible from transaction list views but can be found in inquiries. Transaction in the Status of 'Deleted' are only used a information. Replaced: Signifies the transaction was voided or corrected. When a transaction is corrected or Voided, the Status of the original transaction is changed to 'Replaced' and a new transaction is cloned and marked as 'Void'. This is done to ensure that a reversal journal entry can be created and posted in an open fiscal period to record the Void. Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APTransactionHeader.TransactionStatusSK
Subtotal	Identifies the sum of all the sale line items on the transaction. Database Field: ERPx_APTransactionHeader.TaxableAmount
Tax	Identifies the applicable sales tax for the transaction. Database Field: ERPx_APTransactionHeader.TaxedAmount
Tax Class	Tax Classes store all the Tax Details (individual taxes) used to calculate sales tax on Quick Sales, Fisherman Sales, and Tender Resale transactions. Database Field: ERPx_APTransactionHeader.TaxClassSK
Tender	Identifies the ID of the Tender account that is assigned to the transaction. 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. Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.FromVendorSK
Tender Name	Identifies the name of the Tender assigned to the transaction or master file. This is set in the Fishermen & Tenders Record View. 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. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.FromVendorSK
Total Amount	Identifies the total amount of the transaction. [Total Amount] = [Sub Total] + [Tax] Database Field: ERPx_APTransactionHeader.ExtendedAmount
Transaction	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
Transaction Type	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 Field: ERPx_APTransactionType.TransactionName, ERPx_APTransactionClass.TransactionTypeSK, ERPx_APTransactionHeader.TransactionClassSK

Page Header

Related Topics

Page Definitions

Technical Details

Browser not supported