-
Inventory segmentation support for sourcing using IBM IV services and OMS
Customer has DCs in US and EMEA while they maintain inventory within each DC with different buckets including bulk inventory and common ATP. Common ATP is shared with the wholesale orders. Sourcing requirement is to use the bulk inventory of a DC,...
0
Future consideration
-
Bulk Supply/Demand API
Ability to call multiple API's with single API similar to multiAPI in OMS product. This will enable the customers to call multiple API's like get supplies, get demands with in same response for an Item and parse the data accordingly. Requirement...
1
Planned for future release
-
Ability to disable item and node combination for specific DGs
We need an ability to disable item and node combination for some specific DGs in IV whereas for other DGs this Item and Node Combination should be enabled. Currently IV does not seem to support this feature.
0
Future consideration
-
Lock Ship nodes at Delivery method level (Enhancement for IBM Sterling OMS v9.5)
This is very much needed for the retailers to maintain a granular Inventory visibility within store network and also to increase the business revenue by showing availability for a specific delivery mode instead of blocking the availability for the...
2
Delivered
-
Remove Rate Limits in Pre Prod environment
We have multiple applications which receive data from IV and so when ever those applications including IBM OMS have a deployment we will execute performance tests. Having rate limit on the pre-prod environment limits our ability to perform the tests.
0
Future consideration
-
IV doesn't allow syncing negative inventory postion like GIV does.
When an Absolute sync is done for Item-Node combination with -ve value IV ignores it. Where as we have this functionality in GIV
0
Future consideration
-
IV doesn't provide ability to differentiate various shipnodes by ship node type. As a result events published from IV cannot be filtered and/or distributed over separate channels within the external consumer by ship node type.
Currently in Ship Node configuration only Delivery method configuration is there need additional ability to differentiate DC vs Store so we can define various rules based on Ship Node type
0
Future consideration
-
Ability/ API to provide inventory availability considering the OPEN_ORDER/ BACKORDER in the response of IV service
The Get Network Availability API exposed in Inventory Visibility mandate Distribution Group to be passed in the input. The API does not consider OPEN_ORDER/ BACKORDER demand types while computing the availability in IV. This leads to inconsistenci...
3
Future consideration
-
Want to drill down to order data (PO , MFG Order) from inventory screen
From the inventory screen , user should be able to see the orders( Purchase orders , sales orders ) that is causing the supply and demand. This is currently possible in Inventory console screens
0
Future consideration
-
IV Full Sync: Ability to import inventory availability into OMS in batch mode and reset any items to o if there is no open relevant demands in OMS
The loadInvnetoryMismatch API is used to bulk load inventory (supply qty for each SKU/location combination) into OMS and this API has a feature (CompleteInventoryFlag) where the API can reset inv to 0 for any items that are not passed in the input...
1
Planned for future release