Sales Order Record View

Sales Order Record View

The purpose of this page is to record the details for sales transactions. From here, users can add and allocate items, edit shipping information, associate items to contracts, adjust freight accruals and more. Additionally, users may assign a price list to the transaction or reprice specific items as need. Journal details generated by the transaction may also be viewed from this page.

Once items have been added to the transaction, the 'Shipments' tab will be visible and allow for edit of shipment information.

In addition to Sales Orders, this record view is also used for the following:

  • Quotes: transactions used to give an estimate for a potential order by adding items, quantities and associated prices. Quantities entered may affect inventory if the item has been allocated. However, Quotes do not create journal entries, cannot be assigned contracts and do not generate invoices. When the Status of a Sales Quote is set to "Approved", it becomes a Sales Order transaction.

  • Returns: Transactions that allow users to quickly generate returns against Posted Invoices without the risk of returning items and/or lots that were never sold or returning more than was sold.

  • Price Adjustments: transactions that allow users to generate price adjustments against Posted Invoices.

 This record view also contains columns for each Attribute that is set up for the 'Sales Order Item' attribute type. Because these are user defined, they are not included in the default view but can be added a saved column layout. Sales Order Item attributes are not included in the help documentation.

Software Version: 2023.11.30 and newer

[ 1 Page Header ] [ 1.1 Header Toolbar ] [ 1.2 Home Tab ] [ 1.3 Shipments Tab ] [ 1.4 Properties Tab ] [ 1.5 Attributes Tab ] [ 2 Page Details ] [ 2.1 Related Topics ] [ 2.1.1 Page Definitions ] [ 2.1.2 Technical Details ]

Page Header

Header Toolbar

Toolbar Icons

Description

Toolbar Icons

Description

Delete

More Actions

  • IQ: Applications - Opens the Transaction Navigation Details Record View and allows the user to manually apply and unapply documents.

  • IQ: Transaction History - Opens the Sales Transaction History Inquiry in a new tab/window for the Customer selected on the transaction.  The inquiry automatically filters for all posted sales transactions in the past 90 days for the corresponding Customer.

  • RV: Journal Details - Opens the Journal Details window showing the Journal Entry for the associated transaction. Please note there are no journal details on Sales Quote transactions.

     Until a transaction is Approved or Posted, this is a temporary journal entry so no Journal ID will be assigned. 

  • RV: Program Details - Opens the Sales Program Details Record View and displays all transaction item(s) that are on an associated On Invoice or Freight Accrual sales program. Please note there are no program details on Sales Quote transactions.

  • Add Shipment - Allows users to add Shipments with different sites and carriers to a Quote/Order.  A new line will be added to the Shipments Tab where users can select a Site, Carrier, Ship By and Deliver On date. 

     This is not applicable (the option is disabled) to Price Adjustments, Returns and logistics Orders (Load Management). 

  • Change Address - Opens the Change Address Record View allowing users to change the shipping address of the transaction. 

  • Change Customer - Opens the Sales Transactions - Change Customer Record View allowing users to change the customer that was previously selected and assigned to the transaction.

  • Remove Shipment - Allows users to remove a Shipment when there are multiple shipments.  Users will not be able to remove the first sequenced shipment, the message "The first Shipment on an order cannot be deleted." will be displayed.  Users will not be able to remove shipments that are assigned to items that have allocations, the message "Shipments with items that have allocations cannot be deleted." will be displayed.  Additionally, if users try to remove a shipment that have items assigned that are not allocated, the item(s) will be moved to the first shipment on the transaction and the message "Shipment [Shipment Number] has been removed and all items on the shipment have been moved to [Shipment Number] [Item(s)]" will be displayed. 

     This is not applicable (the option is disabled) to Price Adjustments, Returns and logistics Orders (Load Management). 

  • Save & Reprice - Reprices any items belonging on a price list and saves the transaction. Users will not be able to reprice Price Adjustment or Return transactions.

New

Each Transaction Type (Quote, Order, Return, or Price Adjustment) with only a single Transaction Class will be displayed as just the Transaction Type Name (e.g. Order).  Each Transaction Type with more than one Transaction Class will be displayed as Transaction Type Name-Transaction Class Name (e.g. Order-Fresh). The base list of Transaction Types includes:

  • Order: Opens the Sales Order: Select Ship-To Record View for users to select the Customer / Customer Address to ship the sales order.

  • Quote: Opens the Sales Order Quote: Select Ship-To Record View for users to select the Customer / Customer Address associated with the sales quote.

  • Return: Opens the Sales Return: Find an Invoice page for users to find a posted invoice and create a Return transaction.

  • Price Adjustment: Opens the Price Adjustment: Find an Invoice page for users to find a posted invoice and create a Price Adjustment transaction.

Note: The Transaction Class will display after the Transaction Type if there is more than one Transaction Class for the Transaction Type.

Notes

Print

Save

Save & Close

Home Tab

 

Order #: [Transaction ID]         Ship To: [Customer Address Name] [Address 1] [Address 2] [Address 3] [City], [State] [ZIP]  

Fields

Description

Actual Ship

Displays the actual date the order was shipped, formatted from the users 'Date Format' preference. This is a date picker that is required to save a transaction in a Status of 'Shipped', 'Approved' and 'Ready To Post'. It is editable while the transaction is in a Status less than 'Approved'. If missing, the message "Actual Ship is required when marking an order as Shipped, Approved, or Ready to Post." will be displayed on Save. If entered, it must be on or after the Order Date, else the message "Actual Ship Date must be on or after Order Date." will be displayed on Save.

Database Field: ERPx_SOOrderHeader.ActualShipDate

Avail. Credit

 This is a non-editable numeric text box that is not required. It defaults as blank if the 'Credit Limit Option' property on the Customer Record View is set as "No Credit" or "Unlimited Credit". Else if the Customer has a Credit Limit amount, then this field is calculated as [Credit Amount] - [Unpaid Invoices] - [Open Balances] - [Total Ext. Amount]. This field is automatically updated when item quantities are entered and the transaction is Saved. If the Available Credit is negative and the 'When credit limits are exceeded' sales preference is set to "Place on Credit Hold", the the message "Transaction [Transaction ID] has been placed on credit hold because the customer has exceeded their credit limit" will be displayed on Save. If the Available Credit is negative and the 'When credit limits are exceeded' sales preference is set to "Warn", the message "Warning, this customer has exceeded their credit limit." will be displayed on Save. This field is color coded as follows:

  • Available Credit > 30%: No coloring

  • Available Credit < = 30%: Green

  • Available Credit < = 10%: Yellow

  • Available Credit < = 0%: Red

This field is for informational use only, cannot be edited and is not stored in the database.

Note - The 'Customer Info' tab on the Find Items / Find Items with Balances Record View also displays the customer's credit limit and available credit percentage.

Avail. Credit %

Displays the current Available Credit as a percentage. This is a non-editable numeric text box that is not required.  This information is only displayed when the ‘Credit Limit Option‘ on the customer record is set to ‘Specific Amount’ and the transaction status is less than 'Ready to Post'. This value is automatically updated when items are entered on the page and ‘Save’ toolbar icon is clicked. This information is for informational use only and cannot be edited. This field is color coded as follows:

  • Available Credit > 30%: No coloring

  • Available Credit < = 30%: Green

  • Available Credit < = 10%: Yellow

  • Available Credit < = 0%: Red

This field is for informational use only, cannot be edited and is not stored in the database.

Note - The 'Customer Info' tab on the Find Items / Find Items with Balances Record View also displays the customer's credit limit and available credit percentage.

Carrier

This is a single-select standard lookup that is conditionally required. This field is only required if the sales order's Transaction Class property for 'Is Carrier Required' is set to "Yes".

This defaults in the following sequence:

  1. The 'Carrier' field selected on the Select Ship-To page. If a 'Carrier' has not be selected on the Select Ship-To page, this will default from

  2. The 'Sales Order Carrier' assigned to the Customer Address. If a 'Sales Order Carrier' has not been assigned to the Customer Address, this will default from

  3. The 'Default Carrier' assigned to the Sales Order Transaction Class. 

This is editable while the transaction is in a Status less than 'Shipped'. However, it is always disabled on Price Adjustment transactions. If required and missing, the message "Carrier is required." will be displayed on Save.

This lookup contains a list of all active Carriers.

Database Fields: ERPx_SOCarrier.CarrierName, ERPx_SOOrderHeader.CarrierSK

Credit Limit

Displays the credit amount assigned to the Customer. This is a non-editable numeric text box that is not required. This information is only displayed when the ‘Credit Limit Option‘ on the customer record is set to ‘Specific Amount’. This field is for informational use only and cannot be edited on this page but is always editable on the 'Credit Amount' property of the Customer master file (when the Credit Limit Option is set to Specific Amount).  

Database Fields: ERPx_ARCustomer.CreditLimitAmount, SOOrderHeader.CustomerSK

Deliver On

 This is a date picker that is sometimes required. It is required when the transaction's Transaction Class property 'Require a Deliver On Date' is set to "Yes". It defaults from the 'Deliver On' field selected on the Select Ship-To page and is editable while the transaction is in a Status less than 'Approved'. If entered it must be on or after the Order Date, else the message "Deliver On Date must be on or after Order Date." will be displayed on Save. It must also be on or after the Ship By Date, else the message "Deliver On Date must be on or after Ship By Date." will be displayed on Save.

Please note this field is disabled if the associated Transaction Class property of 'Single Date Management' is set to "Yes".

Database Field: ERPx_SOOrderHeader.ScheduledDeliveryDate

Hold Code

 This is a single-select standard lookup that is not required. It defaults as blank and is editable while the transaction is in a Status less than 'Approved'. If the Available Credit is negative and the 'When credit limits are exceeded' sales preference is set to "Place on Credit Hold", then the 'Default code for Credit Holds on Order' sales preference value will auto-populate in this field on Save.

This lookup contains a list of all Hold Codes where the 'Transaction Type' property is "Order".

Database Fields: ERPx_MFHoldCode.HoldCode, ERPx_SOOrderHeaderHold.HoldCodeSK

Order Date

This is a date picker that is required. It defaults from the 'Order Date' field selected on the Select Ship-To page. The Order Date must be on or before the Ship By Date, the Deliver On Date and the Actual Ship Date, else the messages "Ship by Date must not be earlier than Order Date." and "Deliver On Date must be on or after Order Date." and "Actual Ship Date must be on or after Order Date." will be displayed on Save. This field is  editable while the transaction is in a Status less than 'Approved'.

Database Field: ERPx_SOOrderHeader.OrderDate

Purchase Order

This is a text box that is not required. It defaults as blank and is editable while the transaction is in a Status less than 'Approved'. If entered, it must be <=35 characters. 

There is validation based on how the Sales Preference "Allow Duplicate PO Numbers" is set:

  • If set to "Yes" then any value is allowed.

  • If set to "No" then the same Purchase Order number may not be re-used by a Customer.

  • If set to "Warn" then you will be prompted with a message indicating that the Purchase Order number has already been used for the customer but the save is allowed. 

 This is only applicable to Sales Quote and Order type transactions. 

Database Field: ERPx_SOOrderHeader.PurchaseOrder

Ship By

 This is a date picker that is sometimes required. It is required when the selected transaction class 'Require a Ship By Date' property is set to "Yes". It defaults from the 'Ship By' field selected on the Select Ship-To Record View and is editable while the transaction is in a Status less than 'Shipped'. If entered it must be on or after the Order Date, else the message "Ship by Date must not be earlier than Order Date." will be displayed on Save. It must also be on or before the Deliver On Date, else the message "Deliver On Date must be on or after Ship By Date." will be displayed on Save.

Please note this field is disabled if the associated Transaction Class property of 'Single Date Management' is set to "Yes".

Database Field: ERPx_SOOrderHeader.ScheduledShipDate

Site

This is a single-select standard lookup that is required. It defaults from the 'Ship From Site' field selected on the Select Ship-To page. This field is editable when the transaction is in a Status less than 'Shipped' and there are no allocations. However, it is always disabled on Price Adjustment and Return transactions.

This lookup contains a list of all active Sites where the 'Visible to Sales' property is set to "Yes".

Database Fields: ERPx_MFSite.SiteID, ERPx_SOOrderHeader.SiteSK

Status

 This is a single-select standard lookup that is required. It defaults as "New" and is always editable until the transaction is posted.

 The Statuses that apply to transactions in this Record View include:

Database Fields: ERPx_SOOrderStatus.OrderStatusName, ERPx_SOOrderHeader.OrderStatusSK

Workflow

This is a single-select standard lookup that is not required. It defaults as "N/A" and is editable while the transaction is in a Status less than 'Ready to Post'.

This lookup contains a list of all user specified Workflow Group Steps for the associated Sales Order Transaction Type.

Database Fields: ERPx_MFWorkflow.WorkflowName, ERPx_SOOrderHeader.WorkflowSK

Shipments Tab

Fields

Description

Fields

Description

BOL

This is a text box that is not required. It defaults as blank and is always editable for non-logistic shipments while the transaction is in a Status less than 'Approved'. This field is always disabled on Quote transactions. If entered, it must be <=100 characters.

Database Field: ERPx_LMLoadTransaction.BOL

Carrier

Identifies the Carrier Name of the first leg of the shipment.  This is conditionally editable for Quote and Order type transactions based on the following rules and is sometimes required. This field is required when the Transaction Class property 'Require Carrier for New Transactions' is set to "Yes", else the message "Carrier is required on Shipments." will be displayed on Save. 

  • If this is the first sequenced Shipment in the grid the Carrier will default from the 'Carrier' field on the 'Home' tab of the Sales Transaction Record View and is not editable. 

  • If this is not the first sequenced Shipment, the Carrier will be editable until the transaction is saved in a status of Shipped or greater. 

This field is never editable on Price Adjustments or Returns and on Sales Quote and Order transactions with a single shipment.

Database Fields: ERPx_SOCarrier.CarrierName, ERPx_SOOrderItem.CarrierSK

Deliver On

Identifies the date the shipment is scheduled to leave the Site, formatted from the users 'Date Format' preferenceThis is conditionally editable for Quote and Order type transactions based on the following rules:

  • If this is the first sequenced Shipment in the grid the Deliver On date will default from the 'Deliver On' field on the 'Home' tab of the Sales Transaction Record View and is not editable. This value is required.

  • If this is not the first sequenced Shipment, the Deliver On field will be editable until the transaction is saved in a status of Shipped or greater. This value is not required.

This field is never editable on Price Adjustments or Returns and on Sales Quote and Order transactions with a single shipment.

Database Field: ERPx_LMLoadHeader.ScheduledArrivalDate

Export Details

Displays a link to the Export Details Record View. This is a hyperlink that is visible for all shipments with a Shipment ID. Clicking the link opens the Export Details Record View on top of the existing frame, allowing edit of additional information regarding the shipment container. This hyperlink is always enabled. This field is never editable and not stored in the database. 

Freight Amt.

Identifies the total "delivered freight" amount that will be accrued in the GL for the shipment. This a non-editable text box that is not required. It defaults as the total freight amount for all legs associated with the shipment on the Shipment Details Record View. This is a calculated field that is not editable.

Database Fields: ERPx_LMLoadTransaction.TotalFreight

Freight Terms

Identifies the freight terms assigned to the shipment. This is a single-select standard lookup that is only required if the transaction's Transaction Class property 'Require Freight Terms' is set to "Yes". It defaults from the 'Freight Terms' selected on the Select Ship-To page. This is always editable for non-logistics shipments while the transaction is in a Status less than 'Approved'. If required and missing, the message "Freight Terms are required for orders in the Transaction Class of [Transaction Class]. Please open the shipment from the Shipment tab to add any missing freight terms." will be displayed on Save. For logistics shipments, this field can be edited from the 'Freight Terms' field in the 'Order Freight Cost' tab of the Load Record View. This field is always disabled on Sales Quote transactions.

This lookup contains a list of all 'Active' Freight Terms.

Database Fields: ERPx_SOFreightTerms.Name, ERPx_LMLoadTransaction.SOFreightTermsEN

GL Date

Displays GL Date for the invoice associated with the shipment. This is a date picker that is required for the transaction to be saved in a status of 'Approved' or greater. It defaults as blank. If blank and the transaction is saved in a status of 'Approved', then this date will default from the 'Invoiced' date for the associated shipment. This field is always editable for the first sequenced shipment while the transaction is in a Status less than 'Approved'. For subsequent shipments this value will default from the first sequenced shipment and is never editable.

Shipments need to be invoiced prior to entering a GL Date. If the 'Invoiced' date is missing, then the message "A GL Date may not be saved until the shipment has been invoiced." will be displayed on Save. The date selected must reside within an open fiscal period, else the message "The 'Shipments Tab - GL Date' for one or more shipments is not in an open Fiscal Period." will be displayed when the transaction is saved in a status of 'Ready to Post'. This field is always disabled on Sales Quote transactions.

If the 'Single Date Management' property on the associated transaction class is set to "Yes", then this will default from the 'Order Date' field on the 'Home' tab of the Sales Transaction Record View.

Database Field: ERPx_SOInvoiceHeader.GLDate

Invoice #

This is a text box that is required for the transaction to be saved in a status of 'Shipped' and greater. It defaults as blank. On Sales Order transactions, if this field is blank when the Status of the transaction is saved as 'Approved', then the Invoice # will be automatically generated based on the transaction's Transaction Class property 'Get Next Invoice Number From'. On Return and Price Adjustment transactions, this field will append the 'Document Prefix' property on the associated transaction class to the original Invoice #. This is only editable for the first sequenced shipment while the transaction is in a Status less than 'Approved'. For subsequent shipments this value will default from the first sequenced shipment and is never editable.  This field is always blank and disabled on Sales Quote transactions, as Sales Quote transactions never generate invoices.

Additional info on regarding this field can be found in this FAQ: How are Invoice Dates and Invoice Numbers assigned?

Database Field: ERPx_SOInvoiceHeader.InvoiceNumber

Invoiced

Identifies the date the shipment was invoiced, formatted from the users 'Date Format' preference. This is a date picker that is required for the transaction to be saved in a status of 'Approved' and greater. It defaults as blank. On Sales Order transactions, if this is blank when the Status of the transaction is saved as 'Approved', then the 'Invoiced' date will be automatically populated based on the transaction's Transaction Class property 'How Invoice Dates Are Assigned'. However if the 'How Invoice Dates Are Assigned' property for the associated transaction class is set to "Manually Assigned", the message "Invoice Date must not be blank." will be displayed on Save.

On Return and Price Adjustment transactions, this field does not have the option to be automatically populated and if blank, the message "Invoice Date must not be blank" will be displayed on Save.

This field is only editable for the first sequenced shipment while the transaction is in a Status less than 'Approved'. For subsequent shipments this value will default from the first sequenced shipment and is never editable. This field is always blank and disabled on Sales Quote transactions, as Sales Quote transactions never generate invoices.

Database Field: ERPx_SOInvoiceHeader.InvoiceDate

Legs

Displays the total number of legs configured for the Shipment. This is a non-editable text box that is required. It defaults as 0 if the shipment does not have a Shipment ID. It defaults as 1 once a shipment ID has been created. This field is for informational use only and is not editable. It can be updated by adding a new leg on the Shipment Details Record View.

Database Field: ERPx_LMLoadTransaction.CountofLegs

Ship By

Identifies the date the shipment is scheduled to leave the Site, formatted from the users 'Date Format' preferenceThis is conditionally editable for Quote and Order type transactions based on the following rules:

  • If this is the first sequenced Shipment in the grid the Ship By date will default from the 'Ship By' field on the 'Home' tab of the Sales Transaction Record View and is not editable. This value is required.

  • If this is not the first sequenced Shipment, the Ship By field will be editable until the transaction is saved in a status of Shipped or greater. This value is not required.

This field is not editable when the shipment is a logistics shipment or a single shipment. This field is always disabled on Price Adjustment and Returns transactions.

Database Field: ERPx_LMLoadHeader.ScheduledShipDate

Shipment

Clicking on the link opens the Shipment Details Record View (for a non-logistics shipment) or the Load Record View (for a logistics shipment). This is a hyperlink that is required to save the Status of the transaction as 'Shipped'. It is never editable. The shipment ID is an auto-generated number. If the shipment's Carrier and Site are set as visible to Logistics, this will remain blank until a logistics shipments has been built from the Loads List View.

Database Field: ERPx_LMLoadHeader.LoadID

Shipment Notes 

Displays a link to the Notes dialog box. This is a hyperlink that is required for all shipments with a Shipment ID. Clicking the link opens the Notes dialog box, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the shipment. This hyperlink is always enabled. This field is never editable and not stored in the database.

Shipment Status 

Identifies the status of the shipment. This is a non-editable text box that is required. This field defaults as "New" for transactions in a Status of 'New' or 'Released'. This field displays as "Shipped" for transactions in a Status of 'Shipped', 'Approved', and 'Ready To Post'. This field displays as "Posted" for transactions in a Status of 'Posted'. This field is not editable.

Database Field: ERPx_LMLoadHeader.LoadStatusSK

Shipped

Identifies the date the shipment left the site, formatted from the users 'Date Format' preference. This is a non-editable text box that is required for the transaction to be saved in a status of 'Approved' or greater. It defaults as blank.

On Sales transactions with single shipments, this defaults from the 'Actual Ship' field in the 'Home' tab of the Sales Transaction Record View and is disabled. On logistic shipments, this field defaults from the 'Actual Ship' field on the 'Load Plan' tab of the Loads Record View.  This field is always disabled on Sales Quote transactions.

Database Fields: ERPx_LMLoadHeader.ActualShipDate, ERPx_SOOrderHeader.ActualShipDate

Site Name

Identifies the name of the Site where the shipment will ship from. This is conditionally editable for Quote and Order type transactions based on the following rules:

  • If this is the first sequenced Shipment in the grid the Site Name will default from the 'Site' field on the 'Home' tab of the Sales Transaction Record View and is not editable. 

  • If this is not the first sequenced Shipment, the Site Name will be editable until the transaction is saved in a status of Shipped or greater. This value is required, if missing the message "Site is required on Shipments" will be displayed on Save.

This field is never editable on Price Adjustments or Returns and on Sales Quote and Order transactions with a single shipment.

Database Fields: ERPx_MFSite.SiteName, ERPx_LMLoadHeader.SiteSk

Tracking #

Identifies the tracking number associated with the shipment(s) on the order. This is a text box that is not required. It defaults as blank and is always editable for non-logistic shipments while the transaction is in a Status less than 'Approved'. This field is always disabled on Sales Quote transactions. If entered, it must be <=100 characters.

Database Field: ERPx_LMLoadTransaction.TrackingNumber

Properties Tab

Fields

Description

Fields

Description

Group: 1

Default Certification

Identifies the certification(s) to be applied to the line items on the transaction. This is a multi-select lookup that is not required. It defaults from the 'Default SO Certification' field on the 'Properties' tab of the Customer Record View. When additional line items are added, any 'Default Certification' values that are checked are automatically selected for the line item. This field is editable while the transaction is in a Status less than 'Approved'. This field is always disabled on Return transactions.

This lookup contains a list of all active Lot Certifications.

Any new certifications that are selected/ removed from this lookup will only apply to new items added to the order and will not update existing items.

Database Fields: ERPx_IMCertification.Certification, ERPx_SOOrderHeaderCertification.CertificationSK , ERPx_SOOrderHeader.OrderHeaderSK

Salesperson - Inside

This a single-select standard lookup that is sometimes required. It is required to Approve or Post when the transaction's Transaction Class property 'Require Inside Salesperson for Posting' is set to "Yes". For all other transaction types, this field is not required. If required and missing, the message "[Transaction ID]: Inside Salesperson is required." will be displayed on Save. It defaults from the "Inside Salesperson" property for the Ship To Customer Address and is editable while the transaction is in a Status less than 'Approved'.

This lookup contains a list of all 'Active' Salespeople where the 'Type' property is "Inside Sales".

Database Fields: ERPx_SPSalesperson.Salespersonname where SalespersonTypeEN = 2, ERPx_SOOrderHeader.InsideSalespersonSK

Salesperson - Outside

This a single-select standard lookup that is sometimes required. It is required to Approve or Post when the transaction's Transaction Class property 'Require Outside Salesperson for Posting' is set to "Yes". For all other transaction types, this field is not required. If required and missing, the message "[Transaction ID]: Outside Salesperson is required." will be displayed on Save. It defaults from the "Salesperson" property for the Ship To Customer Address and is editable while the transaction is in a Status less than 'Approved'.

This lookup contains a list of all 'Active' Salespeople where the 'Type' property is "Outside Sales".

Database Fields: ERPx_SPSalesperson.Salespersonname where SalespersonTypeEN = 1, ERPx_SOOrderHeader.SalesPersonSK

Freight Purchase Order 

A system assigned value to identify whether a Freight Purchase Order is applicable / allowed and if it has been created or not.

  • For 'New' transactions, this is based entirely on the 'Auto-Create Purchase Orders for Delivered Freight' property of the Sales Order's Transaction Class.

  • For 'Posted' transaction this is updated based on the Transaction Class property, the Carrier(s) assigned to each Freight Leg containg estimated freight, and the Status of the transaction. This is not editable and will one of the following values:

  1. Not Applicable: The Transaction's Transaction Class is not configured to create Freight Purchase Orders.

  2. Freight PO Allowed: The Transaction's Transaction Class is configured to create Freight Purchase Orders and the Transaction is not Yet Posted.

  3. Freight PO Created: A Freight Purchase Order was created for the Freight Leg(s) on this Transaction.

  4. Freight PO Not Created: The Transaction's Transaction Class is configured to create Freight Purchase Orders but no Freight Purchase Order was created because not all the Freight Legs, that contained estimated freight, were for Carriers that were configured to create a Freight Purchase Order.

Database Field: ERPx_SOOrderHeader.FreightPOEN

Group: 2

Payment Terms

Identifies the Payment Terms associated with the transaction. This is a single-select standard lookup that is not required. It defaults from the associated Transaction Class 'Default Payment Terms' property, else it defaults from the 'Payment Terms' field on the 'Properties' tab of the associated Customer Record View. This is editable while the transaction is in a Status less than 'Approved'.

This lookup contains a blank value, the current assigned value, and a list of all the 'Active' Payment Terms.

Linked Database Field: ERPx_SOOrderHeader.PaymentTermsSK

Discount Days