EpicorFree referencePDF, Excel, Word exportEpicor KineticDiscrete Manufacturing

Epicor Kinetic Job Status Reference: Every Flag and What It Does

Epicor does not store one job status field. A job's state is the combination of several flags on the JobHead table, and getting the combination right is the difference between a trustworthy BAQ and one that lists closed jobs as open.

Download:

Table.Field	Kind	What it means	Typically set by	Use in a BAQ or dashboard
JobHead.JobNum	Key	Job number, unique within the company.	Job Entry on creation or MRP	Join key to JobOper, JobMtl, JobAsmbl together with Company.
JobHead.PartNum	Attribute	Part the job produces.	Job Entry or MRP	Filter or group by finished part.
JobHead.ProdQty	Quantity	Planned production quantity.	Job Entry or MRP	Compare with received quantity to find short-running jobs.
JobHead.JobType	Attribute	Type of job such as manufacturing versus other job types your site uses.	Job Entry	Exclude non-manufacturing job types from shop floor dashboards.
JobHead.JobEngineered	Flag	The job method has been engineered and approved so it can move toward release.	Engineer in Job Entry or Job Engineering	Find jobs waiting for engineering sign-off: Engineered = false.
JobHead.JobReleased	Flag	Job is released to the shop floor, so labor and material can be reported against it.	Job Entry or Job Release process	Open shop floor work: Released = true and Closed = false.
JobHead.JobFirm	Flag	Job is firmed so MRP treats it as a fixed supply instead of rescheduling it.	Planner in Job Entry	Separate firm supply from suggested supply in a planning view.
JobHead.JobHeld	Flag	Job is on hold, normally blocking further activity until released from hold.	Planner or quality	Hold list for daily production meeting.
JobHead.JobComplete	Flag	Production is finished. The job still holds costs until it is closed.	Shop floor completion or Job Entry	Completed but not closed: the WIP cleanup list.
JobHead.JobClosed	Flag	Job is closed after the close job process. No further transactions are normally allowed.	Close Job process, usually month end	Exclude closed jobs from open work and WIP reports.
JobHead.StartDate	Date	Scheduled job start date.	Scheduling engine or planner	Starts this week lists.
JobHead.DueDate	Date	Scheduled job finish date.	Scheduling engine or planner	Late job report: DueDate < today and Complete = false.
JobHead.ReqDueDate	Date	Required due date driven by demand.	Job Entry or MRP	Compare with DueDate to expose schedule slippage.
JobOper.OpComplete	Flag	The operation is complete.	Labor entry or Job Entry	Find the current operation: first op where OpComplete = false.
JobOper.RunQty	Quantity	Planned run quantity on the operation.	Job Entry	Operation load and throughput reports.
JobMtl.IssuedComplete	Flag	Material requirement is fully issued.	Material issue transactions	Kitting readiness: released jobs with unissued material.
JobMtl.IssuedQty	Quantity	Quantity issued so far to the job.	Issue Material	Compare with RequiredQty for shortages.

Field names reflect the standard Epicor Kinetic data model. Confirm against your version in Data Dictionary Viewer, since custom fields and version changes can differ.

Job status dashboard review

Send us the BAQ behind your job status dashboard and we will review it for flag logic errors.

Optional. The tool and every export work without this. No spam.

How to use this reference

Search for the flag or field you need, then read the last column to see how it is normally used in a BAQ or dashboard. The lifecycle runs roughly Engineered, Released, Complete and then Closed, with Firm and Held as side states. A planner cares about Firm, a shop supervisor about Released and Held, and finance about Complete versus Closed. Start your BAQ from the audience's question and then choose the flags, rather than the other way around.

Open shop floor work: Released true, Complete false, Closed false
Waiting on engineering: Engineered false, Closed false
WIP cleanup: Complete true, Closed false
Planning view: group by Firm to separate fixed supply from suggestions

Complete is not Closed

The most common mistake is treating completion as the end of the job. A complete job has finished production but still carries WIP and variances until the close process runs. Finance usually closes jobs at period end, so the gap between Complete and Closed is your accrual and cleanup list. If a dashboard filters only on Closed, it will show finished jobs as open for weeks.

Firm and Held change how others see the job

Firm tells MRP not to move the job, which matters when planners wonder why a suggested date was ignored. Held blocks activity and is often used by quality. Neither is a replacement for the release flag, and each should be a visible column in any list that supervisors act on, because a hidden hold looks like a stalled shop.

Version and customization notes

Kinetic keeps adding fields and some sites add user-defined columns for their own statuses. Always confirm names in Data Dictionary Viewer before copying into a BAQ, and prefer calculated fields for a combined status label so one definition serves every report.

Frequently Asked Questions

Where is the job status field in Epicor Kinetic?

There is no single status field. State is derived from flags on JobHead such as JobEngineered, JobReleased, JobFirm, JobHeld, JobComplete and JobClosed. Many sites build a calculated field in a BAQ that turns the combination into one readable label for dashboards.

What is the difference between Complete and Closed on an Epicor job?

Complete means production is finished. Closed means the job has been through the close process, so costs are moved out of WIP and the job no longer accepts normal transactions. Many sites leave jobs complete until month end before closing them.

Why does MRP ignore a job I want moved?

Check the Firm flag. MRP treats firm jobs as fixed supply and does not reschedule them in the usual way. Unfirm the job in Job Entry if you want MRP to suggest changes, then rerun the planning process.

Can I add my own job status to Epicor?

You can add user-defined fields and use BPM or a BAQ calculated field to set or display a custom status. Keep it additive and do not overload the standard flags, since standard reports and processes rely on their normal meaning.

If your teams still build job status lists by hand, we can set up a read-only natural language layer over Epicor data that applies these flags consistently.

Talk to an Expert Explore More Free Tools

Related Tools

Epicor

More Epicor tools

See all

Back to All Tools