Purchase Order Transaction Class Record View
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. The purpose of this page is to add, edit, remove, and activate/inactive these records.
Software Version: 2025.04.21 and newer
Page Header
Header Toolbar
Toolbar Icons | Description |
---|---|
Delete | WARNING: Records cannot be recovered once they are deleted! Deletes the transaction, batch, or master file record. When clicked, users will be prompted with: "Are you sure you want to delete this record?". Click "OK" to confirm, or "Cancel" to return without deleting. |
Help | Opens the online WIKI help page for the current page. |
New | Opens a new blank record for data entry. |
Save | Saves the changes made to the record. |
Save & Close | Saves your changes and closes the page. |
Fields | Description |
Class | A single select lookup that Identifies the Transaction Type and Transaction Class ID. When creating a new transaction class, this is blank and after the initial save, it displays as [Transaction Type] - [Transaction Class ID]. The lookup contains the list of all Transaction Classes for the current functional area. Selecting a new value, loads the page with the details for the selected Transaction Class. This field is always enabled. |
Properties Tab
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. |
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. |
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. |
Saved Layouts | Please note that existing saved grid layouts will display the Filter Row as hidden by default. 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. |
Fields | Description |
---|---|
Properties | Identifies the Property that is being set up. |
Value | A text box or lookup to set the value of the property. Property values are always editable and can be changed at any time, unless otherwise specified. |
Group: All | |
Transaction Type | Identifies the type of transaction that the Transaction Class is being configured for. This is a single-select lookup that is required. It defaults as blank but is required before the initial save. It is not editable the after initial Save. This lookup contains values for: Credit Memo, Invoice, and Purchase Order. Database Fields: ERPx_APTransactionType.TransactionName |
Class ID | |
Class Description | This is a text box that is required and must be <=200 characters. If missing, the message "Class Description is required." will be displayed on Save. This field must be unique, else the message "Duplicate Transaction Class Descriptions are not allowed to the same transaction type." will be displayed on Save. It defaults as blank and is always editable. Database Field: ERPx_APTransactionClass.TransactionClassDescription |
Doc Prefix | Database Field: ERPx_APTransactionClass.DocPrefix |
Next Doc Number | Database Field: ERPx_APTransactionClass.NextDocNumber |
Inactive | |
PO Billing Address ID | Identifies the billing Address ID of the Purchase Order. This is a single-select lookup that is not required. This is only visible after the initial Save and editable for Transaction Types of "Purchase Order", it does not apply to Transaction Types of "Invoice" or "Credit Memo". Note: For the 'Default' Purchase Order Class, this is set to "Physical". This lookup contains a blank value, the current assigned value, and a list of all the active Company Addresses configured in Company → Setup → Addresses Database Field: ERPx_MFAddress.AddressID, ERPx_APTransactionClass.BillingAddressSK |
Default PO Site | Identifies the Site displayed as [Site Name] ([Site ID]). This is a single-select lookup that is not required. It defaults as blank and duplicate values are allowed across transaction class types. This is only visible after the initial Save and editable for Transaction Types of "Purchase Order", it does not apply to Transaction Types of "Invoice" or "Credit Memo". If selected, the Site will default as the Site on all new Purchase Orders for this Class. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. This lookup contains a list of all active Sites. Database Fields: ERPx_MFSite.SiteName, ERPx_APTransactionClass.DefaultSiteSK |
Autofill PO Receipt Quantities | A Yes/No lookup to identify whether or not the Ordered/Remaining quantities will default on the line items of manually entered Inventory Receipts that are linked to a PO. This in only visible, after the initial save on Purchase Order Transaction Classes, it does not apply to AP Invoice/Credit Memo Transaction Classes. This is always editable. Database Field: ERPx_APTransactionClass.AutoFillReceiptQuantities |
Default PO Type | Identifies whether or not more than one AP Invoice and/or Inventory Receipt can be recorded against the Purchase Order. The options include:
Database Field: ERPx_APTransactionClass.DefaultPOTypeEN |
First Status POs can be Received or Invoiced | Identifies the first status that Purchase Orders are available to other related transactions (AP Invoices/Credit Memos and Inventory Receipts). This is a single-select lookup that is required. If missing, the message "First Status POs can be Received or Invoiced is required" will be displayed on Save. It defaults as blank, is only visible after the initial Save and editable for Transaction Types of "Purchase Order", it does not apply to Transaction Types of "Invoice" or "Credit Memo". Note: For the 'Default' Purchase Order Class, this is set to "New". This lookup contains all the StatusName values in the ERPx_APPOStatus table WHERE POStatusSK is either 1 (New), or 2 (Released). Database Field: ERPx_APTransactionClass.FirstStatusSKPOsCanBeReceivedorInvoiced |