A lookup to assign one or more conditions you want included in your search. This lookup contains:

• Open - displays all the Purchase Orders that are in an Open or Released status 
• Closed - displays all the Purchase Orders that are in a Closed status

Identifies the extended amount of the Purchase Order Item. This is required and can only be edited by changing either the 'Qty Ordered' or the 'Price' of a line item on the Items Grid of the Purchase Order Record View. It is calculated as [Qty Ordered] * [Price] and is formatted to 2 decimal places. This is editable until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoLine.ExtendedAmount

AP Amt. Fully invoiced

Identifies whether the 'Amt. Ordered' of the Purchase Order item has been fully Invoiced. If the 'AP Amt. Remaining' for a Purchase Order item is <= 0, the item is considered "Fully Invoiced" in terms of Amount (cost) and will display as "Yes", otherwise it will be blank. This allows users to easily determine which PO's have amounts that have not yet been invoiced. This is a calculated field and is not stored in the database. 

AP Amt. Posted

Identifies the extended amount of the line item that has been included on "Posted" AP Invoices and AP Credit Memos. This is a calculated field that is formatted to 2 decimal places.

 When AP Invoices and/or Credit Memos, with line items that reference a Purchase Order are posted, this value is updated.

Database Field: ERPx_APPoLine.InvoicedAmount

AP Amt. Remaining

Identifies the dollar amount of the line item that has not yet been accounted for on an AP Invoice/Credit Memo. This is a calculated field and can only be changed by changing either the 'Qty Ordered' or the 'Price' of a line item on the Items Grid of the Purchase Order Record View or by entering and/or posting AP Invoices/Credit Memos that are linked to this item. It is calculated as [Amt. Ordered] - [AP Amt. Posted] - [AP Amt. Unposted] and is formatted to 2 decimal places. This is editable until the Purchase Order is 'Closed'.

This is a calculated field that is not stored in the database.

AP Qty Fully Invoiced

Identifies whether the 'Qty Ordered' of the Purchase Order item has been fully Invoiced. If the 'AP Qty Remaining' for a Purchase Order item is <= 0, the item is considered "Fully Invoiced" in terms of quantity (units or weight) and will display as "Yes", otherwise it will be blank. This allows users to easily determine which PO's have quantities that have not yet been invoiced. 

This is a calculated field that is not stored in the database.

AP Qty Posted

Identifies the quantity of the line item that has been included on "Posted" AP Invoices and AP Credit Memos. This is a calculated field that is formatted to the Item's 'Unit Decimals' or 'Weight Decimals' depending on the Item's UOM.

 When AP Invoices and/or Credit Memos, with line items that reference a Purchase Order are posted, this value is updated.

Database Field: ERPx_APPoLine.InvoicedQty

AP Qty Remaining

Identifies the quantity of the line item that has not yet been accounted for on an AP Invoice/Credit Memo. This is a calculated field and can only be changed by changing the 'Qty Ordered' of a line item on the Items Grid of the Purchase Order Record View or by entering and/or posting AP Invoices/Credit Memos that are linked to this item. It is calculated as [Qty Ordered] - [AP Qty Posted] - [AP Qty Unposted] and is formatted to the Item's 'Unit Decimals' or 'Weight Decimals' depending on the Item's UOM.

This is a calculated field that is not stored in the database.

AP vs IM Posted Qty

Identifies the difference between the quantities accounted for on "Posted" AP Invoices/Credit Memos and "Posted" Inventory Receipts for the line item. This is a calculated field that is formatted to the Item's 'Unit Decimals' or 'Weight Decimals' depending on the Item's UOM. It is calculated as [IM Qty Posted] - [AP Qty Posted].

• A zero value means there is no difference between the quantities of "Posted" AP Invoices and "Posted" Inventory Receipts.
  • A positive value indicates more Qty has been received than has been paid for.
  • A negative value indicates more Qty has been paid for than has been received.

 When AP Invoice, AP Credit Memo, and/or Inventory Receipt transactions with line items that reference a Purchase Order are posted, this value is updated.

This is a calculated field that is not stored in the database.

Identifies the person responsible for issuing the Purchase Order. This is not required and can be edited from the 'Buyer' field on the 'Home' tab of the Purchase Order Record View. This is always editable even after the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.Buyer

Identifies the Currency assigned to the transaction. This is required and comes from the 'Currency' on the 'Properties' tab of the Purchase Order Record View. This is not editable 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_APVendor.CurrencySK

Identifies the header comment/description of the transaction or batch. This is not required and can be edited from the 'Comment' field on the 'Home' tab of the Purchase Order Record View. This is always editable even after the Purchase Order is 'Closed'.

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 

IM Qty Fully Received

Identifies whether the 'Qty Ordered' of the Purchase Order item has been fully Received. If the 'IM Qty Remaining' for a Purchase Order item is <= 0, the item is considered "Fully Received" in terms of quantity (units or weight) and will display as "Yes" otherwise it will be blank. This allows users to easily determine which PO's have quantities that have not yet been received. 

This is a calculated field that is not stored in the database.

IM Qty Posted

Identifies the quantity of the line item that has been included on "Posted" IM Receipts. This is a calculated field that is formatted to the Item's 'Unit Decimals' or 'Weight Decimals' depending on the Item's UOM.

 When IM Receipts, with line items that reference a Purchase Order are posted, this value is updated.

 Because non-Inventory Purchase Order Items are not "Received" using an Inventory Receipt transaction, the 'IM Qty Posted' value is updated from posted AP Invoices and Credit Memos that reference the Purchase Order Item.

Database Field: ERPX_APPoLine.ReceivedQty

IM Qty Remaining

Identifies the quantity of the line item that has not yet been accounted for on Invoice Receipts. This is a calculated field and can only be changed by changing the 'Qty Ordered' of a line item on the Items Grid of the Purchase Order Record View or by entering and/or posting Inventory Receipts that are linked to this item. It is calculated as [Qty Ordered] - [IM Qty Posted] - [IM Qty Unposted] and is formatted to the Item's 'Unit Decimals' or 'Weight Decimals' depending on the Item's UOM.

This is a calculated field that is not stored in the database.

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 only be edited from the 'Item Description' property on the Item Record View of the assigned Item ID.

Database Fields: ERPx_IMItem.ItemDescription, ERPx_APPoLine.ItemSK

Identifies the Item ID of the Item on the transaction line. This represents the Item ID assigned to the Purchase Order Line Item and is not editable.

Database Fields: ERPx_IMItem.ItemID, ERPx_APPoLine.ItemSK

Identifies the name of the user that last updated the line item on the transaction. 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_APPoLine.LastUser

Identifies an alternate item description for a line item. This is most commonly used to either identify the Vendor's Item Description or to add more clarity to a generic/bulk Item ID. This is a textbox that defaults from the Item Description of the corresponding Item ID and is editable from the Purchase Order record until it is 'Closed'. 

 When AP Invoices, Credit Memos are loaded from a PO, this will default as the 'Line Description' on those transactions.

Database Fields: ERPx_IMItem.ItemDescription, ERPX_APPoLine.LineDescription

A non-editable textbox that displays where the corresponding line item originates from. The available options include:

1. Manual: The line item was manually added by a user.
2. Freight: The line item was auto-added to reflect the Freight + Surcharge amount of a Shipment Leg.
3. Freight - Handling: The line item was auto-added to reflect the Handling amount of a Shipment Leg.
4. Freight - Other: The line item was auto-added to reflect an Other Charge amount of a Shipment Leg.

Database Field: ERPx_APPoLine.LineSourceEN

Identifies the Vendor that the transaction line item was purchased and/or received from. This is not required and can be edited from the 'Line Vendor' column of the Items Grid on the Purchase Order Record View.  This is editable until the first AP Invoice, AP Credit Memo, or IM Receipt against the Purchase Order Item is Posted or until the Purchase Order is 'Closed'.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' AP Vendors assigned to the same Currency ID as the Vendor on the Header. It excludes the Vendor assigned to the Transaction Header.

Database Fields: Database Field: ERPx_APVendor.VendorName, ERPx_APPoLine.VendorSK

Identifies the date of the transaction. This is required and can be edited from the 'Ordered' date field on the 'Home' tab of the Purchase Order Record View. This is 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 whether or not more than one AP Invoice and/or Inventory Receipt can be recorded against the Purchase Order. This is editable until the Purchase Order is 'Closed' and the options include:

1. Single Invoice and Receipt: If this option is selected, the Purchase Order can only be assigned to a single AP Invoice and a single Inventory Receipt transaction.
2. Multiple Invoices and Receipts: If this option is selected, the Purchase Order can be assigned to multiple AP Invoices and multiple Inventory Receipt transactions. 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.POTypeEN

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

Identifies the 'Qty Ordered' of the line item on the Purchase Order. This is required and can be edited from the 'Qty Ordered' field on the Items Grid of the Purchase Order Record View. It is formatted to the Item's 'Unit Decimals' or 'Weight Decimals' depending on the Item's UOM. This is editable until the Purchase Order is 'Closed'. 

 When AP Invoices and/or Credit Memos are loaded from a PO, the 'Quantity' will default as [Qty Ordered] - [AP Qty Posted] - [AP Qty Unposted]. If this results in a negative amount it will default as 0.00.

 When IM Receipts are loaded from a PO, the 'Quantity' will default as [Qty Ordered] - [IM Qty Posted] - [IM Qty Unposted]. If this results in a negative amount it will default as 0.00.

Database Field: ERPx_APPoLine.OrderedQuantity

Database Field: ERPx_APPoHeader.ReceiveBy

Identifies the (source) requisition number that the Purchase Order belongs to.  This is not required and can be edited from the 'Requisition' field on the 'Home' tab of the Purchase Order Record View. This is always editable until the Purchase Order is 'Closed'.

A purchase requisition is a document used to inform department managers, or the purchasing officer, of the decision to purchase so that the purchasing department can start the purchase ordering process. A requisition can have one or more Purchase Orders. 

Database Field: ERPx_APPoHeader.Requisition

Identifies how the purchase will be shipped. This is not required and can be edited from the 'Ship Via' field on the 'Home' tab of the Purchase Order Record View. This is always editable even after the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.ShipVia

Displays the Transaction ID of the originating transaction that the Purchase Order was created from. This is not required and will only display a value for Freight Purchase Orders that are automatically created from Inventory Transfers and Sales Orders and Returns. 

Database Field: ERPx_APPoHeader.SourceTransactionID

Identifies the Status of the transaction. This can be edited from the 'Status' on the 'Home' tab of the Purchase Order Record View and represents the status of the transaction. This is always 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:

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_APPOStatus.StatusName, ERPx_APPoHeader.POStatusSK

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 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 Purchased Order Record View. Because this defaults from the Vendor it is not editable on the transaction.

Vendor Class IDs are used as a short description and unique identifier for Vendor Class records.  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