Final View in eDealer Schema
Entity (ENT) | NMFS Office Of Sustainable Fisheries (OSF)GUID: gov.noaa.nmfs.inport:75306 | Updated: March 28, 2025 | Published / External
-
View As
- Full List View
- Printable Form
- EXPORTS
- InPort XML
- View in Hierarchy
Summary
The Final View combines electronically submitted dealer data from Maine through Texas, including the U.S. Caribbean, that contains non-bluefin tuna HMS dealer data (sharks, swordfish, and bigeye, albacore, yellowfin, and skipjack tunas) into a single view. The view is comprised of the union of multiple data tables from the edealer database, but each row indicates a transaction of either sharks, swordfish, and bigeye, albacore, yellowfin, and skipjack tunas that were electronically submitted by a dealer. It also contains records that were manually created and uploaded by the Atlantic HMS Management Division Staff. These records represent transactions that were identified in other FIN databases (ACCSP and GulfFIN data warehouses) and the SEFSC Caribbean data database. Data generated from our automated Trip Identification Tool and Logbook Reconciliation tool are also saved in the Final View.
DescriptionThis is a final view in the edealer schema on a server housed at ACCSP. It contains the HMS-only (non-bluefin tuna) dealer records submitted electronically from 12 different electronic reporting programs from Maine to Texas, including the U.S. Caribbean. It also contains data variables that are populated from the Trip Identification Tool and the Logbook Reconciliation Tool that are housed within the edealer application
Entity Information
Entity Type
Data View
Data Attribute / Type | Description |
---|---|
YEAR_OF_LANDING
NUMBER |
Year the product was landed and taken from the DATE_LANDED field. If this is not available, the year from DATE_PURCHASED is used. |
MONTH_OF_LANDING
NUMBER |
Month information taken from the DATE_LANDED field. If this is not available, the month from DATE_PURCHASED is used. |
SAFIS_DEALER_RPT_ID
NUMBER |
Unique report identifier coming from the SAFIS system |
DEALER_TICKET_NO
VARCHAR2(50) |
Unique report identifier coming from a Trip Ticket system |
EDEALER_RPT_NUM
VARCHAR2(20) |
Unique report identifier coming from the edealer reporting system (applied to all reports validated and pulled into the edealer production tables) |
REPORT_TYPE
VARCHAR2(30) |
Identifies where the record is pulled. Sources include eDealer production tables (EDLR-P), eDealer records in stuck tables that have been verified as accurate (EDLR-S), records that include "Unclassified" landings and have been reapportioned to a species (REAPP; this information is used for quota monitoring and stock assessments), GulfFIN data (GFIN), ACCSP data (ACCSP), Pelagic longline vessel logbooks from the SEFSC (PLLLB), Caribbean vessel logbook data from Puerto Rico (CAR-PR) and the USVI (CAR-USVI). this is similar to the SOURCE information but more specific. |
TABLE_TYPE
VARCHAR2(30) |
Indicates whether the data came directly from eDealer (via a "VALIDATED" or "STUCK" record) or a record was taken from an outside source and record was entered in manually into the VIEW ("MANUAL"). |
SOURCE
VARCHAR2(50) |
Description of where the report came from: Caribbean report, dealer report, vessel report, PLLLB. This is similar to the information displayed in REPORT_TYPE, but is categorical information. |
CORPORATE_NAME
VARCHAR2(50) |
Corporate name of dealer, if applicable |
SAFIS_DEALER_ID
NUMBER |
The SAFIS participant ID |
NE_PERMIT
VARCHAR2(50) |
The federal dealer permit number issued from GARFO |
SE_PERMIT
VARCHAR2(50) |
The federal dealer permit number issued from SERO |
SOURCE_SYSTEM
VARCHAR2(20) |
Identifiers denoting what data system HMS records were pulled from. These currently are: ACCSP-Cmpr (ACCSP data warehouse comparison), PWR-SEFSC Weigh out (weigh out data comparison), MFIN - P (paper form from GulfFIN), ACCSP (electronic record from ACCSP), SAFIS (electronic record from SAFIS), NCSCBI (electronic record from North Carolina state program), CCL-SEFSC Carib (Caribbean landings from SEFSC), GULFIN (electronic record from GulfFIN) |
SAFIS_PERMIT_ID
NUMBER |
A foreign key from the SAFIS PERMITS table. Identifies the permit under which a Dealer/participant is reporting. |
DEALER_STATE
VARCHAR2(20) |
This is the state listed in the permit file for the dealer's business address. In some cases, it is more accurate to describe it as the State the dealer conducts business in. |
RECEIVED_FILENAME
VARCHAR2(45) |
This is the filename associated with a group of reports submitted by a dealer using a Trip Ticket or Florida VESL reporting program. This serve as a confirmation number that a dealer submitted a report to the federal agency. The contains a time/date stamp that corresponds to the date of submission. |
DATE_PURCHASED
DATE |
Date fish product purchased; the date the dealer took possession of the product |
DATE_LANDED
DATE |
Date fish product landed (when the boat comes to the dock). This date is used for quota monitoring. |
RECONCILED_DATE_LANDED
DATE |
This is the landing date taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool |
LOCATION_CODE
VARCHAR2(6) |
This is a code that indicates the port of landing in the STAG_HMS_DEALER_REPORTS; It is from the PORT code in the VALID_PORTS table and becomes the PORT code in the DEALER_REPORTS table |
PORT_NAME
VARCHAR2(60) |
Name of port where fishing vessel landed and offloaded the product |
PORT_STATE_CODE
VARCHAR2(2) |
The 2-number code used by the FINS (GulfFIN and ACCSP) to indicate the state of the port of landing. |
PORT_STATE
VARCHAR2(2) |
State of the port where the fishing vessel landed and offloaded the product |
RECONCILED_PORT_STATE
VARCHAR2(2) |
This is the port state taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool |
FUS_STATE
VARCHAR2(30) |
State of the port where the fishing vessel landed and offloaded the product according to the Fisheries of the US (FUS). This is the same as the PORT_STATE except: 1) the state of Florida is split into "Florida-East" (FE) and "Florida-West" (FW); and 2) the nomenclature for Caribbean states is slightly different, per S&T request. |
SUPPLIER_VESSEL_ID
VARCHAR2(50) |
USCG documentation number or state registration number of the vessel dealer purchased product from as reported by the dealer |
RECONCILED_VESSEL_ID
VARCHAR2(30) |
This is the vessel registration (USCG # or state registration number) taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool |
VESSEL_ID
NUMBER |
Internal identifier assigned by the SAFIS program and pulled into edealer |
VESSEL_FED_PERMIT_NUMBER
VARCHAR2(127) |
Federal fishing permit number; string concatenated with a comma |
VESSEL_PERMIT_CATEGORY
VARCHAR2(30) |
Swordfish fishing vessel permit category (Directed or Incidental) |
TRIP_ID
VARCHAR2(4000) |
VTR or logbook number of the fishing trip that the dealer purchased fish from |
RECONCILED_TRIP_ID
VARCHAR2(50) |
This is the VTR # taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool |
REASON_NO_FV_LOGBOOK_ID
NUMBER |
Dealer submits the reason a logbook was not submitted by a vessel; this is a number that corresponds to a standardized list of reasons of why a logbook # was not supplied by a dealer; this field is from DEALER_REPORTS table |
EXPLANATION_NO_LOGBOOK
VARCHAR2(150) |
Description of why a dealer did not submit a VTR # on a dealer report; corresponds to the number on the standardized list of reasons why no VTR # was supplied by the dealer; this field is from DEALER_REPORTS table |
WHY_NO_VTR
VARCHAR2(150) |
Name of the field in the STAG_HMS_DEALER_REPORTS table that hold the explanation of why no VTR # was provided by the dealer. |
OBSERVER_LOG_ID
VARCHAR2(25) |
The dealer indicates the logbook identifier from the observer logbook; the presence of this value is used to identify shark research trips |
GEAR_CODE
VARCHAR2(3) |
ACCSP standard code associated with gear submitted on the report by the dealer |
RECONCILED_GEAR_TYPE
VARCHAR2(3) |
This is the gear type taken from the vessel logbook record; this field is populated after a reconcilation event occurs in the Logbook Reconciliation tool |
GEAR_NAME
VARCHAR2(50) |
This information should match the GEAR_NAME column as they exist in the Gear tables at the FINS and as they exist in FIN Standard codes. |
LATE_REPORT_EXPLANATION
VARCHAR2(150) |
Explanation provided by the dealer describing why a report was late |
MODIFIED_DATE_EXPLANATION
VARCHAR2(150) |
Entered by the dealer to explain changes on a report and/or if a transaction is not a duplicate entry (if there are mutliple entries that are the same within a report) |
RECORD_PROCESSED_YN
VARCHAR2(1) |
A "Y" indicates that the record was processed by edealer and put in the production DEALER_REPORTS and LANDINGS tables; a "N" indicates that the record has not been processed; this is taken from the STAG_HMS_DEALER_REPORTS table |
RECORD_DISCARDED_YN
VARCHAR2(1) |
A "Y" indicates that the reocrd was discarded; and "N" indicates that the record has not been discarded; this is taken from the STAG_HMS_DEALER_REPORTS table |
ERROR_EXISTS_YN
VARCHAR2(1) |
Indicates if an error existed in the dealer report. Y (Yes) or N (No) values |
ERROR_MESSAGE
VARCHAR2(1000) |
The message describes the error associated with the dealer report. |
SUBMIT_METHOD
VARCHAR2(1) |
Indicates how a dealer reported was entered and submitted to the federal agencies |
DR_DELETED
VARCHAR2(1) |
"Y" indicates the dealer deleted the record; a NULL value indicates that the dealer has not deleted the record |
PROCESS_ID
NUMBER |
Internal value assigned by the edealer program during a nightly data sycnchronization event with ACCSP; each unique value identifies a separate data synchronization event |
ACTION_FLAG
VARCHAR2(1) |
"A" value indicates that the record is an "add" or initial submission; "U" value indicates that the record has been updated and the update is being shown |
DATE_ENTERED
DATE |
Date report entered into original reporting program |
DATE_SUBMITTED
DATE |
This indicates the date when a dealer submitted a report to federal and state agencies. This date should exist for reports submitted through a reporting program. This information does not exist with manually entered records (e.g., Caribbean data, vessel logbook data). |
UTC_SUBMIT_DATE
DATE |
This indicates the dealer submitted a report. It is in Coordinated Universal Time report submission date/time. Used for reports from Trip Ticket programs |
UTC_UPDATE_DATE
DATE |
This indicates the dealer submitted an updated report. Coordinated Universal Time report update submission date/time. Used for reports from Trip Ticket programs |
UTC_DATE_SUBMITTED_FLAG
VARCHAR2(5) |
Indicates if a report submitted through a Trip Ticket program has a submission date/time stamp from the internet (âÂÂUTCâÂÂ) or from the local computer (âÂÂLOCALâÂÂ). |
UTC_DATE_UPDATED_FLAG
VARCHAR2(5) |
Indicates the updated submission date/time stamp of an updated file. Submission time/date stamp from the internet (âÂÂUTCâÂÂ) or from the local computer (âÂÂLOCALâÂÂ). |
DATE_UPDATED
DATE |
This indicates the date when a dealer updated a report and sent it to the federal and state agencies. This date should exist for reports submitted through a reporting program. This information does not exist with manually entered records (e.g., Caribbean data, vessel logbook data). |
UPDATED_BY
VARCHAR2(40) |
Text identifier of user who updated the record. |
LAST_UPDATED
DATE |
Date dealer report record was last updated. |
LAST_UPDATED_BY
VARCHAR2(100) |
Free text identifying who updated a record. |
DATE_LOADED_IN_EDEALER
DATE |
Date report loaded into eDealer STAG_HMS_DEALER_REPORTS table. |
DATE_LOADED_FINAL_TABLE
DATE |
This is the date the HMS records were submitted to be loaded into this final view. |
DATE_UPDATED_FINAL_TABLE
DATE |
This is the date a HMS record was resubmitted/reloaded in this final view. |
STAG_HMS_DEALER_RPT_ID
NUMBER |
A Primary Key for a STAG_HMS_DEALER_REPORTS record. An auto-generated number. |
HMS_DEALER_RPT_ID
NUMBER |
This is a primary key that ACCSP assigns to the data. It links the stag_hms_dealer_reports and stag_jms_landings tables. |
DEALER_RPT_ID
NUMBER(9) |
Primary Key for DEALER_REPORT records. An auto-generated number. |
STAG_HMS_LANDING_ID
NUMBER |
Foreign key to link between STAG_HMS_LANDINGS and LANDINGS table; do not need to enter this unless we want a certain version of a record to be in View |
LANDING_SEQ
VARCHAR2(40) |
Unique identifier for individual landings in the STAG_HMS_LANDINGS table; foreign key to link additional fields manually loaded with records in the STAG_HMS_LANDINGS table; this value stays the same through time |
LANDING_ID
NUMBER |
Unique identifier for individual landings in the LANIDNGS table; this value will change with each submission of a report |
LANDING_RECORD_PROCESSED_YN
VARCHAR2(1) |
Yes/No flag field indicating whether a landing record was processed. Taken from the STAG_HMS_LANDINGS table |
LANDING_RECORD_DISCARDED_YN
VARCHAR2(1) |
Yes/No flag field indicating whether a landing record was discarded. Taken from the STAG_HMS_LANDINGS table |
LANDING_ERROR_EXISTS_YN
VARCHAR2(1) |
Yes/No flag field indicating whether a landing record had data validation errors. Taken from the STAG_HMS_LANDINGS table |
LANDING_ERROR_MESSAGE
VARCHAR2(1000) |
Text field describing the issues causing a landing record to fail validation. Taken from the STAG_HMS_LANDINGS table |
LANDING_DELETED
VARCHAR2(1) |
A Yes/No flag denoting if a landing record was deleted. Taken from the STAG_HMS_LANDINGS table |
ACTIVE
VARCHAR2(1) |
Yes/No flag indicating if landing record is active |
CLASSIFICATION
VARCHAR2(30) |
Free text providing a general classification of an HMS species (BAYS TUNA, SHARK, SWORDFISH and UNCLASSIFIED SHARK) |
SPECIES_ID
NUMBER |
A Primary Key for a SPECIES record. An auto-generated number. |
SPECIES_ITIS
VARCHAR2(11) |
ITIS code used by itis.gov to indicate species. NOTE: '159786' ("SHARKS, SMALL COASTAL") may be used to report "Shark Belly Flaps"; 159851â ("SHARKS, PELAGIC, UNC") may represent "SHARK FINS" |
COMMON_NAME_AS_REPORTED
VARCHAR2(100) |
Free text describing a common name for an organism. |
COMMON_NAME_ADJUSTED
VARCHAR2(100) |
This is the Common_Name used in the Caribbean vessel logbook data (CAR-PR and CAR-USVI) |
REAPPORTIONED_YN
VARCHAR2(1) |
"Y" indicates that the record was either a report of unclassified HMS-product which was apportioned to species-specific weights, or is a report to species originating from a report of unclassified HMS-product, which was determined by proportions of historical landings |
REAPPORTIONED_KEY
VARCHAR2(63) |
This is a Key that would tie together original records that included "Unclassified" reported species with records added manually that reapportioned these unclassifieds to species-specific landings. The Key would be the same for all records in that group (e.g., 100 lb unclassified shark may break down to 4 different species and all records would have the same REAPP_KEY). Reapportioned records with species-specific information may or may not include landing and purchase dates, month, gear, disposition, market, vessel, port, or dealer information. Originally submitted records and reapportioned records will be differentiated via the "SAME_AS_WAREHOUSE" column, where "N" indicates a reapportioned record. |
REAPPORTIONED_DESC
VARCHAR2(255) |
Percentages applied to unclassified HMS products to determine weights of species. |
UNIT_MEASURE
VARCHAR2(2) |
This field has a code noting the units the REPORTED_QUANTITY is reported in. |
REPORTED_QUANTITY
NUMBER |
Weight of purchased fish. |
DISPOSITION_CODE
VARCHAR2(3) |
A SAFIS code describing how a fish was used after purchase. |
DISPOSITION_DESC
VARCHAR2(50) |
A free text description of the disposition code. |
MULTIPLE_DEALER_GROUP_YN
VARCHAR2(1) |
A "Y" in this field would indicate transactions from more than one dealer exist or are expected. The default for this field should be "N". |
TRIP_KEY
NUMBER |
This is a Key that ties together all records from a single vessel trip. The Trip Key is the same for all records in that group. This is an internal, automated value created by the Trip Identification Tool |
USED_FOR_QM_REPORT_YN
VARCHAR2(1) |
A "Y" in this field would indicate records that should be included for QM updates. A "N" in this field would indicate the record should be excluded for QM updates. |
INCLUDE_FOR_FUS_LANDINGS_YN
VARCHAR2(1) |
A "Y" in this field would indicate records that should be included for tallying FUS landings. An "N" in this field would indicate records that should be EXcluded for FUS total landings. |
USED_FOR_FUS_REPORT_YN
VARCHAR2(1) |
A "Y" in this field would indicate records that should be included in the FUS report. It is possible that a record may be included for FUS landings but not for FUS economics (FUS_ECONOMICS_1_0). Including all records with a "Y" in this field would provide the entire set of records needed to recreate that report, regardless of being excluded from FUS landings or FUS economics. An "N" in this field would indicate records which should be excluded for the FUS report. |
GRADE_CODE
VARCHAR2(1000) |
ACCSP standard code used to describe the grade of the fish, or how the fish was cut up upon weighing |
GRADE_DESCRIPTION
VARCHAR2(50) |
Free text description of the ACCSP gear code value |
CONVERTED_DW_LBS
NUMBER(15,2) |
This is the reported weight converted to dressed/gutted weight |
CONVERTED_WW_LBS
NUMBER(15,2) |
This is the reported weight converted to whole weight |
TO_WW_MULTIPLIER
NUMBER(15,2) |
This is the conversion factor used to calculate whole weight |
TO_DW_DIVIDER
NUMBER(15,2) |
This is the conversion factor used to calculate dressed/gutted weight |
MARKET_CODE
VARCHAR2(1000) |
A code describing the quality of product. |
PURCHASE_PRICE
NUMBER |
Price the dealer paid a fisher per pound of fish product. |
INCLUDE_FOR_FUS_ECONOMICS_YN
VARCHAR2(1) |
A "Y" in this field would indicate records that should be included for determining economic data for the FUS report. A "N" in this field indicates that this record should be Excluded from economic analyses for FUS. |
TOTAL_DOLLARS
NUMBER |
Total Purchase Price of fish product |
SALE_PRICE
NUMBER |
Total sales price for fish if no initial purchase occurred. |
HMS_CATCH_AREA
VARCHAR2(50) |
HMS Catch Area Code; Indicates where fish were caught in the ocean |
AREA_FISHED
VARCHAR2(3) |
Federal Fishing Area Code. |
SUB_AREA_FISHED
VARCHAR2(5) |
Federal Fishing Sub-Area Code. |
LOCAL_AREA_CODE
VARCHAR2(6) |
This is a sub-area code that is most commonly used in the Northeast to identify shellfish beds |
COUNCIL_REGION_AREA
VARCHAR2(50) |
This is the region where the fish was landed as defined by the Councils and as indicated in FIN data. Council areas and HMS regions are different (GOM vs SAT around the tip of Florida and for defining the Atlantic regions). Including this as defined in the FINS would be helpful to easily identify errors in comparison. Council region areas are defined by AREA_FISHED and SUB_AREA_FISHED. |
QUOTA_GROUP
VARCHAR2(50) |
Quota group as defined for HMS quota management |
HMS_REGION
VARCHAR2(50) |
Region as defined for HMS quota management |
SUB_REGION
VARCHAR2(50) |
Sub-region as defined for HMS quota management |
BASELINE_QUOTA_DW_MT
NUMBER |
This is the base quota assigned to an HMS quota group in dressed weight (DW) metric tons (MT) |
BASELINE_QUOTA_WW_MT
NUMBER |
This is the base quota assigned to an HMS quota group in whole weight (WW) metric tons (MT) |
ADJUSTED_QUOTA_DW_MT
NUMBER |
This is the adjusted quota assigned to an HMS quota group in dressed weight (DW) metric tons (MT) |
ADJUSTED_QUOTA_WW_MT
NUMBER |
This is the adjusted quota assigned to an HMS quota group in whole weight (WW) metric tons (MT) |
SEASON_START_DATE
DATE |
The date a particular quota management group was opened for a given season/year |
SEASON_END_DATE
DATE |
The date a particular quota management group was closed for a given season/year |
SUPPLIER_DR_ID_GFIN
VARCHAR2(50) |
Data included from manually entered GulfFIN data. Needed to identify dealer. |
GULFIN_LANDING_ID
NUMBER(38) |
Data included from manually entered GulfFIN data. Helpful to identify landing record in GulfFIN. |
FORM_VERSION
VARCHAR2(60) |
Data included from manually entered FIN data. Helpful to identify method landing report was submitted to FIN. |
DIFFER_FROM_WAREHOUSE_Y
VARCHAR2(1) |
A "Y" in this field indicates the record has been purposefully changed and will not match records already housed in the FIN data warehouses. A null field indicates that the record has not been verified as being the same or different. Changes may exist between eDealer data and master FIN data if a state has made alterations to the record. |
WAREHOUSE_CHANGE_TYPE
VARCHAR2(31) |
If a "Y" exists in DIFFER_FROM_WAREHOUSE_Y, then the type of difference is required: "NEW" means record does not exist in FIN warehouse; "Modified" means the record exists but was changed in the HMS Master View. If "DIFFER_FROM_WAREHOUSE" is null, then this field should be null. |
NOTES
VARCHAR2(500) |
Free form field to hold notes from administrators |
INTERNAL_REVIEW_COMMENTS
VARCHAR2(150) |
Free text describing any record review comments by HMS staff |
REVIEW_COMMENTS_UPDATED_BY
VARCHAR2(100) |
Free text identifying the HMS staffer making review comments |
REVIEW_COMMENTS_UPDATE_DATE
DATE |
Date review comments entered into dealer report record. |
LANDING_STATUS
VARCHAR2(1) |
To keep or exclude a record or landing based on value in the Trip Identification Tool |
ECONOMIC_STATUS
VARCHAR2(1) |
To keep or exclude a record's price information based on value in the Trip Identification Tool |
EX_VESSEL_VALUE
NUMBER(13,3) |
A calculated value of the price / lb at the first purchase multiplied by the total lbs landed |
NOTES_ECONOMIC
VARCHAR2(500) |
Free form field to hold notes from economist |
Child Items
No Child Items for this record.
Contact Information
Data Steward
Jacqueline Wilson Farber
jackie.wilson@noaa.gov
240-338-3936
Distributor
NMFS Office Of Sustainable Fisheries (OSF)
Item Identification
Title: | Final View in eDealer Schema |
---|---|
Short Name: | Final View |
Status: | Completed |
Creation Date: | 2025-03-19 |
Abstract: |
The Final View combines electronically submitted dealer data from Maine through Texas, including the U.S. Caribbean, that contains non-bluefin tuna HMS dealer data (sharks, swordfish, and bigeye, albacore, yellowfin, and skipjack tunas) into a single view. The view is comprised of the union of multiple data tables from the edealer database, but each row indicates a transaction of either sharks, swordfish, and bigeye, albacore, yellowfin, and skipjack tunas that were electronically submitted by a dealer. It also contains records that were manually created and uploaded by the Atlantic HMS Management Division Staff. These records represent transactions that were identified in other FIN databases (ACCSP and GulfFIN data warehouses) and the SEFSC Caribbean data database. Data generated from our automated Trip Identification Tool and Logbook Reconciliation tool are also saved in the Final View. |
Purpose: |
The view allows the consolidation of all commercial landings reported by dealers of sharks, swordfish, and bigeye, albacore, yellowfin, and skipjack tunas. These electronically submitted dealer reports are updated nightly. This also allows us to easily share information generated from our Logbook Reconciliation Tool. |
Notes: |
eDealer database is hosted at ACCSP; Schema: edealer; View: V_FINAL_TABLE |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
UNCONTROLLED | |
None | BAYS tunas |
None | commercial fishery landings |
None | dealer reports |
None | Edealer |
None | logbooks |
None | proxy records |
None | quota monitoring |
None | reconciliation |
None | sharks |
None | swordfish |
None | vessel reports |
Physical Location
Organization: | Atlantic Coastal Cooperative Statistics Program |
---|---|
City: | Arlington |
State/Province: | VA |
Country: | USA |
Entity Information
Entity Type: | Data View |
---|---|
Active Version?: | Yes |
Schema Name: | edealer |
Description: |
This is a final view in the edealer schema on a server housed at ACCSP. It contains the HMS-only (non-bluefin tuna) dealer records submitted electronically from 12 different electronic reporting programs from Maine to Texas, including the U.S. Caribbean. It also contains data variables that are populated from the Trip Identification Tool and the Logbook Reconciliation Tool that are housed within the edealer application |
Data Attributes
Attribute Summary
![]() |
![]() |
Name | Type | Description |
---|---|---|---|---|
100
|
YEAR_OF_LANDING | NUMBER | Year the product was landed and taken from the DATE_LANDED field. If this is not available, the year from DATE_PURCHASED is used. | |
100
|
MONTH_OF_LANDING | NUMBER | Month information taken from the DATE_LANDED field. If this is not available, the month from DATE_PURCHASED is used. | |
100
|
SAFIS_DEALER_RPT_ID | NUMBER | Unique report identifier coming from the SAFIS system | |
100
|
DEALER_TICKET_NO | VARCHAR2(50) | Unique report identifier coming from a Trip Ticket system | |
100
|
EDEALER_RPT_NUM | VARCHAR2(20) | Unique report identifier coming from the edealer reporting system (applied to all reports validated and pulled into the edealer production tables) | |
100
|
REPORT_TYPE | VARCHAR2(30) | Identifies where the record is pulled. Sources include eDealer production tables (EDLR-P), eDealer records in stuck tables that have been verified as accurate (EDLR-S), records that include "Unclassified" landings and have been reapportioned to a species (REAPP; this information is used for quota monitoring and stock assessments), GulfFIN data (GFIN), ACCSP data (ACCSP), Pelagic longline vessel logbooks from the SEFSC (PLLLB), Caribbean vessel logbook data from Puerto Rico (CAR-PR) and the USVI (CAR-USVI). this is similar to the SOURCE information but more specific. | |
100
|
TABLE_TYPE | VARCHAR2(30) | Indicates whether the data came directly from eDealer (via a "VALIDATED" or "STUCK" record) or a record was taken from an outside source and record was entered in manually into the VIEW ("MANUAL"). | |
100
|
SOURCE | VARCHAR2(50) | Description of where the report came from: Caribbean report, dealer report, vessel report, PLLLB. This is similar to the information displayed in REPORT_TYPE, but is categorical information. | |
100
|
CORPORATE_NAME | VARCHAR2(50) | Corporate name of dealer, if applicable | |
100
|
SAFIS_DEALER_ID | NUMBER | The SAFIS participant ID | |
100
|
NE_PERMIT | VARCHAR2(50) | The federal dealer permit number issued from GARFO | |
100
|
SE_PERMIT | VARCHAR2(50) | The federal dealer permit number issued from SERO | |
100
|
SOURCE_SYSTEM | VARCHAR2(20) | Identifiers denoting what data system HMS records were pulled from. These currently are: ACCSP-Cmpr (ACCSP data warehouse comparison), PWR-SEFSC Weigh out (weigh out data comparison), MFIN - P (paper form from GulfFIN), ACCSP (electronic record from ACCSP), SAFIS (electronic record from SAFIS), NCSCBI (electronic record from North Carolina state program), CCL-SEFSC Carib (Caribbean landings from SEFSC), GULFIN (electronic record from GulfFIN) | |
100
|
SAFIS_PERMIT_ID | NUMBER | A foreign key from the SAFIS PERMITS table. Identifies the permit under which a Dealer/participant is reporting. | |
100
|
DEALER_STATE | VARCHAR2(20) | This is the state listed in the permit file for the dealer's business address. In some cases, it is more accurate to describe it as the State the dealer conducts business in. | |
100
|
RECEIVED_FILENAME | VARCHAR2(45) | This is the filename associated with a group of reports submitted by a dealer using a Trip Ticket or Florida VESL reporting program. This serve as a confirmation number that a dealer submitted a report to the federal agency. The contains a time/date stamp that corresponds to the date of submission. | |
100
|
DATE_PURCHASED | DATE | Date fish product purchased; the date the dealer took possession of the product | |
100
|
DATE_LANDED | DATE | Date fish product landed (when the boat comes to the dock). This date is used for quota monitoring. | |
100
|
RECONCILED_DATE_LANDED | DATE | This is the landing date taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool | |
100
|
LOCATION_CODE | VARCHAR2(6) | This is a code that indicates the port of landing in the STAG_HMS_DEALER_REPORTS; It is from the PORT code in the VALID_PORTS table and becomes the PORT code in the DEALER_REPORTS table | |
100
|
PORT_NAME | VARCHAR2(60) | Name of port where fishing vessel landed and offloaded the product | |
100
|
PORT_STATE_CODE | VARCHAR2(2) | The 2-number code used by the FINS (GulfFIN and ACCSP) to indicate the state of the port of landing. | |
100
|
PORT_STATE | VARCHAR2(2) | State of the port where the fishing vessel landed and offloaded the product | |
100
|
RECONCILED_PORT_STATE | VARCHAR2(2) | This is the port state taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool | |
100
|
FUS_STATE | VARCHAR2(30) | State of the port where the fishing vessel landed and offloaded the product according to the Fisheries of the US (FUS). This is the same as the PORT_STATE except: 1) the state of Florida is split into "Florida-East" (FE) and "Florida-West" (FW); and 2) the nomenclature for Caribbean states is slightly different, per S&T request. | |
100
|
SUPPLIER_VESSEL_ID | VARCHAR2(50) | USCG documentation number or state registration number of the vessel dealer purchased product from as reported by the dealer | |
100
|
RECONCILED_VESSEL_ID | VARCHAR2(30) | This is the vessel registration (USCG # or state registration number) taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool | |
100
|
VESSEL_ID | NUMBER | Internal identifier assigned by the SAFIS program and pulled into edealer | |
100
|
VESSEL_FED_PERMIT_NUMBER | VARCHAR2(127) | Federal fishing permit number; string concatenated with a comma | |
100
|
VESSEL_PERMIT_CATEGORY | VARCHAR2(30) | Swordfish fishing vessel permit category (Directed or Incidental) | |
100
|
TRIP_ID | VARCHAR2(4000) | VTR or logbook number of the fishing trip that the dealer purchased fish from | |
100
|
RECONCILED_TRIP_ID | VARCHAR2(50) | This is the VTR # taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool | |
100
|
REASON_NO_FV_LOGBOOK_ID | NUMBER | Dealer submits the reason a logbook was not submitted by a vessel; this is a number that corresponds to a standardized list of reasons of why a logbook # was not supplied by a dealer; this field is from DEALER_REPORTS table | |
100
|
EXPLANATION_NO_LOGBOOK | VARCHAR2(150) | Description of why a dealer did not submit a VTR # on a dealer report; corresponds to the number on the standardized list of reasons why no VTR # was supplied by the dealer; this field is from DEALER_REPORTS table | |
100
|
WHY_NO_VTR | VARCHAR2(150) | Name of the field in the STAG_HMS_DEALER_REPORTS table that hold the explanation of why no VTR # was provided by the dealer. | |
100
|
OBSERVER_LOG_ID | VARCHAR2(25) | The dealer indicates the logbook identifier from the observer logbook; the presence of this value is used to identify shark research trips | |
100
|
GEAR_CODE | VARCHAR2(3) | ACCSP standard code associated with gear submitted on the report by the dealer | |
100
|
RECONCILED_GEAR_TYPE | VARCHAR2(3) | This is the gear type taken from the vessel logbook record; this field is populated after a reconcilation event occurs in the Logbook Reconciliation tool | |
100
|
GEAR_NAME | VARCHAR2(50) | This information should match the GEAR_NAME column as they exist in the Gear tables at the FINS and as they exist in FIN Standard codes. | |
100
|
LATE_REPORT_EXPLANATION | VARCHAR2(150) | Explanation provided by the dealer describing why a report was late | |
100
|
MODIFIED_DATE_EXPLANATION | VARCHAR2(150) | Entered by the dealer to explain changes on a report and/or if a transaction is not a duplicate entry (if there are mutliple entries that are the same within a report) | |
100
|
RECORD_PROCESSED_YN | VARCHAR2(1) | A "Y" indicates that the record was processed by edealer and put in the production DEALER_REPORTS and LANDINGS tables; a "N" indicates that the record has not been processed; this is taken from the STAG_HMS_DEALER_REPORTS table | |
100
|
RECORD_DISCARDED_YN | VARCHAR2(1) | A "Y" indicates that the reocrd was discarded; and "N" indicates that the record has not been discarded; this is taken from the STAG_HMS_DEALER_REPORTS table | |
100
|
ERROR_EXISTS_YN | VARCHAR2(1) | Indicates if an error existed in the dealer report. Y (Yes) or N (No) values | |
100
|
ERROR_MESSAGE | VARCHAR2(1000) | The message describes the error associated with the dealer report. | |
100
|
SUBMIT_METHOD | VARCHAR2(1) | Indicates how a dealer reported was entered and submitted to the federal agencies | |
100
|
DR_DELETED | VARCHAR2(1) | "Y" indicates the dealer deleted the record; a NULL value indicates that the dealer has not deleted the record | |
100
|
PROCESS_ID | NUMBER | Internal value assigned by the edealer program during a nightly data sycnchronization event with ACCSP; each unique value identifies a separate data synchronization event | |
100
|
ACTION_FLAG | VARCHAR2(1) | "A" value indicates that the record is an "add" or initial submission; "U" value indicates that the record has been updated and the update is being shown | |
100
|
DATE_ENTERED | DATE | Date report entered into original reporting program | |
100
|
DATE_SUBMITTED | DATE | This indicates the date when a dealer submitted a report to federal and state agencies. This date should exist for reports submitted through a reporting program. This information does not exist with manually entered records (e.g., Caribbean data, vessel logbook data). | |
100
|
UTC_SUBMIT_DATE | DATE | This indicates the dealer submitted a report. It is in Coordinated Universal Time report submission date/time. Used for reports from Trip Ticket programs | |
100
|
UTC_UPDATE_DATE | DATE | This indicates the dealer submitted an updated report. Coordinated Universal Time report update submission date/time. Used for reports from Trip Ticket programs | |
100
|
UTC_DATE_SUBMITTED_FLAG | VARCHAR2(5) | Indicates if a report submitted through a Trip Ticket program has a submission date/time stamp from the internet (âÂÂUTCâÂÂ) or from the local computer (âÂÂLOCALâÂÂ). | |
100
|
UTC_DATE_UPDATED_FLAG | VARCHAR2(5) | Indicates the updated submission date/time stamp of an updated file. Submission time/date stamp from the internet (âÂÂUTCâÂÂ) or from the local computer (âÂÂLOCALâÂÂ). | |
100
|
DATE_UPDATED | DATE | This indicates the date when a dealer updated a report and sent it to the federal and state agencies. This date should exist for reports submitted through a reporting program. This information does not exist with manually entered records (e.g., Caribbean data, vessel logbook data). | |
100
|
UPDATED_BY | VARCHAR2(40) | Text identifier of user who updated the record. | |
100
|
LAST_UPDATED | DATE | Date dealer report record was last updated. | |
100
|
LAST_UPDATED_BY | VARCHAR2(100) | Free text identifying who updated a record. | |
100
|
DATE_LOADED_IN_EDEALER | DATE | Date report loaded into eDealer STAG_HMS_DEALER_REPORTS table. | |
100
|
DATE_LOADED_FINAL_TABLE | DATE | This is the date the HMS records were submitted to be loaded into this final view. | |
100
|
DATE_UPDATED_FINAL_TABLE | DATE | This is the date a HMS record was resubmitted/reloaded in this final view. | |
100
|
STAG_HMS_DEALER_RPT_ID | NUMBER | A Primary Key for a STAG_HMS_DEALER_REPORTS record. An auto-generated number. | |
100
|
HMS_DEALER_RPT_ID | NUMBER | This is a primary key that ACCSP assigns to the data. It links the stag_hms_dealer_reports and stag_jms_landings tables. | |
100
|
DEALER_RPT_ID | NUMBER(9) | Primary Key for DEALER_REPORT records. An auto-generated number. | |
100
|
STAG_HMS_LANDING_ID | NUMBER | Foreign key to link between STAG_HMS_LANDINGS and LANDINGS table; do not need to enter this unless we want a certain version of a record to be in View | |
100
|
LANDING_SEQ | VARCHAR2(40) | Unique identifier for individual landings in the STAG_HMS_LANDINGS table; foreign key to link additional fields manually loaded with records in the STAG_HMS_LANDINGS table; this value stays the same through time | |
100
|
LANDING_ID | NUMBER | Unique identifier for individual landings in the LANIDNGS table; this value will change with each submission of a report | |
100
|
LANDING_RECORD_PROCESSED_YN | VARCHAR2(1) | Yes/No flag field indicating whether a landing record was processed. Taken from the STAG_HMS_LANDINGS table | |
100
|
LANDING_RECORD_DISCARDED_YN | VARCHAR2(1) | Yes/No flag field indicating whether a landing record was discarded. Taken from the STAG_HMS_LANDINGS table | |
100
|
LANDING_ERROR_EXISTS_YN | VARCHAR2(1) | Yes/No flag field indicating whether a landing record had data validation errors. Taken from the STAG_HMS_LANDINGS table | |
100
|
LANDING_ERROR_MESSAGE | VARCHAR2(1000) | Text field describing the issues causing a landing record to fail validation. Taken from the STAG_HMS_LANDINGS table | |
100
|
LANDING_DELETED | VARCHAR2(1) | A Yes/No flag denoting if a landing record was deleted. Taken from the STAG_HMS_LANDINGS table | |
100
|
ACTIVE | VARCHAR2(1) | Yes/No flag indicating if landing record is active | |
100
|
CLASSIFICATION | VARCHAR2(30) | Free text providing a general classification of an HMS species (BAYS TUNA, SHARK, SWORDFISH and UNCLASSIFIED SHARK) | |
100
|
SPECIES_ID | NUMBER | A Primary Key for a SPECIES record. An auto-generated number. | |
100
|
SPECIES_ITIS | VARCHAR2(11) | ITIS code used by itis.gov to indicate species. NOTE: '159786' ("SHARKS, SMALL COASTAL") may be used to report "Shark Belly Flaps"; 159851â ("SHARKS, PELAGIC, UNC") may represent "SHARK FINS" | |
100
|
COMMON_NAME_AS_REPORTED | VARCHAR2(100) | Free text describing a common name for an organism. | |
100
|
COMMON_NAME_ADJUSTED | VARCHAR2(100) | This is the Common_Name used in the Caribbean vessel logbook data (CAR-PR and CAR-USVI) | |
100
|
REAPPORTIONED_YN | VARCHAR2(1) | "Y" indicates that the record was either a report of unclassified HMS-product which was apportioned to species-specific weights, or is a report to species originating from a report of unclassified HMS-product, which was determined by proportions of historical landings | |
100
|
REAPPORTIONED_KEY | VARCHAR2(63) | This is a Key that would tie together original records that included "Unclassified" reported species with records added manually that reapportioned these unclassifieds to species-specific landings. The Key would be the same for all records in that group (e.g., 100 lb unclassified shark may break down to 4 different species and all records would have the same REAPP_KEY). Reapportioned records with species-specific information may or may not include landing and purchase dates, month, gear, disposition, market, vessel, port, or dealer information. Originally submitted records and reapportioned records will be differentiated via the "SAME_AS_WAREHOUSE" column, where "N" indicates a reapportioned record. | |
100
|
REAPPORTIONED_DESC | VARCHAR2(255) | Percentages applied to unclassified HMS products to determine weights of species. | |
100
|
UNIT_MEASURE | VARCHAR2(2) | This field has a code noting the units the REPORTED_QUANTITY is reported in. | |
100
|
REPORTED_QUANTITY | NUMBER | Weight of purchased fish. | |
100
|
DISPOSITION_CODE | VARCHAR2(3) | A SAFIS code describing how a fish was used after purchase. | |
100
|
DISPOSITION_DESC | VARCHAR2(50) | A free text description of the disposition code. | |
100
|
MULTIPLE_DEALER_GROUP_YN | VARCHAR2(1) | A "Y" in this field would indicate transactions from more than one dealer exist or are expected. The default for this field should be "N". | |
100
|
TRIP_KEY | NUMBER | This is a Key that ties together all records from a single vessel trip. The Trip Key is the same for all records in that group. This is an internal, automated value created by the Trip Identification Tool | |
100
|
USED_FOR_QM_REPORT_YN | VARCHAR2(1) | A "Y" in this field would indicate records that should be included for QM updates. A "N" in this field would indicate the record should be excluded for QM updates. | |
100
|
INCLUDE_FOR_FUS_LANDINGS_YN | VARCHAR2(1) | A "Y" in this field would indicate records that should be included for tallying FUS landings. An "N" in this field would indicate records that should be EXcluded for FUS total landings. | |
100
|
USED_FOR_FUS_REPORT_YN | VARCHAR2(1) | A "Y" in this field would indicate records that should be included in the FUS report. It is possible that a record may be included for FUS landings but not for FUS economics (FUS_ECONOMICS_1_0). Including all records with a "Y" in this field would provide the entire set of records needed to recreate that report, regardless of being excluded from FUS landings or FUS economics. An "N" in this field would indicate records which should be excluded for the FUS report. | |
100
|
GRADE_CODE | VARCHAR2(1000) | ACCSP standard code used to describe the grade of the fish, or how the fish was cut up upon weighing | |
100
|
GRADE_DESCRIPTION | VARCHAR2(50) | Free text description of the ACCSP gear code value | |
100
|
CONVERTED_DW_LBS | NUMBER(15,2) | This is the reported weight converted to dressed/gutted weight | |
100
|
CONVERTED_WW_LBS | NUMBER(15,2) | This is the reported weight converted to whole weight | |
100
|
TO_WW_MULTIPLIER | NUMBER(15,2) | This is the conversion factor used to calculate whole weight | |
100
|
TO_DW_DIVIDER | NUMBER(15,2) | This is the conversion factor used to calculate dressed/gutted weight | |
100
|
MARKET_CODE | VARCHAR2(1000) | A code describing the quality of product. | |
100
|
PURCHASE_PRICE | NUMBER | Price the dealer paid a fisher per pound of fish product. | |
100
|
INCLUDE_FOR_FUS_ECONOMICS_YN | VARCHAR2(1) | A "Y" in this field would indicate records that should be included for determining economic data for the FUS report. A "N" in this field indicates that this record should be Excluded from economic analyses for FUS. | |
100
|
TOTAL_DOLLARS | NUMBER | Total Purchase Price of fish product | |
100
|
SALE_PRICE | NUMBER | Total sales price for fish if no initial purchase occurred. | |
100
|
HMS_CATCH_AREA | VARCHAR2(50) | HMS Catch Area Code; Indicates where fish were caught in the ocean | |
100
|
AREA_FISHED | VARCHAR2(3) | Federal Fishing Area Code. | |
100
|
SUB_AREA_FISHED | VARCHAR2(5) | Federal Fishing Sub-Area Code. | |
100
|
LOCAL_AREA_CODE | VARCHAR2(6) | This is a sub-area code that is most commonly used in the Northeast to identify shellfish beds | |
100
|
COUNCIL_REGION_AREA | VARCHAR2(50) | This is the region where the fish was landed as defined by the Councils and as indicated in FIN data. Council areas and HMS regions are different (GOM vs SAT around the tip of Florida and for defining the Atlantic regions). Including this as defined in the FINS would be helpful to easily identify errors in comparison. Council region areas are defined by AREA_FISHED and SUB_AREA_FISHED. | |
100
|
QUOTA_GROUP | VARCHAR2(50) | Quota group as defined for HMS quota management | |
100
|
HMS_REGION | VARCHAR2(50) | Region as defined for HMS quota management | |
100
|
SUB_REGION | VARCHAR2(50) | Sub-region as defined for HMS quota management | |
100
|
BASELINE_QUOTA_DW_MT | NUMBER | This is the base quota assigned to an HMS quota group in dressed weight (DW) metric tons (MT) | |
100
|
BASELINE_QUOTA_WW_MT | NUMBER | This is the base quota assigned to an HMS quota group in whole weight (WW) metric tons (MT) | |
100
|
ADJUSTED_QUOTA_DW_MT | NUMBER | This is the adjusted quota assigned to an HMS quota group in dressed weight (DW) metric tons (MT) | |
100
|
ADJUSTED_QUOTA_WW_MT | NUMBER | This is the adjusted quota assigned to an HMS quota group in whole weight (WW) metric tons (MT) | |
100
|
SEASON_START_DATE | DATE | The date a particular quota management group was opened for a given season/year | |
100
|
SEASON_END_DATE | DATE | The date a particular quota management group was closed for a given season/year | |
100
|
SUPPLIER_DR_ID_GFIN | VARCHAR2(50) | Data included from manually entered GulfFIN data. Needed to identify dealer. | |
100
|
GULFIN_LANDING_ID | NUMBER(38) | Data included from manually entered GulfFIN data. Helpful to identify landing record in GulfFIN. | |
100
|
FORM_VERSION | VARCHAR2(60) | Data included from manually entered FIN data. Helpful to identify method landing report was submitted to FIN. | |
100
|
DIFFER_FROM_WAREHOUSE_Y | VARCHAR2(1) | A "Y" in this field indicates the record has been purposefully changed and will not match records already housed in the FIN data warehouses. A null field indicates that the record has not been verified as being the same or different. Changes may exist between eDealer data and master FIN data if a state has made alterations to the record. | |
100
|
WAREHOUSE_CHANGE_TYPE | VARCHAR2(31) | If a "Y" exists in DIFFER_FROM_WAREHOUSE_Y, then the type of difference is required: "NEW" means record does not exist in FIN warehouse; "Modified" means the record exists but was changed in the HMS Master View. If "DIFFER_FROM_WAREHOUSE" is null, then this field should be null. | |
100
|
NOTES | VARCHAR2(500) | Free form field to hold notes from administrators | |
100
|
INTERNAL_REVIEW_COMMENTS | VARCHAR2(150) | Free text describing any record review comments by HMS staff | |
100
|
REVIEW_COMMENTS_UPDATED_BY | VARCHAR2(100) | Free text identifying the HMS staffer making review comments | |
100
|
REVIEW_COMMENTS_UPDATE_DATE | DATE | Date review comments entered into dealer report record. | |
100
|
LANDING_STATUS | VARCHAR2(1) | To keep or exclude a record or landing based on value in the Trip Identification Tool | |
100
|
ECONOMIC_STATUS | VARCHAR2(1) | To keep or exclude a record's price information based on value in the Trip Identification Tool | |
100
|
EX_VESSEL_VALUE | NUMBER(13,3) | A calculated value of the price / lb at the first purchase multiplied by the total lbs landed | |
100
|
NOTES_ECONOMIC | VARCHAR2(500) | Free form field to hold notes from economist |
Attribute Details
YEAR_OF_LANDING
Seq. Order: | 1 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Year the product was landed and taken from the DATE_LANDED field. If this is not available, the year from DATE_PURCHASED is used. |
MONTH_OF_LANDING
Seq. Order: | 2 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Month information taken from the DATE_LANDED field. If this is not available, the month from DATE_PURCHASED is used. |
SAFIS_DEALER_RPT_ID
Seq. Order: | 3 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Unique report identifier coming from the SAFIS system |
DEALER_TICKET_NO
Seq. Order: | 4 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Unique report identifier coming from a Trip Ticket system |
EDEALER_RPT_NUM
Seq. Order: | 5 |
---|---|
Data Storage Type: | VARCHAR2(20) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Unique report identifier coming from the edealer reporting system (applied to all reports validated and pulled into the edealer production tables) |
REPORT_TYPE
Seq. Order: | 6 |
---|---|
Data Storage Type: | VARCHAR2(30) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Identifies where the record is pulled. Sources include eDealer production tables (EDLR-P), eDealer records in stuck tables that have been verified as accurate (EDLR-S), records that include "Unclassified" landings and have been reapportioned to a species (REAPP; this information is used for quota monitoring and stock assessments), GulfFIN data (GFIN), ACCSP data (ACCSP), Pelagic longline vessel logbooks from the SEFSC (PLLLB), Caribbean vessel logbook data from Puerto Rico (CAR-PR) and the USVI (CAR-USVI). this is similar to the SOURCE information but more specific. |
TABLE_TYPE
Seq. Order: | 7 |
---|---|
Data Storage Type: | VARCHAR2(30) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Indicates whether the data came directly from eDealer (via a "VALIDATED" or "STUCK" record) or a record was taken from an outside source and record was entered in manually into the VIEW ("MANUAL"). |
SOURCE
Seq. Order: | 8 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Description of where the report came from: Caribbean report, dealer report, vessel report, PLLLB. This is similar to the information displayed in REPORT_TYPE, but is categorical information. |
CORPORATE_NAME
Seq. Order: | 9 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Corporate name of dealer, if applicable |
SAFIS_DEALER_ID
Seq. Order: | 10 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The SAFIS participant ID |
NE_PERMIT
Seq. Order: | 11 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The federal dealer permit number issued from GARFO |
SE_PERMIT
Seq. Order: | 12 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The federal dealer permit number issued from SERO |
SOURCE_SYSTEM
Seq. Order: | 13 |
---|---|
Data Storage Type: | VARCHAR2(20) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Identifiers denoting what data system HMS records were pulled from. These currently are: ACCSP-Cmpr (ACCSP data warehouse comparison), PWR-SEFSC Weigh out (weigh out data comparison), MFIN - P (paper form from GulfFIN), ACCSP (electronic record from ACCSP), SAFIS (electronic record from SAFIS), NCSCBI (electronic record from North Carolina state program), CCL-SEFSC Carib (Caribbean landings from SEFSC), GULFIN (electronic record from GulfFIN) |
SAFIS_PERMIT_ID
Seq. Order: | 14 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A foreign key from the SAFIS PERMITS table. Identifies the permit under which a Dealer/participant is reporting. |
DEALER_STATE
Seq. Order: | 15 |
---|---|
Data Storage Type: | VARCHAR2(20) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the state listed in the permit file for the dealer's business address. In some cases, it is more accurate to describe it as the State the dealer conducts business in. |
RECEIVED_FILENAME
Seq. Order: | 16 |
---|---|
Data Storage Type: | VARCHAR2(45) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the filename associated with a group of reports submitted by a dealer using a Trip Ticket or Florida VESL reporting program. This serve as a confirmation number that a dealer submitted a report to the federal agency. The contains a time/date stamp that corresponds to the date of submission. |
DATE_PURCHASED
Seq. Order: | 17 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date fish product purchased; the date the dealer took possession of the product |
DATE_LANDED
Seq. Order: | 18 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date fish product landed (when the boat comes to the dock). This date is used for quota monitoring. |
RECONCILED_DATE_LANDED
Seq. Order: | 19 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the landing date taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool |
LOCATION_CODE
Seq. Order: | 20 |
---|---|
Data Storage Type: | VARCHAR2(6) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is a code that indicates the port of landing in the STAG_HMS_DEALER_REPORTS; It is from the PORT code in the VALID_PORTS table and becomes the PORT code in the DEALER_REPORTS table |
PORT_NAME
Seq. Order: | 21 |
---|---|
Data Storage Type: | VARCHAR2(60) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Name of port where fishing vessel landed and offloaded the product |
PORT_STATE_CODE
Seq. Order: | 22 |
---|---|
Data Storage Type: | VARCHAR2(2) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The 2-number code used by the FINS (GulfFIN and ACCSP) to indicate the state of the port of landing. |
PORT_STATE
Seq. Order: | 23 |
---|---|
Data Storage Type: | VARCHAR2(2) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
State of the port where the fishing vessel landed and offloaded the product |
RECONCILED_PORT_STATE
Seq. Order: | 24 |
---|---|
Data Storage Type: | VARCHAR2(2) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the port state taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool |
FUS_STATE
Seq. Order: | 25 |
---|---|
Data Storage Type: | VARCHAR2(30) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
State of the port where the fishing vessel landed and offloaded the product according to the Fisheries of the US (FUS). This is the same as the PORT_STATE except: 1) the state of Florida is split into "Florida-East" (FE) and "Florida-West" (FW); and 2) the nomenclature for Caribbean states is slightly different, per S&T request. |
SUPPLIER_VESSEL_ID
Seq. Order: | 26 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
USCG documentation number or state registration number of the vessel dealer purchased product from as reported by the dealer |
RECONCILED_VESSEL_ID
Seq. Order: | 27 |
---|---|
Data Storage Type: | VARCHAR2(30) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the vessel registration (USCG # or state registration number) taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool |
VESSEL_ID
Seq. Order: | 28 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Internal identifier assigned by the SAFIS program and pulled into edealer |
VESSEL_FED_PERMIT_NUMBER
Seq. Order: | 29 |
---|---|
Data Storage Type: | VARCHAR2(127) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Federal fishing permit number; string concatenated with a comma |
VESSEL_PERMIT_CATEGORY
Seq. Order: | 30 |
---|---|
Data Storage Type: | VARCHAR2(30) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Swordfish fishing vessel permit category (Directed or Incidental) |
TRIP_ID
Seq. Order: | 31 |
---|---|
Data Storage Type: | VARCHAR2(4000) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
VTR or logbook number of the fishing trip that the dealer purchased fish from |
RECONCILED_TRIP_ID
Seq. Order: | 32 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the VTR # taken from the vessel logbook record; this field is populated after a reconciliation event occurs in the Logbook Reconciliation tool |
REASON_NO_FV_LOGBOOK_ID
Seq. Order: | 33 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Dealer submits the reason a logbook was not submitted by a vessel; this is a number that corresponds to a standardized list of reasons of why a logbook # was not supplied by a dealer; this field is from DEALER_REPORTS table |
EXPLANATION_NO_LOGBOOK
Seq. Order: | 34 |
---|---|
Data Storage Type: | VARCHAR2(150) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Description of why a dealer did not submit a VTR # on a dealer report; corresponds to the number on the standardized list of reasons why no VTR # was supplied by the dealer; this field is from DEALER_REPORTS table |
WHY_NO_VTR
Seq. Order: | 35 |
---|---|
Data Storage Type: | VARCHAR2(150) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Name of the field in the STAG_HMS_DEALER_REPORTS table that hold the explanation of why no VTR # was provided by the dealer. |
OBSERVER_LOG_ID
Seq. Order: | 36 |
---|---|
Data Storage Type: | VARCHAR2(25) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The dealer indicates the logbook identifier from the observer logbook; the presence of this value is used to identify shark research trips |
GEAR_CODE
Seq. Order: | 37 |
---|---|
Data Storage Type: | VARCHAR2(3) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
ACCSP standard code associated with gear submitted on the report by the dealer |
RECONCILED_GEAR_TYPE
Seq. Order: | 38 |
---|---|
Data Storage Type: | VARCHAR2(3) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the gear type taken from the vessel logbook record; this field is populated after a reconcilation event occurs in the Logbook Reconciliation tool |
GEAR_NAME
Seq. Order: | 39 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This information should match the GEAR_NAME column as they exist in the Gear tables at the FINS and as they exist in FIN Standard codes. |
LATE_REPORT_EXPLANATION
Seq. Order: | 40 |
---|---|
Data Storage Type: | VARCHAR2(150) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Explanation provided by the dealer describing why a report was late |
MODIFIED_DATE_EXPLANATION
Seq. Order: | 41 |
---|---|
Data Storage Type: | VARCHAR2(150) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Entered by the dealer to explain changes on a report and/or if a transaction is not a duplicate entry (if there are mutliple entries that are the same within a report) |
RECORD_PROCESSED_YN
Seq. Order: | 42 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A "Y" indicates that the record was processed by edealer and put in the production DEALER_REPORTS and LANDINGS tables; a "N" indicates that the record has not been processed; this is taken from the STAG_HMS_DEALER_REPORTS table |
RECORD_DISCARDED_YN
Seq. Order: | 43 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A "Y" indicates that the reocrd was discarded; and "N" indicates that the record has not been discarded; this is taken from the STAG_HMS_DEALER_REPORTS table |
ERROR_EXISTS_YN
Seq. Order: | 44 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Indicates if an error existed in the dealer report. Y (Yes) or N (No) values |
ERROR_MESSAGE
Seq. Order: | 45 |
---|---|
Data Storage Type: | VARCHAR2(1000) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The message describes the error associated with the dealer report. |
SUBMIT_METHOD
Seq. Order: | 46 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Indicates how a dealer reported was entered and submitted to the federal agencies |
DR_DELETED
Seq. Order: | 47 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
"Y" indicates the dealer deleted the record; a NULL value indicates that the dealer has not deleted the record |
PROCESS_ID
Seq. Order: | 48 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Internal value assigned by the edealer program during a nightly data sycnchronization event with ACCSP; each unique value identifies a separate data synchronization event |
ACTION_FLAG
Seq. Order: | 49 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
"A" value indicates that the record is an "add" or initial submission; "U" value indicates that the record has been updated and the update is being shown |
DATE_ENTERED
Seq. Order: | 50 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date report entered into original reporting program |
DATE_SUBMITTED
Seq. Order: | 51 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This indicates the date when a dealer submitted a report to federal and state agencies. This date should exist for reports submitted through a reporting program. This information does not exist with manually entered records (e.g., Caribbean data, vessel logbook data). |
UTC_SUBMIT_DATE
Seq. Order: | 52 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This indicates the dealer submitted a report. It is in Coordinated Universal Time report submission date/time. Used for reports from Trip Ticket programs |
UTC_UPDATE_DATE
Seq. Order: | 53 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This indicates the dealer submitted an updated report. Coordinated Universal Time report update submission date/time. Used for reports from Trip Ticket programs |
UTC_DATE_SUBMITTED_FLAG
Seq. Order: | 54 |
---|---|
Data Storage Type: | VARCHAR2(5) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Indicates if a report submitted through a Trip Ticket program has a submission date/time stamp from the internet (âÂÂUTCâÂÂ) or from the local computer (âÂÂLOCALâÂÂ). |
UTC_DATE_UPDATED_FLAG
Seq. Order: | 55 |
---|---|
Data Storage Type: | VARCHAR2(5) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Indicates the updated submission date/time stamp of an updated file. Submission time/date stamp from the internet (âÂÂUTCâÂÂ) or from the local computer (âÂÂLOCALâÂÂ). |
DATE_UPDATED
Seq. Order: | 56 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This indicates the date when a dealer updated a report and sent it to the federal and state agencies. This date should exist for reports submitted through a reporting program. This information does not exist with manually entered records (e.g., Caribbean data, vessel logbook data). |
UPDATED_BY
Seq. Order: | 57 |
---|---|
Data Storage Type: | VARCHAR2(40) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Text identifier of user who updated the record. |
LAST_UPDATED
Seq. Order: | 58 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date dealer report record was last updated. |
LAST_UPDATED_BY
Seq. Order: | 59 |
---|---|
Data Storage Type: | VARCHAR2(100) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Free text identifying who updated a record. |
DATE_LOADED_IN_EDEALER
Seq. Order: | 60 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date report loaded into eDealer STAG_HMS_DEALER_REPORTS table. |
DATE_LOADED_FINAL_TABLE
Seq. Order: | 61 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the date the HMS records were submitted to be loaded into this final view. |
DATE_UPDATED_FINAL_TABLE
Seq. Order: | 62 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the date a HMS record was resubmitted/reloaded in this final view. |
STAG_HMS_DEALER_RPT_ID
Seq. Order: | 63 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A Primary Key for a STAG_HMS_DEALER_REPORTS record. An auto-generated number. |
HMS_DEALER_RPT_ID
Seq. Order: | 64 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is a primary key that ACCSP assigns to the data. It links the stag_hms_dealer_reports and stag_jms_landings tables. |
DEALER_RPT_ID
Seq. Order: | 65 |
---|---|
Data Storage Type: | NUMBER(9) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Primary Key for DEALER_REPORT records. An auto-generated number. |
STAG_HMS_LANDING_ID
Seq. Order: | 66 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Foreign key to link between STAG_HMS_LANDINGS and LANDINGS table; do not need to enter this unless we want a certain version of a record to be in View |
LANDING_SEQ
Seq. Order: | 67 |
---|---|
Data Storage Type: | VARCHAR2(40) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Unique identifier for individual landings in the STAG_HMS_LANDINGS table; foreign key to link additional fields manually loaded with records in the STAG_HMS_LANDINGS table; this value stays the same through time |
LANDING_ID
Seq. Order: | 68 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Unique identifier for individual landings in the LANIDNGS table; this value will change with each submission of a report |
LANDING_RECORD_PROCESSED_YN
Seq. Order: | 69 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Yes/No flag field indicating whether a landing record was processed. Taken from the STAG_HMS_LANDINGS table |
LANDING_RECORD_DISCARDED_YN
Seq. Order: | 70 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Yes/No flag field indicating whether a landing record was discarded. Taken from the STAG_HMS_LANDINGS table |
LANDING_ERROR_EXISTS_YN
Seq. Order: | 71 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Yes/No flag field indicating whether a landing record had data validation errors. Taken from the STAG_HMS_LANDINGS table |
LANDING_ERROR_MESSAGE
Seq. Order: | 72 |
---|---|
Data Storage Type: | VARCHAR2(1000) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Text field describing the issues causing a landing record to fail validation. Taken from the STAG_HMS_LANDINGS table |
LANDING_DELETED
Seq. Order: | 73 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A Yes/No flag denoting if a landing record was deleted. Taken from the STAG_HMS_LANDINGS table |
ACTIVE
Seq. Order: | 74 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Yes/No flag indicating if landing record is active |
CLASSIFICATION
Seq. Order: | 75 |
---|---|
Data Storage Type: | VARCHAR2(30) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Free text providing a general classification of an HMS species (BAYS TUNA, SHARK, SWORDFISH and UNCLASSIFIED SHARK) |
SPECIES_ID
Seq. Order: | 76 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A Primary Key for a SPECIES record. An auto-generated number. |
SPECIES_ITIS
Seq. Order: | 77 |
---|---|
Data Storage Type: | VARCHAR2(11) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
ITIS code used by itis.gov to indicate species. NOTE: '159786' ("SHARKS, SMALL COASTAL") may be used to report "Shark Belly Flaps"; 159851â ("SHARKS, PELAGIC, UNC") may represent "SHARK FINS" |
COMMON_NAME_AS_REPORTED
Seq. Order: | 78 |
---|---|
Data Storage Type: | VARCHAR2(100) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Free text describing a common name for an organism. |
COMMON_NAME_ADJUSTED
Seq. Order: | 79 |
---|---|
Data Storage Type: | VARCHAR2(100) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the Common_Name used in the Caribbean vessel logbook data (CAR-PR and CAR-USVI) |
REAPPORTIONED_YN
Seq. Order: | 80 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
"Y" indicates that the record was either a report of unclassified HMS-product which was apportioned to species-specific weights, or is a report to species originating from a report of unclassified HMS-product, which was determined by proportions of historical landings |
REAPPORTIONED_KEY
Seq. Order: | 81 |
---|---|
Data Storage Type: | VARCHAR2(63) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is a Key that would tie together original records that included "Unclassified" reported species with records added manually that reapportioned these unclassifieds to species-specific landings. The Key would be the same for all records in that group (e.g., 100 lb unclassified shark may break down to 4 different species and all records would have the same REAPP_KEY). Reapportioned records with species-specific information may or may not include landing and purchase dates, month, gear, disposition, market, vessel, port, or dealer information. Originally submitted records and reapportioned records will be differentiated via the "SAME_AS_WAREHOUSE" column, where "N" indicates a reapportioned record. |
REAPPORTIONED_DESC
Seq. Order: | 82 |
---|---|
Data Storage Type: | VARCHAR2(255) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Percentages applied to unclassified HMS products to determine weights of species. |
UNIT_MEASURE
Seq. Order: | 83 |
---|---|
Data Storage Type: | VARCHAR2(2) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This field has a code noting the units the REPORTED_QUANTITY is reported in. |
REPORTED_QUANTITY
Seq. Order: | 84 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Weight of purchased fish. |
DISPOSITION_CODE
Seq. Order: | 85 |
---|---|
Data Storage Type: | VARCHAR2(3) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A SAFIS code describing how a fish was used after purchase. |
DISPOSITION_DESC
Seq. Order: | 86 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A free text description of the disposition code. |
MULTIPLE_DEALER_GROUP_YN
Seq. Order: | 87 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A "Y" in this field would indicate transactions from more than one dealer exist or are expected. The default for this field should be "N". |
TRIP_KEY
Seq. Order: | 88 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is a Key that ties together all records from a single vessel trip. The Trip Key is the same for all records in that group. This is an internal, automated value created by the Trip Identification Tool |
USED_FOR_QM_REPORT_YN
Seq. Order: | 89 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A "Y" in this field would indicate records that should be included for QM updates. A "N" in this field would indicate the record should be excluded for QM updates. |
INCLUDE_FOR_FUS_LANDINGS_YN
Seq. Order: | 90 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A "Y" in this field would indicate records that should be included for tallying FUS landings. An "N" in this field would indicate records that should be EXcluded for FUS total landings. |
USED_FOR_FUS_REPORT_YN
Seq. Order: | 91 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A "Y" in this field would indicate records that should be included in the FUS report. It is possible that a record may be included for FUS landings but not for FUS economics (FUS_ECONOMICS_1_0). Including all records with a "Y" in this field would provide the entire set of records needed to recreate that report, regardless of being excluded from FUS landings or FUS economics. An "N" in this field would indicate records which should be excluded for the FUS report. |
GRADE_CODE
Seq. Order: | 92 |
---|---|
Data Storage Type: | VARCHAR2(1000) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
ACCSP standard code used to describe the grade of the fish, or how the fish was cut up upon weighing |
GRADE_DESCRIPTION
Seq. Order: | 93 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Free text description of the ACCSP gear code value |
CONVERTED_DW_LBS
Seq. Order: | 94 |
---|---|
Data Storage Type: | NUMBER(15,2) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the reported weight converted to dressed/gutted weight |
CONVERTED_WW_LBS
Seq. Order: | 95 |
---|---|
Data Storage Type: | NUMBER(15,2) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the reported weight converted to whole weight |
TO_WW_MULTIPLIER
Seq. Order: | 96 |
---|---|
Data Storage Type: | NUMBER(15,2) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the conversion factor used to calculate whole weight |
TO_DW_DIVIDER
Seq. Order: | 97 |
---|---|
Data Storage Type: | NUMBER(15,2) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the conversion factor used to calculate dressed/gutted weight |
MARKET_CODE
Seq. Order: | 98 |
---|---|
Data Storage Type: | VARCHAR2(1000) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A code describing the quality of product. |
PURCHASE_PRICE
Seq. Order: | 99 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Price the dealer paid a fisher per pound of fish product. |
INCLUDE_FOR_FUS_ECONOMICS_YN
Seq. Order: | 100 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A "Y" in this field would indicate records that should be included for determining economic data for the FUS report. A "N" in this field indicates that this record should be Excluded from economic analyses for FUS. |
TOTAL_DOLLARS
Seq. Order: | 101 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Total Purchase Price of fish product |
SALE_PRICE
Seq. Order: | 102 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Total sales price for fish if no initial purchase occurred. |
HMS_CATCH_AREA
Seq. Order: | 103 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
HMS Catch Area Code; Indicates where fish were caught in the ocean |
AREA_FISHED
Seq. Order: | 104 |
---|---|
Data Storage Type: | VARCHAR2(3) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Federal Fishing Area Code. |
SUB_AREA_FISHED
Seq. Order: | 105 |
---|---|
Data Storage Type: | VARCHAR2(5) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Federal Fishing Sub-Area Code. |
LOCAL_AREA_CODE
Seq. Order: | 106 |
---|---|
Data Storage Type: | VARCHAR2(6) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is a sub-area code that is most commonly used in the Northeast to identify shellfish beds |
COUNCIL_REGION_AREA
Seq. Order: | 107 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the region where the fish was landed as defined by the Councils and as indicated in FIN data. Council areas and HMS regions are different (GOM vs SAT around the tip of Florida and for defining the Atlantic regions). Including this as defined in the FINS would be helpful to easily identify errors in comparison. Council region areas are defined by AREA_FISHED and SUB_AREA_FISHED. |
QUOTA_GROUP
Seq. Order: | 108 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Quota group as defined for HMS quota management |
HMS_REGION
Seq. Order: | 109 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Region as defined for HMS quota management |
SUB_REGION
Seq. Order: | 110 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Sub-region as defined for HMS quota management |
BASELINE_QUOTA_DW_MT
Seq. Order: | 111 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the base quota assigned to an HMS quota group in dressed weight (DW) metric tons (MT) |
BASELINE_QUOTA_WW_MT
Seq. Order: | 112 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the base quota assigned to an HMS quota group in whole weight (WW) metric tons (MT) |
ADJUSTED_QUOTA_DW_MT
Seq. Order: | 113 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the adjusted quota assigned to an HMS quota group in dressed weight (DW) metric tons (MT) |
ADJUSTED_QUOTA_WW_MT
Seq. Order: | 114 |
---|---|
Data Storage Type: | NUMBER |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This is the adjusted quota assigned to an HMS quota group in whole weight (WW) metric tons (MT) |
SEASON_START_DATE
Seq. Order: | 115 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The date a particular quota management group was opened for a given season/year |
SEASON_END_DATE
Seq. Order: | 116 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The date a particular quota management group was closed for a given season/year |
SUPPLIER_DR_ID_GFIN
Seq. Order: | 117 |
---|---|
Data Storage Type: | VARCHAR2(50) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Data included from manually entered GulfFIN data. Needed to identify dealer. |
GULFIN_LANDING_ID
Seq. Order: | 118 |
---|---|
Data Storage Type: | NUMBER(38) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Data included from manually entered GulfFIN data. Helpful to identify landing record in GulfFIN. |
FORM_VERSION
Seq. Order: | 119 |
---|---|
Data Storage Type: | VARCHAR2(60) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Data included from manually entered FIN data. Helpful to identify method landing report was submitted to FIN. |
DIFFER_FROM_WAREHOUSE_Y
Seq. Order: | 120 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A "Y" in this field indicates the record has been purposefully changed and will not match records already housed in the FIN data warehouses. A null field indicates that the record has not been verified as being the same or different. Changes may exist between eDealer data and master FIN data if a state has made alterations to the record. |
WAREHOUSE_CHANGE_TYPE
Seq. Order: | 121 |
---|---|
Data Storage Type: | VARCHAR2(31) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
If a "Y" exists in DIFFER_FROM_WAREHOUSE_Y, then the type of difference is required: "NEW" means record does not exist in FIN warehouse; "Modified" means the record exists but was changed in the HMS Master View. If "DIFFER_FROM_WAREHOUSE" is null, then this field should be null. |
NOTES
Seq. Order: | 122 |
---|---|
Data Storage Type: | VARCHAR2(500) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Free form field to hold notes from administrators |
INTERNAL_REVIEW_COMMENTS
Seq. Order: | 123 |
---|---|
Data Storage Type: | VARCHAR2(150) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Free text describing any record review comments by HMS staff |
REVIEW_COMMENTS_UPDATED_BY
Seq. Order: | 124 |
---|---|
Data Storage Type: | VARCHAR2(100) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Free text identifying the HMS staffer making review comments |
REVIEW_COMMENTS_UPDATE_DATE
Seq. Order: | 125 |
---|---|
Data Storage Type: | DATE |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date review comments entered into dealer report record. |
LANDING_STATUS
Seq. Order: | 126 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
To keep or exclude a record or landing based on value in the Trip Identification Tool |
ECONOMIC_STATUS
Seq. Order: | 127 |
---|---|
Data Storage Type: | VARCHAR2(1) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
To keep or exclude a record's price information based on value in the Trip Identification Tool |
EX_VESSEL_VALUE
Seq. Order: | 128 |
---|---|
Data Storage Type: | NUMBER(13,3) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A calculated value of the price / lb at the first purchase multiplied by the total lbs landed |
NOTES_ECONOMIC
Seq. Order: | 129 |
---|---|
Data Storage Type: | VARCHAR2(500) |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Free form field to hold notes from economist |
Support Roles
Data Steward
Date Effective From: | 2024-11-01 |
---|---|
Date Effective To: | |
Contact (Person): | Wilson Farber, Jacqueline |
Address: |
1315 East West Hwy Silver Spring, MD 20910 USA |
Email Address: | jackie.wilson@noaa.gov |
Phone: | 240-338-3936 |
Fax: | 404-806-9188 |
Contact Instructions: |
Phone: 240-338-3936 |
Distributor
Date Effective From: | 2013-01-01 |
---|---|
Date Effective To: | |
Contact (Organization): | NMFS Office Of Sustainable Fisheries (OSF) |
Address: |
1315 East-West Highway, 13th Floor Silver Spring, MD 20910 |
Contact Instructions: |
Atlantic Highly Migratory Species Management Division Division Chief: Randy Blankinship |
Catalog Details
Catalog Item ID: | 75306 |
---|---|
GUID: | gov.noaa.nmfs.inport:75306 |
Metadata Record Created By: | Jacqueline Wilson Farber |
Metadata Record Created: | 2025-03-19 15:37+0000 |
Metadata Record Last Modified By: | Matthew Van Kleunen |
Metadata Record Last Modified: | 2025-03-28 19:09+0000 |
Metadata Record Published: | 2025-03-28 |
Owner Org: | OSF |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Review Frequency: | 1 Year |