Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Item_number
    The item_number element should not be specified in the import file. It is used to manage updates to reports after they have been submitted, and will be automatically generated at the time the report is initially submittedis just the sequential item number for the report. However, item numbers may have a break in their sequence if a report is submitted, and then a line item is deleted.
  2. Fish_ticket_number
    The fish_ticket_number element is not required. If it is specified the entire weight contains the fish ticket for the line item is allocated to that fish ticket. If not specified, the eLandings system will allocate the line item among the CFEC permits . It will match one of the fish ticket numbers specified on the permit worksheet.
    If provided, the fish_ticket_number value must match one of the values specified on the permit worksheet. The import process will replace the provided values with new fish ticket numbers, generated by the system, but will preserve the relationship of line items and permits It indicates the relationship between the CFEC permit and the catch, which is documented on the printed fish ticket.
  3. Stat_area
    The stat_area element is required if the stat area worksheet is not specified. If the stat area worksheet is provided then the stat_area element on the line item may still be specified. In that case it overrides the stat area worksheet for the weight reported on that line.Species
    The species element is requiredindicates the statistical area for the catch documented on the line item. The stat_are element is not required. If it is not present then the statistical areas for the catch documented on the line item are specified by the stat area worksheet. The percentages on the stat area worksheet indicate the allocation of the catch weight to statistical areas.
    The stat_area element has four attributes.
      • fed_area - The Federal Reporting Area where the statistical area lies.
      • fed_area_2 - If the statistical area crosses a federal reporting area boundary, the fed_area_2 attribute will be present, containing the second Federal Reporting Area. Otherwise, it will be omitted.
      • iphc_area - The IPHC Regulatory Area where the statistical area lies.
      • iphc_area_2 - If the statistical area crosses an IPHC area boundary, the iphc_area_2 attribute will be present, containing the second IPHC Regulatory Area. Otherwise, it will be omitted.
  4. Species
    The species element is always present. It is the ADF&G numeric species code, and it indicates the species of the catch documented on the line item.
    The species element includes one attribute, the species name.
  5. Condition_code
    The condition_code element is requiredalways present. It is a subset of the current fish ticket delivery codes. The valid condition code values will be available on the web application.Weight
    The weight element is requiredthe numeric condition code indicating the physical state of the catch in terms of processing already done to it. The condition code is used to determine the product recovery rate to apply to the line item weight to derive the round weigh of the catch documented on the line item.
  6. Weight
    The weight element is always present for sold items, and is usually present, except for discard items where only a count is documented. This element is the scale weight in pounds for the line item, unless the weight_modifier element indicates it is estimated weight. The weight may include up to 4 decimal places, and should will be less than 100 million.
  7. Weight_modifier
    The weight_modifier element is not requiredalways present. It should not be used for IFQ crab, but can be used for groundfish. However, the is primarily used on groundfish IFQ landing reports to document whether Ice and Slime is included in the weight. The Ice and Slime value can only be used for halibut and sablefish. The estimated value is used for hailed weight fish tickets, and should not be seen for line items on submitted The values will be:

    Value

    Description

    I/S

    Weight includes ice and slime

    Est

    Estimated weight

  8. Count
    The count element is required for IFQ crab, but will not be required for groundfish. The count element is the number of animals for crab landings, and the number of fish for discard lines on groundfish reports where weight is not available and number of fish is required by reporting requirements.
  9. Effort
    The effort element is conditionally required. If the stat area for the line item is not specified and the stat area worksheet is used then the effort element is not required. If the line item stat area is specified then effort is required for IFQ crab. This is the number of pot lifts. Effort is not allowed for groundfish.
  10. Disposition_code
    The disposition_code element is required. Disposition code is a subset of the current ADF&G delivery codes, and additions. The valid disposition code values will be available on the web application.
  11. Agency_line_data
    The agency_line_data element should not be specified in the import file.
  12. Product_item
    The product_item element not allowed for line items that have non-sold dispositions. Multiple product_item elements may be specified per line item, for cases where the line item amount has multiple sizes and grades. For line items with a condition code that can be either a primary or ancillary product, at least one product_item is required. In that case, if the disposition of the line item is not a sold disposition then the product_item may not have a price.
    1. Item_number
      The item_number element should not be specified in the import file. It is used to manage updates to reports after they have been submitted, and will be automatically generated at the time the report is initially submitted.
    2. Product_code
      The product_code element is required. Product code is a misnomer; this data element is actually the sold condition code. For IFQ crab it will be the same as the line item condition code. For groundfish it may be different, for example when the fisherman delivers whole sablefish, but is paid on the weight of dressed fish.
      For IFQ crab the product code must always be the same as the line item condition code.
    3. Product_type
      The product_type element is required. It indicates where the sold item is a primary product or an ancillary product. The values are

      Value

      Description

      P

      Primary product

      A

      Ancillary product

      R

      Reprocessed product

      For IFQ crab the value will always be 'P'. Reprocessed is used only for fishmeal, and generally should not be used unless instructed to do so by management agency personnel.
    4. Size_grade
      The size_grade element is not required. This is an optional field that allows processors to list sizing and grading information on the product items. It is freeform text, with a maximum length of 16 characters.
    5. Tare
      The tare element is the weight of the brailer or tote. This data element is not filled in on landing reports.
    6. Weight
      The weight element is required. This is the weight of the sold item. The total of the weights of all the product items for a line item cannot be more that the weight of the line item.
    7. Price
      The price element is required. The price can have up to 3 decimal places.
  13. Line_Item_stat_area
    The agency_line_data element should not be specified in the import file.
  14. Line Item Comment
    The line item comment is conditionally required. If the condition code for the line item is 97, the comment code for the line item comment should also be 97 and the comment text should contain a description of the condition of the fish. Disposition codes of 62 for overages and 64 for tagged fish also require comments. See the elandings online documentation for codes and valid combinations. In most cases the import files should not specify these dispositions, they should be edited in once the file is imported.
    1. Comment_code
      The code for the comment.
    2. Comment_test
      The text if needed.

...