Skip to Main Content
IBM Sterling


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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Created by Guest
Created on Oct 12, 2023

On a reallocation request, Inventory update in IV should be done synchronously, and should not be through messages posted to internal queues in an asynchronous way

On a reallocation request, Inventory update in IV should be done synchronously, and should not be through messages posted to internal queues in an asynchronous way.

Below is the use case under consideration. The asynchronous update to IV (as mentioned in Step 3 below) should be done rather synchronously for the inventory update to be done in IV immediately, so that backorder scenarios can be avoided.

1. Create Order with certain qty, for eg. 20 qty and schedule

This creates SCHEDULED Demand in IV qty 20

2. ChangeOrder to update address and reallocation which internally calls unscheduleOrder and drops a message for ScheduleOrder in queue.

3. On unscheduleOrder, system generates 2 demand updates one for SCHEDULED quantity -20 and one with BACKORDER.EX Qty 20. These updates are dropped to queue at the time of transaction commit. Subsequently update messages are processed by IV_ADJUST_ID Integration server.

4. At the same time scheduleOrder message is also dropped to another queue. This message is processed by another integration server which tries to schedule the Order.

Note: At this state both integration servers are going to process their respective messages parallelly.

5. If the integration server which is used for schedule picks up its message before demand updates are processed by IV then the ScheduleOrder integration server will not have inventory available and will result in backorder.

6. If the integration server which is used for schedule, picks up its message after the demand updates are processed by IV then scheduleOrder integration server will have inventory available and it will be able to schedule the Order. Since the system is distributed and updates are processed asynchronously there may be situations where the updates are not happening in the same sequence. 

  • Admin
    Sampson Wong
    Reply
    |
    Jan 11, 2024

    Fix in development.