IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

IV event to publish availability only when item threshold is reached.

Currently IV publish event : ProductAvailabilityToSell.ShipNodeChange when the availability for an item at a ship node changes.

Similarly IV event DgAvailabilityChange is published when the availability for an item in a DG changes.

This results in a lot of event messages generated and published to Webhook/IBM Cloud Object Storage.

A configuration can be provided for IV tenant to either publish events for all Availability changes or to publish only when threshold levels are reached. Similar to RaiseEventOnAllAvailabilityChanges flag for RTAM.

When this flag to publish an event for all changes is set to 'Y', ProductAvailabilityToSell.ShipNodeChange events can be published for all availability changes, otherwise, events can be published only then Threshold limits are reached for Item /Distribution Group.

  • Guest
  • Jan 15 2021
  • Delivered
What is your industry? Retail
How will this idea be used?

ProductAvailabilityToSell.ShipNodeChange event messages will be published to the Website to update the inventory cache.

If we can send ProductAvailabilityToSell.ShipNodeChange messages only when threshold (High,Medium,Low) levels are reached , this will reduce network traffic for inventory updates.

When ProductAvailabilityToSell.ShipNodeChange event is published for all inventory changes (within threshold or outside threshold) a large number of messages are generated which also impacts middleware/front end infrastructure processing inventory messages.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.