Receivable documents are transactions generated in the Sales Functional Area. The purpose of this page is to display all outstanding credit balance transactions that have not been fully applied. From here, users can select a single transaction and click the 'Apply Documents' icon in the header toolbar to manually apply the selected transaction to one or more debit balance transactions.
Software Version: 2021.xx.xx and newer
Page Header
| Toolbar Icons | Description |
|---|---|
| Apply Document | Opens the Apply Documents record view. Users must select a transaction prior clicking this toolbar icon. Only one transaction can be selected at a time. If no transaction is selected, the message "Please select one item and try again." will be displayed. |
| 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. |
| 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:
|
| 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. |
| Fields | Description |
| Checkbox | Used to select one transaction to apply a document to. |
| Customer | Error rendering macro 'excerpt-include' : No link could be created for 'Customer ID - Transaction'. This field is required and is not editable after the transaction has been posted.Customer IDs are used as a short description and the unique identifier for Customers. They can be changed at any time to any alphanumeric value. If you do not have an existing strategy for Customer IDs the 3-3-2 method would be recommended. Database Fields: ERPx_ARCustomer.CustomerID, ERPx_ARTransactionHeader.CustomerSK (Payment Receipt), ERPx_SOOrderHeader.CustomerSK (Price Adjustment and Return) |
| Customer Name | Error rendering macro 'excerpt-include' : No link could be created for 'Customer Name - Transaction'. This field is required and is not editable after the transaction has been posted.Customer Names are used as a long description for Customer records. Database Fields: ERPx_ARCustomer.CustomerName, ERPx_ARTransactionHeader.CustomerSK (Payment Receipt), ERPx_SOOrderHeader.CustomerSK (Price Adjustment and Return) |
| Doc Date | Identifies the date of the transaction. This field is required. It comes from the 'Invoiced' field on the 'Shipments' tab of the Sales Transaction List View for Return and Price Adjustment transactions. It comes from the 'Receipt Date' field on the 'Home' tab of the Payment Receipt Record View for Payment Receipt transactions. This field is not editable after the transaction has been posted. Database Fields: ERPx_ARTransactionHeader.TransactionDate (Payment Receipt), ERPx_SOInvoiceHeader.InvoiceDate (Price Adjustment and Return) |
| 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 field is not required. There is no 'Doc No' associated with Return and Price Adjustment transactions. For Payment Receipt transactions, this field comes from the 'Payment #' field on the Payment Receipt Record View. This field is not editable after the transaction has been posted. Database Field: ERPx_ARTransactionHeader.DocNumber (Payment Receipt) |
| GL Date | Identifies the date the transaction posted (or will post) to the general ledger. This field is required and is not editable after the transaction has been posted. Database Field: ERPx_ARTransactionHeader.GLDate (Payment Receipt), ERPx_SOInvoiceHeader.GLDate (Price Adjustment and Return) |
| GL Period | Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This field is required and calculated using the 'GL Date' on the 'Properties' tab (Payment Receipt transaction) or 'Shipments' tab (Return and Price Adjustment transaction) of the associated transaction Record View. This field is not editable. |
| GL Year | Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This field is required and calculated using the 'GL Date' on the 'Properties' tab (Payment Receipt transaction) or 'Shipments' tab (Return and Price Adjustment transaction) of the associated transaction Record View. This field is not editable. |
| Original Amount | Displays the total amount of the transaction. Database Fields: |
| 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........... 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: |
| 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: |
| 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 Documents record view. This is calculated by subtracting previous applications from the original amount. This value is not stored in the database. |
The bolded view is the default view, which will determine the view will automatically display in when opened.