Troubleshooting
Problem
Inventory management (GIV) and order management are implemented on separate Sterling instances. Unexpected inventory updates when Order moves between different statuses in OMS.
Symptom
When reservation is created, node capacity is consumed and when reservation is cancelled , the consumption is replenished.
Example :If initial node capacity is 10 and reservation is made for 5. Available node capacity is 5. When order is ship confirmed same day, GIV receives demand adjustment message and cancels the reservation from demand ALLOCATED. This removes the consumption in YFS_RES_POOL_CAPCTY_CONSMPTN table and available node capacity is again reflected as 10. It means that even though order fulfillment process consumed 5 units from node capacity, node capacity is replenished back to 10 and it will result in scheduling more orders than node capacity can fulfill.
Cause
As per current design, Promising server does not support Node Capacity for releases mentioned but we might include this in future product release.
Resolving The Problem
Scenario mentioned above is working as per the design. Cancelling of reservation removes consumption that the reservation made as promising server does not support node capacity.
Solution : When shipment is confirmed supply is reduced . As a part of that supply adjustment call manageCapacityReservation to make necessary quantity consumption that got shipped.
Was this topic helpful?
Document Information
Modified date:
10 May 2022
UID
swg21664351