To reopen a completed operation in EDGEBIC by User Solutions, clear its actual end date. That single value is what separates frozen history from live work. With it removed, the operation returns to in progress, the next reschedule stops skipping it, and any hours still owed get planned forward onto the same work center.
Completing a step is covered in how to complete an operation. This is the reverse.
Before You Start
| Prerequisite | Why |
|---|---|
| The job is not marked complete at the order level | A completed job locks actuals entry; use Reopen Job first |
| You know whether the hours are wrong too | Reopening clears only the end date, never the logged values |
| You intend to reschedule afterward | Reopening changes the classification; re-planning is a separate run |
Step 1: Choose a Route
Three routes clear the same value. Pick whichever screen you are already on.
| Route | Where |
|---|---|
| Untick the mark-complete option and save | The Log Actuals dialog for the operation |
| Clear the Actual End cell | The Job View grid row, double-click to open the editor |
| Right-click the bar and clear the operation's actual end only | The Schedule View Gantt |
The Log Actuals route is the one to use when you are also correcting hours, because both changes land in the same save.
Step 2: Clear the Actual End
Remove the value and save. The operation immediately shows as in progress: an actual start with no actual end.
If you also need to remove hours that were logged in error, zero every Actual Hrs and Actual Pcs cell in the grid and save without ticking mark-complete. Clearing hours does not clear the actual start, and clearing the actual start does not clear the end. Each of the three values is cleared on purpose, which is exactly why an accidental reopen costs nothing.
Step 3: Reschedule
Reopening changes how the engine classifies the step. It does not by itself re-plan anything. Run a targeted reschedule for the job (the Re-Schedule button on the Job View tab, or on the Schedule View tab after saving changes) so the remaining hours get a real slot and the downstream steps queue behind the corrected picture. The safe way to run it is in how to reschedule safely.
What Changes When You Save
| Surface | Effect |
|---|---|
| The operation's state | In progress: actual start present, actual end removed |
| Logged hours and pieces | Untouched, still on the days they happened |
| The Gantt bar | Drops the completed shade, shows the started state |
| Actual Live card | Status badge returns to Running |
| The audit trail | A reopen event is appended, carrying the actual end date that was removed |
| The next reschedule | The step keeps its work center, its logged hours stay locked, and only the remainder is re-planned |
That last row is the reason this matters. Before the reopen, a reschedule would have preserved the step as finished and never allocated the outstanding work at all. A job can be quietly under-planned by exactly the hours a mistaken completion hid.
How to Check It Worked
Read the operation's row in the Job View grid: Actual Start carries a value, Actual End is empty. The Actual Live card shows Running rather than Complete, with its progress bar reading logged hours against planned. Then open Job Audit on the Job View tab. The newest event should be the reopen, showing the actual end date that was removed. Tracing those events is covered in how to see who changed a schedule.
Common Mistakes
- Expecting the reopen to restore hours you already cleared. It does not. Clearing the end and clearing the hours are independent actions, and reopening never puts values back.
- Reopening but not rescheduling. The classification is right and the plan is still wrong. Two moves, in order.
- Clearing the actual start and leaving the end in place. That produces a step that looks finished with no record of ever starting. Clear both or neither.
- Reopening a step that is covered by its logged hours. It will still read complete on screen. Fix the hours or the routing estimate instead.
- Reopening when the real problem is a short confirm. If the operator finished the physical work with fewer hours than planned, the step is genuinely complete and the site's partial-confirm policy decides what happens to the gap. See how to record a partially finished operation.
Next Steps
If the completion was right and only the date was wrong, how to correct a wrong actual date is the shorter fix. If a whole order needs unlocking, read how to mark a whole job complete, which covers the reopen at order level. When symptoms are unclear, actuals logging mistakes maps each one back to its cause.
Every task in this library is indexed on the EDGEBIC how-to hub. Bring a job with a bad completion on it to a demo of EDGEBIC and we will unwind it together.
Expert Q&A: Deep Dive
Q: We only noticed the wrong completion after a reschedule already ran. Is it too late?
A: No, but the damage is now downstream rather than local. The reschedule preserved the false completion verbatim (it does exactly what it promises) and planned every following step from that fake end date. So the job's tail is sitting on a date that never happened. The fix is the same two moves in order: reopen the operation, then reschedule again. The second run reclassifies the step as in progress, forward-allocates the hours that are genuinely still owed, and re-queues the downstream steps behind the corrected resume point. Check the result on the job audit trail, where both runs appear with their old and new dates.
Q: A step keeps showing as complete even after we cleared the actual end. What is going on?
A: An operation counts as done in two different ways, and clearing the end only addresses one of them. The second is coverage: when the logged hours have fully met or exceeded the planned hours, the Job View, the Gantt shade, and the Actual Live cards all read complete whether or not an end date exists. So check the numbers. If eleven hours are logged against an eleven-hour plan, the step is covered and will look finished. Either the hours are wrong (correct them in the grid) or the routing estimate is too low for the work that is really left. Fixing the routing is the durable answer, because the next job through that step will otherwise be planned short as well.
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.