Enhancements to help better your performance using Hot SKU settings

Body

Did you know that our Engineering team has introduced a few enhancements to help better your performance using Hot SKU settings?

New property - skipLockInventoryitemList

The HotSKU initially blocks the items for a very long time. This is because the HotSKU attempts to lock the SKU to calculate its inventory availability, after it determines that the item is hot.

A new property, yfs.hotsku.skipLockInventoryitemList, is introduced for HotSKU. This property accepts a list of comma-separated items.

For example, yfs.hotsku.skipLockInventoryitemList=DVP6723040,TV0001A5F21,A1,A2,B,C,D4,E. The YFS_INVENTORY_ITEM table is not locked for these items initialized in the property. Items that are sure to turn hot (For example, a new audio release) can be added to this property beforehand to prevent locking

New property - yfs.Hotsku.useAvailabilityAcrossNodes

Hot SKU logic is enhanced to consider availability across all the nodes to decide if availability is low and item needs to be locked.

While determining whether this hot item still needs to be locked, system will take into consideration availability across all nodes requested instead of individual nodes. And compare the consolidated availability across all nodes with the High Availability threshold.If consolidated inventory is 0, we will avoid locking. If consolidated inventory is low, we will lock the sku even though it may be considered hot. If consolidated inventory is high, we will avoid locking.All agents and APIs that update demand or supply and check availability will be impacted by the fix (ex: reservations, order creation/modifications, scheduling, release). The fix does not change the actual availability calculation, instead it just impacts decision whether to lock an item or not. There is a slight chance that multiple threads can schedule or allocate against a node with low availability. This could result into back order from node (no pick) from DC or Store. In such cases, order would get rescheduled to another location based on availability and sourcing decisions

Do refer product documentation for further details.