Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Ticket Classes are used to identify the types of Fish Tickets supported and the default values and business rules for each. They are used in Fishermen Accounting and are required for all Fishermen PermitsThe purpose of this page is to add, edit, remove, and activate/inactive these records.

...

Table of Contents
typeflat

Page Header

Toolbar IconsDescription
Delete
Insert excerpt
Delete - LV
Delete - LV
nopaneltrue
Edit
Insert excerpt
Edit - LV
Edit - LV
nopaneltrue
Excel
Insert excerpt
Excel - Global (old)
Excel - Global (old)
nopaneltrue
Favorites
Insert excerpt
Favorites Add/Remove - Global
Favorites Add/Remove - Global
nopaneltrue
Grid Layout
Insert excerpt
Grid Layout - Global
Grid Layout - Global
nopaneltrue
Help
Insert excerpt
Help - Global
Help - Global
nopaneltrue
New
Insert excerpt
New - Global
New - Global
nopaneltrue
FieldsDescription
CheckboxUsed to select one or more records for delete or mass update.
ADFG Landing Type

Identifies the eLandings Landing Type the Ticket Class is associated with. This is only used for tickets that import from eLandings. This is the field used to link an eLandings ticket to a NorthScope Ticket Class. This defaults to "DOES NOT INTEGRATE" for new records but can be changed to any value in the list but if changed, duplicates are not allowed. If you are changing to a value that already exists on another ticket class, the message "No Duplicate Landing Types allowed" will be displayed on Save.

The list contains the following values:

  • DOES NOT INTEGRATE
  • B - Salmon: Used for Salmon Landings
  • C - Crab: Used for Crab Landings
  • G - Groundfish: Used for GroundfishLandings
  • T - Troll: Used for Troll Landings

The lookup contains all the values in the ERPx_APDeliveryTicketADFGLandingType table displayed as [LandingTypeID] - [LandingTypeName]

Linked Database Field: ERPx_APTransactionClass.ADFGLandingType

Default Price List

Identifies the Price List that will be auto assigned to Fish Tickets. This defaults to blank and is not required. If set, this Price List will be auto-assigned to newly created or imported Fish Tickets. This is always editable from the record view.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Price Lists with a 'Price List Class' of "Fish Ticket".

Linked Database Field: ERPx_APTransactionClass.DefaultPriceListHeaderSK

Default Site Processed

Identifies the value that will be will be auto-assigned as the 'Site Processed' on newly created or imported Fish Tickets. This defaults to blank, is not required, and duplicate values are allowed.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Sites from the ERPx_MFSite table.

Linked Database Field: ERPx_APTransactionClass.DefaultSiteSK

Description

The 'Description'

property 

properton the Ticket Class record.

 This

 This defaults to blank for new records but is required. If missing, the message "Description is required." will be displayed on Save.

 This

 This field is always editable from the record

view and must

view and must be <= 200 characters. 

The Description is used as a long description/name of the Ticket Class.

Linked Database Field: ERPx_APTransactionClass.TransactionClassDescription

Doc Prefix

Identifies the value in the 'Doc Prefix' property on the record

view

view.

This defaults (lightbulb) System assigned numbers cannot be used on Ticket Classes with an ADFG Landing Type Assigned as these numbers are controlled by eLandings.

This defaults to blank for new records and is not required.

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. 

Insert excerpt
Def - Document Prefix - Fish Tickets
Def - Document Prefix - Fish Tickets
nopaneltrue

This field is always editable from the record view

 

and must be <= 10 characters. 

Linked Database Field: ERPx_APTransactionClass.DocPrefix

Inactive

A Yes/No field used to identify if the record is Inactive. If set to 'Yes' then the record is "Inactive" and will not be included in look-ups for transactions or other master files. If set to 'No' then the record is "Active" and can be freely used

Linked Database Field: ERPx_APTransactionClass.IsInactive

Next Ticket Number

Identifies the value in the 'Next Ticket Number' property

on

on the record view.

This defaults

This defaults to blank for new records, is required. If missing, the message "Next Ticket Number is required"

 will

 will be displayed on Save. The value must be a numeric whole number. If not, the message "Error converting data type nvarchar to bigint."

 will

 will be displayed on Save

The 'Next Ticket Number' is used in conjunction with the 'Doc Prefix' 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. 

(lightbulb) System assigned numbers cannot be used on Ticket Classes with an ADFG Landing Type Assigned as these numbers are controlled by eLandings.

Insert excerpt
Def - Document Prefix - Fish Tickets
Def - Document Prefix - Fish Tickets
nopaneltrue

This field is always editable from the record view. However, setting this to a lower number may result in errors caused by duplicate transaction numbers.

Linked Database Field: ERPx_APTransactionClass.NextDocNumber

Rows to Create on New

Identifies the value in the 'Rows to Create on New' property on the record view.

This defaults

This defaults to 5 for new records, is required, and must be between 1 and 25.

  If

  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

 will be displayed on Save.

The 'Rows to Create on New' controls how many blank rows will be added when the New icon is clicked on the Ticket Items grid.

This field is always editable from the record view. 

Linked Database Field: ERPx_APTransactionClass.RowsToCreateOnNew

Ticket Class

A hyperlink that shows the value of the 'Ticket Class' property on the Ticket Class record. Clicking on the link opens the record view for the selected Ticket Class. 

This defaults to blank for new records and is required. If not assigned, the message "Transaction Class is required." will be displayed on Save.

 This

 This value must be unique. If not, the message "No Duplicate Transactions ID values allowed." will be displayed on Save.

 This

 This field is not editable after the initial

Save and must

Save and must be <= 50 characters. 

Linked Database Field: ERPx_APTransactionClass.TransactionClassID

Related Topics



Expand
titlePage Definitions

Page Definitions


...