Slide Menu
Search Help Show/Hide Menu

Item Identification

Title: Table: FLS_REPORTING_REQUIREMENTS
Short Name: FLS_REPORTING_REQUIREMENTS
Status: Completed
Abstract:

The FLS Reporting Requirements table is built by an FLS program from the VPS_VESSEL_PERMIT table to show what permits require reporting activity for particular assigned management units (a/k/a fisheries_management_units). There is one record per: vessel id permit_category reporting year and reporting month. That record will record all status information recorded for that vessel, permit category, and period.

Notes:

Loaded by batch 2103, 02-28-2008 14:10

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
None complicance
None reporting requirements
None vessels

Entity Information

Entity Type: Data Table
Active Version?: Yes
Schema Name: FLS
Description:

The FLS Reporting Requirements table is built by an FLS program from the VPS_VESSEL_PERMIT table to show what permits require reporting activity for particular assigned management units (a/k/a fisheries_management_units). There is one record per: vessel id permit_category reporting year and reporting month. That record will record all status information recorded for that vessel, permit category, and period.

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
Primary Key VESSEL_ID VARCHAR2 The ID of the vessel for which the logbook has been completed.Validation:A foreign key between this table and FLS_VESSEL_LIST ensures that only valid vessel ids can be entered into this table.The column is mandatory and may not be left empty.
100
Primary Key PERMIT_CATEGORY VARCHAR2 General categories under which the SERO permits are grouped. The PERMIT_CATEGORY closely matches the Fisheries Management Units, except that in the Fisheries Management Units, the Sharks are broken down into Shark Unclassified, Small Coastal Shark, Large Pelagic Shark, and Large Coastal Shark.This classification is used by the Resporting Status portion of the FLS system to report on the logbooks that have been received by each permit category.
100
Primary Key REPORTING_YEAR NUMBER The year in which the reporting requirement was or was not met.
100
Primary Key REPORTING_MONTH NUMBER The month when the catch was landed or unloaded. When we receive the logbook at SEFSC, we consider that the reporting requirement for the LANDING DATE month has been met.If a vessel departed the month or several months before it landed or unloaded the catch, the permit holder gets credit for all months between departure and landing date. The records that are added because of this are flagged in the column CREDITS_PREVIOUS_MONTH.Validation:The field is derived from LANDING_DATE on the table FLS_LOGBOOKS_RECEIVED and is assumed to be correct. The column is mandatory.
100
STATUSES VARCHAR2 All status that affected this vessel, amu, year and month
100
REPORTING_DATE DATE The first day of the reporting_month in the reporting year. This simplifies looking at reporting activity over different time periods.

Attribute Details

VESSEL_ID

CC ID: 27336
Seq. Order: 1
Data Storage Type: VARCHAR2
Max Length: 10
Required: Yes
Primary Key: Yes
Status: Active
Description:

The ID of the vessel for which the logbook has been completed.Validation:A foreign key between this table and FLS_VESSEL_LIST ensures that only valid vessel ids can be entered into this table.The column is mandatory and may not be left empty.

General Data Type: VARCHAR2

PERMIT_CATEGORY

CC ID: 27337
Seq. Order: 2
Data Storage Type: VARCHAR2
Max Length: 5
Required: Yes
Primary Key: Yes
Status: Active
Description:

General categories under which the SERO permits are grouped. The PERMIT_CATEGORY closely matches the Fisheries Management Units, except that in the Fisheries Management Units, the Sharks are broken down into Shark Unclassified, Small Coastal Shark, Large Pelagic Shark, and Large Coastal Shark.This classification is used by the Resporting Status portion of the FLS system to report on the logbooks that have been received by each permit category.

General Data Type: VARCHAR2

REPORTING_YEAR

CC ID: 27338
Seq. Order: 3
Data Storage Type: NUMBER
Max Length: 22
Required: Yes
Primary Key: Yes
Precision: 4
Scale: 0
Status: Active
Description:

The year in which the reporting requirement was or was not met.

General Data Type: NUMBER

REPORTING_MONTH

CC ID: 27339
Seq. Order: 4
Data Storage Type: NUMBER
Max Length: 22
Required: Yes
Primary Key: Yes
Precision: 2
Scale: 0
Status: Active
Description:

The month when the catch was landed or unloaded. When we receive the logbook at SEFSC, we consider that the reporting requirement for the LANDING DATE month has been met.If a vessel departed the month or several months before it landed or unloaded the catch, the permit holder gets credit for all months between departure and landing date. The records that are added because of this are flagged in the column CREDITS_PREVIOUS_MONTH.Validation:The field is derived from LANDING_DATE on the table FLS_LOGBOOKS_RECEIVED and is assumed to be correct. The column is mandatory.

General Data Type: NUMBER

STATUSES

CC ID: 27340
Seq. Order: 5
Data Storage Type: VARCHAR2
Max Length: 8
Required: Yes
Primary Key: No
Status: Active
Description:

All status that affected this vessel, amu, year and month

General Data Type: VARCHAR2

REPORTING_DATE

CC ID: 27341
Seq. Order: 6
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

The first day of the reporting_month in the reporting year. This simplifies looking at reporting activity over different time periods.

General Data Type: DATE

Catalog Details

Catalog Item ID: 7167
GUID: gov.noaa.nmfs.inport:7167
Metadata Record Created By: Lee M Weinberger
Metadata Record Created: 2008-02-28 14:10+0000
Metadata Record Last Modified By: Lee M Weinberger
Metadata Record Last Modified: 2021-05-06 22:24+0000
Metadata Record Published: 2021-05-06
Owner Org: SEFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Next Review Date: 2022-05-07