NorthScope 2021.03.05

Owned by Janice Dannenberg (Unlicensed)
Last updated: Mar 08, 2021 by Emma Greenwood
4 min read

(Software Version: 2021.03.05 Database Version: 2021.03.05)

Release Date: March 05, 2021


Improvements

Fisherman Accounting

NS-7675 Added property to Ticket Class Record View to require Chill Type on a Fish Ticket

Don’t mind us, we’re chillin’ out here. We added a new property called “Require Chill Type Before Approval” to the ‘Setup’ group on the Ticket Class Record View. This field will default to “No” and if updated to “Yes”, then the message “[Ticket Number] Chill Type is required.” will be displayed when a Fish Ticket is saved as ‘Approved’ or ‘Ready to Post’ and does not have a Chill Type selected. This validation will occur on both the Fish Ticket Record View and the Fish Ticket List View (via Mass Update of the ‘Status’ field).

 

NS-7728 Revised Chum / Red Split Percentage calculations

We know how important splitting Mixed Fish tickets is. That’s why we updated the way we calculate the Chum / Red percentages. If the calculated Chum Lbs is < 0.50 Lbs, we will not add a Chum line to the fish ticket and all weight and number of fish will be recorded in the Red line. If the calculated Chum Lbs is >= 0.50 and < 1.00, then we will add a Chum line with 1 Lb and 1 fish. All remaining Lbs and number of fish will be recorded to the Red line, rounded to whole numbers. If the calculated Chum Lbs is >= 1.00, then we will round the calculated Chum Lbs and number of fish to whole numbers. If the remaining Red Lbs is < 0.50, then we will not add a Red line; As long as the remaining Red Lbs is >= 0.50, a Red line will be added.

We used the same calculation logic from above when users attempt to recalculate Mixed Fish percentages for tickets that have been Corrected. Previously, users could only utilize the Chum % mass update functionality if both Chum and Red lines were on the fish ticket. Now, we’ve updated the Chum % mass update to work, as long as a fish ticket has previously gone through the Chum/Red process, even if only one line exists on the ticket. Please refer to How do the Chum % (Chum/Red Split) calculations work? FAQ for more information.

Note – A datafix will be run to determine if existing Fish Tickets contain both a Chum and a Red item with the same Condition, Grade, Disposition and Sold Condition. If tickets meeting these criteria are found, then the data fix will assume the two items are a result of a mixed fish item and populate a field in the database. Users won’t notice anything different as a result of the datafix.

 

NS-7732 Added a new Fish Ticket Premium Assignment to Auto Assign Floating Tickets

To give users the ability to apply Premiums to Floating tickets, we have added a new option on the Premium record in the ‘How this Program is assigned to Tickets?'’ property lookup called “Auto-Assign – Floating Tickets”. If the 'Floating’ property on the Properties tab of the Fish Ticket Record View is set to “Yes”, and the criterion on the associated Premium record is met, then the Premium will be automatically assigned to the Fish Ticket. And we’ll all float on… alright!

Note - We added an additional Enumeration Option to the existing ‘APAssignmentMethod' Enumeration Class called “Auto Assign - Floating Tickets“.


Purchasing

NS-7749 Created new Purchasing Transaction Class List View

We wanted to class up the place a little and we did that by adding the new Invoice and Credit Memo Transaction Class List View. It can be accessed from the Purchasing > Configuration menu. Here you may view, create, edit or delete Transaction Classes and their associated properties. Class ID, Class Description and Doc Prefix will need to be unique by Transaction Type. Please note that you (#DrSeussWeek) should not, may not, will not, and cannot delete Transaction Classes that have been used on an open or posted transaction. New active Transaction Classes will be available from the New lookup on the Invoices List View.

Note – The ‘Class ID’ field will only be editable after initial Save for systems that are not integrating AP Invoice and Credit Memos with a third-party system.

 

NS-7753 Added Transaction Class to Build Payment Batch Record View

We have added the ability to filter transactions by Transaction Class on the Build Payment Batch Record View. This field will be a multi-select lookup that contains only active Transaction Classes set up on the Transaction Class List View. Not selecting a Transaction Class value will return all transactions, even if the transaction is on an inactive Transaction Class. Additionally, a new ‘Transaction Class’ column has been added to the Transactions grid. It is hidden by default.

We also made a slight update to how we filter transactions. Previously, we did not include Credit Memos and Payments in the Transactions grid if the ‘Due Date as of’ or ‘Discount Date as of’ fields were populated. Now, if the ‘Due Date as of’ and ‘Discount Date as of’ fields are populated, then Credit Memo and Payment transactions will be displayed in the Transactions grid, assuming those transactions are selected on the ‘Include Transactions’ field and match all other filter options.


Technical Changes

  • Please view cumulative schema changes here. 
  • No config file changes.