Used to select one or more Vendor Classes. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

Vendor Classes are used to identify default values that will be applied to new Vendor accounts and to group Vendor accounts together for reporting purposes. 

The lookup contains a list of all 'Active' Fisherman Classes.

Used to select one or more Fishermen, Tenders, Fishermen and Tenders or Loans. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

A Fisherman is an Account Type used to identify someone that catches fish and sells them to a processing facility. A Fisherman & Tender is an Account Type used to identify someone that catches fish during one season and provides Tendering services during another. 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 Loan is an Account Type used to identify the Fisherman and/or Tender whom the loan was issued to.

The lookup contains a list of all Fishermen, Tenders, Fishermen & Tenders, and Loans.

Used to select one or more Vendor Types. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

Vendor Types are used to classify Vendor Classes by functionality. In Accounts Payable, all Vendors are auto-assigned a Vendor Type of "Vendor". In Fisherman Accounting, accounts can be assigned a Vendor Type of either Fisherman, Tender, Fisherman & Tender, or Loan. 

This lookup contains the values in the APVendorType Enumeration Class where Enumeration Value is 2, 3, 4, or 5.

Toolbar Icons

Identifies the ID of the Fisherman, Fisherman & Tender, Tender or Loan.

Database Fields: ERPx_APVendor.VendorID

Identifies the name of the Fisherman, Fisherman & Tender, Tender or Loan.

Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK (Payment Receipt, Fisherman Sale & Tender Resale), ERPx_APTransactionLine.ToDistributionAccountSK (Adjustment & Balance Transfer), ERPx_APTransactionHeader.VendorSK (AP Invoice & AP Credit Memo), ERPx_APDeliveryTicketHeader.FishermanAccountVendorSK (Fish Ticket), ERPx_APSettlementTransaction.SettleToEntitySK (Payment), ERPx_APPoHeader.VendorSK (Purchase Order)

Identifies the type of account the transaction is associated with. This comes from the 'Vendor Type' field on the 'Properties' tab of the Vendor Class Record View. This field is only editable when the 'Vendor Class' is updated for the associated Account.

Vendor Types are used to classify Vendor Classes by functionality. In Accounts Payable, all Vendors are auto-assigned a Vendor Type of "Vendor". In Fisherman Accounting, accounts can be assigned a Vendor Type of either Fisherman, Tender, Fisherman & Tender, or Loan. 

Database Field: ERPx_APVendor.VendorTypeEN

Identifies the date of the transaction. 

Database Field: ERPx_APTransactionHeader.TransactionDate or ERPx_APDeliveryTicketHeader.TicketDate or ERPx_APPoHeader.PODate

Identifies the date of the transaction.

Database Fields: ERPx_APVendor.SAGLAcct

Identifies the header comment/description of the transaction or batch.

This field can be edited from the header 'Description' field on the 'Home' tab or header of the associated transaction. For Payment transactions, this can be edited from the 'Description' field in the grid of the Process Payments Record View. This is always editable while the transaction is in a Status of "New".

Database Field: ERPx_APTransactionHeader.Description or ERPx_APPoHeader.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 field can be edited from the 'Doc No' field on the 'Home' tab or header of the associated transaction if the transaction contains the field. For Payment Receipt transactions, this field can be edited from the 'Payment #' field on the Payment Receipt Record View. This is always editable while the transaction is in a Status of "New".

Database Field: ERPx_APTransactionHeader.DocNumber

Identifies the Master Account assigned to the Account.

The Master Account is a way to associate more than one Fisherman Accounts together for informational purposes.

Displays the total net balance of the transaction. This is calculated as [Posted Balance]+[Open Transactions]-[Open POs]. Negative net balances will appear within parentheses. This field is not editable.

Database Fields: ERPx_APTransactionHeader.ExtendedAmount or ERPx_APDeliveryTicketHeaderTotalNetAmount

Displays the total amount distributed to the Account on a Purchase Order transaction in a Status of "Open". This is a calculated field and is editable by changing the 'Quantity' and/or 'Price' fields for a line item on the Purchase Order Record View while the transaction is in a Status of "New".

Database Field: ERPx_APPoHeader.OrderedAmount

Displays the total balance of the transaction if the status is "New" or "Approved". Please note that Open Amounts for tickets will display the total amount for the ticket and may not accurately reflect the total amount that will affect the account on posting. Negative balances will appear within parentheses. This is a calculated field and is not editable.

Database Fields: ERPx_APTransactionHeader.ExtendedAmount or ERPx_APDeliveryTicketHeaderTotalNetAmount

Displays the total balance of the transaction if the status is "Ready to Post" or "Posted". Negative balances will appear within parentheses. This is a calculated field and is not editable.

Database Fields: ERPx_APTransactionHeader.ExtendedAmount or ERPx_APDeliveryTicketHeaderTotalNetAmount

This field will either display "Open", "Posted" or "Void". This can be edited from the 'Status' field on the 'Home' tab or header of the associated transaction. All statuses less than "Ready to Post" will be displayed as "Open". This field is editable while the transaction is in a Status less than "Ready to Post".

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 Inquiry include:

Open: This is the default Status for all new records. While in the Status of 'Open', all editable fields are open for edit.

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.

Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APTransactionHeader.TransactionStatusSK or ERPx_APDeliveryTicketHeader.TransactionStatusSK or ERPx_APPoHeader.TransactionStatusEN

Identifies the Transaction Type for each transaction. This comes from the Transaction Type selected when starting a new transaction. This is never editable.

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 Fields: ERPx_APTransactionType.TransactionName, ERPx_APTransactionHeader.TransactionClassSK or ERPx_APDeliveryTicketHeader.TransactionClassSK or ERPx_APPoHeader.TransactionTypeEN

Identifies the unique Transaction ID for each transaction. Clicking on this link opens the transaction record view for the selected record. This is a system assigned number that comes from the 'Transaction Class' and is never editable.

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 or ERPx_APDeliveryTicketHeader.TicketNumber or ERPx_APPoHeader.PurchaseOrderID