Grower Accounting Tickets record the purchase of crops or aquaculture harvests. The purpose of this list view is to display Tickets that have not been posted. From this list view, users may open the corresponding Ticket.

This list view also contains columns for each Attribute that is set up under 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

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.
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!}
Edit	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).
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.
Mass Update	Opens the mass update dialog, which allows to mass update the following properties: Ticket Status
More Actions	Displays a drop down menu of related actions. The list of options includes: Reprice/Correct - This allows users to reprice or correct one or more posted tickets.
New	Allows users to select the type of transaction or record they want to add.
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.
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.

Columns

Column Headers	Description
Checkbox	Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Accruals	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. A Grower Accounting Accrual is used to automate the recording expenses incurred as part of a Ticket. These are most often used to accrue for taxes, harvesting, or hauling expenses that will be paid by the company. Database Field: ERPx_CPTicketHeader.GrossAccrualsAmount
Charges	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. A Charge represents something that will be deducted (most often) from a Grower Ticket. Charges are most commonly used to deduct (pass along) fees associated with harvesting, hauling, and damaged / down-grade product. Database Field: ERPx_CPTicketHeader.GrossChargesAmount
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
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
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
Delivered Wt.	The 'Delivered Weight' describes the total weight of the "product" that was included in the shipment. It excludes the weight of the vehicle, packaging, and any other tare. It is calculated as [Gross Weight] - [Total Tare]. This is a calculated field that cannot be edited unless either the 'Weight In', 'Weight Out', or 'Total Tare' amounts are edited. Database Field: ERPx_CPTicketHeader.NetWeight
Farmer Class	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. Database Field: ERPx_APVendor.VendorClassSK
Farmer ID	Identifies the ID of the Farmer that the ticket is assigned to. This can only be edited by changing the 'Vendor ID' value on the Vendor Record View. 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 by changing the 'Vendor Name' value on the Vendor Record View. 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.	A calculated field that equals the sum of the extended amounts from all the Ticket Items. This is a calculated field that is only editable by changing the weights and/or prices of one or more ticket items. Database Field: ERPx_CPTicketHeader.GrossTicketAmount
Gross Wt.	The 'Gross Weight' describes the total weight that was offloaded from the vehicle. It includes tare weights for things like packaging, containers, and pallets. It is calculated as [Weight In] - [Weight Out]. This is a calculated field that cannot be edited unless either the 'Weight In' or 'Weight Out' amounts are edited. Database Field: ERPx_CPTicketHeader.GrossWeight
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
Hold Code	Identifies the Hold Code that has been assigned to the ticket. 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. Hold Codes are used to prevent a process from being performed or a transaction from being posted. Database Fields: ERPx_MFHoldCode.HoldCode, ERPx_CPTicketHeaderHold.HoldCodeSK
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_CPTicketHeader.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_CPTicketHeader.LastUser
Net Amt.	A calculated field that Identifies the net amount owed to the Grower/Farmer for the Ticket. This is calculated as: ([Gross Amount] - [C harges]). The 'Net Amount' will match the sum of the 'Net Amount' value for all Ticket Items. This is a calculated field and is not editable. Database Field: ERPx_CPTicketHeader.NetTicketAmount
Paid Wt.	'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' of a 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_CPTicketHeader.PaidWeight
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
Sample Size	The Sample Size identifies the total weight that was randomly selected from the delivery. Rather than testing everything on the load, Samples are taken and tested to determine various attributes of the load including, but not limited to, size and quality grades, commodities, and dockage. The results of the Sample are applied to the entire load. This is editable from the Home tab on the Ticket Record View for tickets that have not been Approved or Posted. Database Field: ERPx_CPTicketHeader.SampleWeight
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
Total Tare	Identifies the 'Total Tare' weight of delivery. This is not required and is editable from either the 'Total Tare' field on the Home tab or by editing the details on the Tare tab of the ticket record view. If the Tare is entered on the Tare tab, this field will populate from the detail totals and be disabled. If the Tare is being managed from the Home tab, it is editable until the Ticket is in a Status of Approved, Ready to Post, or Posted. The 'Tare Weight' describes the total weight of the packaging and any additional tare such as pallets. [Gross Weight] - [Tare Weight] = [Delivered Weight]. Database Field: ERPx_CPTicketHeader.ContainerTare
Units	Identifies the # of containers the Ticket Item was delivered in. This is not required and is editable from the Item's Grid on the Ticket Record View for tickets that have not been Approved or Posted. Database Field: ERPx_CPTicketHeader.Units
Unpaid Wt.	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_CPTicketHeader.UnpaidWeight
Version	Identifies the version of the Ticket. This is a system assigned value and is not editable. A blank value signifies a version 1 ticket. All ticket versions greater than 1 will display with a numeric value. 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
Weight In	The 'Weight In' describes the total weight of the shipment. It includes the weight of the product, packaging, and the vehicle weight. This is used in the calculation of 'Gross Weight' where [Weight In] - [Weight Out] = [Gross Weight] This can be edited from the 'Weight In' field on the Ticket Record View for tickets that have not yet been Approved or Posted. Database Field: ERPx_CPTicketHeader.WeightIn
Weight Out	The 'Weight Out' describes the total weight of the vehicle and occupants after it has been unloaded. This is used in the calculation of 'Gross Weight' where [Weight In] - [Weight Out] = [Gross Weight] This can be edited from the 'Weight Out' field on the Ticket Record View for tickets that have not yet been Approved or Posted. Database Field: ERPx_CPTicketHeader.WeightOut

NorthScope

Tickets List View

Page Header

Toolbar Icons

Columns

Column Headers

Related Topics