NorthScope 2019.03.22
(Software Version: 2019.03.22 Database Version: 2019.03.22)
Release Date: March 22, 2019
Improvements
Purchasing
NS-4309 Added Vendor Class to the Invoices and Invoice Lines List Views and Inquiries
To make it easier to review AP Invoices and Credit Memos, the Vendor Class column was added to the following List Views and Inquiries:
- List Views
- Invoices
- Invoice Lines
- Inquiries
- AP Invoices
- AP Invoice Lines
Note: This column was added to the system views of pages listed above. Any existing custom user views on these pages will need to be deleted and re-created.
Sales Order
NS-4182 Added capability for users to control how many blank rows are added on ‘New’
A new property called “Rows to Create on New” was added to the Sales Order Transaction Class Record View to allow users to specify the number of lines that are displayed in the grid of a Sales Order Transaction. The number of lines will either be displayed when opening a new sales order with no line items or when the New button on the grid toolbar is clicked. This new property must contain a value between 1 and 25 and is required.
System
NS-4239 Updated Company Name to support 100 Characters and added Company Short Name
Previously, the ‘Company Name’ field in the DataEntityCompany table was 25 characters. This name was used both for printed reports and to display the in the upper left corner of the NorthScope navigation menu. Because the company name on the NorthScope menu does not word wrap, and 25 characters was not enough for all companies, the “Company Name” field was updated to 100 characters and a new 25 character “Company Short Name” has been added for the NorthScope main menu. The following record views and list views were updated to use the Company Short Name:
- Security Groups List view
- Security Groups Record View
- Security Groups Copy Record View
- Currencies List View
This development item includes a datafix to update the Company Short Name using the current left 25 characters of the Company Name.
Bug Fixes
Purchasing
NS-4245 & NS-4248 Issue with unapplying Voided Checks
When a user voids a payment (Vendor or Fisherman check), the original payment is updated to a Status of ‘Replaced’ and a new instance of the payment is created with a Status of ‘Void’. The original payment is auto applied to the new voided payment to clear the balance.
Prior to this update, users were able to view the applications from either the Void or Replaced payments and ‘unapply’ them from each other. When this happened, the Vendor Balances, Fisherman Balances, and Vendor History inquiries would display incorrect balances. The General Ledger and the Aging reports were always correct.
A fix was made to prevent users from doing this. If a user tries to unapply either payments, they will receive a message “You cannot unapply the replaced/voided version of this transaction.”
NS-4254 Issue with voiding an AP Check that included credit memos and/or manual payments
Prior to this release, there were some instances where voiding an AP Check was not correctly unapplying all documents that were paid with the check.
This only occurred in scenarios where the check was created from the ‘Build Check Batch’ process and it contained one or more credit memos and/or manual payments. When this occurred, the total open balance of the Vendor was correct, but the balances of the open detail transactions were not.
Technical Changes
Schema Changes
ALTER TABLE [dbo].[ERPx_MFDataEntityCompany] ALTER COLUMN [CompanyShortName] [varchar] (25) NOT NULL
ALTER TABLE [dbo].[ERPx_MFDataEntityCompany] ALTER COLUMN [CompanyID] [varchar] (15) NOT NULL
ALTER TABLE [dbo].[ERPx_MFDataEntityCompany] ALTER COLUMN [CompanyName] [varchar] (100) NOT NULL
ALTER TABLE [dbo].[ERPx_MFDataEntityCompany] ALTER COLUMN [ServerName] [varchar] (25) NOT NULL
ALTER TABLE [dbo].[ERPx_MFDataEntityCompany] ALTER COLUMN [DatabaseName] [varchar] (100) NULL
ALTER TABLE [dbo].[ERPx_MFDataEntityCompany] ALTER COLUMN [CompanyLogoFileLocation] [varchar] (500) NULL
ALTER TABLE [dbo].[ERPx_MFDataEntityCompany] ALTER COLUMN [DataLayerID] [varchar] (50) NULL
ALTER TABLE [dbo].[ERPx_MFSite] ADD [IntegratedTransferDefaultViaSiteSK] [bigint] NULL
ALTER TABLE [dbo].[ERPx_MFSite] ADD CONSTRAINT [FK_ERPx_MFSiteIntegratedTransferDefaultViaSiteSK_ERPx_MFSite] FOREIGN KEY ([IntegratedTransferDefaultViaSiteSK]) REFERENCES [dbo].[ERPx_MFSite] ([SiteSK])
ALTER TABLE [dbo].[ERPx_SOOrderTypeDocument] ADD [RowsToCreateOnNew] [int] NOT NULL DEFAULT(5)