NorthScope 2019.03.01

Owned by Emma Greenwood
Last updated: Mar 04, 2019
6 min read

(Software Version: 2019.02.22 Database Version: 2019.03.01)

Release Date: March 01, 2019


New Feature

Fisherman Accounting

NS-3973 & NS-4094 Added functionality at the Ticket Class level so users can configure how Fish Tickets are imported from eLandings

Prior to this release, all the rules for how Fish Tickets imported from eLandings were system controlled and were the same across all Ticket Classes. In most cases, NorthScope self-healed setup data when tickets were imported. For example; if an existing Fisherman was missing a Permit or a Ticket Item had not been setup, or a ticket contained a new Vessel they were automatically added. However, not all missing master file data was auto-added which caused confusion. Additionally, some plants do not want master file data auto-added or may want to control when master file data is auto-added. 

With this release, users can now configure each Ticket Class as to whether they will allow Fish Tickets to import if they contain missing or inactive:

  • Fishermen (CFEC Permit Holders) <-- Fishermen can now be auto-added from eLandings
  • Fish Ticket Items and their Components (Specie, Conditions, Dispositions, and Grades)
  • Fishermen Permits
  • Chill Types
  • Gear Codes
  • Management Programs
  • Ports
  • Stat Areas
  • Vessels

To accomplish this, new properties were added to the ADFG Group on the Ticket Class record view:

  • Allow Import of Missing or Inactive Fishermen
  • Allow Import of Missing or Inactive Permits
  • Allow Import of Missing or Inactive Fish Ticket Items and Components
    • This includes Fish Ticket Items and their Components.  Components include Specie, Conditions, Dispositions, and Grades.
  • Allow Import of Missing or Inactive Chill Types
  • Allow Import of Missing or Inactive Gears
  • Allow Import of Missing or Inactive Management Programs
  • Allow Import of Missing or Inactive Ports
  • Allow Import of Missing or Inactive Stat Areas
  • Allow Import of Missing or Inactive Vessels

This allows users to specify which ticket properties they want auto-added when importing new tickets. Each of these properties contains a Yes/No option and each new property defaults to “Yes” except for “Allow Import of Missing or Inactive Fisherman” which defaults to “No”.

This section describes how NorthScope works if your Ticket Class is set to “Allow Import of Missing or Inactive Fishermen”.

  • There are 3 new Preferences that control how new Fishermen get added in NorthScope:
    • Default Fisherman Vendor Class – This preference value is required if you want Fishermen auto-added.
    • Default Fisherman Payment Terms – If blank, the Payment Terms will be set from the Vendor Class otherwise the Payment Terms will come from this preference.
      • This value is only required if the ‘Default Fishermen Vendor Class’ does not contain default Payment Terms. 
    • Default Fisherman Attribute Class – This preference value is optional.
  • Fishermen properties will be assigned as follows:
    • Fishermen ID – First 3 characters of the fisherman last name + First 3 characters of the fisherman first name + first 2 of the middle name
    • Fisherman Name – Last Name, First Name
    • Payment Terms – From the Vendor Class otherwise the Preference
    • Vendor Class – From the Default Fisherman Vendor Class Preference
    • Settlement Accrual Account – From the Vendor Class
    • Checkbook – From the Vendor Class otherwise from the preference ‘Default Fisherman Checkbook ID’
    • Tax Type - Blank
    • 1099 Type - Blank
    • Attribute Class – From the Default Fisherman Attribute Class Preference
    • On Hold - No
    • Inactive – No
    • Currency – From the Vendor Class otherwise company default
    • Vendor Type – Fisherman
    • Check Name – Fisherman First Name + Last Name
    • CFECID – From eLandings
  • Fisherman Addresses will be added as follows
    • Address ID – PRIMARY
    • Check Name - Fisherman First Name + Last Name
    • Address 1 – Blank
    • Address 2 – Blank
    • City – Blank
    • State – Blank
    • Zip - Blank
    • Phone – Blank
    • Email - Blank
    • Check Default – Yes
    • Check Description - Blank


NS-4076 Added a new Fish Ticket property called “Fishing Period”

Before this change, Fish Tickets that contained a “Fishing Period” in eLandings where integrating that value to the “Season” property in NorthScope. A new property for “Fishing Period” has been added and this property is now populated from eLandings and/or can be manually updated. The “Season” property will no longer be populated from this value, so users can now use both values.

Fishing Period has been added to the following:

  • Fish Ticket Record View Properties (Group 6)
  • Ticket List View
  • Ticket Lines List View
  • Tickets Inquiry
  • Ticket Line Inquiry

Inventory

NS-4101 Added the ability to Correct Posted Inventory Transactions  

A new “Correct” only feature was added to the Void/Correct page Action dropdown to enable users to correct posted inventory transactions.   Processing a correction for an inventory transaction from the Void/Correct page will create a new record and a new transaction ID is created.  The correction record view has a new header field called “Corrected From” which displays the Transaction ID that the correction is being made from and is for information only.  A new header toolbar icon called “Process Correction” was added and when clicked will update the transaction with the changes made by the user. The changes displayed will be the difference between the original and the new transaction, for example if the original transaction contained a line item with 100 units and the correction transaction was updated to 90 units, after clicking "Process Correction" a line item of –10 units will be displayed. The Status and Site are disabled until the “Process Correction” button is clicked, the Status is updated to Approved and enabled for the user to post the transaction.  Users can make any edits to the transaction prior to clicking the “Process Correction” button, once this button is clicked "Process Correction" is disabled.    

A new drop-down called “Override Negative Balances” was added to the Void/Correct page and contains the values “Match Trans”, “Allowed”, “Not Allowed”.  This field defaults to Match Trans and allows the user to override the Transaction property “Negative Available Balances” on the newly created transaction record.  

A new property called “Single Date Management” was added to the Inventory Transaction Class, this field is a drop-down menu with the values Yes or No and defaults to No.  If set to Yes, the GL Date on the Transaction Record View will be disabled and will always follow the transaction date. 

Improvements 

Fisherman Accounting

NS-4076 Updated how “Sold Condition” is populated from eLandings

“Sold Condition” now defaults from the “Condition” code of the line item if no value is provided from eLandings. Before this change it defaulted from a preference.


NS-4133 Renamed the Master Fisherman Account property on the Vendor Record View

The “Master Fisherman Account” property has been renamed to “Alternate Paid Account” on the Record View for Fisherman and Fisherman & Tenders. This change was made to more accurately describe the function of this property which is to override the Paid Fisherman for a Fish Ticket. The Vendor List View and the File Import for Vendors were also updated to reflect this change. 

To be consistent throughout the application, the “Paid Fisherman” and “Fisherman Account” columns have been renamed to “Paid Account” in the following Record View, List Views, and Inquiries: 

  • Ticket Record View – field renamed from “Paid Fisherman” to “Paid Account”
  • Tickets List View – column renamed from “Paid Fisherman” to “Paid Account”
  • Ticket Lines List View – column renamed from “Paid Fisherman” to “Paid Account”
  • Tickets Inquiry – column renamed from “Paid Fisherman” to “Paid Account”
  • Ticket Lines Inquiry – column renamed from “Paid Fisherman” to “Paid Account”
  • Ticket Stat Area List Inquiry – column renamed from “Fisherman Account” to “Paid Account” 

Bug Fixes

Financial

NS-4130 Fixed an issue with Fiscal Period Integration

If the Fiscal Period Outbound Integration setting is set to "Immediate" or "Timed", there was an issue with closing fiscal periods in Dynamics GP which was fixed.

Inventory

NS-4170 Fixed an issue with multi-page Inventory Transfer Transactions 

Previously, on Transfers that contained more than 25-line items, if a user changed the Via or To Site prior to posting not all line items were updated correctly.  

Technical Changes

Schema Changes

ALTER TABLE [dbo].[ERPx_APTransactionClass] ADD [AllowMissingOrInactiveFishermanImport] [bit] NOT NULL DEFAULT ((0))

ALTER TABLE [dbo].[ERPx_APTransactionClass] ADD [AllowMissingOrInactivePermitImport] [bit] NOT NULL DEFAULT ((1))

ALTER TABLE [dbo].[ERPx_APTransactionClass] ADD [AllowMissingOrInactiveFishTicketItemAndComponentImport] [bit] NOT NULL DEFAULT ((1))

ALTER TABLE [dbo].[ERPx_APTransactionClass] ADD [AllowMissingOrInactiveChillTypeImport] [bit] NOT NULL DEFAULT ((1))

ALTER TABLE [dbo].[ERPx_APTransactionClass] ADD [AllowMissingOrInactiveGearImport] [bit] NOT NULL DEFAULT ((1))

ALTER TABLE [dbo].[ERPx_APTransactionClass] ADD [AllowMissingOrInactiveManagementProgramImport] [bit] NOT NULL DEFAULT ((1))

ALTER TABLE [dbo].[ERPx_APTransactionClass] ADD [AllowMissingOrInactivePortImport] [bit] NOT NULL DEFAULT ((1))

ALTER TABLE [dbo].[ERPx_APTransactionClass] ADD [AllowMissingOrInactiveStatAreaImport] [bit] NOT NULL DEFAULT ((1))

ALTER TABLE [dbo].[ERPx_APTransactionClass] ADD [AllowMissingOrInactiveVesselImport] [bit] NOT NULL DEFAULT ((1))

ALTER TABLE [dbo].[ERPx_APDeliveryTicketHeader] ADD [FishingPeriod] [varchar] (20) NULL

ALTER TABLE [dbo].[ERPx_APVendor] ADD [PaidFishermanVendorSK] BIGINT NULL

ALTER TABLE [dbo].[ERPx_APVendor] ADD CONSTRAINT [FK_ERPx_APVendor_ERPx_APVendor] FOREIGN KEY ([PaidFishermanVendorSK]) REFERENCES [dbo].[ERPx_APVendor] ([VendorSK])

ALTER TABLE [dbo].[ERPx_APVendor] DROP COLUMN [MasterVendorSK]

ALTER TABLE [dbo].[ERPx_ARCustomer] ALTER COLUMN [CurrencyID] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL

ALTER TABLE [dbo].[ERPx_IMTransactionClass] ADD [SingleDateManagement] BIT NOT NULL DEFAULT(0)

ALTER TABLE [dbo].[ERPx_IMTransactionDetail] ADD [CorrectedFromTransactionDetailSK] [bigint] NULL

ALTER TABLE [dbo].[ERPx_IMTransactionDetail] ADD CONSTRAINT [FK_ERPx_IMTransactionDetail_ERPx_IMTransactionDetail] FOREIGN KEY ([CorrectedFromTransactionDetailSK]) REFERENCES [dbo].[ERPx_IMTransactionDetail] ([TransactionDetailSK])

ALTER TABLE [dbo].[ERPx_IMTransactionHeader] ADD [IsCorrectionComplete] [BIT] NOT NULL DEFAULT(0)

ALTER TABLE [dbo].[ERPx_IMTransactionMoreActionsCriteria] ADD [OverrideNegativeBalancesEN] INT NULL

ALTER TABLE [dbo].[ERPx_SOOrderHeader] ALTER COLUMN [CurrencySK] [bigint] NOT NULL