Page Comparison

...

Ifq_report

The ifq_report element is not required. The eLandings system has features that generate IFQ reports from line item data. The report generation process is fairly complex, and the user is allowed to edit the generated IFQ reports before they are submitted. However, all IFQ reports, however generated and edited, must pass validation checks that insure consistency between the fish tickets and the IFQ reports.
Although not recommended, the ifq_report elements may be specified in the import file if a processor desires to generate them outside of the eLandings system.

...

...

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"

• • return_msg - the text of the message associated with the return code
  • return_code - the return code for the submission of the the IFQ report
  • card_holder - the name of the IFQ cardholder, as identified by the NMFS person ID on the report.
  • permit_holder - the name of the IFQ permit holder. This may be the same as the card holder, or may be different in the case of hired skippers.
  • tran_date_time - the date and time the IFQ report was submitted.
  • tran_number - the transaction confirmation number of the IFQ report
  • net_ifq_weight - the weight debited from the IFQ permit
  • net_ipq_weight - the weight debited from the IPQ permit, if one was entered.
  • class_code - the class code for the IFQ report.
  • sector_code - the sector code for the IFQ report.

1. Item_number
   The item_number element indicate the report in sequence.
2. Nmfs_person_id
   The nmfs_person_id element identifies the individual who did the fishing. The nmfs_person_id has one attribute, the person name
3. Ifq_permit_number
   The ifq_permit_number element identifies the IFQ permit that was debited for the report. The ifq_permit_number includes two attributes.
   • name - the name of the permit holder
   • permit_class - the permit class for crab IFQ. This element is omitted for Halibut and Sablefish IFQ.
4. Fish_ticket_number
   The fish_ticket_number element associates the IFQ report with a specific fish ticket, and hence a CFEC permit.
5. Ipq_permit_number
   The ipq_permit_number element indicates the IPQ permit that will be debited. It will only be present on crab reports, and then only if the IFQ permit is a class A permit. For Halibut and Sablefish IFQ reports it will always be omitted.
6. Fishery
   The fishery element is never present for IFQ crab or sablefish reports. For IFQ halibut it specifies a fishery type if the halibut was harvested as bycatch in another fishery. In most cases it will be omitted since this is a rare condition. The values are:

   Value	Description
   L	Dinglebar troll lingcod fishery
   S	Salmon troll fishery

7. Species
   The species element will always be present. It contains the species code.
   The species element includes one attribute, the species name.
8. Ifq_item
   At least one ifq_item element will always be present, but more than one ifq_item may occur. The ifq_item element has one attribute, the ifq_fishery which is the name of the fishery and/or area.
   1. Item_number
      The item_number element indicates the item in sequence.
   2. Stat_area
      The stat_area element will always be present.
      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. The iphc_area element will be omitted from crab IFQ items.
      • 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.
   3. Iphc_regulatory_area
      The iphc_regulatory_area element will not be for IFQ crab or sablefish. It will always be present for IFQ halibut. It indicates the IPHC area for which quota was debited.
   4. Condition_code
      The condition_code element will always be present.
      • The condition_code element has one attribute, the name describing the condition identified by the code.
   5. Ice_and_slime
      The ice_and_slime element is used for IFQ halibut and sablefish IFQ items.
   6. Price
      The price element is used only with IFQ crab. It will be omitted from IFQ halibut and sablefish reports.
   7. Sold_weight
      The sold_weight element indicates the weight sold on the IFQ report.At least one of sold weight, retained weight, or deadloss weight will be present on IFQ items. If the item has no sold weight this element will be omitted
   8. Retained_weight
      The retained_weight element indicates the weight retained by the fisherman for future sale or personal use. If the item has no retained weight this element will be omitted.
   9. Deadloss_weight
      The deadloss_weight element indicates the deadloss for crab deliveries. It will never be present for halibut and sablefish IFQ reports. It a crab IFQ item has not deadloss this element will be omitted.

...