Customer Activity Inquiry
The Customer Activity inquiry lists all the transactions posted against a customer account. From here, users can open the transaction, the Journal Details, or void transactions.
Software Version: 2023.09.15 and newer
Page Header
| Toolbar Icons | Description |
|---|---|
| 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.
|
| Inquiry Criteria | Opens Inquiry Criteria window where users can define the following criteria:
|
| Journal Details | Opens the Journal Details page for the selected record(s). |
| Refresh | Re-queries the contents of the grid/page based on the Inquiry Criteria parameters or the default parameters for grids that do not support Inquiry Criteria. |
| Void | Opens the Void Transaction page for the selected record. Only Quick Sales and Payment Receipts can be voided or corrected from here. Sales Orders, Price Adjustments, and Returns must be voided from the Transaction History Inquiry. |
| Fields | Description |
| Checkbox | Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete. |
| Avail. Disc. Amt. | A non-editable text box to display the calculated discount amount that the sales transaction is still eligible for. This is calculated for all sales invoices that were posted with a Payment Term that contained a discount (e.g., 2%10 Net 30). If the 'Trans. Date' of the document being applied falls within the discount days of the sales invoice date then an amount will be shown, otherwise it will be 0.00. This value in this field is informational only, a user is still able to override the actual 'Discount Amount'. This is a calculated amount and not linked to a Database Field. |
| Currency | Identifies the Currency assigned to the transaction. Database Fields AR Transactions: ERPx_MFCurrency.CurrencyID, ERPx_ARTransactionHeader.CurrencySK Database Fields for SO Transactions: ERPx_MFCurrency.CurrencyID, ERPx_SOOrderHeader.CurrencySK |
| Customer | Displays the unique identifier for the Customer record or for the Customer assigned to a transaction. Database Fields AR Transactions: ERPx_ARCustomer.CustomerID, ERPx_ARTransactionHeader.CustomerSK Database Fields for SO Transactions: ERPx_ARCustomer.CustomerID, ERPx_SOOrderHeader.CustomerSK |
| Customer Name | Identifies the name of the Customer record or for the Customer assigned to a transaction. Database Fields AR Transactions: ERPx_ARCustomer.CustomerName, ERPx_ARTransactionHeader.CustomerSK Database Fields for SO Transactions: ERPx_ARCustomer.CustomerName, ERPx_SOOrderHeader.CustomerSK |
| Discount Date | A date field to display the last day the Payment Terms discount is applicable. This is displayed for all Sales transactions that were posted with a Payment Term that contains a discount (e.g., 2%10 Net 30) and is calculated by adding the number of discount days to the invoice date for sales Invoices and to the Doc Date for Quick Sales. This field will be blank for all Sales Invoices, Price Adjustments, Returns, and Quick Sales that were posted with a Payment Terms that did not include a discount. This is a calculated field based on the payment terms assigned to the order and not linked to a Database Field. |
| Doc Date | A date field to show the date of the transaction. For Sales Invoice, Returns, and Price Adjustments this will be the Invoice Date and for Quick Sales this is the Doc Date. Database Field AR Transactions: ERPx_ARTransactionHeader.TransactionDate Database Field for SO Transactions: ERPx_SOOrderHeader.OrderDate |
| Doc Description | A non-editable text box to display the header comment/description of a Quick Sale or Payment Receipt transaction. This will always be blank for Sales Invoices, Returns, and Price Adjustment transactions. Database Field for AR Transactions: ERPx_ARTransactionHeader.Description Database Fields for SO Transactions: N/A |
| Doc No | A non-editable text box to display the 'Doc No' of a Quick Sale or Payment Receipt transaction. This will always be blank for Sales Invoices, Returns, and Price Adjustment transactions. Database Field AR Transactions: ERPx_ARTransactionHeader.DocNumber Database Fields for SO Transactions: N/A |
| Due Date | A date field to display the date the payment is due. This is displayed for all transactions in the grid and is calculated by adding the number of due days to the invoice date for sales Invoices and to the Doc Date for Quick Sales. This is a calculated field based on the payment terms assigned to the order and not linked to a Database Field. |
| Fully Applied Date | A textbox to identify the date that the transaction was fully settled. This will only display a date if the 'Fully Settled' field = "Yes". |
| Fully Applied Days | A textbox to identify how many days it took to fully settle the transaction. This field is used in the Average Days to pay calculation. |
| Fully Settled | A textbox to identify if the transaction has been fully settled. If "Yes", the transaction has been fully settled. If blank, there is still a remaining balance on the transaction. This is a calculated amount and not linked to a Database Field. |
| GL Date | Identifies the date the transaction posted (or will post) to the general ledger. Database Field AR Transactions: ERPx_ARTransactionHeader.GLDate Database Fields for SO Transactions: ERPx_SOInvoiceHeader.GLDate |
| GL Period | 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. |
| GL Year | 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. |
| Orig. Amt. | A non-editable text box to display the sales transaction amount. Database Fields AR Transactions: ERPx_ARTransactionHeader.ExtendedAmount Database Fields for SO Transactions: ERPx_SOOrderHeader.ExtendedAmount |
| Orig. Terms Disc. Amt. | A non-editable text box to display the discount amount the transaction was eligible for when it was posted. This is calculated for all Sales transactions posted with a Payment Term that contained a discount (e.g., 2%10 Net 30). If the transaction contained a Payment Term with a discount, an amount will be shown, otherwise it will be 0.00. This is calculated by multiplying the Payment Terms Discount Amount by the Invoice Amount. This will be blank for Payment Receipts. This is a calculated amount and not linked to a Database Field. |
| Open Amt. | A non-editable text box to display the open amount of the transaction. This is calculated by subtracting all previous Applied Amounts, Discount Amounts, and Write Off Amounts from the transactions 'Orig. Amount'. This is a calculated amount and not linked to a Database Field. |
| Payment Terms | A non-editable text box to display the Payment Term ID of the Payment Term the transaction was posted with. This defaults from the Customer but can be changed on the transaction prior to posting. Database Fields AR Transactions: ERPx_MFPaymentTerms.PaymentTermName, ERPx_ARTransactionHeader.PaymentTermSK Database Fields for SO Transactions: ERPx_MFPaymentTerms.PaymentTermName, ERPx_SOOrderHeader.PaymentTermSK |
| PO | A non-editable text box to display the the Purchase Order number (PO number) of a Sales Invoice, Return, and Price Adjustment transaction. This will always be blank for Quick Sales and Payment Receipt transactions. Database Field AR Transactions: N/A Database Fields for SO Transactions: ERPx_SOOrderHeader.PurchaseOrder |
| Posted Status | 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: Open: This refers to all Statuses that exist prior to posting. This includes New, Released, In Process, Staging, Loading, Shipped, and Approved. 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. 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. 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 AR Transactions: ERPx_APTransactionStatus.StatusName, ERPx_ARTransactionHeader.TransactionStatusSK Database Fields for SO Transactions: ERPx_APTransactionStatus.StatusName, ERPx_SOOrderHeader.OrderStatusSK |
| Transaction | 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 AR Transactions: ERPx_ARTransactionHeader.TransactionID Database Fields for SO Transactions: ERPx_SOOrderHeader.OrderID |
| Transaction Type | 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 be one of the following:
Database Fields AR Transactions: ERPx_ARTransactionType.TransactionName, ERPx_ARTransactionClass.TransactionTypeSK, ERPx_ARTransactionHeader.TransactionClassSK Database Fields for SO Transactions: ERPx_ARTransactionType.TransactionName, ERPx_SOOrderHeader.OrderTypeSK |
Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.