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: 2022.08.02 and newer
Page Header
Header Toolbar
| Toolbar Icons | Description |
|---|---|
| Grid Layout | Opens the Saved Grid Layout menu that allows the user to select another saved layout, create a new layout, save changes to a layout, or assign a saved layout as the default for the page. Once changes are made to a grid, such as columns are added or removed, the user can click the Saved Grid Layout icon and save the changes to the grid layout and name the new layout. The new layout can also be set as the default, instead of the System View. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific).
|
| Help | Opens the online WIKI help page for the current page.
|
| New | Allows the user to create a new master file record or transaction by opening a blank record view page. This icon is always enabled. |
| Save | Saves the changes made to the record.
|
| 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 |
The bolded view is the default view, which will determine the view will automatically display in when opened. Properties Tab
| Toolbar Icons | Description |
|---|---|
| Excel | Export the contents of the list view 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 only the filtered contents will be exported. |
| 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 |
| 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 |
| Allow Posting of Transactions with missing Costs | This property is currently under development. |
| 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 |