Ticket Classes are used to group tickets of a similar kind together for reporting and analysis. Ticket Classes are used to identify the types of Fish Tickets supported and the default values and business rules for each. They are required for all Fishermen Permits. Ticket Classes also store additional properties that describe how the ticket interfaces with third party applications such as eLandings. The purpose of this page is to set the properties of Transaction Classes used for Fish Tickets. Users may also view, add, remove and inactivate Transaction Classes.

Software Version: 2025.04.21 and newer

Page Header

Header Toolbar

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.
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.
Fields	Description
Class	Identifies the Fish Ticket Class as [Ticket Class ID] - [Description]. This is a single-select standard lookup that is required once a Ticket Class has been saved. It defaults to blank for a new Ticket Class. This field is always editable after initial Save. When users update the value selected in this field, the Ticket Class Record View will automatically refresh to display the Properties for the selected Ticket Class. This lookup contains all Fish Ticket Classes. Database Fields: ERPx_APTransactionClass.TransactionClassID - ERPx_APTransactionClass.TransactionClassDescription where ERPx_APTransactionClass.TransactionTypeSK = 7.

Properties Tab

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.
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.
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.
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.
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
Properties	Identifies the Property that is being set up.
Value	A text box or lookup to set the value of the property. Property values are always editable and can be changed at any time, unless otherwise specified.
Group: Setup
Ticket Class	The unique identifier of the Transaction Class. This is a text box that is required. It defaults as blank and must be <= 50 characters. If missing, the message "Transaction Class is required." will be displayed on Save. This value must be unique, else the message "No Duplicate Transaction ID values allowed." will be displayed on Save. This field is always editable. Ticket Classes are used to group tickets of a similar kind together for reporting and analysis. Ticket Classes are used to identify the types of Fish Tickets supported and the default values and business rules for each. They are required for all Fishermen Permits. Ticket Classes also store additional properties that describe how the ticket interfaces with third party applications such as eLandings. Database Field: ERPx_APTransactionClass.TransactionClassID
Description	Identifies the (Long) Description for the Transaction Class. This is a text box that is required. It defaults as blank and must be <= 200 characters. If missing, the message "Description is required" will be displayed on Save. If the value exceeds 200 characters, the message "Description cannot have more than 200 characters." will be displayed on Save. This field is always editable. Database Field: ERPx_APTransactionClass.TransactionClassDescription
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 text box that is not required. It defaults as blank and must be <= 10 characters. If the value exceeds 10 characters, the message "Document Prefix cannot have more than ten characters." will be displayed on Save. This field is enabled and always editable if the 'ADFG Landing Type' field is set to "DOES NOT INTEGRATE". Else, this field is disabled. The 'Doc Prefix' is used in conjunction with the 'Next Ticket Number' to auto assign ticket numbers. This feature is typically used for non Alaska Fish Tickets that are manually entered. System assigned ticket numbers are created by stringing together the [Doc Prefix] and [Next Ticket Number]. The next ticket number is auto incremented each time a system assigned number is used. System assigned numbers cannot be used on Ticket Classes with an ADFG Landing Type Assigned as these numbers are controlled by eLandings. Database Field: ERPx_APTransactionClass.DocPrefix
Next Ticket Number	Identifies the numerical suffix that will be appended to the 'Document Prefix' field to create unique Transaction IDs for transactions belonging to the Transaction Class. This is a counter that increases by 1 every time a new transaction is created for the Transaction Class. This is a text box that is required. This defaults as blank. If missing or not a numeric whole number, the message "Next Ticket Number must be a positive whole number." will be displayed on Save. This field is enabled and always editable if the 'ADFG Landing Type' field is set to "DOES NOT INTEGRATE". Else, this field is disabled. The 'Doc Prefix' is used in conjunction with the 'Next Ticket Number' to auto assign ticket numbers. This feature is typically used for non Alaska Fish Tickets that are manually entered. System assigned ticket numbers are created by stringing together the [Doc Prefix] and [Next Ticket Number]. The next ticket number is auto incremented each time a system assigned number is used. System assigned numbers cannot be used on Ticket Classes with an ADFG Landing Type Assigned as these numbers are controlled by eLandings. Database Field: ERPx_APTransactionClass.NextDocNumber
Number of RSW Readings	Identifies the number of Refrigerated Sea Water (RSW) Temperature rows that will be displayed on the 'RSW Temp' tab of the Fish Ticket Record View. This is a text box that is required. It defaults to "3" and must be a number between 1 and 20. If blank, it will be set to 3 and if set to any value other than 1 - 20, the message "Number of RSW Readings must be between 1 and 20." will be displayed on Save. This field is always editable. Database Field: ERPx_APTransactionClass.NumberOfRSWReadings
Default Site Processed	Identifies the default value of the 'Site Processed' field in the 'Home' tab of a newly created or imported Fish Ticket with the Ticket Class. This is a single-select standard lookup that is not required. It defaults as blank and is always editable. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. The lookup contains a blank value and list of all active Sites. Database Fields: ERPx_MFSite.SiteID, ERPx_MFSite.SiteName, ERPx_APTransactionClass.DefaultSiteSK
Require Chill Type before Approval	Identifies whether or not the Chill Type is required for a Fish Ticket to be Approved or Posted. This is a Yes/No lookup that is required. It defaults to "No" and is always editable. Database Field: ERPx_APTransactionClass.RequireChillTypeBeforeApproval
Require Stat Area Before Approval	Identifies whether or not a Stat Area is required for a Fish Ticket to be Approved or Posted. This is a Yes/No lookup that is required. It defaults to "Yes" and is always editable. Database Field: ERPx_APTransactionClass.RequireStatAreaBeforeApproval
Single Date Management	A Yes/No lookup to select whether or not the Delivery and Fishing Began dates on a Fish Ticket default from the Landed Date. This defaults to "No" for new records and is always required. This field is always editable. When this property is set to “Yes”, users can only enter and edit the 'Landed Date' field on the 'Fish Ticket - New Delivery Ticket' page and on the Fish Ticket Record View. The Delivery Date and Fishing Began fields will be disabled. No other date fields are affected by this property. The following date fields will default from the Fish Ticket Landed Date: Delivery Date Fishing Began Database Field: ERPx_APTransactionClass.SingleDateManagement
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 a Yes/No lookup that is required. It defaults as "No" and is always editable. Database Field: ERPx_APTransactionClass.IsInactive
Group: Pricing
Default Price List	Identifies the ID of the Price List to be defaulted on a new Fish Ticket created with the Fish Ticket Class. This is a single-select standard lookup that is not required. It defaults to blank and is always editable. The lookup contains a blank value and list of all active Fish Ticket Price Lists. Database Fields: ERPx_MFPriceListHeader.PriceListID, ERPx_APTransactionClass.DefaultPriceListHeaderSK
Group: ADFG
ADFG Landing Type	Identifies the Landing Type that integrates with eLandings. This is a single-select standard lookup that is required. It defaults to “DOES NOT INTEGRATE”, which means the Ticket Class will not integrate with eLandings. This field is always editable. If the value already exists on another Ticket Class, then the message "No Duplicate Landing Types allowed." will be displayed on Save. The lookup contains the value "DOES NOT INTEGRATE" and all values in the ERPx_APDeliveryTicketADFGLandingType table displayed as [LandingTypeID] - [LandingTypeName]. Database Field: ERPx_APTransactionClass.ADFGLandingType
Allow Import of Missing or Inactive Fishermen	Identifies whether or not to allow the import of missing or inactive Fishermen. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Fisherman will be automatically added on Import. This field defaults to "No" and is always editable. Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveFishermanImport
Allow Import of Missing or Inactive Permits	Identifies whether or not to allow the import of missing or inactive Permits. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Permits will be automatically added on Import. This field defaults to "Yes" and is always editable. Database Field: ERPx_APTransactionClass.AllowMissingOrInactivePermitImport
Allow Import of Missing or Inactive Fish Ticket Items and Components	Identifies whether or not to allow the import of missing or inactive Fish Ticket Items and Components. Components include Specie, Conditions, Dispositions, and Grades. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Fish ticket Items and Components will be automatically added on Import. This field defaults to "Yes" and is always editable. Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveFishTicketItemAndComponentImport
Allow Import of Missing or Inactive Chill Types	Identifies whether or not to allow the import of missing or inactive Chill Types. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Chill Types will be automatically added on Import. This field defaults to "Yes" and is always editable. Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveChillTypeImport
Allow Import of Missing or Inactive Gears	Identifies whether or not to allow the import of missing or inactive Gears. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Gears will be automatically added on Import. This field defaults to "Yes" and is always editable. Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveGearImport
Allow Import of Missing or Inactive Management Programs	Identifies whether or not to allow the import of missing or inactive Management Programs. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Management Programs will be automatically added on Import. This field defaults to "Yes" and is always editable. Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveManagementProgramImport
Allow Import of Missing or Inactive Ports	Identifies whether or not to allow the import of missing or inactive Ports. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Ports will be automatically added on Import. This field defaults to "Yes" and is always editable. Database Field: ERPx_APTransactionClass.AllowMissingOrInactivePortImport
Allow Import of Missing or Inactive Stat Areas	Identifies whether or not to allow the import of missing or inactive Stat Areas. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Stat Areas will be automatically added on Import. This field defaults to "Yes" and is always editable. Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveStatAreaImport
Allow Import of Missing or Inactive Vessels	Identifies whether or not to allow the import of missing or inactive Vessels. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Vessels will be automatically added on Import. This field defaults to "Yes" and is always editable. Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveVesselImport
Allow Submit to eLandings	Identifies whether or not to allow tickets to be submitted to eLandings. This is a Yes/No lookup that is required. If the property is set to "Yes", then tickets can be submitted from the Fish Ticket List View Mass Update "Submit to eLandings" property. This field defaults to "No" and is always editable. Database Field: ERPx_APTransactionClass.AllowELandingsExport

Page Header

Header Toolbar

Properties Tab

Related Topics

Page Definitions

Technical Details