Oracle Cloud SCM study materials
Oracle Cloud SCM study resources

Lot Shelf-Life and Negative On-Hand in a Multi-Warehouse Inventory

Oracle Cloud SCM · Put your knowledge to work in context.

All case studies

Lot Shelf-Life and Negative On-Hand in a Multi-Warehouse Inventory

A life-sciences distributor manages three warehouses in Oracle Cloud Inventory. Item L-220 is lot-controlled and shelf-life-controlled with a 180-day total shelf life and a 60-day minimum remaining shelf life at shipment. Warehouse Dallas has 3,200 units across four lots: Lot D1 has 1,200 units expiring in 45 days; D2 has 900 units expiring in 120 days; D3 has 700 units expiring in 200 days; D4 has 400 units with no expiry date because it was received before shelf-life controls were enabled. A cycle count in Dallas shows a system quantity of 3,200 but a counted quantity of 3,150; the variance is in Lot D2. A transfer order to Warehouse Austin for 500 units has been stuck in 'In Transit' for 12 days. Austin shows a negative on-hand of -50 for L-220.

1. What is the most likely cause of the negative on-hand in Austin, and how should it be corrected?

Read the worked answer

A negative on-hand usually means a transaction consumed inventory that the system did not know was there. In this case the most likely cause is the transfer order: the 500 units were shipped from Dallas but not received in Austin, while an outbound transaction in Austin was allowed against expected supply. The stuck 'In Transit' status for 12 days supports this. A second possibility is an inventory issue or reservation in Austin before the transfer receipt was posted.

The correction path is:

  • Review the transfer order transaction history and confirm whether the shipment was actually dispatched. If the goods arrived, receive the transfer in Austin; that should offset the -50 and reconcile the 500 units.
  • If the goods did not arrive, investigate with the carrier and do not simply receive the transfer to make the number look right. A forced receipt would create false inventory.
  • Check why negative on-hand was allowed. The item or organization may permit negative balances, or the transaction may have bypassed availability checking. Restrict negative on-hand for lot-controlled items.
  • Post a cycle count or adjustment only after the transfer is resolved; otherwise the adjustment will double-correct the error.

The judgment is to trace the transaction before adjusting. A negative balance is a symptom, not the root cause.

2. How should the planner treat Lots D1 and D4, given the 60-day minimum remaining shelf-life rule?

Read the worked answer

Lot D1 has 1,200 units with 45 days remaining, which is below the 60-day shipment minimum. It cannot be shipped to a customer under the current rule, even though it is not expired. Options are to consume it in a non-shipment use, transfer it to a location with a different rule, sell it with a documented exception, or scrap it. The planner should not reserve it against open sales orders that require shipment.

Lot D4 has 400 units with no expiry date because it was received before shelf-life controls were enabled. That is a data integrity problem. The planner should assign a defensible expiry date based on the manufacturer's lot documentation or, if unavailable, quarantine the lot until quality provides one. Leaving it blank means the system may treat it as non-expiring and ship it ahead of compliant stock.

After fixing D4, the available-to-promise picture changes: D1 is effectively blocked for shipment, D2 and D3 are shippable if their remaining shelf life is at least 60 days at the planned ship date, and D4 becomes controlled. The planner should also set the item's shelf-life controls to apply at receipt so future lots cannot enter without an expiry date.

3. The Dallas cycle count shows a 50-unit shortage in Lot D2. What should the planner do, and how does the transfer order affect the count?

Read the worked answer

The 50-unit shortage in D2 is a real variance and should be investigated before adjustment. The planner should check recent transactions for D2: picks, shipments, transfer issues, and any unposted movements. If the 500-unit transfer to Austin included D2 stock, confirm whether the transfer issue was posted correctly and whether the quantity was deducted from the right lot. A lot-level system quantity of 900 for D2 may be overstated if a pick was posted to the wrong lot.

The cycle count should be approved as a 50-unit adjustment only if no transaction explains the difference. Approval should follow the company's count tolerance; a 50-unit variance on 900 units is about 5.6%, which likely exceeds an automatic tolerance and needs a second count or supervisor approval.

The transfer order also affects Dallas inventory. Once the transfer is received in Austin, Dallas should already have been relieved at shipment. If Dallas still shows the 500 units, the issue was not posted and the cycle count is masking a transfer problem. The planner should reconcile the transfer, then re-count D2, then adjust. Doing this in the reverse order can hide a process failure.