What Stock a Job Actually Drew From Inventory in EDGEBIC

There is a window in EDGEBIC that shows exactly what one job took out of stock, and the only way to open it is a double-click most planners never try. It answers a question that comes up constantly and is otherwise awkward to settle: did this job draw raw materials in the normal way, or was part of it satisfied straight off the shelf without any work at all?

This post covers how to open it, how to read the two columns that carry the meaning, and what it is and is not good for. It sits under the EDGEBIC planning guide.

Opening It

In EDGEBIC by User Solutions, open Job View for the job you are interested in. In the job tree, find a Product or material step, then double-click one of its actuals cells. The Inventory used by this job window opens, headed with the job number.

That double-click is the entire access route. There is no button, no toolbar entry and no menu item that opens this window from anywhere else in the product, which is the single reason it stays undiscovered so long. If you are new to the surrounding screen, the Job View cockpit covers the tree and the grid it lives in.

If the job took nothing from stock, the window still opens and shows a short message saying so. That is a useful answer in itself rather than a dead end: it rules stock out and sends you looking elsewhere.

The Summary Line, Then the Grid

The window opens with a plain-language summary at the top, followed by a grid of the individual movements.

Most of that is self-explanatory. Two columns carry nearly all the meaning.

Level: The Column That Answers the Real Question

Level separates the two entirely different things that can happen to a job.

Finished item means stock of the product itself covered part of the order. That portion needed no work at all: no saw time, no mill time, no operations scheduled against it. The order was satisfied out of inventory.

Material means components were drawn out of stock to build the order in the ordinary way, which is what happens on a normal job.

This distinction is why the window is worth knowing about. When a job finishes suspiciously fast, or its operations appear never to have been scheduled, a finished item row for the full quantity explains it in one glance. That is the consume-from-stock behavior working as designed, covered in when an order is fully satisfied from stock. Without this window, the same job looks like a scheduling fault.

A single job can carry both kinds of row. Partial coverage from finished stock plus materials drawn for the remainder is a perfectly normal pattern, and the level column is what lets you read the split.

Movement: Taken, Returned, and the Grayed Rows

Movement reads taken or returned. A reversed movement is drawn grayed and in italics.

Nothing disappears here. Stock taken and later given back leaves both halves on the record, because inventory movements in EDGEBIC are append-only, as explained in why inventory transactions are append-only. The grayed italic styling is how a reversal announces itself, so a pair that cancels out is obvious without having to do arithmetic on the quantities.

Treat grayed rows as history rather than a current draw. They are left visible on purpose so the numbers can always be traced back.

Why: Where the Movement Came From

The Why column names the cause. For stock drawn during planning it reads Schedule Transaction, which is the scheduler consuming stock as part of a run rather than anyone posting a movement by hand.

That wording matters more than it looks. Stock is drawn while the scheduler runs, not when you save a job and not when you tick a field on a product. Until a run happens, nothing has been consumed and this window has nothing to show. A movement labeled as a schedule transaction is therefore also a timestamp: it tells you which run made the decision.

Movements posted by hand carry the comment that was typed at the time instead, so a receipt, an issue or a count correction shows its own reason rather than the scheduler's.

A Worked Example

A job is raised for 100 units of a product, and 40 are already on the shelf.

Before the run the job looks like a 100-unit build, with the full routing and the full machine hours behind it.

After the run it is a 60-unit build. The scheduler consumed the 40 that existed and scheduled work for the shortfall only. Every downstream number follows the shortfall rather than the order: hours, capacity, and the materials the routing needs are all sized against 60, not 100.

Open Job View for that job, double-click an actuals cell on the product step, and the window states it plainly: 40 of the finished item came off the shelf, so that much of the order needed no work. The grid backs the sentence up with a finished item row for 40, taken, dated to the job's need date.

This is the case that sends planners looking for a bug. The routing says one thing, the schedule shows less work than the routing implies, and nothing on the Gantt explains the difference. The explanation is a stock draw, and this is the screen that says so in words.

Partial coverage is the normal middle case. Stock rarely covers an order exactly. When it covers part, the scheduler builds only the remainder, and this window shows the split: a finished item row for the part that came from stock, and material rows for the components drawn to build the rest.

What It Is Good For

Explaining a job that looks too easy. The most common use. One glance at the level column tells you whether the plant was skipped because stock covered the order.

Settling an argument about material. The grid names what moved, how much, when, and why, for that job specifically.

Confirming a reversal actually happened. If someone corrected a movement, the returned row is right there beside the original.

What It Is Not

It is not a search. The window answers what one job took. It cannot tell you which job consumed a quantity you are trying to account for. For that, start from the EDGEBIC inventory ledger, which records every movement with its source, then come here once the ledger has named the job.

It is not a reservation view. What a job has already drawn is a different question from what is currently earmarked for future jobs, which is the inventory reservation map.

It is not editable. It reports movements, it does not post them.

The Habit Worth Forming

When a job's actuals look wrong, check this window before you check anything else. A large share of "the schedule did not plan my operations" reports are not scheduling problems at all. They are stock quietly doing its job, and this is the one screen that says so plainly.

For the planning decision that produces this behavior in the first place, read how build-to-stock and consume-from-stock work together.