Versions Compared

Version Old Version 4 New Version 5
Changes made by

Janice Dannenberg (Unlicensed)

Emma Greenwood

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
Def - Ticket Class (FA)
Def - Ticket Class (FA)
nopaneltrue
The purpose of this page is to set the properties of Transaction Classes used for Fish Tickets. Users may also view, add, remove and inactivate Transaction Classes.

...

Toolbar IconsDescription
Excel
Insert excerpt
Excel - RV Grid
Excel - RV Grid
nopaneltrue
FieldsDescription
Properties
Insert excerpt
Properties - RV
Properties - RV
nopaneltrue
Value 
Insert excerpt
Value - RV
Value - RV
nopaneltrue
Group: Setup
Ticket Class

Insert excerpt
Transaction Class
Transaction Class
nopaneltrue
This is a text box that is required. It defaults as blank and must be <= 50 characters. If missing, the message "Transaction Class is required." will be displayed on Save. This value must be unique, else the message "No Duplicate Transaction ID values allowed." will be displayed on Save. This field is not editable after the initial Save. 

Insert excerpt
Def - Ticket Class (FA)
Def - Ticket Class (FA)
nopaneltrue

Database Field: ERPx_APTransactionClass.TransactionClassID

Description

Insert excerpt
Transaction Class Description
Transaction Class Description
nopaneltrue
This is a text box that is required. It defaults as blank and must be <= 200 characters. If missing, the message "Cannot insert the value NULL into column 'TransactionClassDescription', table 'ERPx_APTransactionClass'; column does not allow nulls. INSERT fails." will be displayed on Save. If the value exceeds 200 characters, the message "Description cannot have more than 200 characters." will be displayed on Save. This field is always editable.

Database Field: ERPx_APTransactionClass.TransactionClassDescription

Doc Prefix

Insert excerpt
Document Prefix
Document Prefix
nopaneltrue
This is a text box that is not required. It defaults as blank and must be <= 10 characters. If the value exceeds 10 characters, the message "Document Prefix cannot have more than ten characters." will be displayed on Save. This field is enabled and always editable if the 'ADFG Landing Type' field is set to "DOES NOT INTEGRATE". Else, this field is disabled.

Insert excerpt
Def - Document Prefix - Fish Tickets
Def - Document Prefix - Fish Tickets
nopaneltrue

Database Field: ERPx_APTransactionClass.DocPrefix

Next Ticket Number

Insert excerpt
Next Document Number
Next Document Number
nopaneltrue
This is a text box that is required. This defaults as blank. If missing or not a numeric whole number, the message "Next Ticket Number must be a positive whole number." will be displayed on Save. This field is enabled and always editable if the 'ADFG Landing Type' field is set to "DOES NOT INTEGRATE". Else, this field is disabled.

Insert excerpt
Def - Document Prefix - Fish Tickets
Def - Document Prefix - Fish Tickets
nopaneltrue

Database Field: ERPx_APTransactionClass.NextDocNumber

Rows to Create on New

Identifies the number of blank rows that will be added to the Fish Ticket Record View grid when the New button is clicked. This is a text box that is required. It defaults to "5" and must be a number between 1 and 25.  If blank, it will be set to 5 and if set to any value other than 1 - 25, the message "Rows to Create on New must be between 1 and 25." will be displayed on Save. This field is always editable.

Database Field: ERPx_APTransactionClass.RowsToCreateOnNew

Number of RSW ReadingsIdentifies 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.

Insert excerpt
Def - Site
Def - Site
nopaneltrue

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. Note to tester - Verify this field appears before the Inactive field 

Database Field: ERPx_APTransactionClass.RequireChillTypeBeforeApproval

Inactive

Insert excerpt
Def - Inactive
Def - Inactive
nopaneltrue
This is a Yes/No lookup that is required. It defaults as "No" and is always editable.

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. This field 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 is updated to a value that 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


Related Topics

User Guide: Ticket Class

...