Ticket Class List View
Ticket Classes are used to identify the types of Fish Tickets supported and the default values and business rules for each. They are used in Fishermen Accounting and are required for all Fishermen Permits. The purpose of this page is to add, edit, remove, and activate/inactive these records.
Software Version: 2022.11.28 and newer
Page Header
| Toolbar Icons | Description |
|---|---|
| Delete | Deletes the selected record(s). When clicked, users will be prompted with: "Are you sure you want to delete the selected records?". Click "OK" to confirm, or "Cancel" to return without deleting. WARNING: Records cannot be recovered once they are deleted! |
| Edit | Opens the selected record for editing. If a record is not selected, the page will not open. |
| Excel |  Clicking the Excel toolbar icon exports the current contents of the grid to an Excel file that is automatically downloaded. The contents that export are only those currently visible. If the grid is filtered, only the filtered contents will be exported. |
| Favorites |   Clicking on the star icon when it is an outline, adds the page to the 'My Shortcuts' tab and fills in the star. Clicking on the star icon when it is filled in (solid color), removes the page from the 'My Shortcuts' tab and returns the icon to an outline.
|
| Grid Layout | Opens the Saved Grid Layout menu that allows the user to select another saved layout, create a new layout, save changes to a layout, or assign a saved layout as the default for the page. Once changes are made to a grid, such as columns are added or removed, the user can click the Saved Grid Layout icon and save the changes to the grid layout and name the new layout. The new layout can also be set as the default, instead of the System View. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific).
|
| Help | Opens the online WIKI help page for the current page.
|
| New | Opens a new blank record for data entry. |
| Fields | Description |
| Checkbox | Used to select one or more records for delete or mass update. |
| ADFG Landing Type | Identifies the eLandings Landing Type the Ticket Class is associated with. This is only used for tickets that import from eLandings. This is the field used to link an eLandings ticket to a NorthScope Ticket Class. This defaults to "DOES NOT INTEGRATE" for new records but can be changed to any value in the list but if changed, duplicates are not allowed. If you are changing to a value that already exists on another ticket class, the message "No Duplicate Landing Types allowed" will be displayed on Save. The list contains the following values:
The lookup contains all the values in the ERPx_APDeliveryTicketADFGLandingType table displayed as [LandingTypeID] - [LandingTypeName] Linked Database Field: ERPx_APTransactionClass.ADFGLandingType |
| Default Price List | Identifies the Price List that will be auto assigned to Fish Tickets. This defaults to blank and is not required. If set, this Price List will be auto-assigned to newly created or imported Fish Tickets. This is always editable from the record view. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Price Lists with a 'Price List Class' of "Fish Ticket". Linked Database Field: ERPx_APTransactionClass.DefaultPriceListHeaderSK |
| Default Site Processed | Identifies the value that will be will be auto-assigned as the 'Site Processed' on newly created or imported Fish Tickets. This defaults to blank, is not required, and duplicate values are allowed. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Sites from the ERPx_MFSite table. Linked Database Field: ERPx_APTransactionClass.DefaultSiteSK |
| Description | The 'Description' property on the Ticket Class record. This defaults to blank for new records but is required. If missing, the message "Description is required." will be displayed on Save. This field is always editable from the record view and must be <= 200 characters. The Description is used as a long description/name of the Ticket Class. Linked Database Field: ERPx_APTransactionClass.TransactionClassDescription |
| Doc Prefix | Identifies the value in the 'Doc Prefix' property on the record view. This defaults to blank for new records and is not required. The 'Doc Prefix' is used in conjunction with the 'Next Ticket Number' to auto assign ticket numbers. This feature is typically used for non Alaska Fish Tickets that are manually entered. System assigned ticket numbers are created by stringing together the [Doc Prefix] and [Next Ticket Number]. The next ticket number is auto incremented each time a system assigned number is used.
This field is always editable from the record view and must be <= 10 characters. Linked Database Field: ERPx_APTransactionClass.DocPrefix |
| Inactive | A Yes/No field used to identify if the record is Inactive. If set to 'Yes' then the record is "Inactive" and will not be included in look-ups for transactions or other master files. If set to 'No' then the record is "Active" and can be freely used. Linked Database Field: ERPx_APTransactionClass.IsInactive |
| Next Ticket Number | Identifies the value in the 'Next Ticket Number' property on the record view. This defaults to blank for new records, is required. If missing, the message "Next Ticket Number is required" will be displayed on Save. The value must be a numeric whole number. If not, the message "Error converting data type nvarchar to bigint." will be displayed on Save The 'Doc Prefix' is used in conjunction with the 'Next Ticket Number' to auto assign ticket numbers. This feature is typically used for non Alaska Fish Tickets that are manually entered. System assigned ticket numbers are created by stringing together the [Doc Prefix] and [Next Ticket Number]. The next ticket number is auto incremented each time a system assigned number is used.
This field is always editable from the record view. However, setting this to a lower number may result in errors caused by duplicate transaction numbers. Linked Database Field: ERPx_APTransactionClass.NextDocNumber |
| Rows to Create on New | Identifies the value in the 'Rows to Create on New' property on the record view. This defaults to 5 for new records, is required, and must be between 1 and 25. If blank it will be set to 5 and if set to any value other than 1 - 25, the message "Rows to Create on New must be between 1 and 25." will be displayed on Save. The 'Rows to Create on New' controls how many blank rows will be added when the New icon is clicked on the Ticket Items grid. This field is always editable from the record view. Linked Database Field: ERPx_APTransactionClass.RowsToCreateOnNew |
| Ticket Class | A hyperlink that shows the value of the 'Ticket Class' property on the Ticket Class record. Clicking on the link opens the record view for the selected Ticket Class. This defaults to blank for new records and is required. If not assigned, the message "Transaction Class is required." will be displayed on Save. This value must be unique. If not, the message "No Duplicate Transactions ID values allowed." will be displayed on Save. This field is always editable and must be <= 50 characters. Linked Database Field: ERPx_APTransactionClass.TransactionClassID |
Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.