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
When working with our IBM partners, there was a tool that the team used for monitoring system health. We have implemented Sterling Inventory Visibility for our website (9/27/22). However, there is trepidation in the team as we have no way to see h...
Out of the box purge agent for clearing entries in INV_INVENTORY_ITEM_LOCK table
As part of the Hot SKU implementation, Lululemon has enabled granular locking at the Item / Node / demand level by adding following properties in Customer overrides.
This has improved the performance of the system by reducing database row lock co...
Publish In-Stock and Out-of-stock events only to COS Bucket
Currently, we cannot publish only the events to a cos bucket when the On hand inventory of an SKU becomes out of stock or comes back in stock. Instead, we are forced to use threshold values to control the publish, which is not very efficient. Ther...
It would be great if IBM could provide the ability to reset the data in Sterling IV or the ability to roll back to an older data snapshot. This will help the clients a lot.
Right now, we are asked to use APIs to do it, which is not efficient and...
Can we subscribe to the 'IV events' for different enterprises?
Events published based on separate inventory orgs, reduces the loads on the receivers, and it will increase the throughput.We are eagerly waiting for this enhancement from IBM, request you to please expedite this feature as soon as possible.
Need api to fetch total reservations made against the item (Aggregated Reservation Details)
At this moment there is no API which can provide total reserved quantities against an Item . This API is required to understand the aggregated reservations details for an Item , against all shipnodes . IF the shipnode is paased then the total quan...
Order Hub: Streamline Inventory Adjustments across Segments
In prior R2 release, we only had RTL and RTL Store Segments. As such inventory adjustments to a Store Segment occurred as follows: Run an inventory search for a specific Retail Store Segment (RTL-XXX). The inventory adjust logic automatically decr...
Transaction ID should be treated as unique by Sterling IV regardless of when it is posted. This will help to avoid duplicate transaction updates into the Platform.
Currently, Sterling IV has the ability to not reprocess a transaction with the same transaction id only for 15 mins. But at BigLots, we have business cases wherein the same transaction can be reposted after 15 days to one month. We have discussed ...
Move aggregation of Resource pool capacity consumption to asynchronous process to reduce locking
As of now manageCapacityReservation/reserveInventory/reserveAvailableInventory API calls are locking YFS_RES_POOL_CAPCTY_CONSMPTN when capacity is reserved against node/date/shift combination. This slows down reservations when pick capacity enabled.
A network level reservation has been made against a Distribution Group. The consumer proceeds through the checkout journey and now that reservation needs to be modified and made at the node level (eg consumer has now chosen to pick up in store). W...
Do not place IBM confidential, company confidential, or personal information into any field.