Fish Ticket Items are the individual items on a Fish Ticket. The purpose of this list view is to display Ticket Items on open (unposted) Fish Tickets. From here users can open the Ticket, Mass Update the Purchase GL Account for one or more Ticket Lines, and or use the More Actions menu to Void/Correct and/or run the Fish Ticket Item or Premium Reprice.

This list view also contains columns for each Attribute that is set up for the 'Fish Ticket Line' attribute type. Because these are user defined, they are not included in the default view but can be added a saved column layout.

Software Version: 2025.04.21 and newer

Page Header

Columns	Description
Toolbar Icons	Description
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.
Edit	Opens the selected record for editing. If a record is not selected, the message "Please select a row to edit." will be displayed.
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.
Favorites	Clicking on the star icon when it is an outline, adds the page to the 'My Shortcuts' tab and fills in the star. Clicking on the star icon when it is filled in (solid color), removes the page from the 'My Shortcuts' tab and returns the icon to an outline. Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.
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.
Help	Opens the online WIKI help page for the current page.
Mass Update	Opens the mass update dialog, which allows to mass update the following properties: Purchase Account
More Actions	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.
New	Allows users to select the type of transaction or record they want to add. 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 a blank record will be displayed, but a Fisherman with a permit for the class is required to proceed and create a Ticket record. The options display a list of all the 'Active' Ticket Classes setup in the system.
Print	Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. When clicked, all the Reports that launch from the Print Dialog that are assigned to this page, and that the user has rights to (if Report Data Access is enabled) are displayed.
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.
Refresh	Re-queries the contents of the grid/page based on the Search Options or the default values for grids that do not support Search Options. This ONLY re-queries the contents of columns that are currently visible, if you add a new column the contents will be empty until you click 'Refresh' again.
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.
Checkbox	Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Buying Station	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
CFECID	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
Chill Type	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
Condition	Identifies the Condition for the Fish Ticket Item. Conditions define the forms that fish can be in when delivered to a plant or after processing. The Condition is part of what makes a Fish Ticket Item unique (Specie + Condition + Disposition + Sold Condition + Grade). Database Fields: ERPx_APDeliveryTicketLine.DeliveryTicketItemSK, ERPx_APDeliveryTicketItem.SpecieSK, ERPx_APCondition. ConditionID + ERPx_APCondition. ConditionDescription
Created	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
Created By	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
Delivered	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
Delivery #	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 # This is required for the transaction to be approved or posted. It can be edited from the 'Delivery #' field on the 'Home' tab of the Fish Ticket Record View. Database Field: ERPx_APDeliveryTicketHeader.DeliveryNumber
Disposition	Identifies the 'Disposition' for the Fish Ticket Item. Dispositions define the intended use or disposal of the fish or shellfish. The most common disposition code is, 'Sold for Human Consumption' - code 60. Disposition codes can also indicate non-commercial disposal of catch. Examples of disposition codes include all discards of fish or shellfish at sea, or at the dock, fish or shellfish retained for personal use or bait, and discarded at sea or at the dock. The Disposition is part of what makes a Fish Ticket Item unique (Specie + Condition + Disposition + Sold Condition + Grade). Database Fields: ERPx_APDeliveryTicketLine.DeliveryTicketItemSK, ERPx_APDeliveryTicketItem.DispositionSK, ERPx_APDisposition. DispositionID + ERPx_APDisposition. DispositionDescription
Dock Delivery	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
Ext. Amount	Identifies the Extended Amount of the Ticket Item. The 'Ext. Amount' is calculated as: [Weight] x [Price].
Fishing Period	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
Fishing Vessel	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
Floating	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
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 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
GL Date	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
GL Period	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.
GL Year	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.
Grade	Identifies the Grade of the Fish Ticket Item. Grades define the size, color, and/or quality of the catch. They are part of what makes a Fish Ticket Item unique (Specie + Condition + Disposition + Sold Condition + Grade). Database Fields: ERPx_APDeliveryTicketLine.DeliveryTicketItemSK, ERPx_APDeliveryTicketItem.GradesSK, ERPx_APGrade. GradeID + ERPx_APGrade. GradeDescription
Gross Amount	Identifies the Gross Amount of the Ticket Item. The 'Gross Amount' is calculated as: [Ext. Amount] + [Premiums]. Database Field: ERPx_APDeliveryTicketLine.GrossAmount
Headland	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
Landed	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
Landing #	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
Last Updated	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
Last Updated By	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
Major Specie	Identifies the Major Specie that the Specie belongs to. A Major Species is used to identify a group of Species that belong together. Major Species are setup on the Specie List View. Database Fields: ERPx_APDeliveryTicketLine.DeliveryTicketItemSK, ERPx_APDeliveryTicketItem.SpecieSK, ERPx_APSpecie.MajorSpecie
Mgt. Prog.	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
Net Amount	Identifies the Net Amount of the Ticket Item. The 'Net Amount' is calculated as: [Gross Amount] - [Tax - Fisherman].
Net Weight	Identifies the Net Weight of the Ticket Item. The 'Net Weight' is calculated as: [Weight] * [Wt. Mod].
Paid Account	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
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.
Payable Account Description	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.
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 a non-editable text box that is required. It defaults to the Permit Holder assigned the Permit selected on the New Fish Ticket page. Database Fields: ERPx_APVendor.VendorSK.VendorName , ERPx_APDeliveryTicketHeader.PermitHolderVendorSK
Port of Landing	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
Prem - Chill	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".
Prem - Chill Amt	Identifies the dollar amount of the "Chill" type premiums assigned to the Ticket Item.
Prem - Dock	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".
Prem - Dock Amt	Identifies the dollar amount of the "Dock" type premiums assigned to the Ticket Item.
Prem - Other	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".
Prem - Other Amt	Identifies the dollar amount of the "Other" type premiums assigned to the Ticket Item.
Premiums	Displays the total amount of all the Premiums assigned to the Ticket Item.
Price	Identifies the Price assigned to the Ticket Item.
Price List ID	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. 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
Price UOM	Displays the unit of measure upon which the line item price is based.
Processor ID	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
Purchase Account	The GL Account assigned to the Ticket Line. This identifies the Expense Account that will be debited for the Ticket Item.
Purchase Account Description	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.
Reprice Comment	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
Season	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
Site Processed	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
Slide	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
Sold - Condition	Identifies the Condition the Fish Ticket Item was sold in. Conditions define the forms that fish can be in when delivered to a plant or after processing. The Condition is part of what makes a Fish Ticket Item unique (Specie + Condition + Disposition + Sold Condition + Grade). Database Fields: ERPx_APDeliveryTicketLine.DeliveryTicketItemSK, ERPx_APDeliveryTicketItem.SoldConditionSK, ERPx_APCondition. ConditionID + ERPx_APCondition. ConditionDescription
Source	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
Specie	Identifies the ID and Description of the Specie assigned to the Ticket Item. A Species is a group of similar fish or shellfish that can freely interbreed. When recording the species on an ADF&G fish ticket, the specific species code must be indicated, as it is very important for management purposes. The Specie ID is part of what makes a Fish Ticket Item unique (Specie + Condition + Disposition + Sold Condition + Grade). Database Fields: ERPx_APDeliveryTicketLine.DeliveryTicketItemSK, ERPx_APDeliveryTicketItem.SpecieSK, ERPx_APSpecie.SpecieID + ERPx_APSpecie.SpecieName
Status	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
Tax - Borough	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".
Tax - Borough Amt	Identifies the dollar amount of the "Borough Tax" assigned to the Ticket Item.
Tax - City	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".
Tax - City Amt	Identifies the dollar amount of the "City Tax" assigned to the Ticket Item.
Tax - Company	Identifies the total amount of tax, from all the Tax Programs, that is expensed to the Company.
Tax - Fisherman	Identifies the total amount of tax, from all the Tax Programs, that was/is being withheld from the Fisherman.
Tax - Observer	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".
Tax - Observer Amt	Identifies the dollar amount of the "Observer Tax" assigned to the Ticket Item.
Tax - Other	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".
Tax - Other Amt	Identifies the dollar amount of the "Other Tax" assigned to the Ticket Item.
Tax - State	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".
Tax - State Amt	Identifies the dollar amount of the "State Tax" assigned to the Ticket Item.
Tax - Total	Identifies the total amount of tax, from all the Tax Programs, for the Ticket Item. It is calculated as: [Tax - Fisherman] + [Tax - Company]
Tax Price	Identifies the Tax Price assigned to the Ticket Item. The Tax Price is the price used for calculating the tax basis amount.
Tender	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
Tender Vessel	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
Ticket #	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
Ticket Class	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
Ticket Item Description	Displays the Fish Ticket Item Description. Database Fields: ERPx_APDeliveryTicketLine.DeliveryTicketItemSK, ERPx_APDeliveryTicketItem.GeneratedItemDescription
Ticket Item ID	Displays the Fish Ticket Item ID. Database Fields: ERPx_APDeliveryTicketLine.DeliveryTicketItemSK, ERPx_APDeliveryTicketItem.ItemID
Units	Identifies the count of the physical objects (Box, Bag, Case, Each, Tote, etc.) on the transaction. Database Field: ERPx_APDeliveryTicketLine.Units
Units UOM	Identifies the unit of measure that the units are stored in (Box, Bag, Case, Each, Tote, etc.) for a line item or on the transaction. Database Fields: ERPx_APDeliveryTicketLine.UnitsUOMSK, ERPx_IMUOM.UOMID
Version	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
Version Type	Identifies whether the ticket is the Original, a Correction, or a Reprice.
Weight	Identifies the gross weight of the item.
Wt. Mod.	Identifies the weight modification that will manipulate the gross weight of the line item.

Page Header

Columns

Related Topics