Fish tickets document the harvest of fish and shellfish sold, discarded, or retained by the fisherman for personal use. All licensed processors must fill out a fish ticket for each landing from a fishing permit holder. Fish tickets are a record of purchase between the processors (or buyers) and the fishermen, and for the resource managers, they are a record of how many fish were taken from the sea. The information collected includes species landed, weight, gear used, harvest dates, who caught the fish, and the processor’s license code. Information specific to each fishery is also collected when the catch is delivered. The purpose of this page is to view, add, edit, remove, and post individual Fish Ticket transactions. Additionally, users may view any Taxes, Premiums and Journal Details associated with the transaction.

Software Version: 2023.12.19 and newer

Page Header

Header Toolbar

Toolbar Icons	Description
Delete	Deletes the transaction or master file record. When clicked, users will be prompted with: "Are you sure you want to delete this record?". Click "OK" to confirm, or "Cancel" to return without deleting. _{WARNING: Records cannot be recovered once they are deleted!}
Grid Layout	Opens the Saved Grid Layout menu that allows the user to select another saved layout, create a new layout, save changes to a layout, or assign a saved layout as the default for the page. Once changes are made to a grid, such as columns are added or removed, the user can click the Saved Grid Layout icon and save the changes to the grid layout and name the new layout. The new layout can also be set as the default, instead of the System View. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific). The bolded view is the default view, which will determine the view will automatically display in when opened.
Journal Details	Opens the Journal Details window showing the Journal Entry for this transaction. Until the transaction Approved or Posted, this is a temporary journal entry so no Journal ID will be assigned.
Help	Opens the online WIKI help page for the current page. This icon is only visible on pages that are documented in the online help.
New	Allows users to select the type of transaction or record they want to add. The list contains: A list of all the 'Active' Ticket Classes.
Notes	Opens the Notes dialog, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the record. This icon is always enabled.
Print	Opens the Print dialog, showing any applicable printable reports to be printed, downloaded, and/or emailed.
Save	Saves the changes made to the record. It is only necessary to click the Save button when a change is detected on the page. When a change has been made, a ‘ + ‘ character is displayed prior to the page name in the page title bar (light blue bar in the upper left corner of the page). Clicking Save reloads the page.
Taxes & Premiums	Opens the Taxes & Premiums page.

Home Tab

Fields	Description
Amount	Identifies the Net Amount of the transaction by taking the sum of the line item net amounts. This is a non-editable text box that is required. This defaults to "0.00" and is never editable. Database Field: ERPx_APDeliveryTicketHeader.TotalNetAmount
Chill Type	Identifies the ID of the chill type. This is a single-select standard lookup that defaults to blank. This is required on Approved and Ready To Post when the associated Ticket Class property "Require Chill Type Before Approval" is set to Yes, else the message "Chill Type is Required" is displayed. If that ticket class property is set to No then the Chill Type field is not required at anytime. This field can only be edited while the transaction is set to a Status of New. 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. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Chill Types configured in the Chill Type Master List. Database Fields: ERPx_APChillType. ChillTypeID, ERPx_APDeliveryTicketHeader.ChillTypeSK
Crew Size	Identifies the number of crew members on the Vessel during a fishing trip. This is text box that defaults to 1. It is required and and if missing, the message "Crew Size is required for ADFG Landing Types of Groundfish and Crab" will be displayed on Save. The value must be greater than or equal to 1 for all tickets other than tickets with an ADF&G Salmon landing class. This field is always editable. Database Field: ERPx_APDeliveryTicketHeader.CrewSize
Days Fished	Identifies the number of days that the gear was in the water, actively fishing. This would include soak days (times) for pots and longline gear. Days spent traveling to and from the grounds, when gear has been removed from the water, should not be considered when calculating days fished. This is a text box that defaults to 1. It is required and if missing, the message "Days Fished must be greater than or equal to one" will be displayed on Save. The value must be greater than or equal to 1 and is always editable, even after the ticket is posted. Database Field: ERPx_APDeliveryTicketHeader.DaysFished
Delivered	Identifies the date the catch was delivered to the Plant. This is a text box that defaults to the date entered in the Delivery Date field on the New Delivery Ticket page. It is required and if missing, the message "Delivery Date is required" will be displayed on Save. This field must be on or after the Landed Date on the 'Home' tab. If not, the message "Delivery Date must be greater than or equal to Landed Date" will be displayed on Save. This field can only be edited while the transaction is set to a Status of New. 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 field defaults to blank and is required to save the transaction as a status of Approved or greater. If missing, the message "Delivery Number is required" will be displayed on Save. This must be <= 50 characters and is always editable. Database Field: ERPx_APDeliveryTicketHeader.DeliveryNumber
Dock Delivery	Identifies whether the Fish were delivered directly to the Dock of the processor facility. This is a single-select standard lookup that defaults to "Not Specified". It is required and is always editable while the transaction is in a Status of New. This lookup contains the values in the DeliveryTicketDockDelivery Enumeration Class. Database Field: ERPx_APDeliveryTicketHeader.DockDeliveryEN
Fishing Began	Identifies the date the fishing trip began. This is a text box that defaults to the date entered in the Landing Date field on the New Delivery Ticket page . This is not required, but if entered, needs to be on or before the current date, on or before the Landed Date, and on or before the Delivered date. If not, the message "Fishing Began cannot be after today's date." or "Fishing Began cannot be after Landed date." or "Fishing Began cannot be after Delivered date." will be displayed on Save of Approved or Ready to Post Status. This field is always editable, even after the ticket is posted. Database Field: ERPx_APDeliveryTicketHeader.FishingBegan
Fishing Vessel	Identifies the vessel that caught the fish. This is a single-select standard lookup that defaults to blank. This is not required and is always editable. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Vessels configured in the Vessels Master List. Database Fields: ERPx_APVessels.VesselName, 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 a single-select standard lookup that defaults to the Gear of the associated Permit Holder selected on the New Delivery Ticket page. This is a required field and is always editable while the transaction is in a Status of New. The lookup contains the current assigned value and any other permits for the ticket fisherman for the same ticket class. Database Fields: ERPx_APGear.GearDescription, ERPx_APVendorPermit.GearSK, ERPx_APDeliveryTicketHeader.VendorPermitSK
Landed	Represents the date the fish were landed. This is a text box that defaults to the date entered in the Landed Date field on the New Delivery Ticket page. If missing, the message "Landed Date is required." will be displayed on Save. The ticket cannot be approved or posted if the date is greater than the current date or if it is before the Fishing Began date. Else, the message "Landed Date cannot be after current date." or "Fishing Began cannot be after Landed date." will be displayed on Save of Approved or Ready to Post Status. This field is required and is always editable while the transaction is in a Status of New. 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
Manual Premiums	Identifies all the Premiums that were manually assigned to the ticket. This is a multi-select standard lookup that defaults to blank. It is not required and is always editable while the transaction is in a Status of New. The lookup contains a list of all 'Active' applicable Premium Programs that have a start date earlier than the ticket date and are set to be manually assigned. When a Premium is assigned, it is auto added to every line item and the amounts can be edited by opening that 'Taxes & Premiums' window. Premiums are most often used to represent things that increases the price you pay fishermen for their fish but they can also be configured to reduce the amount you pay. Premiums can be configured to be manually added or automated based on business rules. The Manual Premiums lookup displays all applicable 'active' and any previously saved manual premiums, but the premium is only assigned to the ticket if the ticket meets all the premiums criteria (e.g. Specie, Gear, Stat Area). Click the Taxes & Premiums button from the header toolbar to review all premiums assigned to the ticket. The Manual Premiums lookup will not display any applicable values until a Ticket Item is added to the record. Database Fields: ERPx_APProgram.APProgramName, ERPx_APDeliveryTicketEligiblePremium.APProgramSK, ERPx_APDeliveryTicketHeader.DeliveryTicketHeaderSK
Mgmt. Program	Identifies the management program abbreviation. This is a single-select standard lookup that defaults to the value set in the 'Management Program' field on the Fisherman Accounting Preferences page. This field required for the transaction to be Approved or Posted. If missing, the message "A Management Program is required to approve a ticket." will be displayed on Save. This is editable when the ticket is in a Status of New. 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_APDeliveryTicketHeader.ManagementProgramSK
Paid Account	Identifies the Fisherman Account that is being paid for the Fish Ticket. This is a single-select standard lookup that defaults to the 'Alternate Paid Account' value selected on the corresponding Fisherman's master file record or that was assigned as the Paid Account on integrated tickets. Otherwise, this value defaults to the Fisherman's name that was selected on the New Delivery Ticket page or that was assigned as the Permit Holder on integrated tickets. This is required for the transaction to be Approved or Posted and if missing, the message "Paid Account is required." is displayed on Save. This field is always editable while in a Status of New. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Fishermen, Fishermen & Tenders, and Tenders. Database Fields: ERPx_APVendor.VendorName, ERPx_APDeliveryTicketHeader.FishermanAccountVendorSK
Permit Holder	Identifies the owner of the Permit (the fisherman) that was associated with the catch. This is a non-editable text box that field defaults to the Fisherman selected on the New Delivery Ticket page. This is required and is never editable. Database Fields: ERPx_APVendor.VendorName, ERPx_APDeliveryTicketHeader.PermitHolderVendorSK
Price List	Identifies the ID of the Price List that is assigned to the transaction. This is a single-select standard lookup that defaults to the value set in the 'Default Price List' field in the 'Properties' tab of the associated Ticket Class record view. If the Price List is updated, the message "Do you want to update prices from the selected Price List"? will display. This field is not required and is always editable while in a Status of New. Price Lists are used to store a group of Items with pre-defined prices and effective dates. The lookup contains a blank value, the current assigned value and a list of all 'Active' Fish Ticket Price Lists with the same Ticket Class configured in the Price Lists Master List. Database Fields: ERPx_MFPriceListHeader.PriceListID, ERPx_APDeliveryTicketHeader.PriceListHeaderSK
Site Processed	Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. This is a single-select standard lookup that defaults to the 'Default Site Processed' field configured for the Ticket Class. This field is required when the ticket is saved as Approved or Ready to Post and is only editable while in a Status of New. The lookup displays all 'Active' Sites, with the exception of In Transit Sites that are configured in the Fisherman Accounting functional area. Database Fields: ERPx_MFSite.SiteName, ERPx_APDeliveryTicketHeader.SiteProcessedSiteSK
Status	Identifies the Status of the transaction. This is a single-select standard lookup that defaults as 'New' and is required. This is always editable while the transaction is in a Status of New or Approved. 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". Replaced: Signifies the transaction was voided or corrected. When a transaction is corrected or Voided, the Status of the original transaction is changed to 'Replaced' and a new transaction is cloned and marked as 'Void'. This is done to ensure that a reversal journal entry can be created and posted in an open fiscal period to record the Void. Void: Signifies a previously posted transaction has been voided. This status is only available for transactions that support voiding posted records (not all transactions support this). Voided transactions remain in the database and can be viewed from history inquiries. Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APDeliveryTicketHeader.TransactionStatusSK
Tender	Identifies the Tender associated with the transaction. The Tender may have been assigned as the buyer or delivered the ticket. This is a single-select standard lookup that defaults to blank. This is not required and is always editable. 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. The lookup contains a list of all 'Active' Tenders. Database Fields: ERPx_APVendor.VendorName, ERPx_APDeliveryTicketHeader.TenderDeliveredVendorSK
Ticket #	Identifies the Fish Ticket number (aka the Fish Ticket Transaction ID). This is a text box that defaults to the Ticket Number value entered on the New Delivery Ticket page. This field is required and if missing, the message "Ticket Number is required." will be displayed on Save. This must be <= 50 characters. Duplicate ticket numbers are not allowed and if entered, the message "Duplicate Ticket Numbers are not allowed. This ticket number has already been assigned to a different delivery ticket" will be displayed on Save. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.TicketNumber

Properties Tab

Fields	Description
# of Observers	Displays the number of state of Alaska certified observers onboard. This is a text box that is required and defaults to 0. This value must be numeric and greater than or equal to 0. Else the messages "# of Observers property must be a number." or "Number of Observers cannot be below zero." will be displayed on Save. This is always editable. Database Field: ERPx_APDeliveryTicketHeader.NumberObservers
Buying Station Name	Identifies the name of the buying station. This is a text box that is not required. The field defaults to blank and if entered, must be <= 100 characters. This is always editable. Database Field: ERPx_APDeliveryTicketHeader.BuyingStationName
CFECID	Identifies the fisherman's unique identifier with the state of Alaska. This is a text box that defaults from the 'CFECID' field in the 'Properties' tab of the Fisherman record view. The value in this field must match the permit serial number on record for the fisherman in order for the transaction to be saved as new. Else, the message "The CFECID does not match the Fisherman's CFECID" will be displayed on Save. This field is required for the transaction to be approved or posted. Else the message "CFECID is required to approve a ticket" will be displayed on Save. This must be <= 50 characters. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.CFECID
Chill Type	Identifies the ID of the chill type. This is a non-editable text box defaults to the value selected on 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
CQE Delivery	Identifies whether or not the delivery was via the CQE program. This is a Yes/No lookup that is required. It defaults to "No" and is always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.CQEDelivery
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 a non-editable text box that is required. 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 a non-editable text box that is required. Database Field: ERPx_APDeliveryTicketHeader.CreatedBy
Crew Size	Identifies the number of crew members on the Vessel during a fishing trip. This is a non-editable text box that is required. It defaults to the value entered on the 'Crew Size' field on the 'Home' tab of the Fish Ticket record view. The value must be greater than or equal to 1 for all tickets, other than tickets with an ADF&G Salmon landing class, and can be edited at any time from the 'Home' tab. Database Field: ERPx_APDeliveryTicketHeader.CrewSize
Currency SK	Displays the unique identifier from the database of the Currency assigned to the Vendor. This is a non-editable text box that is required. This field is for information only and is never editable by the user. Database Field: ERPx_APDeliveryTicketHeader.CurrencySK
Days Fished	Identifies the number of days that the gear was in the water, actively fishing. This would include soak days (times) for pots and longline gear. Days spent traveling to and from the grounds, when gear has been removed from the water, should not be considered when calculating days fished. This is a non-editable text box that is required. It defaults to the value entered on the 'Days Fished' field on the 'Home' tab of the Fish Ticket record view. The value must be greater than or equal to 1 and can be edited at any time from the 'Home' tab. Database Field: ERPx_APDeliveryTicketHeader.DaysFished
Delivered	Identifies the date the catch was delivered to the Plant. This is a non-editable text box that is required. It defaults to the value entered on the 'Delivered' field on the 'Home' tab of the Fish Ticket record view. This field must be on or after the Landed Date on the 'Home' tab. This can be edited at any time from the 'Home' tab. 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 a non-editable text box that is required to save the transaction as a status of Approved or greater. It defaults to the value entered on the 'Delivery #' field on the 'Home' tab of the Fish Ticket record view. This can be edited at any time from the 'Home' tab. Database Field: ERPx_APDeliveryTicketHeader.DeliveryNumber
Discard Report	Identifies the status of the discard report. This is a single-select standard lookup that is not required. It defaults to blank and is always editable. This lookup contains the values in the MFDiscardReport Enumeration Class. Discard reports are required by federal regulation to be given to the processor at the time of a groundfish offload if the vessel is federally permitted and is greater than or equal to 60 feet in overall length. The report includes discard or disposition information for all groundfish, prohibited species, and forage fish reported to the shoreside processor, stationary floating processor, or mothership by catcher vessels or buying stations. Database Field: ERPx_APDeliveryTicketHeader.DiscardReportEN
Dock Delivery	Identifies whether the Fish were delivered directly to the Dock of the processor facility. This is a non-editable text box that is required. It defaults to the value selected on the 'Dock Delivery' field on the 'Home' tab of the Fish Ticket record view. This can be edited from the 'Home' tab while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.DockDeliveryEN
Dual Permit	Identifies whether or not there were combined permits used for the delivery ticket. This is a Yes/No lookup that is required. It defaults to "No" and always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.DualPermit
Dual Permit ID	Identify the dual permit ID if the Dual Permit property is set to Yes. This is a single-select standard lookup that is required for status of 'Approved' or greater if the 'Dual Permit' property is set to "Yes". Else, the message 'A Dual Permit ID is required to Approve or Post a ticket when Dual Permit is selected" will be displayed on Save. This is always editable while the transaction is in a Status of New. The lookup contains a list of all 'Active' eligible permits. Eligible permits are those that are of the same transaction class, gear, and fishery as the primary permit. Database Fields: ERPx_APVendor.VendorName, ERPx_APVendorPermit.Permit, ERPx_APVendorPermit.VendorPermitSK, ERPx_APDeliveryTicketHeader.DualPermitVendorPermitSK
eLandings Status	Identifies the submission status of the fish ticket in eLandings. This is a single select lookup that is not required. This is defaulted from eLandings data and is always editable, even on Posted tickets. Database Field: ERPx_APDeliveryTicketADFGLandingImportHeader.ADFGStatusID, ERPx_APDeliveryTicketHeader.ELandingStatusEN
Federal Permit #	Displays the Federal permit number. This is a text box that is not required, but if entered, should be <= 20 characters. For manually entered fish tickets, this will default from the 'Federal Permit #' value saved on the Preferences page. For fish tickets imported from eLandings, this will default the value from the eLandings data. This field is always editable. Database Field: ERPx_APDeliveryTicketHeader.FederalPermitNumber
Fisherman SK	Displays the unique identifier from the database for the Paid Fisherman. This is non-editable text box that is required. This field is for information only and is defaults to the identifier associated with the 'Paid Account' selected on the 'Home' tab of the Fish Ticket record view. It is never editable by the user. Database Field: ERPx_APDeliveryTicketHeader.FishermanAccountVendorSK
Fishing Began	Identifies the date the fishing trip began. This is a non-editable text box that defaults to the date entered on the 'Fishing Began' field on the 'Home' tab of the Fish Ticket record view. This is not required, but if entered, needs to be on or before the current date, on or before the Landed Date, and on or before the Delivered date. This field can be edited at any time from the 'Home' tab. Database Field: ERPx_APDeliveryTicketHeader.FishingBegan
Fishing Period	Identifies the period during which the fish ticket catch was made. This is a text box that is not required. It defaults to blank, but if entered, should be <= 20 characters. This field is always editable. Database Field: ERPx_APDeliveryTicketHeader.FishingPeriod
Fishing Vessel	Identifies the vessel that caught the fish. This is a non-editable single-select standard lookup that is not required. This defaults to the value selected for the 'Fishing Vessel' field on the 'Home' tab of the Fish Ticket record view. This field can be edited at any time from the 'Home' tab. Database Fields: ERPx_APVessels.VesselName, ERPx_APVessels.VesselNumber, ERPx_APDeliveryTicketHeader.VesselSK
Floating	Identifies whether or not the delivery was a floating delivery. This is a Yes/No lookup that is required. It defaults to "No" and is always editable while the transaction is in a Status of New. If there is a Premium record setup to Auto Assign - Floating Tickets, and the program criteria matches the associated criteria, this property needs to be set to "Yes" for the premium to be assigned. 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 a non-editable single-select standard lookup that is required. This defaults to the value selected for the 'Gear' field on the 'Home' tab of the Fish Ticket record view. This can be edited from the 'Home' tab while the transaction is in a Status of New. 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 a date picker that is required to Approve or Post the ticket. This defaults to blank. When saving in a Status of 'Approved' or greater, this field will automatically default from the value of the 'Delivered' field on the 'Home' tab of the Fish Ticket record view if it is blank. This date must be in a valid fiscal period, else the message "This Fiscal Period is not open." will be displayed on Save. This date must be less than or equal to the current date, else the message "GL Date cannot be after current date" will display on Save. This field is always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.GLDate
Headland	Identifies the nearest headland to where the fish were caught. This is a text box that is not required. It defaults to blank and if entered, should be <= 200 characters. This field is always editable. Database Field: ERPx_APDeliveryTicketHeader.Headland
Integration Status	Displays the integration status of the fish ticket. This is a non-editable text box that is not required. This is defaulted from eLandings data and never editable by the user. Database Fields: ERPx_APDeliveryTicketADFGIntegrationStatus.StatusDescription, ERPx_APDeliveryTicketHeader.ADFGIntegrationStatusSK
Landed	Represents the Landed Date of the ticket. This is a non-editable text box that is required. This defaults to the value entered for the 'Landed' field on the 'Home' tab of the Fish Ticket record view. This date must be <= the current date or after the Fishing Began date. This field is always editable from the 'Home' tab while the transaction is in a Status of New. 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 a text box that is only required for eLandings tickets. If entered, must be <= 50 characters. This field defaults to blank and is always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.LandingNumber
Landing Time	Identifies the time at which the delivery began to be unloaded. This is a text box that is not required. If entered, must be <= 20 characters. This field defaults to blank and is always editable. Database Field: ERPx_APDeliveryTicketHeader.LandingTime
Last Delivery For Trip	Identifies whether or not the fish ticket records the last delivery for the trip. This is a Yes/No lookup that is required. It defaults to "No" and is always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.LastDeliveryForTrip
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 a non-editable text box that is required. 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 a non-editable text box that is required. Database Field: ERPx_APDeliveryTicketHeader.LastUser
Management Program	Identifies the management program using the abbreviation and description. This is a non-editable single-select standard lookup that defaults to the value set in the 'Mgmt. Program' field on the 'Home' tab of the Fish Ticket record view. This field required for the transaction to be Approved or Posted. This field is always editable from the 'Home' tab while the transaction is in a Status of New. 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
Manual IFQ Report	Identifies whether or not a manual IFQ report was submitted. This is a Yes/No lookup that is required. It defaults to "No" and is always editable while the transaction is in a Status of New. An IFQ or Individual Transferable (Fishing) Quota is a form of limited entry that gives private property rights to fishers, by assigning a fixed share of the total allowable catch to each fisher. ITQs are frequently referred to as an Individual Fishing Quota (IFQ). Alaskan halibut and sablefish fisheries and the Rationalized Crab program fisheries of the Bering Sea and Aleutian Islands are exclusive IFQ fisheries. With each landing, poundage from the quota is debited from the individual's IFQ account. Database Field: ERPx_APDeliveryTicketHeader.ManualIFQReport
Master Number	Displays the original DeliveryTicketHeaderSK from the database. This is used to link all versions of the same Ticket together. This is non-editable text box that is required. This field is for information only. It is never editable by the user. Database Field: ERPx_APDeliveryTicketHeader.MasterNumber
Moved to Avoid Salmon	Identifies whether or not the vessel moved the fishing location to avoid salmon bycatch. This is a Yes/No lookup that is required. It defaults to "No" and is always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.MovedToAvoidSalmon
Multiple IFQ Permits	Identifies whether or not the fish ticket is associated with a harvest that was divided among multiple IFQ permits. This is a Yes/No lookup that is required. It defaults to "No" and is always editable while the transaction is in a Status of New. An IFQ or Individual Transferable (Fishing) Quota is a form of limited entry that gives private property rights to fishers, by assigning a fixed share of the total allowable catch to each fisher. ITQs are frequently referred to as an Individual Fishing Quota (IFQ). Alaskan halibut and sablefish fisheries and the Rationalized Crab program fisheries of the Bering Sea and Aleutian Islands are exclusive IFQ fisheries. With each landing, poundage from the quota is debited from the individual's IFQ account. Database Field: ERPx_APDeliveryTicketHeader.MultipleIFQPermits
Out of State	Identifies whether or not fishing occurred out of state. This is a Yes/No lookup that is required. It defaults to "No" and is always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.OutOfState
Paid Account	Identifies the Fisherman Account that is being paid for the Fish Ticket. This is a non-editable single-select standard lookup that is required. This defaults to the value selected for the 'Paid Account' field on the 'Home' tab of the Fish Ticket record view. This field is always editable from the 'Home' tab while the transaction is in a Status of New. Database Fields: ERPx_APVendor.VendorName, ERPx_APDeliveryTicketHeader.FishermanAccountVendorSK
Paper Ticket #	Identifies the paper fish ticket number associated with the fish ticket. This is a text box that is not required. If entered, must be <= 50 characters. This field defaults to blank and is always editable from the 'Home' tab while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.PaperTicketNumber
Partial Delivery	Identifies whether or not the delivery was only a portion of the vessel's load. This is a Yes/No lookup that is required. It defaults to "No" and is always editable. A Partial delivery is a delivery consisting of only a portion of a vessel's total harvest from one fishing trip. All fish tickets that represent only a portion of the harvest from one fishing trip must be identified as a partial delivery. The harvest from a single fishing trip can be documented on more than one fish ticket, either split among IFQ shareholders, divided for multiple fishery bycatch caps or permits, or delivered to more than one processor. A partial delivery constitutes a landing. Database Field: ERPx_APDeliveryTicketHeader.PartialDelivery
Permit	Identifies the permit number that is associated to the Permit Holder. This is a non-editable text box that is required. This defaults to the value entered on 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 Delivery Ticket page. Database Fields: ERPx_APVendor.VendorSK.VendorName , ERPx_APDeliveryTicketHeader.PermitHolderVendorSK
Permit Holder Permit SK	Displays the unique identifier from the database for the Permit Holder's Permit number. This is a non-editable text box that is required. It is for information only and is never editable by the user. Database Fields: ERPx_APDeliveryTicketHeader.VendorPermitSK
Permit Holder SK	Displays the unique identifier from the database for the Permit Holder. This is a non-editable text box that is required. It is for information only and is never editable by the user. Database Field: ERPx_APDeliveryTicketHeader.PermitHolderVendorSK
Permit Magnetic Stripe Read	Identifies whether or not the magnetic stripe on the permit associated with the fish ticket was read. This is a Yes/No lookup that is required. It defaults to "No' and is editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.MagStripeRead
Port of Landing	Identifies the location the fish or shellfish were unloaded. This is a single-select standard lookup that is required. If missing, the message "Port of Landing is required" will be displayed on Save. It defaults from the 'Port of Landing' field on the Fisherman Accounting Preferences page. This field is always editable. The lookup contains a list of all 'Active' Ports. Database Fields: ERPx_APPort.PortDescription, ERPx_APDeliveryTicketHeader.PortSK
Price List	Identifies the ID and Description of the Price List that is assigned to the transaction. This is a non-editable single-select standard lookup that defaults to the value set in the 'Price List' field in the 'Home' tab of the Fish Ticket record view. This field is not required and is always editable from the 'Home' tab while the transaction is in a Status of New. Price Lists are used to store a group of Items with pre-defined prices and effective dates. Database Fields: ERPx_MFPriceListHeader.PriceListID, ERPx_MFPriceListHeader.Description, ERPx_APDeliveryTicketHeader.PriceListHeaderSK
Processor ID	Identifies the processor identification code of the buyer. This is a text box that is required. If missing, the message "Processor ID is required" will be displayed on Save. This field must be <= 10 characters. It defaults from the 'Processor ID' field on the Fisherman Accounting Preferences page. This field is always editable. Database Field: ERPx_APDeliveryTicketHeader.ProcessorID
Processor ID - Custom Processor	Identifies the custom processor's processor code, if applicable. This is a text box that is not required. It defaults as blank and is editable while the transaction is in a Status of New. If entered, this must be <= 200 characters. Database Field: ERPx_APDeliveryTicketHeader.CustomProcessorID
Registered Buyer #	Identifies the Registered Buyer permit number. This is a text box that is not required. This field must be <= 10 characters. It defaults from the 'Registered Buyer #' field on the Fisherman Accounting Preferences page. This field is always editable. A Registered Buyer Permit is a permit issued by the NMFS, that authorizes the person identified on the permit to receive and make an IFQ landing by an IFQ permit or cardholder or to receive and make a CDQ halibut landing by a CDQ permit or cardholder at any time during the fishing year for which it is issued until the Registered Buyer permit expires, or is revoked, suspended, or modified under applicable Federal law. Database Field: ERPx_APDeliveryTicketHeader.RegisteredBuyer
Registered Crab Receiver	Identifies the Registered Crab Receiver permit number. This is a text box that is not required. This field must be <= 10 characters, else the message "Registered Crab Receiver must be shorter than 10 characters" will be displayed on Save. It defaults from the 'Registered Crab Receiver' field on the Fisherman Accounting Preferences page. This field is always editable. A Registered Crab Receiver Permit (RCR) is required: for any person who receives unprocessed CR crab from the person(s) who harvested the crab, the owner or operator of a vessel that processes CR crab at sea, any person holding IPQ, and any person required to submit a Departure Report. Database Field: ERPx_APDeliveryTicketHeader.RegisteredCrabReceiver
Reprice Comment	Displays a comment regarding the reasoning or other notes about the reprice. This is a non-editable text box that is not required unless the Fish Ticket was repriced. It defaults from the 'Reprice Comment' field entered in the header of the Fish Ticket Premium Reprice record view or the Fish Ticket Item Reprice record view. This field is never editable by the user from the Fish Ticket record view. Database Field: ERPx_APDeliveryTicketHeader.RepriceComment
Season	Identifies which fishing season the delivery occurred in. This is a single-select standard lookup that is not required. If defaults from the 'Season' field on the Fisherman Accounting Preferences page. This field is always editable. The lookup contains a list of all 'Active' Seasons. 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 a non-editable text box that is required. It defaults from the 'Site Processed' field on the 'Home' tab of the Fish Tickets record view. This is only editable from the 'Home' tab while the transaction is in a Status of New. Database Fields: ERPx_MFSite.SiteName, ERPx_APDeliveryTicketHeader.SiteProcessedSiteSK
Slide	Identifies whether or not the delivery was a slide delivery. This is a Yes/No Lookup that is required. It defaults to "No" and is always editable 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
Source	Identifies where the fish ticket originated. 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). This field is never editable by the user. Database Field: ERPx_APDeliveryTicketHeader.Source
Status	Identifies the Status of the transaction. This is a non-editable text box that is required. This defaults from the 'Status' field on the 'Home' tab of the Fish Ticket record view and is always editable from the 'Home' tab while the transaction is in a Status of New or Approved. Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APDeliveryTicketHeader.TransactionStatusSK
Tender	Identifies the Tender associated with the transaction. This is a non-editable single-select standard lookup that is not required. It defaults from the 'Tender' field in the 'Home' tab of the Fish Ticket record view and is always editable. 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 Delivered SK	Displays the unique identifier from the database for the Tender selected on ticket. This is a non editable text box that is not required. If populated, it defaults from the 'Tender' field in the 'Home' tab of the Fish Ticket record view. This field is for information only and is never editable by the user. Database Fields: ERPx_APDeliveryTicketHeader.TenderDeliveredVendorSK
Tender Vessel	Identifies the Vessel that is assigned to the Tender on the ticket. This is a non-editable text box that is not required. If populated, it defaults from the 'Primary Vessel' field in the 'Properties' tab of the Fishermen & Tenders record view. This field is for information only and is never editable by the user. Database Fields: ERPx_APVessels.VesselName, ERPx_APVendor.TenderVesselSK, ERPx_APDeliveryTicketHeader.TenderDeliveredVendorSK
Ticket #	Identifies the Fish Ticket number (aka the Fish Ticket Transaction ID). This is a non-editable text box that is required. It defaults from the 'Ticket #' field entered on the 'Home' tab of the Fish Ticket record view. This is editable from the 'Home' tab while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.TicketNumber
Ticket SK	Displays the unique identifier from the database for the Ticket. This is a non-editable text box that is required. This field is auto-assigned by the system. It is for information only and is never editable by the user. Database Field: ERPx_APDeliveryTicketHeader.DeliveryTicketHeaderSK
Transaction Class	Identifies the Ticket Class for the Fish Ticket. This is a non-editable text box that is required. It defaults from the Ticket Class selected when the fish ticket was created. This field is for information only and is never 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
Transaction Class SK	Displays the unique identifier from the database for the Transaction Class selected when creating the ticket. This is a non-editable text box that is required. This field is auto-assigned by the system. It is for information only and is never editable by the user. Database Field: ERPx_APDeliveryTicketHeader.TransactionClassSK
Version	Identifies the version number of the fish ticket. This is a non-editable text box that is required. This field is auto-assigned by the system. It is for information only and is never editable by the user. 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	Identities the type of version attributed to the fish ticket - i.e. Original, Correction, or Reprice. This is a non-editable text box that is required. This field is auto-assigned by the system. It is for information only and is never editable by the user. This lookup contains the values in the DeliveryTicketVersionType Enumeration Class. Database Field: ERPx_APDeliveryTicketHeader.DeliveryTicketVersionTypeEN
Vessel SK	Displays the unique identifier from the database for the Vessel selected on the ticket. This is a non-editable text box that is required. This field is auto-assigned by the system. It is for information only and is never editable by the user. Database Field: ERPx_APDeliveryTicketHeader.VesselSK

Stat Area Tab

Fields	Description
Toolbar Icons	Description
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 only the filtered contents will be exported.
New	Adds new blank lines in the grid section to allow for data entry.
Percent	Identifies the percentage of the ticket total came from the assigned Stat Area. This is a text box that is required to Approve or Post the transaction. It defaults to "0.00" and must be greater than 0.00 and less than 100.00 if a Stat Area is assigned. Else, the message "Stat Area Percent must be greater than or equal to zero" will be displayed on Save. The sum of the Percent for all the Stat Areas must equal 100.00. Else, the message "At least one Stat Area must be assigned to a ticket and the percentages must total 100" will be displayed on Save of Approved or Ready to Post Status. This field is always editable while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketStatArea.Percent
PotLifts	Identifies how many Pots were pulled for each Stat Area. This is a textbox that is required. It defaults to "0" and is editable while the transaction is in a Status of New. This field must be greater than or equal to 0, else the message "Potlifts must be greater than or equal to zero". Pot lifts identify the total number of times pots are set and retrieved within an ADF&G statistical area to produce the catch. The number of pot lifts by area combined with area, catch, gear type, gear size, and length of time gear is used to catch fish or shellfish, assist in determining the catch per unit effort (CPUE), or more commonly referred to as 'effort'. Database Field: ERPx_APDeliveryTicketStatArea.PotLifts
Stat Area	Identifies all the Statistical Areas that fish were caught. This is a single-select standard lookup that is required before taxes will calculate and is required to Approve or Post the transaction. If missing, the message "At least one Stat Area must be assigned to a ticket and the percentages must total 100" will be displayed on Save of Approved or Ready to Post Status. This field defaults as blank and must be unique. Else, the message "You cannot have duplicate Stat Areas on a ticket" will be displayed on Save. This field is always editable while the transaction is in a Status of New. 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. The lookup contains a list of all 'Active' Stat Areas. Database Fields: ERPx_APStatAreas.StatAreaID, ERPx_APDeliveryTicketStatArea.StatAreaSK

RSW Temp Tab

Fields	Description
Temperature	Identifies the temperature of the refrigerated sea water. This is a text box that is not required. If entered, it must be equal or greater than zero. Else, the message "Temperature must be greater than or equal to zero" will be displayed on Save. This field defaults to "0.00" and is always editable. If one or more temperature is entered, the system will a automatically calculate the number of readings, Low, High and Average temperature. Database Field: ERPx_APDeliveryTicketRSW.Temperature

Fields

Description

Temperature

Identifies the temperature of the refrigerated sea water. This is a text box that is not required. If entered, it must be equal or greater than zero. Else, the message "Temperature must be greater than or equal to zero" will be displayed on Save. This field defaults to "0.00" and is always editable. If one or more temperature is entered, the system will a automatically calculate the number of readings, Low, High and Average temperature.

Database Field: ERPx_APDeliveryTicketRSW.Temperature

Attributes Tab

Fields	Description
Attributes	The Attributes displayed are determined by the Attribute Setup and the Assign Attribute Rules. The Attributes can be setup and assigned to the transaction type in the Attributes section of the Company module (Company → Attributes → Fisherman). Attributes are user-defined fields to store additional structured information (Attribute Values) for master file and transaction records. As new Attributes are created, they are dynamically added as columns to master file and transaction list views as well as historical transaction inquiries. Whereas Properties are used to describe database values that install with every instance of NorthScope (e.g. Customer ID, Vendor Name, Payment Terms), Attributes are user defined and can be added as needed but there is no system functionality tied to them. When Attributes are added, the Data Type must be specified. The Data Types include: Text - Attribute Values can be any combination of text and/or numeric values can be entered up to 200 characters. These are best used for Attributes that have values that may be difficult to pre-determine or where there the values are not necessary for reports and/or inquiries. For example, An attribute to store the name of a person would be better configured as a Text Attribute. List - Attribute Values must be selected from a pre-defined list of acceptable values. These are best used for Attributes that have a limited list of values that are easy to pre-determine and where uniformity of data is desired. For example, An attribute to store the "Brand Label" of an Item would be ideal to come from a List. Date - Attribute Values must be a valid Date. These are best used for Attributes that store Dates only, time would not be useful. For example, if you had an Attribute for a "Customer Review Date" having the date is important but time is not. Date/Time - Attribute Values must be a valid Date & Time. These are best used for Attributes that store Dates & Times both. For example, if you had an Attribute to record when an Order shipped, having both a Date and Time may be desired. When Attributes are created, the "Assign Rules by" page can be opened to change the data entry rules for each Transaction Type (for Transaction Level Attributes) or each Attribute Class (for Master File Attributes). The data entry options include: No: The Attribute is not displayed on Transaction or Master File Record Views for the applicable Transaction Type or Master File with the associated Attribute Class Yes - Not Required: The Attribute is displayed on Transaction or Master File Record Views for the applicable Transaction Type or Master File with the associated Attribute Class but users are not required to enter a value Yes - Required: The Attribute is not displayed on Transaction or Master File Record Views for the applicable Transaction Type or Master File with the associated Attribute Class

Fields

Description

Attributes

The Attributes displayed are determined by the Attribute Setup and the Assign Attribute Rules. The Attributes can be setup and assigned to the transaction type in the Attributes section of the Company module (Company → Attributes → Fisherman).

Attributes are user-defined fields to store additional structured information (Attribute Values) for master file and transaction records. As new Attributes are created, they are dynamically added as columns to master file and transaction list views as well as historical transaction inquiries. Whereas Properties are used to describe database values that install with every instance of NorthScope (e.g. Customer ID, Vendor Name, Payment Terms), Attributes are user defined and can be added as needed but there is no system functionality tied to them.

When Attributes are added, the Data Type must be specified. The Data Types include:

Text - Attribute Values can be any combination of text and/or numeric values can be entered up to 200 characters. These are best used for Attributes that have values that may be difficult to pre-determine or where there the values are not necessary for reports and/or inquiries. For example, An attribute to store the name of a person would be better configured as a Text Attribute.
List - Attribute Values must be selected from a pre-defined list of acceptable values. These are best used for Attributes that have a limited list of values that are easy to pre-determine and where uniformity of data is desired. For example, An attribute to store the "Brand Label" of an Item would be ideal to come from a List.
Date - Attribute Values must be a valid Date. These are best used for Attributes that store Dates only, time would not be useful. For example, if you had an Attribute for a "Customer Review Date" having the date is important but time is not.
Date/Time - Attribute Values must be a valid Date & Time. These are best used for Attributes that store Dates & Times both. For example, if you had an Attribute to record when an Order shipped, having both a Date and Time may be desired.

When Attributes are created, the "Assign Rules by" page can be opened to change the data entry rules for each Transaction Type (for Transaction Level Attributes) or each Attribute Class (for Master File Attributes). The data entry options include:

No: The Attribute is not displayed on Transaction or Master File Record Views for the applicable Transaction Type or Master File with the associated Attribute Class
Yes - Not Required: The Attribute is displayed on Transaction or Master File Record Views for the applicable Transaction Type or Master File with the associated Attribute Class but users are not required to enter a value
Yes - Required: The Attribute is not displayed on Transaction or Master File Record Views for the applicable Transaction Type or Master File with the associated Attribute Class

Browser not supported