- Home
- Blog
- EDGEBIC How-To
- How to Change a Job Quantity After It Is Scheduled…
How to Change a Job Quantity After It Is Scheduled in EDGEBIC
To change a job quantity after it is scheduled in EDGEBIC, edit the order, save it, then run the scheduler again for that job. The saved edit changes order master data on its own. The bars on the plan keep showing the old quantity's hours until you re-plan, and that is deliberate: EDGEBIC by User Solutions never lets a data edit silently rewrite a plan the shop floor is already working to.
Quantity is one of the five fields that genuinely require a re-run. For the run itself, see how to run the scheduler in EDGEBIC. The rest of the library lives at the EDGEBIC how-to hub.
Before You Start
- The job exists on the Drive Schedule grid and already carries a Scheduled badge.
- You know whether the job has actuals logged. Check the Actuals Logged? column: a Y changes what the re-run will and will not touch.
- Work center calendars and capacity are current, because the re-run plans against them as they are right now.
The Steps
- Find the job on the Drive Schedule tab.
- Click the edit button in the row's Actions column. The Edit Manufacturing Order dialog opens with the same fields as order entry, pre-filled.
- Change the Quantity field. It must stay greater than 0 and no more than 1,000,000.
- Click Save Order. The dialog closes and the grid row updates immediately.
- Decide your scope. Tick only the rows you intend to re-plan. Unticked jobs keep their existing schedules and their reserved capacity.
- Run the scheduler. Press the schedule button and read the Confirm Scheduling dialog, which reports how many jobs are new and how many existing jobs will be rescheduled. For one job on its own, the Job View tab's Re-Schedule button is cleaner.
- Confirm and let the progress overlay finish.
What Changes When You Save
| Stage | What actually changes |
|---|---|
| Save the edit | The order's quantity. Nothing else. No capacity is claimed or released. |
| Before the re-run | Every bar, every date, and every hours figure still reflects the old quantity. |
| After the re-run | The job's operations are rebuilt with run hours computed from the new quantity, and capacity is re-claimed on every work center the job touches. |
| Recorded work | Completed and in-progress operations are preserved exactly. Only remaining steps are re-planned. |
| Other jobs | Jobs you did not tick keep their slots. New work is planned around them. |
The cost roll-up follows the quantity too, so the estimated hours and cost figures in the order's Cost Analysis panel reflect the new number after the save.
How to Check It Worked
Open the Job View tab and select the job. The summary panel's hours header shows Total Hours, Actual Hours, Remaining and % Complete for the whole job. Total Hours should have moved in proportion to the quantity change on the run-time portion of the work. Then read the per-operation grid: Sched Hours on each work center step is where the new quantity actually lands.
Back on Drive Schedule, check Item Start, Job End and Days Late. A quantity increase that pushes Job End past the Due Date turns Days Late red before the date passes, which is the warning working as intended.
Common Mistakes
Editing the quantity and walking away. The plan does not react to master data edits. Until you re-run, the Gantt, the dashboards and anything you print for the floor all describe the old quantity. Make the change, then run.
Re-running the whole plant to fix one job. Ticking every row moves bars that did not need to move, and shop floors distrust plans that churn. Tick the one job, or use the single-job Re-Schedule button on Job View. How to schedule a single job covers the narrow path.
Assuming a bigger quantity only stretches that one job. It does not. The extra hours are claimed from the same finite work center capacity everything else competes for, so the jobs queued behind it on that machine move too. Check the work center's load after the run, not just the job you edited.
Cutting a quantity on a part-built job and expecting the hours to tidy themselves. Recorded work is never moved or deleted by a reschedule. If operators have already logged more hours than the reduced plan calls for, the variance stays visible in the roll-up. That is the honest answer, and it is usually the one you want.
What to Do Next
If the quantity change also moves the promise, how to change a job's due date is the companion task. If the re-run put the job later than you can live with, work the checklist in how to see why a job is late before you start moving bars by hand. The EDGEBIC product page covers the platform, and what is production scheduling covers the discipline for anyone new to it.
Expert Q&A: Deep Dive
Q: The customer raised an order from 100 to 250 pieces. What is the safest sequence?
A: Edit the order first, then re-plan only that job. Open the row's edit dialog, set Quantity to 250, and save. Now decide the scope: if the job has not started, tick just that row on Drive Schedule and press Schedule + Re-Schedule, and read the confirm dialog to verify it says one existing job will be rescheduled. If the job is already running, use the Job View tab's Re-Schedule button instead, which re-plans that job alone and leaves every other job's reservations intact. Either way, check the work center load afterwards: 150 extra pieces is real hours that have to come from somewhere, and the jobs queued behind it on the same machine are the ones that pay.
Q: I cut a quantity in half but the job still finishes on the same day. Why?
A: Two common causes. First, you have not re-run the scheduler for that job, so the bars are still the old plan. Second, the job's span may not be driven by run hours at all: setup time, queue time between operations, transit days, or simply waiting for a busy work center to free up can dominate a short job. Halving the pieces halves the run hours, not the setup or the waiting. Open the job's operation rows and compare Sched Hours per step before and after the run to see where the time actually sits.
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
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.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
