Courses / Commodity Trading Operations & ERP

Status flags: the gate quantity does not override

An ERP can refuse a materials issue even when there is plenty of stock, because a status flag, not the quantity, is doing the gating.

Module 12 of 12 (optional)3 lessonsAbout 20 minQuiz: 6 questions
Execute

Lesson 1 · free to read

Two independent gates: quantity and status

A 'transfer quantity cannot exceed available quantity' error reads as a stock shortage. It can mean something else entirely: there is plenty of stock, but the system will not move it because of its status — a flag an ERP carries on every lot or bin alongside quantity, separate from it, and checked separately.

Worked example (figures invented). A grain-milling customer on Acumatica tried to issue 1,000 bushels of a wheat lot to a production order. The inventory summary for that item showed 9,000 bushels on hand at the location — nine times the quantity requested — and the issue still failed. Of that 9,000, only 1,500 bushels carried the system's 'released' (green) status; the remaining 7,500 carried a blank status, neither released nor explicitly on hold. A materials issue only draws from released stock, whatever total the on-hand summary shows. The requested 1,000 bushels were, in fact, more than the 1,500 released — but a user reading only the 9,000 total has no way to see that, and reasonably assumes the system is wrong.

The summary screen and the movement screen answer different questions. One totals quantity across every status; the other only ever offers released quantity. Treating the first as a proxy for the second is the trap.

What a system must therefore do: keep quantity and status as two independent fields on every lot, and never let a total that ignores status stand in for "what can actually move".

The rest of this module

  1. Why a receipt that skips QC still needs an explicit status
    Nothing sets a lot to released by itself. An item that requires inspection gets released by the QC pass; an item configured to skip QC needs the same status set some other explicit way, at receipt.
  2. What a system must therefore do
    Show quantity by status, distinguish a quantity failure from a status failure, and audit who left a lot unreleased.

Carry on with the course

The other lessons and the quiz are in the course itself, where your progress is saved and counts towards the certificate: Commodity Trading Operations & ERP.