Page Comparison

Production_report

The producxtionproduction_report element is the top level element in production report files.

...

The messages element provides error and information messages about reports that are submitted to the eLandings server. It should not be specified on reports that are to be imported into eLandings. It will be omitted from reports that are successfully exported from eLandings. The messages element may contain any number of message elements.

The schema version data element allows the software to know the version of the schema for which an XML file was generated. If the schema version element is not provided that indicates the version is 1.0, the original groundfish release production schema. The contents of the schema version element corresponds to the version attribute in the <xs:schema> element of the schema, the top level element of the schema definition.
Image Removed
Note that this is NOT the version attribute in the <xml> element that contains the schema definition. That attribute defines the version of XML, as specified by the W3C consortium.

Production_report_id

The production_report_id is the unique identifier for production reports. The actual number is generated by the eLandings system.

Type of Production Report

The type of production report distinguishes between At-sea, with a type of "A", and Shoreside, with a type of "S".

Status

The status element contains the submission status of the production report. Reports that are to be imported into eLandings should set the status to zero. Values are:

The status element includes a desc attribute, with the text value of the status code.

Transmission

The transmission element is used internally by the eLandings system when reports are transmitted from the seaLandings Processor Workstation software to the server. It is omitted in files exported from eLandings.

Production_report_header

The production_report_header element contains the data that applies to the entire production report.

1. Report_date
   The report_date element is the date of the production being reported.
2. Federal_processor_number
   The federal_processor_number is the federal_processor_permit number for the processor who submitted the report. It is typically omitted from salmon reports. The federal_processor_number element includes three attributes:
   • name - the name of the processing company, plant, or at-sea processing vessel
   • at_sea_proc - a boolean flag indicating the permit is a federal fisheries permit for an at-sea processor. This attribute is omitted from landing reports exported from eLandings.
   • license_year - the most recent year for which the processor was licensed. This attribute is omitted from landing reports exported from eLandings.
3. No_deliveries
   The no_deliveries element is a flag indicating that no deliveries from catcher vessels were received on the date.
4. No_production
   The no_production element is a flag indicating that no processing was done on the date. If the no_production element is set to "true" then the report will not have production_item elements.
5. Vessel
   The vessel element is the vessel ADF&G number, for at-sea operations. It will not be present for shoreside reports.
   • The vessel element includes a name attribute, which contains the name of the vessel
6. Gear
   The gear element is the ADF&G gear code, as entered on fish tickets. It will be present on at-sea reports, but will not be on shoreside reports.
   • then gear element includes a name attribute, which contains the name of the gear type.
7. Crew_size
   The crew_size element is the number of crew onboard, including the skipper, but excluding any observers. It will only be present for at-sea production reports.
8. Port_of_landing
   The port_of_landing element is the ADF&G port code, as entered on fish tickets. It will be present for at-sea production reports, and it will contain the port code value for the at-sea operation type, such as Catcher/Processor or floating inshore processor.
   The port_of_landing element includes two attributes.
   • the name attribute contains the text name of the port or at-sea operation type
   • the ifq_port_code contains the numeric IFQ system port code, as used on IFQ reports. The IFQ port code appears even on reports that do not include IFQ. It is merely an attribute of the alphabetic port code and its presence does not imply IFQ reporting.
9. Observers
   The observers element is the number of observers in the plant or onboard the vessel.
10. Proc_code
    The proc_code element identifies the entity that purchases or otherwise controls the fish, and is equivalent to the proc code embossed on paper fish tickets. It will only be present for shoreside production reports.
    • The proc_code element includes a processor attribute, which contains the name of the processor, as listed on their intent to operate application.
11. Fed_area
    The fed_area element contains the Federal reporting area number where the fish were harvested. It will only be present for at-sea production reports.
12. Special_area
    The special_area element contains the special area code where the fish were harvested, if the harvest was within one of the special areas. It will only be present for at-sea production reports, and will only be present if the harvest took place within a special area.
    1. Management_program
       The management_program element identifies the management program under which the fishing took place. It will be present only for at-sea reports.
       • Program
         The program element is the management program abbreviation such as IFQ, CDQ, AFA, or OA.
       • Program_id
         The program_id element is participant identifier. It will be present if the management program has participant IDs. CDQ numbers for CDQ and Co-op numbers for AFA, are examples of program ids. If the management program has no participant numbers, such as ADAK, then this element will be omitted.
13. Trip_event_code
    The trip_event_code element indicates events that can occur on at-sea processor trips, which affect maximum retainable amounts. It will be present only for at-sea reports, and only if one of the events occurred on the date of the report.

1. Stat_area_worksheet
   The stat_area_worksheet element will be present for at-sea reports, but not for shoreside reports.
   More that one stat_area_worksheet elements may be specified.
   1. Item_number
      he item_number element is just the sequential item number for the stat area worksheet item. However, item numbers may have a break in their sequence if a report is submitted, and then a stat area worksheet item is deleted.
   2. Stat_area
      The stat_area element always present This is the ADF&G 6 digit groundfish statistical area.
   3. Percent
      The percent element will always be present. The total of percents for all stat_area_worksheet elements will equal 100.
   4. Effort
      The effort element is not used for production reports, and will always be omitted.
   5. Count
      The count element is not used on production reports, and will always be omitted.

1. Coded_comment
   The coded_comment element is used for agency purposes. It will not appear in reports exported from eLandings, and should not be specified for reports that are to be imported to eLandings.

...

• Proc_code
  The proc_code element is the ADF&G intent to operate processor code, also known as the F-code.
  • The proc_code element includes a processor attribute, which contains the name of the processor, as listed on their intent to operate application.

...

• Proc_code
  The proc_code element is the ADF&G intent to operate processor code, also known as the F-code.

...

• name - the name of the processing company, plant, or at-sea processing vessel
• license_year - the most recent year for which the buyer was licensed. This attribute is omitted from landing reports exported from eLandings.

...

• name - the name of the processing company, plant, or at-sea processing vessel
• license_year - the most recent year for which the buyer was licensed. This attribute is omitted from landing reports exported from eLandings.

...

...

• The tender_vessel element includes a name attribute, which contains the name of the vessel.

...

...

The message element has four attributes

• The msgid attribute provides a unique identifier for the message, which can be used to lookup further information on the eLandings website.

  Data Type	Since Schema Version	Oracle Database Data Definition	Values
  integer	1.0	NUMBER(10,0)	Msg IDs will typically be between 1000 and 99,999. Msg IDs can be looked up on the eLandings website

• The severity_code attribute identifies the severity of the message

  Data Type	Since Schema Version	Oracle Database Data Definition	Values
  text	1.0	N/A	The severity code values and translations are: S - System Error E - Error W - Warning I - Information

• The severity_desc attribute is the translation of the severity code.
• The prefix attribute is a message prefix that relates the message to particular lines or items in the XML document.

  Data Type	Since Schema Version	Oracle Database Data Definition	Values
  text	1.0	N/A	The prefix is not applicable to all messages. Where used it has values such as "Line x, Grading/pricing line y".

Schema Version

The schema version data element allows the software to know the version of the schema for which an XML file was generated. If the schema version element is not provided that indicates the version is 1.0, the original groundfish release production schema. The contents of the schema version element corresponds to the version attribute in the <xs:schema> element of the schema, the top level element of the schema definition.
Image Added
Note that this is NOT the version attribute in the <xml> element that contains the schema definition. That attribute defines the version of XML, as specified by the W3C consortium.

Production_report_id

The production_report_id is the unique identifier for production reports. The actual number is generated by the eLandings system.

Type of Production Report

The type of production report distinguishes between At-sea, with a type of "A", and Shoreside, with a type of "S".

Status

The status element contains the submission status of the production report. Reports that are to be imported into eLandings should set the status to zero.

The status element includes a desc attribute, with the text value of the status code.

Transmission

The transmission element is used internally by the eLandings system when reports are transmitted from the seaLandings Processor Workstation software to the server. It is omitted in files exported from eLandings.

Production_report_header

The production_report_header element contains the data that applies to the entire production report.

1. Report_date
   The report_date element is the date of the production being reported.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   date	1.0	DATE	Date of the report, referring to the date when the production took place.

2. Federal_processor_number
   The federal_processor_number is the federal_processor_permit number for the processor who submitted the report. It is typically omitted from salmon reports.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(6,0)	Federal Processor Number is the Federal Processing Permit for Shoreside Production Reports and At-Sea Production Reports for motherships, and the Federal Fisheries Permit for catcher/processors.

   The federal_processor_number element includes three attributes:
   • name - the name of the processing company, plant, or at-sea processing vessel

     Data Type	Since Schema Version	Oracle Database Data Definition	Values
     text	1.0	VARCHAR2(50)	Federal Processor Number Name is the name of the processor.

   • at_sea_proc - a boolean flag indicating the permit is a federal fisheries permit for an at-sea processor. This attribute is omitted from production reports exported from eLandings.
   • license_year - the most recent year for which the processor was licensed. This attribute is omitted from production reports exported from eLandings.
3. No_deliveries
   The no_deliveries element is a flag indicating that no deliveries from catcher vessels were received on the date.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   boolean	1.0	CHAR(1)	No Deliveries indicates whether or not the operation received deliveries from catcher vessels on the date of the report. No Deliveries only applies to Shoreside production reports. Value will be TRUE or FALSE.

4. No_production
   The no_production element is a flag indicating that no processing was done on the date. If the no_production element is set to "true" then the report will not have production_item elements.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   boolean	1.0	CHAR(1)	No Production indicates whether or not the operation did production on the date of the report. No Production indicates that the lack of production items is because there was no data to report. Value will be TRUE or FALSE.

5. Vessel
   The vessel element is the vessel ADF&G number, for at-sea operations. It will not be present for shoreside reports.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(5,0)	Vessel is the ADF&G Number of the at-sea processing vessel. Vessel ADF&G numbers can be looked up on the CFEC website. Vessel applies to At-Sea production reports only.

   • The vessel element includes a name attribute, which contains the name of the vessel

     Data Type	Since Schema Version	Oracle Database Data Definition	Values
     text	1.0	VARCHAR2(50)	Vessel names can be looked up on the CFEC website, as above.

6. Gear
   The gear element is the ADF&G gear code, as entered on fish tickets. It will be present on at-sea reports, but will not be on shoreside reports.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   1.0	integer	NUMBER(3,0)	Gear is the eLandings gear code. Valid values can be looked up on the eLandings website. Gear applies to At-Sea production reports only.

   • The gear element includes a name attribute, which contains the name of the gear type.

     Data Type	Since Schema Version	Oracle Database Data Definition	Values
     text	1.0	VARCHAR2(25)	Gear name is the description of the gear associated with the gear code. Values can be looked up on the eLandings website, as above.

7. Crew_size
   The crew_size element is the number of crew onboard, including the skipper, but excluding any observers. It will only be present for at-sea production reports.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(3,0)	Crew size is the size of the crew including the skipper, for at-sea processors. Crew Size applies to At-Sea production reports only. Rules for crew size are documented by the eLandings business rules

8. Port_of_landing
   The port_of_landing element is the ADF&G port code, as entered on fish tickets. It will be present for at-sea production reports, and it will contain the port code value for the at-sea operation type, such as Catcher/Processor or floating inshore processor.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   text	1.0	CHAR(3)	Port of landing is the eLandings port code for Shoreside production reports, or the at-sea operation type for At-Sea production reports. Valid values can be looked up on the eLandings website

   The port_of_landing element includes two attributes.
   • the name attribute contains the text name of the port or at-sea operation type

     Data Type	Since Schema Version	Oracle Database Data Definition	Values
     text	1.0	VARCHAR2(50)	Port of landing name is the city or location associated with the port code. Values can be looked up on the eLandings website, as above.

   • the ifq_port_code contains the numeric IFQ system port code, as used on IFQ reports. The IFQ port code appears even on reports that do not include IFQ. It is merely an attribute of the alphabetic port code and its presence does not imply IFQ reporting.
9. Observers
   The observers element is the number of observers in the plant or onboard the vessel.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(2,0)	Observers is the number of observers in the processing plant. Observers applies to Shoreside production reports only. Rules for observers onboard are documented by the eLandings business rules

10. Proc_code
    The proc_code element identifies the entity that purchases or otherwise controls the fish, and is equivalent to the proc code emprinted on paper fish tickets. It will only be present for shoreside production reports.

    Data Type	Since Schema Version	Oracle Database Data Definition	Values
    text	1.0	VARCHAR2(6)	Proc code is the ADF&G processor code of the processing plant for Shoreside production reports. It is not used on At-Sea production reports.

    • The proc_code element includes a processor attribute, which contains the name of the processor, as listed on their intent to operate application.

      Data Type	Since Schema Version	Oracle Database Data Definition	Values
      text	1.0	VARCHAR2(50)	Proc code processor is the name of the processor.

11. Fed_area
    The fed_area element contains the Federal reporting area number where the fish were harvested. It will only be present for at-sea production reports.

    Data Type	Since Schema Version	Oracle Database Data Definition	Values
    integer	1.0	NUMBER(6,0)	Fed area is the Federal reporting area where the catch took place. Valid values can be looked up on the eLandings website

12. Special_area
    The special_area element contains the special area code where the fish were harvested, if the harvest was within one of the special areas. It will only be present for at-sea production reports, and will only be present if the harvest took place within a special area.

    Data Type	Since Schema Version	Oracle Database Data Definition	Values
    text	1.0	VARCHAR2(5)	Valid special areas are: AISWW - Aleutian Islands State Waters West of 120W COBLZ - Opilio Crab Bycatch Limitation Zone RKCSA - Red King Crab Savings Area

13. Management_program
    The management_program element identifies the management program under which the fishing took place. It will be present only for at-sea reports.
    1. • Program
         The program element is the management program abbreviation such as IFQ, CDQ, AFA, or OA.

         Data Type	Since Schema Version	Oracle Database Data Definition	Values
         text	1.0	VARCHAR2(5)	The abbreviation of the management program under which the fishing took place. The valid values can be looked up on the eLandings website

       • Program_id
         The program_id element is participant identifier. It will be present if the management program has participant IDs. CDQ numbers for CDQ and Co-op numbers for AFA, are examples of program ids. If the management program has no participant numbers, such as ADAK, then this element will be omitted.

         Data Type	Since Schema Version	Oracle Database Data Definition	Values
         integer	1.0	NUMBER(3,0)	The management program participant ID, for management programs that require participant IDs. The valid values can be looked up on the eLandings website

14. Trip_event_code
    The trip_event_code element indicates events that can occur on at-sea processor trips, which affect maximum retainable amounts. It will be present only for at-sea reports, and only if one of the events occurred on the date of the report.

    Data Type	Since Schema Version	Oracle Database Data Definition	Values
    integer	1.3	NUMBER(2,0)	Trip event code values are: 1 - New Week 2 - Gear Change 3 - Offloaded Product 4 - Directed Fishing Closure 5 - Enter SSL Protection Area 6 - Leave SSL Protection Area

Stat_area_worksheet

The stat_area_worksheet element will be present for at-sea reports, but not for shoreside reports.
More that one stat_area_worksheet elements may be specified.

1. Item_number
   he item_number element is just the sequential item number for the stat area worksheet item. However, item numbers may have a break in their sequence if a report is submitted, and then a permit stat area worksheet item is deleted.Cfec
2. Stat_permitarea
   The cfecstat_permit area element is the entire CFEC permit information needed to identify the permit.
   • Fishery
     The fishery element is the fishery code on the CFEC permit card.
   • Permit_number
     The permit_number element is is the unique permit number on the CFEC card. It is a five digit number followed by one alphabetic check character.
   • Year_seq
     The year_seq element is is the year and card sequence from the CFEC card. It is a two digit year, a two digit sequence number, and one alphabetic check character.
3. Mag_stripe_read
   The mag_stripe_read element identifies identifies whether the CFEC permit date was read into the eLandings system by swiping the magnetic stripe on the CFEC permit card.

1. 1. Percent
      The percent element is is used by the eLandings system when allocating line items to stacked permits. The percents on the permit worksheet elements will add up to 100. Percent may be specified as zero.
   2. Fish_ticket_number
      The fish_ticket_number element contains the fish ticket number for the permit.
   3. Fish_ticket_sequence
      The fish_ticket_sequence element is the internal agency batch sequence for the fish ticket. It will be omitted for XML files seen by processors and third party systems.
   4. Batch Year
      The batch_year element is the internal agency batch year for the fish ticket. It will be omitted for XML files seen by processors and third party systems.
   5. Batch Office Code
      The batch_office code element is the internal agency office code of the office that data enters the the fish ticket receipt data. It will be omitted for XML files seen by processors and third party systems.
   6. Batch_number
      The batch_number element is the internal agency batch identifier for the fish ticket. It will be omitted for XML files seen by processors and third party systems.
   7. Ifq_permit_worksheet
      The ifq_permit_worksheet element is used for IFQ permit information. Multiple ifq_permit_worksheet elements may be provided for each CFEC permit, allowing multiple IFQ permits to be stacked on each CFEC permit.
      1. Item_number
         The item_number element is just the sequential item number for the ifq permit. However, item numbers may have a break in their sequence if a report is submitted, and then an ifq permit item is deleted.
      2. Ifq_permit_number
         The ifq_permit_number element is the IFQ system permit identfier.
      3. Nmfs_person_id
         The nmfs_person_id element is the unique ID issued by NMFS to each person authorized to fish for IFQ species, whether a permit holder or a hired skipper. The nmfs_person_id will be the same for all ifq_permit_worksheet elements associated with a single CFEC permit.
      4. Species
         The species element is the ADF&G species code associated with the permit.
      5. Fishery_area
         The fishery_area element is used by the eLandings system when allocating line items to permits. The fishery area elements specifies the area or fishery where the permit has quota, and is used to allocate itemized catch from that area or fishery to the permit. This element is typically used in conjunction with the pounds element to "max out" a permit.
      6. Pounds
         The pounds element is used by the eLandings system when allocating line items to permits. The pounds element specifies an amount of IFQ quota pounds to allocate to that permit. This is typically used to "max out" a permit that is close to the end of its quota.
      7. Ipq_permit_number
         The ipq_permit_number is conditionally required for crab landings. It will not be present for groundfish landings. If the IFQ permit is a class A permit, then an IPQ number will be present. The IPQ permit will be associated with the RCR number specified in the header.

1. Dual_permit
   The dual_permit element is a boolean flag that indicates, two or more CFEC permit holder was present on the vessel when the fishing occurred. This flag may not be applicable in all fisheries and is subject to regulation. Legal use of this box is only available is specific areas. Check with your local ADF&G staff before using this box. This flag is typically used for Salmon. The presence of multiple permits on the fish ticket increases fishing limits. When dual permit is used, only one CFEC permit is recorded on the fish ticket.
2. Tender_trip_number
   The
3. Total_tare
   The
4. Fishing_period
   The
5. Out_of_state
   The
6. Tender_batch
   The
7. Tally_invoice
   The
8. Floating
   The
9. Slide
   The

Line_item

At least one line_item element is required.

• • The line item element has one attribute, the round weight for the item.

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.
4. 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.
5. 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 omittedalways present This is the ADF&G 6 digit groundfish statistical area.

Data Type	Since Schema Version	Oracle Database Data Definition	Values
integer	1.0	NUMBER(6,0)	Stat area is the statistical area where the catch took place. Valid values can be looked up on the eLandings website

6. Percent
   The percent element will always be present. The total of percents for all stat_area_worksheet elements will equal 100.
7. Effort
   The effort element is not used for production reports, and will always be omitted.
8. Count
   The count element is not used on production reports, and will always be omitted.

Production_item

The production_item element is used on both at-sea and shoreside reports, but may not be present if the value of the no_production flag is true.

• The production_item element has one attribute, the round weight for the item.

  Data Type	Since Schema Version	Oracle Database Data Definition	Values
  decimal	1.1	NUMBER(13,4)	Round weight is the weight for the production or discard item, converted to round, or green weight according to the condition code. Values will be between 0 and 999,999,999.9999

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 production item is deleted.
2. Fmp_area
   The fmp_area element contains the Federal Management Plan area for the line. For at-sea reports the Federal area reported in the header must be in the FMP area reported for each production item.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	VARCHAR2(5)	Federal Management Plan area. FMP Area only applies to Shoreside production reports. Values are: BSAI - Bering Sea and Aleutian Islands GOA - Gulf of Alaska

3. 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.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(3,0)	Species is the numeric species code. Valid values can be looked up on the eLandings website

   The species element includes one attribute, the species name.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   text	1.0	VARCHAR2(60)	Species name is the name associated with the species code. Values can be looked up on the eLandings website, as above

4. Product_type
   The product_type element is required. It indicates where the sold item is a primary product or an ancillary product.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   text	1.0	CHAR(1)	Product type identifies whether the item is the main product produced from the fish, or is additional product. Valid values are: P - Primary A - Ancillary R - Reprocessed

5. Product_code
   The product_code element is always present. It is the numeric condition code indicating the physical state of the catch in terms of what processing was done to it. The condition code is used to determine the product recovery rate to apply to the production item weight to derive the round weigh of the catch documented on the production item.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(3,0)	Product code is the condition of the fish regarding processing that has taken place. Valid values can be looked up on the eLandings website, as condition codes

6. Weight
   The weight element is This element is the scale weight for the production item. The weight may include up to 4 decimal places, and will be less than 100 million. For at-sea production reports, the weight is reported in metric tons. For shoreside production reports, the weight is reported in pounds.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   decimal	1.0	NUMBER(13,4)	Weight is the scale weight of the production or discard item. It will be between 0 and 999,999,999.9999

7. Line Item Comment
   The line item comment present in specific situations. The only current use is if the product code for the production item is 97, the comment code for the line item comment must also be 97 and the comment text will contain a description of the condition of the fish.
   1. Comment_code
      The comment_code element is the code for the comment.

      Data Type	Since Schema Version	Oracle Database Data Definition	Values
      integer	1.0	NUMBER(2,0)	The only valid comment code is 97 - description of other condition

      The text information for the comment, if any was entered.

      Data Type	Since Schema Version	Oracle Database Data Definition	Values
      text	1.0	VARCHAR2(500)	The comment text is required for comment 97. It can be any text.

8. Line_Item_stat_area
   The line_item_stat_area element is used internally by the eLandings system, and will not be present in exported or imported files.

Discard_item

The discard_item element is used on at-sea production reports to document discards. It will not be present on shoreside reports.

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. Species
   The species element is always present. It is the ADF&G numeric species code, and it indicates the species of the catch discard documented on the line item.discard item.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(3,0)	Species is the numeric species code. Valid values can be looked up on the eLandings website

   The species element includes one attribute, the species name.
3. 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.
4. 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.
5. 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

6. Count
   The count element is always present for IFQ crab sold items and salmon, is generally not populated for groundfish. name.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   text	1.0	VARCHAR2(60)	Species name is the name associated with the species code. Values can be looked up on the eLandings website, as above

7. Disposition_code
   The disposition_code element will always be present. It identifies the discard disposition of the discard item, such as discarded at sea or donated to a food bank.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   integer	1.0	NUMBER(3,0)	Disposition code is the numeric code indicating the disposition of the discard item. Valid values can be looked up on the eLandings website

8. Weight
   The weight element is may be present for discard items, but may be omitted on discard items where only a count is documented. This element is the scale weight in pounds for the discard item. The weight may include up to 4 decimal places, and will be less than 100 million.

   Data Type	Since Schema Version	Oracle Database Data Definition	Values
   decimal	1.0	NUMBER(13,4)	Weight is the scale weight of the production or discard item. It will be between 0 and 999,999,999.9999

9. Count
   The count element is the number of animals accounted for on that line item. For discard lines on groundfish reports count will always be present if weight is omitted.
10. Effort
    The effort element is 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.
11. Disposition_code
    The disposition_code element will 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 are available on the web application.
12. Agency_line_data
    The agency_line_data element will be omitted from reports that are made visible to processors and third party systems.
13. Product_item
    The product_item element may be present for line items that have 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 will be present. In that case, if the disposition of the line item is not a sold disposition then the product_item will not have a price.
    1. Item_number
       The item_number element is 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 will 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. 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

    4. Size_grade
       The size_grade element will not always be present. This is an optional field that allows processors to list sizing and grading information on the 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 will 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 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 places. In some cases the price will be zero.
14. Line_Item_stat_area
    The line_item_stat_area element will not be present

    Data Type	Since Schema Version	Oracle Database Data Definition	Values
    decimal	1.0	NUMBER(13,4)	Count is the number of fish or animals documented by the discard item. It will be between 1 and 100,000,000.

15. Line_Item_stat_area
    The line_item_stat_area element is used internally by eLandings, and will not be present in exported production reports.

Coded_comment

The coded_comment element is used for agency purposes. It will not appear in reports exported from eLandings, and should not be specified for reports that are to be imported to eLandings.

Mra_trip

The mra_trip element contains summary data on species and weights on production reports for the same vessel. The summary data is useful for determining when maximum retainable amount limits have been reached. This element will only be present on at-sea reports exported from eLandings. It should not be specified for import files.

1. Mra_trip
   The mra_trip element contains the summaries for the current trip. The mra_trip element has 4 attributes.
   • start_date - the start date of the trip.
   • end_date - the end date of the trip.
   • trip_event_code - the code indicating the event that caused the start of a new trip.
   • trip_event_desc - the description of the event that caused the start of a new trip.
   1. Mra_species
      The mra_species element specifies the species. An mra_trip element may have many mra_species.
      The mra_species element has 6 attributes
      • species_code - the numeric species code, as was entered in the production items.
      • species_name - the species name
      • product_code - the numeric product code, as was entered in the production items
      • product_name - the product code description
      • total_weight - the total of the weights as entered, for the trip, for the species
      • total_round_weight - the total weight converted to round weight.
      1. Mra_prod_report
         The mra_prod_report element summaries the individual production reports for the trip. An mra_species may have many mra_prod_reports.
         The mra_prod_report element has 7 attributes.
         • report_id - the production report id
         • report_date - the report date of the production report
         • round_weight - the round weight of the species for the production report
         • trip_event_code - the trip event code reported on the production report. If no trip event was reported this attribute will be omitted.
         • trip_event_desc - the trip event description for the trip event reported on the production report. If no trip event was reported this attribute will be omitted.
         • management_program - the management program reported on the production report.
         • management_program_id - the management program participant id reported on the production report, if one was reported.
         1. Weight
            The weight element contains the total weight of the species for the production report documented by the mra_prod_report.