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  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 view and must be <= 10 characterscharacters. 

Linked Database Field: ERPx_SOOrderTypeDocument.DocumentPrefix

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

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

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

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

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

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:

• 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 field is always editable from the record view.

Linked Database Field: ERPx_SOOrderTypeDocument.IntegrationMethodEN

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:

• 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