Opens the mass update dialog, which allows to mass update the following properties: 

• Hold Code: A single-select lookup that defaults to "(No Change)", but also contains a list of all Hold Codes. Assigns the selected Hold Code to selected/filtered transactions when Apply is clicked. The selected Hold Code must match the transaction type, else the message "[Transaction ID]: The Hold Code did not match the transaction type and could not be applied." will be displayed on Save.
  
• Sales Order Attributes: All Sales Order attributes configured in the Attributes Master File. Assigns the entered/selected value to selected/filtered transactions when Apply is clicked.
  
• Reprice Sales Orders and Quotes: A Yes/No lookup that defaults to "No". Selecting "Yes" will reprice any line items on the selected/filtered transactions from the Price List specified on the transaction. Note: If the 'Price' field has previously been overridden by a user, the line item will not be repriced.
  
• Status: A single-select lookup that defaults to "(No Change)". Assigns the selected Status to selected/filtered transactions when Apply is clicked. Options 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".

• Workflow: A single-select lookup that defaults to "(No Change)". Assigns the selected Workflow Step to selected/filtered transactions when Apply is clicked. Options include:
  • (Next Step)
  • All Sales Order Workflow Steps set up on the Sales: Configuration - Workflow Record View
    

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

• RV: Allocate: Opens the Allocate Sales Transaction Item Record View to allocate by Inventory Lot or Warehouse Lot.
• Copy Order: After selecting an Order and clicking this option a new order is created with all of the same data with the exception of any allocations, Actual Ship date and Invoice details.  Note: This option is only available for Order type transactions.

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

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

• Quotes: Each unique Quote Class is displayed. When clicked, the Select Ship-To Record View opens allowing users to select the Customer / Customer Address associated with the quote.
• Order: Each unique Order Class is displayed. When clicked, the Select Ship-To Record View opens allowing users to select the Customer / Customer Address associated with the order.
  
• 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.

Opens the Notes dialog, filtered for the appropriate Note Type(s), allowing the user to enter Notes for the selected line item. From here, users can add, review, or edit Notes associated with the line item. If no line items are selected, entered Notes will apply to all line items and be appended to any existing Notes. This toolbar 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. 

 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.

 Selected transaction(s) that are on Hold with a hold code set to disable printing will display the message "One or more of the selected records cannot be printed.”

 Filtered transaction(s) that are on Hold with a hold code set to disable printing will not print anything, but any filtered records not on hold, or printing is enabled while on hold will print as expected. 

Identifies the ID of the Address for the associated Account. This is required and can be edited from the 'Address ID' field on the 'Properties' tab of the Customer Addresses Record View. This is the Address ID of the Ship To Address that was selected. It comes from the 'Ship To' field on the 'Home' tab of the Sales Transaction 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

Identifies the Name associated with the Address ID for the associated Account. This is required and can be edited from the 'Address Name' field on the 'Properties' tab of the Customer Addresses Record View. It comes from the 'Ship To' field on the 'Home' tab of the Sales Transaction Record View.

Database Fields: ERPx_ARCustomerAddress.AddressName, ERPx_SOOrderHeader.AddressSK

Identifies the amount being accrued from one or more Brokerage programs. This displays the total 'Program Amt.' of all line items on the transaction that qualify for one or more related Brokerage programs. This is not required. This is a calculated field and may be edited from the Sales Program Details Record View.

 This field uses the Ordered Ext Amount for transactions where the Status is less than "Shipped" and Allocated Ext Amount for transactions where the Status is "Shipped" or greater.

Database Field: ERPx_SPProgramSettlementItem.ComputedAmount

Identifies the default Carrier associated with the transaction. This is not required and can be edited from the 'Carrier' field on the 'Home' tab of the Sales Transaction Record View.

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

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. This field displays the total cost of all inventory line items on the transaction. This is not required and can be edited in the Update Costs inquiry.

 This field uses the last applicable cost for unallocated line items and the Actual or Market Cost for allocated items.

Database Field: ERPx_SOOrderHeader.ExtendedCostAmount

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 field is required.

Database Field: ERPx_SOOrderHeader.CreatedDate

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 field is required.

Database Field: ERPx_SOOrderHeader.CreatedBy

Identifies the Currency assigned to the transaction. This is required and comes from the 'Currency' field in the 'Home' tab of the Sales Transaction Record View. This field is not editable.

The Currency identifies the kind of money used for transactions. For example, if a Customer or Vendor is setup with a Currency of "USD" then all transactions for them are stated in terms of US Dollars and all payments received or made must be in US Dollars.

Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_SOOrderHeader.CurrencySK

Displays the unique identifier for the Customer record or for the Customer assigned to a transaction. This is required and can be edited from the 'Customer ID' field on the 'Properties' tab of the Customer Record View. It comes from the 'Ship To' field on the 'Home' tab of the Sales Transaction 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

Identifies the name of the Customer record or for the Customer assigned to a transaction. This is required and can be edited from the 'Customer Name' field on the 'Properties' tab of the Customer Record View. It comes from the 'Ship To' field on the 'Home' tab of the Sales Transaction Record View.

Customer Names are used as a long description for Customer records. 

Database Fields: ERPx_ARCustomer.CustomerName, ERPx_SOOrderHeader.CustomerSK  

Displays the default date the order (or Shipment) will be delivered, formatted from the users 'Date Format' preference. This is required and can be edited from the 'Deliver On' field on the 'Home' tab of the Sales Transaction Record View.

Database Field: ERPx_SOOrderHeader.ScheduledDeliveryDate

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 field uses the Ordered Ext Amount for calculations on transactions where the Status is less than "Shipped" and the Allocated Ext Amount on transactions where the Status is "Shipped" or greater.

Database Field:  ERPx_SOOrderHeader.FreightAccrualAmount

Identifies the Freight Terms assigned to the shipment. This is not required and can be edited from the 'Freight Terms' field on the 'Shipments' tab of the Sales Transaction Record View.

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.

Database Fields: ERPx_SOOrderHeader.SOFreightTermsEN, ERPx_SOFreightTerms.Description

Identifies the profit amount, using only product costs, on the transaction. This is not required and not stored in the database. This may be edited by editing any of the fields used in calculating this amount.

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

Identifies the percentage of profit, using only product costs, on the transaction. This is not required and not stored in the database. This may be edited by editing any of the fields used in calculating this amount.

Gross Margin % is a calculated field that identifies the Gross Margin % for the Transaction, Item, or Lot. It is calculated as:

[Gross Margin Amt.] / [Amount]

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 field is required.

Database Field: ERPx_SOOrderHeader.LastUser

Identifies the final profit amount on the transaction. This is not required and not stored in the database. This may be edited by editing any of the fields used in calculating this amount.

The Net Margin Amt. is a calculated field that identifies the final profit amount. Whereas the Gross Margin Amount is used to show the difference between the sales revenue and the Product Cost, the Net Margin Amount also includes Freight, Brokerage, Rebate, and Other Accrued expenses. It is calculated as:

[Gross Margin Amt.] - [Freight Amt.] - [Brokerage Amt.] - [Rebate Amt.] - [Other Accrual Amt.]

Identifies the percentage of final profit on the transaction. This is not required and not stored in the database. This may be edited by editing any of the fields used in calculating this amount.

The Net Margin % is a calculated field that identifies the final profit %. Whereas the Gross Margin % is used to show the profit margin just factoring sales revenue less Product Cost, the Net Margin % also includes Freight, Brokerage, Rebate, and Other Accrued expenses. It is calculated as:

[Net Margin Amt.] / [Amount]

Identifies if a hold has been placed on the transaction. This is required and can be edited from either the 'Hold Code' field on the 'Home' tab of the Sales Transaction Record View or via Mass Update on the Sales Transactions List View.

A transaction may be placed on hold by assigning a Hold Code. Hold Codes are used to prevent a process from being performed or a transaction from being posted.

Database Field: ERPx_MFHoldCode.HoldCode

The Other Accruals represent the amount calculated from 'Accrual' Sales Programs where the 'Freight Accrual' property is set to "No". This displays the total 'Program Amt.' of all line items on the transaction that qualify for one or more related non-freight Accrual programs. This is not required. This is a calculated field and may be edited from the Sales Program Details Record View.

 This field uses the Ordered Ext Amount for calculations on transactions where the Status is less than "Shipped" and the Allocated Ext Amount on transactions where the Status is "Shipped" or greater.

Database Field: ERPx_SPProgramSettlementItem.ComputedAmount

Identifies the Payment Terms assigned to the transaction. This is not required and can be edited from the 'Payment Terms' field on the 'Properties' tab of the Sales Transaction Record View.

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.

Linked Database Field: ERPx_SOOrderHeader.PaymentTermsSK

Identifies the actual cost of all items on the transaction. This field is not required. If the item is ordered, but not allocated, this field may be edited from the 'Actual Cost' field for the Item in the Item Master File. If the item is allocated, this field may be edited from the 'Actual Cost' assigned on the Inventory Lot.

The Product Cost Amt. represents the actual cost of the Product(s) sold. It is set one of two ways:

1. For Sales Inventory Items, on transactions, that have not been allocated (just ordered) this comes from the 'Actual Cost' assigned on the Item Master File. This allows for calculating an estimated product cost, gross margin, and net margin.
2. For Sales Inventory Items, on transactions, that have been allocated this comes from the 'Actual Cost' assigned on the Lot. This allows for a more accurate product cost, gross margin, and net margin.

Note: Until the Lots have been closed for Costing, the Product Cost Amounts are subject to change.  

Database Fields: ERPx_SOOrderItem.ItemActualCost, ERPx_IMLotCostHistory.Cost, ERPx_IMLotBalance.LotSK

Identifies the Purchase Order number (PO number) entered for the transaction or transaction line item. This is not required and can be edited from the 'Purchase Order' field on the 'Home' tab of the Sales Transaction Record View.

Database Field: ERPx_SOOrderHeader.PurchaseOrder

Identifies the amount being accrued from one or more Rebate programs. This displays the total 'Program Amt.' of all line items on the transaction that qualify for one or more related Rebate programs. This is not required. This is a calculated field and may be edited from the Sales Program Details Record View.

 This field uses the Ordered Ext Amount for transactions where the Status is less than "Shipped" and Allocated Ext Amount for transactions where the Status is "Shipped" or greater.

Database Field: ERPx_SPProgramSettlementItem.ComputedAmount

Identifies the name of the inside salesperson associated with the transaction. This is not required and can be edited from the 'Salesperson - Inside' field on the 'Properties' tab of the Sales Transaction Record View.

Inside Salespeople typically work in the office and are involved with sales over the telephone, email, or other cyber communication methods.

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

Identifies the name of the outside salesperson associated with the transaction. This is not required and can be edited from the 'Salesperson - Outside' field on the 'Properties' tab of the Sales Transaction Record View.

Outside Salespeople typically work outside the office and are involved with face to face meetings with active and prospective customers.

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

Displays the default date the order (or Shipment) is, or was, expected to be shipped, formatted from the users 'Date Format' preference. This is required and can be edited from the 'Ship By' field on the 'Home' tab of the Sales Transaction Record View. It comes from the 'Ship By' field on the 'Home' tab of the Sales Transaction Record View.

Database Field: ERPx_SOOrderHeader.ScheduledShipDate

Displays the destination City, State where the order will be shipped to. This not is required and comes from the 'City' and 'State' fields on the 'Properties' tab of the Customer Addresses Record View when the transaction was created. Once the transaction is created, this field is not editable.

The City identifies the value of 'City' in an address record. The State identifies the value of 'State' in an address record.

Database Fields: ERPx_ARCustomerAddress.City, ERPx_ARCustomerAddress.State, ERPx_SOOrderHeader.ShipCity, ERPx_SOOrderHeader.ShipState

Displays the Country the order will be shipped to. This is not required and comes from the 'Country' field on the 'Properties' tab of the Customer Addresses Record View when the transaction was created. Once the transaction is created, this field is not editable.

The Country identifies the 'Country' of an address record. 

Database Fields: ERPx_ARCustomerAddress.Country, ERPx_SOOrderHeader.ShipCountry

Displays the phone number at the address where the order will be shipped to. This is not required and comes from the 'Phone' field on the 'Properties' tab of the Customer Addresses Record View when the transaction was created. Once the transaction is created, this field is not editable.

Used to record the primary phone number associated with an address. This is informational only. 

Database Fields: ERPx_ARCustomerAddress.Phone1, ERPx_SOOrderHeader.ShipPhone1

Identifies the unique Site ID (warehouse ID) of the Site the transaction, shipment, item, or lot is associated with. This is required and can be edited from the 'Site' field on the 'Home' tab of the Sales Transactions Record View.

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

Database Fields: ERPx_MFSite.SiteID, ERPx_SOOrderHeader.SiteSK

Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. This is required and can be edited from the 'Site' field on the 'Home' tab of the Sales Transactions Record View.

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

Identifies the Status of the transaction. This is required and can be edited from the 'Status' on the 'Home' tab of the Sales Transaction Record View.

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

The unique identifier of the Transaction Class. This is required and comes from the 'Transaction Class' value selected by the user when the sales order or sales quote was created. It is not editable. 

Identifies the date of the transaction. It is formatted from the users 'Date Format' preference. This is required and can be edited from the 'Order Date' field on the 'Home' tab of the Sales Transaction Record View.

Database Field: ERPx_SOOrderHeader.OrderDate

Identifies the unique Transaction ID for each transaction. Clicking on the link opens the corresponding transaction record view.  This is required, is a system assigned value and is not 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

Identifies workflow step the transaction is in. This is not required. It can be edited from the 'Workflow' field on the 'Home' tab of the Sales Transaction Record View.

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.

Database Fields: ERPx_MFWorkflow.WorkflowName, ERPx_SOOrderHeader.WorkflowSK