OracleFree referencePDF, Excel, Word exportOracle E-Business SuiteDiscrete Manufacturing

Oracle EBS Discrete Job Statuses Reference

In Oracle E-Business Suite, the status of a discrete job decides which material, move and resource transactions Work in Process will accept. This reference lists each status with its STATUS_TYPE code and what it does on the shop floor.

Download:

STATUS_TYPE	Status	What it means	Transactions allowed	Typical next step
1	Unreleased	Job exists but is not yet released to the shop floor.	Edit job, BOM and routing. No material or move transactions.	Release the job.
3	Released	Job is active on the shop floor.	Component issues, moves, resource charges, completions.	Complete assemblies.
4	Complete	Job is finished but charges can still be posted.	Charges and returns still allowed.	Run Close Discrete Jobs.
5	Complete - No Charges	Job is finished and further charges are blocked.	No further charges.	Close the job.
6	On Hold	Job is suspended by planner or supervisor.	No transactions until the hold is removed.	Release or cancel.
7	Cancelled	Job is cancelled and cannot be used for production.	No production transactions.	Close if charges remain.
12	Closed	Variances calculated and posted, job is final.	No transactions.	Reporting only.
13	Pending - Mass Loaded	Job loaded through the interface and awaiting processing.	None until processed.	Run the Work Order Interface.
14	Pending Close	Close request submitted and not yet processed.	None while closing.	Wait for the close program.
15	Failed Close	Close program failed for this job.	Limited, fix the cause first.	Review the log and resubmit.
16	Pending Scheduling	Job is waiting for the scheduler.	None until scheduled.	Run the scheduler or check the interface.
17	Draft	Job saved in draft and not yet firm.	Editing only.	Promote to Unreleased or Released.
8	Pending Routing Load	Routing is being loaded for the job.	None until the load ends.	Wait or check the interface.
9	Failed Bom Load	Bill of material load failed.	None.	Fix the BOM and resubmit.
10	Failed Routing Load	Routing load failed.	None.	Fix the routing and resubmit.

Codes and wording come from the WIP_JOB_STATUS lookup and can differ slightly between 11i and R12 patch levels. Confirm in Application Utilities Lookups on your own instance before using a code in a customization.

Job status health check on your own data

Optional: we can review how many of your jobs sit in each status and which ones look stuck.

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

How to use this reference

Type a status name or numeric code in the search box to filter the table. The code column matches WIP_DISCRETE_JOBS.STATUS_TYPE, so you can paste it straight into a query, a report parameter or an Alert condition. Use the Excel export when you need to hand a status chart to planners or to document a job lifecycle in a design document.

The normal job lifecycle

A typical job moves from Unreleased to Released, then to Complete when the finished quantity is received, and finally to Closed after the Close Discrete Jobs program calculates variances. Complete - No Charges is the usual choice when the shop floor is done and nobody should post more labor or material.

Unreleased to Released: planners firm and release
Released to Complete: assembly completion transactions
Complete to Closed: variance calculation at period end
Hold and Cancelled sit outside the main path

Interface and error statuses

Pending Mass Loaded, Pending Close and the Failed statuses are mostly set by programs, not by people. If many jobs sit in Pending or Failed, look at the concurrent request log for the Work Order Interface or Close Discrete Jobs, then fix the data and resubmit. Do not update STATUS_TYPE directly in the database, because related tables and accounting would be left inconsistent.

Common mistakes

Closing jobs before all charges have posted is the most frequent cause of unexpected variances. Another is cancelling a job that already has material issued, which leaves stranded cost until the job is closed. Always check pending transactions and uncosted transactions first, then change the status through the form or the supported API.

Frequently Asked Questions

Where is the job status stored in Oracle EBS?

The status is stored in WIP_DISCRETE_JOBS.STATUS_TYPE as a number. The meaning of each number comes from the WIP_JOB_STATUS lookup type, so you can join to FND lookup tables to display the text.

What is the difference between Complete and Complete - No Charges?

Complete still accepts charges such as late labor or material returns. Complete - No Charges blocks all further charges, which is useful when you want the cost to freeze before closing the job.

Can I reopen a closed job?

Closed jobs generally cannot be reopened through normal forms. Some releases offer a reopen option for specific cases. Check your version and test in a non-production instance before relying on it.

Why is my job stuck in Pending Close?

The Close Discrete Jobs request has not completed or has errored. Check the concurrent request log, resolve pending or uncosted transactions that block it, and resubmit the close.

If your planners keep asking which jobs are stuck in which status, we can build a read-only view over your EBS data that answers it in plain English.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

Back to All Tools