...
There are multiple ways to batch tickets in the eLandings system. For tickets created electronically they include:
- Using the Auto Batching Tool Tool for salmon or salmon troll report types.
- Opening a previously entered ticket and assigning batching information to an Individual Landing Report.
...
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'.
Click the 'Search' button.
Select the correct operation 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 no Operation matches we can create one now by clicking the 'Create' button at the top of the Operation modal dialog.
Note | ||
---|---|---|
| ||
In this case, an operation Operation already exists that we can reuse. The operation id Operation ID = 970111. However, if the search finds no operationsOperations, 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 operationOperation, we would create one here. Typically, you use the Business's name as the operation name. If the proc code 'Proc Code' starts with an 'F', than set the 'Type' of operation Operation to "Plant/Reciever". If the proc code 'Proc Code' starts with a 'Z', than set the type 'Type' of operation Operation to "At-Sea Processor". If you have additional information about the operation Operation to guide you in setting the operation typeOperation Type, than use that. In general we want to have a minimum of a operation nameOperation Name, a processor code Processor Code and a portPort. 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 Operation you would Click the 'Create' button and then you would be able to select your newly created operationcreated 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 codeMissing Processor Code". The missing 'Proc Code' = 'M9999'. There are several operations Operations that have already been created using M9999. These include:
To assign one of these operations 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.
...