Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

AP Invoices represent transactions that carry amounts the company owes for purchasing goods or services from a Vendor. AP Credit Memos represent transactions that carry amounts owed to the company because of returns and/or credits on goods or services previously purchased from a Vendor. 

 This list view also contains columns for each Attribute that is set up for the 'AP Purchasing' and 'Items' attribute types. Because these are user defined, they are not included in the default view but can be added a saved layout. AP Purchasing and Items attributes are not included in the help documentation.

Software Version: 2021.11.24 and newer

Page Header

Filter ItemsDescription
Auto Hide FiltersA 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.
  • When checked, each time the 'Refresh' button is clicked, the search options will be hidden, allowing for more rows of data to be visible on the page. This behavior is ideal for users that have entered their search parameters and want to see the results in full-screen. 
  • When unchecked, the search options will not be hidden when the 'Refresh' button is clicked. This behavior is ideal for users that need to run several searches with different search parameters.

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.

Auto Refresh on OpenA non-required text box that defaults as checked and is used to determine if the inquiry opens with or without data in the grid.
  • When checked, each time the page is opened, the search is run using the default parameters (or a 'Saved Search' if one was set as your default for the page) so the grid will be populated with data .  
  • When unchecked, the search is NOT run when the page opens and no data will be present until the 'Refresh' button is clicked. 

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.

Also Include

A lookup to assign one or more conditions you want included in your search. This lookup contains:

  • Voids & Replaced
Date Option

A single-select lookup to identify which 'Date' field will be used. The lookup contains the following values:

  • Doc Date
  • GL Date
Date Range
A text box to identify the method for selecting a date range, a specific date, or a min/max date.

For help on using this control refer to the FAQ Article /wiki/spaces/HELP/pages/3108732991.

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

Refer to this FAQ for advanced search options.

Search

A non-required text box that defaults to blank and is used to search across multiple fields. When the page is 'Refreshed', the data returned will be limited by what was included in the Search box (in addition to any other Search Options). 

Refer to this FAQ for advanced search options.

The Search field can be used to search across the following fields: 

  • Doc No
  • Item & Doc Description
  • Purchase Order
  • Transaction
  • Vendor ID
  • Vendor Name
Transaction Class

Used to select one or more Transaction Classes. The values in this lookup are listed alphabetically. If there is more than one Transaction Class for the Transaction Type, then the value in the lookup will display as [Transaction Type] - [Transaction Class]. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each.

The lookup contains a list of all 'Active' AP Transaction Classes.

Vendor

Used to select one or more Vendors. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

A Vendor is a company or person that sells goods or services to your company. They are used in Purchasing and on Brokerage Sales Programs.

The lookup contains a list of all 'Active' Vendors

Vendor Class

Used to select one or more Vendor Classes. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

Vendor Classes are used to identify default values that will be applied to new Vendor accounts and to group Vendor accounts together for reporting purposes. 

The lookup contains a list of all 'Active' AP Vendor Classes.

Page Detail

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

(lightbulb) Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.

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

 Displays a drop down menu of related actions. The list of options includes: 

  • IQ: PO Linked Lines -Opens an inquiry with all the Purchase Orders, AP Invoices, AP Credit Memos, and Inventory Receipt lines with this Purchase Order assigned. 
  • RV: Transaction. Opens the Transaction Record View in a new Tab.
  • RV: Purchase OrderOpens the record view of the Purchase Order. If there is not a linked PO, a message will appear indicating "There is no Purchase Order for this transaction." 
  • Void Transaction: Opens the Void Transaction Window.
  • View in PaperVision - This option is only visible when the preferences for PaperVision are configured.
Print

 Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. 

When clicked, all the Reports that launch from the Print Dialog that are assigned to this page, and that the user has rights to (if Report Data Access is enabled) are displayed.

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.
RefreshRe-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. 
Saved Layouts 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.  

Please note that existing saved grid layouts will display the Filter Row as hidden by default.

Search Options Toggles between displaying and hiding the Search Options portion of the page.
FieldsDescription
CheckboxUsed to select one or more records.
1099 Amount

Identifies the amount applicable to the Vendor's 1099 statement amount.  This is a numeric text box that is not required and defaults as follows:

  • If the 1099 Type is set to "No 1099", the 1099 Amount is blank and not editable
  • If the 1099 Type is set to any value other than "No 1099" the 1099 Amount will default to the "Amount" value for the corresponding line item but can be overwritten to a value less than the "Amount" value. If a value is entered that is more than this amount, it will default back to the "Amount" value for the line item.  This is always editable even after the transaction is posted.

If the 1099 Type value is updated to "No 1099", the 1099 Amount value will be cleared, and if a 1099 Amount is entered manually by the user when the line item is added, the 1099 Amount will not default from or be updated to the line "Amount".  

Database Field: ERPx_APTransactionLine.TenNinetyNineAmount

1099 Type

If you plan on sending the Vendor a 1099 statement at the end of the year, this is used to specify the 1099 statement box number where you are most likely to report amounts. This is informational only and does not drive functionality. This is a single-select lookup that defaults from the 1099 Type of the Vendor assigned to the transaction. This is required and is always editable even after the transaction is posted.  

This lookup contains all the values in the ERPx_APTenNinetyNineType table.

Database fields: ERPx_APTenNinetyNineType.TenNinetyNineTypeDescription, ERPx_APVendor.TenNinetyNineTypeSK, ERPx_APTransactionLine.TenNinetyNineTypeSK

Amount

Identifies the Extended amount of the line item. This is required and is calculated as [Quantity] * [Price] for each transaction line. This can only be edited by changing the Quantity and/or Price of the transaction line. Positive lines represent a purchase and negative lines represent a purchase credit.

Database Field: ERPx_APTransactionLine.ExtendedAmount

Comment

Identifies an alternate comment/description for a line item. This is most commonly used to either identify the Vendor's Item ID or to add more clarity to a generic/bulk Item ID.  This is not required and can be edited from the 'Comment' on the 'Home' tab of the Invoice/Credit Memo Record View. This is always editable, even after the transaction is Posted.

Database Field: ERPx_APTransactionHeader.Description

Currency ID


Identifies the Currency assigned to the transaction. This is required and comes from the 'Currency ID' on the 'Properties' tab of the Invoice/Credit Memo Record View. This is not editable on the transaction.

The Currency identifies the kind of money used for transactions. For example, if a Customer or Vendor is setup with a Currency of "USD" then all transactions for them are stated in terms of US Dollars and all payments received or made must be in US Dollars.

Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_APTransactionHeader.CurrencySK

Distributed To

Identifies how the (extended) amount of the line item was, or will be, applied. Identifies the name of a Project, Employee, Fisherman, Tender or Fisherman Loan. This is not required and can be edited from the 'Distributed To' on the Item grid of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New.

Database Fields: ERPx_APVendor.VendorName, ERPx_MFEmployee.EmployeeName, ERPx_GLProject.ProjectDescription, ERPx_APTransactionLine.ToDistributionAccountSK

Distributed Type

Identifies the type of distribution based on the selected Distributed To field.  (Project, Fisherman, Tender or Loan). This is not required and is derived from the 'Distributed To' on the Item grid of the Invoice/Credit Memo Record View. This is only editable by changing the Distributed To field on the transaction. This contains the associated value in the MFDistributionType  Enumeration Class.

Database Field: ERPx_APTransactionLine.ToMFDistributionTypeEN

Doc Date

Identifies the date of the transaction. This is required and can be edited from the 'Doc Date' on the 'Home' tab of the Invoice/Credit Memo Record View. This is always editable, even after the transaction is Posted.

Database Field: ERPx_APTransactionHeader.TransactionDate

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' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the transaction/Invoice # assigned by your Vendor. This is always editable while the transaction is in a Status of New.

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 Invoice/Credit Memo Record View. 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 Invoice/Credit Memo Record View. 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 Invoice/Credit Memo Record View. This can only be edited by changing the GL Date.

Item Added

Identifies the Date & Time that the line item was added to the Transaction. This is formatted from the users 'Date Format' preference and is a system assigned value and is never editable by a user.

Database Field: ERPx_APTransactionHeader.CreatedDate TW: The columns are in the LV but I don't think we have this field in the DB

Item Added By

Identifies the name of the user that added the line item to 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.

Database Field: ERPx_APTransactionHeader.CreatedByTW: The columns are in the LV but I don't think we have this field in the DB

Item Description

Identifies the Description associated with the Item ID assigned to a transaction line, journal line detail or master file record. This is required.

Database Field: ERPx_APTransactionLine.ItemSK, ERPx_IMItem.ItemDescription

Item ID


Identifies the ID of the Item.  This is required.

Database Field: ERPx_APTransactionLine.ItemSK, ERPx_IMItem.ItemID

Item Last Updated

Identifies the Last Updated Date & Time of the line item on the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user.

Database Field: ERPx_APTransactionLine.LastUpdated

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

Database Field: ERPx_APTransactionLine.LastUser

Item Type


Error rendering macro 'excerpt-include' : No link could be created for 'Item Type'.
 This is required.

Line Comment


Identifies an alternate comment/description for a line item. This is most commonly used to either identify the Vendor's Item ID or to add more clarity to a generic/bulk Item ID.  This is not required and is always editable even after the transaction is posted.

Database Field: ERPx_APTransactionLine.LineDescription

Ln.

Identifies the Line # for each Transaction Line Item. The Line # sets the sort of the items on grids, list views, inquiries, and reports.This is not required

Database Field: ERPx_APTransactionLine.LineNumber

Payable GL Account

Identifies the payable account number for the line item. This is required and comes from the Vendor's 'Accounts Payable' on the 'GL Accounts' tab of the Vendors List View. Because this defaults from the Vendor, it is not editable on the transaction.

The GL Account that is assigned for the "Accounts Payable" Account Type, on the Accounts tab of the Vendor Record View and Vendor Class Record View. This is the account where accounts payable amounts are posted for the selected Vendor. 

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_APVendor.APGLAcctRef

Payable GL Account Description

Identifies the name of the payable account number for the line item. This is required and comes from the Vendor's 'Accounts Payable' on the 'GL Accounts' tab of the Vendors List View. Because this defaults from the Vendor, it is not editable on the transaction.

The GL Account that is assigned for the "Accounts Payable" Account Type, on the Accounts tab of the Vendor Record View and Vendor Class Record View. This is the account where accounts payable amounts are posted for the selected Vendor. 

Database Fields: ERPx_GLAccount.Description, ERPx_APVendor.APGLAcctRef

Pmt./Apply Hold

Displays as "Yes" for AP Invoices and Credit Memos that are on a Payment or Application hold. This is not required and can be edited from the 'Pmt./Apply Hold' on the 'Properties' tab of the Invoice/Credit Memo Record View. This is always editable, even for posted transactions as long as they have not yet been fully applied.

  • Invoices on hold will not be selected for payment when building AP Check Batches.
  • Credit Memos on hold cannot be selected to apply to open Invoice

Database Field: ERPx_APTransactionHeader.IsOnApplicationHold

PO #


Identifies the Purchase Order number (PO number) entered for the transaction or transaction line item. This is not required and can be edited from the 'PO #' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the purchase order you used when making the purchase. This is always editable while the transaction is in a Status of New.

(lightbulb) This field is only used for Purchase Orders setup in NorthScope. The 'Reference' field should be used to record a PO# on a transaction when the PO# does not exist in NorthScope. 

Database Field: ERPx_APTransactionHeader.PurchaseOrderID 

PO Ln.


Identifies the Purchase Order line item that the AP Invoice/Credit Memo line item is linked to. This is a single-select lookup that is not required. This is editable while the transaction is in a Status of "New"

 The Price and Quantity will not default from the Purchase Order line item. 

Database Field: ERPx_APTransactionLine.POLineSK

Price

Identifies the price of the line item. This is required and can be edited from the 'Price' on the Item grid of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New.

Database Fields: ERPx_APTransactionLine.Price

Purchase GL Account


Identifies the GL Account the purchase line will post to. This is required and can be edited from the 'Purchase GL Account' on the Item grid of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New. 

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_APTransactionLine.AccountSK

Purchase GL Account Description


Identifies the name of the General Ledger account assigned as the purchase account on the line item. This is required and can be edited from the 'Purchase GL Account' on the Item grid of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New. 

Database Fields: ERPx_GLAccount.Description, ERPx_APTransactionLine.AccountSK

Quantity

Identifies the quantity of the line item. This is required and can be edited from the 'Quantity' on the Item grid of the Invoice/Credit Memo Record View. This is always editable while the transaction is in a Status of New. 

Database Fields: ERPx_APTransactionLine.Quantity

Reference


Identifies the Reference entered for the transaction. This is text box that is not required and is always editable even after the transaction is posted.

A Reference number is used to record an additional tracking number that associates this transaction to another system. For example, if a transaction was imported from a 3rd party system this could be used to store the unique identifier from that system's transaction. 

Status

Identifies the Status of the transaction. This can be edited from the 'Status' on the 'Home' tab of the Invoice/Credit Memo 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 transaction in this List View include:

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.

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

Identifies the unique Transaction ID for each transaction. Clicking on this link opens the AP Invoice / Credit Memo Record View for the selected 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 Class ID


The unique identifier of the Transaction Class. This is required and comes from the 'Transaction Class ID' on the 'Properties' tab of the Invoice/Credit Memo Record View. This is not editable.

Transaction Classes are used to differentiate transactions within a Transaction Type. For example, Transaction Classes of Fresh and Frozen can be setup for the Transaction Type of 'Sales Order'. Transaction Classes are used in all functional areas throughout the application.

Database Fields: ERPx_APTransactionClass.TransactionClassDescription, ERPx_APTransactionHeader.TransactionClassSK

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.

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

UOM

Identifies the unit of measure that the units are stored in (Box, Bag, Case, Each, Tote, etc.) for a line item or on the transaction. This is not required and can be edited from the 'UOM' on the Item grid of the Invoice/Credit Memo Record View. This is only editable while the transaction is in a Status of New. 

Database Fields: ERPx_IMUOM.UOMID, ERPx_APTransactionLine.QuantityUOMSK

Vendor Class ID


Identifies the class that is assigned to the Vendor on the transaction. This is required and comes from the 'Vendor Class' assigned to the 'Vendor' that is selected on the 'Home' tab of the Invoice/Credit Memo Record View. Because this defaults from the Vendor it is not editable on the transaction.

Vendor Classes are used to identify default values that will be applied to new Vendor accounts and to group Vendor accounts together for reporting purposes. 

Database Field: ERPx_APVendorClass.ClassDescription, ERPx_APTransactionHeader.VendorSK

Vendor ID

Identifies the ID of the Vendor account that is assigned to the transaction. This is required and represents the ID of the 'Vendor' on the 'Home' tab of the Invoice/Credit Memo Record View. This is only editable by changing the Vendor assigned to the transaction.

Vendor IDs are used as a short description and unique identifier for Vendor records. They can be changed at any time to any alphanumeric value. If you do not have an existing strategy for Vendor IDs the 3-3-2 method would be recommended.

Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.VendorSK

Vendor Name

Identifies the name of the Vendor assigned to the transaction or master file. This is set in the Vendor Record View This is required and represents the name of the 'Vendor' on the 'Home' tab of the Invoice/Credit Memo Record View. This is only editable by changing the Vendor assigned to the transaction.

Vendor Names are used as a long description for Vendors.

Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK

Related Topics



 Page Definitions

Page Definitions


 Technical Details

Technical Details

  • No labels