Ports List View
Ports identify the location that tickets were delivered to. The purpose of the Ports List View is to manage all the available codes and descriptions. This master file comes pre-loaded with the Ports as assigned by the Alaska department of Fish & Game. From here, users can add new records, edit ID's and Descriptions of existing records, and activate/inactivate records.
Pots can be manually managed or can be auto-added as Fish Tickets are imported from eLandings provided the (Fish) Ticket Class is configured to 'Allow import of Missing or Inactive Ports'.
Software Version: 2022.11.28 and newer
Page Header
Toolbar Icons | Description |
|---|---|
Column Filter Show/Hide | |
Delete | |
Excel | |
Favorites | |
Group By Show/Hide | |
Help | |
New | |
Quick Column Filter | |
Save | |
Saved Layouts | |
Fields | Description |
Checkbox | Used to select one or more records. |
Port ID | A text box to add or edit the unique identifier of the Port record. This defaults to blank but is required for all records. If missing, the message "Port ID is required." will be displayed on Save. The ID must be unique, otherwise the message "Duplicate Port IDs are not allowed." will be displayed on Save. This field must be <= 20 characters. Database Field: ERPx_APPort.PortID |
Port Name | A text box to add/edit the name associated with the Port ID. This defaults to blank but is not required. This field must be <= 100 characters. Database Field: ERPx_APPort.PortDescription |
COAR Area | A text box to associate a COAR Area with a Port. This defaults from the value set by ADF&G but is not required, is always editable, duplicates are allowed, and it must be <= 20 characters. Database Field: ERPx_APPort.COARArea |
IFQ Port ID | A text box to associate an IFQ Port ID with a Port. This defaults from the value set by ADF&G but is not required, is always editable, duplicates are allowed, and it must be <= 20 characters. Database Field: ERPx_APPort.IFQPortID |
Inactive | A Yes/No field used to identify if the Port is Inactive. If set to 'Yes' then the record is "Inactive" and will not be included in look-ups. Setting this to Inactive only prevents the record from being manually assigned to new transactions or master files, it does not prevent transactions containing this value to be posted. 'No' values display as blank in the grid. This value is always editable. Database Field: ERPx_APPort.IsInactive |
Related Topics