Sales Transaction Class List 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. They are assigned when the New icon is selected for sales transactions. For example, if there was a need to differentiate between Fresh and Frozen transactions, you could create Transaction Classes for each. The purpose of this page is to add, edit, remove, and activate/inactive these records.
Software Version: 2025.04.21 and newer
Page Header
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. |
Delete | Note: If a record is not selected prior to clicking the button, the message “Please select a row to delete.” will be displayed. WARNING: Records cannot be recovered once they are deleted! Deletes the selected record(s). When clicked, users will be prompted with: "Are you sure you want to delete the selected records?". Click "OK" to confirm, or "Cancel" to return without deleting. |
Edit | Opens the selected record for editing. If a record is not selected, the message "Please select a row to edit." will be displayed. |
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 |
|
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. |
New | Opens a new blank record for data entry. |
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 |
Checkbox | Used to select one or more records for delete or mass update. |
Document Prefix | Identifies the value in the 'Document Prefix' property on the record view. This defaults to blank for new records and is not required. 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. The 'Next Document Number' is auto-incremented each time a new transaction for the selected transaction class is created. This field is always editable from the record view and must be <= 10 characters. Database Field: ERPx_SOOrderTypeDocument.DocumentPrefix |
Inactive | A Yes/No field used to identify if the record is Inactive. If set to 'Yes' then the record is "Inactive" and will not be listed as a value when the 'New' icon is clicked from Sales Transactions List View. If set to 'No' then the record is "Active" and can be freely used. Database Field: ERPx_SOOrderTypeDocument.IsInactive |
Logo File | Used to display the network path for the image file used on the transaction reports for records assigned to the Transaction Class. This defaults to blank for new records and is not required. This is only used for reports and does not drive any other functionality. This field is always editable from the record view and must be <= 1000 characters. Database Field: ERPx_SOOrderTypeDocument.DocumentLogoLocation |
Next Document Number | Identifies the value in the 'Next Document Number' property on the record view. This defaults to blank for new records and is 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. 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 field is always editable from the record view. Database Field: ERPx_SOOrderTypeDocument.NextDocNumber |
Payment Terms | The 'Payment Terms' property on the Transaction Class record. This defaults to blank on new records and is not required. This field is always editable from the record view. The 'Payment Terms' is used to assign a default Payment Term to a sales order Transaction Class. If assigned, all new sales transactions, for the Class, will get the Payment Term from here, and not from the customer. This lookup contains a blank value, the current assigned value, and a list of all the 'Active' Payment Terms. Database Field: ERPx_SOOrderTypeDocument.DefaultPaymentTermSK |
Transaction Class | A hyperlink that shows the value of the 'Transaction Class' property on the Transaction Class record. Clicking on the link opens the record view for the selected Transaction Class. This defaults to blank for new records and is 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 |
Transaction Integration | Identifies the value in the 'Transaction Integration to Host System' property on the record view. This defaults to "Transaction with Journal Details" for new records. This functionality is only applicable where NorthScope sales transactions are sent to a separate host system. For systems that send sales transactions, this preference describes how they are sent. The options include:
This field is always editable from the record view. Database Field: ERPx_SOOrderTypeDocument.IntegrationMethodEN |
Transaction Type | Identifies the value in the 'Transaction Type' property on the record view. This defaults to blank and is 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 |