A Tender resale is a transaction used to record sales transactions made between Tenders and Fishermen. These may include line items that the Tender owns and/or line items that the company owns. Line items for Tender owned products create a balance transfer event between the Tender and Fisherman. They have no financial impact on the company and show up on the Fisherman Statement for both the Tender and Fisherman. Line items for Company owned products create a sale between the company and fisherman. These line items only show on the Fisherman Statement for the Fisherman and can be settled against Fish Ticket balances. The purpose of this page is to view, add, edit, remove, and post individual Tender Resale transactions.

Software Version: 2023.09.15 and newer

Page Header

Header Toolbar

Toolbar Icons	Description
Delete	Deletes the transaction or master file record. When clicked, users will be prompted with: "Are you sure you want to delete this record?". Click "OK" to confirm, or "Cancel" to return without deleting. _{WARNING: Records cannot be recovered once they are deleted!}
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.
Journal Details	Opens the Journal Details window showing the Journal Entry for this transaction. Until the transaction Approved or Posted, this is a temporary journal entry so no Journal ID will be assigned.
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.
New	Allows users to select the type of transaction or record they want to add. The list contains: Fisherman Sale: A Fisherman Sale is a transaction used to record sales from the company to a Fisherman or Tender. These transactions can be settled against Fish Ticket balances. Tender Resale: A Tender resale is a transaction used to record sales transactions made between Tenders and Fishermen. These may include line items that the Tender owns and/or line items that the company owns. Line items for Tender owned products create a balance transfer event between the Tender and Fisherman. They have no financial impact on the company and show up on the Fisherman Statement for both the Tender and Fisherman. Line items for Company owned products create a sale between the company and fisherman. These line items only show on the Fisherman Statement for the Fisherman and can be settled against Fish Ticket balances.
Notes	Opens the Notes dialog, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the record. This icon is always enabled.
Print	Opens the Print dialog, showing any applicable printable reports to be printed, downloaded, and/or emailed.
Save	Saves the changes made to the record. It is only necessary to click the Save button when a change is detected on the page. When a change has been made, a ‘ + ‘ character is displayed prior to the page name in the page title bar (light blue bar in the upper left corner of the page). Clicking Save reloads the page.

Home Tab

Fields	Description
Date	Identifies the date of the transaction. This is a text box that defaults to today's date. It is required and if missing, the message "Doc Date is required." will be displayed on Save. This is always editable while in a status of New. Database Field: ERPx_APTransactionHeader.TransactionDate
Doc No	Identifies the Doc No (document number) for the transaction. Unlike a Transaction ID that is system assigned based on the Transaction Class of the Transaction Type, this is a manually entered value. This is a text box that defaults to blank. This field is not required, but if entered, it must be <= 50 characters. The Doc No value must be unique by transaction type. No two Fisherman Sale or Tender Resale Doc No values may be the same, else the message "Duplicate Doc No's are not allowed. Please enter a valid Doc No." will be displayed on Save. This field is always editable. Database Field: ERPx_APTransactionHeader.DocNumber
Fisherman	Identifies the name of the Fisherman, Fisherman & Tender or Tender associated with the transaction. This is a single-select standard lookup that identifies the fisherman for the transfer. This defaults to blank and is required. If missing, the message "Fisherman is required." will be displayed on Save. This field can only be edited while the transaction is set to a Status of New. The transaction cannot be Approved or Posted with the same Tender and Fisherman if there is a Transfer line item included on the transaction. Else, the message "You cannot Approve or Post a Tender Resale with the same Tender and Fisherman with a Transfer Line." will be displayed on Save. A Fisherman is an Account Type used to identify someone that catches fish and sells them to a processing facility. A Tender is a vessel that is attendant to other vessels and is used to transport or ferry unprocessed fish or shellfish received from another vessel to a shoreside processor or mothership. Tender vessels operate, in most circumstances, as an agent for a specific processor and take deliveries from harvesting vessels. A Fisherman & Tender is an Account Type used to identify someone that catches fish during one season and provides Tendering services during another. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Fishermen, Fishermen & Tenders, and Tenders that have not been excluded from the "Tender Resale" Transaction on the 'Excluded Transaction' tab of the Fisherman & Tender Record View. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK
Price List	Identifies the ID and Description of the Price List that is assigned to the transaction. This is a single-select standard lookup that is not required. This field is only enabled once a Fisherman is saved to the transaction. This defaults to blank. If a Fisherman Sale Price List exists, then it will default to the Fisherman Sale Price List associated with the selected Fisherman. If changed, the message "On Save, do you want to update existing prices of items found on the new Price List?" will be displayed. This field can only be edited while the transaction is set to a Status of New. Price Lists are used to store a group of Items with pre-defined prices and effective dates. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Fisherman Sale Price Lists. Database Fields: ERPx_MFPriceListHeader.PriceListID, ERPx_APTransactionHeader.PriceListHeaderSK
Sale Amount	Identifies the sum of all the sale line items (items owned by the company) on the transaction. This is a non-editable text box that defaults to "0.00". This field is auto calculated on Save by adding the 'Extended' column for all sale line items and any associated taxes. It is required and is never editable by the user. This value is not stored in a database field.
Status	Identifies the Status of the transaction. This is a single-select standard lookup that defaults as 'New' and is required. This is always editable while the transaction is in a Status of 'New' or 'Approved'. Status is used to identify where a transaction, Purchase Order, Price List, BOM, or Master File record is in its life cycle. Records start in a Status of 'New' and progress sequentially through additional statuses until they are 'Posted' or 'Closed'. The list of potential Statuses changes depending on the transaction type. The Statuses that apply to transactions in this List View include: New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist. Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned. Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled with the exception any fields that are always editable and updates the Transaction Status to "Posted". Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APTransactionHeader.TransactionStatusSK
Tax Class	Identifies the Tax Class that is assigned to the transaction. This is a single-select standard lookup that is not required. This field is only editable if the fisherman accounting preference for 'Enable Sales Tax on Tender Resles' is set to "Yes". If the user selected a Tax Class that shares the same currency as the Fisherman's Tax Class, then that Tax Class will remain selected. If the user selected a Tax Class that does not share the same currency as the Fisherman or did not select a Tax Class at all, this field will default to select the Tax Class selected on the Fisherman's record view Properties tab for 'Tax Class'. This field can only be edited while the transaction is set to a Status of New. Tax Classes store all the Tax Details (individual taxes) used to calculate sales tax on Quick Sales, Fisherman Sales, and Tender Resale transactions. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Tax Classes. Database Fields: ERPx_MFTaxClass.TaxClassName, ERPx_APTransactionHeader.TaxClassSK
Tender	Identifies the Tender associated with the transaction. This is a single-select standard lookup that is required. If missing, the message "Tender is required." will be displayed on Save. This field can only be edited while the transaction is set to a Status of New. The transaction cannot be Approved or Posted with the same Tender and Fisherman if there is a Transfer line item included on the transaction. Else, the message "You cannot Approve or Post a Tender Resale with the same Tender and Fisherman with a Transfer Line." will be displayed on Save. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Accounts with a Vendor Class of either Fishermen & Tender or Tender. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.FromVendorSK
Transfer Amount	Identifies the sum of all the transfer line items (items owned by the Tender) on the transaction. This is a non-editable text box that defaults to "0.00". This field is auto calculated on Save by adding the 'Extended' column for all transfer line items. It is required and is never editable by the user. This value is not stored in a database field.

Properties Tab

Fields	Description
Created By	Identifies the name of the user that created the record. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. Database Field: ERPx_APTransactionHeader.CreatedBy
Created Date	Identifies the Created Date & Time of the record, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. Database Field: ERPx_APTransactionHeader.CreatedDate
Currency ID	Identifies the Currency assigned to the transaction. This is a non-editable text box that defaults from the Currency assigned to the selected Fisherman. This is required and not editable from this page. Even though this field is required, it is currently for information only and does not drive any functionality. The Currency identifies the kind of money used for transactions. For example, if a Customer or Vendor is setup with a Currency of "USD" then all transactions for them are stated in terms of US Dollars and all payments received or made must be in US Dollars. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Company Currencies. Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_APTransactionHeader.CurrencySK
Fisherman ID	Identifies the ID of the Fisherman, Fisherman & Tender or Tender associated with the transaction. This is a non-editable text box that defaults as the ID of the selected Fisherman. This is required and only editable by changing the Fisherman assigned to the transaction. Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.VendorSK
GL Date	Identifies the date the transaction posted (or will post) to the general ledger. This is an editable date picker that defaults as blank and is required. If not manually edited, will be automatically set to match the 'Date' value in the Home tab when the transaction is saved with a Status of either Approved or Ready to Post. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionHeader.GLDate
Last Updated	Identifies the Last Updated Date & Time of the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. Database Field: ERPx_APTransactionHeader.LastUpdated
Last User	Identifies the name of the user that last updated the Transaction. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user. Database Field: ERPx_APTransactionHeader.LastUser
Posted Date	Identifies the Date & Time the transaction was posted. This is a non-editable text box that defaults to blank and is populated at the time the transaction is posted. This is not required and not editable from this page. Database Field: ERPx_APTransactionHeader.PostedDate
Tender ID	Identifies the ID of the Tender account that is assigned to the transaction. This is a non-editable text box that defaults as the ID of the selected Tender. This is required and only editable by changing the Tender assigned to the transaction. A Tender is a vessel that is attendant to other vessels and is used to transport or ferry unprocessed fish or shellfish received from another vessel to a shoreside processor or mothership. Tender vessels operate, in most circumstances, as an agent for a specific processor and take deliveries from harvesting vessels. Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.FromVendorSK
Transaction Class	The unique identifier of the Transaction Class. This is a non-editable text box that is required and defaults as 'Default'. This is not editable. Transaction Classes are used to differentiate transactions within a Transaction Type. For example, Transaction Classes of Fresh and Frozen can be setup for the Transaction Type of 'Sales Order'. Transaction Classes are used in all functional areas throughout the application. Database Fields: ERPx_APTransactionClass.TransactionClassDescription, ERPx_APTransactionHeader.TransactionClassSK
Transaction SK	Identifies the SK value of the transaction. This is a non-editable text box that is system generated, required and is not editable. Database Field: ERPx_APTransactionHeader.TransactionHeaderSK

Attributes Tab

Fields	Description
Attributes	A non editable text box that shows the name of the Attribute. Attributes are user-definable fields that are used on master files and transactions and are editable from the Attributes List View. The Attribute will only be displayed if the Applies property on the Assign Attribute Rules by page is set to either "Yes - Required" or "Yes - Not Required". Attributes set to "No" will not be displayed. The Attributes displayed here are setup and assigned in the Attributes section of the Company module (Company → Setup → Attributes → Fisherman).
Available	A non editable text box that shows whether the Attribute Value is required or not. If the Attribute Value is required it will display "Yes - Required" if it is optional it will display "Yes - Not Required". This value is only editable from the 'Assign Attribute Rules' page (Company → Setup → Attributes → Fisherman → Transactions hyperlink).
Value	Identifies the value assigned to the corresponding attribute. Because Attributes are configurable as either Text, List, Date, or Date/Time the data entry is either a text box, lookup, or date picker. The value defaults to blank and is only required if the Attribute's 'Applies' property is set to "Yes - Required" in the Assign Attribute Rules page. Attribute Values for Master Flies are always editable. Attribute Values for transactions are always editable for unposted transactions.

Page Detail

Items Grid

The purpose of the Items grid is to add, edit and delete the line items for the Invoice and Credit Memo transaction.

Fields	Description
Toolbar Icons	Description
Delete	Deletes the selected line(s) from the transaction or master file. This icon is only enabled for transactions with a Status of 'New'.
Excel	Exports the contents of the grid to an Excel file that will automatically download. The contents that export are those that are visible to the user. Therefore, if the user has filtered the view only the filtered contents will be exported.
New	Adds new blank lines in the grid section to allow for data entry.
Checkbox	Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Description	Identifies the Description for the line item. This is a text box that defaults to blank, but auto-populates once an Item is selected from the Item drop-down menu. This field is required and must be <= 200 characters. If missing, the message "A Description is required for all line items." will be displayed on Save. This field is always editable while the transaction is in a Status of New or Approved. Database Field: ERPx_APTransactionLine.LineDescription
Extended	Identifies the Extended amount of the line item. This is a non-editable text box lookup that defaults as "0.00" and is required. This can only be edited by changing the Quantity and/or Price of the transaction line. It is calculated as [Quantity of line item] * [Price of line item]. Database Field: ERPx_APTransactionLine.ExtendedAmount
Item	Identifies the Item, displayed as Item ID: Item Description. This is a single-select standard lookup that defaults to blank. It is required and is always editable while in a Status of New. Item IDs are the unique identifier for Items. The lookup contains a blank value, the current assigned value, "Transfer" for balance transfers, and a list of all the 'Active' Items in the Item Master File. Database Fields: ERPx_IMItem.ItemID, ERPx_IMItemItemDescription, ERPx_APTransactionLine.ItemSK
Price	Identifies the price of the line item. This is a text box that defaults as "0.00" and is required to be > 0. If not, the message "Price is required and must be greater than zero." will be displayed on Save. The number of decimals follows the corresponding Item's Price decimal value. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionLine.Price
Purchase Account	Identifies the GL Account that will be Credited on a sale or Debited on a sales return. This is a single-select stand lookup defaults from the Item's Sales account. It is required for any non-transfers and if missing, the message "A Purchase Account is required for all sale lines." will be displayed on Save. This is always editable while in a Status of new. The GL Account that is assigned for the "Sales" Account Type, on the Accounts tab of the Item Record View and Item Class Record View. The Sale Account identifies the revenue account that sale transactions post to. This lookup contains a blank value, the current assigned value, and all active GL Accounts with a 'Control Account Type' of "Sales" and the 'Use In SO' property set to "Yes". Database Fields: ERPx_GLAccount.AccountNumber, ERPx_GLAccount.Description, ERPx_APTransactionLine.AccountSK
Quantity	Identifies the quantity of the line item.This is a text box that defaults as "1.00" and is required. The number of decimals follows the corresponding Item's Units / Weight decimal value(s), and is displayed after saving an item. For sales lines, the value entered in this field can be negative or positive to record both sales and returns. For transfer lines, the value entered in this field can only be positive. If not, the message "Quantity is required and must be greater than zero for transfer lines." will be displayed on Save. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionLine.Quantity
UOM	Identifies the unit of measure that the items are stored in (Lbs, kgs, Cases, etc.) on the transaction. This is a single-select standard lookup that defaults as blank and is not required. Once an Item is selected, this field defaults to the Item UOM default. This is always editable while the transaction is in a Status of New. A UOM is a quantity used as a standard of measurement. It identifies how much makes up "1" of the measurement. Examples include Bag, Box, Each, Kg, Lb, ext. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Units of Measure. Database Fields: ERPx_IMUOM.UOMID, ERPx_APTransactionLine.QuantityUOMSK