Identifies the extended amount of the line item based on the ordered quantity. This is a numeric text box that is auto calculated as [Quantity] x [Price]. This can only be updated by changing either the 'Quantity' or 'Price'. This is formatted to 2 decimal places.

Database Field: ERPx_APPoLine.ExtendedAmount

Identifies the Currency assigned to the transaction. This is required and comes from the 'Currency ID' on the 'Properties' tab of the Purchase Order Record View. This is not editable on the transaction as it comes in from the 'Currency' assigned to the Vendor.

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 

Database Field: ERPx_APPoHeader.Description

Identifies how the (extended) amount of the line item was, or will be, applied. Identifies the name of a Project, Employee, Fisherman, Tender or Fisherman Loan. This is not required and is editable until the Purchase Order is 'Closed'.

Database Fields: ERPx_APVendor.VendorName, ERPx_MFEmployee.EmployeeName, ERPx_GLProject.ProjectDescription, ERPx_APPoLine.ToDistributionAccountSK 

Identifies the date the Purchase Order will expire.This is required and can be edited from the 'Expire By' date on the 'Home' tab of the Purchase Order Record View. This is always editable until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.ExpireDate

Identifies the date of the transaction. This is required and can be edited from the 'Ordered' date on the 'Home' tab of the Purchase Order Record View. This is always editable until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.PODate 

Identifies the payable account number for the line item. This is required and is only editable from "Accounts Payable" GL Account, on the Accounts Tab of the Vendor Record View of the assigned Purchase Order's Vendor.

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_APVendor,APGLAcctRef 

Identifies the unique Transaction ID for each transaction.Clicking on this link opens the Purchase Order Record View for the selected record. This is a system assigned number that comes from the 'Transaction Class' and is required and is editable by users until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.PurchaseOrderID

Identifies the price of the line item. This is a numeric text box that is required and must be greater than or equal to 0. It is formatted to the Item's 'Price Decimals'. This is editable until the Purchase Order is 'Closed'. 

Database Field: ERPx_APPoLine.Price

Identifies the GL Account the purchase line will post to. This is not required and is editable from the 'Purchase Account' column of the Items Grid on the Purchase Order Record View.

 When AP Invoices and/or Credit Memos are loaded from a PO, the 'Purchase Account' will default from the current Purchase Account assigned to the Purchase Order Item.

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_APTransactionLine.AccountSK

Identifies the quantity of the line item being ordered. This is a numeric text box that must be greater than 0. It is formatted to 2 decimal places. This is editable until the Purchase Order is 'Closed'. 

Database Field: ERPx_APPoLine.OrderedQuantity

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.

Closed: Used to indicate that the record is no longer open to be used on other transactions. Closed records are only visible from inquiries, not list views.

Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APPoHeader.TransactionStatusEN

The unique identifier of the Transaction Class. This is required and comes from the 'Transaction Class' on the 'Properties' tab of the Purchase Order Record View. This is not editable.

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_APTransactionClass.TransactionClassDescription, ERPx_APPoHeader.TransactionClassSK

Identifies whether or not more than one AP Invoice can be recorded against the Purchase Order. This is editable until the Purchase Order is 'Closed' and the options include:

1. Allow Single Invoice: If this option is selected, the Purchase Order can only be assigned to a single AP Invoice.
   1. Once it has been assigned on and AP Invoice, it can no longer be manually entered and will no longer be displayed in the PO Lookups for that transaction and the Purchase Order's Status will be auto set to "Closed".
   2. An 'Open' Purchase Order can always be applied to multiple AP Credit Memos.   
2. Allow Multiple Invoices: If this option is selected, the Purchase Order can be assigned to multiple AP Invoices. Purchase Orders set to this Type must be manually Closed.

This lookup contains all the values in the APPOType Enumeration Class 

Database Field: ERPx_APPoHeader.TransactionTypeEN 

This is a single-select lookup and is required and is editable until the Purchase Order is 'Closed'.

The lookup contains all 'Active' UOMs 

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_APPoLine.QuantityUOMSK

Identifies the class that is assigned to the Vendor on the transaction. This is required and comes from the 'Vendor Class' assigned to the 'Vendor' that is selected on the 'Home' tab of the Purchase Order Record View. Because this defaults from the Vendor it is not editable on the transaction.

Vendor Classes are used to identify default values that will be applied to new Vendor accounts and to group Vendor accounts together for reporting purposes. 

Database Field: ERPx_APVendorClass.ClassDescription, ERPx_APPoHeader.VendorSK

Identifies the ID of the Vendor account that is assigned to the transaction. This is required and represents the ID of the 'Vendor' on the 'Home' tab of the Purchase Order Record View. This is only editable by changing the Vendor assigned to the transaction.

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

Database Fields: ERPx_APVendor.VendorID, ERPx_APPoHeader.VendorSK

Identifies the name of the Vendor assigned to the transaction or master file. This is set in the Vendor Record View.  This is required and represents the name of the 'Vendor' on the 'Home' tab of the Purchase Order Record View. This is only editable by changing the Vendor assigned to the transaction.

Vendor Names are used as a long description for Vendors.

Database Fields: ERPx_APVendor.VendorName, ERPx_APPoHeader.VendorSK