Identifies the sum of the 'Amt. Ordered' of all the line items on the Purchase Order. This is a calculated field that is formatted to 2 decimal places. 

Database Field: ERPx_APPoHeader.OrderedAmount

AP Amt. Fully Invoiced

AP Amt. Posted

Identifies the sum of the extended amounts of all the line item that have 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_APPoHeader.InvoicedAmount

AP Amt. Remaining

Identifies the sum of line item's 'AP Amt. Remaining' values. This is a calculated field and can only be changed by changing either the 'Qty Ordered' or the 'Price' of one or more line items on the Items Grid of the Purchase Order Record View or by entering and/or posting AP Invoices/Credit Memos that are linked to a PO line item. It is calculated as the sum of all line's [Amt. Ordered] - [AP Amt. Posted] - [AP Amt. Unposted] and is formatted to 2 decimal places.  

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

AP Qty Fully Invoiced

Identifies whether the 'Qty Ordered' for every 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). If all the Purchase Order items are "Fully Invoiced" in terms of their quantities, this 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 formatted to two decimal places and is not stored in the database.

AP Qty Posted

Identifies the sum of the quantities of all the line items that have 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_APPoHeader.InvoicedQty

AP Qty Remaining

Identifies the sum of all the line items 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 one or more line items on the Items Grid of the Purchase Order Record View or by entering and/or posting AP Invoices/Credit Memos that are linked to one or more PO line items. It is calculated as the sum of each line items [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 formatted to two decimal places and 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 two decimal places and is not stored in the database. It is calculated as [IM Qty Posted] - [AP Qty Posted].

• A zero value means there is no difference between the sum of the line items 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.

Identifies the person responsible for issuing the Purchase Order. This is not required.

Database Field: ERPx_APPoHeader.Buyer

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 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. This field is required.

Database Field: ERPx_APPoHeader.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. This field is required.

Database Field: ERPx_APPoHeader.CreatedBy

Identifies the Discount % associated with the Payment Terms of the Vendor. This is not editable on the transaction.

Database Fields: ERPx_MFPaymentTerms.DiscountPercent, APPOHeader.DiscountPercent

IM Qty Fully Received

Identifies whether the 'Qty Ordered' of all the Purchase Order items have 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). If all the Purchase Order items are "Fully Received" in terms of their quantities, this 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 and is not stored in the database.

IM Qty Posted

Identifies the sum of the line items that have been included on "Posted" IM Receipts. This is a calculated field that is formatted to two decimal places.

 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_APPoHeader.ReceivedQty

IM Qty Remaining

Identifies the sum of the quantity of the line items 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 one or more line items on the Items Grid of the Purchase Order Record View or by entering and/or posting Inventory Receipts that are linked to a PO line item. It is the sum of the line items [Qty Ordered] - [IM Qty Posted] - [IM Qty Unposted]. This is formatted to two decimal places.

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

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. This field is required.

Database Field: ERPx_APPoHeader.LastUpdated

Identifies the name of the user that last updated 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. This field is required.

Database Field: ERPx_APPoHeader.LastUser

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 Payment Terms assigned to the transaction. This is required and can be edited from the 'Payment Terms' field on the 'Properties' tab of the Purchase Order Record View. This is editable until the Purchase Order is Closed.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Payment Terms.

Database Fields: ERPx_MFPaymentTerms.PaymentTermName, APPOHeader.PaymentTermSK

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

Database Field: ERPx_APPoHeader.PurchaseContactName

Identifies the sum of the 'Qty Ordered' of all the line items on the Purchase Order. This is a calculated field that is formatted to 2 decimal places. The 'Qty Ordered' can be 0.00 but it cannot be negative. 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] - [Qty Invoiced]. 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] - [Qty Received]. If this results in a negative amount it will default as 0.00.

Database Field: ERPx_APPoHeader.OrderedQty

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