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: 2022.11.28 and newer

Page Header

Header Toolbar

Toolbar Icons	Description
Delete	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. _{WARNING: Records cannot be recovered once they are deleted!}
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

Fields	Description
Toolbar Icons	Description
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.
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.
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. 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
Class ID	The unique identifier of the Transaction Class. This is a text box that is required and must be <=50 characters. If missing, the message "Class ID is required." will be displayed on Save. This field must be unique by Company and Transaction Type. Else, the message "Duplicate Transaction Class ID's are not allowed to the same transaction type." will be displayed on Save. It defaults as blank and is always editable. Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each. Database Field: ERPx_APTransactionClass.TransactionClassID
Class Description	Identifies the (Long) Description for the Transaction Class. 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	Identifies the prefix that will combine with the 'Next Document Number' field to create the Transaction ID for transactions belonging to the transaction class. This is a text box that is required and must be <= 10 characters. If missing, the message "Doc Prefix is required." will be displayed on Save. This field must be unique by Company and Transaction Type. Else, the message "Duplicate Doc Prefixes 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.DocPrefix
Next Doc Number	Identifies the numerical suffix that will be appended to the 'Document Prefix' field to create unique Transaction IDs for transactions belonging to the Transaction Class. This is a counter that increases by 1 every time a new transaction is created for the Transaction Class. This is a numeric text box that is required. It defaults to "10000", is always editable and must be >0. If missing or not numeric or not >0, then the message "Next Doc Number is required and must be a number greater than 0." will be displayed on Save. Database Field: ERPx_APTransactionClass.NextDocNumber
Inactive	Identifies if the record is "Inactive". If inactive (set to "Yes"), it will not be included in look-ups for transactions or other master files. If set to "No" or blank, the record is active and can be freely used. This is a Yes/No lookup that is required. It defaults as No and is always editable. This property is visible after the initial Save. Database Field: ERPx_APTransactionClass.IsInactive
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: Single Invoice and Receipt: If this option is selected, the Purchase Order can only be assigned to a single AP Invoice for each unique Vendor (Primary and Line) and a single Inventory Receipt transaction. Once the PO has been assigned to a Receipt and/or AP Invoice for each unique Vendor (Primary and Line), users will not be able to assign it to an additional transaction. Once it has been assigned to both an AP Invoice (for each unique Vendor if line Vendors are selected) and Inventory Receipt (for PO's that contain inventory items) the Purchase Order's Status will be auto set to "Closed". An 'Open' Purchase Order can always be assigned to multiple AP Credit Memos and negative Receipts. Multiple Invoices and Receipts: If this option is selected, the Purchase Order can be assigned to multiple AP Invoices and multiple Inventory Receipt transactions. Purchase Orders set to this Type must be manually Closed. This is a single-select lookup that is 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 missing, the message "Default PO Type is required" will be displayed on Save. It defaults as blank on New and is always editable. Note: For the 'Default' Purchase Order Class, this is set to "Single Invoice & Receipt". 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

NorthScope

Purchase Order Transaction Class Record View

Page Header

Header Toolbar

Properties Tab

Related Topics

Page Definitions

Technical Details