My Firmed Job Quantity Is Higher Than the MPS Bucket: Causes and Fixes

A firmed job quantity that sits up to one unit above its MPS bucket is rounding, not an error: a bucket can hold a fractional quantity, a job cannot, and the firm step rounds up rather than down. EDGEBIC by User Solutions makes that choice deliberately so a firmed build never comes in under what the planner committed.

The opposite direction has a different explanation. When a job quantity is materially lower than its bucket, the build was usually netted down against stock, which is also correct. This post covers both cases and how to tell them apart, and it sits with the other planning symptoms in the EDGEBIC troubleshooting guide. For the firming step itself see how to firm an MPS quantity into a job, and for the module see the master production schedule explained.

What You Are Seeing

You committed a quantity in the MPS grid, firmed the bucket, and the job that appeared carries a different number. Sometimes it is one unit higher. Sometimes it is a good deal lower. Nobody edited the job in between.

Why It Happens

Cause 1: Fractional Bucket, Whole-Unit Job (the Small Difference)

An MPS bucket quantity is stored with decimals so a planner can commit a figure that came out of a calculation rather than a count. A job quantity is a whole number of pieces. The firm step converts one to the other by rounding up.

Rounding up is the deliberate direction: a job that rounded down would build fewer pieces than the plan called for, and the shortfall would surface at the end of the routing. A difference of up to one unit is expected and needs no action.

How to tell: the bucket quantity has a decimal part and the job is exactly the next whole number up.

Cause 2: The Build Was Netted Down Against Stock (the Large Difference)

If part of the demand is already covered by inventory, the scheduling run builds only the balance. A bucket of 110 with 25 units available produces a job for 85. The bucket keeps recording what you planned; the job records what has to be made.

How to tell: the difference is more than a unit, and the product's transaction history shows a stock movement against the job for the covered quantity.

Cause 3: The Bucket and the Job Have Drifted Apart Since Firming

Once a bucket is firmed, the job is the live object. Editing the job quantity afterwards does not revise the bucket, so the two can legitimately differ because someone changed the job on purpose.

How to tell: neither rounding nor netting explains the gap, and the job carries an edit.

How to Fix It

• For rounding, do nothing. The behavior is correct. If the fractions matter for costing, enter whole numbers in the bucket so the two figures agree from the start.
• For netting, confirm rather than correct. Filter the product's transaction history to the job number and check the stock movement covers the difference. How to audit the inventory ledger for a part covers the reading.
• For an edited job, decide which number is authoritative and note it. The bucket is a plan; the job is the commitment.
• Reconcile released rows periodically so a bucket that no longer has a live job behind it gets re-firmed or removed.

How to Diagnose It, in Order

1. Read the bucket quantity and check for a decimal part. If the job is the next whole number up, you are done.
2. Compare the size of the gap. A gap under one unit is rounding. A larger gap is not.
3. Check the product's transaction history filtered to the job. A stock movement explains a netted-down build.
4. Check whether the job was edited after it was created from the bucket.
5. Re-run scheduling only if the coverage looks wrong, not merely to make the numbers match.

The Number That Should Not Be Reconciled Away

It is tempting to force bucket and job to be identical. Resist that where netting is involved. A bucket that says 110 and a job that says 85 is a plant correctly avoiding building 25 units it already owns, and flattening the difference by raising the job would build stock you do not need. The right reconciliation is to understand each number's role: the bucket is the demand-side plan, the job is the supply-side commitment after coverage.

How to Prevent It

• Enter whole-unit bucket quantities whenever demand allows. It removes the rounding question entirely.
• Expect netting to change job quantities on stocked products, and check coverage before treating a smaller job as a mistake. What is consume-from-stock netting explains the mechanism.
• Review released buckets on a rhythm, so a bucket whose job was removed is caught while you still remember the decision, which is the failure covered in my MPS firmed quantity did not become a job.
• Keep on-hand balances trustworthy, because every netting decision reads them. A drifted balance produces job quantities that look inexplicable and are simply built on a bad number.