You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Coming next release

Handle reason/action codes for returns in sales

(RTC-28027)

To avoid storing all sales we aggregate sales to see the stock changes in batches with exception for items sold with serial numbers. When return is done with damaged flag set, we treat that return as breakage, in result such return will create two lines, one as sale with amount increasing the stock, and one breakage line decreasing it again.


Release 24.04.2023

Permissions for item transactions per store

(RTC-30977)

In User Management there are permissions for "View transaction" and "Manage transaction" per item transaction type. Permissions are assigned to roles on store level.

Improvements

ModuleDescription
Stock transactions

Fix: Show store number and name (RTC-30944)

  • When an item has stock in only one store, then a store label with proper store's name and number is displayed;
  • For store users - store label with proper store's name and number is displayed.

Supplier number is displayed in both Transaction log and Stock status views - grids were displaying wrong value from database (OrganizationNumber instead of ExternalSupplierNo).

System

ItemService integration (RTC-31163)

When InventoryService was receiving ItemChanges event with ItemReceiptText longer than 50 characters, then item merger was failing with conflicts in data model. Change in ItemReceiptText length from 50 to 255 resolves that problem.


Release 27.03.02023

ModuleDescription
Transactions in user interface

Create Internal Use from user interface (RTC-30100, RTC-30101)

New transaction types was implemented in modal and it allows user to create these transactions in the UI from "Stock status" and "Transactions log" views. The transaction types are:

  • Internal use
  • Stock adjustment (increase/decrease stock)
Stock Status

Stock Status per item (RTC-29742)

Providing a view displaying stock status for a given item that consists of three main sections: Stock status, Model and Other store. In Stock status section, a picker for selecting store is available. There is also a donut chart with key values: number of items reserved, put away, available and in stock. Model section is presented when the model contains multiple colors and sizes, otherwise, it is hidden. There is a possibility to switch between models using color/size field as a dropdown list. In Other store section stock statistics are shown for the given item in other stores.

Release 13.03.02023

ModuleDescription
Stock status

Reservation field in Stock Status (RTC-29562)

Field "Quantity reserved" was added to the Stock Status grid

Transaction in UI

Create breakage from UI (RTC-30097)

New transaction modal was implemented and it allows user to create breakage transactions in the UI from "Stock status" and "Transactions log" views

Stock Status per item

Grid view of movements for items in store (RTC-27199)

Providing a grid to see item transactions for a specific item in a selected store. The functionality is implemented using a hyperlink on Available quantity on Stock status view that takes users to a second level (tab Status), where they can choose store using the picker. In that place, user can also change color and size of selected item using pickers in breadcrumb if these properties are available. After that transactions for this item in a selected store are displayed in grid (tab Transactions). Implemented grid contains columns compatible with Figma. The ability to export transactions for item in a selected store to excel has also been added. 


System parameter: "DisplayIdentifier" has been added to [dbo].[ConfigurationParameter] to enable change type of Item identifier displayed in breadcrumb in tab Status.

This parameter can have two possible values:

  • GTIN (default value)
  • ItemNo (i.e. external item number)


Release 27.02.02023

ModuleDescription
Store integration extension

Store Management (RTC-29835)

Adding new columns: Gln and UseInventory to [Chain].[Store] table and new table [Chain].[StoreRelatedStore] in order to link stores with other related stores. 

After creating or updating the store in Store Management, values of Gln, UseInventory flag, related stores, profile, region and teams are correctly updated in the database based on information from an event from StoreService.

Export of data

Export item transactions (RTC-27531)

"Export" job has been extended to export item transactions. It publishes Inventory.ItemTransaction.Export events to both - BatchToProcess service bus topic and BatchToProcess container in Azure storage.
The Sale and StockStatusImport transactions are not exported.

"Export" job from InventoryIntegrationPackage needs to be enabled with default configuration (with the scheduled trigger for exporting Item transactions enabled).

Export stock status (RTC-29213)

"Export job" has been extended to export stock. It publishes Inventory.StockStatus.Export events to both - BatchToProcess service bus topic and BatchToProcess container in Azure storage.

"Export" job from InventoryIntegrationPackage needs to be enabled with default configuration (with the scheduled trigger for exporting stock status enabled).

Merger job

Internal transfer transaction merger job (RTC-27672)

ItemTransactionMerger support for Internal transfer transactions has been added. Internal transfer transactions are created in InventoryService and stocks are properly updated:

  • items' stocks are reduced in the origin store;
  • items' stocks are increased in the destination store.


Release 30.01.2023

ModuleDescription
Transactions

Non stock items (RTC-28406)
Stock for non stock items, in InventoryService marked as "TrackStock=0", is not updated while processing item or sale transactions. 

Reason Codes

Reason code resolved (RTC-28645)
Reason and action codes are now properly resolved for each transaction type. 

Export reason codes (RTC-25406)
Export job have been added to the "InventoryIntegrationPackage". It exports data that has been modified recently. Job is based on change tracking tables in the database. It publishes data as blobs to the "BatchToProcess" topic. Job is by default executed every minute. 

Export job right now supports reason codes, it publishes "Inventory.ReasonCode.Export" event to both "BatchToProcess" bus topic and "BatchToProcess" container in Azure storage. 


Release 16.01.2023

ModuleDescription
Transactions

Skip transactions (RTC-28556)
Receipts without lines or with all voided lines are skipped and events with those receipts are not published to the Inventory Service database.

Complaint transaction processing (RTC-27673, RTC-27340)
Added support for Complaint transactions when returning defect items. 

Support for Internal use transaction has been added to PosLogProcessing and ItemTransactionImport jobs.
Incoming poslogs with TransactionType="ReturnDefectItem" are properly processed and saved to the staging tables in Inventory Service.

ItemTransactionMerger support for Complaint transactions has been added. Complaint transactions are created in InventoryService and stocks are properly updated.

Stock Status (RTC-27495)
Added new item transaction type: StockStatus

This transaction type overrides stock value instead of adjusting the stock values.
Will be used when adding stock from third party stock master or correcting stock status. 

Reason Codes

Repository for reason codes in UI (RTC-23663)
There are two new views added:
Reason codes register and System parameters. In reason codes view, user can browse, edit and create reason/action codes for: breakage, internal use, stock adjustment, internal transfer and complaint. "

Countries" parameter which was added, allows user to modify languages displayed in reason codes register. Default value of the parameter is "[]". Then, in reason code creation view, only English name and description are displayed. Supported countries are: NO, SE, FI, DK, AT, DE, EE, PL, NL, BE.

Example of System parameter value is:

[{"countryCode":"NO","isDefault":false},{"countryCode":"SE","isDefault":true},{"countryCode":"AT","isDefault":false},{"countryCode":"DE","isDefault":false},{"countryCode":"PL","isDefault":false}]

where  "isDefault" parameter can be set on true only for one of the country codes. Dutch is common for BE and NL and German is common for AT and DE.


Release 16.12.2022

ModuleDescription
Stock Update

Stock update (RTC-27312)

ItemTransactionMerger job has been extended with stock update logic:

  • When item has stock in InventoryService, then stock for this item in sender store is properly update with stock value from incoming transaction;
  • When item has no stock in InventoryService, then new entry for this item and sender store is created with stock value taken from incoming transaction.

The stock changes from StockAdjustment transactions are properly registered and updated in InventoryService.

Sales transaction

Sales transaction processing (RTC-27311 ,RTC-27313)

Added support of processing receipts with type sale, updating stock in Inventory module based on sold amount. 

Support for Sale transaction has been added to POSLogProcessing and ItemTransactionImport jobs.
Incoming POSLogs with TransactionType="Normal" and with valid RetailTransaction content are properly processed and saved to the staging tables in Inventory Service.

The items' stock is properly updated in InventoryService based on sales transaction data.
Sales data is read from staging tables, processed and properly saved in the InventoryService database
Item transactions are created in each job's run,  single item transaction has all items with aggregated stocks within single store from all read events.

Internal Use

Internal Use transactions (RTC-27671)

ItemTransactionMerger support for InternalUse transactions has been added. InternalUse transactions are created in InventoryService and stocks are properly updated.

Grid View

Grid view of items and stock levels (RTC-22717)

Added grid view allows user to see, filter and sort stock of items. 
File exporter job has been added to the InventoryIntegrationPackage. It exports stock to excel and saves them into blob container named "Inventory"
Note: Function "Export to Excel" requires additional setup before enabled in each environment. 

  • No labels