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.

RTAM - Cannot run RTAM in multi threaded mode

Refer this PMR -


Let me consider a scenario here

Total Records - 13000

Max Record per thread - 5000

I have configured 3 thread.


Thread 1 picks 5000

Thread 2 picks 5000

Thread 3 picks 3000


Thread 3 completes the job quicker than the other threads and calls the EOF message. In other words, Service to execute on Completion will be execute anytime getJobs retrieves 0 messages.

Requirement -  EOF message needs to be sent once after all the items have been processed. Essentially  when the executeJobs doesnt have any records to process.

If we have to implement sterling as store inventory master, it becomes pertinent that such features should be included out of the box in product, else we can not reliably publish store inventory to external systems.




This is URGENT PRIORITY for us.


Thank you

Abhijit Kumar Roy

OMNI Architect, Eileen Fisher

  • Guest
  • Sep 26 2018
  • Future consideration
What is your industry? Retail
How will this idea be used?

We have requirement to send the Store Inventory Full sync every night to Order Capture Systems. With increasing SKU levels and increasing Stores, it is turning out to be a deterrent. Plus we have a very narrow window for full sync as there are other reconciliation among RMS and Wholesale systems take up most of the Store off hours. We just cannot keep a single thread running.

  • Guest commented
    27 Sep, 2018 06:07pm

    This is an excellent call out! This has been a major sore point for some of my previous clients who have a large number of SKUs (~2mil) for which Inventory needs to be published and there is no sure fire way of processing these for over 300 stores at 1 go without multi threading.


  • Guest commented
    27 Sep, 2018 06:04pm

    IBM should fix this.  Pretty impactful.

  • Guest commented
    27 Sep, 2018 05:54pm

    I'm surprised to learn that IBM QA didn't catch this issue. Multi-thread message processing is a requirement for medium to large retail companies. The danger is that if one of your clients does not catch this bug in their QA and it will go to production - this specific issue will have an impact on company bottom line as RTAM process will be stopped prematurely and not full SFS inventory posted to the web. Item availability on a web will be impacted and your clients will lose revenue.


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.