Overview of Job and Repetitive Schedule Statuses
Job and repetitive schedule statuses can help you manage manufacturing operations.
Job statuses describe various stages the life cycle of a job and control job activities. See: Discrete Job Statuses.
Repetitive schedule statuses describe stages in the life cycle of a repetitive schedule and control schedule activities. See: Repetitive Schedule Statuses.
Job and repetitive schedule statuses control issue, move, resource, overhead, completion, scrap, job close, period close, and purge transactions. See: Transaction Control by Status.
Job and repetitive schedule statuses are automatically updated after certain activities. For example, the status of a job is updated to Complete when you complete all the assemblies on the job. Statuses can also be manually changed although there are some restrictions.
Job and repetitive schedule statuses control engineering change order (ECO) implementation. See: ECO Implementation by Status.
Oracle Master Scheduling/MRP and Oracle Supply Chain Planning includes supplies and demands from jobs based on their status. See: Planning Control by Status.
When you release --by changing the status from Unreleased to Released -- a job or schedule with a routing, the release date is automatically set and the Queue intraoperation step of the first routing operation is updated with the job or schedule quantity. You can 'unrelease' jobs and schedules if there are no net issue, move, resource, completion, or scrap charges against them.
Putting jobs and schedules 'on hold' allows you to respond to changes and to control production by temporarily preventing transactions. You can manually change jobs and repetitive schedules to On Hold. You also set the WIP Respond to Sales Order Changes parameter so that Unreleased jobs building assemble-to-order (ATO) items are automatically changed from Unreleased to On Hold when configuration items are unassigned in Oracle Order Entry/Shipping. See: Discrete Parameters.
Status Based Reporting
Job and repetitive schedule statuses control what information is displayed in various reports and inquiries. See: Reporting by Status.
Closed jobs and Complete - No Charges and Cancelled repetitive schedules cannot be updated. Job and schedules with these statuses can be purged. You can change the status of a job or schedule so that it can be updated.
Concurrent Processing Support
When you define discrete jobs, the WIP:Define Discrete Job form profile option determines whether job bills of material and routings, if any, are created (loaded) concurrently or interactively. The status of the job tracks the progress and outcome of the concurrent load process (e.g., Pending Bill Load, Pending Routing Load, Failed Bill Load, and Failed Routing Load). See: Work in Process Profile Options.
Statuses also track the progress of the job close process (e.g., Pending Close and Failed Close).
Discrete Job Status Control
Repetitive Schedule Status Control
Job and Repetitive Schedule Status Changes