Reservations

A reservation links the request, item, location and optional lot to a quantity, state and expiry date. The reserve path selects an approved request and calculates eligible free quantity from posted signed movements less active reservations. It checks the source revision and actor scope before creating the claim. A claim protects the intended stock while leaving on-hand quantity unchanged.

• Approved source. Start with the approved request and its current revision.
• Exact claim. Record item, location, optional lot, quantity and expiry on the reservation.
• Single consumption. Confirm physical issue once, then pair the consumed claim with its posted movement.

Agree who may set a reservation expiry and how the team releases an abandoned claim. Rehearse simultaneous claims for the same lot and site before using this path in live work. Decide who sets claim expiry and who releases an abandoned active claim. Use the item’s base unit for both the request and reservation. For lot-tracked stock, confirm the selected lot is released and unexpired when the claim is made. Rehearse simultaneous approved requests for the same item, site and lot; each new claim must use posted on-hand less active claims. Agree who confirms the actual physical issue and how the receipt’s operation key is reused after a timeout.

Suppose two approved client requests need the same released lot. The first reservation claims a defined quantity and appears in Active stock claims. The second request must use the remaining free quantity, even though the on-hand figure has not changed. When the physical issue is confirmed, the claim becomes consumed and a negative posted movement records the actual stock effect. A repeated confirmation must use the existing operation receipt, not consume the same scope again. If the second request exceeds the remaining free quantity, the Warehouse Operator should leave it unclaimed rather than split the first claim invisibly. Once the first issue is physically confirmed, the workflow marks that claim consumed and appends its negative posted movement. The request reaches its executed state when the issue is recorded. Repeating confirmation with the same key should return the existing effect. For a cancelled unexecuted request, the Coordinator asks the claim owner to release any active reservation; a consumed claim cannot be released again.

• Active stock claims — Current claims by request, item, site, lot and expiry.
• Approved requests for issue — Approved work awaiting a physical issue.

Start with the client stock request path, then use review and correction when a decision or quantity needs attention. The data model shows how the records link, while roles helps the team rehearse access.