# Epicor Job Lifecycle Flags Reference (JobHead and JobOper Fields)

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

## Short answer

Lookup table of the job status flags on Erp.JobHead and related tables, what they mean and how to use them in BAQs.

## Category

epicor

## Erp

Epicor Kinetic

## Audience

- Epicor developer
- Production planner
- BAQ author

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Table

**Key:** table

**Type:** text

#### Field

**Key:** field

**Type:** text

#### Meaning

**Key:** meaning

**Type:** text

#### BAQ use

**Key:** baq

**Type:** text

**Rows:**

**Table:** JobHead

**Field:** JobEngineered

**Meaning:** Job is engineered; method of manufacture is approved

**Baq:** Exclude unengineered jobs from release lists

**Table:** JobHead

**Field:** JobReleased

**Meaning:** Job released to the shop floor and available for labor and issues

**Baq:** Filter = true for active shop work

**Table:** JobHead

**Field:** JobFirm

**Meaning:** Firm job, protected from MRP changes

**Baq:** Separate firm vs planned work

**Table:** JobHead

**Field:** JobHeld

**Meaning:** Job is on hold

**Baq:** Exclude from dispatch lists

**Table:** JobHead

**Field:** JobComplete

**Meaning:** Production marked complete

**Baq:** Use false for work still to do

**Table:** JobHead

**Field:** JobClosed

**Meaning:** Job closed; no further transactions

**Baq:** Use false for open jobs

**Table:** JobHead

**Field:** ProdQty

**Meaning:** Quantity to be produced

**Baq:** Compare with received quantity for completion %

**Table:** JobHead

**Field:** StartDate

**Meaning:** Scheduled start date

**Baq:** Backlog and schedule adherence

**Table:** JobHead

**Field:** DueDate

**Meaning:** Scheduled due date

**Baq:** Late job reports

**Table:** JobOper

**Field:** OpComplete

**Meaning:** Operation marked complete

**Baq:** Find remaining operations by work center

**Table:** JobOper

**Field:** OpCode

**Meaning:** Operation code

**Baq:** Join to OpMaster for descriptions

**Table:** JobMtl

**Field:** IssuedComplete

**Meaning:** Material fully issued to the job

**Baq:** Shortage and kitting reports

**Table:** JobHead

**Field:** PartNum

**Meaning:** Part being manufactured

**Baq:** Group by part for demand views

**Table:** JobHead

**Field:** JobNum

**Meaning:** Job number, key with Company

**Baq:** Join key for all job child tables

**Notes:** Field names are as commonly seen in the Erp schema; verify exact names and any version-specific fields in the Data Dictionary Viewer. Epicor Help describes the full job lifecycle: engineer, release, report, complete, close.

## Content

**Intro:** Most Epicor job reports are filtering on a handful of flags, and mixing them up gives wrong answers. This reference explains each flag and how it behaves in a BAQ.

**Sections:**

#### How to use the reference

**Body:** Search by table or field to read the meaning, then copy the filter idea into your BAQ criteria. For an open work list you will typically combine JobReleased true, JobComplete false and JobClosed false, with JobHeld false if you do not want held jobs. Export to Excel to share with planners and report writers.

#### The job lifecycle in plain terms

**Body:** A job is created, engineered when its method is approved, released so the shop can charge labor and issue material, completed when production is done, and closed when no more transactions are allowed and costs are finalized. Firm and held are separate controls: firm protects from MRP rescheduling, held pauses work. Each step maps to a flag, which makes lifecycle reports straightforward.

**Bullets:**

- Engineer: JobEngineered
- Release: JobReleased
- Complete: JobComplete
- Close: JobClosed
- Controls: JobFirm and JobHeld

#### Common mistakes

**Body:** Treating complete as closed leaves jobs that still collect cost in your open list. Ignoring held jobs inflates apparent backlog. Comparing flags to text instead of true or false in BAQ criteria returns nothing. And remember that operation level flags such as OpComplete matter for dispatch lists, since a released job may have most operations done.

**Cta:** Netray can turn these job rules into plain-English questions over live Epicor data, read-only and on-prem if needed.

**Faq:**

#### What is the difference between JobComplete and JobClosed?

**Answer:** JobComplete says production is finished. JobClosed locks the job against further transactions, usually after costs are reconciled. A job can be complete but still open for late labor, receipts or adjustments.

#### Does JobFirm stop production?

**Answer:** No. JobFirm protects the job from MRP changes. Production proceeds normally. Use JobHeld if you need to pause work on a job.

#### How do I list late jobs in a BAQ?

**Answer:** Filter JobClosed false and JobComplete false, then add a DueDate less than today as a criteria or calculated field. Add the operations table if you want to see which operation is behind.

#### Are the fields the same in every version?

**Answer:** Core flags have been stable, but always confirm in the Data Dictionary Viewer for your version, particularly if you rely on newer scheduling or planning fields.

## Search terms

epicor job status, epicor jobreleased jobengineered, epicor jobclosed vs jobcomplete, erp.jobhead fields, epicor job lifecycle, epicor job firm meaning, epicor jobhead flags baq, epicor job oper opcomplete

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