Identifies the GL Account that will be Credited on a sale or Debited on a sales return. This required and can be edited from the 'Sale Account' field in the Items grid of the Quick Sale record view while in a Status of 'New'.

The GL Account that is assigned for the "Sales" Account Type, on the Accounts tab of the Item Record View and Item Class Record View. The Sale Account identifies the revenue account that sale transactions post to. 

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_ARTransactionLine.AccountSK

Identifies the Description associated with the GL Account assigned to a transaction line, journal entry line, or master file record. This required and can be edited from the 'Sale Account' field in the Items grid of the Quick Sale record view while in a Status of 'New'.

Database Fields: ERPx_GLAccount.Description, ERPx_ARTransactionLine.AccountSK

Identifies the Currency assigned to the transaction. This is required and comes from the 'Currency' property on the Properties tab of the Customer record view. This field is can not be edited on the transaction.

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_ARTransactionHeader.CurrencySK

Identifies the GL Account that will be Debited on a sale or Credited on a sales return. This is required and comes from the 'Accounts Receivable' field on the Accounts tab of the Customer record view. This field is can not be edited on the transaction.

The GL Account that is assigned for the "Accounts Receivable" Account Type, on the Accounts tab of the Customer Record View and Customer Class Record View. This is the account where accounts receivable amounts are posted for the selected customer. 

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_ARCustomer.GLARAccountSK

Identifies the Description associated with the GL Account assigned to a transaction line, journal entry line, or master file record.  This is required and comes from the 'Accounts Receivable' field on the Accounts tab of the Customer record view. This field is can not be edited on the transaction.

Database Fields: ERPx_GLAccount.Description, ERPx_ARCustomer.GLARAccountSK

Identifies the date of the transaction. This is required and can be edited from the 'Doc Date' field on the Home tab of the Quick Sale record view while in a Status of 'New'.

Database Field: ERPx_ARTransactionHeader.TransactionDate

Identifies the header comment/description of the transaction or batch. This is not required and can be edited from the 'Description' field on the Home tab of the Quick Sale record view.

Database Field: ERPx_ARTransactionHeader.Description

Identifies the Doc No (document number) for the transaction. Unlike a Transaction ID that is system assigned based on the Transaction Class of the Transaction Type, this is a manually entered value. This is not required and can be edited from the 'Description' field on the Home tab of the Quick Sale record view.

Database Field: ERPx_ARTransactionHeader.DocNumber

Identifies the Extended amount of the line item. This is required and can be edited by changing the 'Quantity' or 'Price' field on the Items grid of the Quick Sale record view while in a Status of 'New'.

Database Field: ERPx_ARTransactionLine.ExtendedAmount

Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This is required and can be edited from the 'GL Date' field on the Properties tab of the Quick Sale record view while in a Status of 'New'. This value 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 and can be edited from the 'GL Date' field on the Properties tab of the Quick Sale record view while in a Status of 'New'. This value is not stored in the database. 

Identifies the ID of the Item.  This is required and can be edited from the 'Item' field on the Items grid of the Quick Sale record view while in a Status of 'New'. 

Item IDs are the unique identifier for Items. 

Database Fields: ERPx_IMItem.ItemID, ERPx_ARTransactionLine.ItemSK

Identifies the class that is assigned to the Item on the transaction or transaction line. This is required and comes from the 'Item Class' property on the Properties tab of the Item record view. This field is can not be edited on the transaction.

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 Fields: ERPx_IMItem.ItemClassSK, ERPx_ARTransactionLine.ItemSK

Identifies the Description associated with the Item ID assigned to a transaction line, journal line detail or master file record. This is required and can be edited from the 'Description' field on the Items grid of the Quick Sale record. 

Database Field: ERPx_ARTransactionLine.ItemDescription

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 'PO' field on the Home tab of the Quick Sale record view.

Database Field: ERPx_ARTransactionHeader.PurchaseOrderID

Identifies the price of the line item. This is required and can be edited from the 'Price' field on the Items grid of the Quick Sale record view while in a Status of 'New'. 

Database Field: ERPx_ARTransactionLine.Price

Identifies the ID of the Price List that is assigned to the transaction.  This is required and can be edited from the 'Price List' field on the Home tab of the Quick Sale record view while in a Status of 'New'. 

Price Lists are used to store a group of Items with pre-defined prices and effective dates.

Database Field: ERPx_ARTransactionHeader.PriceListHeaderSK

Identifies the quantity of the line item. This is required and can be edited from the 'Quantity' field on the Items grid of the Quick Sale record view while in a Status of 'New'. 

Database Field: ERPx_ARTransactionLine.Quantity

Identifies the reference for a line item on the transaction.
This is not required and can be edited from the 'Reference' field on the Items grid of the Quick Sale record view.

Database Field: ERPx_ARTransactionLine.Reference

Displays the unique identifier for the Customer record or for the Customer assigned to a transaction. If the Sale was to an Employee, this will be the Employee ID. This is required and can be edited by changing the 'Sold To' field on the Home tab of the Quick Sale record view while in a Status of 'New'. 

Database Fields: ARCustomer.CustomerID, ERPx_ARTransactionHeader.CustomerSK

Identifies the name of the Customer record or for the Customer assigned to a transaction. If the Sale was to an Employee, this will be the Employee Name. This is required and can be edited by changing the 'Sold To' field on the Home tab of the Quick Sale record view while in a Status of 'New'. 

Database Fields: ERPx_ARCustomer.CustomerName, ERPx_ARTransactionHeader.CustomerSK

Identifies the Status of the transaction. This is required and can be edited from the 'Status' field on the Home tab of the Quick Sale record view while the transaction is in a Status of 'New' or 'Approved'.

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.  

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.

Database Fields: ERPx_ARTransactionStatus.StatusName, ERPx_ARTransactionHeader.TransactionStatusSK

Identifies the Tax Class that is assigned to the transaction. This is not required and can be edited by changing the 'Tax Class' field on the Home tab of the Quick Sale record view while in a Status of 'New'. 

Tax Classes store all the Tax Details (individual taxes) used to calculate sales tax on Quick Sales, Fisherman Sales, and Tender Resale transactions. 

Database Field: ERPx_ARTransactionHeader.TaxClassSK

Identifies the unique Transaction ID for each transaction. Clicking on this link opens the Quick Sale record view for the selected record. This is a system assigned number that comes from the 'Transaction Class' and is required, but is never editable by users.

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_ARTransactionHeader.TransactionID

The unique identifier of the Transaction Class. This is required and is never editable. It is assigned based on the 'Sold To' field on the Home tab of the Quick Sale record view. If a Customer is selected, the Transaction Class will be displayed as "Customer Sale". If an Employee is selected, the Transaction Class will be displayed as "Employee Sale".

Transaction Classes are used to differentiate transactions within a Transaction Type. For example, Transaction Classes of Fresh and Frozen can be setup for the Transaction Type of 'Sales Order'. Transaction Classes are used in all functional areas throughout the application.

Database Fields: ERPx_ARTransactionClass.TransactionClassDescription, ERPx_ARTransactionHeader.TransactionClassSK

Identifies the Transaction Type for each transaction. This is required and is never editable. It is assigned based on the 'Sold To' field on the Home tab of the Quick Sale record view. If a Customer is selected, the Transaction Class will be displayed as "Customer Sale". If an Employee is selected, the Transaction Class will be displayed as "Employee Sale".

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, ERPx_ARTransactionClass.TransactionTypeSK

Identifies the unit of measure that the items are stored in (Lbs, kgs, Cases, etc.) on the transaction.
This is required and can be edited from the 'UOM' field on the Items grid of the Quick Sale record view while in a Status of 'New'. 

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.UOMID, ERPx_ARTransactionLine.QuantityUOMSK