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 11 Current »

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. The purpose of this page is to view, add, edit, remove, and 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

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.
Delete Deletes the selected record(s). When clicked, users will be prompted with: "Are you sure you want to delete the selected records?". Click "OK" to confirm, or "Cancel" to return without deleting. 

WARNING: Records cannot be recovered once they are deleted! 

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. 
Mass Update

Opens the mass update dialog, which allows to mass update the following properties: 

  • Status: A single-select lookup that defaults to "(No Change)". Assigns the selected Status to selected/filtered transactions when Apply is clicked. Options 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.

New Opens a new blank record for data entry.
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.

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.

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

Identifies the sum of the Extended Amounts of all the line items on the Purchase Order. This is a calculated field that is not editable by the user.

Database Field: ERPx_APPoHeader.OrderedAmount 

Amt. Posted

Identifies the sum of the 'Invoiced Amount' of all the line items on the Purchase Order. It represents the dollar amount that has been accounted from on Posted AP Invoices/Credit Memos. This is a calculated field that is not editable by the user.

Database Field: ERPx_APPoHeader.InvoicedAmount 

Amt. Unposted

Identifies the sum of the 'Invoiced Amount' of all the line items on Unposted AP Invoices/Credit Memos. This is a calculated field that is not editable by the user. This field is not stored in the database.

Amt. Remaining

Identifies how much of the Purchase Order is still open. It is calculated as: [Amt. Ordered] - [Amt. Posted] - [Amt. Unposted].  This is a calculated field that is not editable by the user. This field is not stored in the database.

Created

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. 

Database Field: ERPx_APPoHeader.CreatedDate

Created By

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. 

Database Field: ERPx_APPoHeader.CreatedBy

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

Description

Identifies the header comment/description of the transaction or batch. This is not required and can be edited from the 'Description' 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

Expire By

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

Last Updated

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. 

Database Field: ERPx_APPoHeader.LastUpdated

Last Updated By

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. 

Database Field: ERPx_APPoHeader.LastUser

Ordered

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 

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' and is required and is editable by users until the Purchase Order is 'Closed'.

Database Field: ERPx_APPoHeader.PurchaseOrderID

Transaction Class

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

Type

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

Vendor Class

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

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

Page Definitions


 Technical Details

Technical Details


  • No labels