Due to some limitations, Sterling Selling and
Fulfillment Foundation lock
the YFS_INVENTORY_ITEM records even when the item is considered as
Hot SKU.
In the following scenarios, the YFS_INVENTORY_ITEM
records are locked even when the item is considered as Hot SKU.
- The updateFutureInventory and getInventoryMismatch APIs
always lock the YFS_INVENTORY_ITEM records during supply adjustment.
- If the request is for specific tag criteria, the YFS_INVENTORY_ITEM
records are locked for all the tag-controlled items.
- The YFS_INVENTORY_ITEM records are locked for a Hot SKU item to
calculate availability, if the inventory for the item is below the
safety level.
Note: The reserveItemInventory API checks
the safety level availability of all the Hot SKU items. However, it
does not load an availability picture for Hot SKU items. A prior call
to one of the promising APIs such as findInventory API
is needed to load the availability picture for all the Hot SKU items.
- If the Summarize and Maintain Total Supply and Demand
Values For Tag Controlled Items installation rule is enabled,
the Hot SKU logic is not used. Also, the values of the TotalOnhandSupply,
TotalOtherSupply and TotalDemand fields are appropriately updated.
- When an item turns hot on the first abnormal lock, availability
is not registered and lock is applied. When the value of yfs.yfs.hotsku.useTimeOutLocking and yfs.yfs.hotsku.registerAvailabilityOnLockTimeout properties
are set to Y, availability check is performed and
registered. For more information about registering availability when
an item turns hot, see Hot SKU control parameters.