Order Management Hot SKU Feature

Transcription

1 Sandeep Khare Client Engagement Manager Order Management Hot SKU Feature Document number

2 Agenda Introduction Customer Scenarios Hot SKU Feature Hot SKU Properties Inventory Consolidation Agent Big Picture Hot SKU New Features 2

3 Introduction What is YFS_ITEM_INVENTORY table? YFS_ITEM_INVENTORY table is parent table for all the inventory tables in IBM Sterling OMS Installation. For any update or read operation on inventory related tables, this table (parent) is locked instead of locking multiple individual inventory tables. Why does IBM Sterling OMS locks YFS_ITEM_INVENTORY table? To avoid any kind of dirty read or update, Sterling OMS locks YFS_ITEM_INVENTORY table. Disadvantages of locking YFS_ITEM_INVETORY? When multiple transactions are working on same InventoryItemKey (Item) then only one transaction will get the lock and others have to wait. How to overcome the disadvantage Hot SKU feature is present in the product 3

4 Customer Scenarios (real life example needs to be given) Large number of orders for few particular Items Long running transactions 4

5 Hot SKU Feature Hot SKU properties needs to be enabled When the Item meets conditions set in customer overrides then Item turns Hot. When Item turns Hot then to register inventory availability product will lock Item Inventory table once. Once Inventory availability is registered then Item s supply or demand update will not require lock on Item Inventory table. Current picture of availability will be maintained locally at JVM level. Any further availability request will be addressed through this local availability picture. Hot Item works through YFS_INVENTORY_SUPPLY_ADDNL and YFS_INVENTORY_DEMAND_ADDNL i.e. insert any new supply and demand in them. Inventory consolidation agent runs continuously, this agent runs at a regular interval, picks records from additional table, sum up the supply/demand and update them in normal supply/demand table. JVM will continue to check if local availability of Item has dropped below threshold level (decided by hotsku properties). If yes, then Item lock will be required. Hot SKU feature works at JVM level. Other JVM where Item may not be hot will read updated supply and demand by doing union between normal supply/demand table and additional supply/demand table. 5

6 Hot SKU Feature properties (description from doc & explanation) yfs.hotsku.usehotskufeature=y Set this property to "Y" to use the Hot SKU feature yfs.hotsku.usetimeoutlocking=y The lock request timeout option in the Hot SKU feature is useful in reducing the amount of lock holding time by limiting the time the lock request blocks. This can be useful when you are primarily processing large orders (for example, over 50 lines per order) where the transactions could block for a very long time. yfs.hotsku.secondstoclassifyasabnormaltime=0.5 The Hot SKU feature tracks the time to lock inventory item records. If a lock request for an item is longer than the yfs.hotsku.secondstoclassifyasabnormaltime threshold, the Hot SKU feature increments the number of "abnormal" lock attempts for SKU. 6

7 Hot SKU Feature properties (description from doc & explanation) yfs.hotsku.numberofabnormallocksforswitchtohotsku=1 SKU turns hot when the count reaches the above property threshold. yfs.hotsku.numrequestsintrackingwindowtokeepashotsku=1 Interval of one tracking window during which "abnormal" lock requests are tracked. A subsequent window begins once the first window ends. yfs.hotsku.windowtimeinminutes=60 This is the time till the item remains hot. yfs.hotsku.showextramessagesasinfo=y This property shows the extra messages in the application server logs at info logging level 7

8 Hot SKU Feature properties (description from doc & explanation) yfs.hotsku.maxitemmapsizeinmemory=10000 Max distinct ItemID of hot item map size in memory. yfs.hotsku.qtymultiplier=30* Average requested quantity multiplier (This number can represent number of threads or JVMs which will running simultaneously) * Needs to be set based on the testing. * Properties description is from knowledge center 8

9 Hot SKU Feature properties (description from doc & explanation) 9

10 Hot SKU Feature properties (description from doc & explanation) 10

11 Inventory Consolidation Agent When Item is turned hot then JVMs will write data to inventory supply additional and inventory demand additional table instead of inventory supply and inventory demand tables. Inventory consolidation agent consolidates supply and demand from the YFS_INVENTORY_SUPPLY_ADDNL and YFS_INVENTORY_DEMAND_ADDNL tables. Consolidation is performed by summing up the quantities of additional supply and demand in the YFS_INVENTORY_SUPPLY and YFS_INVENTORY_DEMAND tables. This agent needs to be run aggressively. Large number of records in additional tables will slow down promising APIs. Promising APIs will do union of supply and supply additional while reading supply. Same is true for demand read operation performed by promising APIs. 11

12 Bigger Picture Challenges Traditionally retailers use to have couple of big warehouses in their fulfillment network. From past few years, there is change in traditional approach taken by retailers. They have started adding their store to fulfillment network. Now, typically a retailer can have around 1k-4k stores in their fulfillment network. With Multi Channel Retailing, retailers have to provide accurate and updated inventory picture to multiple channels. New business scenarios like Buy Online Pickup in Store. To address these new challenges, IBM has come with following new features in Sterling OMS Promising Server Smart Sourcing Edge Server Deployment Velocity Based RTAM New functionalities in Hot SKU feature 12

13 Hot SKU new features yfs.hotsku.lockitemoninventorychanges (OMS 9.4 FP4 ) When the yfs.hotsku.lockitemoninventorychanges property is set to N, inventory locking is avoided during adjustments. The contention would be reduced as the lock contention will move from the item level down to the item-supply or the itemdemand level. The overall response time is improved for supply or demand updates, as an additional lookup will no longer be needed. In addition to reduced lookups, item locking can be completely avoided. Also, since the lock on YFS_INVENTORY_ITEM no longer occurs, there would be an intrinsic lock applied at the row level for each supply or demand record. yfs.hotsku.lockonlyonlowavailability (OMS 9.4 Base product) The yfs.hotsku.lockonlyonlowavailability determines whether locking should be avoided until availability gets low. By default, the property assumes that the availability is checked for the first time and all the items have high availability. If this property is set to Y, then, it is assumed that the availability is high and lock will be avoided. If the property is set to Y, then, the availability calculation will not lock the YFS_INVENTORY_ITEM if the INV_INVENTORY_ITEM_LOCK doesn t exist for the demand type. yfs.hotsku.assumeunavailableonlocktimeout (OMS 9.4 Base product ) The yfs.hotsku.assumeunavailableonlocktimeout determines whether an item should be assumed unavailable if in case the lock cannot be acquired. This property is applicable only when yfs.hotsku.lockonlyonlowavailability is set to Y. If the yfs.hotsku.usetimeoutlocking property is set to Y and yfs.hotsku.assumeunavailableonlocktimeout is set to Y, it will be assumed that there is no inventory available for this item if a timeout occurs. Inventory will be assumed unavailable for this sourcing rule detail. If there are multiple sourcing rule details, then normal expansion will continue and lock will be attempted again 13

14 Hot SKU new features yfs.yfs.hotsku.registeravailabilityonlocktimeout (OMS 9.3 FP3) When a SKU turns hot for the first time, availability cannot be registered. This causes a lock on the YFS_INVENTORY_ITEM table to occur, unless it is specified by the yfs.hotsku.skiplockinventoryitemlist property. This property determines if locking is needed based on the inventory available. Locking occurs only when availability is low. yfs.hotsku.useavailabilityacrossnodes (92 FP 29) 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. yfs.hotsku.skiplockinventoryitemlist (92 FP 8) This property accepts a list of comma-separated items. For example, yfs.hotsku.skiplockinventoryitemlist=dvp ,tv0001a5f21,a1,a2,b,c,d4,e. The YFS_INVENTORY_ITEM table is not locked for these items initialized in the property. 14

15 Thank You!! 15