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.

Ability/ Option to clean up data loaded into IV via a self-serve option/ API

Currently, IV APIs do not give the option to clean up the data loaded into it via the integration with OMoC. There are APIs to perform adjustments or to zero-out the supplies/ demands and hence availability in IV (and thereby the process to clean up data), they could be leveraged for small dataset. However, when the volume of data is large, the effort involved to carry out the cleanup is time-consuming and error-prone as there is no single API to perform the cleanup in IV as a whole in a generic manner. In certain cases, as part of testing there could be scenarios when inventory in OMoC IV can go out of sync.

Hence, this necessitates the ability/ option to clean up data loaded into IV via a self-serve option/ an API.

  • Guest
  • Apr 10 2019
  • Submitted
How will this idea be used?

To elaborate, let us say we have OMoC instance has an inventory item (I1) with a certain supply (say 100 qty) and the same is in sync with IV as well. We are planning to truncate the transactional data and clean up all the transaction data (including inventory) on OMoC instance and load it with fresh set of data. If an adjustment happens to this item (I1) as part of this load (say for 10 qtys). the same will be sent to IV yielding the supply update in IV for that item to be 110 and OMoC will say the supply to be 10.

 

Hence, it would help to provide an option to truncate such supply/ demand data in IV just like we have the option to clean up transaction data in OMoC. 

What is your industry? Computer Services
What is the idea priority? Medium
  • Attach files
  • Guest commented
    10 Apr, 2019 03:26pm

    It is crucial during Testing and Deployment that we be able to synchronize the inventory between OMS and IV.   Client expectations are that these two systems will work in conjunction with one another and always be in sync.   It will become a very common request by clients to be able to do this. 

  • Guest commented
    10 Apr, 2019 02:52pm

    Going forward, as more customer implement IV this is going to be a very common ask.