The purpose of the Void/Correct Fish Ticket page is to void posted Fish Tickets. Voiding a Fish Ticket creates a new version of the transaction. A new reversing transaction is created using the specified 'Default GL Date'. This reversing transaction also creates a reversing journal entry. The Status of the original Ticket is changed to "Replaced" and the Status of the new Ticket is set to "Void". Only posted Tickets can be voided. When the void is complete, the Fisherman Balances are updated.

Software Version: 2024.10.30 and newer

Page Header

Toolbar Icons	Description
Help	Opens the online WIKI help page for the current page. This icon is only visible on pages that are documented in the online help.
Process	Attempts to process the Void and/or Void & Correct of the source transaction if there are no errors. Successfully voiding or voiding & correcting a Fish Ticket completes the following: Void: Creates a new version of the Ticket that reverses the original line items and quantities. The new transaction is created as follows: Ticket number: Same as the source Transaction with a "vX" (where X represents the next version # of the ticket) appended to indicate it is a new version. GL Date: comes from the 'Default GL Date' specified. Status: Set to Void (the source transaction's status is changed to "Replaced". The new transaction's Journal Entry effectively reverses the original transaction's Journal Entry. Updates the Fisherman Balances. Void & Correct: Creates a new clone of the source transaction (with a new version ID) that can be edited and re-posted from the Fisherman Accounting → Fish Tickets List View. If the transaction is Posted, all the steps outlined above for a Void will also happen. Note: If a user tries to Void/Correct a Fish Ticket that is on an open Settlement Batch will see the following message when the Process button is clicked: "(TicketNumber) is part of an open payment batch and cannot be voided or corrected."
Refresh Data	Refreshes the contents of the grid based on the search criteria specified.
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). The bolded view is the default view, which will determine the view will automatically display in when opened.
Fields	Description
Action	A single select lookup to identify whether the intention is to Void or Correct (Void & Correct) the Fish Ticket. This defaults to blank and is required. The lookup contains the following options: Correct (Void & Correct) Void
Date From	A text box to enter the earliest Date you wish to see Tickets for. This defaults to one year prior to the current date and is required.
Date To	A text box to enter the latest Date you wish to see Tickets for. This defaults to one year prior to the current date and is required.
Default GL Date	A date field to identify the GL Date of the Void or correction. This default to the current date but can be set to any date on or after the transaction's GL Date that falls within a Fiscal Period that is open for Purchasing. This date will be used as the GL Date for the new version of the Ticket. If the Void Date entered is before the GL Date of the source transaction, the message "Cannot supply a void date prior to the transaction's GL Date." will be displayed when the Void icon is clicked. If the Void Date entered falls within a period that is not open for Purchasing, the message "The Fiscal Period is not open." will be displayed when the Void icon is clicked. If you change the Default GL Date, you must click the 'Refresh Data' icon in the header toolbar for the change to take effect.
Delivery #	A text box to identify all or part of the Delivery # pertaining to the Ticket you wish to void. This is not required but if selected it will limit the number of potential tickets returned in the Tickets Grid.
Fisherman	A single select lookup to select the Fisherman you wish to void a Fish Ticket for. This is not required but if selected it will limit the number of potential tickets returned in the Tickets Grid.
Transaction	A text box to identify all or part of the Ticket # you wish to void. This is not required but if selected it will limit the number of potential tickets returned in the Tickets Grid.
Transaction Type	A single select lookup to select the type of transaction being voided. This defaults to "Fish Ticket" and is required. The lookup only contains the option for Fish Ticket.

Tickets Grid

The purpose of the Tickets Grid is to show all the potential Fish Tickets based on the selection criteria specified.

Fields	Description
Checkbox	Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Account ID	A textbox that shows the value of the 'Vendor ID' of the Permit Holder assigned to the Fish Ticket. The Account ID is used as a short description and unique identifier of the Fisherman or Tender account. Database Field: ERPx_APVendor.VendorID
Account Name	A textbox that identifies the owner of the Permit (the fisherman) that was associated with the catch. Database Fields: ERPx_APVendor.VendorSK.VendorName , ERPx_APDeliveryTicketHeader.PermitHolderVendorSK
Amount	Identifies the 'Amount' of the Fish Ticket (net amount owed to the Fisherman). Database Field: ERPx_APDeliveryTicketLine.Amount
Delivery #	A unique number used to group one or more Fish Tickets together. This number is used three different ways: If the ticket was delivered by a Tender, this represents the Tender Batch ID. For manually entered tickets, in Plants that log deliveries in a separate book, this is used to record the number from that book For all other integrated tickets, this represents the Landing # This is required for the transaction to be approved or posted. It can be edited from the 'Delivery #' field on the 'Home' tab of the Fish Ticket Record View. Database Field: ERPx_APDeliveryTicketHeader.DeliveryNumber
Chill Type	Identifies the ID of the chill type. Database Fields: ERPx_APChillType. ChillTypeID, ERPx_APDeliveryTicketHeader.ChillTypeSK
Dock Delivery	A Yes/No value to show if the Ticket was delivered to the Dock. This is required and can be edited from the 'Dock Delivery' field on the 'Home' tab of the Fish Ticket Record View. Database Field: ERPx_APDeliveryTicketHeader.DockDeliveryEN
Floating	Identifies whether or not the fish were "floating" or suspended when they were offloaded. This is a Yes/No lookup that is required. It defaults to "No". This is not required and can be edited from the 'Floating' field on the 'Properties' tab of the Fish Ticket Record View while the transaction is in a Status of New. Floating is a quality field. If the fish are floating, in the water in the fish hold, that indicates they have been in there for a while and are of lower quality. Database Field: ERPx_APDeliveryTicketHeader.Floating
Gear	Identifies the Gear Type for the ticket. Gear is the specific apparatus or equipment used to catch fish or shellfish. A few examples of gear include: longline, pots, beam trawl, and purse seine. This is required and can be edited from the 'Gear' field on the 'Home' tab of the Fish Ticket Record View. Database Fields: ERPx_APGear.GearDescription, ERPx_APVendorPermit.GearSK, ERPx_APDeliveryTicketHeader.VendorPermitSK
GL Date	Identifies the date the transaction posted (or will post) to the general ledger. This is required for the transaction to be approved or posted. It can be edited from the 'GL Date' field on the 'Properties' tab of the Fish Ticket Record View. Database Field: ERPx_APDeliveryTicketHeader.GLDate
Permit Holder	Identifies the owner of the Permit (the fisherman) that was associated with the catch. This is a non-editable text box that is required. It defaults to the Permit Holder assigned the Permit selected on the New Delivery Ticket page. Database Fields: ERPx_APVendor.VendorSK.VendorName , ERPx_APDeliveryTicketHeader.PermitHolderVendorSK
Slide	Identifies whether or not the fish were offloaded using a slide. This is a Yes/No Lookup that is required. It defaults to "No". This is not required and can be edited from the 'Slide' field on the 'Properties' tab of the Fish Ticket Record View while the transaction is in a Status of New. Slide is a quality field that indicates if the fish were transferred from the catcher vessel to the tender using a slide, which reduces handling and associated damage. Database Field: ERPx_APDeliveryTicketHeader.Slide
Trans Date	Identifies the date the catch was delivered to the Plant. This is required and can be edited from the 'Delivered' field on the 'Home' tab of the Fish Ticket Record View.
Transaction	Identifies the Fish Ticket number (aka the Fish Ticket Transaction ID). The Ticket # can be manually assigned or can come from downloaded eLandings ticket numbers. Clicking on the link opens the Fish Ticket Record View for the selected record. This is required and can be edited from the 'Ticket #' field on the 'Home' tab of the Fish Ticket record view while the transaction is in a Status of New. Database Field: ERPx_APDeliveryTicketHeader.TicketNumber
Void/Correct GL Date	Identifies the new GL Date for the Void and Correction.

Page Header

Toolbar Icons

Tickets Grid

Fields

Related Topics

Page Definitions

Technical Details

Browser not supported