The bolded view is the default view, which will determine the view will automatically display in when opened. 

Displays the Buying Station name assigned in the ticket properties. This is not required and can be edited from the 'Buying Station Name' field on the 'Properties' tab of the Fish Ticket Record View.

Database Field: ERPx_APDeliveryTicketHeader.BuyingStationName

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

A Yes/No value to show if the Ticket was delivered to the Dock. This is required and can be edited from the 'Dock Delivery' field on the 'Home' tab of the Fish Ticket Record View.

Database Field: ERPx_APDeliveryTicketHeader.DockDeliveryEN

Identifies the Extended Amount of the Ticket Item.

The 'Ext. Amount' is calculated as: [Weight] x [Price].

Identifies the period during which the fish ticket catch was made.  This is not required and can be edited from the 'Fishing Period' field on the 'Properties' tab of the Fish Ticket Record View.

Database Field: ERPx_APDeliveryTicketHeader.FishingPeriod

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 whether or not the fish were "floating" or suspended when they were offloaded. This is a Yes/No lookup that is required. It defaults to "No".  This is not required and can be edited from the 'Floating' field on the 'Properties' tab of the Fish Ticket Record View while the transaction is in a Status of New.

Floating is a quality field. If the fish are floating, in the water in the fish hold, that indicates they have been in there for awhile, and are of lower quality.

Database Field: ERPx_APDeliveryTicketHeader.Floating

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 Gross Amount of the Ticket Item.

The 'Gross Amount' is calculated as: [Ext. Amount] + [Premiums].

Database Field: ERPx_APDeliveryTicketLine.GrossAmount

Displays the nearest headland to where the fish were caught. This is not required and can be edited from the 'Headland' field on the 'Properties' tab of the Fish Ticket Record View.

Database Field: ERPx_APDeliveryTicketHeader.Headland

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 unique landing report number issued by eLandings. This is only required for eLandings tickets. It can be edited from the 'Landing #' field on the 'Properties' tab of the Fish Ticket Record View. 

Database Field: ERPx_APDeliveryTicketHeader.LandingNumber

Identifies the Last Updated Date & Time of the Transaction, 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.LastUpdated

Identifies the name of the user that last updated the Transaction. 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.LastUser

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 Net Amount of the Ticket Item.

The 'Net Amount' is calculated as: [Gross Amount] - [Tax - Fisherman].

Identifies the Net Weight of the Ticket Item.

The 'Net Weight' is calculated as: [Weight] * [Wt. Mod].

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

The GL Account that is assigned for the "Settlement Accrual" Account Type, on the Accounts tab of the Fisherman or Loan Record View and Fisherman Class Record View. This is the Balance Sheet account that is Debited or Credited when Fishing Transactions are posted for the selected Fisherman, Tender, or Loan account. 

The GL Account Description of the Payable Account. 

The GL Account that is assigned for the "Settlement Accrual" Account Type, on the Accounts tab of the Fisherman or Loan Record View and Fisherman Class Record View. This is the Balance Sheet account that is Debited or Credited when Fishing Transactions are posted for the selected Fisherman, Tender, or Loan account. 

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

Identifies the owner of the Permit (the fisherman) that was associated with the catch. This is a non-editable text box that is required. It defaults to the Permit Holder assigned the Permit selected on the New Delivery Ticket page.

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

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

Identifies if the Ticket Item has a "Chill" type Premium assigned. If so, it will display as "Yes". If not, it will be blank.

A 'Chill' Premium is defined as a Premium where the Premium's 'Program Class' has been assigned a Group of "Chill".

Identifies the dollar amount of the "Chill" type premiums assigned to the Ticket Item.

Identifies if the Ticket Item has a "Dock" type Premium assigned. If so, it will display as "Yes". If not, it will be blank.

A 'Dock' Premium is defined as a Premium where the Premium's 'Program Class' has been assigned a Group of "Dock".

Identifies the dollar amount of the "Dock" type premiums assigned to the Ticket Item.

Identifies if the Ticket Item has a "Other" type Premium assigned. If so, it will display as "Yes". If not, it will be blank.

An 'Other' Premium is defined as a Premium where the Premium's 'Program Class' has been assigned a Group of "Other".

Identifies the dollar amount of the "Other" type premiums assigned to the Ticket Item.

Identifies the ID of the Price List that is assigned to the transaction. This is not required and can be edited from the 'Price List' field on the 'Home' tab of the Fish Ticket Record View.

Displays the unit of measure upon which the line item price is based.

Identifies the processor identification code of the buyer. This is required and can be edited from the 'Processor ID' default preference or the 'Processor ID' field on the 'Properties' tab of the Fish Ticket Record View if no value is specified in the preference.

Database Field: ERPx_APDeliveryTicketHeader.ProcessorID

The GL Account assigned to the Ticket Line. This identifies the Expense Account that will be debited for the Ticket Item.

The GL Account Description of the Payable Account. 

The GL Account assigned to the Ticket Line. This identifies the Expense Account that will be debited for the Ticket Item.

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 which fishing season the delivery occurred in. This is not required and can be edited from the 'Season' field on the 'Properties' tab of the Fish Ticket Record View.

Database Fields: ERPx_APSeasons.SeasonName, ERPx_APDeliveryTicketHeader.SeasonSK

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 whether or not the fish were offloaded using a slide. This is a Yes/No Lookup that is required. It defaults to "No".  This is not required and can be edited from the 'Slide' field on the 'Properties' tab of the Fish Ticket Record View while the transaction is in a Status of New.

Slide is a quality field that indicates if the fish were transferred from the catcher vessel to the tender using a slide, which reduces handling and associated damage.

Database Field: ERPx_APDeliveryTicketHeader.Slide

Identifies whether the Fish Ticket was manually entered or imported from eLandings. This is a non-editable text box that is required. If the ticket was manually entered, it will be "Manual".  If the ticket was imported from eLandings, it will say "eLandings" + the elandings XML schema version (e.g. ELandings2.5).

Database Field: ERPx_APDeliveryTicketHeader.Source

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 if the Ticket Item has a "Borough Tax" assigned. If so, it will display as "Yes". If not, it will be blank.

A "Borough Tax" is defined as a Tax where the Tax Program's 'Program Class' has been assigned a Group of "Borough".

Identifies the dollar amount of the "Borough Tax" assigned to the Ticket Item.

Identifies if the Ticket Item has a "City Tax" assigned. If so, it will display as "Yes". If not, it will be blank.

A "City Tax" is defined as a Tax where the Tax Program's 'Program Class' has been assigned a Group of "City".

Identifies the dollar amount of the "City Tax" assigned to the Ticket Item.

Identifies if the Ticket Item has an "Observer Tax" assigned. If so, it will display as "Yes". If not, it will be blank.

An "Observer Tax" is defined as a Tax where the Tax Program's 'Program Class' has been assigned a Group of "Observer".

Identifies the dollar amount of the "Observer Tax" assigned to the Ticket Item.

Identifies if the Ticket Item has an "Other Tax" assigned. If so, it will display as "Yes". If not, it will be blank.

An "Other Tax" is defined as a Tax where the Tax Program's 'Program Class' has been assigned a Group of "Other".

Identifies the dollar amount of the "Other Tax" assigned to the Ticket Item.

Identifies if the Ticket Item has a "State Tax" assigned. If so, it will display as "Yes". If not, it will be blank.

A "State Tax" is defined as a Tax where the Tax Program's 'Program Class' has been assigned a Group of "State".

Identifies the dollar amount of the "State Tax" assigned to the Ticket Item.

Identifies the total amount of tax, from all the Tax Programs, for the Ticket Item. It is calculated as: [Tax - Fisherman] + [Tax - Company]

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

Displays the 'Vessel Name' of the Vessel assigned to the Tender.  This is not required and can be edited from the 'Primary Vessel' field in the 'Properties' tab of the Fishermen & Tenders record view for the selected Tender.

Database Fields: ERPx_APVessels.VesselName, ERPx_APVendor.TenderVesselSK, ERPx_APDeliveryTicketHeader.TenderDeliveredVendorSK

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

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

Displays the version number of the Fish Ticket. The version of a transaction will only be visible if it is greater than 1. This is a system assigned value and is required. It is not editable.

By default, a new transaction is set to Version 1. If the transaction has been voided, corrected or repriced, the version number will be incremented. In order for a transaction to have a version greater than 1 all the previous versions must be voided (a transaction can only have one active version). 

Database Field: ERPx_APDeliveryTicketHeader.Version

Identifies whether the ticket is the Original, a Correction, or a Reprice.

Identifies the gross weight of the item.

Identifies the weight modification that will manipulate the gross weight of the line item.