Deletes the selected record(s). When clicked, users will be prompted with: "Are you sure you want to delete the selected records?". Click "OK" to confirm, or "Cancel" to return without deleting. 

_{WARNING: Records cannot be recovered once they are deleted!}

Opens the selected record for editing. If a record is not selected, the page will not open.

Export the contents of the list view 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. 

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. 

Opens the mass update dialog, which allows to mass update the following properties: 

Group: Chum/Red Split:

• Chum%: A text box that defaults to blank. When the NorthScope 'Chum %' Mass Update is applied, all selected tickets containing a ticket item with specie 460 (Mixed Fish) are updated by replacing the 460 item(s) with a matched set of specie 450 and 420 items. 

Group: Dates: 

• Delivery Date: A date picker that defaults to "(No Change)". Assigns the selected Delivery Date to selected/filtered Fish Tickets when Apply is clicked. 
• GL Date: A date picker that defaults to "(No Change)". Assigns the selected GL Date to selected/filtered Fish Tickets when Apply is clicked. 

Group: eLandings:

• eLandings Status: A single-select lookup that defaults to "(No Change)", but also has options for "Not Submitted", "Initial Report Submitted", "Final Report Submitted" and "Report Voided" that assigns the selected status to selected/filtered Fish Tickets when Apply is clicked; and an option "(Clear Value)" that when selected and Apply is clicked will remove the eLandings Status assigned to the selected Ticket(s).
• Submit to eLandings: A single-select lookup that defaults to "(No Change)", but also has an option "Yes" that will process selected/filtered tickets into the Outbound integration queue ready for submission to eLandings.  Note: The corresponding Ticket Class "Allow Submit to eLandings" property has to be set to "Yes" to allow tickets to be processed. 

Group: General:

• Change Price List and Update Prices: A single-select standard lookup that defaults to "(No Change)", but also contains a list of all active Price Lists configured in the Price List List View where the Price List Class is "Fish Ticket" that assigns the selected Price List and updates prices to selected/filtered Fish Tickets when Apply is clicked; and an option "(Clear Value)" that when selected and Apply is clicked will remove the Price List assigned to the selected Ticket(s) but leave the prices as they are. 
• Delivery #: A text box that defaults to blank.  Assigns the value entered, which must be <= 50 characters, for Delivery # to one or several tickets when Apply is clicked. 
• Dock Delivery: A single-select standard lookup that defaults to "(No Change)", but also has options for "Yes", "No" and "Not Specified". Assigns the selected value to specify whether or not the Fish were delivered directly to the Dock of the processor facility.
• Manual Premiums: A multi-select standard lookup that defaults to blank, but also contains a list of all active Premiums configured on the Fish Ticket Premiums List View that assigns the selected Premium(s) to selected/filtered Fish Tickets when Apply is clicked and an option "(Clear Value)" that when selected and Apply is clicked will remove all the Manual premiums that are currently assigned to the selected Ticket(s).  Premiums are only assigned to the ticket if the ticket meets all the premiums criteria (e.g. Specie, Gear, Stat Area). Click the Taxes & Premiums button from the Record View header toolbar to review all premiums assigned to the ticket. 
• Season: A single-select standard lookup that defaults to "(No Change)", but also contains a list of all active Seasons configured on the Seasons List View that assigns the selected Season to selected/filtered Fish Tickets when Apply is clicked; and an option "(Clear Value)" that when selected and Apply is clicked will remove the Season assigned to the selected Ticket(s). 
• Site Processed: A single-select standard lookup that defaults to "(No Change)", but also contains a list of all active Sites configured on the Sites List View that assigns the selected Site to selected/filtered Fish Tickets when Apply is clicked; and an option "(Clear Value)" that when selected and Apply is clicked will remove the Site assigned to the selected Ticket(s). 
• Stat Area (for single Stat Area Ticket only): A single-select standard lookup that defaults to "(No Change)", but also contains a list of all active Stat Areas configured on the Stat Area Master file that assigns the selected Stat Area to selected/filtered Fish Tickets when Apply is clicked; and an option "(Clear Value)" that when selected and Apply is clicked will remove the Stat Area as well as the % value assigned to the selected Ticket(s).    
• Tender: A single-select standard lookup that defaults to "(No Change)", but also contains a list of all active Tenders configured on the Fisherman & Tenders list view that assigns the selected Tender to selected/filtered Fish Tickets when Apply is clicked; and an option "(Clear Value)" that when selected and Apply is clicked will remove the Tender assigned to the selected Ticket(s).

Group: Status:

• Status: A single-select standard lookup that defaults to "(No Change)", but also has options for "New", "Approved" and "Ready to Post". Assigns the selected Status to selected/filtered Fish Tickets when Apply is clicked. 

Displays a drop down menu of related actions. The list of options includes:

• Void/Correct: Opens the Void/Correct Fish Ticket utility to allow users to void or correct one or more posted tickets.  
• /wiki/spaces/HELP/pages/1239253130: Opens the Fish Ticket Item Reprice utility to allow users to reprice ticket line items on one or more posted tickets.  
• Fish Ticket Premium Reprice: Opens the Fish Ticket Premium Reprice utility to allow users to reprice the Premiums attached to ticket line items on one or more posted tickets.    
• Split Fish Ticket: Opens the Split Ticket Record View to allow users to split a single fish ticket's line item(s) between two fishermen. Users must first select one fist ticket prior to selecting this option.

Allows users to select the class for the transaction they want to add. The list contains: all active Fish Ticket Classes. Selecting one opens a new Fish Ticket record that displays all the Fisherman with active permits for the corresponding ticket class. If no permits have been setup for any Fishermen for the selected ticket class then the blank record will be displayed, but a Fisherman with a permit for the class is required to proceed and create a Ticket record. 

Identifies the fisherman's unique identifier with the state of Alaska.  This is required for the transaction to be approved or posted. It can be edited from the 'CFECID' field on the 'Properties' tab of the Fish Ticket Record View.

Database Field: ERPx_APDeliveryTicketHeader.CFECID

Identifies the ID of the chill type. This is not required and can be edited from the 'Chill Type' field on the 'Home' tab of the Fish Ticket Record View. 

A Chill Type refers to the refrigeration system used to keep fish cold in the vessel hold. It is generally used in conjunction with Temperature. This is used to improve the quality of catch.

Database Fields: ERPx_APChillType. ChillTypeID, ERPx_APDeliveryTicketHeader.ChillTypeSK

Identifies the Created Date & Time of the record, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. This is required and is not editable.

Database Field: ERPx_APDeliveryTicketHeader.CreatedDate

Identifies the name of the user that created the record. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. This is required and is not editable.

Database Field: ERPx_APDeliveryTicketHeader.CreatedBy

Identifies the date the catch was delivered to the Plant. This is required and can be edited from the 'Delivered' field on the 'Home' tab of the Fish Ticket Record View.

 The Delivery Date can be also updated from the Tickets list view using the Mass Update tool. 

Database Field: ERPx_APDeliveryTicketHeader.DeliveryDate

A unique number used to group one or more Fish Tickets together. This number is used three different ways:

• If the ticket was delivered by a Tender, this represents the Tender Batch ID.
• For manually entered tickets, in Plants that log deliveries in a separate book, this is used to record the number from that book
• For all other integrated tickets, this represents the Landing #

Database Field: ERPx_APDeliveryTicketHeader.DeliveryNumber

Identifies the Extended amount of all the line items on the Fish Ticket. This is a calculated field that is not directly editable. It can be changed by editing the 'Weight', 'Weight Modifier' or 'Price' for a line item in the Items grid on the Fish Ticket Record View.

Database Field: ERPx_APDeliveryTicketLine.Amount

Identifies the vessel that caught the fish. This is not required and can be edited from the 'Fishing Vessel' field on the 'Home' tab of the Fish Ticket Record View.

Database Fields: ERPx_APVessels.VesselName, ERPx_APVessels.VesselNumber, ERPx_APDeliveryTicketHeader.VesselSK

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 can be edited from the 'Gear' field on the 'Home' tab of the Fish Ticket Record View.

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

Identifies the date the transaction posted (or will post) to the general ledger.  This is required for the transaction to be approved or posted. It can be edited from the 'GL Date' field on the 'Properties' tab of the Fish Ticket Record View.

Database Field: ERPx_APDeliveryTicketHeader.GLDate

Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This is required for the transaction to be approved or posted. It is not directly editable.  It can be changed by editing the 'GL Date' field on the 'Properties' tab of the Fish Ticket Record View. This field is not stored in the database.

Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This is required for the transaction to be approved or posted. It is not directly editable.  It can be changed by editing the 'GL Date' field on the 'Properties' tab of the Fish Ticket Record View. This field is not stored in the database.

Displays the total amount for all line items before taxes. This is a calculated field that is not directly editable. It can be changed by editing the 'Weight', 'Weight Modifier', 'Price' or 'Premium Rate' for a line item in the Items grid on the Fish Ticket Record View.

Database Field: ERPx_APDeliveryTicketLine.GrossAmount

Represents the Landed Date of the ticket. This is required and can be edited from the 'Landed' field on the 'Home' tab of the Fish Ticket Record View. 

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.

Database Field: ERPx_APDeliveryTicketHeader.TicketDate

Identifies the management program using the abbreviation and description. This is required for the transaction to be approved or posted. It can be edited from the 'Mgmt. Program' field on the 'Home' tab of the Fish Ticket Record View.

A Management Program is a unique fishery program with specific management strategies and/or allocation. Management programs that must be identified in the eLandings System include: IFQ, Adak crab and groundfish, CDQ (and specific ID number), AFA (and specific ID number), state managed groundfish, etc.

Database Fields: ERPx_APManagementPrograms.ManagementProgramID, ERPx_APManagementPrograms.ManagementProgramName,  ERPx_APDeliveryTicketHeader.ManagementProgramSK

Identifies the Fisherman Account that is being paid for the Fish Ticket. This is required and can be edited from the 'Paid Account' field on the 'Home' tab of the Fish Ticket Record View.

Database Fields: ERPx_APVendor.VendorName, ERPx_APDeliveryTicketHeader.FishermanAccountVendorSK

Identifies the location the fish or shellfish were unloaded. This is required and can be edited from the 'Port of Landing' field on the 'Properties' tab of the Fish Ticket Record View.

Database Fields: ERPx_APPort.PortDescription, ERPx_APDeliveryTicketHeader.PortSK

Price Lists are used to store a group of Items with pre-defined prices and effective dates.

Database Fields: ERPx_MFPriceListHeader.PriceListID, ERPx_APDeliveryTicketHeader.PriceListHeaderSK

Displays a comment regarding the reasoning or other notes about the reprice. This is only required if the Fish Ticket has been repriced. This field is not editable.

Database Field: ERPx_APDeliveryTicketHeader.RepriceComment

Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. This is required and can be edited from the 'Site Processed' field on the 'Home' tab of the Fish Tickets record view.

Database Fields: ERPx_MFSite.SiteName, ERPx_APDeliveryTicketHeader.SiteProcessedSiteSK

Identifies the Status of the transaction. This is required and can be edited from the 'Status' field on the 'Home' tab of the Fish Ticket Record View.

Status is used to identify where a transaction, Purchase Order, Price List, BOM, or Master File record is in its life cycle. Records start in a Status of 'New' and progress sequentially through additional statuses until they are 'Posted' or 'Closed'. The list of potential Statuses changes depending on the transaction type.  The Statuses that apply to transactions in this List View include:

New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist.  

Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned.

Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled with the exception any fields that are always editable and updates the Transaction Status to "Posted".

Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APDeliveryTicketHeader.TransactionStatusSK

Identifies the total amount of tax, from all the Tax Programs, that is expensed to the Company. This is a calculated field that is not directly editable. It can be changed by editing the 'Weight', 'Weight Modifier', 'Price', 'Premium Rate' or 'Company Rate' for a line item in the Items grid on the Fish Ticket Record View.

Fish Ticket Taxes represent money withheld from a fisherman and/or money accrued by the company to pay taxes associated with Fish Tickets. Fish Ticket Taxes can be a fisherman liability, company liability, or a liability for both. Taxes charged to the fishermen are withheld from each Fish Ticket and paid by the company. Taxes that are a company liability are accrued on each Fish Ticket so they can be paid at a later date. Fish Ticket Taxes are used on Fish Tickets in Fisherman Accounting and are automatically calculated based on a combination of applicable Species, Ticket Items, Stat Areas, Gear, Chill Type, Fishermen, Management Programs, and Site Processed. Each Fish Ticket items is evaluated against all active tax programs to calculate the correct tax amount.

Database Field: ERPx_APDeliveryTicketHeader.TotalCompanyTaxAmount

Identifies the total amount of tax, from all the Tax Programs, that was/is being withheld from the Fisherman. This is a calculated field that is not directly editable. It can be changed by editing the 'Weight', 'Weight Modifier', 'Price', 'Premium Rate' or 'Fisherman Rate' for a line item in the Items grid on the Fish Ticket Record View.

Fish Ticket Taxes represent money withheld from a fisherman and/or money accrued by the company to pay taxes associated with Fish Tickets. Fish Ticket Taxes can be a fisherman liability, company liability, or a liability for both. Taxes charged to the fishermen are withheld from each Fish Ticket and paid by the company. Taxes that are a company liability are accrued on each Fish Ticket so they can be paid at a later date. Fish Ticket Taxes are used on Fish Tickets in Fisherman Accounting and are automatically calculated based on a combination of applicable Species, Ticket Items, Stat Areas, Gear, Chill Type, Fishermen, Management Programs, and Site Processed. Each Fish Ticket items is evaluated against all active tax programs to calculate the correct tax amount.

Database Field: ERPx_APDeliveryTicketHeader.TotalFishermanTaxAmount

Identifies the total amount of tax, from all the Tax Programs, for all the Ticket Items. It is calculated as: [Tax - Fisherman] + [Tax - Company]. This is a calculated field that is not directly editable. It can be changed by editing the 'Weight', 'Weight Modifier', 'Price', 'Premium Rate', 'Company Rate' or 'Fisherman Rate' for a line item in the Items grid on the Fish Ticket Record View.

Fish Ticket Taxes represent money withheld from a fisherman and/or money accrued by the company to pay taxes associated with Fish Tickets. Fish Ticket Taxes can be a fisherman liability, company liability, or a liability for both. Taxes charged to the fishermen are withheld from each Fish Ticket and paid by the company. Taxes that are a company liability are accrued on each Fish Ticket so they can be paid at a later date. Fish Ticket Taxes are used on Fish Tickets in Fisherman Accounting and are automatically calculated based on a combination of applicable Species, Ticket Items, Stat Areas, Gear, Chill Type, Fishermen, Management Programs, and Site Processed. Each Fish Ticket items is evaluated against all active tax programs to calculate the correct tax amount.

Database Field: ERPx_APDeliveryTicketHeader.TotalTaxAmount

Identifies the Tender associated with the transaction. This is not required and can be edited from the 'Tender' field on the 'Home' tab of the Fish Ticket Record View.

A Tender is a vessel that is attendant to other vessels and is used to transport or ferry unprocessed fish or shellfish received from another vessel to a shoreside processor or mothership.  Tender vessels operate, in most circumstances, as an agent for a specific processor and take deliveries from harvesting vessels.

Database Fields: ERPx_APVendor.VendorName, ERPx_APDeliveryTicketHeader.TenderDeliveredVendorSK

Identifies the type of Fish Ticket associated with the transaction. This is required and is not 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 Fields: ERPx_APTransactionClass.TransactionClassID, ERPx_APDeliveryTicketHeader.TransactionClassSK

Identifies the Fish Ticket number (aka the Fish Ticket Transaction ID). The Ticket # can be manually assigned or can come from downloaded eLandings ticket numbers. Clicking on the link opens the Fish Ticket Record View for the selected record. This is required and can be edited from the 'Ticket #' field on the 'Home' tab of the Fish Ticket record view while the transaction is in a Status of New.

Database Field: ERPx_APDeliveryTicketHeader.TicketNumber