Versions Compared

Version Old Version 1 New Version Current
Changes made by

Anagha Chacko

Anagha Chacko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Increff Merchandising

...

Solution - Enterprise Release Notes

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

...

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 considered for level 1 rev/day in the 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

  • To correctly meet the forecast objectives in buying, we started not suggesting any buy output for those which are marked with 0% override.

  • Outputs of the OD module should still contain these Store+AGs but the modules post-OD won't contain these Store+AGs

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

  • JIRA Ticket: IRISENT-4264

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 level 1 rev/day in the store style ranking

  • Currently, the universe of store styles considered for Level 1 consists of styles live in the store on run date. It does not consider stock-outs.

  • For IST and Replenishment with replacement, Level 1 universe will include all the store-style combinations which were present in “Duration in days to analyze Ranking and Top seller” days.

  • JIRA Ticket: IRISENT-4284

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

...

  1. Modification of default period type: Default period types have been modified to ensure a better, error-free experience

  2. Enforcing 0% override from the 'Revenue Contribution Override' input in other modules: 0% Rev override will ensure that it is completely eradicated

  3. Other value additions

Get familiar with the new changes/ enhancements

Modification of default period type in the Open-to-Buy module

  • Earlier, the default period type in the Open-to-Buy module was set to “NONE” which was causing failures for users who were unaware of this

  • Now, when the user adds a new input period in buying module , the default period type will be set to FULL“FULL_PRICE_PERIOD. PERIOD”. This ensures an error-free run in case the input period is not updated before the run

  • If there are many sub-periods in a period, only the first one becomes FULLsub-period would be set to “FULL_PRICE_PERIODPERIOD” 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

...

  • “EOSS”

Enforcing 0% override from the 'Revenue Contribution Override' input in other modules

  • Earlier, despite giving 0% override in the 'Revenue Contribution Override' input in the Optimum Depth module, the Store+Attribute Group combinations which were expected to not have any contribution in the Distribution or Buying outputs were still available in the output

  • To eliminate this, post Optimum Depth module run, the group of Store+Attribute Group under the umbrella of 0% override have been removed from the universe of Store+Attribute Group from all the modules that are dependent on Optimum Depth

  • These Store+AGs combinations will still be present in the Optimum Depth module outputs and the Optimum Depth Override FAQ output. They will be printed with the remark, “Override provided as 0% and Store+AG pruned hereafter”

Other Value Additions

Revamped runtime validations for the Reordering module

  • A warning has been added to ensure the user is aware when the store-category combinations for which warehouse-store category mapping input is absent.

  • The warning highlights the combination of Stores present in the store list and categories enabled in Category Config without any Warehouse store category mapping

  • In the Validation download, instead of providing the styles for which the input periods were missing, the tool will provide the styles under the channel level for which the input periods are missing. This will be visible as a validation error

Inclusion of all store-style combinations in store-style ranking

  • Earlier the tool did not consider styles that did not have stock for the run date but had sales in the analysis duration for store-style ranking

  • It will now include all store-style combinations present under the analysis duration for Inter Store Transfer and Replenishment/Replace runs

Have any Questions?

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

...