Table: ODDS_TRIP_PLAN_LOG
Entity (ENT) | Alaska Fisheries Science Center (AFSC)GUID: gov.noaa.nmfs.inport:18866 | Updated: August 9, 2022 | Published / External
Item Identification
Title: | Table: ODDS_TRIP_PLAN_LOG |
---|---|
Short Name: | ODDS_TRIP_PLAN_LOG |
Status: | Completed |
Abstract: |
VESSEL PLANT SEQ for deployment of assigned observer. |
Notes: |
Loaded by batch 4561, 04-30-2013 18:33 |
Entity Information
Entity Type: | Data Table |
---|---|
Active Version?: | Yes |
Schema Name: | NORPAC |
Description: |
VESSEL PLANT SEQ for deployment of assigned observer. |
Data Attributes
Attribute Summary
Name | Type | Description | ||
---|---|---|---|---|
100
|
TRIP_PLAN_LOG_SEQ | NUMBER | Unique trip log sequence number | |
100
|
TRIP_STATUS_SEQ | NUMBER | This column is the unique FK identifier for an odds_lov_trip_status record. From which trip_status_code is denormalized for the convenience of the APEX GUI. | |
100
|
TRIP_STATUS_CODE | VARCHAR2 | The trip status completed, cancelled , pending. The value of this attribute is denormalized from odds_lov_trip_status for the convenience of the APEX application. | |
100
|
TRIP_OBSERVER_SEQ | NUMBER | This fk is the unique key for status of observer coverage for a logged trip. | |
100
|
TRIP_OBS_CODE | VARCHAR2 | Code describing observer coverage for a logged trip. This code is denormalized from odds_lov_trip_obs_status for the convenience of the user application. | |
100
|
INHERIT_OBS_TRIP_SEQ | NUMBER | If a trip is cancelled for any reason within the odds system, this trip number a subsequent trip inherits the properties of the recursive parent. | |
100
|
VESSEL_PLANT_SEQ | NUMBER | This attribute represents cruise number and vessel from the logistics system of an observer assigned to trip if applicable. It is the FK to ols_vessel_plant, is populated by the application when an observer is assgned by an employer, and provides the connection to employer and to a specific contract for a fishery observer. | |
100
|
DATE_LOGGED | DATE | date trip was added to system | |
100
|
LOGGED_BY | NUMBER | User who entered t the trip log record - this may be done by NMFS Staff or the Vessel representative. If done by the vessel, the 72 hour rules applies for the observer provider and the column value is validated against the odds_user_vessel table | |
100
|
PLANNED_EMBARK_DATE | DATE | Date that a vessel representative declares as the planned date of embarkation of a fishing trip. | |
100
|
ORIGINAL_EMBARK_DATE | DATE | date - time of embark date when originally entered into system. allows trip delay check. | |
100
|
PLANNED_EMBARK_PORT | NUMBER | Port the vessel leaves from - fk from atl_lov_port. | |
100
|
PLANNED_DISEMBARK_DATE | DATE | date - time vessel declares as its intent to return from a trip. Close out trip | |
100
|
DISEMBARK_DATE | DATE | Date vessel returned from trip | |
100
|
DISEMBARK_PLANT | NUMBER | Declared port and processor at which a trip is intended to terminate. This fk is from atl_lov_plant. | |
100
|
PLANNED_DISEMBARK_PLANT | NUMBER | Stated intention of plant and port trip terminus. Entered when logging a trip. | |
100
|
CANCEL_DATE_TIME | DATE | It is permitted to cancel a declared trip prior to fortyeight hours after the declard embark date. This attribute records the timstamp of that action. | |
100
|
TRIP_SELECTED_OBS | VARCHAR2 | indicates final outcome if the planned trip is observed or not observed | |
100
|
AMENDED_COUNT | NUMBER | Number of times a log record was amended | |
100
|
AMENDED_BY | NUMBER | User who last amended the trip log - this may be done by NMFS Staff or the Vessel representative. If done by the vessel, the 72 hour rules applies for the observer provider and the column value is validated against the odds_user_vessel tabl | |
100
|
AMENDED_DATE | DATE | Date user last amended the log record | |
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. | |
100
|
CDQ_FLAG | VARCHAR2 | indicated if trip is cdq or not | |
100
|
AFA_TRIP_FLAG | VARCHAR2 | inidcates answer for AFA filter question. Should only be N or null. Null for non AFA vessels | |
100
|
ROCKFISH_TRIP_FLAG | VARCHAR2 | inicates answer for rockfish filter question for participating vessels. Should be N or null . | |
100
|
TRAWL_GEAR_TRIP_FLAG | VARCHAR2 | indicates answer for trawl gear filter question. Trawl gear CDQ trips are not logged. | |
100
|
VESSEL_SEQ | NUMBER | Sequence for the vessel the trip plan is for | |
100
|
LOGGED_FOR | NUMBER | User trip was logged for when logged by the call center | |
100
|
TRIP_PLAN_NUMBER | VARCHAR2 | If an ODDS trip is recorded manually by the call center. Then a preprinted form is used - that form is prepopulated with a unique alphanumeric identifier composed of AB+an integer. The manual form is provided to allow an ODDS trip to be recorded when the ODDS system is not available. | |
100
|
SAMPLE_PLAN_SEQ | NUMBER | Sample plan seq identifing the strata the trip belongs to |
Attribute Details
TRIP_PLAN_LOG_SEQ
Seq. Order: | 1 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | Yes |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Unique trip log sequence number |
General Data Type: | NUMBER |
TRIP_STATUS_SEQ
Seq. Order: | 2 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
This column is the unique FK identifier for an odds_lov_trip_status record. From which trip_status_code is denormalized for the convenience of the APEX GUI. |
General Data Type: | NUMBER |
Foreign Key Relations: |
NORPAC.ODDS_LOV_TRIP_STATUS |
TRIP_STATUS_CODE
Seq. Order: | 3 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
The trip status completed, cancelled , pending. The value of this attribute is denormalized from odds_lov_trip_status for the convenience of the APEX application. |
General Data Type: | VARCHAR2 |
TRIP_OBSERVER_SEQ
Seq. Order: | 4 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 38 |
Scale: | 0 |
Status: | Active |
Description: |
This fk is the unique key for status of observer coverage for a logged trip. |
General Data Type: | NUMBER |
Foreign Key Relations: |
NORPAC.ODDS_LOV_TRIP_OBS_STATU |
TRIP_OBS_CODE
Seq. Order: | 5 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Code describing observer coverage for a logged trip. This code is denormalized from odds_lov_trip_obs_status for the convenience of the user application. |
General Data Type: | VARCHAR2 |
INHERIT_OBS_TRIP_SEQ
Seq. Order: | 6 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Scale: | 0 |
Status: | Active |
Description: |
If a trip is cancelled for any reason within the odds system, this trip number a subsequent trip inherits the properties of the recursive parent. |
General Data Type: | NUMBER |
Foreign Key Relations: |
NORPAC.ODDS_TRIP_PLAN_LOG |
VESSEL_PLANT_SEQ
Seq. Order: | 7 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
This attribute represents cruise number and vessel from the logistics system of an observer assigned to trip if applicable. It is the FK to ols_vessel_plant, is populated by the application when an observer is assgned by an employer, and provides the connection to employer and to a specific contract for a fishery observer. |
General Data Type: | NUMBER |
Foreign Key Relations: |
NORPAC.OLS_VESSEL_PLANT |
DATE_LOGGED
Seq. Order: | 8 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
date trip was added to system |
General Data Type: | DATE |
LOGGED_BY
Seq. Order: | 9 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 38 |
Scale: | 0 |
Status: | Active |
Description: |
User who entered t the trip log record - this may be done by NMFS Staff or the Vessel representative. If done by the vessel, the 72 hour rules applies for the observer provider and the column value is validated against the odds_user_vessel table |
General Data Type: | NUMBER |
PLANNED_EMBARK_DATE
Seq. Order: | 10 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Date that a vessel representative declares as the planned date of embarkation of a fishing trip. |
General Data Type: | DATE |
ORIGINAL_EMBARK_DATE
Seq. Order: | 11 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
date - time of embark date when originally entered into system. allows trip delay check. |
General Data Type: | DATE |
PLANNED_EMBARK_PORT
Seq. Order: | 12 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Port the vessel leaves from - fk from atl_lov_port. |
General Data Type: | NUMBER |
Foreign Key Relations: |
NORPAC.ATL_LOV_PORT_CODE |
PLANNED_DISEMBARK_DATE
Seq. Order: | 13 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
date - time vessel declares as its intent to return from a trip. Close out trip |
General Data Type: | DATE |
DISEMBARK_DATE
Seq. Order: | 14 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date vessel returned from trip |
General Data Type: | DATE |
DISEMBARK_PLANT
Seq. Order: | 15 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Declared port and processor at which a trip is intended to terminate. This fk is from atl_lov_plant. |
General Data Type: | NUMBER |
Foreign Key Relations: |
NORPAC.ATL_LOV_PLANT |
PLANNED_DISEMBARK_PLANT
Seq. Order: | 16 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Stated intention of plant and port trip terminus. Entered when logging a trip. |
General Data Type: | NUMBER |
CANCEL_DATE_TIME
Seq. Order: | 17 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
It is permitted to cancel a declared trip prior to fortyeight hours after the declard embark date. This attribute records the timstamp of that action. |
General Data Type: | DATE |
TRIP_SELECTED_OBS
Seq. Order: | 18 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
indicates final outcome if the planned trip is observed or not observed |
General Data Type: | VARCHAR2 |
AMENDED_COUNT
Seq. Order: | 19 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Number of times a log record was amended |
General Data Type: | NUMBER |
AMENDED_BY
Seq. Order: | 20 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
User who last amended the trip log - this may be done by NMFS Staff or the Vessel representative. If done by the vessel, the 72 hour rules applies for the observer provider and the column value is validated against the odds_user_vessel tabl |
General Data Type: | NUMBER |
AMENDED_DATE
Seq. Order: | 21 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date user last amended the log record |
General Data Type: | DATE |
LANDING_REPORT_ID
Seq. Order: | 22 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
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 |
CDQ_FLAG
Seq. Order: | 23 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
indicated if trip is cdq or not |
General Data Type: | VARCHAR2 |
AFA_TRIP_FLAG
Seq. Order: | 24 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
inidcates answer for AFA filter question. Should only be N or null. Null for non AFA vessels |
General Data Type: | VARCHAR2 |
ROCKFISH_TRIP_FLAG
Seq. Order: | 25 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
inicates answer for rockfish filter question for participating vessels. Should be N or null . |
General Data Type: | VARCHAR2 |
TRAWL_GEAR_TRIP_FLAG
Seq. Order: | 26 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
indicates answer for trawl gear filter question. Trawl gear CDQ trips are not logged. |
General Data Type: | VARCHAR2 |
VESSEL_SEQ
Seq. Order: | 27 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Sequence for the vessel the trip plan is for |
General Data Type: | NUMBER |
Foreign Key Relations: |
NORPAC.ATL_LOV_VESSEL |
LOGGED_FOR
Seq. Order: | 28 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
User trip was logged for when logged by the call center |
General Data Type: | NUMBER |
TRIP_PLAN_NUMBER
Seq. Order: | 29 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 10 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
If an ODDS trip is recorded manually by the call center. Then a preprinted form is used - that form is prepopulated with a unique alphanumeric identifier composed of AB+an integer. The manual form is provided to allow an ODDS trip to be recorded when the ODDS system is not available. |
General Data Type: | VARCHAR2 |
SAMPLE_PLAN_SEQ
Seq. Order: | 30 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Sample plan seq identifing the strata the trip belongs to |
General Data Type: | NUMBER |
Catalog Details
Catalog Item ID: | 18866 |
---|---|
GUID: | gov.noaa.nmfs.inport:18866 |
Metadata Record Created By: | Doug Turnbull |
Metadata Record Created: | 2013-04-30 18:33+0000 |
Metadata Record Last Modified By: | SysAdmin InPortAdmin |
Metadata Record Last Modified: | 2022-08-09 17:11+0000 |
Metadata Record Published: | 2016-05-18 |
Owner Org: | AFSC |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2016-05-18 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2017-05-18 |