How to Clear a Job's Actuals From One Operation Forward in EDGEBIC

To clear a job's actuals from one operation forward in EDGEBIC, right-click that operation's bar on the Schedule View Gantt and choose either the entry that clears the current operation and every following operation on the job, or the entry that clears the following operations and keeps the current one. Both are job-scoped in EDGEBIC by User Solutions, so no other job is touched.

This is the cleanup for a run of wrongly stamped steps. For a single operation see how to correct a wrong actual date; the full task library is at the EDGEBIC how-to hub.

Before You Start

• You have identified the first operation in the routing whose actuals are wrong. Everything from there forward is what these entries release.
• You have decided whether that first operation itself should be cleared. That single decision picks which of the two menu entries you use.
• You know the job is not finished in a way you want preserved. Clearing removes the dates that mark work as done.
• You are prepared to reschedule afterwards. Clearing frees the steps; the run is what gives them honest dates.

The Steps

1. Open the Schedule View tab and find the job. If the board is crowded, right-click a bar of the job and shade the others so you can read the routing across the lanes without mis-clicking.
2. Identify the boundary operation, the first one in routing order whose actual dates should not exist.
3. Right-click that bar to open the operation menu.
4. Choose the entry that matches your decision. One clears the actual start and end date and times for the current operation and every following operation on the selected job. The sibling entry does the same for the following operations only and leaves the current operation's actuals in place.
5. Read the bars. The released operations return to their engine-planned positions rather than the positions the actuals were drawing them at.
6. Check the operation rows on the Job View tab. The cleared operations should show empty Actual Start and Actual End columns, and the hours columns should look like something the floor would recognize.
7. Reschedule the job. The freed steps are now not-started work, so the engine re-plans them from the job's real resume point. Use the targeted route in how to reschedule only the jobs that changed.

Choosing the Right Clear

The same right-click menu carries five cleanup entries and they differ only in reach. Picking the narrowest one that solves your problem is the whole skill.

The last row is a different instrument with a different blast radius, covered separately in how to clear actuals for a work center from a date forward.

How to Check It Worked

Three checks, in order. First, on the Gantt, the cleared bars should no longer carry an actuals state color, and any completed shade over them should be gone. Second, on the Job View operation grid, Actual Start and Actual End must be empty for exactly the steps you meant to release and unchanged for every step before the boundary. Third, the job's hours header should show a lower Actual Hours figure if hours were tied to those stamps, and Remaining should have grown to match.

Then open the job audit trail. The clear is a change event, so you can prove what was released and when, which matters when the question comes back a week later.

Common Mistakes

Clicking the wrong boundary. Clearing from the wrong operation either leaves a bad stamp in place or releases a good one. Confirm routing order before you act, because these entries walk forward from where you clicked, not from where you meant.

Reaching for the work-center entry by mistake. Its label mentions all jobs that use the work center for a reason. On a shared machine it can strip stamps from jobs nobody raised a problem about, and nothing puts them back.

Clearing and not rescheduling. A released step keeps drawing at its engine-planned position, which is where the last run put it, not where reality now implies it belongs. Until you re-run, the plan and the truth disagree, the situation described in how to resume a job from where the shop actually is.

Assuming the dates were the whole problem. Logged daily hours are what progress reporting and the next reschedule really consume. Review the operation rows after clearing rather than trusting that the dates carried everything with them.

Using a clear to move an operation. If the goal is a different position rather than an absence of history, the tools are a drag or an exact typed move, not a clear. Clearing is for stamps that should never have existed.

Trying to clear an externally fed operation. An operation whose actual dates arrived from an external feed outranks other states on the board, and the feed will reassert itself. Correct the source data instead.

Next Steps

Clearing is usually the middle of a three-part repair: release the bad stamps, re-log what genuinely happened, then reschedule. If the boundary operation is real and only its close was premature, how to reopen a completed operation is the narrower fix, and how to un-start an operation covers the start-only case. For the neighboring entries on the same menu, the Gantt right-click operation menu is the tour.

The takeaway

Clearing forward within one job is the tool that keeps a data-entry accident from becoming a week of wrong promises, and its virtue is precision: one job, one boundary, one action. Choose the narrowest entry that solves the problem, verify the rows before you re-run, and let the engine give the freed steps dates you can defend. See where actuals fit in the platform on the EDGEBIC product page, and if you are arriving from the earlier User Solutions planning tools, the move from RMDB to EDGEBIC shows what carries over. Next, read how to clear actuals for a work center from a date forward for the wider instrument and how to correct a wrong actual date for the single-operation case.