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.