Shipments are used to describe the unique delivery of product on a Sales Order, Sales Return, or Inventory Transfer. A Shipment contains one or more Freight Legs and describes the Items that were/are to be delivered by a single Carrier, on a single Date, and most often (but not always) shipped from the same Site. The purpose of this page is to view Sales Order Shipments for un-posted sales transactions. From here users can open sales transactions or jump directly to the Shipment Details, Load details, and/or Export Details. Users can also use the Mass Update to set Load and/or Sales Order Attributes.

This list view also contains columns for each Attribute that is set up for the 'Sales Order' and 'Logistics' attribute types. Because these are user defined, they are not included in the default view but can be added a saved column layout. Sales Order and Load Management (Logistics) attributes are not included in the help documentation.

Software Version: 2023.10.31 and newer

Page Header

Toolbar Icons	Description
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 grid 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, or excluded columns, only the contents in the grid will be exported.
Export Details	Opens the Export Details Record View to view and enter additional information regarding the shipment container.
Favorites	Clicking on the star icon when it is an outline, adds the page to the 'My Shortcuts' tab and fills in the star. Clicking on the star icon when it is filled in (solid color), removes the page from the 'My Shortcuts' tab and returns the icon to an outline. Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.
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.
Mass Update	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.
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. 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.
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.
Fields	Description
Checkbox	Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
# Legs	Identifies the number of legs associated with the shipment. This is required and can be edited by adding a new leg on the Shipment Details Record View. Database Field: ERPx_LMLoadTransaction.CountofLegs
Address ID	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. 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
Address Name	Identifies the ID of the Address 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
Amount	Identifies the total allocated extended amount for all line items on the shipment, formatted to 2 decimals. This is a calculated field and can be edited by changing the unit/weight allocations or by updating the 'Price' field of a line item associated with the shipment on the Sales Transaction Record View. It is calculated as [Allocated Quantity] * [Price], where [Allocated Quantity] is the Allocated Units if the 'Price UOM' for the item is is a Unit UOM and is the Allocated Weight if the 'Price UOM' for the item is a Weight UOM. Database Field: ERPx_SOOrderItem.AllocatedAmount
Amount - Ord.	Identifies the total ordered extended amount for all line items on the shipment, formatted to 2 decimals. This is a calculated field and can be edited by changing the unit/weight Ordered Quantities or by updating the 'Price' of a line item associated with the shipment on the Sales Transaction Record View. It is calculated as [Ordered Quantity] * [Price], where [Ordered Quantity] is the Ordered Units if the 'Price UOM' for the item is is a Unit UOM and is the Ordered Weight if the 'Price UOM' for the item is a Weight UOM. Database Field: ERPx_SOOrderItem.OrderedAmount
Attention To	Identifies the value from the 'Attention To' field. This field is only available for systems that get the Customer Address from a host system. This is not required and can be edited by clicking the 'More Actions' button and choosing 'Change Address' on the 'Home' tab of the Sales Transaction Record View while the transaction is in a status less than Approved. Database Fields: ERPx_ARCustomerAddress.AttentionTo, ERPx_SOOrderHeader.ShipAttentionTo
BOL	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
Booking #	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
Brokerage Amt.	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
Carrier Name	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
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 value comes from the Created Date & Time of the Order. This field is required. Database Field: ERPx_SOOrderHeader.CreatedDate
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 value comes from the Created Date & Time of the Order. This field is required. Database Field: ERPx_SOOrderHeader.CreatedBy
Currency	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_ARCustomer.CustomerID, ERPx_SOOrderHeader.CustomerSK
Customer ID	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
Customer Name	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
Days Out	Identifies the number of days before the Shipment is to be shipped. This is a calculated field that can be either positive or negative. It is calculated as [Ship By Date] - [Current Date]. It is a positive number when the 'Ship By' is in the future and a negative number when the 'Ship By' is in the past. This is required and can be edited from the 'Ship By' field on the 'Shipments' tab of the Sales Transaction Record View. This field is not stored in the database.
Deliver On	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
Forwarder	Displays the name/ID of the forwarder that corresponds to the shipment. This is not required and can be edited from the 'Forwarder' field on the Export Details Record View. A Freight Forwarder is a person or firm that arranges to pick up or deliver goods on instructions of a shipper or a consignee, from or to a point by various necessary conveyances and common carriers. Database Field: ERPx_LMLoadHeader.Forwarder
Freight Amt.	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: Manually by clicking on the Shipment hyperlink on the Shipment Tab and entering delivered freight amounts. 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
Freight Terms	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
GL Date	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
GL Period	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.
GL Year	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.
Gross Margin Amt.	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.]
Gross Margin Pct.	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]
Invoice	Identifies the invoice number associated with the sales order shipment. This is required for the transaction to be saved in a status of 'Shipped' and greater. It can be edited from the 'Invoice #' field on the 'Shipments' tab of the Sales Transaction Record View. Database Field: ERPx_SOInvoiceHeader.InvoiceNumber
Invoiced	Identifies the date the shipment was invoiced, formatted from the users 'Date Format' preference. This is required for the transaction to be saved in a status of 'Shipped' and greater. It can be edited from the 'Invoiced' field on the 'Shipments' tab of the Sales Transaction Record View. Database Field: ERPx_SOInvoiceHeader.InvoiceDate
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 system assigned value and is never editable by a user. This field is required. Database Field: ERPx_LMLoadHeader.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 system assigned value and is never editable by a user. This field is required. Database Field: ERPx_LMLoadHeader.LastUser
Net Margin Amt.	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.]
Net Margin Pct.	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]
Other Accrual Amt.	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
Pct. Filled Units	Identifies the percentage of allocated units versus ordered units for all line items that make up the shipment. This is a calculated field and can be edited by changing the unit allocation or 'Ord. Units' quantity for a line item on the shipment. It is calculated as [Allocated Unit Quantity] / [Ordered Unit Quantity] * 100. This field is not stored in the database.
Pct. Filled Weight	Identifies the percentage of allocated weight versus ordered weight for all line items that make up the shipment. This is a calculated field and can be edited by changing the weight allocation or 'Ord. Weight' quantity for a line item on the shipment. It is calculated as [Allocated Weight] / [Ordered Weight] * 100. This field is not stored in the database.
Place of Delivery	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
Place of Delivery Date	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
Port of Discharge	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
Port of Discharge Date	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
Port of Entry	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
Port of Entry Date	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
Port of Loading	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
Port of Loading Date	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
Product Cost Amt.	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: 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. 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
Purchase Order	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. 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
Salesperson - Inside	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
Salesperson - Outside	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
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 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
Ship City/State	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
Ship Country	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
Ship Phone	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
Shipment	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
Shipment Status	Identifies the status of the shipment. This is required and comes from the 'Load Status' field on the 'Shipments' tab of the Sales Transaction Record View. This field displays 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 field is required for the transaction to be saved in a status of 'Shipped' or greater. It can be edited from the 'Actual Ship' field on the 'Home' tab of the Sales Transaction Record View. Database Fields: ERPx_LMLoadHeader.ActualShipDate, ERPx_SOOrderHeader.ActualShipDate
Shipping Line	Displays the name/ID of the business that transports the products aboard the ship. This is not required and can be edited from the 'Shipping Line' field on the Export Details Record View. Database Field: ERPx_LMLoadHeader.ShippingLine
Site	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
Site Name	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
Status	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
Tracking #	Identifies the tracking number associated with the shipment(s) on the order. This is not required and can be edited from the 'Tracking #' field on the 'Shipments' tab of the Sales Transaction Record View. Database Field: ERPx_LMLoadTransaction.TrackingNumber
Trans Class	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. Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each. Database Field: ERPx_SOOrderTypeDocument.DocumentID
Trans Date	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
Trans Type	Identifies the Transaction Type for each transaction. This is required. It is a system assigned value and is not editable. The transaction types are: Quote, Order, Return and Price Adjustment. 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 Field: ERPx_SOOrderType.OrderTypeName
Transaction	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
Units	Identifies the total number of allocated units for all line items on the shipment, formatted to 2 decimal places. This is a calculated field and can be edited by changing the unit allocation of one or more line items associated with the shipment. Database Field: ERPx_SOOrderItem.AllocatedUnits
Units - Ord.	Identifies the total number of ordered units for all line items on the shipment, formatted to 2 decimal places. This is a calculated field and can be edited by changing the 'Ord. Units' of one or more line items associated with the shipment. Database Field: ERPx_SOOrderItem.OrderedUnits
Vessel	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
Vessel Number	Displays the Vessel Number of the Vessel carrying the shipment. This is not required and can edited from the 'Vessel Number' field in the header of the Export Details Record View. Database Field: ERPx_LMLoadHeader.VesselNumber
Weight	Identifies the total allocated weight for all line items on the shipment, formatted to 2 decimal places. This is a calculated field and can be edited by changing the weight allocation of one or more line items associated with the shipment. Database Field: ERPx_SOOrderItem.AllocatedWeight
Weight - Ord.	Identifies the total ordered weight for all line items on the shipment, formatted to 2 decimal places. This is a calculated field and can be edited by changing the 'Ord. Weight' of one or more line items associated with the shipment. Database Field: ERPx_SOOrderItem.OrderedWeight
Workflow Name	Identifies workflow step the transaction is in. This is not required. It an 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_SOOrderType.WorkflowSK

Page Header

Related Topics

Page Definitions

Technical Details