Ticket Line Stat Area History Inquiry

Fish Ticket Items are the individual items on a Fish Ticket. The purpose of this inquiry is to display Ticket Items, on posted Fish Tickets, by Stat Area and ratio of lbs caught for each. Users may utilize search options to filter the results. From this inquiry, users can open the Ticket, Journal Details, Ticket Reprice, or the Void/Correct page.

(lightbulb) This inquiry also contains columns for each Attribute that is set up for the Fisherman Accounting → Fish Ticket transactions. Because these are user defined, they are not included in the default view but can be added a saved column layout.

Software Version: 2023.08.31 and newer

Page Header

Filter Items

Description
Auto Hide FiltersA non-required text box that defaults as checked and is used to determine if the Search Options should be hidden when the Inquiry runs or is refreshed.
  • When checked, each time the 'Refresh' button is clicked, the search options will be hidden, allowing for more rows of data to be visible on the page. This behavior is ideal for users that have entered their search parameters and want to see the results in full-screen. 
  • When unchecked, the search options will not be hidden when the 'Refresh' button is clicked. This behavior is ideal for users that need to run several searches with different search parameters.

Users can only change the default value of this setting with a custom search in the "Saved Searches" lookup. If you change the default setting but do not save it in a custom search, it will only remain this way while the page is opened.

Refer to this FAQ for advanced search options.

Auto Refresh on OpenA non-required text box that defaults as checked and is used to determine if the inquiry opens with or without data in the grid.
  • When checked, each time the page is opened, the search is run using the default parameters (or a 'Saved Search' if one was set as your default for the page) so the grid will be populated with data .  
  • When unchecked, the search is NOT run when the page opens and no data will be present until the 'Refresh' button is clicked. 

Users can only change the default value of this setting with a custom search in the "Saved Searches" lookup.

Refer to this FAQ for advanced search options.

Date Type

A single-select lookup to identify which 'Date' field will be used. The lookup contains the following values:

  • Delivered Date
  • GL Date
  • Landed Date
Date RangeA text box to identify the method for selecting a date range, a specific date, or a min/max date.

For help on using this control refer to the FAQ Article /wiki/spaces/HELP/pages/3108732991.

HelpOpens the online WIKI help page for the current page. 

(lightbulb) This icon is only visible on pages that are documented in the online help.

Include

A lookup to assign one or more conditions you want included in your search. This lookup contains:

  • Voids. Select if you want Items from Voided Tickets. Defaults as unselected.
Saved SearchesDisplays the saved searches lookup and related icons. This tool allows users to select previously saved search options, create a new set of search options, save changes to existing search options, forget/delete saved search options and/or assign a saved search option as the default for the page. Once changes are made to the search options, the user can click the Save Options icon and save the changes. Saving search options will also save the preferences for 'Auto Refresh on Open' and 'Auto Hide Filters'. The new search option can also be set as the default.  Default searches can be removed by clicking the 'Set as Default' button again when the current default search is selected.  

Refer to this FAQ for advanced search options.

Search

A non-required text box that defaults to blank and is used to search across multiple fields. When the page is 'Refreshed', the data returned will be limited by what was included in the Search box (in addition to any other Search Options). 

Refer to this FAQ for advanced search options.

The Search field can be used to search across the following fields: 

  • Ticket
  • Delivery #
  • Site Processed ID
  • Ticket Class
  • Permit
  • Fishing Vessel
  • Tender
Stat Area

A text box to enter all or part of a Stat Area. 

A Stat Area (or Statistical area) is the five or six-digit ADF&G statistical code denoting a specific area of catch. Statistical areas are unique to the fishery "type". For example, there are unique statistical areas for salmon, herring, and shellfish/groundfish harvests. Also referred to as 'stat area.' Groundfish and shellfish (except Southeast Alaska) utilize a six-digit stat area number loosely based on latitude and longitude.

Version

A single select lookup to specify which Ticket Version(s) to return. The options include:

  • All Versions. Use this method if you want all versions of the the ticket.
  • Current Posted Version. Use this method if only want to return the 'Current' version of the the ticket. This is the default value.

Page Detail

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

(lightbulb) 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. 
More Actions

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

  • RV: Journal Details: Opens the Journal Details page. 
  • Item Reprice: Opens the 'Fish Ticket Items Reprice' page.
  • Premium Reprice: Opens the 'Fish Ticket Premium Reprice' page.
  • Void/Correct: Opens the 'Void/Correct Fish Ticket' page.
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. 

(lightbulb) 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.

Search Options Toggles between displaying and hiding the Search Options portion of the page.
FieldsDescription
CheckboxUsed to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
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

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

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.

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

Database Field: ERPx_APDeliveryTicketHeader.DeliveryDate

DeliveryTicketLineSK

Identifies the unique identifier of the line item.

Database Field: ERPx_APDeliveryTicketLine.DeliveryTicketLineSK

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 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

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 PeriodIdentifies 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 YearIdentifies 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

Item ID

Displays the Fish Ticket Item ID.

Database Fields: ERPx_APDeliveryTicketLine.DeliveryTicketItemSK, ERPx_APDeliveryTicketItem.ItemID

Item ID Description

Displays the Fish Ticket Item Description.

Database Fields: ERPx_APDeliveryTicketLine.DeliveryTicketItemSK, ERPx_APDeliveryTicketItem.GeneratedItemDescription

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

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

Net Amount

Identifies the Net Amount of the Ticket Item. The 'Net Amount' is calculated as: [Gross Amount] - [Tax - Fisherman].

Database Field: ERPx_APDeliveryTicketLine.NetAmount

Net Weight

Identifies the Net Weight of the Ticket Item. The 'Net Weight' is calculated as: [Weight] * [Wt. Mod].

Database Field: ERPx_APDeliveryTicketLine.NetWeight 

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. 

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_APVendor.SAGLAcctRef, ERPx_DeliveryTicketHeader.FishermanAccountVendorSK 

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. 

Database Fields: ERPx_GLAccount.Description, ERPx_APVendor.SAGLAcctRef, ERPx_DeliveryTicketHeader.FishermanAccountVendorSK 

Percent

Identifies the percent of the catch from the Stat Area.

Database Fields: ERPx_APDeliveryTicketStatArea.Percent, ERPx_APDeliveryTicketHeader.DileverTicketHeaderSK

PremiumsDisplays the total amount of all the Premiums assigned to the Ticket Item.
Price

Identifies the Price assigned to the Ticket Item.

Database Field: ERPx_APDeliveryTicketLine.Price

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.

Database Fields: ERPx_IMUOM.UOMID, ERPx_APDeliveryTicketLine.PriceUOMSK 

Purchase Account

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

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_APDeliveryTicketLine.PurchaseGLAccountSK

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.

Database Fields: ERPx_GLAccount.Description, ERPx_APDeliveryTicketLine.PurchaseGLAccountSK

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

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

Stat Area

A Stat Area (or Statistical area) is the five or six-digit ADF&G statistical code denoting a specific area of catch. Statistical areas are unique to the fishery "type". For example, there are unique statistical areas for salmon, herring, and shellfish/groundfish harvests. Also referred to as 'stat area.' Groundfish and shellfish (except Southeast Alaska) utilize a six-digit stat area number loosely based on latitude and longitude.

Database Fields: ERPx_APStatAreas.StatAreaID, ERPx_APDeliveryTicketStatArea.StatAreaSK, ERPx_APDeliveryTicketHeader.DileverTicketHeaderSK

Status

Identifies the Status of the transaction.

Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APDeliveryTicketHeader.TransactionStatusSK 

Tax District 

Identifies if the Tax District assigned to the Stat Area.

Database Fields: ERPx_APStatAreas.TaxDistrict, ERPx_APDeliveryTicketStatArea.StatAreaSK, ERPx_APDeliveryTicketHeader.DeliveryTicketHeaderSK

Taxes 

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

Tender Delivered

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 

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

Units

Identifies the count of the physical objects (Box, Bag, Case, Each, Tote, etc.) on the transaction.

Database Field: ERPx_APDeliveryTicketLine.Units

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.

Database Field: ERPx_APDeliveryTicketHeader.DeliveryTicketVersionTypeEN

Weight

Identifies the gross weight of the item.

Database Field: ERPx_APDeliveryTicketLine.DeliveredWeight 

Wt. Mod.

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

Database Field: ERPx_APDeliveryTicketLine.WeightModifier 

Related Topics


 Page Definitions


 Technical Details