Introduction
There are multiple ways to batch tickets in the eLandings system. They include:
- Using the Auto Batching Tool
- Opening a previously entered ticket and assigning batching information to an Individual Landing Report.
At times eLandings ADFG users data enter paper tickets into eLandings from a paper ticket. These tickets may originate from Alaska, Seattle, Oregon, or Canada. During the data entry process, ADFG staff have the opportunity to assign batching information. This allows the ADFG user to do two things at once. However batching during data entry is not required. If the ticket is data entered but not batched at that time, ADFG users can use later use one of the two methods listed above to assign batching information.
This document will attempt to describe how ADFG staff can use the Agency eLandings webpage to assign batch information during data entry.
The new agency eLandings webpage is accessible using a web browser. We recommend using CHROME or Firefox. There are some known bugs with Internet Explorer (IE).
TEST
http://elandingstest.alaska.gov/web/
TRAINING
http://elandingst.alaska.gov/web/
PRODUCTION
https://elandings.alaska.gov/web/
In this document, we will use fake data to demonstrate the process. As we are using fake data, we will be working in the TEST system. All screenshots listed below will be in the TEST system.
Assigning Batching Info during Data Entry
Imagine that we have a paper Groundfish ticket that does not exist in eLandings yet.
We want to data enter this fish ticket.
We will log into the eLandings TEST system by opening CHROME and going to:
http://elandingstest.alaska.gov/web/
We will log in with:
UserId = HGURLL
Password = H_gurll
Note: You can show your password while typing by clicking on the "Show Password" checkbox.
On login, Agency users are presented with the "Welcome To eLandings Agency Portal". We also call this the main page or home page.
You can always get back to this page by clicking on the Agency menu item at the top left of the screen.
On the Agency Portal page, click on "Create Landing Report" button.
A modal dialog will appear entitled "Create Landing Report".
In the Report Type combo Box, select "Groundfish" and then click the create button.
The Groundfish Landing Report Entry Screen will be displayed.
Notice that the data entry screen was given a new landing report id.
The landing report id = 18326505
The new landing report id will be assigned to the ticket when you save the data to the system. From that point on, you can search for and retrieve the ticket in eLandings using this landing report id.
Our paper ticket has a paper fish ticket number = G02 000111
We can tell eLandings what the original fish ticket number on the paper ticket was.
Enter the paper fish ticket number in the Paper Fish Ticket field.
By entering the paper fish ticket number, we help establish an audit trail from the paper ticket to the electronic system. After data entering the landing report into eLandings, you will want to print the electronic ticket and staple it to the front of the sign paper ticket as another means of establishing the audit trail between the paper and electronic system.
It is a good idea to write on the paper ticket with the signature, the landing report id, after you have saved the ticket in eLandings. In this way, if the paper and electronic printed tickets are separated, anyone looking at the signed paper copy will have a clear indicator that it was data entered into eLandings.
Next we want to enter the header information from the paper ticket
All eLandings tickets have an associated operation.
An eLandings operation is a collection of codes including the State of Alaska issued Processor Code, the Federal Permit Number, the Registered Buyer Number, the Registered Crab Receiver, port code, and vessel number. Not all of these codes are required. You may not know if the user has any of these operation codes. We ask that you just do the best you can.
In this case the ticket shows only two operation codes: the proc code and the port. 
The processor code = X0111
The port code = JNU
We will look and see if an operation already exists with this proc code and port code. If it doesn't exist, we will create it now.
Click on the Set Op button
You now see the Operation modal dialog.
Enter the Proc Code and port code and then click the search button.
In this case, an operation already exists that we can reuse. The operation id = 970111. We can click on 970111 to assign the operation to the landing report.
If the search finds no operations, we can click on the Create button at the top of the Operation modal dialog.
We won't create an new operation now, but just to show you what the screen looks like, click on the Create button now.
You should see the Create Operation modal dialog.
If we didn't find an operation, we would create one here. Typically, you use the Business's name as the operation name. If the proc code starts with an 'F', than set the Type of operation to "Plant/Reciever". If the proc code starts with a 'Z', than set the type of operation to "At-Sea Processor". If you have additional information about the operation to guide you in setting the operation type, than use that.
In general we want to have a minimum of a operation name, a processor code and a port. Set the status to active. If you have other codes, enter those. Just don't sweat too much about this. 
Click the cancel button on the Create Operation modal dialog.
If the paper ticket does not have a state of Alaska processor code and does not have a Federal Permit Number, than you will need to use a "missing processor code".
The missing processor code = 'M9999'
There are several operations that have already been created using M9999.
These include:
You could use one of these operations if they match the port code you need. You can always create another operation for another port code.
To see these, in the Operation Modal Dialog, Enter the Proc code = M9999, clear the port code field and click the search button.
To assign one of these operations to the ticket, you would click on the Operation ID field labeled "ID".
Fortunately, we know the processor code and port code, and we have an operation already. We will use that instead.
In the Operation Modal Dialog, Enter the Proc code = X0111, port code= JNU field and click the search button. Then click on the Operation ID 970111 to use this operation on the ticket we are data entering.
When you click on 970111, the Operation modal dialog will close and the operation id will show up on the landing report entry page.
Note: in the future we may display the operation id and operation name rather than the operation id.
Enter the CFEC permit and batching information.
Scroll down and click on the pencil on paper edit button in the CFEC Permits section.
You now see the Add CFEC Permit Modal Dialog
Notice that the Batch Year, Office, Batch Number and Sequence Ticket Number are blank.
You can data enter the Batch Year, Office, Batch Number now manually now.
Alternatively, you can tell the agency eLandings web page about the batch you will be working with.
I will demonstrate how to do that now.
Click the cancel button on the Add CFEC Permit Dialog Modal dialog.
Now we have to be very careful to avoid losing our work. We want to be sure we right click on the next step rather than left click. If you left click, you will lose your work!
Right-Click on "Agency" and click "Open link in new tab"
Then click on the new browser tab
This will take you back to the main page.
Click on Report > Set Batch Number
Enter the Batch Year = 2018, Office Code = Juneau, and Batch Number = 11. Then click ok.
You can set the Batch Information at any time.
By clicking OK on the Set Batch Information page, the system will take you to the landing report search page, where you can create a new landing or search for an existing landing report.
Note: if you want to change the Set Batch Information, you can always go back to it.
Note: if you want to clear the Set Batch Information, click on Report > Close Batch. We won't do that write now.
We already have a ticket half way data entered. We want to go back to the other browser tab.
Click on the first browser tab.
Now that we can see our partially data entered ticket again, click on the pencil on paper edit button in the CFEC Permits section.
Notice that the batching information that we entered into "Set Batching Information" is automatically entered into the Add CFEC Permit modal dialog now.
We will pretend that our next sequence ticket number in the batch is 61 and enter that.
This will really depend on your batching information that you create in the ADFG Fish Ticket App (Neptune, Trident, Venus, Zephyr) and what seq ticket number you are on.
We will enter the other information from the paper fish ticket
Notice that we entered the paper fish ticket number G02 000111 again to say this permit is associated with the fish ticket number. In the future, this may change to automatically assign a elandings system generated fish ticket number.
Click ok
Next we will enter the line item from the paper ticket
Click on the pencil on paper icon in the line item section.
The Add Itemized Catch modal dialog is displayed.
Note: in the future, this may be changed to show a blank line item in the itemized catch table. But for now it is a modal dialog.
Enter the line item data.
When you are done click the ok button.
Now click the save button at the bottom of the screen. 
The report is displayed in read only format after saving.
Once you are done with a batch be sure to click on Report > Close Batch