Sales Order Record View

A Sales Order is a document generated by the seller upon receiving a request, or purchase order, from a buyer. It specifies the details about the product or service along with price, quantity, billing & shipping addresses, payment terms, and more. 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.

(lightbulb) 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

Page Header

Header Toolbar

Toolbar IconsDescription
Delete Deletes the transaction, batch, or master file record. When clicked, users will be prompted with: "Are you sure you want to delete this record?". Click "OK" to confirm, or "Cancel" to return without deleting. 

WARNING: Records cannot be recovered once they are deleted!

More Actions

 Displays a drop down menu of related actions. The list of options includes:

  • 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

 Allows users to select the type of transaction or record they want to add.

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

 Opens the Notes dialog, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the record. This icon is always enabled. 

Notes are used throughout the application to add additional details to Master Files and Transactions. Transactions and Master Files that support Notes store the text of the note in one or more 'Note Types' as a way to classify/organize notes. 

Print Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. 

When clicked, all the Reports that launch from the Print Dialog that are assigned to this page, and that the user has rights to (if Report Data Access is enabled) are displayed.

Save

 Saves the changes made to the record. 
Save & Close Saves your changes and closes the page.

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 'Approved' and 'Ready To Post'. It is editable while the transaction is in a Status less than 'Shipped'. 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

Identifies the amount of available credit that is remaining for the Customer. 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

Identifies the default Carrier associated with the transaction. 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.

Carriers represent entities that transport goods from one location to another. They can be actual freight companies (i.e. UPS or Fed Ex) and/or they can represent a delivery method (i.e. Our Truck, Customer Pickup, Transfer in Storage, or UPS-Air). They are used on Inventory transfers and sales order shipments. 

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

Displays the default date the order (or Shipment) will be delivered, formatted from the users 'Date Format' preference. 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.

(lightbulb) 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

Identifies if a hold has been placed on the transaction. 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.

Hold Codes are used to prevent a process from being performed or a transaction from being posted.

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

Identifies the date of the transaction. 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

Identifies the Purchase Order number (PO number) entered for the transaction. 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. 

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

A Purchase Order (aka PO) is a document issued by a buyer committing to pay the seller for specific products or services to be delivered in the future. The advantage to the buyer is the ability to place an order without immediate payment. From the seller’s perspective, it reduces credit risk, since the buyer is obligated to pay once the products or services have been delivered. Each PO has a unique number associated with it that helps both buyer and seller track delivery and payment.  

Database Field: ERPx_SOOrderHeader.PurchaseOrder

Ship By

Displays the default date the order (or Shipment) is, or was, expected to be shipped, formatted from the users 'Date Format' preference. 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.

(lightbulb) 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

Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. 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.

Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances.

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

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

Status is used to identify where a transaction, Purchase Order, Price List, BOM, or Master File record is in its life cycle. Records start in a Status of 'New' and progress sequentially through additional statuses until they are 'Posted' or 'Closed'. The list of potential Statuses changes depending on the transaction type.  The Statuses that apply to transactions in this Record View include:

New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist.  

Released: This status is used to signify that the transaction is ready to be released to production. While in the Status of 'Released', all editable fields are open for edit.

Shipped: This status indicates the order has physically left the facility. This either manually updated or automatically updated if the order was shipped from a Site that has an integrated bar code system. Line Item edit for orders in this status is controlled by the Status Setup configuration.

Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned.

Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled with the exception any fields that are always editable and updates the Transaction Status to "Posted".

Database Fields: ERPx_SOOrderStatus.OrderStatusName, ERPx_SOOrderHeader.OrderStatusSK

Workflow

Identifies workflow step the transaction is in. 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'.

A workflow is a sequence of steps/tasks involved in moving from the beginning to the end of a process.  Workflow Groups are created for transactions and have defined steps to specify how a transaction can move to different statuses.

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
BOL

Identifies the Bill of Lading 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 Quote transactions. If entered, it must be <=100 characters.

Bill of Lading (BOL) is a document of title, a receipt for shipped goods, and a contract between a carrier and shipper. This document must accompany the shipped goods and must be signed by an authorized representative from the carrier, shipper, and receiver.

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.

Carriers represent entities that transport goods from one location to another. They can be actual freight companies (i.e. UPS or Fed Ex) and/or they can represent a delivery method (i.e. Our Truck, Customer Pickup, Transfer in Storage, or UPS-Air). They are used on Inventory transfers and sales order shipments. 

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.

Freight Terms are used to describe the contract terms between the shipper and receiver or product. They can be assigned to Inventory Transfer and Sales Order Shipments. These can print on transaction documents but do not drive an other functionality.

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 #

Identifies the invoice number associated with the sales order shipment. 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.

(lightbulb) 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

Identifies the unique Shipment ID for the 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.

Notes are used throughout the application to add additional details to Master Files and Transactions. Transactions and Master Files that support Notes store the text of the note in one or more 'Note Types' as a way to classify/organize notes. 

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.

Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances.

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

(lightbulb) 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

Identifies the name of the inside salesperson associated with the transaction. 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'.

Salespeople are individuals that sell goods and services to other entities. Inside Salespeople typically work in the office and are involved with sales over the telephone, email, or other cyber communication methods.

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

Identifies the name of the outside salesperson associated with the transaction. 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'.

Salespeople are individuals that sell goods and services to other entities. Outside Salespeople typically work outside the office and are involved with face to face meetings with active and prospective customers.

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

Payment Terms identify the terms your company extends to your Customers and that your Vendors extend to you. Payment Terms are used to calculate aging and payment discounts.

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

This is a numeric textbox that identifies the Discount Days associated with the Payment Terms. This defaults to the number of Discount Days associated with the Payment Terms assigned to the transaction but can be overwritten while the transaction is in a status less than Approved. This value must be greater than or equal to 0 and is used to calculate the Discount Date for the corresponding transaction. If the Payment Term does not have Discounts associated with it, this defaults to blank and is not editable.  

(lightbulb) Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated.

Database Field: ERPx_SOOrderHeader.DiscountDays

Due Days

This is a numeric textbox that identifies the Due Days associated with the Payment Terms. This defaults to the number of Due Days associated with the Payment Terms assigned to the transaction but can be overwritten while the transaction is in a status less than Approved.  This value must be greater than or equal to 0 and is used to calculate the Due Date for the corresponding transaction. 

 Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated.

Database Field: ERPx_SOOrderHeader.DueDays

Group: 3
Transaction Class

The unique identifier of the Transaction Class. This is a non-editable text box that is required. It defaults from the 'Transaction Class' value selected by the user when the transaction was created and/or edited on the Select Ship-To page when the sales order or sales quote was created. It is never editable once a transaction has been created. 

Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each.

Database Field: ERPx_SOOrderType.DocumentID

Transaction ID

Identifies the unique Transaction ID for each transaction. This is a non-editable text box that is required. This field is informational and never editable.

Sales transaction numbers may be system assigned IDs to differentiate unique transactions. Transaction ID's are unique by the unique combination of 'Document Prefix' + 'Next Document Number'.

Database Field: ERPx_SOOrderHeader.OrderID

Customer ID

Displays the unique identifier for the Customer record or for the Customer assigned to a transaction. This is a non-editable text box that is required. It defaults from the 'Customer' field for the selected Address on the Select Ship-To page. It can be edited from the 'Customer ID' field on the 'Properties' tab of the associated Customer on the Customer Record View.

Customer IDs are used as a short description and the unique identifier for Customers. They can be changed at any time to any alphanumeric value. If you do not have an existing strategy for Customer IDs the 3-3-2 method would be recommended.

Database Fields: ERPx_ARCustomer.CustomerID, ERPx_SOOrderHeader.CustomerSK

Bill to Address ID

Identifies the ID of the Address for the associated Account. This is a non-editable text box that is required. It defaults to the 'Address ID' field where the Address Type is 'Billing" or "Both" for the selected Customer. It can be edited from the 'Address ID' field on the 'Properties' tab of the Customer Addresses Record View.

Customer Address IDs are used as a short description and unique identifier for Customer Address records. They can be changed at any time to any alphanumeric value. For Customers with only one Address, the default value of PRIMARY can be used. Address IDs of BILLING and SHIPPING are often used for Customers with separate addresses for each. For customers with many Ship-to addresses a City or Street name can be used.

Database Fields: ERPx_ARCustomerAddress.AddressID, ERPx_SOOrderHeader.AddressSK

Ship to Address ID

Displays the ID the Ship To Address associated with the Customer on the transaction. This is required. It defaults based on the 'Ship To' address selected on the 'Select Ship To' page. This is editable when the Status is New, Released, or Shipped.

The lookup contains the list of 'Active' Address IDs with an Address Type of "Shipping" or "Both" belonging to the Customer assigned to the transaction.

Database Fields: ERPx_ARCustomerAddress.AddressID, ERPx_SOOrderHeader.ShipAddressSK

Created By

Identifies the name of the user that created the record. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. This is a non-editable text box that is required.

Database Field: ERPx_SOOrderHeader.CreatedBy

Created

Identifies the Created Date & Time of the record, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. This is a system assigned value and is never editable by a user. This is a non-editable text box that is required.

Database Field: ERPx_SOOrderHeader.CreatedDate

Last Updated

Identifies the Last Updated Date & Time of the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. This is a non-editable text box that is required.

Database Field: ERPx_SOOrderHeader.LastUpdated

Last Updated By

Identifies the name of the user that last updated the Transaction. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. This is a non-editable text box that is required.

Database Field: ERPx_SOOrderHeader.LastUser

Original Transaction ID

Identifies the transaction ID of the original posted transaction. This is a non-editable text box that is required on Price Adjustment and Return transactions and on Sales Orders that originated from a Quote. This is not applicable to Quote transactions. This defaults from the 'Transaction ID' field of the original Sales Order or Sales Quote transaction. This field is informational and never editable.

Sales transaction numbers may be system assigned IDs to differentiate unique transactions. Transaction ID's are unique by the unique combination of 'Document Prefix' + 'Next Document Number'.

Database Field: ERPx_SOOrderHeader.OriginTransID

Group: 4
EDI Order Status

Identifies the status of the Electronic Document Interchange for the transaction. This is a single-select standard lookup that is required. It defaults to "No EDI". This field is editable while the transaction is in a Status less than 'Approved'. It is disabled if saved in any status other than "No EDI". Additionally, a "(E)" is added to the end of the Transaction ID if the transaction is saved in any status other than "No EDI". This field is for information only.

This lookup contains the values in the EDIOrderStatus Enumeration Class.

Database Field: ERPx_SOOrderHeader.EDIOrderStatusEN

Master Number

Identifies the unique SK value of the originating transaction. This is a non-editable text box that is required. For Sales Order and Sales Quote transactions, this defaults from the 'Transaction SK' field. For Price Adjustments and Return transactions, this defaults from the 'Transaction SK' field of the original sales order transaction. This is a system assigned value and is never editable. 

Database Field: ERPx_SOOrderHeader.MasterNumber

Original Transaction Type

Identifies the Transaction Type associated with the original posted transaction. This is a non-editable text box that is required if the 'Original Transaction ID' field has a value. It defaults from the transaction type selected when the original transaction was created. This field is informational and never editable.

Transaction Types are used to differentiate unique types transactions within the system. Transactions with the same Transaction Type share the same record view pages and business rules. Transaction Types can be further classified using Transaction Classes. Every transaction in the system is assigned a Transaction Type.

Database Fields: ERPx_ARTransactionType.TransactionName, ERPx_SOOrderHeader.OriginTransTypeSK

Ship to Address SK

Displays the unique SK value of the Ship To address associated with the Customer on the transaction. This is a non-editable text box that is required. It defaults based on the 'Ship To' value selected on the 'Home' tab.  This is a system assigned value and is never editable. 

Database Field: ERPx_SOOrderHeader.ShipAddressSK

Transaction SKDisplays the unique SK value of the transaction. This is a non-editable text box that is required. This is a system assigned value and is never editable.

Database Field: ERPx_SOOrderHeader.OrderHeaderSK

Attributes Tab

Fields
Description
Attributes

A non editable text box that shows the name of the Attribute. Attributes are user-definable fields that are used on master files and transactions and are editable from the Attributes List View. The Attribute will only be displayed if the Applies property on the Assign Attribute Rules by page is set to either "Yes - Required" or "Yes - Not Required". Attributes set to "No" will not be displayed. The Attributes displayed here are setup and assigned in the Attributes section of the Company module (Company → Setup → Attributes → Sales Order). 

RequiredA non editable text box that shows whether the Attribute Value is required or not. If the Attribute Value is required, it will display "Yes". If it is optional, it will display as blank. This value is only editable from the 'Assign Attribute Rules' page (Company → Setup → Attributes → Sales Order → Transactions hyperlink). 
Value

Identifies the value assigned to the corresponding attribute.

Because Attributes are configurable as either Text, List, Date, or Date/Time the data entry is either a text box, lookup, or date picker. The value defaults to blank and is only required if the Attribute's 'Applies' property is set to "Yes - Required" in the Assign Attribute Rules page. Attribute Values for Master Flies are always editable. Attribute Values for transactions are always editable for unposted transactions.

 This is editable if the Transaction Class property 'Allow Attribute Edit After Approval' is set to "Yes".  

Page Details

Toolbar IconsDescription
Add Item

 Adds a blank line in the grid to allow for data entry. If a valid Item ID is entered, the line will be saved. If not, the 'Item Lookup' window will open allowing users to search for the Item. This button is not displayed on Price Adjustment transactions.  

Allocate Options

A split button that allocate lots by the following methods:

If the transaction has multiple shipments for different Sites, when users select one of these options the message "Items are assigned to different sites. Please select only items assigned to the same site." will be displayed.  Users can select a line item/s for the same site and then select one of these options to allocate the items.  

Column Filter Show/Hide Toggles between displaying and hiding a filter row in the grid under the column headers. The filter row will be displayed by default if the Quick Column Filter is also implemented in the page. When enabled, this will allow users to type in text to filter by a specific column.
Excel Exports the contents of the list view to an Excel file that will automatically download. The contents that export are those that are visible to the user. Therefore, if the user has filtered the view only the filtered contents will be exported. 
Find Items & Lots

A split button that find items by the following methods:

  • Find Items - Allow for adding items to sales transactions when allocations will be done at a later time.
  • Find Items with Balances - Allow for adding items to sales transactions, while showing item balances, when allocations will be done at a later time.
  • Find Lots - Allow for adding and allocating items in a single step.
Group By Show/Hide Toggles between displaying and hiding a row in the grid above the column headers to enable grouping by one or more column(s). Once displayed, users may drag and drop column headers to group by a specific column. Once the grid is grouped by a column(s), a subtotal footer row will display in the grouping for columns that have a page footer total. 
Help Opens the online WIKI help page for the current page. 
Item Notes

Opens the Item Notes dialog, allowing users to enter Notes and/or attach files to the selected line item. If no line items are selected, the note(s) will be saved to all line items or appended to any existing Notes. Files can only be attached to a single selected line item. Item Notes can be added even after a transaction is posted.

Notes are used throughout the application to add additional details to Master Files and Transactions. Transactions and Master Files that support Notes store the text of the note in one or more 'Note Types' as a way to classify/organize notes. 

More Actions

 Displays a drop down menu of related actions. The list of options includes:

  • IQ: Sales Item History - Opens the Sales Item History Inquiry in a new tab/window for the selected Item(s) ordered on posted sales transactions in the past 90 days for the corresponding Customer.  If no Item(s) is selected the inquiry opens filtered for all Items for the associated customer.  Note: This is only visible on Quote and Order type transactions. 
  • Substitution - Opens the Sales Order Item Substitution Record View for users to view, update and delete substitution item(s) that can be used in place of an ordered item. Users may add substitution items directly to the sales transaction using this Record View. 
Quick Column Filter

 Used to filter across all columns in the grid. When the user types text into the Quick Column Filter text box, the grid's Filter Row will be automatically hidden. The text in the Quick Column Filter text box automatically replaces any existing Filter Row filters. The results of the data immediately refresh as you enter text. 

Saved Layouts

 Displays the column layout lookup and related icons. This tool allows users to select a previously saved layout, create a new layout, save changes to a layout, forget/delete a layout and/or assign a saved layout as the default for the page. Once changes are made to the layout, such as columns are added or removed, the user can click the Save Layout icon and save the changes to the column layout. The visibility of the Filter Row is also saved with a saved layout. The new layout can also be set as the default. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific).  Default layouts can be removed by clicking the 'Set as Default' button again when the current default layout is selected.  

Please note that existing saved grid layouts will display the Filter Row as hidden by default.

Remove Items

 Removes the selected line(s). When clicked, you are prompted with the message "Are you sure you want to delete n item(s)? Okay or Cancel". This cannot be done on transactions with a Status of 'Approved', Ready to Post', 'Posted', 'Closed', 'Void', or 'Replaced'.

FieldsDescription
CheckboxUsed to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Account

Identifies the GL Account and Account Description for the line item.  This is an editable textbox that is not required.  It defaults to the Sales GL Account for the corresponding line item if one is setup on the Item master file, else it defaults to blank. It is editable until the transaction is in a status of 'Approved', 'Ready To Post' or 'Posted'.  

The Account can be updated by entering a new account segment value along with the separator to quickly replace an account with a new account value (for example an account in the same division but different department), or search for an account based on the account segment(s) entered.  For example, if the line item Account displays ‘1000-111-10 - Sales: Pacific Cod’ and a user enters '-12' and an active account number '1000-111-12' exists, the Account field will be automatically updated to display the new account number and account description. 

Additionally, the "Account Segment for Quick Replacement" preference in Financial > Configuration > Preferences can be set for the most commonly replaced Account Segment to allow for the account to be updated automatically based on the segment value entered without the segment separator. 

For example:

  • The Account Format in NorthScope is setup with three segments, broken down as follows: Segment 1 = "Account" and is 4 digits long, Segment 2 = "Division" and is 3 digits long and Segment 3 = "Department" and is 2 digits long.
  • Account Segment for Quick Replacement Financial Preference is set to ‘3 - Department’
  • User opens Sales Transaction Record View with a line item Account of ‘1000-111-10 - Sales: Pacific Cod’
  • User deletes Sales GL Account content and types in ‘12’
  • NorthScope uses the entry of ‘12’ combined with the Account Segment for Quick Replacement preference of ‘3 - Department’ to determine the ‘12’ is referencing the department segment of the GL Account and does one of two things:
    • Defaults the Sales GL Account to the only account that matches, if there’s only one, reading “1000-111-12 – [Account Description]”
    • Displays the Account Lookup with all the Accounts available that match the value entered for the user to select the correct account

A GL Account Segment is a specific part of a GL Account. Every GL Account contains at least 1 segment referred to as the "Natural Account" but some companies require additional structure to segment Natural Accounts by things like Companies, Divisions, Departments,, etc. GL Account Segments are typically separated by "-" (e.g. 2000-00).

Note: Users may only replace an account with active accounts that are set to 'Open to SO' in the GL Accounts master file.  

Note: This field is always disabled on negative lines of a Price Adjustment transaction. 

Database fields: ERPx_GLAccount.AccountNumber - ERPx_GLAccount.Description, ERPx_SOOrderItem.AccountSK

Actual Cost

Displays the Actual Cost assigned to the item or lot. This is a non-editable text box that is not required. It defaults as "0.00000". If there is an Actual Cost associated with the item, this field is calculated as [Quantity] x [Actual Cost], where Quantity comes from the 'Cost UOM' of a single unit (or weight equivalent) on the 'Properties' tab of the Item Record View. For example, if the 'Cost UOM' of an item is "Cases", then the calculated Actual Cost would be [1] x [Actual Cost]. If the 'Cost UOM' of an item is "Lbs", then the calculated Actual Cost would be [Weight per 1 unit] x [Actual Cost]. It is editable from the 'Actual Cost' field on the 'Properties' tab of the Item Record View.

The Actual Cost reflects the cost that will post to the General Ledger. For some items this may be set from a default or "standard" cost rate and for other items this may reflect that actual amount paid to purchase or incurred to produce the product. For each individual LotSK, this is calculated as the [Actual Base Cost Rate] + sum of all the [Actual Cost Layer Rates]. 

Database Field: ERPx_IMItem.CurrentCost

Amount 

Identifies the extended amount of the line item based on allocated quantities. This is a non-editable text box that is required. This field defaults as "0.00" and is calculated as [Allocated Quantity] x [Price], where Allocated Quantity is either 'Units' if the 'Price UOM' is unit-based or 'Weight' if the 'Price UOM is weight-based. This field can be updated by changing allocated quantities or the 'Price' field.

Database Field: ERPx_SOOrderItem.AllocatedAmount

Amount - Ord.

Identifies the extended amount of the line item based on the ordered quantities. This is a non-editable text box that is required. This field defaults as "0.00" and is calculated as [Ordered Quantity] x [Price], where Ordered Quantity is either 'Units - Ord.' if the 'Price UOM' is unit-based or 'Weight - Ord.' if the 'Price UOM is weight-based. This field can be updated by changing ordered quantities or the 'Price' field.

Database Field: ERPx_SOOrderItem.OrderedAmount

Brokerage Amt.

Identifies the total 'Program Amt.' for all the Brokerage programs associated with the line item. This is not required. This is a calculated field and may be edited from the Sales Program Details Record View or by editing one or more of the associated Sales Programs.

Identifies the amount being accrued from one or more Brokerage programs.

Database Field: ERPx_SOOrderItem.BrokerageAmount

Certification

Displays the required certification(s) for the line item. This is a multi-select lookup that is not required. When additional line items are added, any 'Default Certification' values in the 'Properties' tab that are checked are automatically selected for the line item. Else, this field defaults as blank. This field is editable while the transaction is in a Status less than 'Approved' or when the line item has been allocated, whichever occurs first. This field is always disabled for Price Adjustment and Return transactions.

This lookup contains a list of all selected Lot Certifications for the line item on the Item Record View where the Lot Certification Type is "Item Only" or "Item & Site'.

(lightbulb) Any new certifications that are selected/ removed from the 'Default Certification' field will only apply to new items added to the order and will not update existing items.

Database Fields: ERPx_IMCertification.Certification, ERPx_SOOrderItemCertification.CertificationSK , ERPx_SOOrderItem.OrderItemSK

Contract

Identifies the sales contract the line item is associated with. This is a single-select standard lookup that is not required. It defaults as blank and is sometimes editable. This field is editable while the transaction is in a Status less than 'Approved'. However, this field is always disabled on Sales Quote and Price Adjustment transactions.

Sales Contracts are used to manage sales obligations between the company and a customer. In some instances, a customer will contract with the company to purchase an agreed upon amount of product over a set time period. This provides the customer with assurances that their demand can be met and provides the company with assurances that they will not over/under produce products to meet their customer demands.

This lookup contains a list of all Contracts where the Customer on the Contract is equal to the Customer on the transaction and the transaction Order Date falls within the Contract Start/End date.

Database Fields: ERPx_SCContractHeader.ContractID, ERPx_SOOrderItem.ContractHeaderSK

Cost Amt.

Identifies either the total 'Actual' or 'Market' cost for the line item. This is not required and can only be edited by editing either the 'Actual' or 'Market' costs for the line item and/or one or more of the allocated Lots. 

If the Sales Order Cost - Sales Order Preference is set to 'Actual' then this will use the Actual Costs, if set to 'Market' then it will come from the Market Cost.

Identifies the extended cost amount for the Inventory Item(s). This will show either the Actual or Market cost depending on the value specified in the Sales Order Cost - Sales Order Preference.

Database Field: ERPx_SOOrderItem.ExtendedCostAmount or ERPx_SOOrderItem.ExtendedMarketCostAmount

Cost Rate

A calculated filed that identifies either the total 'Actual' or 'Market' cost rate for the line item. This is a calculated field that is calculated from dividing the Total Cost by the quantity. This is not required and can only be edited by editing either the 'Actual' or 'Market' costs for the line item and/or one or more of the allocated Lots. 

If the Sales Order Cost - Sales Order Preference is set to 'Actual' then this will use the Actual Costs, if set to 'Market' then it will come from the Market Cost.

Database Field: ERPx_SOOrderItem.CostRate 

Cost UOM

Identifies the unit of measure the item's cost is stated in terms of. This is the value assigned in the "Cost UOM" property on the Item Record View. This is required for Costing and can be edited from the 'Cost UOM' property on the 'Advanced Properties' tab of the Item Record View.

Database Field: ERPx_SOOrderItem.CostUOMSK 

Freight Amt.

The Freight Amt. represents the freight/shipping cost of the Product(s) on a Sales Transaction. It is set one of two ways:

  1. Manually by clicking on the Shipment hyperlink on the Shipment Tab and entering delivered freight amounts.
  2. Automated from 'Accrual' Sales Programs where the 'Freight Accrual' property is set to "Yes".

The amounts entered are rolled down to the items based on total weight. 

 This is not required. This is a calculated field and may be edited from the Shipment or by editing one or more of the associated Sales Programs.

Database Field: ERPx_SOOrderItem.FreightAccrualAmount

Gross Margin Amt.

The Gross Margin Amt. is a calculated field that identifies the profit amount just factoring in product costs. Whereas the Net Margin Amount is used to show the final profit amount that also includes Freight, Brokerage, Rebates, and Other Accrued expenses, the Gross Margin Amt. only includes Product Costs. It is calculated as:

[Ext. Amount] - [Product Cost Amt.]

Gross Margin Pct

Gross Ma