eLandings Batching Manually Entered Tickets
Introduction
6/1/2018 – In a previous document, agencyELandingsTestPlan.docx, we discussed how eLandings ADFG users could use the Agency eLandings webpage to batch tickets in two waysThis document will describe how ADFG staff can use the Agency Web to assign batch information during data entry of paper tickets.
| Note |
|---|
Batching during data entry is not required. If the ticket is data entered but not batched at that time, ADFG users can use one of the methods listed above to assign batching information at a later time. |
There are multiple ways to batch tickets in the eLandings system. For tickets created electronically they include:
- Using the Auto Batching Tool for salmon or salmon troll report types.
- Opening a previously entered ticket and assigning batching information
...
However, ADFG users are often required to data enter paper fish tickets into the eLandings from a paper ticketsystem. 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 In this example we will walk through data entering 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: 
Log into the Agency Web system. If you need help doing this please see the Agency Web Users Manual.
| 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.
| Note |
|---|
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 
Click on "Create Landing Report" button. 
A modal dialog will appear entitled "Create Landing Report".
In Report Type select the Report Type combo Box, select . (ex. "Groundfish" and then click the create )
Click the 'Create' button. 
The Groundfish Landing Report Entry Screen will be displayed. (For purposes of the example it will be the GroundFish Landing Report Entry Screen).
Notice that the data entry screen was given a new landing report idLanding Report ID.
The landing report id Landing Report ID = 18326505
in this case.
| Note |
|---|
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.
| Tip |
|---|
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 |
...
signed paper ticket as another means of establishing the audit trail between the paper and electronic system. |
...
It is a good idea to |
...
add the newly created landing report id |
...
to the signed paper ticket once you have saved the electronic ticket in eLandings. |
...
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 Enter the header information from the paper ticket.
All eLandings tickets have an associated operationOperation.
An eLandings operation 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 codePort Code, and vessel numberVessel 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 Processor Code and the portPort Code.
The processor code Processor Code = X0111
The port code Port Code = JNU
We will look and
Check to see if an operation already exists with this proc code and port codeOperation with the same Processor Code and Port Code exists. If it doesn't exist, we will can 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.
' and 'Port'.
Click the 'Search' button.
Select the correct Operation from the table. If no Operation matches we can create one now by clicking the 'Create' button.
| Note | ||
|---|---|---|
| ||
In this case, an |
...
Operation already exists that we can reuse. The |
...
Operation ID = 970111. |
...
However, if the search finds no |
...
Operations, we can click on the 'Create' button at the top of the Operation modal dialog. |
...
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. |
...
To finish the creating a new Operation you would Click the 'Create' button and then you would be able to select your newly created Operation. Note: There been some issues with folks receiving ERROR 2891: Date of Landings cannot be before the date the Operation was created. If you get his error, please contact eLandings@alaska.gov and we will adjust the Operation date.
|
| Note | ||
|---|---|---|
| ||
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 |
...
'Proc Code' = 'M9999'. There are several |
...
Operations that have already been created using M9999. These include:
|
...
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' 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 |
...
'. |
Click on the 'ID' 970111 to use this operation Operation on the ticket we are data entering.
When you click on 970111, the 
The Operation modal dialog will close and the operation id will the ID you selected with 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. in the 'Operation' field.
Enter the CFEC permit Permit and batching 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 You can data enter the 'Batch Year', 'Office', and 'Batch Number now ' manually now .
Alternatively, you or you can tell the agency eLandings web page Agency Web 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
| Warning |
|---|
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
Click "Open link in new tab" 
Then click
Click on the new newly opened browser tab
This will take you back to , leaving the previous one open.
The new tab will open on the main page. 
Click on 'Report > '.
Click 'Set Batch Number'. 
Enter the 'Batch Year', 'Office Code', and 'Batch Number' to set your batching information.
| Note |
|---|
In this case we will enter 'Batch Year' = 2018, 'Office Code' = Juneau, and 'Batch Number' = 11. |
...
Click 'OK' to save the batch information.
| Tip |
|---|
You can set the Batch Information at any time |
...
during the data entry process. |
The Landing Report search page will open after you've clicked 'OK' to set the batch information.
| Note |
|---|
If you want to change the Set Batch Information, you can always go back to it. |
...
If you want to clear the Set Batch Information, click on Report > Close Batch. |
...
(Don't do that |
...
if you're following along with the example) |
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 
Enter the ticket sequence number in the 'Sequence Ticket Number' Field.
| Note |
|---|
For this example we will enter 61 in the 'Sequence Ticket Number' field. The actual sequence number will depend on the batching information that you |
...
created in the ADFG Fish Ticket |
...
Application (Neptune, Trident, Venus, Zephyr) and what |
...
the current sequence ticket number |
...
is. |
We will
enter Enter the other remaining information from the paper fish ticket.
Notice that we re-entered the paper fish ticket number G02 000111 again to say associate 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
Click 'OK'.
Next we will enter the line item data from the paper ticket.
Click on the pencil on paper icon in the line item 'Itemized Catch' 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
Enter the line item data from the paper fish ticket into the Add Itemized Catch modal dialog fields.
Click the 'OK' button.
Click the 'Save' button at the bottom of the screen to save the 'Itemized Catch' data.
The report is displayed in read only format after saving. 
Once you are done with a batch be sure to click close the batch.
Click on Report > Close Batch
Anchor
