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.
Software Version: 2023.09.29 and newer
Page Header
Header Toolbar
Toolbar Icons | Description |
---|---|
Delete | Deletes the transaction, batch, or master file record. When clicked, users will be prompted with: "Are you sure you want to delete this record?". Click "OK" to confirm, or "Cancel" to return without deleting. WARNING: Records cannot be recovered once they are deleted! Note: Users will not be able to delete a Freight Purchase Order record, the message “[PO#] is a Freight Purchase Order and therefore can not be deleted. Freight Purchase Orders can only be closed.” will be displayed when the button is clicked. |
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:
_
|
New | Allows users to select the type of transaction or record they want to add. The list contains all the 'Active' Purchase Order Classes displayed as Purchase Order - [ClassID]. Note: The Transaction Class will display after the Transaction Type if there is more than one Transaction Class for the Transaction Type. |
Notes | Opens the Notes dialog, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the record. This icon is always enabled. Note Types of "Purchase Order" saved to the Vendor will default on the Purchase Order Notes. Notes are used throughout the application to add additional details to Master Files and Transactions. Transactions and Master Files that support Notes store the text of the note in one or more 'Note Types' as a way to classify/organize notes. |
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. | |
Save | Saves the changes made to the record. |
Save & Close | Saves your changes and closes the page. |
Home Tab
Manual PO's: PO #: [PO ID] Ship To: [Shipping Address Name] [Address 1] [Address 2] [Address 3] [City], [State] [ZIP] Freight PO's: "PO #: [PO #] Created from [SourceTransactionType]: [SourceTransactionID] Shipped from: [Load Header Site Name]". | |
Fields | Description |
---|---|
Buyer | Identifies the person responsible for issuing the Purchase Order. This is a text box that defaults to blank and is not required, but if entered, it must be <=50 characters. This is always editable even after the Purchase Order is 'Closed'. Database Field: ERPx_APPoHeader.Buyer |
Comment | Identifies the header comment/description of the transaction or batch. This is text box that defaults to blank and is not required, but if entered, it must be <=150 characters. This is always editable even after the Purchase Order is 'Closed' and will default on all new AP Invoices, AP Credit Memos, and IM Receipts that reference this Purchase Order. Database Field: ERPx_APPoHeader.Description |
Ordered | Identifies the date of the transaction. This is a date picker that is required. It defaults as the current date. The 'Ordered' date must be on or before the Expire By date, else the message "Expire By date must be later than the Ordered date." will be displayed on Save. This is editable until the Purchase Order is 'Closed'. Database Field: ERPx_APPoHeader.PODate |
PO # | A Purchase Order # (aka PO #) is the unique identifier of a Purchase Order. 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. The options include:
This lookup contains all the values in the APPOType Enumeration Class. Database Field: ERPx_APPoHeader.POTypeEN |
Requisition # | Identifies the (source) requisition number that the Purchase Order belongs to. This is text box that defaults to blank and is not required, but if entered, it must be <=25 characters. This is editable until the Purchase Order is 'Closed'. AP Invoices, AP Credit Memos, and IM Receipts that reference this Purchase Order will also reference this Requisition #. 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 |
Ship Via | Identifies how the purchase will be shipped. This is text box that defaults to blank and is not required, but if entered, it must be <=100 characters. This is always editable even after the Purchase Order is 'Closed'. Database Field: ERPx_APPoHeader.ShipVia |
Site Name | Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. This is a single-select lookup that is not required. It defaults from the 'Default Site' assigned to the Purchase Order Transaction Class. This is editable until the Purchase Order transaction is 'Closed'. This is also editable after transactions have been posted against the Purchase Order since it is just used to set the default Site on new Inventory Receipts. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. This lookup contains a list of all active Sites. Database Fields: ERPx_MFSite.SiteID, ERPx_APPoHeader.SiteSK |
Status | Identifies the Status of the transaction. This is a single-select lookup that is required. It defaults as "New" and is always editable. The Statuses that apply to transactions in this Record 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. PO's cannot be 'Closed' if there are any unposted AP Invoices, Credit Memos or Inventory Receipts else the message "Purchase Orders referenced on unposted transactions cannot be closed. PO#: [PurchaseOrderID] - AP Invoice [TransactionID] PO#: [PurchaseOrderID] - AP Credit Memo [TransactionID] PO#: [PurchaseOrderID] - IM Receipt [TransactionID] Database Fields: ERPx_APPoHeader.POStatusSK |
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 a single-select lookup that is required. It defaults as blank and is editable until the Purchase Order is 'Closed' or until the first Invoice or Credit Memo is entered against the Purchase Order, whether it is posted or not, otherwise the message "You cannot change the Vendor on Purchase Orders that are assigned to invoices/credit memos. (AP Transaction # list)” will be displayed. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Vendors with a VendorTypeEN = 1. Database Fields: Database Field: ERPx_APPoHeader.VendorSK, ERPx_APVendor.VendorName |
Properties Tab
Fields | Description |
---|---|
Group: 1 | |
Purchase Contact Name | Identifies the Vendor's Contact Name for Purchases. This is text box that defaults from the "Purchase" Contact on the 'Contacts' tab of the Vendor Record View. It is not required, but if entered, it must be <=100 characters. This is always editable even after the Purchase Order is 'Closed'. Database Field: ERPx_APPoHeader.PurchaseContactName |
Ship Attention To | Identifies the name of the person the purchase is intended for. This is a text box that defaults to blank and is not required, but if entered, it must be <=100 characters. This is always editable even after the Purchase Order is 'Closed'. Database Field: ERPx_APPoHeader.ShipAttentionTo |
Reference | Identifies the Reference entered for the transaction. This is text box that defaults to blank and is not required, but if entered, it must be <=100 characters. This is always editable even after the Purchase Order is 'Closed'. For Freight PO's generated from Sales Orders this value will default to the Shipment number. Database Field: ERPx_APPoHeader.Reference |
Receive By | Identifies the date the Purchase Order should be fully received. This is a date picker that defaults as blank and is not required. If entered, it must be on or after the 'Ordered' date, else the message "Receive By date must be later than the Ordered date." will be displayed on Save. This is editable until the Purchase Order is 'Closed'. This is for informational purposes only. Database Field: ERPx_APPoHeader.ReceiveBy |
Expire By | Identifies the date the Purchase Order will expire. This is a date picker that is required. It defaults as 1 year from the current date. The 'Expire By' date must be on or after the 'Ordered' date, else the message "Expire By date must be later than the Ordered date." will be displayed on Save. This is editable until the Purchase Order is 'Closed'. This is for informational purposes only, until a Purchase Order's Status is set to "Closed" it can be used regardless of whether it has expired or not. Database Field: ERPx_APPoHeader.ExpireDate |
Group: 2 | |
Payment Terms (Primary PO Vendor) | Identifies the Payment Terms assigned to the transaction. This is a single-select lookup that defaults from the Payment Terms assigned to the selected Vendor on the Home tab. This is not required and is editable until the Purchase Order is Closed. Payment Terms identify the terms your company extends to your Customers and that your Vendors extend to you. Payment Terms are used to calculate aging and payment discounts. 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 |
Discount Percent | This is a textbox that identifies the Discount percent associated with the Payment Terms, formatted to 5 decimal places. This is editable while the transaction is in a 'New' status and will be reset if the Payment Terms are changed. If the Payment Terms does not have a discount (e.g., "Net 30") this will default to 0.00000. Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. Database Fields: ERPx_MFPaymentTerms.DiscountPercent, APPOHeader.DiscountPercent |
Discount Days | This is a numeric textbox that identifies the Discount Days associated with the Payment Terms. This is editable and required if a Discount Percent is specified, if missing, the message "Discount Days is required" will be displayed on Save. The value must be >= 0 when specified. Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. Database Field: APPOHeader.DiscountDays |
Due Days | This is a numeric textbox that identifies the Due Days associated with the Payment Terms. This is always required and must be >= 0 and >= 'Discount Days' value, if missing the message "Due Days is required" will be displayed on Save. This is editable until the Purchase Order is Closed. Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. Database Field: APPOHeader.DueDays |
Group: 3 | |
Transaction Class ID | The unique identifier of the Transaction Class. This is required and comes from the 'Purchase Order Class' selected when the Purchase Order was initially created. This is not editable. Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each. Database Field: ERPx_APPoHeader.TransactionClassSK, ERPx_APTransactionClass.TransactionClassID |
Vendor ID | Identifies the ID of the Vendor account that is assigned to the transaction. This defaults from the 'Vendor ID' for the Vendor assigned to the Purchase Order. It can only be edited from the 'Vendor ID' field on the 'Properties' tab of the Vendor Record View, for the Vendor assigned to the Purchase Order. 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 |
Currency | Identifies the Currency assigned to the transaction. This is required and comes from the 'Currency' assigned on the 'Properties' tab of the Vendor Record View, for the Vendor assigned to the Purchase Order. 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_APPoHeader.CurrencySK |
Group: 4 | |
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. This is a non-editable text box that is required. Database Field: ERPx_APPoHeader.CreatedBy |
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. This is a system assigned value and is never editable by a user. This is a non-editable text box that is required. Database Field: ERPx_APPoHeader.CreatedDate |
Last Updated By | 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 is a non-editable text box that is required. Database Field: ERPx_APPoHeader.LastUser |
Last Updated | 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 is a non-editable text box that is required. Database Field: ERPx_APPoHeader.LastUpdated |
Transaction SK | Identifies the SK value of the Transaction. This is a non-editable text box that is informational only. Database Field: ERPx_APPoHeader.POHeaderSK |
Vendor SK | Identifies the SK value of the Vendor assigned on the Home Tab of the Purchase Order. This is a non-editable text box that is informational only. Database Field: ERPx_APPoHeader.VendorSK |
Attributes Tab
Fields | Description |
---|---|
Attributes | A non editable text box that shows the name of the Attribute. Attributes are user-definable fields that are used on master files and transactions and are editable from the Attributes List View. The Attribute will only be displayed if the Applies property on the Assign Attribute Rules by page is set to either "Yes - Required" or "Yes - Not Required". Attributes set to "No" will not be displayed. The Attributes displayed here are setup and assigned in the Attributes section of the Company module (Company → Setup → Attributes → Sales Order). |
Required | A non-editable text box that shows whether the Attribute Value is required or not. If the Attribute Value is required, it will display "Yes". If it is optional, it will display as blank. This value is only editable from the 'Assign Attribute Rules' page (Company → Setup → Attributes → AP Purchasing → Transactions hyperlink). |
Value | Identifies the value assigned to the corresponding attribute. Because Attributes are configurable as either Text, List, Date, or Date/Time the data entry is either a text box, lookup, or date picker. The value defaults to blank and is only required if the Attribute's 'Applies' property is set to "Yes - Required" in the Assign Attribute Rules page. Attribute Values for Master Flies are always editable. Attribute Values for transactions are always editable for unposted transactions. This is always editable until the Purchase Order is Closed. |
Page Details
Toolbar Icons | Description |
---|---|
Add Item | Adds a blank line in the grid to allow for data entry. If a valid Item ID is entered, the line will be saved. If not, the 'Item Lookup' window will open allowing users to search for the Item. |
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. |
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. |
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. |
Item Notes | Opens the Item Notes dialog, allowing users to enter Notes and/or attach files to the selected line item. If no line items are selected, the note(s) will be saved to all line items or appended to any existing Notes. Files can only be attached to a single selected line item. Item Notes can be added even after a transaction is posted. |
More Actions | Displays a drop down menu of related actions. The list of options includes:
|
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. |
Saved Layouts | 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. |
Remove Items | Removes the selected line(s). When clicked, you are prompted with the message "Are you sure you want to delete n item(s)? Okay or Cancel". This cannot be done on transactions with a Status of 'Approved', Ready to Post', 'Posted', 'Closed', 'Void', or 'Replaced'. Only line items, with an 'Line Source' of "Manual", that have not been invoiced or received can be removed. If a line item with a Line Source other than "Manual" is attempted to be removed, the message "Only lines with a Line Source of Manual can be removed." will be displayed. If a line item that has been Received or Invoiced is attempted to be removed, the message “Purchase Order Lines that are assigned to transactions cannot be deleted. (Transaction #)” will be displayed. |
Fields | Description |
Checkbox | Used 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' has been fully Invoiced. If the 'Amt. Invoiced' for the line item is >= the 'Amt. Ordered' for the item, 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. |
Amt. Fully Received | Identifies whether the 'Amt. Ordered' has been fully Received. If the 'Amt. Received' for the line item is >= the 'Amt. Ordered' for the item, 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. This is a calculated field and is not stored in the database. |
Amt. Ordered | Identifies the extended amount of the line item based on the ordered quantity. This is auto calculated as [Qty Ordered] x [Price]. This can only be updated by changing either the 'Qty Ordered' or 'Price'. This is formatted to the currency decimals on the Currency assigned to the Purchase Order Header Vendor. Database Field: ERPx_APPoLine.ExtendedAmount |
AP Amt. Posted | Identifies the sum of the extended amounts of the line item that have been included on "Posted" AP Invoices and AP Credit Memos. This is a calculated field, formatted to the currency decimals on the Currency assigned to the Purchase Order Header Vendor. 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 Qty Posted | Identifies the quantity of the line item that has been included on "Posted" AP Invoices and AP Credit Memos. This is a numeric text box that is auto updated and not editable. This is formatted to the Item's 'Unit Decimals' or 'Weight Decimals' depending on the Purchase Order 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 |
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 a single-select lookup that defaults as blank and is not required. This is only editable for line items with an 'Item Type' of "Manual" until the Purchase Order is 'Closed'. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Fishermen, Tenders, Loans, and Projects. |