How inventory demand is handled on the promising server

Inventory is handled with an event. Review the following samples of how inventory demand is handled.

As shown in the following diagram, inventory demand is propagated from an Order server to the Promising server using the EXTERNAL_DEMAND_CHANGE event. The published demand is processed by an integration agent running on the Promising server. The agent calls the reserveItemInventoryList API to create inventory reservation based on data in the published XML files.

PromisingServerAndAvailability

Therefore, inventory demands are created on the Promising server when inventory reservations are created. In other words, inventory demand is not created directly for Order and Promising server integration. It is created using inventory reservation.

The following table provides an example of a simple order’s life cycle, showing how inventory demand creation occurs on the Promising server.

Transaction Order server running without Promising server. The inventory demand table is updated directly. Order server running with Promising server. The inventory demand is updated using Inventory Reservation.
  Inventory Demand Inventory Reservation
Create order OPEN_ORDER OPEN_ORDER
Schedule order SCHEDULED SCHEDULED
Release order ALLOCATED SCHEDULED
Ship order Demand becomes zero Reservation is deleted.
Note: Reservations created for orders use ReservationID as the OrderHeaderKey.