This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Ability to schedule on hand inventory publish for a set of DG’s or nodes
Currently, the IV events for inventory publish only include available units (supply - demands - safety stock). We have a need to schedule (intra day changes and nightly sync) the publish of ON HAND units for SKU/location level to certain external ...
Node level safety stock values considered when calculating Network level SS
This feature would allow retailers who already define safety stock at node level to more easily leverage the new IBM safety stock rules because the values they set at node level can automatically be considered to create a network level value
Include an Identifier to differentiate between the Inventory dbavailabilitycache message triggered by a delta vs full sync(publish_all trigger)
In our integration with IV services, we encountered scenarios where a full sync is being consumed by MW system and in the interim delta change comes in, the delta change processing is delayed because of the lengthy processing of full sync messages...
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
Node Configuration Attributes to specify Inventory Restrictions that impact available inventory for consumption
Note setup 1) Supported delivery methods, SLAs by delivery methods, calendars and capacities for nodes. 2) There should be a way to specify conditional values for node parameters. A few example use cases 1) For a Node, Delivery Method, SKU --> ...
Do not place IBM confidential, company confidential, or personal information into any field.