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

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

• Quotes: Each unique Quote Class is displayed. When clicked, the Select Ship-To Record View opens allowing users to select the Customer / Customer Address associated with the quote.
• Order: Each unique Order Class is displayed. When clicked, the Select Ship-To Record View opens allowing users to select the Customer / Customer Address associated with the order.
  
• Return: Opens the Sales Return: Find an Invoice page for users to find a posted invoice and create a Return transaction.
• Price Adjustment: Opens the Price Adjustment: Find an Invoice page for users to find a posted invoice and create a Price Adjustment transaction.

 Saves all changes made on the page. 'Ord. Units', 'Ord, Weight', and 'Price' may be updated from this LV.

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

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

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

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

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

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

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

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

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

Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_SOOrderHeader.CurrencySK

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

Customer IDs are used as a short description and the unique identifier for Customers. They can be changed at any time to any alphanumeric value. If you do not have an existing strategy for Customer IDs the 3-3-2 method would be recommended.

Database Fields: ERPx_ARCustomer.CustomerID, ERPx_SOOrderHeader.CustomerSK

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

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

Database Fields: ERPx_ARCustomer.CustomerName, ERPx_SOOrderHeader.CustomerSK 

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

Database Fields:  ERPx_SOOrderHeader.ScheduledDeliveryDate, ERPx_LMLoadTransactionItem.DeliverOnDate

The Freight Amt. represents the freight/shipping cost of the Product(s) on a Sales Transaction. It is set one of two ways:

1. Manually by clicking on the Shipment hyperlink on the Shipment Tab and entering delivered freight amounts.
2. Automated from 'Accrual' Sales Programs where the 'Freight Accrual' property is set to "Yes".

The amounts entered are rolled down to the items based on total weight. 

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

Database Field: ERPx_SOOrderItem.FreightAccrualAmount

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

Database Field: ERPx_SOInvoiceHeader.GLDate

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

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

Identifies the profit amount, using only product costs, 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.]

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]

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

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

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

Identifies the type of item and its behavior in the system. Item Types fall under two main categories: 

1. Item Types that maintain perpetual inventory balances 
   1. Inventory
2. Item Types that do not maintain perpetual inventory balances
   1. AP Expense 
   2. Freight
   3. Misc
   4. Tax

Database Field: ERPx_IMItemType.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

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

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]

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

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

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

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

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:

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

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

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

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

Database Field: ERPx_SOOrderHeader.PurchaseOrder

Identifies the amount being accrued from one or more Rebate programs. This displays the total 'Program Amt.' 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

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

Salespeople are individuals that sell goods and services to other entities. Outside Salespeople typically work outside the office and are involved with face to face meetings with active and prospective customers.

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

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

Database Fields: ERPx_SOOrderItem.ScheduledShipDate, ERPx_LMLoadHeader.ScheduledShipDate

Displays the destination City and State the shipment containing the item. This not is required and comes from the 'City' and 'State' fields on the 'Properties' tab of the Customer Addresses Record View when the transaction was created. Once the transaction is created, this field is not editable.

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

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

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

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

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

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

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

Status is used to identify where a transaction, Purchase Order, Price List, BOM, or Master File record is in its life cycle. Records start in a Status of 'New' and progress sequentially through additional statuses until they are 'Posted' or 'Closed'. The list of potential Statuses changes depending on the transaction type.  The Statuses that apply to transactions in this List View include:

New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist.  

Released: This status is used to signify that the transaction is ready to be released to production. While in the Status of 'Released', all editable fields are open for edit.

Shipped: This status indicates the order has physically left the facility. This either manually updated or automatically updated if the order was shipped from a Site that has an integrated bar code system. Line Item edit for orders in this status is controlled by the Status Setup configuration.

Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned.

Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled with the exception any fields that are always editable and updates the Transaction Status to "Posted".

Database Fields: ERPx_SOOrderStatus.OrderStatusName, ERPx_SOOrderHeader.OrderStatusSK. ERPx_SOOrderItem.OrderStatusSK

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

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

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

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

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