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 Order transaction class.
Software Version: 2020.04.03.20 and newer
Table of Contents | ||
---|---|---|
|
...
Toolbar Icons | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Excel |
| ||||||||
Fields | Description | ||||||||
Properties |
| ||||||||
Value |
| ||||||||
Group: Default | |||||||||
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 Linked 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. Linked 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 never required. This field must be <= 10 characters. 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. Linked 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. Linked Database Field: ERPx_SOOrderTypeDocument.NextDocNumber | ||||||||
Rows to Create on New | A text box to specify the how many blank rows will be added to the Items grid when the New icon is clicked. This defaults to 5 for new records, is always required, and must be between 1 and 25. If set to any value other than 1 - 25, the message "Rows to Create on New must be between 1 and 25." will be displayed on Save. This field is always editable. Linked Database Field: ERPx_SOOrderTypeDocument.RowsToCreateOnNew | ||||||||
Default Payment Terms | A single-select lookup to select the default Payment Term that will be assigned to new Orders created with this Transaction Class. When assigned, the Payment Term for a new sales transaction will be defaulted from the Transaction Class, not the Customer. This defaults to blank on new records and is not required. This field is always editable. 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 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 containsthe values in the IntegrationMethod Enumeration Class where Enumeration Value = 2,3. Linked Database Field: ERPx_SOOrderTypeDocument.IntegrationMethodEN | ||||||||
Logo Location | A text box to specify the network path for the image file used on the transaction reports for Order 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. Linked Database Field: ERPx_SOOrderTypeDocument.DocumentLogoLocation | ||||||||
Single Date Management | A non-editable text box that displays whether or not all dates on a sales transaction default from the Order Date. This defaults to "No" for new records and is always required. This field is always editable. When this property is set to “Yes”, users can only enter and edit the 'Order Date' field on the 'Select Ship-To' page and the Sales Order Record View, all other date fields are disabled and auto-populated from the Order Date. The following date fields will default from the sales transaction Order Date:
Linked Database Field: ERPx_SOOrderTypeDocument.SingleDateManagement | ||||||||
Require a Ship By Date | A Yes/No lookup to select whether a Ship By Date is required for saving a sales transaction. This defaults to "Yes" for new records and is always required. This field is always editable. If this is set to "Yes", when users create new Orders, they will be prompted with the message "A Ship Date is required, please enter a valid date." before they can re-query or move past the 'Select Items' page if the 'Ship By' date has not been set. If this is set to "No", the 'Ship By' date is not required. Linked Database Field: ERPx_SOOrderTypeDocument.IsShipByDateRequired | ||||||||
Require a Deliver On Date | A Yes/No lookup to select whether a Deliver On Date is required for saving a sales transaction. This defaults to "Yes" for new records and is always required. This field is always editable. If this is set to "Yes", when users create new Orders, they will be prompted with the message "A Deliver On date is required, please enter a valid date." before they can re-query or move past the 'Select Items' page if the 'Deliver On' date has not been set. If this is set to "No", the 'Deliver On' date is not required. Linked Database Field: ERPx_SOOrderTypeDocument.IsDeliverOnDateRequired | ||||||||
Allow Attribute Edit After Approval | A Yes/No lookup to select when sales order attributes can be edited. This defaults to "No" for new records and is always required. This field is always editable.
Linked Database Field: ERPx_SOOrderTypeDocument.IsAttributeEditAllowedAfterApproval | ||||||||
Inactive | A Yes/No lookup to select whether the Transaction Class is displayed in the Transaction Class lookup when a new sales Order transaction is created. This defaults to "Yes" for new records and is always required. This field is always editable. Linked Database Field: ERPx_SOOrderTypeDocument.IsInactive | ||||||||
Require Freight Terms | A Yes/No lookup to select whether the Freight Terms field is required for saving a sales transaction. This defaults to "No" for new records and is always required. This field is always editable. If this is set to "Yes", when users create new Orders, they will be prompted with the message "Freight Terms are required for this Transaction Class." before they can re-query or move past the 'Select Items' page if the 'Freight Terms' have not been set. If this is set to "No", 'Freight Terms' are not required. Linked Database Field: ERPx_SOOrderTypeDocument.AreFreightTermsRequired | ||||||||
Allow delete of inventory tracked items with allocations? | A Yes/No/Warn lookup to select how to manage deletion of inventory tracked items that have been allocated. This defaults to "Warn" for new records and is always required. This field is always editable.
Linked Database Field: ERPx_SOOrderTypeDocument.AllowDeleteItemsWithAllocation | ||||||||
Group: Invoices | |||||||||
Get Next Invoice Number From | A single-select lookup to specify how the next Invoice transaction number will generate. This defaults to blank for new records and is never required. This field is always editable.
This lookup containsthe values in the SOSourceNumberEN Enumeration Class where Enumeration Value = 1,2. Linked Database Field: ERPx_SOOrderTypeDocument.NextInvoiceSourceNumberEN | ||||||||
Transaction Class for Invoices | A single-select lookup to specify the Invoice Transaction Class to use when an invoice is created from a Sales Order. This property is only used when the ‘Get Next Invoice Number From’ is set to "Invoice Transaction Class". This defaults to blank for new records and is always required. This field is always editable. This lookup contains a list of all Transaction Classes where the Transaction Type is Invoice. Linked Database Field: ERPx_SOOrderTypeDocument.DocumentID where ERPx_SOOrderTypeDocument.OrderTypeDocumentSK = ERPx_SOOrderTypeDocument.InvoiceOrderTypeDocumentSK | ||||||||
How Invoice Dates Are Assigned | A single-select lookup to specify how invoice dates are assigned. This defaults to blank for new records and is always required. This field is always editable.
This lookup containsthe values in the SOInvoiceDateMode Enumeration Class. Linked Database Field: ERPx_SOOrderTypeDocument.InvoiceDateModeEN | ||||||||
Group: Order | |||||||||
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. Linked Database Field: ERPx_SOOrderTypeDocument.SendInvoicesToHostSystemEN | ||||||||
Group: Price Adjustments | |||||||||
Get Next Price Adjustment Number From | A single-select lookup to specify how the next Price Adjustment transaction number will generate. This defaults to blank for new records and is never required. This field is always editable.
This lookup contains the values in the SOSourceNumberEN Enumeration Class where Enumeration Value = 1,3,5. Linked Database Field: ERPx_SOOrderTypeDocument.NextPriceAdjSourceNumberEN | ||||||||
Transaction Class for Price Adjustments | A single-select lookup to specify the Price Adjustment Transaction Class to use when a Price Adjustment transaction number is created from the sales order. This property is used to assign the Transaction Class to the Price Adjustment transaction. This is also used to assign the transaction number to the Price Adjustment if the ‘Get Next Price Adjustment Number From’ property is set to "Price Adjustment Transaction Class". This defaults to blank for new records and is never required. This field is always editable. This lookup contains a list of all Transaction Classes where the Transaction Type is Price Adjustment. Linked Database Field: ERPx_SOOrderTypeDocument.DocumentID where ERPx_SOOrderTypeDocument.OrderTypeDocumentSK = ERPx_SOOrderTypeDocument.PriceAdjOrderTypeDocumentSK | ||||||||
Group: Quotes | |||||||||
Allow Quotes | A Yes/No lookup to select whether the or not Quotes can be created for this Order Class. This defaults to "No" for new records and is always required. This field is always editable.
Linked Database Field: ERPx_SOOrderTypeDocument.AllowQuote | ||||||||
Get Next Quote Number From | A single-select lookup to specify how the next Quote transaction number will generate. This defaults to "Order Transaction Class" for new records and is always required. This field is always editable.
This lookup contains the values in the SOSourceNumberEN Enumeration Class where Enumeration Value = 6,7. Linked Database Field: ERPx_SOOrderTypeDocument.NextQuoteSourceNumberEN | ||||||||
Transaction Class for Quotes | A non-editable text box specify the Quote Transaction Class to use when a Quote transaction is created from the sales order. This property is used to assign the Transaction Class to the Quote transaction. This is also used to assign the transaction number to the Quote if the ‘Get Next Quote Number From’ property is set to "Quote Transaction Class". This defaults to the associated Quote Transaction Class for new records and is always required. Linked Database Field: ERPx_SOOrderTypeDocument.DocumentID where ERPx_SOOrderTypeDocument.OrderTypeDocumentSK = ERPx_SOOrderTypeDocument.QuoteOrderTypeDocumentSK | ||||||||
Default Order Status for Converted Quote | A single-select lookup to specify the sales order Status when the Quote is converted to an Order. This defaults to "New" and is always required. This field is always editable. The lookup contains the values of "New" and "Released". However, the "Released" status is only displayed in the lookup when the “Released” status is enabled on the ‘Sales: Configuration – Status Setup’ page. Linked Database Field: ERPx_SOOrderTypeDocument.DocumentID where ERPx_SOOrderTypeDocument.OrderTypeDocumentSK = ERPx_SOOrderTypeDocument.QuoteOrderTypeDocumentSKQuoteConversionDefaultOrderStatus | ||||||||
Group: Returns | |||||||||
Get Next Return Number From | A single-select lookup to specify how the next Return transaction number will generate. This defaults to blank for new records and is never required. This field is always editable.
This lookup containsthe values in the SOSourceNumberEN Enumeration Class where Enumeration Value = 4,5. Linked Database Field: ERPx_SOOrderTypeDocument.NextReturnSourceNumberEN | ||||||||
Transaction Class for Returns | A single-select lookup to specify the Return Transaction Class to use when a Return transaction number is created from the sales order. This property is used to assign the Transaction Class to the Return transaction. This is also used to assign the transaction number to the Return if the ‘Get Next Return Number From’ property is set to "Return Transaction Class". This defaults to blank for new records and is never required. This field is always editable. This lookup contains a list of all Transaction Classes where the Transaction Type is Return. Linked Database Field: ERPx_SOOrderTypeDocument.DocumentID where ERPx_SOOrderTypeDocument.OrderTypeDocumentSK = ERPx_SOOrderTypeDocument.ReturnOrderTypeDocumentSK |
Related Topics
Expand | ||
---|---|---|
| ||
Page Definitions |
...