Skip to end of banner
Go to start of banner

Release 53

Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 3 Next »

Increff Merchandising Software - Enterprise Release Notes

Following are the enhancements/fixes in MS Enterprise with the latest deployment

User Interface - 9.0.1

Application - 5.17

Algorithm - 12.24

The current release has been tested and will work best with Chrome version - 106.0.5249.119.

Summary

  1. Removal of Store+AG combinations with 0% override post OD

  2. OTB - Style wise buy module changes

  3. Modification in universe of store-style combinations considered for store style ranking

  4. Updated reordering module validations

  5. Change Period Type default in Buying Input period from NONE to FULL_PRICE_PERIOD

Get familiar with the new changes/ enhancements

Key Feature Enhancements

This section will contain new features/ algorithms/ enhancements and optimizations to existing algorithms, reports, and dashboards in the product.

Removal of Store+AG combinations with 0% override post OD

  • Post Optimum Depth modue run, the group of Store+AGs under the umbrella of 0% override has been removed from the universe of Store+AGs

  • These Store+AGs combinations would still be present in the Optimum Depth module outputs but not in the outputs of modules post Optimum Depth

  • In the Optimum Depth Override FAQ output, these Store+AG combinations will be printed with the remark, “Override provided as 0% and Store+AG pruned hereafter”

OTB - Style wise buy module changes

  • Added a separate tag in Style Segmentation input called "campaign". Store styles that are present in any campaign are tagged as "1" and if not present then "0".

  • ASP override, Min Display Override, STR Override are merged into a single input OTB SWB Overrides

Modification in universe considered for store style ranking

  • For Inter Store Transfer and Replenishment/Replacement modules universe of store-style combinations considered for store style ranking will also include stock outs

  • The universe of store-style combinations will include all store-style combinations that were present in “Duration in days to analyse Ranking and Top Seller” days

Other Value Additions

Product Usability Enhancements

This section will contain functionalities related to users logs, scheduling, users and access management, anything in the UI that pushes self-usability, etc. If any of these points need to be supported with relevant screen grabs from the UI then those will also be included here.

Updated reordering module validations

  • Added a warning to inform the user that reordering is being run without any wh mapping for reordering stores + enabled categories

  • Added channel to the input periods for lead time and cover duration present in the Reordering module.

  • JIRA Ticket: IRISENT-4270, IRISENT-4292

Change Period Type default in Buying Input period from NONE to FULL_PRICE_PERIOD

  • Whenever the user adds a new input period in buying module the period type will be set to FULL_PRICE_PERIOD. If there are many sub-periods in a period, only the first one becomes FULL_PRICE_PERIOD and the remaining ones will get tagged as EOSS.

  • JIRA Ticket: IRISENT-4247

Bug Fixes

This section will contain bugs identified in the UI and algorithms that have been fixed in the current release.

Fixing the issues with input period subperiods

  • Each subperiod to have the option to edit the forecast start and end dates

    • Whenever 2 or more sub-periods were given in OD and the user puts the same forecast period for both sub-periods in OW/OTB Depletion one of the sub-periods gets hidden.

    • Going forward each subperiod in Optimum depth will have a visible option to edit the Forcast period in OW/OTB Depletion.

  • If there are 2 or more sub-periods in a period having the same period type (EOSS or NONE), then UI only shows 1 sub-period. Only sub-periods with unique period types in that period are being shown instead of all sub-periods. This is now fixed and the user can edit the period type of all sub-periods in a period.

  • JIRA Ticket: IRISENT-4261

Fix the Reorder index out of bounds exception if there are no warehouses given for reordering store + enabled categories

  • The reordering module used to fail when no warehouses were mapped to any of the reordering store and enabled category combination. This is now taken care of in the product and additionally, a warning related to this is introduced.

  • JIRA Ticket: IRISENT-4269

Fix the issue of printing different closing stock values in weekly depletion and post-depletion outputs

  • Previously, based on the depletion’s start date we were printing depletion quantity in weekly depletion output. Now based it got shifted to the depletion week’s end date.

  • JIRA Ticket: IRISENT-4282

Fixed the issue while uploading blanket level lead time input

  • Blanket level Lead time input is now handled in the product which was resulting in the failure of module previously.

  • JIRA Ticket: IRISENT-4283

Handled the blanket-level Merchandising tagging input while populating output reports.

  • Blanket-level Merchandising tagging input was not working in the output report as a result output tables like r_output_ist_health_rate is coming blank. This is now fixed

  • JIRA Ticket: IRISENT-4278

Tables and API changes

Have any Questions?

Please feel free to contact your account manager if you have any queries.

  • No labels