Sales Transaction Class List View
- Janice Dannenberg (Unlicensed)
- Tom Williams
- Emma Greenwood
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: 2019.09.03 and newer
Page Header
| Toolbar Icons | Description |
|---|---|
| Delete | 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. WARNING: Records cannot be recovered once they are deleted! |
| Edit | Opens the selected record for editing. If a record is not selected, the page will not open. |
| Excel |  Clicking the Excel toolbar icon exports the current contents of the grid to an Excel file that is automatically downloaded. The contents that export are only those currently visible. If the grid is filtered, only the filtered contents will be exported. |
| Favorites |   Clicking on the star icon when it is an outline, adds the page to the 'My Shortcuts' tab and fills in the star. Clicking on the star icon when it is filled in (solid color), removes the page from the 'My Shortcuts' tab and returns the icon to an outline.
|
| 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 | Opens a new blank record for data entry. |
| 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. Linked 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. Linked 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. Linked 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. Linked 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. Linked 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. Linked 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. Linked 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 Linked Database Field: ERPx_SOOrderTypeDocument.OrderTypeSK |
Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.