Skip to content

Purchase Orders from Deficit

The production orders deficit report shows what the stock is short of for the planned production. This service takes the next step: it creates draft purchase orders — one per vendor and location, with rows for exactly the shortage.

Where to find it: Modules → Production (also in modules: Purchase Orders) → Maintenances → Purchase Orders from Deficit

What it does

  1. Counts the shortage the way the report does with "Show vendor orders" ticked, per location: the production orders' need minus the stock minus what is already ordered from vendors and not yet received — approved orders and drafts alike, unless they are closed.
  2. Finds the vendor of each item — from the latest approved goods receipt of that item. The system has no separate "item vendor" card, so the purchase history is the source.
  3. Creates draft orders: one per vendor–location pair. The header and rows are filled by the same logic as the purchase order window: currency, payment terms and VAT from the vendor card; name, unit and purchase price from the item card; the sums are calculated.

When it has run, the service window lists the numbers of the orders it created. What is left is to review them, adjust prices or quantities if needed, and approve them — the service approves nothing itself.

Run parameters

The same filters as the deficit report: Product order (number), Structure, Location and the production orders' Status (Created, Started, or both — "All"). Empty fields mean no restriction.

Typical situations

Run a second time. No new orders: the drafts already created cover the shortage, and the report no longer shows it. If a new production order has appeared since, the service creates an order only for the new difference.

An item has never been bought. There is nowhere to take a vendor from — the service names such an item in its message and creates no order for it. Order it by hand; after its first goods receipt the service will take the vendor from there.

One order was not created. For example, the vendor card has no payment terms — the same refusal as in the window. The other vendors get their orders, and the message says which one failed and why.

The quantity is not a round number. The service orders exactly the shortage, without pack multiples or a minimum batch — adjust the quantity in the draft before approving it.

The service refuses access. It creates purchase orders and reads production orders, so only a user with the right to create the former and view the latter can run it.

Where to look next