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

> Source: https://netray.co/tools/epicor-kinetic-job-status-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A searchable lookup of the job lifecycle flags and related fields in Epicor Kinetic job entry, so you can build BAQs and dashboards with the right filter.

## Category

epicor

## Erp

Epicor Kinetic

## Industry

Discrete Manufacturing

## Audience

- Epicor administrator
- Production planner
- BAQ developer

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Table.Field

**Key:** field

**Type:** text

#### Kind

**Key:** type

**Type:** text

#### What it means

**Key:** meaning

**Type:** text

#### Typically set by

**Key:** set_by

**Type:** text

#### Use in a BAQ or dashboard

**Key:** baq_use

**Type:** text

**Rows:**

**Field:** JobHead.JobNum

**Type:** Key

**Meaning:** Job number, unique within the company.

**Set by:** Job Entry on creation or MRP

**Baq use:** Join key to JobOper, JobMtl, JobAsmbl together with Company.

**Field:** JobHead.PartNum

**Type:** Attribute

**Meaning:** Part the job produces.

**Set by:** Job Entry or MRP

**Baq use:** Filter or group by finished part.

**Field:** JobHead.ProdQty

**Type:** Quantity

**Meaning:** Planned production quantity.

**Set by:** Job Entry or MRP

**Baq use:** Compare with received quantity to find short-running jobs.

**Field:** JobHead.JobType

**Type:** Attribute

**Meaning:** Type of job such as manufacturing versus other job types your site uses.

**Set by:** Job Entry

**Baq use:** Exclude non-manufacturing job types from shop floor dashboards.

**Field:** JobHead.JobEngineered

**Type:** Flag

**Meaning:** The job method has been engineered and approved so it can move toward release.

**Set by:** Engineer in Job Entry or Job Engineering

**Baq use:** Find jobs waiting for engineering sign-off: Engineered = false.

**Field:** JobHead.JobReleased

**Type:** Flag

**Meaning:** Job is released to the shop floor, so labor and material can be reported against it.

**Set by:** Job Entry or Job Release process

**Baq use:** Open shop floor work: Released = true and Closed = false.

**Field:** JobHead.JobFirm

**Type:** Flag

**Meaning:** Job is firmed so MRP treats it as a fixed supply instead of rescheduling it.

**Set by:** Planner in Job Entry

**Baq use:** Separate firm supply from suggested supply in a planning view.

**Field:** JobHead.JobHeld

**Type:** Flag

**Meaning:** Job is on hold, normally blocking further activity until released from hold.

**Set by:** Planner or quality

**Baq use:** Hold list for daily production meeting.

**Field:** JobHead.JobComplete

**Type:** Flag

**Meaning:** Production is finished. The job still holds costs until it is closed.

**Set by:** Shop floor completion or Job Entry

**Baq use:** Completed but not closed: the WIP cleanup list.

**Field:** JobHead.JobClosed

**Type:** Flag

**Meaning:** Job is closed after the close job process. No further transactions are normally allowed.

**Set by:** Close Job process, usually month end

**Baq use:** Exclude closed jobs from open work and WIP reports.

**Field:** JobHead.StartDate

**Type:** Date

**Meaning:** Scheduled job start date.

**Set by:** Scheduling engine or planner

**Baq use:** Starts this week lists.

**Field:** JobHead.DueDate

**Type:** Date

**Meaning:** Scheduled job finish date.

**Set by:** Scheduling engine or planner

**Baq use:** Late job report: DueDate < today and Complete = false.

**Field:** JobHead.ReqDueDate

**Type:** Date

**Meaning:** Required due date driven by demand.

**Set by:** Job Entry or MRP

**Baq use:** Compare with DueDate to expose schedule slippage.

**Field:** JobOper.OpComplete

**Type:** Flag

**Meaning:** The operation is complete.

**Set by:** Labor entry or Job Entry

**Baq use:** Find the current operation: first op where OpComplete = false.

**Field:** JobOper.RunQty

**Type:** Quantity

**Meaning:** Planned run quantity on the operation.

**Set by:** Job Entry

**Baq use:** Operation load and throughput reports.

**Field:** JobMtl.IssuedComplete

**Type:** Flag

**Meaning:** Material requirement is fully issued.

**Set by:** Material issue transactions

**Baq use:** Kitting readiness: released jobs with unissued material.

**Field:** JobMtl.IssuedQty

**Type:** Quantity

**Meaning:** Quantity issued so far to the job.

**Set by:** Issue Material

**Baq use:** Compare with RequiredQty for shortages.

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use this reference

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Where is the job status field in Epicor Kinetic?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

epicor job status, epicor kinetic job released engineered firm, epicor jobhead fields, epicor job closed vs complete, epicor job lifecycle, epicor job entry flags, epicor baq job status filter, epicor held job

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json