NorthScope 2020.04.03

Owned by Janice Dannenberg (Unlicensed)
Last updated: Apr 03, 2020
6 min read

(Software Version: 2020.04.03 Database Version: 2020.04.03)

Release Date: April 03, 2020


New Feature

Sales

New Feature! NS-5568, NS-6165, NS-6169 & NS-6173 Created Sales Quote Transaction

The highly anticipated Quote transaction is live with this release of NorthScope! What does this mean? How do I use it? What do I need to know? We hope to answer those questions below, so here goes. From the Transaction List list view, users have the option to create a new quote. You will notice the quote creation process looks almost identical to an order, with several key differences:

  • Quotes will not create journal entries.
  • Sales Programs will not be calculated for a quote and the Programs Detail button will not be visible in the header.
  • Items added to the quote will not affect customer credit limits. Automatic credit holds will not apply to quotes.
  • Quotes will not be assignable to a contract – the Contract dropdown on the quote’s Items grid is disabled.
  • Quotes only have 2 statuses: New, Approved.
  • The Shipment tab of a quote will have Shipped, Invoice #, Invoiced and GL Date fields disabled. This is due to the fact that quotes will not have shipments/loads. When the quote is converted to an order, the logistics load will be built as per the current process.
  • Quotes do not generate Invoice Numbers and are therefore, not returnable or price adjustable.

Now, a few pertinent similarities between quotes and orders:

  • Quotes and orders will share the same sales order attributes and sales order item attributes. We’ve updated our ‘Company: Setup – Attributes’ page to change the transaction name from ‘Sales Order – Order’ to ‘Sales Order – Order and Quote’. If sales order attributes and sales order item attributes are saved on a quote, the values for the attributes will remain when the quote is converted to an order.
  • Price list applications for quotes will operate in the same manner as on an order. For example, items will default prices from an applicable price list and may be repriced as long as the current price was not manually overridden.
  • Notes entered on the quote will appear on the order.
  • Certifications for items saved on the quote will appear on the order.
  • Items added to the quote can be allocated, but allocation is not required to convert a quote to an order. If items are allocated on the quote, they will affect available inventory balances and will persist when the quote is converted to an order. Additionally, quoted prices will not change when a quote is converted to an order.

A quote is automatically converted to an order when the Status is set to “Approved”. This can be accomplished within the Quote Transaction RV or from the Transaction List list view via the Status button. Users will receive a message stating "Quote [Quote #] has been converted to Order [Order #]" for a single quote conversion or "[Count of Quotes] Quotes have been converted to Orders" for multiple quote conversions at once. When a quote is converted to an order, the status of the order will default to the status that is set up on the Order Transaction Class record view. This new property is called ‘Default Order Status for Converted Quote’ and is available for users to configure. The property defaults to “New” but can also be set to “Released”, so long as the “Released” status is enabled on the ‘Sales: Configuration – Status Setup’ page.

What if I want to delete a quote? Not a problem. Users can delete quotes while in status ‘New’ from either the Quote Transaction RV or the Transaction List list view. Deleting a quote will set the status to “Void” and any inventory allocations existing on the quote will be removed so that inventory balances will not be impacted. You can always view deleted quotes from the ‘Transaction History Inquiry’ page.


Improvements

Inventory

NS-5619 Created Hold Code Override functionality for Inventory Lots

Hold up! We’ve designed a way to allow users with override capability to be able to allocate from an inventory lot that is on hold. To accomplish this, we have updated the Hold Codes record view in the Inventory functional area with an “Allowed to Override” tab that displays the names of all the Users configured in the system with the ability to include or remove one or many users to have Override capabilities.  When an inventory lot is assigned a Hold Code, the available units and weights are zeroed out. Hold Code override functionality affects the following:

  • Inventory Transactions
    • Because Production Input transactions and Transfer transactions can deplete inventory, users without Hold Code override capability will be prevented from saving those inventory transactions containing lots with Hold Codes. Users will see the lot disabled on ‘Find Inventory Lots’ page.
    • Production Output transactions, Adjustment transactions and Receipt transactions have no restrictions because they add inventory. Users may freely add to inventory lots that are on hold.
    • We’ve also updated the code behind inventory file imports to work accordingly.
  • Sales Allocations
    • When a sales order is created for an inventory lot on hold, only users with override capability will be able to allocate from the lot. This can only be accomplished via the ‘Allocate by Inventory Lot’ tab on the ‘Allocate Sales Transaction Item’ page. Users do not have the option to “Allocate by Item” or “Allocate by Warehouse Lot” because multiple hold codes with different override users may exist.
    • Auto Allocate will not be allowed to automatically allocate held lots even if the user is in the “Can Override” group.

Note – XML integration for inventory transactions and sales allocations work a bit differently. For Inventory transactions, due to the limitations of XML, we cannot specify the user executing the integration. As a result, if a lot is on hold, no allocations to the lot will be allowed since we do not have the user information.  Sales order allocations will display the following message in the Inbound integration queue “Item [Item ID], Site [Site ID], Production Batch [Prod Batch ID], Warehouse Lot [Whse Lot ID], Owner [Owner ID] is currently on [Hold Code] hold and cannot be added to the [Transaction ID] transaction” if the user tries to integrate an allocation for a lot that is on hold regardless of the override capability. 

Fisherman Accounting

NS-6036 Added the ability to store Fish Ticket Reprice sessions

Repricing Items and Premiums is complicated and sometimes time consuming and we want to make it easier. We will now store the reprice session until the session is processed. This means users will be able to navigate away from the Fish Ticket Premium Reprice and the Fish Ticket Item Reprice pages and the data that was entered will remain on the page the next time the page is opened. This will be done based on the user, which means two users will be unable to reprice the same ticket items. However, a Delete button has been added to the Reprice header toolbar so that users may delete the user session and start over.


Bug Fixes

Fisherman Accounting

NS-6205 Error displayed when deleting a Fish Ticket line item on a Fish Ticket associated with Tax/Premium programs

We were preventing a Fish Ticket line item that was on a Fish Ticket associated with a Tax/Premium program from being deleted. That was pretty silly of us. Users are now able to delete any line items they wish from the grid on the fish ticket record view, so long as the transaction is in New status.


Inventory

NS-5898 Integration of inventory transactions was rounding to two decimals

On integrated inventory transactions, we were rounding to two decimal places for an item’s Units and Weight. We should have been using the item’s ‘Unit Decimals’ and ‘Weight Decimals’ values in the Properties tab of the Item record view. This has been corrected.


Sales

NS-5882 Updated Price Adjustments that create inventory transactions to not display error when Posting

Price adjustment transactions were creating inventory transactions when they shouldn’t have been, and users were seeing an error when the status of the transaction was set to “Ready to Post”. That error is a thing of the past, much like we hope Coronavirus will be soon. #StayHealthy

Technical Changes

Please view cumulative schema changes here.