Unapplied Fishing Documents List View 3.0
The purpose of this page is to display all outstanding Debit balance transactions that have not been fully applied. From here, users can select a single transaction and click the 'Apply Document' icon in the header toolbar to manually apply the selected transaction to one or more Credit balance transactions.
Software Version: 2025.04.21 and newer
Page Header
Search
Search Options | Description |
---|---|
Auto Hide Filters |
Users can only change the default value of this setting with a custom search in the "Saved Searches" lookup. If you change the default setting but do not save it in a custom search, it will only remain this way while the page is opened. Refer to this FAQ for advanced search options. A non-required text box that defaults as checked and is used to determine if the Search Options should be hidden when the Inquiry runs or is refreshed. |
Auto Refresh on Open |
Users can only change the default value of this setting with a custom search in the "Saved Searches" lookup. Refer to this FAQ for advanced search options. A non-required text box that defaults as checked and is used to determine if the inquiry opens with or without data in the grid. |
Fisherman | A multi-select lookup that defaults to the Account(s) that was selected prior to clicking the Apply Documents button on the Fisherman Balances list view. If no Account was selected, all the accounts that were visible in the grid will default in the lookup. |
Hide fully applied transactions | A Yes/No lookup that defaults to "Yes". If set to Yes then fully applied transactions will not be visible. |
Include transactions through | A Date picker to select a date that determines which transactions to include in the grid. It defaults to the current date but can be changed at any time. |
Saved Searches | Refer to this FAQ for advanced search options. Displays the saved searches lookup and related icons. This tool allows users to select previously saved search options, create a new set of search options, save changes to existing search options, forget/delete saved search options and/or assign a saved search option as the default for the page. Once changes are made to the search options, the user can click the Save Options icon and save the changes. Saving search options will also save the preferences for 'Auto Refresh on Open' and 'Auto Hide Filters'. The new search option can also be set as the default. Default searches can be removed by clicking the 'Set as Default' button again when the current default search is selected. |
Page Detail
Toolbar Icons | Description |
---|---|
Apply Document | Opens the Apply Fishing Transactions Record View. Users must select a transaction prior clicking this toolbar icon. Only one transaction can be selected at a time. |
Column Filter Show/Hide | Toggles between displaying and hiding a filter row in the grid under the column headers. The filter row will be displayed by default if the Quick Column Filter is also implemented in the page. When enabled, this will allow users to type in text to filter by a specific column. |
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, or excluded columns, only the contents in the grid will be exported. |
Group By Show/Hide | Toggles between displaying and hiding a row in the grid above the column headers to enable grouping by one or more column(s). Once displayed, users may drag and drop column headers to group by a specific column. Once the grid is grouped by a column(s), a subtotal footer row will display in the grouping for columns that have a page footer total. |
Help | Opens the online WIKI help page for the current page. |
Quick Column Filter | Used to filter across all columns in the grid. When the user types text into the Quick Column Filter text box, the grid's Filter Row will be automatically hidden. The text in the Quick Column Filter text box automatically replaces any existing Filter Row filters. The results of the data immediately refresh as you enter text. |
Refresh |
|
Saved Layouts | Please note that existing saved grid layouts will display the Filter Row as hidden by default. Displays the column layout lookup and related icons. This tool allows users to select a previously saved layout, create a new layout, save changes to a layout, forget/delete a layout and/or assign a saved layout as the default for the page. Once changes are made to the layout, such as columns are added or removed, the user can click the Save Layout icon and save the changes to the column layout. The visibility of the Filter Row is also saved with a saved layout. The new layout can also be set as the default. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific). Default layouts can be removed by clicking the 'Set as Default' button again when the current default layout is selected. |
Search Options | Toggles between displaying and hiding the Search Options portion of the page. |
Fields | Description |
Checkbox | Used to select one transaction to apply a document to. |
Account | Identifies the ID of the Fisherman, Fisherman & Tender, Tender or Loan. This is required and comes from the 'Fisherman ID' or 'Loan ID' field on the Fishermen & Tenders record view or Loan record view. This is only editable by changing the Fisherman, Fisherman & Tender, Tender, or Loan assigned to the transaction. Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.VendorSK, ERPx_APTransactionLine.AccountSK, ERPx_APTransactionLine.FromDistributionAccountSK, ERPx_APTransactionLine.ToDistributionAccountSK, ERPx_APDeliveryTicketHeader.FishermanAccountVendorSK |
Account Class | Identifies the description of the Fisherman Class associated with the transaction. This is required and comes from the 'Fisherman Class ID' field on the Fishermen & Tenders record view. This is only editable by changing the Fisherman, Fisherman & Tender or Tender assigned to the transaction. Database Fields: ERPx_APVendor.VendorClassSK, ERPx_APTransactionHeader.VendorSK, ERPx_APTransactionLine.AccountSK, ERPx_APTransactionLine.FromDistributionAccountSK, ERPx_APTransactionLine.ToDistributionAccountSK , ERPx_APDeliveryTicketHeader.FishermanAccountVendorSK |
Account Name | Identifies the name of the Fisherman, Fisherman & Tender, Tender or Loan. This is required and comes from the 'Fisherman Name' or 'Loan Name' field on the Fishermen & Tenders record view or Loan record view. This is only editable by changing the Fisherman, Fisherman & Tender, Tender or Loan assigned to the transaction. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK, ERPx_APTransactionLine.AccountSK, ERPx_APTransactionLine.FromDistributionAccountSK, ERPx_APTransactionLine.ToDistributionAccountSK, ERPx_APDeliveryTicketHeader.FishermanAccountVendorSK |
Distributed Description | Identifies a description of the distribution, including the name of the Vendor, Fisherman, Fisherman & Tender, Tender or Loan. This is required for Tender Resale, AP Invoice/Credit Memo and Balance Transfer transaction types and not required for all other transaction types. For Tender Resale transaction types, this field can be edited from the 'Tender' field on the Tender Resale record view. For AP Invoice/Credit Memo transaction types, this field can be edited from the 'Vendor' field on the Invoice/Credit Memo record view. For Balance Transfer transaction types, this field can be edited from the 'Transfer Balance To - Credit' field on the Balance Transfer record view. This is only editable by changing the 'Tender', 'Vendor' or 'Transfer Balance To - Credit' fields on the associated transactions. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.FromVendorSK (Tender Resale), ERPx_APTransactionHeader.VendorSK (AP Invoice/Credit Memo), ERPx_APTransactionLine.ToDistributionAccountSK (Balance Transfer) |
Doc Date | Identifies the date of the transaction. This is required and can be edited from the 'Date' field on the in the associated transaction header. This is always editable while the transaction is in a Status of New. Database Fields: ERPx_APTransactionHeader.TransactionDate, ERPx_APDeliveryTicketHeader.TicketDate |
Doc Description | Identifies the header comment/description of the transaction or batch. This is not required and can be edited from the 'Description' field on the associated transaction header. This is always editable. Database Field: ERPx_APTransactionHeader.Description |
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 not required and can be edited from the 'Doc No' field on the in the associated transaction header. This is always editable while the transaction is in a Status of New. Depending on the transaction type, this is sometimes editable after the transaction has been posted. Database Field: ERPx_APTransactionHeader.DocNumber |
GL Date | Identifies the date the transaction posted (or will post) to the general ledger. This is required and can be edited from the 'GL Date' on the 'Properties' tab of the associated transaction. If not manually edited, this 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 |
GL Period | Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This is required and calculated using the 'GL Date' on the 'Properties' tab of the associated transaction. This can only be edited by changing the GL Date. |
GL Year | Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This is required and calculated using the 'GL Date' on the 'Properties' tab of the associated transaction. This can only be edited by changing the GL Date. |
Line Description | Identifies the Description for the line item. This is required for Adjustments, AP Invoices/Credit Memos, Tender Resales and Balance Transfers. This can be edited from the 'Description' on the Item grid of the associated transaction. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionLine.LineDescription |
Original Amount | Displays the total amount of the transaction. For AP Invoice/Credit Memo, Adjustment, Tender Resale and Balance Transfer transaction types, this displays the 'Extended' amount of the individual line item. For Fish Ticket transaction types, this displays the 'Amount' field. For Fisherman Sale transaction types, this displays the 'On Account' field. For Check and ACH payment transaction types, this displays the 'Amount' field for the specific check or ACH payment. This is required and can be edited by changing the Price or Quantity of line items. This can only be edited while in a Status of New.
Database Fields: ERPx_APTransactionLine.ExtendedAmount, ERPx_APTransactionheader.ExtendedAmount, ERPx_APDeliveryTicketHeader.TotalAmount |
Transaction | Identifies the unique Transaction ID for each transaction. Clicking on this link opens the record view for the selected transaction. This is a system assigned number that comes from the 'Transaction Class' and is required but is not editable by users. 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 Fields: ERPx_APTransactionHeader.TransactionID, ERPx_APDeliveryTicketHeader.TicketNumber |
Transaction Type | Identifies the Transaction Type for each transaction. This is required and comes from the Transaction Type selected when starting a new transaction. This is never editable. The following transaction types have the ability to debit the Settlement Accrual Account and display on this page:
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 |
Unapplied Amount | Displays the amount of the transaction that is not yet applied. This is required and updates when amounts are entered in the 'Applied Amount' field on the Apply Fishing Transactions record view. This is calculated by subtracting previous applications from the original amount. This value is not stored in the database.
|