Table: ATLW_OFFLOAD
Entity (ENT) | Alaska Fisheries Science Center (AFSC)GUID: gov.noaa.nmfs.inport:9629 | Updated: August 9, 2022 | Published / External
Item Identification
Title: | Table: ATLW_OFFLOAD |
---|---|
Short Name: | ATLW_OFFLOAD |
Status: | Completed |
Abstract: |
This entity represents an offload event at a processing plant or mothership. |
Purpose: |
Working Tables accept the raw data from field transmissions or data entry. They are unconstrained, Relational integrity data validation is performed when data are loaded into NORPAC transaction tables. Error checking is performed by batch processes on production data. |
Notes: |
Loaded by batch 2390, 06-30-2009 16:11 |
Entity Information
Entity Type: | Data Table |
---|---|
Active Version?: | Yes |
Schema Name: | NORPAC |
Description: |
This entity represents an offload event at a processing plant or mothership. |
Data Attributes
Attribute Summary
Name | Type | Description | ||
---|---|---|---|---|
100
|
RECORD_SET_STATUS_SEQ | NUMBER | Sequence generated unique identifier of a record set header | |
100
|
CRUISE | NUMBER | Sequence generated by Norpac and supplied to the observer as an unique identifier for an observer cruise record. | |
100
|
OFFLOAD_SEQ | NUMBER | Sequence generated unique identifier for an offload record | |
100
|
OFFLOAD_NUMBER | NUMBER | Unique offload for an observer cruise entered by the observer. | |
100
|
TRIP_SEQ | NUMBER | Sequence generated unique identifier of a trip | |
100
|
PLANT_SEQ | NUMBER | Optional FK to Plant. Part of arc involving catcher vessel, haul, and cruise plant. Code identifying a processing plant - inherited from the NORPAC data set. The plant_vessel_code is created by logistics staff. | |
100
|
CRUISE_PLANT_SEQ | NUMBER | Sequence generated unique value for a cruise plant record. | |
100
|
DELIVERY_VESSEL_ADFG | VARCHAR2 | ADFG number entered by the observer if the vessel does not exist in the vessel lookup table | |
100
|
GEAR_TYPE_CODE | NUMBER | Numeric value from Norpac Domestic Gear that combined with the Form defines the unique identifier for a gear record | |
100
|
GEARTYPE_FORM | VARCHAR2 | Form that the gear is valid for. For example the gear may be Unknown for a delivery but will always be determined for a haul. | |
100
|
DELIVERY_END_DATE | DATE | Date the delivery was complete. | |
100
|
NMFS_AREA | VARCHAR2 | NMFS Reporting Area | |
100
|
DELIVERED_WEIGHT | NUMBER | Total weight of the delivery | |
100
|
TOTAL_POLLOCK_WEIGHT | NUMBER | Identifies the total weight of pollock delivered | |
100
|
LB_MT | VARCHAR2 | Pounds (LB) or Metric Tons (MT) identifier of weight. | |
100
|
GROUNDFISH_WEIGHED_FLAG | VARCHAR2 | Identifies whether or not all the groundfish were weighed. | |
100
|
SORTED_AT_SEA_FLAG | VARCHAR2 | Identifies catch sorted by the catcher vessel at sea. | |
100
|
OFFLOAD_TO_TENDER_FLAG | VARCHAR2 | Identifies if a tender was used to make this delivery. | |
100
|
PERMIT | VARCHAR2 | Unique Code identifying a vessel or Processor - inherited from the NORPAC data set and created by the RAM division in Juneau | |
100
|
LANDING_REPORT_ID | NUMBER | The region uses the landing report id off the electronic fish ticket as a join column for the catch accounting system. The value is printed on the lower quadrant of every ER fish ticket. Landing_Report_ID is unique to an offload. |
Attribute Details
RECORD_SET_STATUS_SEQ
Seq. Order: | 1 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | Yes |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Sequence generated unique identifier of a record set header |
General Data Type: | NUMBER |
CRUISE
Seq. Order: | 2 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | Yes |
Precision: | 8 |
Scale: | 0 |
Status: | Active |
Description: |
Sequence generated by Norpac and supplied to the observer as an unique identifier for an observer cruise record. |
General Data Type: | NUMBER |
OFFLOAD_SEQ
Seq. Order: | 3 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | Yes |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Sequence generated unique identifier for an offload record |
General Data Type: | NUMBER |
OFFLOAD_NUMBER
Seq. Order: | 4 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Unique offload for an observer cruise entered by the observer. |
General Data Type: | NUMBER |
TRIP_SEQ
Seq. Order: | 5 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Sequence generated unique identifier of a trip |
General Data Type: | NUMBER |
PLANT_SEQ
Seq. Order: | 6 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Optional FK to Plant. Part of arc involving catcher vessel, haul, and cruise plant. Code identifying a processing plant - inherited from the NORPAC data set. The plant_vessel_code is created by logistics staff. |
General Data Type: | NUMBER |
CRUISE_PLANT_SEQ
Seq. Order: | 7 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Sequence generated unique value for a cruise plant record. |
General Data Type: | NUMBER |
DELIVERY_VESSEL_ADFG
Seq. Order: | 8 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 6 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
ADFG number entered by the observer if the vessel does not exist in the vessel lookup table |
General Data Type: | VARCHAR2 |
GEAR_TYPE_CODE
Seq. Order: | 9 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Numeric value from Norpac Domestic Gear that combined with the Form defines the unique identifier for a gear record |
General Data Type: | NUMBER |
GEARTYPE_FORM
Seq. Order: | 10 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Form that the gear is valid for. For example the gear may be Unknown for a delivery but will always be determined for a haul. |
General Data Type: | VARCHAR2 |
DELIVERY_END_DATE
Seq. Order: | 11 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date the delivery was complete. |
General Data Type: | DATE |
NMFS_AREA
Seq. Order: | 12 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 3 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
NMFS Reporting Area |
General Data Type: | VARCHAR2 |
DELIVERED_WEIGHT
Seq. Order: | 13 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 10 |
Scale: | 3 |
Status: | Active |
Description: |
Total weight of the delivery |
General Data Type: | NUMBER |
TOTAL_POLLOCK_WEIGHT
Seq. Order: | 14 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 10 |
Scale: | 3 |
Status: | Active |
Description: |
Identifies the total weight of pollock delivered |
General Data Type: | NUMBER |
LB_MT
Seq. Order: | 15 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Pounds (LB) or Metric Tons (MT) identifier of weight. |
General Data Type: | VARCHAR2 |
GROUNDFISH_WEIGHED_FLAG
Seq. Order: | 16 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Identifies whether or not all the groundfish were weighed. |
General Data Type: | VARCHAR2 |
SORTED_AT_SEA_FLAG
Seq. Order: | 17 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Identifies catch sorted by the catcher vessel at sea. |
General Data Type: | VARCHAR2 |
OFFLOAD_TO_TENDER_FLAG
Seq. Order: | 18 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Identifies if a tender was used to make this delivery. |
General Data Type: | VARCHAR2 |
PERMIT
Seq. Order: | 19 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 6 |
Required: | Yes |
Primary Key: | Yes |
Status: | Active |
Description: |
Unique Code identifying a vessel or Processor - inherited from the NORPAC data set and created by the RAM division in Juneau |
General Data Type: | VARCHAR2 |
LANDING_REPORT_ID
Seq. Order: | 20 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 10 |
Scale: | 0 |
Status: | Active |
Description: |
The region uses the landing report id off the electronic fish ticket as a join column for the catch accounting system. The value is printed on the lower quadrant of every ER fish ticket. Landing_Report_ID is unique to an offload. |
General Data Type: | NUMBER |
Catalog Details
Catalog Item ID: | 9629 |
---|---|
GUID: | gov.noaa.nmfs.inport:9629 |
Metadata Record Created By: | Doug Turnbull |
Metadata Record Created: | 2009-06-30 16:11+0000 |
Metadata Record Last Modified By: | SysAdmin InPortAdmin |
Metadata Record Last Modified: | 2022-08-09 17:11+0000 |
Metadata Record Published: | 2018-09-26 |
Owner Org: | AFSC |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2018-09-26 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2019-09-26 |