Linked Database Field: ERPx_SOOrderTypeDocument.NextInvoiceSourceNumberENOrderTypeSK

A single-select lookup text box to specify the name of the Invoice Transaction Class to use when an invoice number is created from the sales order. This property is only used when the ‘Get Next Invoice Number From’ is set to ‘Invoice Transaction Class’. This defaults . 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.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 where ERPx_SOOrderTypeDocument.OrderTypeDocumentSK = ERPx_SOOrderTypeDocument.InvoiceOrderTypeDocumentSK

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 is always editable from the record view and must be <= 10 characters.

• Invoice Date Matches Transaction Date: When this property value is selected on the transaction class, the invoice date on the Sales Order will default to the Order Date of the transaction.
• Invoice Date Matches Actual Ship Date: When this property is selected on the transaction class, the invoice date on the Sales Order will default to the Shipped Date on the Shipments tab on the transaction.
• Manually Assigned: When this property value is selected on the transaction class, the invoice date on the Sales Order must be manually entered by the user. 

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

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: When this property value is selected on the transaction class, 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: When this property value is selected on the 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: When this property value is selected on the transaction class, 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 only used when the ‘Get Next Price Adjustment Number From’ 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

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 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 from the record view.

Linked Database Field: ERPx_SOOrderTypeDocument.RowsToCreateOnNew

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

A single-select lookup to specify how the next Quote transaction number will generate. This defaults to blank 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.

Linked Database Field: ERPx_SOOrderTypeDocument.NextQuoteSourceNumberEN

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.

This lookup contains a list of all Transaction Classes where the Transaction Type is Quote.

Linked Database Field: ERPx_SOOrderTypeDocument.DocumentID where ERPx_SOOrderTypeDocument.OrderTypeDocumentSK = ERPx_SOOrderTypeDocument.QuoteOrderTypeDocumentSK

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: When this property value is selected on the transaction class, the Return transaction number will default to the “Document Prefix” and “Next Document Number” saved on the Return transaction class. 
  
• Source Invoice: When this property value is selected on the transaction class, the Return transaction number will default to the source Invoice number. A prefix of ‘R-‘ is added to the Invoice number.

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

Linked Database Field: ERPx_SOOrderTypeDocument.

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 only used when the ‘Default Next Return Number From’ is set to ‘Return Transaction Class’. This defaults to blank for new records and is never required. This field is always editable.

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