How to Export One Job's Operation List to Excel in EDGEBIC

The Job View in EDGEBIC by User Solutions exports one job's operation list to Excel from a header button, carrying the scheduled and actual dates, the hours, the pieces, and percent complete exactly as your grid is arranged. It is the fastest way to build a job packet, brief a customer, or take one job into a meeting without exporting the whole plant. This is the sequence, and the two settings that decide what actually lands in the file.

For plant-wide exports, see how to export a report to Excel. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• The job has been scheduled at least once, so it has operations to list.
• Actuals are logged if the export needs to show progress. The actual columns read empty on a job nobody has logged.
• You know the date range the export should cover, because the window on screen is the window in the file.

Step 1: Select the Job

Open the Job View tab and pick the job in the Select Job dropdown. The summary panel above the grid fills with the job number, the end product, the original planned window, the quantity, the operation count, and the hours roll-up of total, actual, remaining, and percent complete.

Step 2: Set the Date Window

Use the Start and End pickers. The default window runs from today minus seven days to today plus three weeks, which is right for daily work and wrong for a job packet.

Clear a picker to fall back to the job's own first or last date on that side. Clearing both gives you the whole job, which is usually what an export is for.

Step 3: Arrange the Columns You Want

The export follows the grid as displayed, so arranging first saves editing later. The per work center grid lists one row per operation with:

Column order, width, visibility, sorting, and grouping are saved automatically per user, so the arrangement you set once is the arrangement you export from then on. There is no save layout button to press.

Step 4: Export

Click Export Excel in the header buttons and save the file. The header row of buttons also carries Log Actual, Complete this Job or Reopen Job, Job Audit, Import Actuals, and Re-Schedule, so take care not to press a neighbor by reflex.

Step 5: Sanity-Check the File

Two checks catch nearly every surprise:

1. Row count. It should match the operation count in the summary panel, unless your date window deliberately cut the job short.
2. A completed row. Its actual dates and actual hours should match what the floor reported. If they are empty, the operations were never logged, and the export is honestly reporting an absence rather than losing data.

What Changes When You Export

Nothing in the plan. Exporting reads the grid and writes a file. No dates move, no capacity is claimed, and no audit event is written, because nothing about the job changed.

What the file is, though, is a snapshot. Actuals land later, reschedules move remaining work, and the same export tomorrow will read differently. That is the argument for dating the file and filing it with the job rather than treating it as a live view.

How to Check It Worked

Open the spreadsheet beside the Job View and compare three numbers: the total hours in the header, the actual hours in the header, and the number of rows. If the header says twelve operations and the file has eight, the date window trimmed it. Widen the window and export again.

Common Mistakes

• Exporting with the default window. Seven days back and three weeks forward will cut both ends off a long job.
• Treating the export as the audit record. For who changed what and when, use the job audit trail from the same header, which reconstructs the whole life cycle including reschedules, work center swaps, and completion events. See how to run the job audit trail.
• Expecting a plant-wide file from this button. It exports the job on screen.
• Reading percent complete on a job with no logging. Percent complete is built from logged hours, so an unlogged job reads as barely started no matter what the floor says.
• Sending an undated file. Reports and exports are point in time, and a spreadsheet with no date is an argument waiting to happen.

See how one job's plan, progress, and history stay in one place on the EDGEBIC product page.