This page lists the Purchase Order, all AP Invoices/Credit Memo, and all Inventory Receipt transactions. The purpose of this page is to quickly show all the Purchase Order related transactions.
This list view also contains columns for each Attribute that is set up for 'AP Purchasing'. 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
Search
| Filter Items | Description |
|---|---|
| Auto Hide Filters |  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.
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 Open |  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.
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. |
| PO # | Used to select all or part of a PO #. This is a text box that is not required. |
| Requisition | Used to select all or part of a Requisition #. This is a text box that is not required. |
| Saved Searches |  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. 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:
|
| 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. |
Page Detail
| Toolbar Icons | Description |
|---|---|
| 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.
|
| 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. |
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. |
| Refresh |
|
| 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. |
| Fields | Description |
| Checkbox | Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete. |
| Comment | Identifies the header comment/description of the transaction or batch. This is not required and can be edited from the 'Comment' field on the 'Home' tab of the transaction Record View. This is always editable even after the transaction is 'Closed'. Database Field: ERPx_APPoHeader.Description, ERPx_APTransactionHeader.Description, ERPx_IMTransactionHeader.Description |
| Requisition # | Identifies the (source) requisition number that the Purchase Order belongs to. This is not required and can be edited from the 'Requisition' field on the 'Home' tab of the Purchase Order Record View. This is always editable until the Purchase Order is 'Closed'. A purchase requisition is a document used to inform department managers, or the purchasing officer, of the decision to purchase so that the purchasing department can start the purchase ordering process. A requisition can have one or more Purchase Orders. Database Field: ERPx_APPoHeader.Requisition |
| Site ID | Identifies the unique Site ID (warehouse ID) of the Site the transaction, shipment, item, or lot is associated with. This is only applicable for Purchase Order and IM Receipts (it is not applicable for AP Invoice/Credit Memos) and it is only required for IM Receipts. Database Field: ERPx_MFSite.SiteID, ERPx_APPoHeader.SiteSK, ERPx_IMTransactionHeader.SiteSK |
| Status | Identifies the Status of the transaction. This is required and is always editable. The Statuses that apply to Purchase Orders in this inquiry 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. Released: This status is used to signify that the transaction is ready to be released to production. While in the Status of 'Released', all editable fields are open for edit. Closed: Used to indicate that the record is no longer open to be used on other transactions. Closed records are only visible from inquiries, not list views. The Statuses that apply to AP Invoices/Credit Memos and IM Receipts in this inquiry 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. 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. Database Fields: ERPx_APPOStatus.StatusName, ERPx_APPoHeader.POStatusSK, ERPx_APTransactionHeader.TransactionStatusSK, ERPx_IMTransactionHeader.TransactionStatusSK |
| Transaction Class | The unique identifier of the Transaction Class. This is required and comes from the 'Transaction Class' on the 'Properties' tab of the transaction 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_APPoHeader.TransactionClassSK, ERPx_APTransactionHeader.TransactionClassSK, ERPx_IMTransactionClass.TransactionClassID, ERPx_IMTransactionHeader.TransactionClassSK |
| Transaction Date | Identifies the date of the transaction. This is required and can be edited from the 'Home' tab of the Transaction Record View. This is editable until the Purchase Order is 'Closed' or the transaction is in a Status >= "Approved". Database Field: ERPx_APPoHeader.PODate, ERPx_APTransactionHeader.TransactionDate, ERPx_IMTransactionHeader.TransactionDate |
| Transaction ID | Identifies the unique Transaction ID for each transaction. Database Field: ERPx_APPoHeader.PurchaseOrderID, ERPx_APTransactionHeader.TransactionID, ERPx_IMTransactionHeader.TransactionID |
| 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. The Transaction Types applicable to this inquiry include:
|
| 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 transaction 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_APPoHeader.VendorSK, ERPx_APTransactionHeader.VendorSK, ERPx_IMTransactionHeader.ReceivedFromVendorSK |
| 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 Name' on the 'Home' tab of the transaction 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_APPoHeader.VendorSK, ERPx_APTransactionHeader.VendorSK, ERPx_IMTransactionHeader.ReceivedFromVendorSK |
