Page Header

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 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 Invoice Number From' property set to "Invoice Transaction Class". Otherwise this is inherited from the source Order.

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. 

This value is only used if the corresponding 'Order' Transaction Class has the 'Get Next Invoice Number From' property set to "Invoice Transaction Class". Otherwise this is inherited from the source Order.

Linked Database Field: ERPx_SOOrderTypeDocument.NextDocNumber

A single-select lookup to select the default Payment Term for the 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

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 contains the 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 Invoice 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 the Transaction Class is displayed in the Transaction Class lookup when a new sales 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 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