Purchase Order Record View
Software Version: 2024.05.20 and newer
Page Header
Header Toolbar
Toolbar Icons | Description |
---|---|
Delete | 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 | |
More Actions |
_
|
New | 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 | Note Types of "Purchase Order" saved to the Vendor will default on the Purchase Order Notes. |
Save | |
Save & Close |
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 |
Database Field: ERPx_APPoHeader.Description |
Ordered |
Database Field: ERPx_APPoHeader.PODate |
PO # |
Database Field: ERPx_APPoHeader.PurchaseOrderID |
PO Type |
This lookup contains all the values in the APPOType Enumeration Class. Database Field: ERPx_APPoHeader.POTypeEN |
Requisition # |
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 |
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. This lookup contains a list of all active Sites. Database Fields: ERPx_MFSite.SiteID, ERPx_APPoHeader.SiteSK |
Status |
The Statuses that apply to transactions in this Record View include: 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 |
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 |
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 |
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) |
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 |
Database Field: ERPx_APPoHeader.TransactionClassSK, ERPx_APTransactionClass.TransactionClassID |
Vendor ID |
Database Fields: ERPx_APVendor.VendorID, ERPx_APPoHeader.VendorSK |
Currency |
Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_APPoHeader.CurrencySK |
Group: 4 | |
Created By |
Database Field: ERPx_APPoHeader.CreatedBy |
Created |
Database Field: ERPx_APPoHeader.CreatedDate |
Last Updated By |
Database Field: ERPx_APPoHeader.LastUser |
Last Updated |
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 |
Attributes Tab
Fields | Description |
---|---|
Attributes |
|
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 |
|
Page Details
Toolbar Icons | Description |
---|---|
Add Item | |
Add Vendor Item | |
Column Filter Show/Hide | |
Excel | |
Group By Show/Hide | |
Item Notes | |
More Actions |
|
Quick Column Filter | |
Saved Layouts | |
Remove Items |
|
Fields | Description |
Checkbox | |
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 |
The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Fishermen, Tenders, Loans, and Projects. This defaults to "Single Invoice and Receipt" and is not editable for Freight Purchase Orders. Database Fields: ERPx_APVendor.VendorName, ERPx_MFEmployee.EmployeeName, ERPx_GLProject.ProjectDescription, ERPx_APPoLine.ToDistributionAccountSK |
IM Amt. Posted | Identifies the sum of the extended amounts of all the line item that have been included on "Posted" AP Invoices, AP Credit Memos, and IM Receipts. This is a calculated field, formatted to the currency decimals on the Currency assigned to the Purchase Order Header Vendor. When IM Receipts, with line items that reference a Purchase Order are posted, this value is updated as [Qty Received] * [PO Item Price]. 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. Database Field: ERPx_APPoLine.ReceivedAmount |
IM Qty Posted | Identifies the quantity of the line item that has been included on "Posted" IM Receipts. 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 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 'Qty Received' value is updated from posted AP Invoices and Credit Memos that reference the Purchase Order Item. Database Field: ERPx_APPoLine.ReceivedQty |
Item Description |
Database Fields: ERPx_IMItem.ItemDescription, ERPx_APPoLine.ItemSK |
Item ID |
When the 'Add Item' icon is clicked, users may enter all or part of an Item ID or Description and hit the Enter key on the keyboard. If a complete Item ID was entered, the line item will be saved, if not, the Item Lookup dialog box will open with a list of items containing the data entered. From the Item Lookup dialog box, users may check the checkbox next to one or multiple item(s) to add to the transaction using the Save & Close button. Database Fields: ERPx_IMItem.ItemID, ERPx_APPoLine.ItemSK |
Item Type |
Database Fields: ERPx_IMItemType.Description, ERPx_IMItem.ItemTypeSK |
Line Comment |
When AP Invoices and Credit Memos, and IM Receipts are loaded from a PO, this will default as the 'Line Comment' on those transactions. Database Field: ERPx_APPoLine.LineComment |
Line Description |
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 |
Line Source | A non-editable textbox that displays where the corresponding line item originates from. This is required and never editable. The available options include:
Database Field: ERPx_APPoLine.LineSourceEN |
Line Vendor |
This feature is used when more than 1 vendor is required to complete the Purchase Order. For example, on PO-123 you are purchasing 2 different Item Codes of packaging from ACME PACKAGING for $2,200. However, the order will be delivered by ABC DELIVERY who will be invoicing you separately for $150. Using this feature, you can add all 3 lines to the same Purchase Order and assign "ABC Delivery" as the 'Item Vendor' for the 'FREIGHT' line. When you enter the invoice from ACME PACKAGING it will auto load with only the 2 Item Codes and when you enter the invoice from ABC DELIVERY it will auto load with only the freight item. This helps ensure more visibility to all your costs while reducing the chance of overpaying for something. 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: ERPx_APVendor.VendorName, ERPx_APPoLine.VendorSK |
Ln. |
For example, if you had line items 10, 20, and 30 and you wanted the last one (Ln. 30) to be second, you could edit the value to any number between 10 and 20 (i.e. 15) and on save the lines would be sorted in the new sequence (10, 15, and 30) and then all Ln.'s would be re-set to base 10 numbers (10, 20, 30). Database Field: ERPx_APPoLine.LineNumber |
Price |
When AP Invoices and/or Credit Memos are loaded from a PO, the 'Price' will default from the current Purchase Order Item's Price. Database Field: ERPx_APPoLine.Price |
Purchase GL Account |
The Account can be easily updated using the quick replacement feature, for information on how this works please see this FAQ. 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_GLAccount.Description, ERPx_APTransactionLine.AccountSK, ERPx_APPoLine.AccountSK |
Qty Fully Invoiced | Identifies whether the 'Qty Ordered' has been fully Invoiced. If the 'Qty Invoiced' for the line item is >= the 'Qty Ordered' for the item, 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 Items have quantities that have not yet been invoiced. This is a calculated field and is not editable or stored in the database. |
Qty Fully Received | Identifies whether the 'Qty Ordered' has been fully Received. If the 'Qty Received' for the line item is >= the 'Qty Ordered' for the item, 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 Items have quantities that have not yet been invoiced. This is a calculated field and is not editable or stored in the database. |
Qty Ordered | Identifies the quantity of the line item being ordered. This is a numeric text box that defaults to 0 and must be > = 0. It is formatted to the Item's 'Unit Decimals' or 'Weight Decimals' depending on the UOM. This is only editable for line items with an 'Item Type' of "Manual" until the Purchase Order is 'Closed'. If the line item is a Fixed Weight item that requires whole units, then on Save:
These alerts are only displayed where applicable for new lines being added, or if an existing line Quantity or UOM are being updated. An Item is a 'Fixed Weight' item that requires whole units when the following properties are set as:
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_APPoLine.OrderedQuantity |
UOM |
The lookup contains all 'Active' UOMs on the selected Item's UOM Schedule. When AP Invoices and Credit Memos are loaded from a PO, the 'UOM' will default from the Purchase Order Item's UOM. Database Fields: ERPx_IMUOM.UOMName, ERPx_APPoLine.QuantityUOMSK |
Related Topics
Configuring and Managing Freight Management
Freight Purchase Order Edit Rules