NorthScope ver. 2.8.6

Release Date: June 5, 2015

New Features

Purchasing

NS-341: Delivery Tickets – Added the “Sold-to” Conditions Code

Added a new Ticket Item property to specify the “Sold-to” condition code. This value is sometimes required by the ADF&G, so it was necessary to add it. In instances where the sold-to condition is not required, users can enter a blank condition code (Code 00).

NS-376: Default Condition Preferences

Users can now assign a default preference for “Sold To” condition codes. This will reduce time spent assigning condition codes for each line item in a delivery ticket.

NS-342: Delivery Tickets – Added Comment Codes and Comments for Ticket Items

Users can now assign comment codes and comments to ticket line items associated with discards and tagged fish. This is only used for specific types of dispositions per ADF&G. The drop-down for comment codes contains codes from eLandings.

NS-370: Download Tickets and Landing Numbers from eLandings to NorthScope

From NorthScope, you can now independently download ranges of Landing Numbers or Ticket Numbers. If you download ticket numbers, you must specify whether they are for salmon, crab, or groundfish.

NS-371: eLandings Accounts for NorthScope Users

NorthScope can now store eLandings user names and passwords in user accounts. With this feature, a NorthScope user may utilize all eLandings integration features using their own unique eLandings user name and password.

NS-372: Auto-Assigned Ticket Numbers

This new feature adds the capability for eLandings-managed tickets that are entered manually to get their ticket and landing numbers from numbers downloaded directly from eLandings.

NOTE: This feature must be configured by NLP Support. To begin using this feature, contact NLP support and schedule a set-up appointment.

NS-373: Download Tickets from eLandings

With this feature, users can download a single ticket or a batch of tickets (tender batch).NOTE: In order to run this process the NorthScope user must have an assigned eLandings User Name and Password associated with their NorthScope user profile.

NS-374: Upload Tickets from NorthScope to eLandings

Users can now upload delivery tickets directly to eLandings. This feature only applies to tickets within “Ticket Classes” that are configured for eLandings integration. Tickets can be manually uploaded or can be auto-uploaded when they are set to a status of “Ready to Post”.

NOTE: This feature must be configured by NLP Support. To begin using this feature, contact NLP support and schedule a set-up appointment.

NS-391: Added a new Sales Transaction Detail Inquiry

Added a new inquiry to allow users a single place to analyze all of their sales. This includes the detail lines for Customer, Employee, and Fisherman sale transactions, as well as all “Sales” line types from Tender Sale transactions. Transfer lines on Tender Sales are not included.

Enhancements

Purchasing

NS-353: Ticket Item Reprice

Prior to this change, the selection part of the Ticket Item Reprice was timing out in companies with large amounts of ticket history. The selection portion of the reprice was re-written to improve efficiency.

NS-307: Update to the Mass Hire Worksheet

Fixed an issue that allowed employee ID’s to be created with an apostrophe. This was necessary because apostrophes were causing problems during searches and on some reports.

NS-364 – Deliveries by Specie & Product Report

The report has been modified so that the name that prints at the top of the report matches its name.

Added selection criteria for Disposition and included them as a multi select Combo Box. The combo box list contains all active Disposition codes (ID - Name) sorted alphabetically. The transactions on the report will only include the disposition codes selected. The default of this combo box is “60 – Sold”.

NS-365 – Deliveries by Ticket Class Report

The report has been modified so that the name that prints at the top of the report matches its name.

Added selection criteria for Disposition and included them as a multi select Combo Box. The combo box list contains all active Disposition codes (ID - Name) sorted alphabetically. The transactions on the report will only include the disposition codes selected. The default of this combo box is “60 – Sold”.

NS-367, 368: Purchase Order & Customer/Employee Sale Reports

Several cosmetic changes have been added to the reports, including the ability to print the company logo on them. Reports now also print 3 copies (File, Customer, and Original).

NS-369: Specify Default Number of Blank Lines in Delivery Tickets by Ticket Class

This enhancement allows users to specify the default number of blank rows in each ticket class during configuration. Prior to this enhancement, all tickets defaulted to 5 blank lines.

NOTE: This feature must be configured by NLP Support. To begin using this feature, contact NLP support and schedule an appointment.

NS-379: Fisherman Settlement Checks

On the check portion of the document, moved the Pay line (both the text and numeric amounts) up one line so that they do not show in the window of the envelope. One the stub portion of the document, changed the Vendor value to be the Vendor Name instead of the ID. This required moving the Vendor up to be on its own line.

System

NS-378: NorthScope Application Version Location & Format

NorthScope’s application version will no longer be located on the User Login page. The current application version will now be located in NorthScope’s System module, in the “About” page.

In addition, the format of NorthScope’s version numbers is changing. Instead of a “X.Y.Z” display format, it will now be displayed in a date format “YYYYMMDD.x”. The .x will signify if there are more than one released versions in any one day. This change was made to match NorthScope’s database version tracking.

Fixes

Purchasing

NS-336: Auto-Application of Payments

This fix corrected an error caused when a writing a new check to a fisherman when a previous check written to the same fisherman was voided. 

NS-338: Delivery Ticket Decimal Places

The display of decimal places for the Price column is now consistent at 4 decimal places for both the Ticket Record View, Item Re-price, and Premium Re-price screens.

NS-343: Blank Settlement Checks

In some instances, settlement checks for some vendors would be blank. This was caused because the vendor record did not have an address ID assigned as the primary address.

A fix was added so that when new vendors are created, a primary address ID is automatically added.

NS-344: Customer Record for Employee

A bug has been fixed that prevented employees with no payroll history from being removed from the NorthScope database after a user deletes them in Microsoft Dynamics® GP.

NS-345: Duplicate Journal Entries for Employee Sales

A bug has been fixed that created identical, duplicate journal entries for employee sales whenever a user double-clicked the “Save” icon.

NS-346: Employee Sales Ensuring Employees are set to Allow Arrears Deductions

If an employee was not set up to allow arrears deductions, and an employee sale is recorded for that employee, then the employee will be corrected to allow arrears deductions.

NS-360: Settlement Check Batches

This fix corrected an issue where newly written checks were being added to previously printed check batches. Now, newly created checks are only added to batches that have not yet been printed.

NS-389: Saving New Employee Sales as “Ready to Post”

This fix corrected an integration error when users tried to input employee sales directly into a “Ready to Post” status. Before this fix, users had to create new employee sales, save as “New”, then open the record again to save it as “Ready to Post”.

Financial

NS-347: Manual Journal Entries can be created as “Ready to Post”

Prior to this fix, new journal entries were required to be saved with a status of “New” before they could be changed to “Ready to Post”. Now, journal entries can be created and saved with any status.

Sales Order

NS-363: Fixed Issue with Customer Favorites Not Updating Correctly

Customer favorites are now being updated correctly based on the module preferences.