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.

Opens 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). 

 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. 

A calculated field that identifies the delivered weight of the Ticket Item. This is calculated as: [Ticket Header Net Weight] * ([Ticket Items Sample] / [Ticket Header Sample Size]). This can only be edited by changing either the Ticket Item's 'Sample' or one of the Ticket Header Properties that impact the Ticket's Net Weight or Ticket's Sample Size.  This is a calculated field that cannot be edited unless:

• One or more of the following header values are edited: Weight In, Weight Out, or Total Tare
• One or more of the following ticket items values are edited: Sample or Sample Pct.

Database Field: ERPx_CPTicketItem.TotalWeight

Identifies the Class assigned to the Farmer. This can only be edited by changing the 'Vendor Class ID' value on the Vendor Record View.

Farmer Classes are used to identify default values that will be applied to new Farmer accounts and to group Farmers together for reporting purposes. 

Linked Database Field: ERPx_APVendor.VendorClassSK

A calculated field that Identifies the extended amount of the Ticket Item. This is calculated as: ([Delivered Wt.] * [Price]) and can only be changed by editing the Price or changing one of the other properties that impact 'Delivered Wt.'.  This is a calculated field and can only be edited by changing the weight or price of the line item.

Database Field: ERPx_CPTicketItem.GrossAmount

Identifies who harvested the crop. This is not required and can be edited on the 'Properties' tab of the Ticket Record View for tickets that have not been Approved or Posted.

Harvesters are used in Grower Accounting to identify the entity that harvested the crop being purchased.

Database Field: ERPx_CPTicketHeader.HarvesterSK

For Ticket Items - Identifies the Item, displayed as Item ID: Item Description.

For Charge and Accrual Items - Display the Program ID

Database Field: ERPx_CPTicketItem.ItemSK, ERPx_CPItem.ItemID, ERPx_CPItem.ItemDescription

Identifies the type of item and its behavior in the system. Grower Accounting Item Types fall under two categories: 

1. Dockage: To identify Items that are typically not purchased (e.g., dirt, foreign material, etc.)
2. Item: To identify Items that you are purchasing.

 This is not populated for rows where the 'Row Type' = 'Charge' or 'Accrual'.

Database Field: ERPx_CPTicketItem.ItemSK, ERPx_CPItem.ILineTypeEN

A calculated field that Identifies the net amount owed to the Grower/Farmer for the Ticket/ Ticket Item. This is calculated as: ([Gross Amt.] - [Charge Amt.]). The sum of the 'Net Amt.' value for each Ticket Item will match the 'Net Amount' on the Ticket Header.  This is a calculated field and is not editable.

Database Field: ERPx_CPTicketItem.NetAmount

'Paid Weight' describes the weight that was included in the 'Net Weight' that is being paid for or deducted (items with a non-zero price). [Delivered Weight] - [Unpaid Weight] = [Paid Weight].
 This can only be edited by editing the 'Price' on the ticket line on the Ticket Record View for tickets that have not yet been Approved or Posted. 

 Note: Paid Weight is calculated for line-items with a non-zero Price. Items with a negative price are considered 'paid'.

Database Field: ERPx_CPTicketItem.PaidWeight

Identifies the price of the line item. This can only be edited by editing the 'Price' on the ticket line on the Ticket Record View for tickets that have not yet been Approved or Posted. 

Database Field: ERPx_CPTicketItem.Price

Identifies the account number and description of the GL Account that is used for the Item when it is entered on a Ticket. This is required for any Ticket Item that has a Net Amount <> 0.00. This is editable from the Item grid on the Ticket Record View until the Ticket is Approved or Posted.

Database Fields: ERPx_GLAccount.AccountNumber - Description, ERPx_CPTicketItem.PurchaseGLAccountSK

The 'Sample Pct.' represents the percentage of the total Sample that is applied to a Ticket Item. This is a calculated field that can only be edited by changing either the 'Sample' or 'Sample Pct.' on a Ticket Item.

Database Field: ERPx_CPTicketItem.SampleWeightPercent

Identifies the Status of the transaction. This comes from the 'Status' on the 'Home' tab of the Ticket Record View. It is not editable. 

Status is used to identify where a transaction, Purchase Order, Price List, BOM, or Master File record is in its life cycle. Records start in a Status of 'New' and progress sequentially through additional statuses until they are 'Posted' or 'Closed'. The list of potential Statuses changes depending on the transaction type.  The Statuses that apply to transactions in this List 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.  

Received: Used to indicate the difference between a scheduled Ticket and one that have been Received. While in the Status of 'Received' 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.

Graded: Used to indicate the difference between a Ticket that has been Received and one that has had the sample taken and graded. While in the Status of 'Graded' 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.

Reviewed: Used to indicate a Ticket that has been reviewed for accuracy. While in the Status of 'Reviewed' 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.

Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned.

Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled with the exception any fields that are always editable and updates the Transaction Status to "Posted".

Database Field: ERPx_CPTicketHeader.TicketStatusSK, ERPx_CPTicketStatus.StatusName

The unique identifier of the Transaction Class. This comes from the 'Transaction Class' value selected by the user when the transaction was created. It is not editable.

The 'Unpaid Weight' describes the weight that was included in the 'Delivered Weight' that is not being paid for (items with a price of 0.00). This most often represents dockage/waste material that is being sorted out. [Delivered Weight] - [Unpaid Weight] = [Paid Weight].
This can only be edited by editing the 'Price' of a ticket line on the Ticket Record View for tickets that have not yet been Approved or Posted.

 Note: Unpaid Weight is only calculated for line-items with a 0.00 Price. Items with a negative price are not considered 'Unpaid'.

Database Field: ERPx_CPTicketItem.UnpaidWeight