Troubleshooting
Problem
Attempts to implement Node Capacity feature with Release as Unit causes incorrect comsumption of capacity orders in IBM Sterling Order Management.
Symptom
Steps to reproduce:
- Set only one Fulfillment Node.
- Define Node Capacity with Unit as Release against the Fulfillment Node.
- Set the Node Capacity value as 1 per working day for this Node Calendar.
With this set, if you reserve the Inventory against the node, it consumes the capacity for the day. If there's another reservation, it gives AvailableShipDate of next day.
- Create Order 1 and then Order 2.
The reservation for Order 1 happens first, the Order is on hold and not yet released. But the capacity is already consumed on Node for today against this Order.
Now, even if Order 2 gets reservation, the ShipDate given shall be of next Day. Though, the Holds are getting cleared for Order 2 first and moved to Released status.
Expected Behavior: In this case Order 2 should consume the capacity when released and not Order1.
Cause
Capacity is not released by the Order1.
Resolving The Problem
Call the manageCapacityReservation API to release the capacity used by Order1.
Sample input xml :
<CapacityReservationList>
<CapacityReservation Operation="Delete">
<CapacityConsumption ConsumptionDate="2014-01-21">
</CapacityConsumption>
</CapacityReservation>
</CapacityReservationList>
Once the capacity will get released, Order 2 can use that capacity.
[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Distributed Order Management","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.2.1;9.2","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21667577