Grower Accounting Tickets record the purchase of crops or aquaculture harvests. The purpose of this inquiry is to display Ticket items for all Tickets that have been posted.

This inquiry also contains columns for each Attribute that is set up under the 'Grower Accounting Items' Master File attribute type and the 'Grower Accounting' Transaction attribute type. Because these are user defined, they are not included in the default view but can be added a saved column layout. User configured attributes are not included in the help documentation.

Software Version: 2022.08.26 and newer

Page Header

Search

Filter Items	Description
Auto Hide Filters	A non-required text box that defaults as checked and is used to determine if the Search Options should be hidden when the Inquiry runs or is refreshed. When checked, each time the 'Refresh' button is clicked, the search options will be hidden, allowing for more rows of data to be visible on the page. This behavior is ideal for users that have entered their search parameters and want to see the results in full-screen. When unchecked, the search options will not be hidden when the 'Refresh' button is clicked. This behavior is ideal for users that need to run several searches with different search parameters. Users can only change the default value of this setting with a custom search in the "Saved Searches" lookup. If you change the default setting but do not save it in a custom search, it will only remain this way while the page is opened. Refer to this FAQ for advanced search options.
Auto Refresh on Open	A non-required text box that defaults as checked and is used to determine if the inquiry opens with or without data in the grid. When checked, each time the page is opened, the search is run using the default parameters (or a 'Saved Search' if one was set as your default for the page) so the grid will be populated with data . When unchecked, the search is NOT run when the page opens and no data will be present until the 'Refresh' button is clicked. Users can only change the default value of this setting with a custom search in the "Saved Searches" lookup. Refer to this FAQ for advanced search options.
Crop	Crops are used in Grower Accounting to identify the unique combination of Commodity and Variety. This is a multi-select lookup that is not required to return results. It defaults as "All".
Date Range	A text box to identify the method for selecting a date range, a specific date, or a min/max date. For help on using this control refer to the FAQ Article /wiki/spaces/HELP/pages/3108732991.
Date Type	A single-select lookup to identify which 'Date' field will be used. It defaults to 'GL Date' and the lookup contains the following values: Delivered Date Harvested Date GL Date
Farmer	A Farmer is an Account Type used to identify entities you purchase farmed products from. They are used in Grower Accounting master files and transactions. This is a multi-select lookup that is not required to return results. It defaults as "All".
Include	A lookup to assign one or more conditions you want included in your search. It defaults to 'Posted' and the lookup contains: Posted Repriced & Corrected Unposted Void
Item	Used to select one or more Items. This is a multi-select standard lookup that is not required to return results. It defaults as blank. Ticket Items are the unique objects that you purchase from Growers. They are used on Grower Accounting Tickets and Grower Accounting Price Lists. The lookup contains a list of all 'Active' Ticket Items.
Saved Searches	Displays the saved searches lookup and related icons. This tool allows users to select previously saved search options, create a new set of search options, save changes to existing search options, forget/delete saved search options and/or assign a saved search option as the default for the page. Once changes are made to the search options, the user can click the Save Options icon and save the changes. Saving search options will also save the preferences for 'Auto Refresh on Open' and 'Auto Hide Filters'. The new search option can also be set as the default. Default searches can be removed by clicking the 'Set as Default' button again when the current default search is selected. Refer to this FAQ for advanced search options.
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: Attr: [Attribute Value] (columns are not displayed by default in the grid, but may still be searched on) Crop Farmer Field Site: [Site ID] or [Site Name] Ticket Ticket Item Description Ticket Item ID
Site	Used to select one or more Sites. It displays as [Site Name]. This is a multi-select lookup that is not required to return results. It defaults as "All". Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. The lookup contains a list of all Sites.
Ticket Class	Used to select one or more Transaction Classes. The values in this lookup are listed alphabetically. This is a multi-select lookup that is not required to return results. It defaults as "All". 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 Grower Accounting Ticket Classes.

Page Detail

Toolbar Icons	Description
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.
Edit	Opens the selected record for editing. If a record is not selected, the message "Please select a row to edit." will be displayed.
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. 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.
New	Allows users to select the type of transaction or record they want to add.
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. 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 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.

Column Headers	Description
Checkbox	Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Accrual Amt.	A calculated field that summarizes the Accruals being applied to a Ticket Item. The detail Accruals can be viewed on the Charges & Accruals page. An 'Accrual Amount' can only be changed by either changing the 'Rate' for an Accrual (on the Charges & Accruals page) or by changing something that impacts the 'Delivered Wt.' and/or 'Gross Amt.' of a Ticket Item. Database Field: ERPx_CPTicketItem.AccrualAmount
Charge Amt.	A calculated field that summarizes the Charges being applied to a Ticket Item. The detail Charges can be viewed on the Charges & Accruals page. A 'Charge Amt.' can only be changed by either changing the 'Rate' for a Charge (on the Charges & Accruals page) or by changing something that impacts the 'Delivered Wt.' and/or 'Gross Amt.' of a Ticket Item. Database Field: ERPx_CPTicketItem.ChargeAmount
Crop	Identifies the Crop that was harvested from the Field assigned to the Ticket. This can only be edited when initially creating a ticket. Crops are used in Grower Accounting to identify the unique combination of Commodity and Variety. Database Field: ERPx_CPTicketHeader.CropSK
Delivered	Identifies the date the ticket was delivered. This can only be edited by editing the 'Delivered' field on the Ticket Record View for tickets that have not yet been Approved or Posted. Database Field: ERPx_CPTicketHeader.DeliveryDate
Farmer Class	Identifies the Class assigned to the Farmer on the ticket. This can only be edited from the Farmer Master File.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
Farmer ID	Identifies the ID of the Farmer that the ticket is assigned to. This can only be edited from the Vendor Master file. A Farmer is an Account Type used to identify entities you purchase farmed products from. They are used in Grower Accounting master files and transactions. Database Field: ERPx_APVendor.VendorID
Farmer Name	Identifies the Farmer that the ticket is assigned to. This can only be edited when initially creating a ticket. A Farmer is an Account Type used to identify entities you purchase farmed products from. They are used in Grower Accounting master files and transactions. Database Field: ERPx_CPTicketHeader.FarmerSK
Field	Identifies the Field the ticket was harvested from. This can only be edited when initially creating a ticket. Fields represent the objects farmers grow crops in. A field is unique by combination of: [Field Name] + [Farmer Name] + [Crop] + [Growth Method]. For Example, you can have Field #1 for Farmer ABC and for Farmer XYZ. Fields are used in Grower Accounting master files and transactions. Database Field: ERPx_CPTicketHeader.FieldSK
GL Date	Identifies the date the transaction posted (or will post) to the general ledger. This is required for the transaction to be approved or posted. It can be edited from the 'GL Date' field on the 'Properties' tab of the Ticket Record View for tickets that have not been Approved or Posted. Database Field: ERPx_CPTicketHeader.GLDate
GL Period	Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This is required for the transaction to be approved or posted. It is not directly editable. It can only be changed by editing the 'GL Date' field on the 'Properties' tab of the Ticket Record View for tickets that have not been Approved or Posted. This field is not stored in the database.
GL Year	Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This is required for the transaction to be approved or posted. It is not directly editable. It can be changed by editing the 'GL Date' field on the 'Properties' tab of the Ticket Record View for tickets that have not been Approved or Posted. This field is not stored in the database.
Gross Amt.	Displays the Extended Amount of the line item. 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
Harvested	Identifies the date the ticket was harvested. This can only be edited by editing the 'Harvested' field on the Ticket Record View for tickets that have not yet been Approved or Posted. Database Field: ERPx_CPTicketHeader.HarvestDate
Harvester	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
Hauler	Identifies who delivered 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. Haulers are used in Grower Accounting to identify the entity that delivered the crop to the plant, cooler, or co-packer. Database Field: ERPx_CPTicketHeader.HaulerSK
Item	Identifies the Item, displayed as Item ID: Item Description. This is required. Database Field: ERPx_CPTicketItem.ItemSK, ERPx_CPItem.ItemID, ERPx_CPItem.ItemDescription
Item Type	A text box to display the 'Item Type' assigned to the Ticket Item. This can only be edited from the Ticket Items Record View. Identifies the type of item and its behavior in the system. Grower Accounting Item Types fall under two categories: Dockage: To identify Items that are typically not purchased (e.g., dirt, foreign material, etc.) Item: To identify Items that you are purchasing. Database Field: ERPx_CPTicketItem.ItemSK, ERPx_CPItem.ILineTypeEN
Net Amt.	A calculated field that Identifies the net amount owed to the Grower/Farmer for the Ticket/ Ticket Item. This is calculated as: ([G ross 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
Net Wt.	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 editable from the Ticket Record View. Database Field: ERPx_CPTicketItem.TotalWeight
Paid Wt.	Identifies the weight of the line item with a non-zero price. 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. '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]. 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
Price	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
Price List	Identifies the Price List associated with the Farmer on the ticket. This can only be edited by changing the price list assigned to the farmer. Price Lists are used to store a group of Items with pre-defined prices and effective dates. Database Field: ERPx_CPTicketHeader.PriceListSK
Price UOM	Identifies the unit of measure which the line item's price is based upon. This can only be edited by changing the value selected in the "Scale Weight UOM" preference. Database Field: ERPx_MFPriceListItemHistory.PriceUOMSK
Purchase GL Account	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
Sample	Identifies the weight of the sample that graded out for the line item. This is required and can be edited from the Item's Grid on the Ticket Record View for tickets that have not been Approved or Posted. Database Field: ERPx_CPTicketItem.SampleWeight
Sample Pct.	Identifies the percentage of the entire sample that graded out for the line item. This is a calculated field and can be edited by editing the 'Sample Size' from the Item's Grid on the Ticket Record View for tickets that have not been Approved or Posted. Database Field: ERPx_CPTicketItem.SampleWeightPercent
Site Name	Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. This comes from the 'Site' lookup on the Ticket Record View. It is not editable. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. Database Fields: ERPx_MFSite.SiteName, ERPx_CPTicketHeader.SiteSK
Status	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 Inquiry 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
Ticket	Identifies the unique Transaction ID for each transaction. This is a system assigned value and is not editable. Clicking on this link opens the transaction record view. Database Field: ERPx_CPTicketHeader.TicketNumber
Ticket Class	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. Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each. Database Field: ERPx_CPTicketHeader.TransactionClassSK
Ticket 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_CPTicketHeader.CreatedDate
Ticket 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_CPTicketHeader.CreatedBy
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_CPTicketItem.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_CPTicketItem.LastUser
Units	Identifies the # of containers the Ticket Item was delivered in. This is not required and is editable until the Ticket is Approved or Posted. Database Field: ERPx_CPTicketItem.Units
Unpaid Wt.	Identifies the weight of the line item with a 0.00 price. 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. 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]. 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
Version	Identifies the version of the Ticket. A blank value signifies a version 1 ticket. All ticket versions greater than 1 will display. By default, a new transaction is set to Version 1. If the transaction has been voided, corrected or repriced, the version number will be incremented. In order for a transaction to have a version greater than 1 all the previous versions must be voided (a transaction can only have one active version). Database Field: ERPx_CPTicketHeader.TicketVersion

Page Header

Search

Filter Items

Page Detail

Toolbar Icons

Column Headers

Related Topics