Delete

Help

New

Save

Save & Close

Fields

Description

Class

Identifies the Fish Ticket Class as [Ticket Class ID] - [Description]. This is a single-select standard lookup that is required once a Ticket Class has been saved. It defaults to blank for a new Ticket Class. This field is always editable after initial Save. When users update the value selected in this field, the Ticket Class Record View will automatically refresh to display the Properties for the selected Ticket Class.

This lookup contains all Fish Ticket Classes.

Database Fields: ERPx_APTransactionClass.TransactionClassID - ERPx_APTransactionClass.TransactionClassDescription where ERPx_APTransactionClass.TransactionTypeSK = 7.

Column Filter Show/Hide

Excel

Group By Show/Hide

Quick Column Filter

Saved Layouts

Fields

Description

Properties

Value 

Group: Setup

Ticket Class

Database Field: ERPx_APTransactionClass.TransactionClassID

Description

Database Field: ERPx_APTransactionClass.TransactionClassDescription

Doc Prefix

Database Field: ERPx_APTransactionClass.DocPrefix

Next Ticket Number

Database Field: ERPx_APTransactionClass.NextDocNumber

Number of RSW Readings

Identifies the number of Refrigerated Sea Water (RSW) Temperature rows that will be displayed on the 'RSW Temp' tab of the Fish Ticket Record View. This is a text box that is required. It defaults to "3" and must be a number between 1 and 20.  If blank, it will be set to 3 and if set to any value other than 1 - 20, the message "Number of RSW Readings must be between 1 and 20." will be displayed on Save. This field is always editable.

Database Field: ERPx_APTransactionClass.NumberOfRSWReadings

Default Site Processed

Identifies the default value of the 'Site Processed' field in the 'Home' tab of a newly created or imported Fish Ticket with the Ticket Class. This is a single-select standard lookup that is not required. It defaults as blank and is always editable.

The lookup contains a blank value and list of all active Sites.

Database Fields: ERPx_MFSite.SiteID, ERPx_MFSite.SiteName, ERPx_APTransactionClass.DefaultSiteSK

Require Chill Type before Approval

Identifies whether or not the Chill Type is required for a Fish Ticket to be Approved or Posted. This is a Yes/No lookup that is required. It defaults to "No" and is always editable. 

Database Field: ERPx_APTransactionClass.RequireChillTypeBeforeApproval

Require Stat Area Before Approval

Identifies whether or not a Stat Area is required for a Fish Ticket to be Approved or Posted.  This is a Yes/No lookup that is required.  It defaults to "Yes" and is always editable. 

Database Field: ERPx_APTransactionClass.RequireStatAreaBeforeApproval

Single Date Management

A Yes/No lookup to select whether or not the Delivery and Fishing Began dates on a Fish Ticket default from the Landed Date. This defaults to "No" for new records and is always required. This field is always editable. When this property is set to “Yes”, users can only enter and edit the 'Landed Date' field on the 'Fish Ticket - New Delivery Ticket' page and on the Fish Ticket Record View. The Delivery Date and Fishing Began fields will be disabled.  No other date fields are affected by this property. 

The following date fields will default from the Fish Ticket Landed Date:

• Delivery Date

• Fishing Began

Database Field: ERPx_APTransactionClass.SingleDateManagement

Inactive

Database Field: ERPx_APTransactionClass.IsInactive

Group: Pricing

Default Price List

Identifies the ID of the Price List to be defaulted on a new Fish Ticket created with the Fish Ticket Class. This is a single-select standard lookup that is not required. It defaults to blank and is always editable.

The lookup contains a blank value and list of all active Fish Ticket Price Lists.

Database Fields: ERPx_MFPriceListHeader.PriceListID, ERPx_APTransactionClass.DefaultPriceListHeaderSK

Group: ADFG

ADFG Landing Type

Identifies the Landing Type that integrates with eLandings. This is a single-select standard lookup that is required. It defaults to “DOES NOT INTEGRATE”, which means the Ticket Class will not integrate with eLandings. This field is always editable. If the value already exists on another Ticket Class, then the message "No Duplicate Landing Types allowed." will be displayed on Save.

The lookup contains the value "DOES NOT INTEGRATE" and all values in the ERPx_APDeliveryTicketADFGLandingType table displayed as [LandingTypeID] - [LandingTypeName].

Database Field: ERPx_APTransactionClass.ADFGLandingType

Allow Import of Missing or Inactive Fishermen

Identifies whether or not to allow the import of missing or inactive Fishermen. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Fisherman will be automatically added on Import. This field defaults to "No" and is always editable.

Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveFishermanImport

Allow Import of Missing or Inactive Permits

Identifies whether or not to allow the import of missing or inactive Permits. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Permits will be automatically added on Import. This field defaults to "Yes" and is always editable.

Database Field: ERPx_APTransactionClass.AllowMissingOrInactivePermitImport

Allow Import of Missing or Inactive Fish Ticket Items and Components

Identifies whether or not to allow the import of missing or inactive Fish Ticket Items and Components. Components include Specie, Conditions, Dispositions, and Grades.  This is a Yes/No lookup that is required. If the property is set to "Yes", then the Fish ticket Items and Components will be automatically added on Import. This field defaults to "Yes" and is always editable.

Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveFishTicketItemAndComponentImport

Allow Import of Missing or Inactive Chill Types

Identifies whether or not to allow the import of missing or inactive Chill Types. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Chill Types will be automatically added on Import. This field defaults to "Yes" and is always editable.

Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveChillTypeImport

Allow Import of Missing or Inactive Gears

Identifies whether or not to allow the import of missing or inactive Gears. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Gears will be automatically added on Import. This field defaults to "Yes" and is always editable.

Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveGearImport

Allow Import of Missing or Inactive Management Programs

Identifies whether or not to allow the import of missing or inactive Management Programs. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Management Programs will be automatically added on Import. This field defaults to "Yes" and is always editable.

Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveManagementProgramImport

Allow Import of Missing or Inactive Ports

Identifies whether or not to allow the import of missing or inactive Ports. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Ports will be automatically added on Import. This field defaults to "Yes" and is always editable.

Database Field: ERPx_APTransactionClass.AllowMissingOrInactivePortImport

Allow Import of Missing or Inactive Stat Areas

Identifies whether or not to allow the import of missing or inactive Stat Areas. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Stat Areas will be automatically added on Import. This field defaults to "Yes" and is always editable.

Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveStatAreaImport

Allow Import of Missing or Inactive Vessels

Identifies whether or not to allow the import of missing or inactive Vessels. This is a Yes/No lookup that is required. If the property is set to "Yes", then the Vessels will be automatically added on Import. This field defaults to "Yes" and is always editable.

Database Field: ERPx_APTransactionClass.AllowMissingOrInactiveVesselImport

Allow Submit to eLandings

Identifies whether or not to allow tickets to be submitted to eLandings.  This is a Yes/No lookup that is required.  If the property is set to "Yes", then tickets can be submitted from the Fish Ticket List View Mass Update "Submit to eLandings" property. This field defaults to "No" and is always editable. 

Database Field: ERPx_APTransactionClass.AllowELandingsExport