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.

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

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

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

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

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

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