Price Adjustment Transaction Class Record View 3.0
Sales Transaction Classes are used to categorize sales transactions within specific transaction types and assign specific default values and business rules for each. The purpose of this page is to set the properties for the Price Adjustment transaction class.
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 to select a Transaction Class. This defaults to blank for a new Transaction Class and is always required after initial Save. This field is editable after initial Save. When users update the value selected in this field, the Transaction Class record view page will refresh to display the Properties for the selected Transaction Class. This lookup contains all Transaction Classes and is displayed as '[Transaction Class] - '[Transaction Type]'. Database Field: ERPx_SOOrderTypeDocument.DocumentID - ERPx_SOOrderType.OrderTypeName where ERPx_SOOrderTypeDocument.OrderTypeSK = ERPx_SOOrderType.OrderTypeSK |
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: Configuration | |
Transaction Type | A single-select lookup to select a Transaction Type. This defaults to blank and is always required. If not assigned, the message "Transaction Type is required." will be displayed on Save. This field is not editable after the initial Save. The value can be set to:
This lookup contains all the values in ERPx_SOOrderType where IsEnabled = 1 Database Field: ERPx_SOOrderTypeDocument.OrderTypeSK |
Transaction Class | A text box to specify the name of the Transaction Class. This defaults to blank for new records and is always required. If not assigned, the message "Transaction Class is required." will be displayed on Save. This value must be unique by Transaction Type. If not, the message "Duplicate Transaction Classes are not allowed." will be displayed on Save. This field is not editable after the initial Save and must be <= 15 characters. Database Field: ERPx_SOOrderTypeDocument.DocumentID |
Document Prefix | A text box to specify the Document Prefix to be used in the Transaction ID. This defaults to blank for new records and is required else the message "A Document Prefix is required for Price Adjustments" will be displayed on Save. This field must be <= 10 characters. This field must be unique by Transaction Type and Company. If not, the message "Duplicate Document Prefixes are not allowed for the same Transaction Types. This Document Prefix has already been assigned to the [Transaction Class Name] Transaction Class." will display on Save. This field is always editable. The 'Document Prefix' is used in conjunction with the 'Next Document Number' to determine the system assigned Transaction ID's. Transaction ID's are created by stringing together the [Document Prefix] + [Next Ticket Number] from the applicable Transaction Class. This value is only used if the corresponding 'Order' Transaction Class has the 'Get Next Price Adjustment Number From' property set to "Price Adjustment Transaction Class". Otherwise this is inherited from the source Order or Invoice. Database Field: ERPx_SOOrderTypeDocument.DocumentPrefix |
Next Document Number | A text box to specify the Next Document Number to be used in the Transaction ID. This defaults to blank for new records and is always required. If missing, the message “Next Document Number is required.” will be displayed on Save. The value must be a numeric whole number. If not, the message "Next Document Number must be a number and cannot contain letters or symbols." will be displayed on Save. This field is always editable. The 'Document Prefix' is used in conjunction with the 'Next Document Number' to determine the system assigned Transaction ID's. Transaction ID's are created by stringing together the [Document Prefix] + [Next Document Number] from the applicable Transaction Class. The 'Next Document Number' is auto-incremented each time a new transaction for the selected transaction class is created. This value is only used if the corresponding 'Order' Transaction Class has the 'Get Next Price Adjustment Number From' property set to "Price Adjustment Transaction Class". Otherwise this is inherited from the source Order or Invoice. Database Field: ERPx_SOOrderTypeDocument.NextDocNumber |
Logo Location | A text box to specify the network path for the image file used on the transaction reports for Price Adjustment transactions assigned to the Transaction Class. This is only used for reports and does not drive any other functionality. This defaults to blank for new records and is not required. This field is always editable and must be <= 1000 characters. Database Field: ERPx_SOOrderTypeDocument.DocumentLogoLocation |
Remit To Address | A single select lookup to select a Remit To Address to be used on sales reports. This is required and defaults to the first Remit To Address from the ERPx_MFAddress table for the corresponding company. This address will only be used on reports for transactions associated with this class if the Customer associated with the transaction does not have a Remit To Address configured, otherwise the Customer's Remit To Address will default on the associated report(s). This field is always editable. The lookup contains a list of all the active Remit To type addresses in the Company Addresses master file. Database Field: ERPx_MFAddress.AddressID, ERPx_SOOrderTypeDocument.RemitToAddressSK |
Inactive | A Yes/No lookup to select whether the Transaction Class is displayed in the Transaction Class lookup when a new Price Adjustment transaction is created. This defaults to "Yes" for new records and is always required. This field is always editable. Note: If the price adjustment class is selected as the 'Transaction Class for Price Adjustments' on the order class record and the user tries to inactivate the corresponding price adjustment class the following message will be displayed on save "This class is currently assigned to Order Class [Class Name] and must be removed before it can be deactivated." Database Field: ERPx_SOOrderTypeDocument.IsInactive |
Group: Data Entry | |
Allow Attribute Edit On Approved and Posted Transactions | A Yes/No lookup to select when Price Adjustment transaction attributes can be edited. This defaults to "No" for new records and is always required. This field is always editable.
Database Field: ERPx_SOOrderTypeDocument.IsAttributeEditAllowedAfterApproval |
Group: Integration | |
Transaction Integration to Host System | A single-select lookup to select if and how sales transactions are sent to a separate host system. This defaults to "Transaction with Journal Details" for new records and is always required. This field is always editable. The options include:
This property is only applicable for NorthScope systems that send Sales Transactions to a host system (e.g. Dynamics GP). For NorthScope systems that do not integrate transactions to a host system, this property is not used or applicable. This lookup contains the values in the IntegrationMethod Enumeration Class where Enumeration Value = 2,3. Database Field: ERPx_SOOrderTypeDocument.IntegrationMethodEN |
First status invoices are sent to the host system | A non-editable text box to show the status of the invoice sent to the host system. This defaults to "Ready to Post" for new records and is always required. Currently, this field can only be edited from the database. This property is only applicable for NorthScope systems that send Sales Transactions to a host system (e.g. Dynamics GP). For NorthScope systems that do not integrate transactions to a host system, this property is not used or applicable. Database Field: ERPx_SOOrderTypeDocument.SendInvoicesToHostSystemEN |