Linked Database Field: ERPx_SOOrderTypeDocument.DocumentID - ERPx_SOOrderType.OrderTypeName where ERPx_SOOrderTypeDocument.OrderTypeSK = ERPx_SOOrderType.OrderTypeSK 

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:

• Quote: Used to provide an estimate for a potential order
• Order: Used to track the order and shipment of items
• Invoice: Used to invoice a customer
• Return: Used to allow customers to return items
• Price Adjustment: Used to provide customers with price adjustments for items

This lookup contains all the values in ERPx_SOOrderType where IsEnabled = 1

Linked Database Field: ERPx_SOOrderTypeDocument.OrderTypeSK

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

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 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.

Linked Database Field: ERPx_SOOrderTypeDocument.DocumentPrefix

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.OrderTypeSK

NextDocNumber

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

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.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 lookup contains a blank value, the current assigned value, and a list of all the 'Active' Payment Terms.

Linked Database Field:   ERPx_SOOrderTypeDocument.DocumentPrefix

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

DefaultPaymentTermSK

A Yes/No lookup to select whether the Carrier 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 set to "Yes", when new Orders are created, the message "Carrier is required for orders in the transaction class and there is no transaction class or customer address default set." will display on the Select Ship-To Record View if the 'Carrier' has not been set. If set to "No", then 'Carrier' is not required. 

Linked Database Field: ERPx_SOOrderTypeDocument.RowsToCreateOnNewIsCarrierRequired

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.

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:

• Transaction with Journal Details: When transactions for this Transaction Class are posted, an outbound record is created so that it can be imported by the host system. This can only happen if the Outbound Transaction Type of "SO Transaction Class" is configured in the Integration Configuration master file.
• No Integration: When transactions for this Transaction Class are posted, no outbound record is created, even if the Outbound Transaction Type of "SO Transaction Class" is configured in the Integration Configuration master file to send transactions.

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

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

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 are created, they will be prompted with the message "A Ship by Date is required , please enter a valid date." before they can re-query or move past the 'Select Items' page for orders in the transaction class." will display on the Select Ship-To Record View if the 'Ship By' date field has not been set. If this is set to "No", the then 'Ship By' date field is not required.   

Linked Database Field: ERPx_SOOrderTypeDocument.IsShipByDateRequired

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 are created, they will be prompted with the message "A Deliver On date Date is required , please enter a valid date." before they can re-query or move past the 'Select Items' page for orders in the transaction class." will display on the Select Ship-To Record View if the 'Deliver On' date field has not been set. If this is set to "No", the then 'Deliver On' date field is not required.  

Linked Database Field: ERPx_SOOrderTypeDocument.IsDeliverOnDateRequired

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. 

• A value of "No" means that sales order attributes can only be edited when the sales transaction is in New status.
• A value of "Yes" means that sales order attributes can always be edited, regardless of status.

Linked Database Field: ERPx_SOOrderTypeDocument.IsAttributeEditAllowedAfterApproval

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

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 are created, 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 orders in the transaction class and there is no transaction class or customer address default set." will display on the Select Ship-To Record View if the 'Freight Terms' have not been set. If this is set to "No", then 'Freight Terms' are not required. 

Linked Database Field: ERPx_SOOrderTypeDocument.AreFreightTermsRequired

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.

• A value of “Yes” allows users to delete inventory tracked Sales Order Items that have been allocated.
• A value of “No” displays an error message preventing users from deleting inventory tracked Sales Order Items that have been allocated.
• A value of “Warn” prompts users with a friendly message when attempting to delete inventory tracked Sales Order Items that have been allocated.

Linked Database Field: ERPx_SOOrderTypeDocument.AllowDeleteItemsWithAllocation

A Yes/No lookup to select if the 'Salesperson - Inside Sales' property is required on the Sales Order Record View when Approving or Posting the transaction. This defaults to "No" for new records and is always required. This field is always editable.

Linked Database Field: ERPx_SOOrderTypeDocument.RequireInsideSalesperson

A Yes/No lookup to select if the 'Salesperson - Outside Sales' property is required on the Sales Order Record View when Approving or Posting the transaction. This defaults to "No" for new records and is always required. This field is always editable.

Linked Database Field: ERPx_SOOrderTypeDocument.RequireOutsideSalesperson

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.

• Source Order: The invoice number on the Sales Order will be auto-assigned to match the Sales Order number.  The Sales Order transaction number is assigned based on the “Document Prefix” and “Next Document Number” saved on the Order transaction class.
  
• Invoice Transaction Class: The invoice number will be auto assigned from the the “Document Prefix” and “Next Document Number” of the Invoice transaction  class assigned in the 'Transaction Class for Invoices' property.
  

This lookup containsthe values in the SOSourceNumberEN Enumeration Class where Enumeration Value = 1,2. 

Linked Database Field: ERPx_SOOrderTypeDocument.NextInvoiceSourceNumberEN

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

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.

• Invoice Date Matches Transaction Date: The invoice date on the Sales Order will default from the 'Order Date' of the transaction.
• Invoice Date Matches Actual Ship Date: The invoice date on the Sales Order will default from the 'Shipped Date' on the Shipments tab on the transaction.
• Manually Assigned: The invoice date on the Sales Order must be manually entered by the user. 

This lookup containsthe values in the SOInvoiceDateMode Enumeration Class.

Linked Database Field: ERPx_SOOrderTypeDocument.InvoiceDateModeEN

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

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.

• Source Order: The Price Adjustment transaction number will default to the Sales Order transaction number.  The Sales Order transaction number is assigned based on the “Document Prefix” and “Next Document Number” entered on the Order transaction class. A prefix ‘PA-‘ is added to the transaction number.
  
• Price Adjustment Transaction Class: The Price Adjustment transaction number will default to the “Document Prefix” and “Next Document Number” saved on the Price Adjustment transaction class. 
  
• Source Invoice: The Price Adjustment transaction number will default to the source Invoice transaction number. A prefix of ‘PA-‘ is added to the Invoice number.

This lookup contains the values in the SOSourceNumberEN Enumeration Class where Enumeration Value = 1,3,5. 

Linked Database Field: ERPx_SOOrderTypeDocument.NextPriceAdjSourceNumberEN

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

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.

• A value of “Yes” will set the Inactive property value to be "No" on the Quote transaction class, given the Order transaction Class's Inactive property value is also "No".
• A value of “No” will set the Inactive property value to be "Yes" on the Quote transaction class.

Linked Database Field: ERPx_SOOrderTypeDocument.AllowQuote

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.

• Order Transaction Class: The Quote transaction number will default to the Sales Order transaction number.  The Sales Order transaction number is assigned based on the “Document Prefix” and “Next Document Number”.
  
• Quote Transaction Class: The transaction class, the Quote transaction number will default to the “Document Prefix” and “Next Document Number” saved on the Quote transaction class. 
  

This lookup contains the values in the SOSourceNumberEN Enumeration Class where Enumeration Value = 6,7. 

Linked Database Field: ERPx_SOOrderTypeDocument.NextQuoteSourceNumberEN

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

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.QuoteConversionDefaultOrderStatus

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.

• Return Transaction Class: The Return transaction number will default to the “Document Prefix” and “Next Document Number” saved on the Return transaction class. 
  
• Source Invoice: The Return transaction number will default to the source Invoice number. A prefix of ‘R-‘ is added to the Invoice number.

This lookup containsthe values in the SOSourceNumberEN Enumeration Class where Enumeration Value = 4,5.

Linked Database Field: ERPx_SOOrderTypeDocument.NextReturnSourceNumberEN

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