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

• Logistics Attributes: All Logistics attributes configured in the Attributes Master File. Assigns the entered/selected value to selected/filtered transactions when Apply is clicked.
  
• 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.

 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 Bill of Lading associated with the shipment(s) on the order. This is not required and can be edited from the 'BOL' field on the 'Shipments' tab of the Sales Transaction Record View.

A 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

A Booking Number is the reservation number issued by a carrier or freight forwarder to shippers. This is not required and can be edited from the 'Booking #' field on the Export Details Record View.

Database Field: ERPx_LMLoadHeader.BookingNumber

Identifies the amount being accrued from one or more Brokerage programs. This field displays the 'Program Amt.' of all items on the shipment that qualify for the program. This field is not required. This field 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 Carrier Name of the first leg of the shipment. This is not required and can be edited from the 'Carrier' field on the 'Home' tab of the Sales Transaction Record View or the 'Carrier' field on Leg 1 on the Shipment Details Record View for a single shipment or the first shipment if multiple exist, else it can be edited from the 'Carrier' field on the 'Shipments' tab of the Record View for subsequent shipments. 

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

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 value comes from the Created Date & Time of the Order. 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 value comes from the Created Date & Time of the Order. This field is required.

Database Field: ERPx_SOOrderHeader.CreatedBy

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

Identifies the total freight amount for the shipment. This is a calculated field. It is calculated as [Freight Weight] x [Freight Rate] x ([Surcharge %] / 100) + [Other Charges] for all legs of the shipment. This can be edited by updating the 'Freight Rate', 'Surcharge %' or 'Other Charges' fields on the Shipment Details Record View.

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 Fields: ERPx_LMLoadHeader.TotalFreight, ERPx_LMLoadTransaction.FreightAmount

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.

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

Database Fields: ERPx_LMLoadHeader.SOFreightTermsEN, ERPx_LMLoadTransaction.SOFreightTermsEN

Identifies the date the transaction posted (or will post) to the general ledger. This is required for transactions saved with a 'Status' of "Approved" or "Ready to Post" and can be edited from the 'GL Date' field on the 'Shipments' tab of the Sales Transaction Record View.

Database Field: ERPx_SOInvoiceHeader.GLDate

Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. Identifies the fiscal period based on the GL Date on the shipment. This is required for the transaction to be saved in a status of 'Approved' or greater and can be edited from the 'GL Date' field on the 'Shipments' tab of the Sales Transaction Record View. This field is not stored in the database.

Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. Identifies the fiscal year based on the GL Date on the shipment. This is required for the transaction to be saved in a status of 'Approved' or greater and can be edited from the 'GL Date' field on the 'Shipments' tab of the Sales Transaction Record View. This field is not stored in the database.

Identifies the profit amount, using only product costs, of the Shipment. This field is not required and not stored in the database. This field 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, of the Shipment. This field is not required and not stored in the database. This field 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 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 system assigned value and is never editable by a user. This field is required.

Database Field: ERPx_LMLoadHeader.LastUpdated

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 system assigned value and is never editable by a user. This field is required.

Database Field: ERPx_LMLoadHeader.LastUser

Identifies the final profit amount of the Shipment. This field is not required and not stored in the database. This field 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 of the Shipment. This field is not required and not stored in the database. This field 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]

The Other Accruals represent the amount calculated from 'Accrual' Sales Programs where the 'Freight Accrual' property is set to "No". This field displays the total 'Program Amt.' of all items on the shipment that qualify for the program. This field is not required. This field 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 place the shipment was delivered to. This is not required and can be edited from the 'Place of Delivery' field in the header of the Export Details Record View.

Database Field: ERPx_LMLoadHeader.DeliveryPort

Identifies the date the shipment was delivered, formatted from the users 'Date Format' preference. This is not required and can be edited from the 'Place of Delivery / Date' field in the header of the Export Details Record View.

Database Field: ERPx_LMLoadHeader.DeliveryDate

Identifies the port the shipment was discharged from. This is not required and can be edited from the 'Port of Discharge' field in the header of the Export Details Record View.

Database Field: ERPx_LMLoadHeader.DischargePort

Identifies the date the shipment was discharged from the receiving port, formatted from the users 'Date Format' preference. This is not required and can be edited from the 'Port of Discharge / Date' field in the header of the Export Details Record View.

Database Field: ERPx_LMLoadHeader.DischargeDate

Identifies the port the shipment entered from. This is not required and can be edited from the 'Port of Entry' field in the header of the Export Details Record View.

Database Field: ERPx_LMLoadHeader.EntryPort

Identifies the date the shipment arrived at the receiving port, formatted from the users 'Date Format' preference. This is not required and can be edited from the 'Port of Entry / Date' field in the header of the Export Details Record View.

Database Field: ERPx_LMLoadHeader.EntryDate

Identifies the port where the shipment was loaded. This is not required and can be edited from the 'Port of Loading' field in the header of the Export Details Record View.

Database Field: ERPx_LMLoadHeader.LoadingPort

Identifies the date the shipment was loaded at the port, formatted from the users 'Date Format' preference. This is not required and can be edited from the 'Port of Loading / Date' field in the header of the Export Details Record View.

Database Field: ERPx_LMLoadHeader.LoadingDate

Identifies the actual cost of all items on the Shipment. 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. It 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 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.

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.

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.

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.

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.

Database Fields: ERPx_SOOrderItem.ScheduledShipDate, ERPx_LMLoadHeader.ScheduledShipDate

Displays the destination City and State the shipment containing the item. 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 shipment 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 shipment 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 Shipment ID for the shipment. Clicking on the link opens the corresponding Shipment Details Record View. The shipment ID is auto generated based on a combination of Carrier, Site and Ship By Date. This is required, is a system assigned value and is not editable.

Database Field: ERPx_LMLoadHeader.LoadID

Identifies the Site ID (warehouse ID) where the shipment will ship from. This is required and can be edited from the 'Site' field on the 'Home' tab of the Sales Transactions Record View for a single shipment or the first shipment if multiple exist, else it can be edited from the 'Site Name' field on the 'Shipments' tab of the Record View for subsequent shipments.

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

Identifies the name of the Site where the shipment will ship from. This is required and can be edited from the 'Site' field on the 'Home' tab of the Sales Transactions Record View for a single shipment or the first shipment if multiple exist, else it can be edited from the 'Site Name' field on the 'Shipments' tab of the Record View for subsequent shipments.

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

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

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

Identifies the unique Transaction ID containing the shipment. 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

Displays the name/ID of the Vessel carrying the shipment. This is not required can edited from the 'Vessel' field in the header of the Export Details Record View.

Database Field: ERPx_LMLoadHeader.Vessel