Sales Items List View
Sales items are the individual items on a sales transaction. The purpose of this page is to view line item on open (un-posted) sales transactions. This page can also be used to add new Sales Quotes, Orders, Price Adjustment and Return Transactions. Additionally, some fields can be updated directly from the list view including: Ord. Units, Ord, Weight, and Price.
This list view also contains columns for each Attribute that is set up for the 'Items', 'Logistics' 'Sales Order' and 'Sales Order Item' attribute types. Because these are user defined, they are not included in the default view but can be added a saved column layout. Item, Load Management (Logistics) Sales Order and Sales Order Item attributes are not included in the help documentation.
Software Version: 2023.11.30 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. |
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. |
New | 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:
|
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. |
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. |
Refresh | Re-queries the contents of the grid/page based on the Search Options or the default values for grids that do not support Search Options. This ONLY re-queries the contents of columns that are currently visible, if you add a new column the contents will be empty until you click 'Refresh' again. |
Save | Saves all changes made on the page. 'Ord. Units', 'Ord, Weight', and 'Price' may be updated from this LV. |
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. |
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 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 |
Amount | Identifies the Line Items allocated extended amount, formatted to 2 decimal places. This is a calculated field and can only be edited by changing the unit/weight allocations or by updating the 'Price' field of a line item on the Sales Transaction Record View. It is calculated as ([Allocated Quantity] * [Price]), where [Allocated Quantity] is the Allocated 'Units' when the 'Price UOM' is a Unit UOM and it is the Allocated 'Weight' when the 'Price UOM' is a Weight UOM. Database Field: ERPx_SOOrderItem.AllocatedAmount |
Amount - Ord. | Identifies the ordered extended amount of the line item. This is a calculated field and can be edited by changing the 'Ord. Units', 'Ord. Weight' or 'Price' fields of the line item 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 a Unit UOM, and 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 of the line item. 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 Fields: ERPx_SOOrderHeader.BOL, ERPx_LMLoadTransactionItem.BOL |
Brokerage Amt. | Identifies the amount being accrued from one or more Brokerage programs. This displays 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. 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 |
Carrier Name | Identifies the Carrier associated with the shipment of a line item. 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 of the associated shipment 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 |
Contract # | Identifies the sales contract the line item is associated with. This is not required and can be edited when applicable from the 'Contract' field on the Sales Transaction Record View grid. This field is editable while the transaction is in a Status less than 'Approved'. However, this field is always disabled on Sales Quote transactions. This is only editable 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. 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. Database Fields: ERPx_SCContractHeader.ContractID, ERPx_SOOrderItem.ContractHeaderSK |
Cost Amt. | 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 displays the total cost of all Lots associated with the line item. 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_SOOrderItem.ExtendedCostAmount |
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_MFCurrency.CurrencyID, ERPx_SOOrderHeader.CurrencySK |
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 order 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' field is in the future and a negative number when the 'Ship By' field is in the past. It 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 Fields: ERPx_SOOrderHeader.ScheduledDeliveryDate, ERPx_LMLoadTransactionItem.DeliverOnDate |
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:
The amounts entered are rolled down to the items based on total weight. This displays the total freight amount of the line item. This is not required. This can be edited by updating the 'Freight Rate', 'Surcharge %' or 'Other Charges' fields on the Shipment Details Record View or from the Sales Program Details Record View for the Freight Accrual Program.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_SOOrderItem.FreightAccrualAmount |
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. 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. 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, for the line item. 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.] |
Gross Margin Pct. | Identifies the percentage of profit, using only product costs, for the line item. 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] |
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 for the associated shipment on the 'Shipments' tab of the Sales Transaction Record View. Database Fields: ERPx_SOInvoiceHeader.InvoiceNumber, ERPx_LMLoadTransaction.InvoiceHeaderSK |
Invoice Item: Description | Identifies the Item ID and Sales Invoice Description. This is required and can be edited from the 'Item ID' and 'Sales Invoice Description' fields on the 'Properties' tab of the Item Record View. Item IDs are the unique identifier for Items. The Sales Invoice Description is used in companies that want a lot of detail in the Item Description but more of a "marketing" description used on Sales Invoices. Database Field: ERPx_SOOrderItem.ItemSalesInvoiceDescription |
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 |
Item Added | Identifies the date the item was added to the transaction, 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_SOOrderItem.CreatedDate |
Item Added By | Identifies the name of the user that added the item to 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_SOOrderItem.CreatedBy |
Item Attribute Class | Identifies the Attribute Class configured for the Item. This is not required and can be edited from the 'Item Attribute Class' field on the 'Properties' tab of the Item Record View. Attribute Classes are assigned to master files to control which Attributes are visible, and/or required, to records within the master file. Database Fields: ERPx_MFAttributeClass.ClassDescription, ERPx_IMItem.AttributeClassSK |
Item Class | Identifies the class that is assigned to the Item on the transaction or transaction line. This is required and can be edited from the 'Item Class' field on the 'Properties' tab of the Item Record View. Item Classes are used to identify default values that will be applied to new Inventory Items and to group Items together for reporting purposes. Database Field: ERPx_IMItem.ItemClass.Description |
Item Last Updated | Identifies the date the item on the transaction was last updated, 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_SOOrderItem.LastUpdated |
Item Last Updated By | Identifies the name of the user that last updated the item on 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_SOOrderItem.LastUser |
Item Type | Identifies the type of item and its behavior in the system. Item Types fall under two main categories:
Database Field: ERPx_IMItemType.Description |
Item: Description | Identifies the Item, displayed as Item ID: Item Description. This is required and can be edited from the 'Item ID' and 'Item Description' fields on the 'Properties' tab of the Item Record View. Item IDs are the unique identifier for Items. Database Fields: ERPx_IMItem.ItemID:ItemDescription, ERPx_SOOrderItem.OrderItemSK |
Net Margin Amt. | Identifies the final profit amount of the line item. 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.] |
Net Margin Pct. | Identifies the percentage of final profit of the line item. 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] |
On Hold | 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 Fields: ERPx_MFHoldCode.HoldCode, ERPx_SOOrderHeaderHold |
Other Accrual Amt. | 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.' for all the non-freight 'Accrual' 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. 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 the line item. This is a calculated field and can be edited by changing the unit allocation or 'Ord. Units' quantity for the line item. 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 the line item. This is a calculated field and can be edited by changing the weight allocation or 'Ord. Weight' quantity for the line item. It is calculated as [Allocated Weight] / [Ordered Weight] * 100. This field is not stored in the database. |
Price | Identifies the price of the line item. It is formatted to the Item's 'Price Decimals' and is required. It can be edited from the 'Price' column of the Sales Items List View while the transaction is in a status of New or Released. Else if the transaction is in a status of Shipped or greater, this field is disabled and is not editable. Database Field: ERPx_SOOrderItem.ItemPrice |
Price UOM | Displays the unit of measure upon which the line item price is based. It is required and can be edited from the 'Price UOM' field in the Items grid of the Sales Transaction Record View. A UOM is a quantity used as a standard of measurement. It identifies how much makes up "1" of the measurement. Examples include Bag, Box, Each, Kg, Lb, ext. Database Fields: ERPx_IMUOM.UOMName, ERPx_IMItem.DefaultSOPriceUOMSK |
Product Cost Amt. | Identifies the actual cost of the line item. 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:
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 |
Production Instructions | Displays the first 100 characters from the line item's 'Production Inst.' note type. This is not required and can be edited from the Notes Dialog Box for the associated line item. Database Field: ERPx_SOOrderItemNote.Note |
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 |
Rebate Amt. | Identifies the amount being accrued from one or more Rebate programs. This displays the total 'Program Amt.' for all the Rebate 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. 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 |
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: ARCustomerAddress.City, ERPx_ARCustomerAddress.State, ERPx_SOOrderHeader.ShipCity, ERPx_SOOrderHeader.ShipState |
Ship Country | Displays the Country the item's 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 item's 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 Shipment ID of the shipment containing the line item. This is required for the transaction to be saved in a status of 'Shipped' and greater. The shipment ID is auto generated based on a combination of Carrier, Site and Ship By Date and is not editable. Database Field: ERPx_LMLoadHeader.LoadID |
Shipment Status | Identifies the status of the shipment containing the line item. This is required only if a shipment exists. It can be edited from the 'Load Status' field on the 'Shipments' tab of the Sales Transaction Record View. Database Field: ERPx_LMLoadHeader.LoadStatusSK |
Shipped | Identifies the date the item's 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 |
Site | Identifies the unique Site ID (warehouse ID) of the Site the transaction, shipment, item, or lot is associated with. AKA, where the item 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 (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. AKA, where the item 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 |
Sub for Item | Identifies the Item ID the line item was substituted for. It is not required. It can be edited by clicking the Substitution button on the Sales Transaction Record View and adding substitution items for the ordered item on the Sales Order Item Substitution Record View. Database Field: ERPx_SOOrderItem.OriginTransactionItemSK |
Sub. Item | Identifies if the line item has a substitute item on the same transaction. This is not required and can be edited by clicking the Substitution button on the Sales Transaction Record View and adding substitution items for the ordered item on the Sales Order Item Substitution Record View. This field is not stored in the database. |
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 associated with the line item. 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 Line Items allocated 'Units', formatted to 2 decimal places. This is a calculated field and can only be edited by changing the quantity of allocated 'Units' on one or more line items on the Sales Transaction Record View. Database Field: ERPx_SOOrderItem.AllocatedUnits |
Units - Ord. | Identifies the 'Ordered Units' for the line item, formatted to the Item's 'Unit Decimals'. This is not required and can be edited by changing the 'Ord. Units' column of the Sales Items List View based on the settings in the /wiki/spaces/HELP/pages/1081622 master file. This field is disabled if an item's 'Manage Items By' property is "Weight Only". Database Field: ERPx_SOOrderItem.OrderedUnits |
Units UOM | Identifies the unit of measure that the units are stored in (Box, Bag, Case, Each, Tote, etc.) for a line item or on the transaction. This is required if the item is managed by 'Units and Weight' or by 'Units Only'. It can be edited from the 'Units UOM' field in the Items grid on the Sales Transaction Record View. A UOM is a quantity used as a standard of measurement. It identifies how much makes up "1" of the measurement. Examples include Bag, Box, Each, Kg, Lb, ext. Database Fields: ERPx_IMUOM.UOMName, ERPx_SOOrderItem.UnitUOMSK |
Weight | Identifies the Line Items allocated 'Weight', formatted to 2 decimal places. This is a calculated field and can only be edited by changing the quantity of allocated 'Weight' on one or more line items on the Sales Transaction Record View. Database Field: ERPx_SOOrderItem.AllocatedWeight |
Weight - Ord. | Identifies the 'Ordered Weight' for the line item, formatted to the Item's 'Unit Decimals'. This is not required and can be edited by changing the 'Ord. Weight' column of the Sales Items List View based on the settings in the /wiki/spaces/HELP/pages/1081622 master file. If the item's 'Allow Variable Ordered Qty' property is set to "Yes", then this field can be edited by changing the 'Ord. Weight' of the line item based on the settings in the /wiki/spaces/HELP/pages/1081622 master file. This field is disabled if an item's 'Manage Items By' property is "Units Only". Database Field: ERPx_SOOrderItem.OrderedWeight |
Weight UOM | Identifies the unit of measure that the weight is stored in (Lbs, Kg, Oz, Ton, etc.) for a line item or on the transaction. This is required if the item is managed by 'Units and Weight' or by 'Weight Only'. It can be edited from the 'Weight UOM' field in the Items grid on the Sales Transaction Record View. A UOM is a quantity used as a standard of measurement. It identifies how much makes up "1" of the measurement. Examples include Bag, Box, Each, Kg, Lb, ext. Database Fields: ERPx_IMUOM.UOMName, ERPx_SOOrderItem.WeightUOMSK |
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. |