Sites List View: Fisherman Accounting
- Tatum Garino (Unlicensed)
- Janice Dannenberg (Unlicensed)
- Tom Williams
Sites represent Plants, Warehouses, Distribution Centers, or any other object that manages inventory balances. They are used in Fisherman Accounting to record the location the fish were delivered to (and processed). Sites can also be used as criteria in setting up Fish Ticket Taxes and Fish Ticket Premiums. The purpose of this page is to add, edit, remove, and activate/inactive these records.
This list view also contains columns for each 'Lot Certification' with a certification 'Type' of "Item & Site" or Site Only". Because these are user defined, they are not included in the default view but can be added a saved layout.
Software Version: 2019.11.08 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 | Puts the list view in edit mode allowing all editable fields to be modified at one time. To get out of edit mode you must either Cancel or Save your changes. |
| 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. |
| Auto Generate Warehouse Lots By | Identifies how Warehouse Lot Numbers are auto-generated for applicable transfer line items. This is not visible for new Sites and is only required and editable for Sites where the following conditions are both true:
If these conditions are true and the value is missing, the message "[SiteID] has the "Auto Generate Warehouse Lots on Transfer Receipts" option turned on but is missing a selection for "Auto Generate Warehouse Lots by"" will be displayed on Save. When this feature is enabled for the 'To Site' (the receiving Site) on an inventory Transfer transaction, the system will automatically populate the warehouse lot values in the 'To Warehouse Lot' , on Save. The values will be populated as either:
Linked Database Field: ERPx_MFSite.WarehouseLotTemplate This lookup contains all the values in the WarehouseLotTemplateEN Enumeration Class. |
| Auto Generate Warehouse Lots on Transfer Receipts | Identifies whether or not the Warehouse Lot Numbers are auto-generated for applicable transfer line items. This is only visible for Sites where the 'Warehouse Lot Tracked' property is set to either: "Yes - Allow multiple items in single lots" or "Yes - Limit Warehouse Lots to single items". This value is required if the Site is warehouse lot tracked and there is a value in the "Auto Generate Warehouse Lots By" property. If these conditions are true and the value is missing, the message "Unable to set "Auto Generate Warehouse Lots By" if "Auto Generate Warehouse Lots on Transfer Receipts" is not enabled on Save. When this feature is enabled for the 'To Site' (the receiving Site) on an inventory Transfer transaction, the system will automatically populate the warehouse lot values in the 'To Warehouse Lot' , on Save. The values will be populated as either:
Linked Database Field: ERPx_MFSite.AssignWarehouseLotsOnTransferReceipts This lookup contains options for either "Yes" or "No". |
| City | The 'City' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 35 characters. Linked Database Field: ERPx_MFSite.City |
| Country | The 'Country' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 50 characters. Linked Database Field: ERPx_MFSite.Country |
| Default Via Site for Integrated Transfers | Identifies the "In Transit Site" that will be auto assigned to imported Transfer transactions where the current site is listed as the 'To Site' (the receiving Site). As a result, a one part transfer transaction will import as a two part transfer. This is typically assigned when:
It is not required and always editable but is only visible, and applicable for non In-Transit Sites (Sites with the 'In Transit' property set to "No"). Two-part Transfers provide a way to deduct on-hand inventory from the 'From Site' (the sending site) before receiving it into the 'To Site' (the receiving Site). This is useful when transfers cannot be physically shipped and received at the same time, or when companies need to manage variances between what was actually shipped and actually received. This is accomplished by creating two separate, but linked, transfer transactions: 1) a one-part transfer that, when posted, moves on-hand balances from the 'From Site' (the sending site) to the 'Ship Via' (the in-transit site) and then creates a linked, un-posted transfer receipt transaction to move on-hand balances from the 'Ship Via' (the in-transit site) to the 'To Site' (the receiving Site). This allows the sending Site to deduct what they actually sent, the receiving Site to receive what they actually received, and any discrepancies to be reflected in the in transit Site. Linked Database Field: ERPx_MFSite.IntegratedTransferDefaultViaSiteSK |
The 'Email' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 50 characters. Linked Database Field: ERPx_MFSite.Email | |
| Fax | The 'Fax' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 25 characters. Linked Database Field: ERPx_MFSite.Fax |
| In Transit | A Yes/No lookup to identify whether the Site is an "In Transit" Site or not. The value defaults to "No" but can be changed at anytime. A value of "Yes" means that the Site is an "In Transit". In Transit Sites are visible in the In Transit and Ship Via Site look ups and canot be set to 'Visible to Sales'. A value of "No" means that the Site is not and In Transit Site. Linked Database Field: ERPx_MFSite.IsInTransit |
| 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_MFSite.IsInactive |
| Next Prod. Batch # | Identifies the next Production Batch ID that will be used, by an integrated WMS or bar code data collection system, if they are configured to auto generate Production Batches. This defaults to 10000 for new Sites, is not required, is always editable, and must be an integer value. This is only used for imported transactions and does not impact manual data entry. Linked Database Field: ERPx_MFSite.NextProductionBatchNumber |
| Phone | The 'Phone' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 25 characters. Linked Database Field: ERPx_MFSite.Phone1 |
| Prod. Batch Prefix | Identifies a prefix that will be appended to the 'Next Production Batch #, by an integrated WMS or bar code data collection system, if they are configured to auto generate Production Batches. Because the 'Next Production Batch #' is an integer value, there is a possibility more than one Site could use the same number. Using a 'Production Batch Prefix' ensures Production Batch #'s remain unique across multiple production facilities. This does not impact manual data entry. This defaults as '[Site ID]-' for new Sites, is always editable, and must be <= 25 characters. This is only used for imported transactions and does not impact manual data entry. Linked Database Field: ERPx_MFSite.ProductionBatchPrefix |
| Registration | Identifies the Plant's registration number. This is typically an FDA assigned number for US facilities. This defaults to blank for new records, is not required, and can be edited any time, and must be <= 50 characters. This is only used for reports. Linked Database Field: ERPx_MFSite.Registration |
| Site ID | A hyperlink that shows the value of the 'Site ID' property on the Site record. Clicking on the link opens the record view for the selected Site. This defaults to blank for new records and is required. If not assigned, the message "Site ID is required." will be displayed on Save. This value must be unique. If not, the message "Duplicate Site IDs are not allowed." will be displayed on Save. This field is always editable from the record view and must be <= 20 characters. The Site ID is used as a short description and unique identifier of the Site. Linked Database Field: ERPx_MFSite.SiteID |
| Site Name | The 'Site Name' property on the Site record. This defaults to blank for new records and is required but duplicate values are allowed. If not assigned, the message "Site Name is required." will be displayed on Save. This field is always editable from the record view and must be <= 35 characters. The Site Name is used as a long description/name of the Site. Linked Database Field: ERPx_MFSite.SiteName |
| State | The 'State' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 30 characters. Linked Database Field: ERPx_MFSite.State |
| Vendor Name | The 'Vendor name' of the AP Vendor that the Site is associated with. This defaults to blank for new records and is not required. Associating an AP Vendor with a Site is only for informational purposes. Linked Database Field: ERPx_MFSite.VendorSK This lookup contains a blank value, the current assigned value, and a list of all the 'Active' Vendor Accounts with an Account Type of Vendor. |
| Visible to Logistics | A Yes/No lookup to identify whether or not the management of Sales Order shipment data is done within Load Management or from the individual Sales transaction. The value defaults to "No" but can be changed at anytime. If set to Yes: Shipment data for sales transactions that are set to ship from BOTH a Site and Carrier that are visible to logistics, is managed in Load Management and not on the individual Sales transaction. The data is visible on the Sales transaction but not editable. A value of "No" means that all shipment data for sales transactions set to ship from this Site, is managed from the Sales transaction. Linked Database Field: ERPx_MFSite.IsVisibleToLogistics |
| Visible to Sales | A Yes/No lookup to identify whether or not product can be sold from this Site. Some Sites may be used exclusively for production or storage. These Sites would not be visible to Sales. The value defaults to "No" but can be changed at anytime. A value of "Yes" means that the Site will be visible in look-ups for Sales transactions. A value of "No" means that the Site will not be visible in look-ups for Sales transactions. Linked Database Field: ERPx_MFSite.IsVisibleToSales |
| Visible to WMS | A Yes/No lookup to identify whether or not the Site is managed by a WMS or bar code data collection system. The value defaults to "No" but can be changed at anytime. A value of "Yes" means that orders set to ship from these Sites will be visible to the bar code system. A value of "No" means that orders set to ship from these Sites will not be visible to the bar code system. Linked Database Field: ERPx_MFSite.IsVisibleToWMS |
| Warehouse Lot Tracked | Identifies which option is selected in the 'Warehouse Lot Tracked' property on the Site record. The available options include:
This defaults to No for new records but can be edited at any time. Linked Database Field: ERPx_MFSite.IsSiteWarehouseLotTracked This lookup contains all the values in the WarehouseLotTrackedEN Enumeration Class. |
| Zip | The 'Zip' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 15 characters. Linked Database Field: ERPx_MFSite.Zip |