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. The purpose of this page is to view, add, edit, remove, and post individual Fisherman Sale transactions.
Software Version: YYYY.MM.DD and newer
Page Header
Header Toolbar
| Toolbar Icons | Description |
|---|---|
| Delete | 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! |
| 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).
|
| Journal Details | Opens the Journal Details window showing the Journal Entry for this transaction.
|
| Help | Opens the online WIKI help page for the current page.
|
| New | Allows users to select the type of transaction or record they want to add. The list contains:
|
| Opens the Print dialog, showing any applicable printable reports to be printed, downloaded, and/or emailed. | |
| Save | Saves the changes made to the record.
|
The bolded view is the default view, which will determine the view will automatically display in when opened. Home Tab
| Fields | Description |
|---|---|
| Cash | Identifies the amount of cash received as payment for the transaction. This is a text box to enter a cash payment amount that was received at the time of the transaction. This defaults as "0.00" and is not required. The amount entered will automatically update the 'Payment Details' tab and the total 'On Account'. This field is only enabled after item(s) have been added to the Items grid and is always editable while in a Status of New. Database Field: ERPx_APTransactionHeader.PmtCash |
| Check | Identifies the amount of the check received as payment for the transaction. This is a text box to enter a check payment amount that was received at the time of the transaction. This defaults as "0.00" and is not required. The amount entered will automatically update the 'Payment Details' tab and the total 'On Account'. This field is only enabled after item(s) have been added to the Items grid and is always editable while in a Status of New. Database Field: ERPx_APTransactionHeader.PmtCheck |
| Credit Card | Identifies the amount of the credit card payment for the transaction. This is a text box to enter a credit card payment amount that was received at the time of the transaction. This defaults as "0.00" and is not required. The amount entered here will automatically update the 'Payment Details' tab and the total 'On Account'. This field is only enabled after item(s) have been added to the Items grid and is always editable while in a Status of New. Database Field: ERPx_APTransactionHeader.PmtCard |
| Description | Error rendering macro 'excerpt-include' : No link could be created for 'Description - Header'. This is a text box to assign a description to the Fisherman Sale transaction. This defaults as blank and is not required. If entered, it must <= 60 characters. This field is always editable.Database Field: ERPx_APTransactionHeader.Description |
| Doc Date | Identifies the date of the transaction. This is a text box that defaults to today's date. It is required and if missing, the message "Doc Date is required." will be displayed on Save. This is always editable while in a status of New. Database Field: ERPx_APTransactionHeader.TransactionDate |
| 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 is a text box that defaults to blank. This field is not required, but if entered, it must be <= 50 characters. The Doc No value must be unique by transaction type. No two Fisherman Sale or Tender Resale Doc No values may be the same, else the message "Duplicate Doc No's are not allowed. Please enter a valid Doc No." will be displayed on Save. This field is always editable. Database Field: ERPx_APTransactionHeader.DocNumber |
| Fisherman | 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. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Fishermen, Fishermen & Tenders, and Tenders that have not been excluded from the "Fisherman Sale" Transaction on the 'Excluded Transaction' tab of the Fisherman & Tender Record View. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK |
| On Account | Shows the total amount of the transaction, net of payment(s) received at the time of the transaction. This is the net amount that will charged or credited. This is a non-editable text box that is calculated as the [sum of the Extended column Amount] - ([Cash Amount] + [Check Amount] + [Credit Card Amount]). This defaults to "0.00", is required and never editable. This is a calculated value that is not stored in a database field. |
| Price List | Identifies the ID and Description of the Price List that is assigned to the transaction. This is a single-select standard lookup that is not required. This field is only enabled once a Fisherman is saved to the transaction. This defaults to blank. If a Fisherman Sale Price List exists, then it will default to the Fisherman Sale Price List associated with the selected Fisherman. If changed, the message "On Save, do you want to update existing prices of items found on the new Price List?" will be displayed. This field can only be edited while the transaction is set to a Status of New. Price Lists are used to store a group of Items with pre-defined prices and effective dates. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Fisherman Sale Price Lists. Database Fields: ERPx_MFPriceListHeader.PriceListID, ERPx_APTransactionHeader.PriceListHeaderSK |
| Status | 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 |
| Tax Class | Identifies the Tax Class that is assigned to the transaction. This is a single-select standard lookup that is not required. This field is only editable if the fisherman accounting preference for 'Enable Sales Tax on Fisherman Sales' is set to "Yes". If the user selected a Tax Class that shares the same currency as the Fisherman's Tax Class, then that Tax Class will remain selected. If the user selected a Tax Class that does not share the same currency as the Fisherman or did not select a Tax Class at all, this field will default to select the Tax Class selected on the Fisherman's record view Properties tab for 'Tax Class'. This field can only be edited while the transaction is set to a Status of New. Tax Classes store all the Tax Details (individual taxes) used to calculate sales tax on Quick Sales, Fisherman Sales, and Tender Resale transactions. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Tax Classes. Database Fields: ERPx_MFTaxClass.TaxClassName, ERPx_APTransactionHeader.TaxClassSK |
Properties Tab
| Fields | Description |
|---|---|
| Created By | 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 |
| Created Date | 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 |
| Currency ID | Identifies the Currency assigned to the transaction. This is a non-editable text box that defaults from the Currency assigned to the selected Fisherman. This is required and not editable from this page. Even though this field is required, it is currently for information only and does not drive any functionality. 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. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Company Currencies. Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_APTransactionHeader.CurrencySK |
| Fisherman ID | Identifies the ID of the Fisherman, Fisherman & Tender or Tender associated with the transaction. This is a non-editable text box that defaults as the ID of the selected Fisherman. This is required and only editable by changing the Fisherman assigned to the transaction. Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.VendorSK |
| GL Date | Identifies the date the transaction posted (or will post) to the general ledger. This is an editable date picker that defaults as blank and is required. If not manually edited, 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 |
| Last Updated | Identifies the Last Updated 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.LastUpdated |
| Last User | Identifies the name of the user that last updated 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.LastUser |
| Posted Date | Identifies the Date & Time the transaction was posted. This is a non-editable text box that defaults to blank and is populated at the time the transaction is posted. This is not required and not editable from this page. Database Field: ERPx_APTransactionHeader.PostedDate |
| Transaction Class | The unique identifier of the Transaction Class. This is a non-editable text box that is required and defaults as 'Default'. 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 |
Payment Details Tab
| Fields | Description |
|---|---|
| Amount | Identifies the amount of cash received as payment for the transaction. This is a text box to enter a Cash, Check and/or Credit Card payment from the Fisherman, Fisherman & Tender or Tender for the sale transaction. This defaults as "0.00" and is not required. The amount entered here will automatically update the 'Home' tab and the total 'On Account'. The 'On Account' amount is calculated as the [sum of the Extended column Amount] - ([Cash Amount] + [Check Amount] + [Credit Card Amount]) and is not stored in a database field. The amount fields are only enabled after item(s) have been added to the Items grid and is always editable while in a Status of New. Database Field: ERPx_APTransactionHeader.PmtCash, ERPx_APTransactionHeader.PmtCheck, ERPx_APTransactionHeader.PmtCard |
| Cash Account | Displays the account number and account description of the cash account associated with the checkbook selected to receive the payment. This is a non-editable text box that defaults to the selected Checkbook's 'Cash Account' field. This is required and can only be edited by changing the associated Checkbook. This field is only enabled after item(s) have been added to the Items grid and is always editable while in a Status of New. The lookup contains... Database Fields: ERPx_GLAccount.AccountNumber, ERPx_GLAccount.Description, ERPx_MFCheckbook.CashAccountSK, ERPx_APTransactionHeader.PmtCashCheckbookSK, ERPx_APTransactionHeader.PmtCheckCheckbookSK, ERPx_APTransactionHeader.PmtCardCheckbookSK |
| Checkbook | Identifies the Checkbook assigned to the transaction. This is a single-select standard lookup that defaults to the preference selection for 'Default Checkbook ID.' This field is only enabled after item(s) have been added to the Items grid and is always editable while in a Status of New. This is required only if a payment has been entered. The lookup contains a list of all the 'Active' Checkbooks. 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. Database Fields: ERPx_MFCheckbook.CheckbookDescription, ERPx_APTransactionHeader.PmtCashCheckbookSK, ERPx_APTransactionHeader.PmtCheckCheckbookSK, ERPx_APTransactionHeader.PmtCardCheckbookSK |
| Reference | Identifies the reference number of the payment you received, most often associated with a Check # Database Field: ERPx_APTransactionHeader.PmtCashReference, ERPx_APTransactionHeader.PmtCheckReference, ERPx_APTransactionHeader.PmtCardReference |
Attributes Tab
| Fields | Description |
|---|---|
| Attributes | A non editable text box that shows the name of the Attribute. Attributes are user-definable fields that are used on master files and transactions and are editable from the Attributes List View. The Attribute will only be displayed if the Applies property on the Assign Attribute Rules by page is set to either "Yes - Required" or "Yes - Not Required". Attributes set to "No" will not be displayed. The Attributes displayed here are setup and assigned in the Attributes section of the Company module (Company → Setup → Attributes → Fisherman). |
| Available | A non editable text box that shows whether the Attribute Value is required or not. If the Attribute Value is required it will display "Yes - Required" if it is optional it will display "Yes - Not Required". This value is only editable from the 'Assign Attribute Rules' page (Company → Setup → Attributes → Fisherman → Transactions hyperlink). |
| Value | Identifies the value assigned to the corresponding attribute. Because Attributes are configurable as either Text, List, Date, or Date/Time the data entry is either a text box, lookup, or date picker. The value defaults to blank and is only required if the Attribute's 'Applies' property is set to "Yes - Required" in the Assign Attribute Rules page. Attribute Values for Master Flies are always editable. Attribute Values for transactions are always editable for unposted transactions. |
Page Detail
Items Grid
The purpose of the Items grid is to add, edit and delete the line items for the Invoice and Credit Memo transaction.
| Toolbar Icons | Description |
| Delete | Deletes the selected line(s) from the transaction or master file. This icon is only enabled for transactions with a Status of 'New'. |
| Excel | 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 only the filtered contents will be exported. |
| New | Adds new blank lines in the grid section to allow for data entry. |
| Fields | Description |
|---|---|
| Checkbox | Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete. |
| Description | Identifies the Description for the line item. This is a text box that defaults to blank, but auto-populates from the 'Item Description' saved on the Item Master File of the selected Item, once an Item is selected from the Item drop-down menu. This field is required and must be <= 200 characters. This field is always editable while the transaction is in a Status of New or Approved. Database Field: ERPx_APTransactionLine.LineDescription |
| Extended | Identifies the Extended amount of the line item. This is a non-editable text box lookup that defaults as "0.00" and is required. This can only be edited by changing the Quantity and/or Price of the transaction line. It is calculated as [Quantity of line item] * [Price of line item]. Database Field: ERPx_APTransactionLine.ExtendedAmount |
| Item | Identifies the ID of the Item. This is a single-select standard lookup that defaults to blank. It is required and is always editable while in a Status of New. Item IDs are the unique identifier for Items. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Items in the Items Master File. Database Fields: ERPx_IMItem.ItemID, ERPx_IMItemItemDescription, ERPx_APTransactionLine.ItemSK |
| Price | Identifies the price of the line item. This is a text box that defaults as "0.00" and is required to be > 0. If not, the message "Price is required and must be greater than zero." will be displayed on Save. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionLine.Price |
| Quantity | Identifies the quantity of the line item. This is a text box that defaults as "1.00" and is required. The value entered in this field can be negative or positive to record both sales and returns. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionLine.Quantity |
| Sale Account | Identifies the GL Account that will be Credited on a sale or Debited on a sales return. This is a single-select stand lookup defaults from the Item's Sales account. It is required and if missing, the message "A Sale Account is required" will be displayed on Save. This is always editable while in a Status of new. The GL Account that is assigned for the "Sales" Account Type, on the Accounts tab of the Item Record View and Item Class Record View. The Sale Account identifies the revenue account that sale transactions post to. This lookup contains a blank value, the current assigned value, and all active GL Accounts with a 'Control Account Type' of "Sales" and the 'Use In SO' property set to "Yes". Database Fields: ERPx_GLAccount.AccountNumber, ERPx_GLAccount.Description, ERPx_APTransactionLine.AccountSK |
| UOM | Identifies the unit of measure that the items are stored in (Lbs, kgs, Cases, etc.) on the transaction. A UOM is a quantity used as a standard of measurement. It identifies how much makes up "1" of the measurement. Examples include Bag, Box, Each, Kg, Lb, ext. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Units of Measure. Database Fields: ERPx_IMUOM.UOMID, ERPx_APTransactionLine.QuantityUOMSK |