Epicor Job Lifecycle Flags Reference (JobHead and JobOper Fields)
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.
| Table | Field | Meaning | BAQ use |
|---|---|---|---|
JobHead | JobEngineered | Job is engineered; method of manufacture is approved | Exclude unengineered jobs from release lists |
JobHead | JobReleased | Job released to the shop floor and available for labor and issues | Filter = true for active shop work |
JobHead | JobFirm | Firm job, protected from MRP changes | Separate firm vs planned work |
JobHead | JobHeld | Job is on hold | Exclude from dispatch lists |
JobHead | JobComplete | Production marked complete | Use false for work still to do |
JobHead | JobClosed | Job closed; no further transactions | Use false for open jobs |
JobHead | ProdQty | Quantity to be produced | Compare with received quantity for completion % |
JobHead | StartDate | Scheduled start date | Backlog and schedule adherence |
JobHead | DueDate | Scheduled due date | Late job reports |
JobOper | OpComplete | Operation marked complete | Find remaining operations by work center |
JobOper | OpCode | Operation code | Join to OpMaster for descriptions |
JobMtl | IssuedComplete | Material fully issued to the job | Shortage and kitting reports |
JobHead | PartNum | Part being manufactured | Group by part for demand views |
JobHead | JobNum | Job number, key with Company | Join key for all job child tables |
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.
Get job questions answered from Epicor
Optional: see a natural-language layer over Epicor job data.
Optional. The tool and every export work without this. No spam.
How to use the reference
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
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.
- Engineer: JobEngineered
- Release: JobReleased
- Complete: JobComplete
- Close: JobClosed
- Controls: JobFirm and JobHeld
Common mistakes
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.
Frequently Asked Questions
What is the difference between JobComplete and JobClosed?
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?
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?
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?
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.
Netray can turn these job rules into plain-English questions over live Epicor data, read-only and on-prem if needed.
Related Tools
Epicor Open Jobs BAQ SQL Generator
Generates a read-only T-SQL query listing open, released jobs from Erp.JobHead with optional due-date and part filters.
EpicorEpicor Business Object Service Reference
Lookup table of common Erp.BO services with their main table, primary key and standard method names.
EpicorEpicor BPM Directive Types Reference
Lookup table of Epicor BPM directive types, when each runs, whether it can stop a save, and typical use.
EpicorEpicor DMT Data Load Checklist
Checklist for planning and running Epicor DMT loads: prerequisites, load order, BPM impact, validation and rollback.
More Epicor tools
See all- Epicor Kinetic Customization Change Request Form Template
- Epicor Kinetic Go-Live Cutover Plan Template
- Epicor Kinetic User Access Request Form Template
- Epicor Kinetic BPM Directive Inventory Worksheet
- Epicor Kinetic Scheduled Task Register Worksheet
- Epicor Kinetic Custom Report Inventory Worksheet
- Epicor Kinetic Data Migration Mapping Worksheet
- Epicor Kinetic Data Load Effort Calculator
- Epicor Business Object Services Reference