Page Comparison

...

1. Item_number
   The item_number element is 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 contains the fish ticket for the line. It will match one of the fish ticket numbers specified on the permit worksheet.
   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 indicates 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 always present. It is the 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 will be less than 100 million.
7. Weight_modifier
   The weight_modifier element is not always present. It 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 always present for IFQ crab , but will not be required sold items and salmon, is generally not populated for groundfish. The count element is the number of animals for crab landings, and the number of fish for accounted for on that line item. For discard lines on groundfish reports where weight is not available and number of fish is required by reporting requirementscount will be present if weight is omitted.
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.used for IFQ crab. This is the number of pot lifts. Effort will not be present for groundfish or salmon reports. Effort on crab landing reports may not be present if the line item does not have a statistical area noted. In that case the effort is documented on the statistical area worksheet.
10. Disposition_code
    The disposition_code element is required. Disposition code is a subset of the current ADF&G delivery codes, and additionswill always be present. It identifies the final usage or action of the line item, such as sold for human consumption or discarded at sea. The valid disposition code values will be are available on the web application.
11. Agency_line_data
    The agency_line_data element should not be specified in the import filewill be omitted from reports that are made visible to processors and third party systems.
12. Product_item
    The product_item element not allowed may be present for line items that have non- sold dispositions, and in certain other cases. 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 requiredwill be present. In that case, if the disposition of the line item is not a sold disposition then the product_item may will 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 submittedis just the sequential item number for the product items under the line item. However, item numbers may have a break in their sequence if a report is submitted, and then a product item is deleted.
    2. Product_code
       The product_code element is requiredwill always be present. 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.
       whole sablefish, but is paid on the weight of dressed fish. In general, salmon product items have the same product code as their line item, but it could be different if the processor wishes to price by a particular condition that is different than the delivery condition. 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 will not requiredalways be present. 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 charactersthe product items. It is freeform text. Processors are free to price product items without providing size/grade information.
    5. Tare
       The tare element is not populated on landing reports extracted from eLandings. Tare is the weight of the brailer or tote. This data element is used by the tLandings subsystem, but is not filled in on landing reports.
    6. Weight
       The weight element is requiredwill always be present. This is the weight of the sold item. The total of the weights of all the product items for a line item cannot will not be more that the weight of the line item, but could be less if the product codes are not the same as the product code on the line item.
    7. Price
       The price element is required. The price can have up to 3 decimal places3 decimal places. In some cases the price will be zero.
13. Line_Item_stat_area
    The agencyline_item_linestat_data area element should will not be specified in the import filepresent.
14. Line Item Comment
    The line item comment is conditionally requiredpresent in specific situations. If the condition code for the line item is 97, the comment code for the line item comment should will also be 97 and the comment text should will contain a description of the condition of the fish. Disposition codes of 62 for overages and 64 for tagged fish also require commentsindicate that a comment should be expected. 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 comment_code element is the code for the comment.
    2. Comment_test
       The text if neededinformation for the comment, if any was entered.

Ifq_report

The ifq_report element may be present for landing reports for IFQ species. The ifq_report element will be present only if the IFQ report was submitted through the eLandings system. IFQ reports that were made to the NMFS data clerks will not appear in the landing report XML file. The ifq_report element has ten attributes. The attributes will be populated if the IFQ report was submitted. If the report was not submitted, the attributes for this element, and many of the attributes for other elements will not be populated. Submitted reports will have a return_code of "000" or "001"

...