eLandings User Manual
Creating Miscellaneous Shellfish Landing Reports in eLandings
https://elandingst.alaska.gov/webMake Sure You Have an eLandings Operation Registered!
To create a Misc. Shellfish landing report in eLandings first make sure you have registered your operation in eLandings. If you need more information on registering a new operation, please see: How to Register a New Operation in eLandings.
Log Into eLandings
Go to the eLandings Login page: https://elandings.alaska.gov/web/ . Enter your UserID and Password then hit the Login button.
eLandings Reports Menu
Once you are logged into the eLandings website, the Reports Menu will come up. If you notice under the title bar there are links to different eLandings pages and features.
Reports Menu: Will bring you back to the Report Menu.
Reports tab: drop down options to view and create landing and production reports, the COAR reporting page, or for importing reports. Importing Reports to eLandings
Admin tab: Operation Administrations page where you add custom processing, tenders, and users. For more information please see: Operations Administration. Under this drop down you will also find the features to: Override Operations on Submitted Reports and Importable Fish Ticket Numbers.
Tools/Queries: many useful features. Some may be useful for reporting and report editing.
Generate Reports: eLandings System Generated Reports
Mixed Salmon Percentage Mass Change
IFQ Weight Calculator: IFQ Weight for halibut and sablefish
Check IFQ Balance
Landing Report Extract (Report Extract Tool)
Production Report Extract (Report Extract Tool)
Observer Fee Search
Generate Tender Log
Statistical Area for Lat/Long
CFEC Card Diagnostics
Codes: Will display all the codes needed for creating reports within the eLandings system, such as delivery, disposition, stat area, and production codes.
Help
User Name drop down: User Profile, Change Password, Logout.
Select an Operation
From Reports Menu page you can create a new misc. shellfish landing report. You can also create a new report from the Landing Report page accessed under the Landing Report tab up in the title bar banner.
Individual users can be associated with one or more Operations.
For example, a business manager might be associated with three Operations - Big Fish Inc, WAI Processing, and the stationary floating processor, The Happy Lady. Each of these operations is unique, and the user is authorized for each operation.
When the user logs into the eLandings system, he/she must designate the Operation that will be used to record landing information. The default operation set in your user profile will always be selected if you do not choose a different operation.
While most users are associated with only one Operation, if your business buys and processes, and/or performs custom processing for another Operation, there will be more than one listed under your User Account.
Once the Operation has been chosen, you can click on the Troll Landing Report button to open the form.
Landing Report Page
The landing report is divided into several sections and entry modals that you will move through in sequential order:
The vessel and Location Information
Permit Worksheet
Itemized Catch
Grading & Pricing
Notice that the Landing Report Number is located at the top of the new report. Here the number is 20395991. The Landing Report Number is a unique number generated by the eLandings System to identify the report. If you need to go and edit a report, the Landing Report number is what you will use to locate the report. Fish ticket numbers, within each report, can also be used to reference and locate an existing report.
Landing Report - Vessel and Location Information
This is the first screen that is displayed when creating a new landing report. Note that some of the required information about your operation is auto-filled based on your processor user account.
The eLandings System auto-fills your Port of Landing, and ADF&G Processor Code.
You should note that a unique Landing Report number is generated each time you initiate a landing report. In the above picture it is Landing Report number 20382267.
When you established your User Account and Operation, you entered all of the federal and state permits associated with your operation.
Vessel & Fishing Information
ADF&G Vessel Number: this is the five digit number permanently assigned by the Commercial Fishery Entry Commission (CFEC).
ADF&G Gear Code: this is the two digit numeric code used to identify the gear used to harvest the catch. These gear codes can be viewed by clicking on the Gear Codes link. For salmon troll this will be either 15 for Power Troll or 05 for Hand Troll.
Date Fishing Began: when the gear was deployed in the water to begin fishing.
Days Fished: when the gear was being fished. This number does not include traveling to and from the fishing grounds, or weather delays.
Date of Landing: when the landing was completed.
Entered From Paper FT: If you are entering a paper fish ticket into eLandings or a ticket from tLandings that was unable to upload into eLandings, please enter the paper fish ticket number (i.e., E18 123456) so that the two fish tickets can be associated together. For more information please see Entering Paper Fish Tickets into eLandings.
Port of Landing: location where the landing occurred. This value is auto-filled from your User Agreement registration. You can modify this value to indicate the correct location for this landing. You can click on the Port Codes link under the Port of Landing area for a list of port codes.
Nearest Bay or Headland: Site description of where fishing actually occurred designated by the nearest bay or headland's name. Example designations are "Icy Point" or "Cape Cross". If you have a question please ask your local area ADF&G office. Note: For Salmon Troll, this is required. Usually not used for other fisheries.
Partial Delivery: check if, Yes, the vessel has made deliveries to other operations or processors from this fishing trip, in other words, deliveries elsewhere, or if the delivery to your operation is only a portion of the catch.
If you created more than one landing report for a delivery, you should also check the Partial Delivery box, to indicate Yes.
ADF&G Processor Code: the owner of the product that has just been purchased - the purchaser. This value is auto-filled from your User Agreement registration. This value is auto-filled from your User Agreement registration. Select the correct number if one than one RCR is associated with your User Agreement.
ADF&G Processor Code (Custom Processor): applicable only if the product is being received or processed by a third party - not the purchaser.
Tender Worksheet
If you are editing a ticket that has been created using tLandings or entering a paper fish ticket you will need to fill in or ensure the validity of the following fields:
Time of Landing: The time fish or shellfish are off-loaded or trans-shipped from the catcher vessel to the first purchaser. The time of landing is the day off-load is completed. For tender deliveries the time landed is when the catcher vessel offloads their product to the tender vessel. If using tLandings, this time is automatically recorded when the landing report is created with that application and brought into eLandings when the landing report is imported with the PTI. The time can be edited. For catcher-processors the time landed is the time the product is caught and brought on board. For catcher-seller vessels the land date time is the time the product is initially brought into port.
Tender Dock Offload Date and Time: These fields are often not used for troll harvest but can be used to document when the tender delivered to the processor.
Tender ADF&G vessel number: The ADF&G vessel number assigned to an acting tender vessel. 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.
Tender Batch: Is the batch number assigned by the processor user when uploading a batch of tickets from tLandings/PTI to eLandings.
Tally Invoice: Tally sheet is provided in tLandings and provides a summary of all items recorded in a landing.
Dock Delivery: Only check this if delivering to a tender tied to the processor docks. More common during peak salmon season with large volumes delivered daily.