Discrete Job Statuses (Oracle Work in Process)


	Previous	Next		Contents	Index	Glossary	Library

Discrete Job Statuses

Discrete job statuses describe the various stages in the life cycle of a job and control the activities that you can perform on it.

User Controlled Statuses

You can manually change user-controlled statuses. For example, you can change a job's status to Released to initiate the production cycle. Some user-controlled statuses are automatically changed based on other events. For example, when you complete a job, its status is changed to Complete.

Released The job is available for production and can be transacted against. When a job is changed to this status, the date released is automatically set to the current date and, if a routing exists, the job quantity is moved to the Queue intraoperation step of the first routing operation.

You can change jobs to this status as you define them.

Unreleased The job is not released for transaction activity. You can update but cannot transact against it.

You can assign a status of Unreleased if there are no net issue, move, resource, completion, or scrap charges associated with the job and no purchase orders or purchase requisitions linked to the job.

Complete The job is completed but accepting transactions and charges. Jobs are automatically updated to this status when the quantity completed into inventory equals the job quantity.

You can manually assign this status only when you update the job, not when you define it.

Complete-No Charges The job is complete and accepting no further activity. You cannot update or transact against it, but you can change its status to Complete. You can assign this status only when you update the job.

On Hold You can update the job but cannot transact against it. You can assign this status to a job when you define it.

Cancelled The job was cancelled before completion. You cannot update the job or transact against it, but you can change its status. You can assign this status only when you update the job.

Closed The job is closed and accepting no further activity. Job are automatically updated to this status upon successful completion of the job close process. You can change jobs with this status to another status if the accounting period that the job was completed in is still open and if your functional security setup permits.

Processing Statuses

Some job statuses are automatically updated by a process. For example, if you have the WIP:Define Discrete Job Form profile option set to concurrent definition, the job status is used to track the progress of the bill of material and routing load process. When you close a job, its status is used to track the progress of the concurrent close process.

Pending Bill Load The concurrent process is loading the bill of material for the job. You cannot update the job nor transact against it.

For non-standard discrete jobs, this is applicable only if you specified a bill reference.

Pending Routing Load The bill of material load was successful and the concurrent process is now loading the routing for the job. You cannot update the job nor transact against it.

For non-standard discrete jobs, this option is applicable only if you specified a routing reference.

Failed Bill Load The concurrent process was unable to load the bill of material for the job. The load may have failed for a number of reasons. For example, the job start date may be outside the last open accounting period at the time of job creation. You can close the failed job with the Close Discrete Jobs window and open another job for the assembly. Or you can resubmit the job once you change the status to Unreleased, Released, or On Hold.

For non-standard discrete jobs, this option is applicable only if you specified a bill reference.

Failed routing load The concurrent process was unable to load the routing for the job. The load may have failed for a number of reasons. For example, the job start or completion date may be outside the organization workday calendar at the time of job creation. You can close the failed job and open another job for the assembly, or you can resubmit the job after changing its status to Unreleased, Released, or On Hold.

For non-standard discrete jobs, this option is available only if you specified a routing reference.

Pending Close The concurrent process is closing the job. You cannot transact against or update it. If the close process terminates abnormally, you can change the status of the job and resubmit it.

Failed Close The concurrent process was unable to close the job. The close may have failed for a number of reasons. For example, there may be pending transactions against the job. You must fix the problems before you can close the job. You cannot transact against it.

Released	The job is available for production and can be transacted against. When a job is changed to this status, the date released is automatically set to the current date and, if a routing exists, the job quantity is moved to the Queue intraoperation step of the first routing operation.
	You can change jobs to this status as you define them.
Unreleased	The job is not released for transaction activity. You can update but cannot transact against it.
	You can assign a status of Unreleased if there are no net issue, move, resource, completion, or scrap charges associated with the job and no purchase orders or purchase requisitions linked to the job.
Complete	The job is completed but accepting transactions and charges. Jobs are automatically updated to this status when the quantity completed into inventory equals the job quantity.
	You can manually assign this status only when you update the job, not when you define it.
Complete-No Charges	The job is complete and accepting no further activity. You cannot update or transact against it, but you can change its status to Complete. You can assign this status only when you update the job.
On Hold	You can update the job but cannot transact against it. You can assign this status to a job when you define it.
Cancelled	The job was cancelled before completion. You cannot update the job or transact against it, but you can change its status. You can assign this status only when you update the job.
Closed	The job is closed and accepting no further activity. Job are automatically updated to this status upon successful completion of the job close process. You can change jobs with this status to another status if the accounting period that the job was completed in is still open and if your functional security setup permits.

Pending Bill Load	The concurrent process is loading the bill of material for the job. You cannot update the job nor transact against it.
	For non-standard discrete jobs, this is applicable only if you specified a bill reference.
Pending Routing Load	The bill of material load was successful and the concurrent process is now loading the routing for the job. You cannot update the job nor transact against it.
	For non-standard discrete jobs, this option is applicable only if you specified a routing reference.
Failed Bill Load	The concurrent process was unable to load the bill of material for the job. The load may have failed for a number of reasons. For example, the job start date may be outside the last open accounting period at the time of job creation. You can close the failed job with the Close Discrete Jobs window and open another job for the assembly. Or you can resubmit the job once you change the status to Unreleased, Released, or On Hold.
	For non-standard discrete jobs, this option is applicable only if you specified a bill reference.
Failed routing load	The concurrent process was unable to load the routing for the job. The load may have failed for a number of reasons. For example, the job start or completion date may be outside the organization workday calendar at the time of job creation. You can close the failed job and open another job for the assembly, or you can resubmit the job after changing its status to Unreleased, Released, or On Hold.
	For non-standard discrete jobs, this option is available only if you specified a routing reference.
Pending Close	The concurrent process is closing the job. You cannot transact against or update it. If the close process terminates abnormally, you can change the status of the job and resubmit it.
Failed Close	The concurrent process was unable to close the job. The close may have failed for a number of reasons. For example, there may be pending transactions against the job. You must fix the problems before you can close the job. You cannot transact against it.

Discrete Job Statuses

User Controlled Statuses

Processing Statuses

See Also