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. 

Opens Inquiry Criteria window where users can define the following criteria: 

• Date From
• Date To
• Status

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 Fields: ERPx_GLAccount.AccountNumber, ERPx_APVendor.SAGLAcctRef, ERPx_APTransactionHeaderVendorSK 

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

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.

Identifies the Description for the line item.

Database Field: ERPx_APTransactionLine.LineDescription

Identifies the GL Account number of the GL Account that is used for the Adjustment line item. This will be the GL Account that is credited when the 'Extended' amount is positive and debited when it is negative.

This lookup contains a blank value, the current assigned value, and all active GL Accounts where 'Use in AP' = "Yes".

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_APTransactionLine.AccountSK 

Identifies the GL Account description of the GL Account that is used for the Adjustment line item. This will be the GL Account that is credited when the 'Extended' amount is positive and debited when it is negative.

Database Fields: ERPx_GLAccount.Description, ERPx_APTransactionLine.AccountSK 

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

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. This will always be "Adjustment".

Database Fields: ERPx_APTransactionType.TransactionName, ERPx_APTransactionClass.TransactionTypeSK, ERPx_APTransactionHeader.TransactionClassSK

Displays the unit of measure upon which the line item price is based. 

Database Field: ERPx_APTransactionLine.QuantityUOMSK