Versions Compared

Key

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

...

  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

...

  • 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, the default period type will be set to “FULL_PRICE_PERIOD”. This increases the chances of 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 sub-period would be set to “FULL_PRICE_PERIOD” and the remaining ones will get tagged as “EOSS”

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

  • Earlier, despite the user giving 0% override in the 'Revenue Contribution Override' input in the Optimum Depth module, the storeStore+AG 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+AGs Attribute Group under the umbrella of 0% override has have been removed from the universe of Store+AGs Attribute Group from all the modules that are dependent on Optimum Depth

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

...

Revamped runtime validations for the Reordering module

  • To help ensure that 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. A warning has been added

  • 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 now provide the styles under the channel level for which the input periods were are missing. This would will be visible as a validation error

...