ADD DEFINITION HERE. The purpose of this page is to view line item details associated with sales transactions. Users may also use this page to add new Sales Quotes, Orders, Price Adjustment and Return Transactions. Additionally, users can manually update ordered unit quantity, ordered weight and/or price of a line item directly from this List View.
This list view also contains columns for each Attribute that is set up for the 'Items', '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, Sales Order and Sales Order Item attributes are not included in the help documentation.
Software Version: 2020.xx.xx and newer
Page Header
Search
Search Options | Description |
|---|---|
| Date Range | |
| Carrier | |
| Include | |
| Item Class | |
| Search | A non-required text box that defaults to blank and is used to search across multiple fields. When the page is 'Refreshed', the data returned will be limited by what was included in the Search box (in addition to any other Search Options). Refer to this FAQ for advanced search options. The Search field can be used to search across the following fields: |
| Site | Used to select one or more Sites. This is a multi-select standard lookup that is not required to return results. It defaults as blank. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain inventory balances. The lookup contains a list of all active Sites. |
| Saved Search Options | Displays the saved search options lookup and related icons. This tool allows users to select previously saved search options, create a new set of search options, save changes to existing search options, forget/delete saved search options and/or assign a saved search option as the default for the page. Once changes are made to the search options, the user can click the Save Options icon and save the changes. The new search option can also be set as the default. |
| Transaction Class |
Page Detail
| 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.
|
| 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. |
| Journal Details | |
| Quick Filter | Error rendering macro 'excerpt-include' : No link could be created for 'Quick Filter'. |
| Refresh | |
| Saved Column 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 |
| % 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. |
| % 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. |
Address | 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 Order 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 Order Record View. Database Fields: ERPx_ARCustomerAddress.AddressName, ERPx_SOOrderHeader.AddressSK |
| Alloc Amount | Identifies the allocated extended amount of the line item, formatted to the Item's 'Price Decimals' of 2 decimals??? (the mockup doesnt specify the number of decimals, but if the 'Price Decimals' is set to 5, we wouldn't want to lose precision). 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 on the Sales Order Record View. It is calculated as [Allocated Quantity] * [Price], where [Allocated Quantity] is the Allocated Units if the 'Default Price UOM' for the item is units based and Allocated Weight if the 'Default Price UOM' for the item is weight based. Database Field: ERPx_SOOrderItem.AllocatedAmount |
| Alloc Units | Identifies the number of allocated units for the line item, formatted to the Item's 'Unit Decimals'. This is a calculated field and can be edited by changing the unit allocation of the line item. Database Field: ERPx_SOOrderItem.AllocatedUnits |
| Alloc Weight | Identifies the allocated weight for the line item, formatted to the Item's 'Weight Decimals'. This is a calculated field and can be edited by changing the weight allocation of the line item. Database Field: ERPx_SOOrderItem.AllocatedWeight |
| Attention To | Identifies the name person receiving the order at the Ship To Address. This is not required and can be edited from ...... There is no field on the customer address record to add/edit this field - should it be added or should the field be removed/updated? Database Fields: ERPx_ARCustomerAddress.AttentionTo, ERPx_SOOrderHeader.ShipAttentionTo |
| 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 |
| 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 Order 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 |
| 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 for a line item in the item's grid of the Sales Order Record View. Carriers represent entities that transport goods from one location to another. They can be actual freight companies (i.e. UPS or Fed Ex) and/or they can represent a delivery method (i.e. Our Truck, Customer Pickup, Transfer in Storage, or UPS-Air). They are used on Inventory transfers and sales order shipments. Database Fields: ERPx_SOCarrier.CarrierName, ERPx_SOOrderItem.CarrierSK |
| Checkbox | Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete. |
| Created By | Identifies the name of the user that created the item. 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 |
| Created Date | Identifies the date the item was created, 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 |
| Created Time | Identifies the time the item was created, formatted in 'HH:MM:SS'. This is a system assigned value and is never editable by a user. This field is required. Database Field: ERPx_SOOrderItem.CreatedDate |
| Currency | Identifies the Currency assigned to the transaction. This is required and comes from the 'Currency' field in the 'Home' tab of the Sales Order 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 | 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 Order 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 Order 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 shipped. This is a calculated field that can be either positive or negative. It is calculated as [Default Ship By] - [Current Date]. It is a positive number when the 'Default Shipped By' field is in the future and a negative number when the 'Default Shipped By' field is in the past. This is required and can be edited from the 'Default Ship By' field on the 'Home' tab of the Sales Order Record View. This field is not stored in the database. |
| GL Date | Identifies the date the transaction posted (or will post) to the general ledger. This field is required for the transaction to be saved in a status of 'Approved' and greater and can be edited from the 'GL Date' field on the 'Shipments' tab of the Sales Order Record View. If the GL Date is missing, this comes from the 'Shipped' field on the 'Shipments' tab of the Sales Order Record View. Else if the 'Shipped' field is blank, this comes from the 'Ship By' field on the 'Shipments' tab of the Sales Order Record View. If all else fails, this comes from the 'Order Date' field on the 'Home' tab of the Sales Order Record View. If the 'Single Date Management' property on the associated transaction class is set to "Yes", then this field will default from the 'Order Date' field on the 'Home' tab of the Sales Order Record View. Check the how the system works currently and leave as highlighted. Database Field: ERPx_SOInvoiceHeader.GLDate |
| GL Period | 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 Order Record View. |
| GL Year | 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 Order Record View. |
| Inside Salesperson Name | Identifies the name of the inside salesperson associated with the transaction. This is not required and can be edited from the 'Salesperson - Inside Sales' field on the 'Properties' tab of the Sales Order 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 |
| 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 Order 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. 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 Order Record View. Database Field: ERPx_SOInvoiceHeader.InvoiceDate |
| 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 Type | Error rendering macro 'excerpt-include' : No link could be created for 'Item Type'. This is required. This field is not editable once the item has been created.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. Database Field: ERPx_IMItem.ItemDescription |
| Last Updated By | Identifies the name of the user that last updated the item. 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 |
| Last Updated Date | Identifies the date the item 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 |
| Last Updated Time | Identifies the time the item was last updated, formatted in 'HH:MM:SS'. This is a system assigned value and is never editable by a user. This field is required. Database Field: ERPx_SOOrderItem.LastUpdated |
| Ord Amount | Identifies the ordered extended amount of the line item, formatted to the Item's 'Price Decimals' of 2 decimals??? (the mockup doesnt specify the number of decimals, but if the 'Price Decimals' is set to 5, we wouldn't want to lose precision). This is a calculated field and can be edited by changing the 'Ord. Units', 'Ord. Weight' or 'Price' fields of a line item on the Sales Order Record View. It is calculated as [Ordered Quantity] * [Price], where [Ordered Quantity] is the Ordered Units if the 'Default Price UOM' for the item is units based and Ordered Weight if the 'Default Price UOM' for the item is weight based. Database Field: ERPx_SOOrderItem.OrderedAmount |
| Ord Units | Identifies the number of ordered units for the line item, formatted to the Item's 'Unit Decimals'. This is a calculated field and can be edited by changing the 'Ord. Units' field for a line item on the Sales Order Record View. Database Field: ERPx_SOOrderItem.OrderedUnits |
| Ord Weight | Identifies the ordered weight for the line item, formatted to the Item's 'Weight Decimals'. This is a calculated field and can be edited by changing the 'Ord. Weight' field for a line item on the Sales Order Record View. Database Field: ERPx_SOOrderItem.OrderedWeight |
| Outside Salesperson Name | Identifies the name of the outside salesperson associated with the transaction. This is not required and can be edited from the 'Salesperson - Outside Sales' field on the 'Properties' tab of the Sales Order 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 |
| 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' filed in the Items grid of the Sales Order 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 |
| Production Inst | 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 Order 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 |
| Ship City/State | Displays the destination City & State the item's shipment. This not is required and can be edited from the 'City' and 'State' fields on the 'Properties' tab of the Customer Addresses Record View. It comes from the 'Ship To' field on the 'Home' tab of the Sales Order Record View. 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 can be edited from the 'Country' 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 Order Record View. 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 the item's shipment be shipped to. This is not required and can be edited from the 'Phone' 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 Order Record View. 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 for the line item. Clicking on the link opens the Shipment Record View. 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 cannot be edited. Database Field: ERPx_LMLoadHeader.LoadID |
| 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 'Shipped' field on the 'Shipments' tab of the Sales Order Record View. Database Fields: ERPx_LMLoadHeader.ActualShipDate, ERPx_SOOrderHeader.ActualShipDate |
| Site | Identifies the Site ID (warehouse ID) where the item will ship from. This is required and can be edited from the 'Site ID' field on the 'Properties' tab of the Site Record View. It comes from the 'Site' field on the 'Shipments' tab of the Sales Order Record View. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. Database Fields: ERPx_MFSite.SiteID, ERPx_LMLoadHeader.SiteSk |
| Site Name | Identifies the name of the Site where the item will ship from. This is required and can be edited from the 'Site Name' field on the 'Properties' tab of the Site Record View. It comes from the 'Site' field on the 'Shipments' tab of the Sales Order Record View. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. Database Fields: ERPx_MFSite.SiteName, ERPx_LMLoadHeader.SiteSk |
| 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 Order 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 Order 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 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 Order Record View. Database Field: ERPx_SOOrderHeader.OrderDate |
| 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. Transaction numbers are system assigned IDs to differentiate unique transactions. Transaction ID's are unique by the unique combination of 'Transaction Type' + 'Transaction Class'. Database Field: ERPx_SOOrderHeader.OrderID |
| Transaction 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 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_SOOrderType.DocumentID |
| Transaction 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_ARTransactionType.TransactionName |
| Unit to Weight Conversion | Identifies the conversion rate from the Units UOM to the Weight UOM for the line item. This is required and can be edited from the 'Multiply By' field on the 'Conversions' tab of the associated UOM schedule. Database Field: ERPx_IMUOMConversion.ConversionValue |
| 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 Order 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 to Unit Conversion | Identifies the conversion rate from the Weight UOM to the Units UOM for the line item. This is required and can be edited from the 'Multiply By' field on the 'Conversions' tab of the associated UOM schedule. Database Field: ERPx_IMUOMConversion.ConversionValue |
| 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 Order 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 |