Identifies the ID of the Address for the associated Account. This comes from the 'Ship To' field on the 'Home' tab of the Sales Transaction Record View. It can be edited from the 'Address ID' field on the 'Properties' tab of the Customer Addresses 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 ID of the Address for the associated Account. This comes from the 'Ship To' field on the 'Home' tab of the Sales Transaction Record View. It can be edited from the 'Address Name' field on the 'Properties' tab of the Customer Addresses Record View.

Database Fields: ERPx_ARCustomerAddress.AddressName, ERPh_SOOrderHeader.AddressSK

Identifies the Bill of Lading associated with the shipment of the line item. This comes from the 'BOL' field on the 'Shipments' tab of the Sales Transaction Record View. It is not editable. 

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: ERPh_SOOrderHeader.BOL, ERPh_LMLoadTransactionItem.BOL

Identifies the amount being accrued from one or more Brokerage programs. This field displays the 'Program Amt.' of the line item that qualifies for the program. This field is not required. This field is a calculated field and may be edited from the Sales Program Details Record View.

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

Database Field: ERPx_SPProgramSettlementItem.ComputedAmount

Identifies the Carrier associated with the shipment of a line item. This comes from the 'Carrier' field of the associated shipment on the 'Shipments' tab of the Sales Transaction Record View. It is not editable. 

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, ERPh_SOOrderItem.CarrierSK

Identifies the Created Date & Time of the record, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user.

Database Field: ERPx_SOOrderHeader.CreatedDate

Identifies the name of the user that created the record. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. 

Database Field: ERPx_SOOrderHeader.CreatedBy

Identifies the Currency assigned to the transaction. This comes from the 'Currency' associated with the Customer on the transaction. 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, ERPh_SOOrderHeader.CurrencySK

Displays the unique identifier for the Customer record or for the Customer assigned to a transaction. This comes from the 'Ship To' field on the 'Home' tab of the Sales Transaction Record View. It can be edited from the 'Customer ID' field on the 'Properties' tab of the Customer 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, ERPh_SOOrderHeader.CustomerSK

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

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

Database Fields: ERPx_ARCustomer.CustomerName, ERPh_SOOrderHeader.CustomerSK 

Identifies the freight amount for the line item on the transaction. This field is not required. This can be edited by updating the 'Freight Rate', 'Surcharge %' or 'Other Charges' fields on the Shipment Details Record View. This is a calculated field and not stored in the database.

 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.

Identifies the date the transaction posted (or will post) to the general ledger.  This comes from the 'GL Date' field on the 'Shipments' tab of the Sales Transaction Record View. It is not editable. 

Database Field: ERPh_SOInvoiceHeader.GLDate

Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This comes from the 'GL Date' field on the 'Shipments' tab of the Sales Transaction Record View. This field is not stored in the database. It is not editable. 

Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This comes from the 'GL Date' field on the 'Shipments' tab of the Sales Transaction Record View. This field is not stored in the database. It is not editable. 

Identifies the profit amount, using only product costs, for the line item. This field is not required and not stored in the database. This field may be edited by editing any of the fields used in calculating this amount.

The Gross Margin Amt. is a calculated field that identifies the profit amount just factoring in product costs. Whereas the Net Margin Amount is used to show the final profit amount that also includes Freight, Brokerage, Rebates, and Other Accrued expenses, the Gross Margin Amt. only includes Product Costs. It is calculated as:

[Ext. Amount] - [Product Cost Amt.]

Identifies the percentage of profit, using only product costs, for the line item. This field is not required and not stored in the database. This field may be edited by editing any of the fields used in calculating this amount.

Gross Margin % is a calculated field that identifies the Gross Margin % for the Transaction, Item, or Lot. It is calculated as:

[Gross Margin Amt.] / [Amount]

Identifies the invoice number associated with the sales order shipment. This comes from the 'Invoice #' field for the associated shipment on the 'Shipments' tab of the Sales Transaction Record View. It is not editable. 

Database Fields: ERPh_SOInvoiceHeader.InvoiceNumber, ERPh_LMLoadTransaction.InvoiceHeaderSK

Identifies the Item ID and Sales Invoice Description. This comes from the 'Item ID' and 'Sales Invoice Description' fields on the 'Properties' tab of the Item Record View. It is not editable. 

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: ERPh_SOOrderItem.ItemSalesInvoiceDescription

Identifies the Attribute Class configured for the Item. This comes from the 'Item Attribute Class' field on the 'Properties' tab of the Item Record View. It is not editable. 

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

Identifies the class that is assigned to the Item on the transaction or transaction line. This comes from the 'Item Class' field on the 'Properties' tab of the Item Record View. It is not editable. 

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 comes from the 'Item ID' and 'Item Description' fields on the 'Properties' tab of the Item Record View. It is not editable. 

Item IDs are the unique identifier for Items. 

Database Fields: ERPx_IMItem.ItemID:ItemDescription, ERPh_SOOrderItem.OrderItemSK

Identifies the Last Updated Date & Time of the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user.

Database Field: ERPx_SOOrderHeader.LastUpdated

Identifies the final profit amount for the line item. This field is not required and not stored in the database. This field may be edited by editing any of the fields used in calculating this amount.

The Net Margin Amt. is a calculated field that identifies the final profit amount. Whereas the Gross Margin Amount is used to show the difference between the sales revenue and the Product Cost, the Net Margin Amount also includes Freight, Brokerage, Rebate, and Other Accrued expenses. It is calculated as:

[Gross Margin Amt.] - [Freight Amt.] - [Brokerage Amt.] - [Rebate Amt.] - [Other Accrual Amt.]

The Other Accruals represent the amount calculated from 'Accrual' Sales Programs where the 'Freight Accrual' property is set to "No". This field displays the 'Program Amt.' of the line item that qualifies for the program. This field is not required. This field is a calculated field and may be edited from the Sales Program Details Record View.

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

Database Field: ERPx_SPProgramSettlementItem.ComputedAmount

Identifies the price of the line item. It is formatted to the Item's 'Price Decimals'. It comes from the 'Price' column of the Sales Items List View or the 'Price' field in the Items grid on the Sales Transaction Record View. It is never editable.

Database Field: ERPh_SOOrderItem.ItemPrice

Displays the unit of measure upon which the line item price is based. It comes from the 'Price UOM' field in the Items grid of the Sales Transaction Record View. It is never editable.

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.UnitsUOMSK, ERPx_SOOrderItem.WeightUOMSK, ERPh_SOOrderItem.UnitsUOMSK, ERPh_SOOrderItem.WeightUOMSK

Identifies the actual cost of the line item. 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: ERPh_SOOrderItem.OrderItemActualCost, ERPx_IMLotCostHistory.Cost, ERPx_IMLotBalance.LotSK

Identifies the Purchase Order number (PO number) entered for the transaction or transaction line item. This comes from the 'Purchase Order' field on the 'Home' tab of the Sales Transaction Record View. It is not editable. 

Database Field: ERPh_SOOrderHeader.PurchaseOrder

Identifies the name of the inside salesperson associated with the transaction. This comes from the 'Salesperson - Inside' field on the 'Properties' tab of the Sales Transaction Record View. It is not editable. 

Salespeople are individuals that sell goods and services to other entities. Inside Salespeople typically work in the office and are involved with sales over the telephone, email, or other cyber communication methods.

Database Fields: ERPx_SPSalesperson.Salespersonname where SalespersonTypeEN = 2, ERPx_SOOrderHeader.InsideSalespersonSK

Identifies the name of the outside salesperson associated with the transaction. This comes from the 'Salesperson - Outside' field on the 'Properties' tab of the Sales Transaction Record View. It is not editable. 

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 destination City and State the shipment containing the item. This 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 posted, 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, ERPh_SOOrderHeader.ShipCity, ERPh_SOOrderHeader.ShipState

Displays the Country the item's shipment will be shipped to. This comes from the 'Country' field on the 'Properties' tab of the Customer Addresses Record View when the transaction was created. Once the transaction is posted, this field is not editable.

The Country identifies the 'Country' of an address record.

Database Fields: ERPx_ARCustomerAddress.Country, ERPh_SOOrderHeader.ShipCountry

Displays the phone number at the address where item's shipment will be shipped to. This comes from the 'Phone' field on the 'Properties' tab of the Customer Addresses Record View when the transaction was created. Once the transaction is posted, 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, ERPh_SOOrderHeader.ShipPhone1

Identifies the Site ID where the item will ship from. This comes from the 'Site' field on the 'Shipments' tab of the Sales Transaction Record View. It is not editable. 

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, ERPh_LMLoadHeader.SiteSk

Identifies the name of the Site where the item will ship from. This comes from the 'Site' field on the 'Shipments' tab of the Sales Transaction Record View. It is not editable. 

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, ERPh_LMLoadHeader.SiteSk

Identifies the Status of the transaction. This comes from the 'Status' on the 'Home' tab of the Sales Transaction Record View. It is not editable. 

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 Inquiry include:

Posted: Signifies the transaction has been posted and/or applied to a transactions (e.g. Payment Receipt). When a transaction is posted, it updates the General Ledger and/or On Hand Item Balances. While in the Status of 'Posted' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable.

Void: Signifies a previously posted transaction has been voided. This status is only available for transactions that support voiding posted records (not all transactions support this). Voided transactions remain in the database and can be viewed from history inquiries.

Database Fields: ERPx_SOOrderStatus.OrderStatusName, ERPh_SOOrderHeader.OrderStatusSK

The unique identifier of the Transaction Class. This comes from the 'Transaction Class' value selected by the user when the transaction was created. It is not editable. 

Identifies the date of the transaction. It is formatted from the users 'Date Format' preference. This comes from the 'Order Date' field on the 'Home' tab of the Sales Transaction Record View. It is not editable. 

Database Field: ERPh_SOOrderHeader.OrderDate

Identifies the Transaction Type for each transaction. This 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

Identifies the unique Transaction ID associated with the line item. This 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: ERPh_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 comes from the 'Units UOM' field in the Items grid on the Sales Transaction Record View. It is not editable. 

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, ERPh_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 comes from the 'Weight UOM' field in the Items grid on the Sales Transaction Record View. It is not editable. 

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, ERPh_SOOrderItem.WeightUOMSK