1 Feature Summary

The following enhancements are included in this release.

Column Definitions

  • Feature: Provides a description of the feature being delivered.

  • Delivered: Identifies whether the feature is Enabled or Disabled upon initial delivery.

  • Scale: Identifies the size of the feature. Options are:

    • Small: These UI or Process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

    • Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

  • Customer Action Required: You must take action before these features can be used. these features are delivered disabled and you choose if and when to enable them.

Corrected Available Inventory Calculations in Case of Multiple Allocations Created using the same PO

The application logic has been fixed to calculate the available inventory correctly in case of multiple allocations being created for the same purchase order, item and source warehouse combination. Each new allocation will now reflect the actual quantity that is present at the time of creation after deducting all existing approved quantity that might exist as part of another allocation for the same purchase order, item and source warehouse combination.

Updated PO Type to be Allowed During Allocation Creation

As a part of this enhancement, the user now can create a regular allocation based out of a purchase order of type = ‘Automatic Reorder of Basic’ (ARB) using the Allocation application, in addition to non-basic (N/B) orders.

Corrected Issue with BOL-Sourced Allocation Containing Multiple Distros

This update resolves an earlier issue where the same distro number was populated for every item in a BOL-sourced allocation, rather than using the individual distro numbers for the items on the BOL. This issue has now been resolved.

Corrected SPO Integration Issues

Addressed issues with the Size Profile Optimization integration with Allocation. The first issue was related to handling of a blank or missing files, which was causing performance issues in processing. The second issue was related to correctly applying size profiles if it is associated with a GID and contains more than one diff (e.g. color). This change requires updates to system options and store definitions in Merchandising. See Steps to Enable for details.

Steps to Enable

To correctly support allocating parent items containing more than one diff using size profiles, the following may need to be updated in your environment, once this patch is applied.

  • Ensure that Parent/Diff is checked for the Size Profile Validation Levels system option in Allocation.

  • Ensure that all stores that you will be allocating in this way have a Default Warehouse defined in Merchandising.