Allows users to select the type of transaction or record 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 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

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

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

Identifies the header comment/description of the transaction or batch. 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

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

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

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.

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.

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.

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

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

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

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

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

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

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

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.

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_GLAccount.Description, ERPx_MFCheckbook.CashAccountSK, ERPx_APTransactionHeader.PmtCashCheckbookSK, ERPx_APTransactionHeader.PmtCheckCheckbookSK, ERPx_APTransactionHeader.PmtCardCheckbookSK

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

Identifies the reference number of the payment you received, most often associated with a Check #
This is a text box that defaults to blank. It is not required, but if entered, must be <= 150 characters. The Reference value is only saved when the Amount field is populated. 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.PmtCashReference, ERPx_APTransactionHeader.PmtCheckReference, ERPx_APTransactionHeader.PmtCardReference

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). 

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). 

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

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

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 Item Master File.

Database Fields: ERPx_IMItem.ItemID, ERPx_IMItemItemDescription, ERPx_APTransactionLine.ItemSK

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

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

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

Identifies the unit of measure that the items are stored in (Lbs, kgs, Cases, etc.) on the transaction.
This is a single-select standard lookup that defaults as blank and is not required. Once an Item is selected, this field defaults to the Item UOM default. This is always editable while the transaction is in a Status of New. 

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