Grower Accounting Tickets record the purchase of crops or aquaculture harvests. The purpose of this page is to add, edit, remove, and post Grower Accounting Tickets.

Software Version: 2023.03.17 and newer

Page Header

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!}
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: RV: Charges & Accruals - Opens the Charges & Accruals record view. RV: Journal Details - Opens the Journal Details window showing the Journal Entry for this transaction. Until the transaction Approved or Posted, this is a temporary journal entry so no Journal ID will be assigned.
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), allowing the user to enter Notes for the selected line item. From here, users can add, review, or edit Notes associated with the line item. If no line items are selected, entered Notes will apply to all line items and be appended to any existing Notes. This toolbar icon is always enabled. 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.
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.
Save	Saves the changes made to the record.
Save & Close	Saves your changes and closes the page.

Home Tab

Fields	Description
Accruals	A calculated field that equals the sum of the 'Accruals' associated with all the Ticket Items. 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 equals the sum of the 'Charges' associated with all the Ticket Items. [Net Amount] = [Gross Amount] - [Charges] 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
Crop	A single select lookup to identify the 'Crop' on the Ticket. This is required and defaults from the Crop selected on the New Ticket Page. This is not editable after the initial save from the New Ticket page. Crops are used in Grower Accounting to identify the unique combination of Commodity and Variety. Database Fields: ERPx_CPCrop.Crop, ERPx_CPTicketHeader.CropSK
Delivered	A date picker to identify the date the Ticket was delivered to the 'Site'. This is required and defaults from the Delivered date entered on the New Ticket Page. This is editable until the Ticket is in a Status of Approved, Ready to Post, or Posted. Database Field: ERPx_CPTicketHeader.DeliveryDate
Delivered Weight	Error rendering macro 'excerpt-include' : No link could be created for 'Def - Net Weight'. 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
Field	A single select lookup to identify the 'Field' where the product came from. This is required and defaults from the Field selected on the New Ticket Page. This is not editable after the initial save from the New Ticket page. 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 Fields: ERPx_CPField.FieldName, ERPx_CPTicketHeader.FieldSK
Gross Amount	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 Weight	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	A date picker to identify the date the contents of the Ticket were harvested. This is required and defaults from the Harvested date entered on the New Ticket Page. This is editable until the Ticket is in a Status of Approved, Ready to Post, or Posted. Database Field: ERPx_CPTicketHeader.HarvestDate
Hold Code	A single select lookup to assign a 'Hold Code' to a Ticket. This defaults to blank and is not required. The lookup contains a list of all the Grower Accounting Hold Codes. This is editable until the Ticket is in a Status of Approved, Ready to Post, 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
Net Amount	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. Database Field: ERPx_CPTicketHeader.NetTicketAmount
Paid Weight	'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]. Database Field: ERPx_CPTicketHeader.PaidWeight
Price List	A single select lookup to identify the 'Price List' on the Ticket. This is not required and defaults from the Price List assigned to the Farmer. This is not editable after the initial save from the New Ticket page. Price Lists are used to store a group of Items with pre-defined prices and effective dates. Database Fields: ERPx_CPPriceListHeader.PriceListName, ERPx_CPTicketHeader.PriceListSK
Sample Size	A text box to record the Sample Size that was taken. This defaults from the 'Net Weight' but can be edited to any value <= the 'Net Weight' else the message "Sample Size cannot be greater than Net Weight" will be displayed on Save. Unless a user manually enters a 'Sample Size', it will always update from the 'Net Weight'. This is editable until the Ticket is in a Status of Approved, Ready to Post, or Posted. 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. Database Field: ERPx_CPTicketHeader.SampleWeight
Site Name	Identifies the name of the Site (warehouse) the transaction, shipment, or master file is associated with. This is a single select lookup that is required. This defaults from the sequence of 1) the Site selected on the New Ticket Page, 2) the Site setup as the 'Site Name' on the Field master file, or 3) the Site setup as the 'Default Site' on the Preferences page. The lookup contains the list of all active sites. This is editable until the Ticket is in a Status of Approved, Ready to Post, or Posted. Database Field: ERPx_MFSite.SiteName, ERPx_CPTicketHeader.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 until the transaction is posted. 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 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. 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 Fields: ERPx_CPTicketStatus.StatusName, ERPx_CPTicketHeader.TicketStatusSK
Total Tare	An editable text box to record the 'Total Tare' weight of delivery. This defaults to 0.00 and is not required. This is editable from either the 'Total Tare' field on the Home tab or by editing the details on the Tare tab. 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
Unpaid Weight	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
Weight In	An editable text box to record the inbound weight of the delivery. This defaults to 0.00 but must be >0 to approve or post a Ticket. This is editable until the Ticket is in a Status of Approved, Ready to Post, or Posted. 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] Database Field: ERPx_CPTicketHeader.WeightIn
Weight Out	An editable text box to record the outbound weight of the delivery vehicle. This defaults to 0.00 and is not required. This is editable until the Ticket is in a Status of Approved, Ready to Post, or Posted. 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] Database Field: ERPx_CPTicketHeader.WeightOut

Properties Tab

Property Name	Description
Group: Ticket
GL Date	Identifies the date the transaction posted (or will post) to the general ledger. This is a date picker that is required, defaults to blank and can be manually edited until the Ticket is in a Status of either Approved or Posted. If blank, when the Ticket is set to a Status of either 'Approved' or 'Ready to Post' it will be auto updated to match the Delivered date on the Home tab. In order to Approve or Post a ticket, the GL Date must fall within a Fiscal Period that open for Purchasing else the message "The Fiscal Period is not open." will be displayed. Database Field: ERPx_CPTicketHeader.GLDate
Ticket Version	Identifies the Version # of the Ticket. This is system assigned and is not editable. 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
Harvester	Identifies the 'Harvester' of the Ticket. This is not required and defaults from the New Ticket page. The lookup contains a blank value, the current assigned value, and a list of all 'Active' Harvesters. This can be edited until the Ticket is in a Status of either Approved or Posted. Harvesters are used in Grower Accounting to identify the entity that harvested the crop being purchased. Database Fields: ERPx_CPHarvester.HarvesterName, ERPx_CPTicketHeader.HarvesterSK
Hauler	Identifies the 'Hauler' of the Ticket. This is not required and defaults from the New Ticket page. The lookup contains a blank value, the current assigned value, and a list of all 'Active' Haulers. This can be edited until the Ticket is in a Status of either 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 Fields: ERPx_CPHauler.HaulerName, ERPx_CPTicketHeader.HaulerSK
Created Date	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
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
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

Tare Tab

The Tare tab is used to store and calculate the 'Total Tare' for a Ticket.

Toolbar Icons	Description
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!}
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.
New	Opens a new blank record for data entry.
Fields	Description
Checkbox	Used to select one or more records for Mass Update or Delete.
Container Tare	Identifies the empty container weight for containers that are of the same Container Type / Weight. This is not required and defaults to 0.00. This is used with the 'Number of Containers' to calculate the 'Total Container Tare' for each Container Type as [Number of Containers] * [Container Tare] = [Total Container Tare]. This is editable until the Ticket is Approved or Posted. Database Field: ERPx_CPTicketContainer.ContainerTare
Containers Per Pallet	An editable text box that can be optionally used to compute the 'Number of Containers' for each Pallet Type. For example, if each pallet contains 48 containers and there are 15 pallets, a user could enter '48' in the 'Containers Per Pallet' field and the system would compute '720' and put that value in the 'Number of Containers' field. This defaults to 0 and can be edited to any whole number that is >=0. If the user already knows the number of containers, they could leave this blank and enter the total in the 'Number of Containers' field. This is editable until the Ticket is Approved or Posted. Database Field: ERPx_CPTicketContainer.ContainersPerPallet
Number of Containers	An editable text box to identify the quantity of Containers that are of the same Container Type / Weight. This defaults to 0 and can be edited to any whole number that is >=0. This is used with the 'Container Tare' to calculate the 'Total Container Tare' for each Container Type as [Number of Containers] * [Container Tare] = [Total Container Tare]. This is editable until the Ticket is Approved or Posted. Database Field: ERPx_CPTicketContainer.NumberofContainers
Number of Pallets	An editable text box to identify the quantity of Pallets that are of the same Pallet Type / Weight. This defaults to 0 and can be edited to any whole number that is >=0. This is used with the 'Pallet Tare' to calculate the 'Total Pallet Tare' for each Pallet Type as [Number of Pallets] * [Pallets Tare] = [Total Pallets Tare]. This is editable until the Ticket is Approved or Posted. Database Field: ERPx_CPTicketContainer.NumberofPallets
Pallet Tare	Identifies the empty pallet weight for Pallets that are of the same Pallet Type / Weight. This is not required and defaults to 0.00. This is used with the 'Number of Pallets' to calculate the 'Total Pallet Tare' for each Pallet Type as [Number of Pallets] * [Pallets Tare] = [Total Pallets Tare]. This is editable until the Ticket is Approved or Posted. Database Field: ERPx_CPTicketContainer.PalletTare
Total Container Tare	A calculated field that identifies the total tare weight from the containers. This is calculated as ([Number of Containers] * [Container Tare]). To be calculated, both the 'Number of Containers' and 'Container Tare' fields are required to have values >0.
Total Pallet Tare	A calculated field that identifies the total tare weight from the pallets. This is calculated as ([Number of Pallets] * [Pallet Tare]). To be calculated, both the 'Number of Pallets' and 'Pallet Tare' fields are required to have values >0.
Total Tare	A calculated field that identifies the total tare weight from the Pallets and Containers. If one or more rows in the Tare gid has a 'Total Tare' value >0, then the 'Total Tare' for all the rows will be used as the Ticket Header's 'Total Tare'. Database Field: ERPx_CPTicketContainer.TotalTare

Attributes Tab

The Attributes tab is where Ticket Attributes are assigned to specific Ticket. If any required attributes are missing the Ticket cannot be Approved or Posted.

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 →Grower Accounting).
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 → Grower Accounting → 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 editable if the Transaction Class property 'Allow Attribute Edit After Approval' is set to "Yes".

Page Details

This grid shows each Ticket Item that is included on the Ticket. From Here, users can add, edit, or remove items.

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.
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.
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.
Notes	Opens the Notes dialog, filtered for the appropriate Note Type(s), allowing the user to enter Notes for the selected line item. From here, users can add, review, or edit Notes associated with the line item. If no line items are selected, entered Notes will apply to all line items and be appended to any existing Notes. This toolbar icon is always enabled.
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.
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'.
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.
Fields	Description
Checkbox	Used to select one or more records for Mass Update 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
Delivered 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. Database Field: ERPx_CPTicketItem.TotalWeight
Gross Amt.	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.'. Database Field: ERPx_CPTicketItem.GrossAmount
Item	Identifies the Item, displayed as Item ID: Item Description. This is required and cannot be edited (it can only be removed). Items can default on new Tickets or can be added by clicking the 'Add Item' button on the Grid Toolbar. Database Fields: ERPx_CPItem.ItemID - ItemDescription, ERPx_CPTicketItem.ItemSK
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. Database Field: ERPx_CPTicketItem.NetAmount
Price	Identifies the price of the line item. This is a numeric text box that is required. It defaults from the Price List assigned to the Ticket but can be edited until the Ticket is Approved or Posted. Database Field: ERPx_CPTicketItem.Price
Price UOM	Identifies the Price UOM for the Ticket Item. This is required and defaults from the 'Scale Weight UOM' preference. This cannot be edited from here. A UOM is a quantity used as a standard of measurement. It identifies how much makes up "1" of the measurement. Examples include Bag, Box, Each, Kg, Lb, ext. Database Fields: ERPx_IMUOM.UOMName, ERPx_CPTicketItem.UOMSK
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 a single-select lookup that defaults from the 'Purchase GL Account' assigned to the Ticket Item. This is required for any Ticket Item that has a Net Amount <> 0.00. This is editable until the Ticket is Approved or Posted. Database Fields: ERPx_GLAccount.AccountNumber - Description, ERPx_CPTicketItem.AccountSK
Sample	The Sample for the Ticket Item identifies the amount from the Ticket Header's 'Sample Size' that applies to the Ticket Item. The sum of the Samples from the Ticket Items must match the 'Sample Size' on the Ticket Header to Approve or Post a Ticket. This defaults as 0.00 and can be edited to any numeric value. If entered as a positive value, the value for 'Units' must be >=0. If entered as a negative value, the value for 'Units' must be <=0. The Ticket Items Sample Size is used to calculate the Ticket Items Net Weight. This is editable until the Ticket is Approved or Posted. Database Field: ERPx_CPTicketItem.SampleWeight
Sample Pct.	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 Ticket Item's 'Sample Size' or one of the Ticket Header Properties that impact the Ticket's Net Weight or Ticket's Sample Size. Database Field: ERPx_CPTicketItem.SampleWeightPercent
Units	Identifies the # of containers the Ticket Item was delivered in. This defaults as blank and is not required. If entered, it must be >=0. Units are saved to two decimal places. For example, if Strawberries were delivered in Freezer Trays this is where you would enter the count of Freezer Trays if it was important to retain. This is editable until the Ticket is Approved or Posted. Database Field: ERPx_CPTicketItem.Units