NorthScope 2018.06.08

Owned by Kati Huttunen (Unlicensed)
Jun 08, 2018
4 min read

Release Date: June 08, 2018

PDF Version

New Features

Financial

NS-3330 Added the Ability to Create Reversing Journal Entries

A New feature was added to the Financial Module of NorthScope to allow users to create reversing Journal Entries. When a reversing journal entry is saved as Ready to Post, a reversing journal entry is created in the date the user selected for the reversing date. This journal entry is created with reversed debit and credit amounts. This work item included the following changes:

  • The New toolbar icon on Journal Entry list view and Journal Entry record view was updated to be a split button with Standard and Reversing options.
  • Added a new column 'Journal Type' to the following list views and inquiries:
    • Journal Entries list view
    • Journal Lines list view
    • Journal Entries inquiry
    • Journal Details inquiry

Inventory

NS-3281 Added Mass Update for To Warehouse Lots to the Transfer Transaction

A new feature was added to the Inventory Module to allow users to Mass Update the 'To Warehouse Lots' field to Transfer transactions. A new option 'To Warehouse Lot' was added to the Mass Update tool which allows users to allocate and update multiple line items within a Transfer transaction to the same Warehouse Lot. Users can select or filter the line items that need updating, then apply the Warehouse Lot through the Mass Update toolbar icon.

Purchasing

NS-3300 Added the Ability to Void and Correct Fisherman Sale and Tender Resale Transactions

A new feature was added to NorthScope to allows users to void and correct posted Fisherman Sale and Tender Resale transactions. A new toolbar icon 'More Actions' was added to the Fisherman Sales and Fisherman Sales Lines list views and Fisherman Sale & Tender Resale inquiry. Clicking this toolbar icon displays and option Void/Correct, which opens the Fisherman Sale void/correct page. Transactions can be filtered by the Fisherman name, Transaction ID and/or transaction dates. When a transaction is corrected, the status of the previous version of the transaction is updated to replaced and a new version is saved in a New status. When a transaction is voided, the status of the previous version of the transaction is updated to replaced and a new version is created in void status. Voiding and correcting Fisherman Sale and Tender Resale transactions update the Fisherman Balance accordingly.

Improvements

Financial

NS-3331 Added a New Financial Preference

A new preference 'Retained Earnings GL Account' was added to the Financial module. This preference determines the Retained Earnings Account that is used in the year end closing process. The combo box displays all active GL accounts with 'Retained Earnings' Control Account type. The preference is not required.

Framework

NS-3333 Disabled Textbox Auto Suggest

A setting was changed in the Chrome browser to disable autocomplete in textboxes, numeric textboxes and date picker fields within NorthScope. Browser history and cache must be cleared for this feature to work.

Inventory

NS-3302 Improved UOM Validations on Item Records

The following new validations were added to Item records:

  • [Item] is managed by [Manage Item By Value]. [Units or Weight] UOMs were not saved.
    • This validation message is displayed, if a Units or Weight only managed item is saved with Sales Order or Inventory Weight or Units UOMs.
  • [Item] is managed by [Manage Item By Value]. Default [Price or Reporting] UOM must be a [Unit or Weight] UOM.
    • This validation message is displayed, if the Default Reporting or Default Price UOM is not a UOM the item is managed by.

Purchasing

NS-3312 Added a New GL Date Column to AP Inquiries

A new column 'GL Date' was added to the following Purchasing inquiries:

  • Cash Receipts inquiry
  • Fisherman Sale & Tender Resales inquiry

Sales Order

NS-3321 Improved Sales Order Integration to the Host System on Approved Status

The Sales Order transaction integration to the Host system on Approved status was improved. The Sales Order transaction is now integrated when the transaction status is moved to a new status that integrates to the Host system. Previously the transaction was integrated only when the status was changed to Approved or Ready to Post, but now the transaction is integrated when the transaction is saved as Approved and again when the transaction is saved as Ready to Post. If the transaction is integrated when the transaction status is Approved, the transaction is now automatically placed on hold using a hold code 'NSHold'. The Transaction Class property 'First status invoices are sent to the host system' was also disabled on transaction class records to limit the access to the feature.

System

NS-3286 Updated the Max for Integration Record Purging Preference

Previously, the system preference 'Number of days to purge archived integration records after' allowed a maximum value 90. The preference was updated to allow maximum value 9999.

Bug Fixes

Financial

NS-3237 Fixed Checkbook Next Check Number Saving

Previously, when the next check number of a checkbook was updated, and a new check was processed, the check number reverted back to the previous check number. The issue is now fixed.

Purchasing

NS-3199 Fixed Account and UOM to Default on Tender Resale Transactions

Due to a bug, the UOM and Sale Account fields were not defaulting from the Item record on Tender Resale transaction records. The issue is now fixed.

NS-3332 Fixed Mass Update Date Validation on Fisherman Sales List View

Due to a bug, the Fisherman Sale, Cash Receipt and Tender Resale status was validating fiscal periods against the transaction date instead of the GL date when the transaction status was updated from the list view. The issue is now fixed.

Sales Order

NS-2814 Fixed Sales Order Date Validation when Multiple Transaction Types

Previously, the Sales Order date validations were not working as expected, if multiple different type Sales Order transaction classes were created in the system with the same transaction class ID. The issue occurred, if e.g. Invoice and Order type transactions classes were created with the same name ORD. The issue is now fixed.