EDGEBIC How-To

How to Issue Material to a Job in EDGEBIC

User Solutions TeamUser Solutions Team
|
6 min read

To issue material to a job in EDGEBIC, you post a manual issue that draws the quantity down from stock as a positive number. In EDGEBIC by User Solutions a manual issue records a physical pick the scheduler does not already account for, and it becomes one permanent signed entry in the ledger. This post covers where the action lives, the sign rule that trips people up, and how to keep it distinct from the automatic consumption a scheduling run performs.

There are two ways material leaves stock for production work: you record a pick by hand, or the scheduler nets an order against on-hand for you. This post is about the first. For the automatic route, read how to let a job consume from stock. Availability varies by installation, so check which inventory features your build exposes before you build a picking process around them.

Most material leaves stock through the scheduler, which nets orders against on-hand automatically during a run. The manual issue exists for everything that route does not cover: the pull that happened outside a scheduled order, the sample sent to a customer, the scrap written off, the kit staged for a job that was never entered. Recording those by hand keeps on-hand honest, because a balance that ignores real draws quietly overstates what is available and leads the projection to promise stock that is already gone. The rule of thumb is simple: if the scheduler will not see it, you post it. That keeps the manual issue and the automatic consume from ever counting the same material twice.

Before You Start

  • The product is a stocked item, so the ledger tracks its movements.
  • You know the quantity being pulled and which job or purpose it is for.
  • You have confirmed the scheduler is not already going to consume this same material during a run. If it is, the engine posts its own issue and a manual one would double the draw-down.

Post the Issue

  1. Click Inventory in the left navigation.
  2. Select the product being consumed in the dropdown at the top of the view.
  3. Open the Adjustments sub-pane.
  4. Enter the quantity consumed in the Qty field as a positive number. Do not negate it.
  5. Type a Comment that names the job or reason, such as "Kit pull for job 7781".
  6. Click Post Issue.

The service takes your positive quantity, applies the negative sign for you, and writes an issue entry. This is the single most common stumbling point: the quantity you type is the amount leaving stock, stated positively. A negative value is rejected.

A Note on the Job Reference

A manual issue posted from the Adjustments pane records the draw against the product and carries your comment, but it is not linked to a specific order through the pane. That is why the comment matters: naming the job in the comment is how you tie an unplanned pick back to the work it fed. When an order is scheduled and the engine consumes stock for it, that engine-posted issue does carry the order reference automatically, which is what separates the two kinds of issue in Transaction History.

What Changes When You Post

A new ledger entry is appended with an issue type and a negative signed quantity. On-hand recalculates from the full ledger sum inside the same transaction, so it drops by exactly the amount you entered. Every pane on the Inventory view refreshes, and the projected balance rows fall to reflect the smaller quantity on hand.

Because the projection reads current on-hand as its opening balance, a manual issue can move a projected stockout date earlier and can reduce the available-to-promise figure. If the pull was significant, expect the calendar to react.

Issuing Below Zero

The system lets you issue more than is on hand and drive the balance negative. This is deliberate rather than a bug: negative on-hand is allowed so that a real over-pull is recorded honestly instead of being silently blocked or clamped at zero. A negative balance is flagged as a warning by the plant-wide anomaly checks, which surface products sitting below zero so a planner can reconcile them, usually by posting a receipt for the shortfall once the paperwork catches up. If you never want to issue below a buffer, that is a separate control on the product, the respect-safety-stock floor, not a property of the issue action itself.

Issue Versus Adjustment for Shrinkage

When stock disappears for a reason you cannot fully attribute, decide whether it is an issue or an adjustment. An issue records a known consumption: material left for a specific purpose. An adjustment records a reconciliation: a count came up short and you are correcting the book to match. Scrap pulled to feed a job is an issue; stock that evaporated between counts with no known destination is an adjustment. Both reduce on-hand, but the entry type is the story an auditor reads later, so pick the one that describes what actually happened.

How to Check It Worked

  1. Open the Transaction History pane for the same product.
  2. Confirm a new row appears with an issue type, your comment, and a negative quantity equal to what you pulled.
  3. Read the Balance After column on that row to see on-hand immediately after the issue.
  4. To isolate hand-entered picks from engine consumption, toggle Show Manual Only on. Your issue stays visible because it carries no order reference; engine-posted issues disappear because they are pegged to an order.

Common Mistakes

  • Entering the quantity as a negative. The service negates a positive figure for you. A negative input is rejected, not honored. Type the amount leaving stock as a positive number.
  • Double-counting against the scheduler. If the job is scheduled and the engine will net it against on-hand, do not also post a manual issue. The engine posts its own consume issue with the comment "Schedule Transaction". Two issues draw the stock down twice.
  • Leaving the comment blank. A manual issue is not linked to an order through the pane, so the comment is the only thing tying the pull to its job. A blank comment leaves an unexplained draw-down.
  • Forgetting there is no delete. The ledger is an audit record. To undo a mistaken issue, post an equal and opposite movement rather than trying to remove the row.

Once you can record a hand pick, learn the automatic side in how to let a job consume from stock, see the full manual-movement set in how to record receipts, issues and adjustments, and browse every task in the EDGEBIC how-to library.

Expert Q&A: Deep Dive

Q: A supervisor pulled 40 units of raw stock to the floor for a rush job that was never entered as an order. How do I record that draw-down?

A: Post it as a manual issue so on-hand reflects reality. Select the product, open the Adjustments pane, enter 40 as a positive quantity, and type a comment such as Kit pull for rush job 7781, no MO. Click Post Issue. The service negates the figure, appends one issue entry, and on-hand drops by 40. Because there is no order behind it, the entry carries no order reference and shows up when you filter Transaction History to manual-only movements, which is exactly where an unplanned pull should be visible for later reconciliation.

Q: How do I make sure I do not double-count when the scheduler is already going to consume stock for the same job?

A: Do not post a manual issue for material the scheduler will net automatically. If a job is scheduled and its product has enough on-hand, the engine posts its own consume issue during the run, comment Schedule Transaction, pegged to the order. Posting a manual issue on top of that draws the stock down twice. Reserve manual issues for draws the scheduler cannot see, and verify the split by filtering Transaction History: manual issues carry no order reference, engine issues do.

Frequently Asked Questions

Ready to Transform Your Production Scheduling?

User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team

User Solutions Team

Manufacturing Software Experts

User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.

Let's Solve Your Challenges Together