Fish Ticket - New Fish Ticket

Fish Ticket - New Fish Ticket

 Fish tickets document the harvest of fish and shellfish sold, discarded, or retained by the fisherman for personal use. All licensed processors must fill out a fish ticket for each landing from a fishing permit holder. Fish tickets are a record of purchase between the processors (or buyers) and the fishermen, and for the resource managers, they are a record of how many fish were taken from the sea. The information collected includes species landed, weight, gear used, harvest dates, who caught the fish, and the processor’s license code. Information specific to each fishery is also collected when the catch is delivered. The purpose of this page is to select the Permit Holder (Fisherman) to create the Fish Ticket record.  From here users can enter a Ticket Number and the Delivery / Landed dates and select a Permit Holder for the corresponding ticket. Only one Permit Holder can be selected at one time. 

Software Version: 2025.04.21 and newer

Page Header

Toolbar IconsDescription
Help Opens the online WIKI help page for the current page. 
Save Saves the changes made to the record. 
Save & Close Saves your changes and closes the page.
Fields Description
Delivery Date

Identifies the date the catch was delivered to the Plant.  This is a date picker that defaults to the current date. It is required and if missing, the message "Delivery Date is required" will be displayed on Save. This field must be on or after the Landed Date. If not, the message "Delivery Date must be greater than or equal to Landed Date" will be displayed on Save. 

If Single Date Management is enabled on the corresponding Ticket Class, the Delivery Date will default from the Landed Date and be disabled. 

Database Field: ERPx_APDeliveryTicketHeader.DeliveryDate

Landed Date

Identifies the date fish or shellfish are off-loaded or trans-shipped from the catcher vessel to the first purchaser. The date of landing is the day off-load is completed. For catcher-processors the land date is the date the product is caught and brought on board. For catcher-seller vessels the land date is the date the product is initially brought into port. This is date picker that defaults to the current date.  It is required and if missing, the message "Landed Date is required" will be displayed on Save.  This field must be on or before the Delivery Date, else the message "Delivery Date must be greater than or equal to Landed Date" will be displayed on Save.

If Single Date Management is enabled on the corresponding Ticket Class, the Landed Date will determine the values for the Delivery Date and Fishing Began date. 

Database Field: ERPx_APDeliveryTicketHeader.TicketDate

Ticket Number

Identifies the Fish Ticket number (aka the Fish Ticket Transaction ID). This is a text box that defaults to "(Use Next Number)" and is required else the message "Ticket Number is required" will be displayed on Save.  For tickets that are integrated from ADF&G using eLandings the next available number will be used for the associated class.  However, for manually entered tickets if a Ticket Number is not specified the message "You are creating a delivery ticket that is managed by ADF&G but do not have any Delivery Ticket Numbers available. Please download more Delivery Ticket Numbers for this ticket class and try again." will be displayed on Save.  When a value is entered, the value must be <= 50 characters. 

Database Field: ERPx_APDeliveryTicketHeader.TicketNumber

Page Detail

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

FieldsDescription
CFECID

Identifies the fisherman's unique identifier with the state of Alaska.  This is required and defaults from the 'CFECID' field on the 'Properties' tab of the Fisherman & Tenders Record View. This is never editable from here but can be changed on the master file at any time. 

Database Field: ERPx_APDeliveryTicketHeader.CFECID

Gear

Identifies the Gear Type for the ticket. Gear is the specific apparatus or equipment used to catch fish or shellfish. A few examples of gear include: longline, pots, beam trawl, and purse seine. This is required and defaults from the 'Gear' field on the 'Permits' tab of the Fisherman & Tenders Record View. This is never editable from here but can be changed on the master file at any time. 

Database Fields: ERPx_APGear.GearDescription, ERPx_APVendorPermit.GearSK, ERPx_APDeliveryTicketHeader.VendorPermitSK

Paid Account

Identifies the Fisherman Account that is being paid for the Fish Ticket. This is required and defaults from the 'Alternate Paid Account' field on the 'Properties' tab of the Fisherman & Tenders Record View. This is never editable from here but can be changed on the master file at any time. 

Database Fields: ERPx_APVendor.VendorName, ERPx_APDeliveryTicketHeader.FishermanAccountVendorSK

Permit

Identifies the permit number that is associated to the Permit Holder. This is required and can be edited from the 'Permit' field on the 'Permits' tab of the Fishermen & Tenders Record View.

A permit issued annually to the designated vessel operator that allows participation in open access or limited entry fisheries managed by the state of Alaska. All shellfish fisheries off-shore Alaska are managed, fully or jointly, by the state of Alaska. Fishery permits are issued annually for specific fisheries. Any commercial activity in state waters requires the operator to obtain a CFEC permit, including harvesting, landing of catch, selling product, or transshipping of catch. Open access fishers obtain an interim use permit. Limited access fisheries such as salmon, herring, and selected shellfish fisheries require a limited entry permit. All members of the crew are required to obtain a crew license to participate in commercial fishing. CFEC permit cards are issued to an individual, even if that individual is fishing for a Rationalized Crab cooperative or a CDQ group. The CFEC permit card must be current for the calendar year and appropriate to the area, gear and harvest

Database Fields: ERPx_APVendorPermit.Permit, ERPx_APDeliveryTicketHeader.VendorPermitSK

Permit Holder

Identifies the owner of the Permit (the fisherman) that was associated with the catch. This is required and defaults from the 'Vendor Name' field on the 'Properties' tab of the Fisherman & Tenders Record View. This is never editable from here but can be changed on the master file at any time. 

Database Fields: ERPx_APVendor.VendorSK.VendorName , ERPx_APDeliveryTicketHeader.PermitHolderVendorSK

Vessel

identify the fishing vessel the Fishing Permit pertains to. This is required and defaults from the 'Gear' field on the 'Permits' tab of the Fisherman & Tenders Record View. This is never editable from here but can be changed on the master file at any time. 

Database Fields: ERPx_APVessels.VesselName + ERPx_APVessels.VesselNumber, ERPx_APVendorPermit.VesselSK, ERPx_APVendor.VendorSK, ERPx_APDeliveryTicketHeader.VesselSK

Year Seq

Identifies the Year Sequence assigned to the Fishing Permit. For Permits that are renewed annually, this will be the only value that changes. This is required and defaults from the 'Year Seq' field on the 'Permits' tab of the Fisherman & Tenders Record View. This is never editable from here but can be changed on the master file at any time. 

Database Fields: ERPx_APVendorPermit.YearSequence, ERPx_APVendor.VendorSK, ERPx_APDeliveryTicketHeader.VendorPermitSK

Related Topics

Entering New Fish Tickets (UG)


 Page Definitions

Page Definitions


 Technical Details

Technical Details