Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

A Purchase Order (aka PO) is a document issued by a buyer committing to pay the seller for specific products or services to be delivered in the future. The advantage to the buyer is the ability to place an order without immediate payment. From the seller’s perspective, it reduces credit risk, since the buyer is obligated to pay once the products or services have been delivered. Each PO has a unique number associated with it that helps both buyer and seller track delivery and payment.  

This page lists each unique Purchase Order item. The purpose of this page is to view line items on close Purchase Orders. 

(lightbulb) This list view also contains columns for each Attribute that is set up for the 'AP Purchasing' attribute type. Because these are user defined, they are not included in the default view but can be added a saved layout. AP Purchasing attributes are not included in the help documentation.

Software Version: 2021.07.23 and newer

Page Header

Filter ItemsDescription
Ordered DateUsed to select the date the Purchase Order was ordered. This is a date range control that allows users to select a single date or a range of dates, formatted from the users 'Date Format' preference. This is required to return results and defaults with a date range of the past 30 days.
Search

A non-required text box that defaults to blank and is used to search across multiple fields. When the page is 'Refreshed', the data returned will be limited by what was included in the Search box (in addition to any other Search Options). 

Refer to this FAQ for advanced search options.

The Search field can be used to search across the following fields: 

  • Description
  • Item Description
  • Purchase Order
  • Vendor ID
  • Vendor Name
Transaction Class

Used to select one or more Transaction Classes. The values in this lookup are listed alphabetically. If there is more than one Transaction Class for the Transaction Type, then the value in the lookup will display as [Transaction Type] - [Transaction Class]. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each.

The lookup contains a list of all 'Active' Transaction Classes.

Vendor

Used to select one or more Vendors. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

A Vendor is a company or person that sells goods or services to your company. They are used in Purchasing and on Brokerage Sales Programs.

The lookup contains a list of all 'Active' Vendors

Vendor Class

Used to select one or more Vendor Classes. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

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. 

The lookup contains a list of all 'Active' AP Vendor Classes.

Page Detail

Toolbar IconsDescription
Column Filter Show/Hide Toggles between displaying and hiding a filter row in the grid under the column headers. The filter row will be displayed by default if the Quick Column Filter is also implemented in the page. When enabled, this will allow users to type in text to filter by a specific column.
EditOpens the selected record for editing. If a record is not selected, the page will either not open or will open the first record (depending on how the page was coded). 
Excel Exports the contents of the grid to an Excel file that will automatically download. The contents that export are those that are visible to the user. Therefore, if the user has filtered the view, or excluded columns, only the contents in the grid will be exported. 
Favorites Clicking on the star icon when it is an outline, adds the page to the 'My Shortcuts' tab and fills in the star. Clicking on the star icon when it is filled in (solid color), removes the page from the 'My Shortcuts' tab and returns the icon to an outline. 

(lightbulb) Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.

Group By Show/Hide Toggles between displaying and hiding a row in the grid above the column headers to enable grouping by one or more column(s). Once displayed, users may drag and drop column headers to group by a specific column. Once the grid is grouped by a column(s), a subtotal footer row will display in the grouping for columns that have a page footer total. 
Help Opens the online WIKI help page for the current page. 
More Actions

 Displays a drop down menu of related actions. The list of options includes:

  • IQ: PO Transaction Items - Opens an inquiry with all the Purchase Orders, AP Invoices, AP Credit Memos, and Inventory Receipts with this Purchase Order Item assigned.  This inquiry has not been designed yet.
  • RV: Transaction: Opens the Purchase Order Record View for the selected transaction.
Print

 Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. 

When clicked, all the Reports that launch from the Print Dialog that are assigned to this page, and that the user has rights to (if Report Data Access is enabled) are displayed.

When clicked, all the Reports assigned to the Functional Area of Purchasing, that launch from the Print Dialog, assigned to the Purchase Order Lines Inquiry, and that the user has rights to are displayed.

Quick Column Filter Used to filter across all columns in the grid. When the user types text into the Quick Column Filter text box, the grid's Filter Row will be automatically hidden. The text in the Quick Column Filter text box automatically replaces any existing Filter Row filters. The results of the data immediately refresh as you enter text.
Refresh Re-queries the contents of the grid/page based on the Search Options or the default values for grids that do not support Search Options. 

(lightbulb) This ONLY re-queries the contents of columns that are currently visible, if you add a new column the contents will be empty until you click 'Refresh' again.

Saved Column Layout Displays the column layout lookup and related icons. This tool allows users to select a previously saved layout, create a new layout, save changes to a layout, forget/delete a layout and/or assign a saved layout as the default for the page. Once changes are made to the layout, such as columns are added or removed, the user can click the Save Layout icon and save the changes to the column layout. The visibility of the Filter Row is also saved with a saved layout. The new layout can also be set as the default. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific).  Default layouts can be removed by clicking the 'Set as Default' button again when the current default layout is selected.  

Please note that existing saved grid layouts will display the Filter Row as hidden by default.

Search Options Toggles between displaying and hiding the Search Options portion of the page.

Fields

Description
CheckboxUsed to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Amt. Fully Invoiced

Identifies whether the 'Amt. Ordered' of the Purchase Order item has been fully Invoiced. If the 'Amt. Invoiced' for a Purchase Order item is >= the 'Amt. Ordered', 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. 

Is this a calculated field or is it stored in the database?

Amt. Fully Received

Identifies whether the 'Amt. Ordered' of the Purchase Order item has been fully Received. If the 'Amt. Received' for a Purchase Order item is >= the 'Amt. Ordered', the item is considered "Fully Received" 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 received.

Is this a calculated field or is it stored in the database?

Amt. Invoiced

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.

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

Amt. Ordered

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

Amt. Received

Identifies the extended amount of the line item that has been included on "Posted" IM Receipts. This is a calculated field that is formatted to 2 decimal places.

(lightbulb) When IM Receipts, with line items that reference a Purchase Order are posted, this value is updated as [Qty Received] * [PO Item Price].

(lightbulb) Because non-Inventory Purchase Order Items are not "Received" using an Inventory Receipt transaction, the 'Amt. Received' value is updated from the extended amounts of posted AP Invoices and Credit Memos that reference the Purchase Order Item.

Currency ID

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.

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

Description

Error rendering macro 'excerpt-include' : No link could be created for 'Description - Header'.
 This is not required and can be edited from the 'Description' field on the 'Home' tab of the Purchase Order Record View. This is always editable until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.Description

Distributed To

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 

Distributed Type

Identifies the type of distribution based on the selected Distributed To field.  This is an auto generated field that is not editable by the user. 

The options include:

  • Project
  • Fisherman
  • Tender
  • Fisherman & Tender
  • Loan

Database Field: ERPX_APPoLine.ToMFDistributionTypeEN

Expire By

Identifies the date the Purchase Order will expire. This is required and can be edited from the 'Expire By' 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.ExpireDate

Item Added ByIdentifies the name of the user that added the line item to 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.
Item AddedIdentifies the Date & Time that the line item was added to the Transaction. This is formatted from the users 'Date Format' preference and is a system assigned value and is never editable by a user.
Item Last Updated ByIdentifies 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.
Item Last UpdatedIdentifies the Last Updated Date & Time of the line item on the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user.
Item Description

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.

Item ID

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.

Item Type

Error rendering macro 'excerpt-include' : No link could be created for 'Item Type'.
 This represents the Item Type assigned to the Item ID and is not editable.

Database Fields: ERPx_IMItemType.Description, ERPx_IMItem.ItemTypeSK

Ln.

Identifies the Line # for each Transaction Line Item. The Line # sets the sort of the items on grids, list views, inquiries, and reports. This is required and can be edited from the Ln. field on the Purchase Order Record View Items Grid until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoLine.LineNumber

Ordered

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

Payable GL Account

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 

Payable GL Account Description

Identifies the name of the payable account number for the line item. This is only editable by changing the 'Account Description' for the Vendors assigned 'Accounts Payable' from the GL Accounts List View. 

PO #

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', it is required, and can be edited from the 'Reference' field on the 'Home' tab of the Purchase Order Record View. This is editable until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.PurchaseOrderID

PO Type

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.
    1. Once it has been used on one of those transactions, it can be assigned to additional transactions but those transactions cannot be 'Approved' or 'Posted'.
    2. Once it has been used on both an AP Invoice and Inventory Receipt (for PO's that contain inventory items) the Purchase Order's Status will be auto set to "Closed".
    3. An 'Open' Purchase Order can always be assigned to multiple AP Credit Memos.   
  2. Multiple Invoices and ReceiptsIf 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.TransactionTypeEN 

Price

Identifies the price of the line item. This is required and can be edited from the 'Price' field on the Items Grid of the Purchase Order Record View. It is formatted to the Item's 'Price Decimals' and is editable until the Purchase Order is 'Closed'. 

Database Field: ERPx_APPoLine.Price

Purchase GL Account

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.

(lightbulb) 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

Purchase GL Account Description

Identifies the name of the General Ledger account assigned as the purchase account on the line item. This is only editable by changing the 'Account Description' for the line items assigned 'Purchase Account' from the GL Accounts List View. 

Qty Fully Invoiced

Identifies whether the 'Qty Ordered' of the Purchase Order item has been fully Invoiced. If the 'Qty Invoiced' for a Purchase Order item is >= the 'Qty Ordered', 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. 

Is this a calculated field or is it stored in the database?

Qty Fully Received

Identifies whether the 'Qty Ordered' of the Purchase Order item has been fully Received. If the 'Qty Received' for a Purchase Order item is >= the 'Qty Ordered', 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. 

Is this a calculated field or is it stored in the database?

Qty Invoiced

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.

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

Qty Ordered

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

(lightbulb) 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.

(lightbulb) 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.

Qty Received

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.

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

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

Reference

Identifies the Reference entered for the transaction.  This is not required and can be edited from the 'Reference' field on the 'Home' tab of the Purchase Order Record View. This is always editable until the Purchase Order is 'Closed'.

A Reference number is used to record an additional tracking number that associates this transaction to another system. For example, if a transaction was imported from a 3rd party system this could be used to store the unique identifier from that system's transaction. 

Database Field: ERPx_APPoHeader.Reference

Requisition #

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

Site ID

Identifies the unique Site ID (warehouse ID) of the Site the transaction, shipment, item, or lot is associated with. This is required and can be edited from the 'Site Name' 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_MFSite.SiteIDERPx_APPoHeader.SiteSK

Status

Identifies the Status of the transaction. This is required and is always editable.

The Statuses that apply to Purchase Orders in this inquiry include:

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.

(lightbulb) Open Purchase Orders are only visible from the Purchase Order and/or Purchase Order Items List Views.

Database Fields: ERPx_APPoHeader.TransactionStatusEN 

Transaction Class ID

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

UOM

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 is required and can be edited from the 'UOM' field on the Items Grid of the Purchase Order Record View until the Purchase Order is 'Closed'.

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

Vendor Class ID

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

Vendor ID

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

Vendor Item Description

Error rendering macro 'excerpt-include' : No link could be created for 'Vendor Item Description'.
 This is always editable from the Purchase Order Record View Items Grid until the Purchase Order is 'Closed'.

(lightbulb) When AP Invoices, Credit Memos, and IM Receipts are loaded from a PO, this will default as the 'PO Item Description' on those transactions.

Linked Database Field: ERPx_APPoLine.ItemReference

Vendor Name

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

Related Topics


 Page Definitions


 Technical Details












  • No labels