Mark Complete on Import is the actuals import option that marks each operation in the file as finished when its row lands, and it is overridden per row by the optional Complete column. It answers a question a file of hours cannot otherwise answer: whether the work those hours represent is done, or merely done so far.
EDGEBIC by User Solutions offers it as a checkbox in the Import Options dialog for an actuals mask. This article defines what it changes and how it interacts with the per-row column. For where those hours land, see the sibling term daily hour breakdown.
How It Works
An actuals row carries a job number, a work center, a date, and hours or pieces. That is enough to record what happened on a day, but not enough to say whether the operation is over. An operation that logged six hours on Tuesday might have finished on Tuesday or might still be running on Wednesday, and the two are treated very differently from that point on.
Mark Complete on Import supplies the missing statement as a blanket default: every operation the file touches is marked finished. The optional Complete column overrides it per row, so a row carrying an explicit value speaks for its own operation regardless of how the option is set.
What being complete means in practice is that the operation gets an actual end. Two consequences follow, and both are the reason the flag matters:
- Rescheduling leaves it alone. A completed operation is history. The engine preserves it exactly as recorded and plans only what remains.
- Its hours count as done. Progress rollups treat the operation as finished work rather than as work still outstanding.
An operation with logged hours and no end is in progress: its hours count, its remaining hours are still planned, and rescheduling may still move the part of it that has not happened.
A Concrete Example
Think of a timesheet and a sign-off. The hours on the timesheet say what was worked. The sign-off at the bottom says the task is over. A batch of timesheets can be signed off as a batch, which is fast when they are all finished tasks, or signed individually when some of the work is still open. Signing the batch when part of it is still open is the mistake this option makes easy, and the per-row column is the remedy.
At Acme Industries a file covers three operations for JOB-2026-0107:
| Job | Work center | Date | Hours | Complete column | Result |
|---|---|---|---|---|---|
| JOB-2026-0107 | Saw-1 | 20 Jul | 4.0 | true | closed, end recorded |
| JOB-2026-0107 | CNC-Mill-1 | 21 Jul | 8.0 | true | closed, end recorded |
| JOB-2026-0107 | Weld-1 | 22 Jul | 3.5 | false | hours land, operation stays in progress |
With Mark Complete on Import ticked but the column present, the Weld-1 row still stays open, because the column wins. Had there been no column, all three would have closed and Weld-1's remaining hours would have vanished from the plan.
How EDGEBIC Uses It
The option suits a specific shape of file: a batch that represents finished work, typically a period close or a backlog load where everything in the file is over. In that case ticking it once saves adding a column that would read true on every row.
For a recurring feed it is usually the wrong instrument, because a nightly or weekly export naturally mixes operations that closed with operations still running, and no single blanket setting is right for both. The per-row column is the better fit there, and it costs one column in the export.
Because actuals imports overwrite the days a file carries, correction is straightforward. Re-importing a corrected file replaces the earlier values for those days rather than adding to them, so a wrongly closed operation can be reopened by sending the same rows with the column set false. After reopening, run the scheduler so the remaining work is planned again; while the operation was marked complete the engine treated it as finished and stopped planning what was left.
The same completion state can be set from the Log Actuals screen and from the shop-floor kiosk, so an import is one of several routes to the same outcome rather than a separate mechanism.
For running the load, see how to import actuals from a file, and for the mask carrying the option see how to set import options for a mask. For where the flag matters most, see what is actuals preservation on reschedule. Browse more definitions in the manufacturing glossary.
It is an option on an actuals import mask that marks each imported operation as finished when the row lands. It is a blanket instruction for the file, and it is overridden per row by the optional Complete column: if a row carries an explicit value in that column, that value wins for that operation. Use the option when a file represents finished work, and the column when a file mixes finished and in-progress operations.
The option is a default applied to every row in the run; the column is a per-row statement that overrides it. If your file contains only completed work the option alone is enough. If some operations in the file are still running, add a Complete column and mark only the finished ones, and the mixed file will import correctly regardless of how the option is set.
The operation gets an actual end recorded, which is what makes it complete rather than in progress. From then on rescheduling treats it as history and will not move it, and its hours count as done in progress rollups rather than as work still outstanding. It is the difference between an operation that has finished and one that has merely had hours logged against it.
Yes, and the mechanism is the same one you used to close them. An operation marked complete carries an actual end, so removing that end reopens it. For a handful of operations the quickest route is the Log Actuals screen, where you can clear the completion on each affected operation directly. For a larger set, prepare a corrected file that carries the same job, work center and date rows with a Complete column set false for the operations that are still running, and re-import it: actuals imports overwrite the days the file carries, so the corrected values replace the wrong ones without double-counting hours. Once the operations are reopened, reschedule so the remaining work is planned forward again, because while they were marked complete the engine treated them as history and stopped planning their leftover hours.
Leave Mark Complete on Import off on that mask and add a Complete column to the export instead. The blanket option is the wrong tool for a recurring feed that mixes states, because the same file will contain finished and running operations every night and no single setting is right for both. With the column present, each row states its own truth: your source system already knows which operations closed today, so let it say so per row. The import is designed for exactly this pattern, since the days a file carries are always overwritten with the file's values, so re-sending the same week every night converges on the correct state rather than accumulating errors. An operation that ran Monday through Wednesday and closed Wednesday will be reopened and reclosed correctly each night without anyone intervening.
Expert Q&A: Deep Dive
Q: We imported a week of shop-floor hours with Mark Complete on Import ticked, and now operations that are still running show as finished. Can we undo that?
A: Yes, and the mechanism is the same one you used to close them. An operation marked complete carries an actual end, so removing that end reopens it. For a handful of operations the quickest route is the Log Actuals screen, where you can clear the completion on each affected operation directly. For a larger set, prepare a corrected file that carries the same job, work center and date rows with a Complete column set false for the operations that are still running, and re-import it: actuals imports overwrite the days the file carries, so the corrected values replace the wrong ones without double-counting hours. Once the operations are reopened, reschedule so the remaining work is planned forward again, because while they were marked complete the engine treated them as history and stopped planning their leftover hours.
Q: Our nightly export sends the whole week every night, including operations still in progress. How should we set this up?
A: Leave Mark Complete on Import off on that mask and add a Complete column to the export instead. The blanket option is the wrong tool for a recurring feed that mixes states, because the same file will contain finished and running operations every night and no single setting is right for both. With the column present, each row states its own truth: your source system already knows which operations closed today, so let it say so per row. The import is designed for exactly this pattern, since the days a file carries are always overwritten with the file's values, so re-sending the same week every night converges on the correct state rather than accumulating errors. An operation that ran Monday through Wednesday and closed Wednesday will be reopened and reclosed correctly each night without anyone intervening.
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
The EDGEBIC Scheduling Glossary Index
A themed index to the EDGEBIC glossary: scheduling engine, capacity and calendars, materials and planning, shop floor, reporting, quoting, and data import terms, defined in plain language.
What Is the Critical Chain in Manufacturing Scheduling?
The critical chain is the longest dependent path through a plan once shared machine contention is counted, not just step precedence. Here is how it differs from the critical path.
What Does Finite Capacity Mean in EDGEBIC?
Finite capacity means the scheduler refuses to book more hours on a machine than that machine actually has. See exactly how EDGEBIC enforces it, day by day and shift by shift.