eLandings User Manual
Message Help 2300-2959
2300 ERROR: Gear Type is invalid |
|
|
|
2301 ERROR: Skate Length is required |
|
|
|
2302 ERROR: Skate Length is invalid |
|
|
|
2303 ERROR: Hook Size is required |
|
|
|
2304 ERROR: Hook Size is invalid | The hook size must be entered as a number. | Hook sizes are often identified as something like 12/0. This is not a number, and will not be accepted by eLandings. In this case the hook size should be entered as 12. | Enter the hook size as a number. |
2305 ERROR: Hook Spacing is required |
|
|
|
2306 ERROR: Hook Spacing is invalid |
|
|
|
2307 ERROR: Hooks Per Skate is required |
|
|
|
2308 ERROR: Hooks Per Skate is invalid |
|
|
|
2309 ERROR: Longline gear definition data is not allowed with non-longline gear | Longline gear required specific definition of things like skate length, hook size, and hook spacing. These definition fields are not allowed for other gear types. |
|
|
2310 ERROR: Either swivels on hooks or swivels on snaps should be indicated if the percent of gear with swivels is greater than zero | If the percent of gear with swivels is greater than zero, then the gear has swivels on hooks or swivels on snaps, and the appropriate flag should be checked. |
|
|
2311 ERROR: Hooks Per Skate is not consistent with Skate Length and Hook Spacing | Hooks per skate must be within 5 percent of skate length divided by hook spacing. |
|
|
2312 ERROR: Begin Depth is required |
|
|
|
2313 ERROR: Begin Depth must be numeric |
|
|
|
2314 ERROR: Begin Depth cannot be negative |
|
|
|
2315 ERROR: Begin Depth is too large |
|
|
|
2316 ERROR: End Depth is required |
|
|
|
2317 ERROR: End Depth must be numeric |
|
|
|
2318 ERROR: End Depth cannot be negative |
|
|
|
2319 ERROR: End Depth is too large |
|
|
|
2320 ERROR: Begin Buoy or Bag number is required |
|
|
|
2321 ERROR: Begin Buoy or Bag number is too long |
|
|
|
2322 ERROR: End Buoy or Bag Number is required |
|
|
|
2323 ERROR: End Buoy or Bag Number is too long |
|
|
|
2324 ERROR: Bird Avoidance Gear is required |
|
|
|
2325 ERROR: Bird Avoidance Gear is invalid |
|
|
|
2326 ERROR: Bird Avoidance Gear CODE not in effect for date DATE where: CODE is The numeric disposition code, indicating what is being done with the catch. DATE is The date entered for the announcement. |
|
|
|
2327 ERROR: Number of skates or pots set is required |
|
|
|
2328 ERROR: Number of skates or pots set must be numeric |
|
|
|
2329 ERROR: Number of skates or pots set cannot be negative |
|
|
|
2330 ERROR: Number of skates or pots set is too large |
|
|
|
2331 ERROR: Number of skates or pots lost is required |
|
|
|
2332 ERROR: Number of skates or pots lost must be numeric |
|
|
|
2333 ERROR: Number of skates or pots lost cannot be negative |
|
|
|
2334 ERROR: Number of skates or pots lost is too large |
|
|
|
2335 ERROR: Set Deploy not found for retrieval |
|
|
|
2336 ERROR: Comment Time is required |
|
|
|
2337 ERROR: Comment Time is invalid, must be HH:MM |
|
|
|
2338 ERROR: Comment Time must be on the date of the date being entered |
|
|
|
2339 ERROR: Comment Time is not allowed for comment code entered |
|
|
|
2340 ERROR: Gear ID cannot be a deleted gear profile on Add |
|
|
|
2341 ERROR: Begin Buoy or Bag Number is invalid |
|
|
|
2342 ERROR: End Buoy or Bag Number is invalid |
|
|
|
2343 ERROR: Begin Buoy or Bag Number cannot be the same as End Buoy or Bag Number |
|
|
|
2344 ERROR: Gear ID cannot be changed to a deleted gear profile |
|
|
|
2345 ERROR: Number of skates or pots lost cannot be greater than the number set |
|
|
|
2346 ERROR: Excel .xlsx file format not supported for templates, please save as Excel 97-2003 .xls file |
|
|
|
2347 ERROR: Landing Report REPORT_ID mixed salmon percentage cannot be undone where: REPORT_ID is The eLandings landing report ID | Mixed Salmon Percentage operations cannot be undone, if a user manually modifies the line items or grading and pricing items after the initial mixed salmon percentage was done or if mixed salmon percentage is not currently applied to this report. | A line item or grading and pricing item was manually modified by the user or this report was not processed through the mixed salmon percentage tool. | Review landing report and do manual corrections on this individual landing report. |
2348 ERROR: Template file must be Excel .xls file |
|
|
|
2349 ERROR: Percentage required for at least one species | Percentage is required for at least one species. |
| Enter a percentage for at least one species. |
2350 ERROR: Product Code CODE not in effect for date DATE where: CODE is The numeric disposition code, indicating what is being done with the catch. DATE is The date entered for the announcement. | The product code was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date. |
|
|
2351 WARNING: Report has retained catch (Disposition 87) and should be marked as partial delivery. A follow-up fish ticket will needed | Disposition code 87 indicates that catch is retained onboard for future sale. This is the definition of a partial delivery, so the partial delivery flag should be checked on the report. |
|
|
2352 ERROR: Query Parameter PARAMETER is missing where: PARAMETER is Parameter in query. | The query is expected to have the given parameter. If this error occurs, the query was constructed incorrectly. Please report this error to the eLandings developers. |
|
|
2353 ERROR: Query Description is required |
|
|
|
2354 ERROR: Query Description is too short |
|
|
|
2355 ERROR: Query Description is too long |
|
|
|
2356 ERROR: Query Description DESCRIPTION is invalid where: DESCRIPTION is The description of the query. |
|
|
|
2357 WARNING: Tare weight value is missing. This information may be required by the Processor. | No value was entered in the Tare Weight field. This warning is controlled by the Missing Tare Weight check box in the tLandings settings | No value was entered in the Tare Weight field | Enter the numeric value in the Tare Weight field |
2359 ERROR: User is not an administrative user for any operations |
|
|
|
2360 ERROR: Processor Code of a child operation must match the processor code of its parent |
|
|
|
2361 ERROR: Federal Permit Number of a child operation must match the federal permit number of its parent |
|
|
|
2362 ERROR: Registered Crab Receiver Number for a Buying Station cannot be the same as its parent |
|
|
|
2364 ERROR: Operations of type TYPE cannot have child operations where: TYPE is The operation type code. |
|
|
|
2366 ERROR: Custom processing Owner operation ID is required |
|
|
|
2367 ERROR: Owner operation OPID not found where: OPID is The operation ID. |
|
|
|
2368 ERROR: Custom processing Processor operation ID is required |
|
|
|
2369 ERROR: Processor operation OPID not found where: OPID is The operation ID. |
|
|
|
2370 ERROR: User USERID is not an active user for either the owner operation or the processor operation where: USERID is The eLandings system user ID. |
|
|
|
2371 ERROR: Operation Type TYPE cannot be custom processing owner where: TYPE is The operation type code. |
|
|
|
2372 ERROR: Operation OPID must be in normal status to be a custom processing owner where: OPID is The operation ID. |
|
|
|
2373 ERROR: Operation Type TYPE cannot be custom processing processor where: TYPE is The operation type code. |
|
|
|
2374 ERROR: Operation OPID must be in normal status to be a custom processing processor where: OPID is The operation ID. |
|
|
|
2379 ERROR: Dependent operation types, such as TYPE , must be created from the Operation Management page where: TYPE is The operation type code. |
|
|
|
2380 ERROR: User USER_ID is not authorized to update Landing Report REPORT_ID where: USER_ID is The eLandings system user ID. REPORT_ID is The eLandings landing report ID |
|
|
|
2381 ERROR: User USER_ID is not authorized to update Production Report REPORT_ID where: USER_ID is The eLandings system user ID. REPORT_ID is The eLandings landing report ID |
|
|
|
2382 ERROR: User USER_ID is not authorized to update Logbook REPORT_ID where: USER_ID is The eLandings system user ID. REPORT_ID is The eLandings landing report ID |
|
|
|
2385 ERROR: An active operation already exists for Processor Code PROC_CODE where: PROC_CODE is The ADF&G Processor Code, also know as the F-code. |
|
|
|
2386 ERROR: Landing Report REPORT_ID has already been submitted or landing report ID has been duplicated where: REPORT_ID is The eLandings landing report ID |
| anding Report has already been submitted or landing report id is has been duplicated. | Take note of landing reports in error and check eLandings system to ensure that report has been submitted correctly. If you cannot find the report, please contact elandings@alaska.gov. |
2387 INFO: UNSUBMITTED_COUNT unsubmitted and SUBMITTED_COUNT initially submitted TYPE landing reports found where: UNSUBMITTED_COUNT is The number of unsubmitted reports. SUBMITTED_COUNT is The number of initially submitted reports. TYPE is The operation type code. |
|
|
|
2388 ERROR: Report ID REPORT_ID already in the database as a TYPE report where: REPORT_ID is The eLandings landing report ID TYPE is The operation type code. |
|
|
|
2389 ERROR: Weight Unit of Measure must be pounds for Halibut or Sablefish |
|
|
|
2390 ERROR: Weight Unit of Measure not allowed without Weight |
|
|
|
2391 ERROR: Trip Entry Sequence of associated trip entry is required |
|
|
|
2392 ERROR: Trip Entry Sequence of associated trip entry is invalid, does not match a trip entry |
|
|
|
2393 ERROR: Trip with start date of DATE must be displayed before going active where: DATE is The date entered for the announcement. |
|
|
|
2394 WARNING: HAUL_SET : Total catch weight of WEIGHT UOM exceeds hail weight where: HAUL_SET is The haul or set number. WEIGHT is The weight in pounds. UOM is The weight unit of measure. |
|
|
|
2395 ERROR: Weight unit of measure cannot be changed if hauls or sets for voyage are already entered |
|
|
|
2396 ERROR: Go Inactive date cannot be prior to the trip start date DATE where: DATE is The date entered for the announcement. |
|
|
|
2397 ERROR: Go Active date cannot be in active period starting DATE where: DATE is The date entered for the announcement. |
|
|