Ticket Class Record View (GA)

Ticket Classes are used to group tickets of a similar kind together for reporting and analysis. Ticket Classes are also used to identify default values and business rules. The purpose of this page is to add, edit, remove, and activate/inactive these records.

Software Version: 2023.03.17 and newer

Page Header

Toolbar IconsDescription
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! 

Help Opens the online WIKI help page for the current page. 
New Opens a new blank record for data entry.
Save Saves the changes made to the record. 
Save & Close Saves your changes and closes the page.
FieldsDescription
Ticket Class

Identifies the Ticket Class Name of the Ticket Class. This is a single select lookup that refreshes the page to show the details for the Class selected.

Database Field: ERPx_CPTransactionClass.TransactionClassDescription

Properties Tab 

Toolbar IconsDescription
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. 

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.
FieldsDescription
Group: ID and Description
Class ID

The unique identifier of the Ticket Class. This is a textbox that is required. It defaults to blank for new records. If not assigned, the message "Class ID is required." will be displayed on Save. This value must be unique. If not, the message "Duplicate Class ID values are not allowed." will be displayed on Save. This field is always editable and must be <= 25 characters. 

Database Field: ERPx_CPTransactionClass.TransactionClassID

Class Description

Identifies the Ticket Class Name of the Ticket Class. This is a textbox that is required. It defaults to blank for new records. If not assigned, the message "Class Description is required." will be displayed on Save. This field is always editable and must be <= 200 characters. 

Database Field: ERPx_CPTransactionClass.TransactionClassDescription

Group: Configuration
Doc Prefix

Identifies the prefix that will combine with the 'Next Document Number' field to create the Transaction ID for transactions belonging to the transaction class. This is a textbox that is not required.  It defaults to blank for new records and is always editable.  If a value is entered it must be <= 10 characters. 

Database Field: ERPx_CPTransactionClass.DocPrefix

Next Doc Number

Specifies the Next Document Number to be used in the Transaction ID. This is a textbox that is required and must be numeric.  It defaults to '1000' and is always editable. If a non-numeric value is entered the message “(TransactionClassID) - Next Doc Number must be numeric” will be displayed on Save. 

Database Field: ERPx_CPTransactionClass.NextDocNumber

Growth Method

Identifies the Growth Method associated with the Ticket Class. This is a single select lookup that is required.  

The lookup contains all the values in the CPGrowthMethod Enumeration Class. 

  • Organic
  • Conventional
  • N/A

Database Field: ERPx_CPTransactionClass.CPGrowthMethodEN

Inactive

Identifies if the record is "Inactive". If inactive (set to "Yes"), it will not be included in look-ups for transactions or other master files. If set to "No" or blank, the record is active and can be freely used.This is required and defaults to "No" (blank) and is always editable.

Database Field: ERPx_CPTransactionClass.IsInactive

Group: Inventory
Auto-Create Receipts from v1 Posted Tickets

Identifies whether or not a Receipt transaction will be created when Grower tickets are posted using the corresponding class.  This is a single select lookup that default to 'No' and is always editable.  If the value is set to 'No' the other Inventory properties are disabled and if a record was set to 'Yes' and then updated to 'No', all the Inventory property values will be cleared and become disabled.  If this property is set to 'Yes', all the Inventory properties will be enabled and are required on Save.  If there are items on the Grower ticket that have Linked Inventory Items assigned, a Receipt transaction will be created for these items when the ticket is Posted. 

Database Field: ERPx_CPTransactionClass.AutoCreateReceipt

Receipt Transaction Class

Identifies the Class that the Inventory Receipt transaction will use when it is created. This is a single select lookup that defaults to blank.  It is only required if the 'Auto-Create Receipts from v1 Posted Tickets' property is set to Yes.  

The lookup contains all the active Inventory Receipt Transaction Classes

Database Fields: ERPx_IMTransactionClass.TransactionClassID, ERPx_CPTransactionClass.IMTransactionClassSK

Create Production Batch as

Identifies how Production Batches will be assigned, to each line item, on auto-created Inventory Receipt Transactions for Lot Tracked Items. This is a single select lookup that defaults to blank.  It is only required if the 'Auto-Create Receipts from v1 Posted Tickets' property is set to Yes.  

The lookup contains the following values:

  • Ticket #: The Production Batch for every line item on the Receipt will default to the source transaction's Ticket #.
  • Delivery Date YYYY-MMThe Production Batch for every line item on the Receipt will default to the Year & Month of the source transaction's Delivered date (e.g., 2022-06)
  • Delivery Date YYYY-MM-DDThe Production Batch for every line item on the Receipt will default to the Year, Month, & Day of the source transaction's Delivered date (e.g., 2022-06-15)
  • Do not defaultThe Production Batch for every line item on the Receipt will default as blank. Note: If the 'Set Status as' property is set to either 'Approved' or 'Ready to Post' and one or more of the Linked Inventory Items are "Lot Tracked", Production Batch values are required, and an error message will be displayed when trying to Approve or Post the Grower ticket.

Database Field: ERPx_CPTransactionClass.CPCreateProductionBatchAsEN

Create Warehouse Lot as 

Identifies how Warehouse Lots will be assigned, to each line item, on auto-created Inventory Receipt Transactions when being received into a Warehouse Lot Tracked SiteThis is a single select lookup that defaults to blank. It is only required if the 'Auto-Create Receipts from v1 Posted Tickets' property is set to Yes.  

The lookup contains the following values:

  • IM Item ID: The Warehouse Lot for every line item on the Receipt will default to the Item ID of the Linked Inventory Item associated to the Ticket Item. For example, if Ticket Item ID 'ABC' was linked to Inventory Item of '20100', then the Warehouse Lot will be set to '20100'.
  • Do not default: The Warehouse Lot for every item on the ticket will default as blank. Note: If the 'Set Status as' property is set to either 'Approved' or 'Ready to Post' and the Receipt Site is Warehouse Lot tracked, Warehouse Lot values are required an error message will be displayed when trying to Approve or Post the Grower ticket.

Database Field: ERPx_CPTransactionClass.CPCreateWarehouseLotAsEN

Default Lot Owner

Identifies the Lot Owner that will be assigned to Lots on auto created Receipt transactions. This is a single select lookup that defaults to 'Use IM Default Owner' which populates the value that is saved in the 'Default Owner' Inventory preference. It is only required if the 'Auto-Create Receipts from v1 Posted Tickets' property is set to Yes. 

The lookup contains the values 'Use IM Default Owner' and all the Lot Owners setup in the master file.

Database Fields: ERPx_IMLotOwner.OwnerName, ERPx_CPTransactionClass.DefaultLotOwnerSK

Set Status as 

Identifies the Status that auto created Receipt transactions will be assigned.  This is a single select lookup that defaults to blank. It is only required if the 'Auto-Create Receipts from v1 Posted Tickets' property is set to Yes.  

The lookup contains the following values: 'New', 'Approved' and 'Ready to Post'. 

Database Fields: ERPx_IMTransactionStatus.TransactionStatusName, ERPx_CPTransactionClass.IMTransactionStatusSK

Crops Tab 

This tab is used to assign one or more 'Crops' to the Class. 

Toolbar IconsDescription
Add Item
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.
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 Item 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'.
FieldsDescription
CheckboxUsed to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Crop

A single select lookup to assign a Crop(s) to the Ticket Class. This defaults to blank on New and is required.  If not assigned the message "At least one Crop is required on a Ticket Class." will be displayed on Save. 

This lookup contains a list of all the records in the Crops Master List.

Database Field: ERPx_CPCrop.Crop

Related Topics



 Page Definitions

Page Definitions


 Technical Details

Technical Details