(Software Version: 2024.05.xx 20 Database Version: 2024.05.xx20)
Release Date: May xx20, 2024
| Table of Contents |
|---|
New Features
Financial and Purchasing
NS-12032 - Added GL Account Assignments to Journal Entry, Accrue and Reverse, Purchase Orders, AP Invoices & Credit Memos.
NLP knows a good thing when we develop it and we think you’ll like this one, too. We recently added the ability to directly key or search for a GL Account to the Sales Transaction screen and have now added the same features to the Purchase Order and AP Invoice & Credit Memo. Now you can overwrite the default GL accounts for each line item by simply keying in a GL account or search using a partial account number or account descriptionAccount Number. While we were at it, we updated the Journal Entry record view Record View with the same account number search feature, replacing the old account dropdown to make this screen easier to use. Be sure to check out this FAQ article to learn more about this great new feature.
Improvements
Financial
NS-11872 - Prevented mismatching GL Dates and Transaction Dates on Banking Transactions
Have you ever looked down at your feet at the end of a long day and realized the socks you were wearing don’t actually match? That’s a little embarrassing; not the end of the world but something you’d rather avoid. Maybe you should replace that burnt out lightbulb over your sock drawer. While they might not be socks, it used to be possible to mismatch the Transaction and GL Dates on Checkbook Adjustments, Deposits, Manual Payments and Transfers. We’ve changed those transactions so the Transaction Date and GL Date are always kept in sync and then removed the GL Date from the Properties section tab of the record view.
Inventory
NS-11053 - Removed correct-only option from Inventory Void & Correct and prevented voiding or correcting Production Orders
To Correct or to Void and Correct, that used to be the question you had to ask yourself when beginning an Inventory Correction. We heard your feedback and have removed the Correct (without voiding) option from the Inventory Void & Correct screen. When creating a correction, the original transaction will always be voided, reversing its effect on inventory, and a new correcting transaction will be created, ready for you to make changes. Additionally, we removed the option to Void or Correct Production Orders, which was incorrectly included as one of the available transaction type options.
NS-12258, NS-12714 - Improved Inventory Lot, Production Batch, and Warehouse Lot Processing
Sometimes improvements are big, flashy changes that make you sit up and take notice. This isn’t one of those types of improvements. What it is, though, is a huge, behind the scenes type of upgrade to how NorthScope processes inventory, warehouse and production lots and batches. We’ve updated the lot and batch processing frameworks, improving handling large amounts of information more efficient efficiently as well as making these processes easier for NLP developers to maintain in the future. Don’t worry, though, while we were doing all this work under the hood, we checked the oil, rotated the tires, we also fixed a few other bugs: an issue causing the Incomplete Lot Information validation to be unexpectedly displayed for Inventory Receipts and incorrectly deleting all lines of an Adjustment transaction when only the selected line should have been deleted. We also fixed an issue with Two-Part Transfer transaction where the In-Transit site is Warehouse Lot tracked but the Warehouse Lot on the Receipt transaction did not fill in the Warehouse Lot as keyed on the first part of the transfer, which prevented these transfers from being posted.
Bugs
Financial
NS-11840 - Fixed GL Account Format sequence bug that was preventing adding new GL Accounts during initial NorthScope installation
Your brand new, fresh, clean and totally empty NorthScope system just got installed and you’re totally jazzed to start adding GL Accounts to it. You’ve started setting your Account Format Segments but they’re all getting set as Sequence #1. We updated the Account Format screen so segments will always be sequenced in the order they are keyed and can’t be resequenced.
Fisherman Accounting
NS-10350 - Fixed a bug in Ticket Purchases report that resulted in Weight not displaying after a Ticket's premiums were changed during a correction
...
NS-11028 - Prevented Fish Ticket GL Date and Journal Date mismatch on replaced ticket versions after voiding or correcting.
GL Dates seem to be a theme with this release of NorthScope, or maybe the theme is more about consistency of dates. In either case, we have fixed an issue that caused the GL Date of a Voided or, in some cases, a Corrected Fish Ticket to disagree with the related Journal Entry’s date.
...
Here you are, minding your own business trying to void an Invoice when you get the message “The selected transaction is part of an open payment batch and cannot be voided.” Huh?!? Our development team found and fixed a problem in the validation that was mixing up transaction types when checking for transaction on open payment batches and was the cause of the validation showing when it shouldn’t have. The same validation also applies to Credit Memos, Fisherman Sales, and Tender Resales.
NS-11507 - Fixed a bug causing Check Numbers to become noneditable in Fisherman Accounting Payment Batches
There are a ton of Fisherman Check and ACH payments that need to go out today, so you and your colleague team up to get through everything as quickly as possible. You’ve You’re working on half of the payments while your coworker is taking care of the other half when all of the sudden the Next Check # field on your Process Checks screen decides to go on break and prevent you from keying the check number. We fixed an issue that was causing the Next Check # field on the Process Checks screen to become disabled when someone else, working in a separate batch, prints their checks just before you print the ACH Remittance.
NS-11533 - Prevented extremely log long Fish Ticket Number from causing Fishermen Aging report to not run correctly
It doesn’t happen very often, but sometimes you really need to have a Fish Ticket Number that is more than 25 characters long. The Fish Ticket record view Record View is completely happy with Fish Ticket Numbers up to 50 characters, so what could possibly go wrong? As it turns out, the Fisherman Aging report will throw a fit if it sees a Ticket Number longer than 25 characters. We’ve updated the Fisherman Aging report to allow Ticket Numbers up to 50 characters long.
NS-12298 - Fixed several Fisherman Accounting Payment Receipt History inquiry Inquiry bugs
A group of small changes can add up to a big improvement, and we think you’ll agree that our recent changes to the Fisherman Accounting Payment History inquiry don’t seem like they are very consequential, individually, but together make this screen much nicer to use. We’ve added the ability to select All checkbooks, added the ability to jump to the Deposit record by clicking on a Deposit ID, added a helpful message when trying to open the Deposit record from the More Actions menu for transactions that are not actually deposits, and last but certainly not least, we made a few inquiry columns wider to make viewing their contents easier.
Inventory
NS-11935 - Updated the Items List View to allow very long Item Class ID and Descriptions
Some things are more than the sum of their parts. Take Item Class IDs and Descriptions: Class IDs can be 25 characters and the Description can be up to 50 characters. How do those sum to more than 75? Because, when displaying them on the Items List View, NorthScope separates these two fields with a colon and a space, making up to 77 characters. We’ve fixed the Item List View so it won’t display an error for when really long Item Class IDs or Descriptions are used.
Sales
NS-12090 - Fixed FIFO rules when allocating by Warehouse Lot
Once upon a time, there was a little bug. This wee bug lived in the Sales Order Allocate by Warehouse Lot screen. When an unsuspecting person wondered wandered into the Allocate by Warehouse Lot screen and did an allocation, the bug would bite and add allocations to inventory lots that had negative On Hand or Available quantities. We have humanely eradicated the bug, so you won’t have to worry about getting bit bitten while doing warehouse lot allocations.
...
Inadvertently double-clicking a Save button shouldn’t have any real adverse effects. It doesn’t make sense that just because a button is very quickly clicked twice that two applications would be created. We’ve fixed an issue where if the Save button was double clicked at just the right speed multiple payment applications would be created in the system.
Technical Changes
- No Please view cumulative schema changes here.
- No config file changes.