Introduction

This document will describe how ADFG staff can use the Agency Web to assign batch information during data entry of paper tickets.

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
Opening a previously entered ticket and assigning batching information to an Individual Landing Report.

However, ADFG users are often required to data enter paper fish tickets into the eLandings system. 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.

Assigning Batching Info during Data Entry

In this example we will walk through data entering a paper Groundfish ticket that does not exist in eLandings yet.

Log into the Agency Web system. If you need help doing this please see the Agency Web Users Manual.

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".

You can always get back to this page by clicking on the Agency menu item at the top left of the screen.

Click on "Create Landing Report" button.

A modal dialog will appear entitled "Create Landing Report".

In Report Type select the Report Type. (ex. "Groundfish")

Click the 'Create' button.

The 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 ID.

The Landing Report ID = 18326505 in this case.

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 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 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'.

Click the 'Search' button.

Select the correct operation from the table. In this case 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.

Create an Operation

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.

Missing 'Proc Code'

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:

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' 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 on the ticket we are data entering.

The Operation modal dialog will close and the the ID you selected with show up in the 'Operation' field.

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 'Batch Year,' 'Office', 'Batch Number' and 'Sequence Ticket Number' are blank. You can data enter the 'Batch Year', 'Office', and 'Batch Number' manually now or you can tell the Agency Web about the batch you will be working with.

Click the cancel button on the Add CFEC Permit Dialog Modal dialog.

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"

Click "Open link in new tab"

Click on the newly opened browser tab, 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.

In this case we will enter 'Batch Year' = 2018, 'Office Code' = Juneau, and 'Batch Number' = 11.

Click 'OK' to save the batch information.

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.

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.

Enter the ticket sequence number in the 'Sequence Ticket Number' Field.

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.