NorthScope 2018.11.21

Owned by Emma Greenwood
Last updated: Nov 26, 2018 by Kati Huttunen (Unlicensed)
5 min read

(Software Version: 2018.11.21 Database Version: 2018.11.21)

Release Date: November 21, 2018


New Features

Inventory

Feature Spotlight! NS-3642 Added the ability to void and correct posted Inventory transactions 

A new “More Actions” toolbar icon was added to the Inventory Transactions List View. Clicking this icon and selecting “Void/Correct”, opens the new Void/Correct page where users can find historical transactions to void or correct.

The Void/Correct page allows users to filter historical transactions by: 

  • Transaction Type – Specify either an Adjustment, Production, Receipt, Transfer, or Transfer Receipt. This defaults to blank but is required.
  • Action – Identify whether you want to Void or Void & Correct the selected transactions. This defaults to blank but is required.
  • Site – Specify the transaction site. For ‘Transfers’ and ‘Transfer Receipts’ this will search across the Site, Via Site or To Site. This defaults to blank but is required.
  • Transaction – Specify part, or all, of the Transaction ID, Reference, or BOL. Leave blank to search all.
  • Date From – Specify the beginning date range from you search. This defaults to a year back but can be edited. This field is required.
  • Date To – Specify the ending date range from you search. This defaults to the current date but can be edited. This field is required.

When a transaction is voided, Status is updated to “Void” and product balances are re-calculated to reflect updated Available and On-Hand balances.  

When a transaction is voided and corrected, the status of the original transaction is updated to “Void”, product balances are re-calculated to reflect updated Available and On-Hand balances, and a new version of the Transaction is created with a Status of “New “. The new transaction can be opened from the Transactions list view, corrected, and re-posted.  

A notification is displayed for the user, if the transaction being voided or corrected contains lots that have sales allocations against them. Users are prevented from processing transaction voiding, if it would result drawing the lot balances negative and the transaction property “Negative Available Balances” is set to “Not Allowed”. When the Transfer side of a two-part transfer is voided, also the Receipt side of the transfer transaction is voided.  

This development item also includes the following changes:  

  • A new status of “Deleted” was added. Previously, deleting an inventory transaction set the status to “Void” and this will now set the status to “Deleted”. 
  • A new Transaction property “Corrected From” was added to the transaction record. The field displays the ID of the original transaction.
  • A new column “Corrected From” was added to the following list views and inquiries:
    • Inventory Transactions List View
    • Transaction History – Item Inquiry
    • Transaction History – Lot Inquiry

This development item includes a data fix to change the status of all “Void” transactions to “Deleted”.

Note: This change impacts the system view of Inventory Transactions List View and Transaction History inquiries and previously saved custom views must be removed and recreated in order to view the new column.

Improvements 

Financial

NS-3674 Added new properties to Journal Entries to show when they were created and who created them and added additional columns to journal list views and inquiries

The following properties were added to the Journal Entry Record View Properties tab:   

  • Created – Displays the date and time the Journal was created
  • Created By – Displays the username of the user that created the Journal

The following columns were added to the Journal Entries and Journal Lines List Views and the Journal Entries and Journal Lines Inquiries:   

  • Created – Displays the date and time the Journal was created
  • Created By – Displays the username of the user who created the Journal
  • Last Updated – Displays the date and time the Journal was most recently updated
  • Last User – Displays the username of the user who updated the Journal most recently

The Created and Created By values are auto-added when the record is created and do not update after that. There are two instances in which a journal record can be created from a transaction; when clicking journal details for the first time from a record view of a transaction or when approving or posting a transaction without first clicking the journal details button.

As part of this work item, the code was updated to ensure the exchange rate is updated in the header section of the journal, if the rate has changed between the time the journal was created and posted.

This development item includes a data fix to populate the “Created” property from the “Last Updated” property and the “Created By” to populate to “Upgrade – R20181121_1321”.

Note: Journal entries created for unposted transactions in other modules will no longer display in the Journal Entries and Journal Lines list views. This list view is intended to only show unposted manual journal entries.


NS-3731 Added new properties to Journal Entries to show when they were Posted and who Posted them  

The following properties were added to the Journal Entry Record View Properties tab:   

  • Posted – Displays the date and time the Journal was posted
  • Posted By – Displays the username of the user that posted the Journal

The following columns were added to the Journal Entries and Journal Lines List Views and the Journal Entries and Journal Lines Inquiries:   

  • Posted – Displays the date and time the Journal was posted
  • Posted By – Displays the username of the user who posted the Journal

These fields are populated when manual journals or transaction journals are saved as Ready to Post or Posted. 

This development item includes a data fix to populate the “Posted” property from the “Last Updated” property and the “Posted By” to populate to “Upgrade – R20181121_1321”.

Note: Journal entries created for unposted transactions in other modules will no longer display in the Journal Entries and Journal Lines list views. This list view is intended to only show unposted manual journal entries.

Bug Fixes

Purchasing

NS-3779 Fixed Issue Mass Updating the Status for a negative Customer Sale 

Users were receiving an invalid error when trying to Approve/Post a negative Customer Sale via the mass update tool. 

Technical Changes

Schema Changes

ALTER TABLE [dbo].[ERPx_GLJournalHeader] ADD [CreatedDate] [datetime] NULL --Will be set to NOT NULL by DataFix

ALTER TABLE [dbo].[ERPx_GLJournalHeader] ADD [CreatedBy] [varchar] (150) NULL --Will be set to NOT NULL by DataFix

ALTER TABLE [dbo].[ERPx_GLJournalHeader] ADD [PostedDate] [datetime] NULL

ALTER TABLE [dbo].[ERPx_GLJournalHeader] ADD [PostedBy] [varchar] (150) NULL


ALTER TABLE [dbo].[ERPx_IMTransactionHeader] ADD [VoidDate] [DATETIME] NULL

ALTER TABLE [dbo].[ERPx_IMTransactionHeader] ADD [VoidedBy] [VARCHAR](150) NULL

ALTER TABLE [dbo].[ERPx_IMTransactionHeader] ADD [CorrectedFromTransactionHeaderSK] [BIGINT] NULL

ALTER TABLE [dbo].[ERPx_IMTransactionHeader] ADD CONSTRAINT [FK_ERPx_IMTransactionHeader_ERPx_IMTransactionHeader_Correction] FOREIGN KEY ([CorrectedFromTransactionHeaderSK]) REFERENCES [dbo].[ERPx_IMTransactionHeader] ([TransactionHeaderSK])


CREATE TABLE ERPx_IMTransactionMoreActionsCriteria

(

    [MoreActionsSK] [BIGINT] NOT NULL IDENTITY(1,1),

    [TransactionTypeSK] [BIGINT] NOT NULL,

    [MFTransactionMoreActionsEN] [BIGINT] NOT NULL,

    [DateFrom] [DATETIME] NULL,

    [DateTo] [DATETIME] NULL,

    [GLAccrualDate] [DATETIME] NULL,

    [SiteSK] [BIGINT] NOT NULL,

    [TransactionID] [VARCHAR](50),

    [UserSK] [BIGINT] NOT NULL,

    [DataEntityCompanySK] [BIGINT] NOT NULL,

    [TransactionsToVoidCorrect] BIGINT NULL,

    [TransactionsProcessed] BIGINT NULL,

    [ValidatedTransactionHeaders] XML NULL

) ON [PRIMARY]


ALTER TABLE [dbo].[ERPx_IMTransactionMoreActionsCriteria] ADD CONSTRAINT [PK_ERPx_IMTransactionMoreActionsCriteria] PRIMARY KEY CLUSTERED  ([MoreActionsSK]) ON [PRIMARY]

ALTER TABLE [dbo].[ERPx_IMTransactionMoreActionsCriteria] ADD CONSTRAINT [FK_ERPx_IMTransactionMoreActionsCriteria_ERPx_IMTransactionType_TransactionTypeSK] FOREIGN KEY ([TransactionTypeSK]) REFERENCES [dbo].[ERPx_IMTransactionType] ([TransactionTypeSK])

ALTER TABLE [dbo].[ERPx_IMTransactionMoreActionsCriteria] ADD CONSTRAINT [FK_ERPx_IMTransactionMoreActionsCriteria_ERPx_MFSite_SiteSK] FOREIGN KEY ([SiteSK]) REFERENCES [dbo].[ERPx_MFSite] ([SiteSK])

ALTER TABLE [dbo].[ERPx_IMTransactionMoreActionsCriteria] ADD CONSTRAINT [FK_ERPx_IMTransactionMoreActionsCriteria_ERPx_MFUser_UserSK] FOREIGN KEY ([UserSK]) REFERENCES [dbo].[ERPx_MFUser] ([UserSK])

ALTER TABLE [dbo].[ERPx_IMTransactionMoreActionsCriteria] ADD CONSTRAINT [FK_ERPx_IMTransactionMoreActionsCriteria_ERPx_MFDataEntityCompanySK_DataEntityCompanySK] FOREIGN KEY ([DataEntityCompanySK]) REFERENCES [dbo].[ERPx_MFDataEntityCompany] ([DataEntityCompanySK])