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 Quote transaction class.
...
| Toolbar Icons | Description |
|---|---|
| Excel | Clicking the Excel toolbar icon exports the current contents of the page to an Excel file that is automatically downloaded. |
| Fields | Description |
| Properties | Identifies the Property that is being set up. |
| Value | A text box or lookup to set the value of the property. Property values are always editable and can be changed at any time, unless otherwise specified. |
| Default | |
| Transaction Type | A non-editable text box that displays "Quote". A Quote Transaction Class is automatically generated when a Order Transaction Class is created. This field is always required and is never editable. Linked Database Field: ERPx_SOOrderTypeDocument.OrderTypeSK |
| Transaction Class | A non-editable text box that displays the Transaction Class of the Order. This field is always required and is never editable. 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 always required. This field must be <= 10 characters. 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 1000 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 the value in the 'Rows to Create on New' field on the associated Order transaction class for new records. This field 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 must be a whole number. If not, the message "Rows to Create on New must be a whole number and cannot contain letters or symbols." will be displayed on Save. This field is always editable from the record view. Linked Database Field: ERPx_SOOrderTypeDocument.RowsToCreateOnNew |
| Default Payment Terms | A non-editable text box that displays the default Payment Term for the Transaction Class. This field is set from the value in the 'Default Payment Terms' field on the associated Order transaction class. This field is always required and is never editable. 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. This field is always editable from the record view. The options include:
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 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.DocumentLogoLocation |
| Single Date Management | A Yes/No lookup to select whether or not specific dates on a sales transaction will default 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 only have the ability to enter and edit the “Order Date” on a sales transaction. The following date fields will default from the 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. 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. 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 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. 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 |
...