Other Transactions List View
- Emma Greenwood
- Tom Williams
The purpose of this page is to view, add, edit, remove, and post Adjustments, Balance Transfers and Payment Receipts. Additionally, users can Mass Update the Status of multiple transactions at once.
Software Version: 2021.02.19 and newer
Page Header
| Toolbar Icons | Description |
|---|---|
| Delete | Deletes the selected record(s). When clicked, users will be prompted with: "Are you sure you want to delete the selected records?". Click "OK" to confirm, or "Cancel" to return without deleting. WARNING: Records cannot be recovered once they are deleted! |
| Edit | Opens the selected record for editing. If a record is not selected, the page will not open. |
| Excel | 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. |
| Favorites |   Clicking on the star icon when it is an outline, adds the page to the 'My Shortcuts' tab and fills in the star. Clicking on the star icon when it is filled in (solid color), removes the page from the 'My Shortcuts' tab and returns the icon to an outline.
|
| Grid Layout | 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).
|
| Help | Opens the online WIKI help page for the current page.
|
| Mass Update | Opens the mass update dialog, which allows to mass update the following properties:
|
| New | Allows users to select the type of transaction or record they want to add. The list contains:
|
| Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. | |
| Fields | Description |
| Checkbox | Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete. |
| Amount | Displays the amount of the transaction, in the currency and currency format of the transaction. This comes from the total of all the 'Extended' values for each line item on the Adjustment and Balance Transfer, and the 'Receipt Amount' for Payment Receipt transactions. This is required on all transaction types, for Adjustments and Balance Transfers it can only be edited by changing the quantity and/or price of one or more transaction lines and for Payment Receipts while the transaction is in New status and does not have any applications. Database Field: ERPx_APTransactionHeader.ExtendedAmount |
| Created | Identifies the Created Date & Time of the record, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. Linked Database Field: ERPx_APTransactionHeader.CreatedDate |
| Created By | Identifies the name of the user that created the record. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. Linked Database Field: ERPx_APTransactionHeader.CreatedBy |
| Doc Date | Identifies the date of the transaction. This is required and can be edited from the 'Date' or 'Receipt Date' field on the associated Record View. This editable from the Record View while the transaction is in New status. Database Field: ERPx_APTransactionHeader.TransactionDate |
| 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 Payment Receipt Record View. This is always editable, even after the transaction is Posted.
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 required and can be edited from the 'Doc No' / 'Payment #' on the associated Record View. This is always editable, even after the transaction is Posted. Database Field: ERPx_APTransactionHeader.DocNumber |
| Fisherman | Identifies the ID of the Fisherman, Fisherman & Tender or Tender associated with the transaction. This is required and represents the ID of the Fisherman selected in the 'Received From' field on the Payment Receipt Record View. This is only editable by changing the Fisherman assigned to the transaction while in New status and no applications have been made. 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.
Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.VendorSK |
| Fisherman Name | Identifies the name of the Fisherman, Fisherman & Tender, Tender or Loan.This is required and represents the name of the Fisherman selected in the 'Received From' field on the Payment Receipt Record View. This is only editable by changing the Fisherman assigned to the transaction while in New status and no applications have been made.
Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK |
| 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 Adjustment and Balance Transfer Record View and the 'Receipt Date' on the Payment Receipt Record View. This can only be edited by changing the GL Date/Receipt 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 Adjustment and Balance Transfer Record View and the 'Receipt Date' on the Payment Receipt Record View. This can only be edited by changing the GL Date/Receipt Date. |
| Last Updated | Identifies the Last Updated Date & Time of the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. Linked Database Field: ERPx_APTransactionHeader.LastUpdated |
| Last Updated By | Identifies the name of the user that last updated the Transaction. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. Linked Database Field: ERPx_APTransactionHeader.LastUser |
| Status | Identifies the Status of the transaction. This is required and can be edited from the 'Status' field on each Record View and represents the status of the transaction. This is always editable while the transaction is in a Status of 'New' or 'Approved'. 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. Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APTransactionHeader.TransactionStatusSK |
| Transaction | Identifies the unique Transaction ID for each transaction. Clicking on this link opens the Record View for the corresponding record. 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 Field: ERPx_APTransactionHeader.TransactionID |
| Transaction Type | Identifies the Transaction Type for each transaction. This is required and displays the type of transaction for the corresponding record. There are three different transaction types for this page:
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 |
Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.