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: 2023.12.19 and newer

Page Header

Header Toolbar

Toolbar Icons	Description
Grid Layout	Opens the Saved Grid Layout menu that allows the user to select another saved layout, create a new layout, save changes to a layout, or assign a saved layout as the default for the page. Once changes are made to a grid, such as columns are added or removed, the user can click the Saved Grid Layout icon and save the changes to the grid layout and name the new layout. The new layout can also be set as the default, instead of the System View. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific). The bolded view is the default view, which will determine the view will automatically display in when opened.
Help	Opens the online WIKI help page for the current page. This icon is only visible on pages that are documented in the online help.
New	Allows the user to create a new master file record or transaction by opening a blank record view page. This icon is always enabled.
Save	Saves the changes made to the record. It is only necessary to click the Save button when a change is detected on the page. When a change has been made, a ‘ + ‘ character is displayed prior to the page name in the page title bar (light blue bar in the upper left corner of the page). Clicking Save reloads 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
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 only the filtered contents will be exported.
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 "Cannot insert the value NULL into column 'TransactionClassDescription', table 'ERPx_APTransactionClass'; column does not allow nulls. INSERT fails." 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
Rows to Create on New	Identifies the number of blank rows that will be added to the Fish Ticket Record View grid when the New button is clicked. This is a text box that is required. It defaults to "5" and must be a number between 1 and 25. If blank, it will be set to 5 and if set to any value other than 1 - 25, the message "Rows to Create on New must be between 1 and 25." will be displayed on Save. This field is always editable. Database Field: ERPx_APTransactionClass.RowsToCreateOnNew
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
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. This field 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 is updated to a value that 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.

Page Header

Header Toolbar

Properties Tab

Related Topics

Page Definitions

Technical Details

Browser not supported