eLandings User Manual
Report Extract Spreadsheet Columns
- Chris Keller
The following tables show the pre-defined columns that can be present in the report extracts downloaded as MS Excel or CSV files. Additional columns can be created and populated using formulas. These addition columns must be created in a template Excel file and uploaded using the template upload feature. The formula value for a column must be set in all rows of the spreadsheet where the formula is desired. The eLandings Report Extract fills in rows in the uploaded template file, ignoring columns with labels other than those defined in the table below. Any value in a column with one of the pre-defined column names will be overwritten.
Landing Report
Column Label |
Data Type |
Oracle Database Data Definition |
Values |
|
|---|---|---|---|---|
landing_report_id |
integer |
NUMBER(10,0) |
Landing report IDs will be between 1 and 9,999,999,999 |
|
type_of_landing_report |
text |
CHAR(1) |
Valid Types of landing reports are: |
|
type_of_landing_report.name |
text |
VARCHAR2(50) |
The names of landing report types are as above. |
|
status |
integer |
NUMBER(10,0) |
Status values are: |
|
status.name |
text |
VARCHAR2(25) |
The names of status types are as above. |
|
date_fishing_ended |
date |
DATE |
 |
|
vessel |
integer |
NUMBER(5,0) |
Vessel is the ADF&G Number of the vessel. Vessel ADF&G numbers can be looked up on the CFEC website |
|
vessel.name |
text |
VARCHAR2(50) |
Vessel names can be looked up on the CFEC website, as above. |
|
crew_size |
integer |
NUMBER(3,0) |
Crew size is the size of the crew including the skipper. Rules for crew size are documented by the eLandings business rules |
|
observers_onboard |
integer |
NUMBER(2,0) |
Observers onboard is the number of observers. Rules for observers onboard are documented by the eLandings business rules |
|
port_of_landing |
text |
CHAR(3) |
Port of landing is the eLandings port code. Valid values can be looked up on the eLandings website |
|
port_of_landing.name |
text |
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. |
|
port_of_landing.ifq_port_code |
integer |
NUMBER(3,0) |
IFQ port code is the numeric code used on the IFQ system. It is associated with the eLandings port code, and can be looked up on the eLandings website. The IFQ port code appears on IFQ receipts. |
|
delivery_port_region |
text |
VARCHAR2(3) |
The Delivery Port Region is the IFQ system port or region code used on some IFQ landings. Valid values can be looked up on the eLandings website |
|
gear |
integer |
NUMBER(3,0) |
Gear is the eLandings gear code. Valid values can be looked up on the eLandings website |
|
gear.name |
text |
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. |
|
proc_code_owner |
text |
VARCHAR2(6) |
Proc code owner is the processor code of the processor who is buying the catch. |
|
proc_code_owner.processor |
text |
VARCHAR2(50) |
Proc code owner processor is the name of the processor who is buying the catch. |
|
proc_code_processor |
text |
VARCHAR2(6) |
Proc code processor is the processor code of the processor who is receiving and the catch, in cases of custom processing. |
|
proc_code_processor.processor |
text |
VARCHAR2(50) |
Proc code processor processor is the name of the processor who is receiving and the catch, in cases of custom processing. |
|
date_fishing_began |
date |
DATE |
Date fishing began is the date that the gear first went in the water. |
|
days_fished |
integer |
NUMBER(3,0) |
Days fished is the number of days between the date fishing began and the date of landing when gear was in the water and fishing was taking place. The business rules for days fished are on the eLandings website |
|
date_of_landing |
dateTime |
DATE |
Date of landing is the date upon which the offload from the catcher vessel was completed. |
|
partial_delivery |
boolean |
CHAR(1) |
Partial Delivery indicates whether or not the delivery was for all fish caught on the trip. Value will be TRUE or FALSE. |
|
last_delivery_for_trip |
boolean |
CHAR(1) |
Last Delivery For Trip indicates whether or not the vessel completed offloading all fish onboard with the current delivery. Value will be TRUE or FALSE. |
|
multiple_ifq_permits |
boolean |
CHAR(1) |
Multiple IFQ Permits indicates whether or not the skipper and crew had more than one IFQ permit under which they did the fishing. Value will be TRUE or FALSE. |
|
manual_ifq_report |
boolean |
CHAR(1) |
Manual IFQ Report indicates whether or not an IFQ report for the landing was made manually by phone to the NMFS Data Technicians. Value will be TRUE or FALSE. |
|
nearest_bay_or_headland |
text |
VARCHAR2(50) |
The nearest bay or headland is a text description of the geographic location where the fishing took place. The business rules for nearest bay or headland are on the eLandings website |
|
federal_processor_number |
integer |
NUMBER(6,0) |
Federal Processor Number is the Federal Processing Permit or Federal Fisheries Permit of the receiving processor. |
|
registered_buyer_number |
integer |
NUMBER(6,0) |
Registered Buyer Number is the groundfish IFQ registered buyer number of the receiving processor. |
|
registered_crab_receiver_number |
integer |
NUMBER(6,0) |
Registered Crab Receiver Number is the crab IFQ registered receiver number of the receiving processor. |
|
discard_report |
text |
CHAR(2) |
Discard Report indicates the whether discard report blue sheets were received by the processor, or the reason they were not received. Values are: |
|
discard_report.desc |
text |
VARCHAR2(50) |
The description associated with the discard report code, values as above. |
|
tender_vessel |
integer |
NUMBER(5,0) |
Tender Vessel is the ADF&G Number of the tender. Vessel ADF&G numbers can be looked up on the CFEC website |
|
tender_vessel.name |
text |
VARCHAR2(50) |
The name of the tender. Names can be looked up on the CFEC website, as above. |
|
chill_type |
text |
VARCHAR2(3) |
The fish hold chilling system type. Valid chill types are documented on the eLandings website |
|
chill_type.desc |
text |
VARCHAR2(60) |
The description of the chilling system type identified by the chill type. |
|
rsw_temp |
decimal |
NUMBER(3,1) |
The temperature of the fish, as maintained by the chilling system, whether Refrigerated SeaWater or another type. Business rules for the temperature are on the eLandings website |
|
dock_delivery |
boolean |
CHAR(1) |
Dock Delivery indicates whether or not delivery was made to a tender vessel tied up at the processing plant dock. Value will be TRUE or FALSE. |
|
buying_station_name |
text |
VARCHAR2(60) |
The operation name of a buying station operation. It can be up to 60 characters long. |
|
cfec_permit.fishery |
text |
VARCHAR2(6) |
The CFEC permit fishery for the permit. CFEC permits can be looked up on the CFEC website |
|
cfec_permit.permit |
text |
CHAR(6) |
The permit number portion of the CFEC permit, including check character, for a total length of 6 characters. |
|
cfec_permit.year_seq |
text |
CHAR(5) |
The two digit year and the two digit sequence within the year of the permit card. The year sequence includes a check character, for a total length of 5 characters. |
|
cfec_permit.holder |
text |
VARCHAR2(60) |
The name of the permit holder, which can be up to 60 characters long |
|
cfec_permit.serial_number |
integer |
NUMBER(9,0) |
The CFEC file number, or serial number, that uniquely identifies the permit holder. |
|
mag_stripe_read |
boolean |
CHAR(1) |
Mag Stripe Read indicates whether or not the CFEC card was read by a magnetic stripe reader. Value will be TRUE or FALSE. |
|
management_program |
text |
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 |
|
management_program_id |
integer |
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 |
|
dual_permit |
boolean |
CHAR(1) |
Dual permit indicates whether two or more permit holders were aboard the catcher vessel, allowing additional gear to be deployed. Value will be TRUE or FALSE. |
|
tender_batch |
text |
VARCHAR2(10) |
A processor assigned tender batch number. It can be up to ten characters in length. |
|
floating |
boolean |
CHAR(1) |
Floating indicates whether or not salmon were floating in a tank when unloaded to a tender. Value will be TRUE or FALSE. |
|
slide |
boolean |
CHAR(1) |
Slide indicates whether or not salmon were unloaded to a tender using a slide. Value will be TRUE or FALSE. |
|
round_weight |
decimal |
NUMBER(13,4) |
Round weight is the weight for the catch, converted to round, or green weight according to the condition code. Values will be between 0 and 999,999,999.9999 |
|
fish_ticket_number |
text |
CHAR(10) |
Fish Ticket Number is the ticket number that associates particular catch lines with particular permits on the landing report. The business rules for the fish ticket number format are on the eLandings website |
. |
stat_area |
integer |
NUMBER(6,0) |
Stat area is the statistical area where the catch took place. Valid values can be looked up on the eLandings website |
|
species |
integer |
NUMBER(3,0) |
Species is the numeric species code. Valid values can be looked up on the eLandings website |
|
species.name |
text |
VARCHAR2(60) |
Species name is the name associated with the species code. Values can be looked up on the eLandings website, as above |
|
condition_code |
integer |
NUMBER(3,0) |
Condition code is the condition of the fish regarding any processing that has already taken place. Valid values can be looked up on the eLandings website |
|
condition_code.name |
text |
VARCHAR2(60) |
Condition code name is the description associated with the condition code. Values can be looked up on the eLandings website, as above. |
|
weight |
decimal |
NUMBER(13,4) |
Weight is the scale weight of the catch item. It will be between 0 and 999,999,999.9999 |
|
weight_modifier |
text |
VARCHAR2(10) |
The weight modifier indicates considerations that apply to the weight of the catch item. Valid values are: |
|
count |
decimal |
NUMBER(13,4) |
Count is the number of fish or animals documented by the catch item. It will be between 1 and 100,000,000. |
|
effort |
decimal |
NUMBER(5,0) |
Effort is the effort, in units appropriate to the gear, that produced the catch item. Values will be between 1 and 10,000. |
|
disposition_code |
integer |
NUMBER(3,0) |
Disposition code is the numeric code indicating the disposition of the catch item. Valid values can be looked up on the eLandings website |
|
disposition_code.name |
text |
VARCHAR2(60) |
Disposition Code Name is the description associated with the disposition code. Values can be looked up on the eLandings website, as above. |
|
sold_round_weight |
decimal |
NUMBER(13,4) |
The sold round weight is the sold weight for the product code, converted to round, or green weight. Values will be between 0 and 999,999,999.9999 |
|
product_code |
integer |
NUMBER(3,0) |
Product code is the condition code of the sold product. Valid values can be looked up on the eLandings website |
|
product_code.name |
text |
VARCHAR2(60) |
The product code name is the description associated with the product code. Values can be looked up on the eLandings website, as above. |
|
product_type |
text |
CHAR(1) |
Product type identifies whether the item is the main product produced from the fish, or is additional product. Valid values are: |
|
size_grade |
text |
VARCHAR2(16) |
The size and grade is the processor's short description of the size and or grading. It can be up to 16 characters long. |
|
sold_weight |
decimal |
NUMBER(13,4) |
The sold weight will be between 0 and 999,999,999.9999 |
|
price |
decimal |
NUMBER(6,4) |
Price is the price per pound, and will between -100.00 and 100.00. Negative prices are allowed for some situations where processors charge fees for handling of certain items. |
Production Report
Column Label |
Data Type |
Oracle Database Data Definition |
Values |
|---|---|---|---|
production_report_id |
integer |
NUMBER(10,0) |
Production report IDs will be between 1 and 9,999,999,999 |
status |
integer |
NUMBER(10,0) |
Status values are: |
status.name |
text |
VARCHAR2(25) |
The names of status types are as above. |
type_of_production_report |
text |
CHAR(1) |
Valid Types of production reports are: |
report_date |
date |
DATE |
Date of the report, referring to the date when the production took place. |
no_deliveries |
boolean |
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. |
no_production |
boolean |
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. |
vessel |
integer |
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. |
vessel.name |
text |
VARCHAR2(50) |
Vessel names can be looked up on the CFEC website, as above. |
gear |
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. |
gear.name |
text |
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. |
crew_size |
integer |
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 |
port_of_landing |
text |
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 |
port_of_landing.name |
text |
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. |
observers |
integer |
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 |
federal_processor_number |
integer |
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. |
federal_processor_number.name |
text |
VARCHAR2(50) |
Federal Processor Number Name is the name of the processor. |
proc_code |
text |
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. |
proc_code_owner.processor |
text |
VARCHAR2(50) |
Proc code processor is the name of the processor. |
fed_area |
integer |
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 |
special_area |
text |
VARCHAR2(5) |
Valid special areas are: |
special_area.desc |
text |
N/A |
The names of special areas, as above. |
management_program |
text |
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 |
management_program_id |
integer |
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 |
trip_event_code |
integer |
NUMBER(2,0) |
Trip event code values are: |
trip_event_code.name |
text |
VARCHAR2(60) |
The names of trip events, as above. |
item_type |
text |
N/A |
Item type identifies whether the item is a production item, or for At-Sea production reports a discard item. Valid values are: |
round_weight |
decimal |
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 |
fmp_area |
integer |
VARCHAR2(5) |
Federal Management Plan area. FMP Area only applies to Shoreside production reports. Values are: |
fmp_area.description |
text |
VARCHAR2(50) |
The names of FMP areas, as above. |
species |
integer |
NUMBER(3,0) |
Species is the numeric species code. Valid values can be looked up on the eLandings website |
species.name |
text |
VARCHAR2(60) |
Species name is the name associated with the species code. Values can be looked up on the eLandings website, as above |
product_type |
text |
CHAR(1) |
Product type identifies whether the item is the main product produced from the fish, or is additional product. Valid values are: |
product_code |
integer |
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 |
product_code.name |
text |
VARCHAR2(60) |
Product code name is the description associated with the product code. Values can be looked up on the eLandings website, as above. |
weight |
decimal |
NUMBER(13,4) |
Weight is the scale weight of the production or discard item. It will be between 0 and 999,999,999.9999 |
weight.units |
text |
VARCHAR2(2) |
Weight Units is the unit of measure for the weight. It is not used on At-Sea or Shoreside production reports, and is always assumed to be metric tons. |
disposition_code |
integer |
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 |
disposition_code.name |
text |
VARCHAR2(60) |
Disposition Code Name is the description associated with the disposition code. Values can be looked up on the |
count |
decimal |
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. |