...
| 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:
To assign one of these Operations to the ticket, you would click on the Operation ID field labeled 'ID'. |
...