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. 

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 GL Account that will be Credited on a sale or Debited on a sales return.

Database Field: ERPx_GLAccount.AccountNumber, ERPx_APTransactionLine.AccountSK 

The GL Account that is assigned for the "Settlement Accrual" Account Type, on the Accounts tab of the Fisherman or Loan Record View and Fisherman Class Record View. This is the Balance Sheet account that is Debited or Credited when Fishing Transactions are posted for the selected Fisherman, Tender, or Loan account. 

Database Field: ERPx_GLAccount.AccountNumber, ERPx_APVendor.SAGLAcctref, ERPx_APTransactionHeader.VendorSK, ERPx_APTransactionLine.TransactionHeaderSK 

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. 

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.

Database Field: ERPx_APTransactionHeader.GLDate

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.

Database Field: ERPx_APTransactionHeader.GLDate

Identifies the ID of the Item.

Database Field: ERPx_IMItem.ItemID, ERPx_APTransactionLine.ItemSK

Identifies the class that is assigned to the Item on the transaction or transaction line.

Item Classes are used to identify default values that will be applied to new Inventory Items and to group Items together for reporting purposes.

Database Fields: ERPx_IMItemClass.ClassID, ERPx_IMItemClass.Description, ERPx_IMItem.ItemClassSk, ERPx_APTransactionLine.ItemSK

Identifies the Description associated with the Item ID assigned to a transaction line, journal line detail or master file record.

Database Field: ERPx_APTransactionLine.LineDescription

Identifies the type of the line item. This will either be:

• Sale: The row is for an Inventory Item ID that was sold.
• Tax: The row is for a total tax amount that was calculated for the transaction

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. 

Database Fields: ERPx_MFSite.SiteName, ERPx_APTransactionHeader.SiteSK

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

Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APTransactionHeader.TransactionStatusSK

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

Transaction numbers are system assigned IDs to differentiate unique transactions. Transaction ID's are unique by the unique combination of 'Transaction Type' + 'Transaction Class'. Clicking on the hyperlink opens the transaction record view.

Database Field: ERPx_APTransactionHeader.TransactionID

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_APTransactionClass.TransactionTypeSK, ERPx_APTransactionHeader.TransactionClassSK

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.

Database Fields: ERPx_IMUOM.UOMID, ERPx_APTransactionLine.QuantityUOMSK