Statuses control what transactions can be performed on discrete jobs and repetitive schedules. Discrete job statuses also help you control whether you can close and purge jobs. Statuses can also be used to control ECO implementation and the MRP planning process.
You can perform issue, completion, move, scrap, and resource transactions for jobs and schedules with Released or Complete statuses. Backflush transactions and overhead charges are indirectly controlled by status since their source move or completion transactions are directly controlled by status.
Cost update transactions are created for standard discrete jobs and non-standard asset jobs with the following statuses: Unreleased, Released, Complete, Complete-No Charges, and On Hold.
When you close an accounting period, accounting transactions for repetitive schedules with statuses of Released, Complete, Complete-No Charges, and On Hold or just Complete and Complete-No Charges depending on how you set the WIP Recognize Period Variances Parameter - are automatically created.
When you close an accounting period, accounting transactions for non-standard expense jobs with statuses of Unreleased, Released, Complete, Complete-No Charges, and On Hold are also automatically created.
You can close jobs of any status except jobs that are Closed, Pending Close, Pending Bill Load, and Pending Routing Load.
You can purge jobs that were closed in a now closed period. You can also purge repetitive schedules that were changed to statuses of Complete-No Charges and Cancelled in closed periods.
Oracle Engineering automatically implements engineering change orders (ECOs) with Release, Schedule, and Implement statuses for jobs with statuses of Unreleased and schedules with statuses of Unreleased, Released, and On Hold. You can optionally choose to implement Open status ECOs using the WIP:Exclude ECOs profile option. See: Work in Process Profile Options, and ECO Statuses in the Engineering User's Guide.
Note: Oracle Engineering does not implement ECOs on non-standard discrete jobs.
When an ECO is implemented in Oracle Engineering, the system automatically regenerates the bills of material for unreleased jobs and schedules to reflect the impact of the ECO.
The impact of an ECO implementation on Released, Complete, or On Hold repetitive schedules depends on whether repetitive assemblies have been moved beyond the Queue intraoperation step of the first routing operation.
See Overview of Engineering Change Orders and Defining Engineering Change Orders in the Engineering User's Guide.
Oracle planning products includes the assembly supply and component demand of jobs with statuses of Unreleased, Released, Complete, and On Hold. Because planning uses different planning algorithms for repetitive manufacturing, repetitive statuses do not impact how repetitive schedule supply and demand is viewed.
Other Sources
Overview of Material Requirements Planning, Oracle MRP User's Guide
Overview of the Planner Workbench, Oracle Advanced Planning Implementation and User's Guide
Job and repetitive schedule statuses determine what information is listed on reports. For example, if a job has a status of Closed, Compete-No Charges, or Cancelled, information about that job and its component requirements is not listed on the Discrete Job Shortage Report since shortages on jobs with these statuses do not need to be filled.
You can view discrete job and repetitive schedule information regardless of status. For example, you could view the component material requirements for a closed job using the View Discrete Jobs window.
| Status Report | Unreleased | Released | Complete | Complete No Charges | On Hold | Cancelled | Closed | Pending Mass Loaded (Rep) |
|---|---|---|---|---|---|---|---|---|
| Discrete Job Data Report | Yes | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| Discrete Dispatch Report | Opt | Yes | Yes | No | Yes | No | No | N/A |
| Discrete Job Listing Report | Yes | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| Discrete Job Pick List Report | Yes | Yes | Yes | No | Yes | No | No | N/A |
| Discrete Job Routing Sheet | Yes | Yes | Yes | No | Yes | No | No | N/A |
| Discrete Job Shortage Report | Yes | Yes | Yes | No | Yes | No | No | N/A |
| Discrete Job Value Report | Yes | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| Expense Job Value Report | No | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| Job Lot Composition Report | Yes | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| Move Transaction Report | No | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| Repetitive Line Report | Yes | Yes | Yes | No | Yes | No | N/A | Yes |
| Repetitive Pick List Report | Yes | Yes | Yes | No | Yes | No | N/A | N/A |
| Repetitive Routing Sheet | Yes | Yes | Yes | No | Yes | No | N/A | N/A |
| Repetitive Schedule Data Report | Yes | Yes | Yes | Yes | Yes | Yes | N/A | Yes |
| Repetitive Schedule Shortage Report | Yes | Yes | Yes | No | Yes | No | N/A | N/A |
| Repetitive Value Report | No | Yes | Yes | Yes | Yes | Yes | N/A | N/A |
| Resource Performance Report | No | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| Resource Transaction Report | No | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| WIP Account Distribution Report | No | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| WIP Account Summary Report | Yes | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| WIP Location Report | No | Yes | Yes | Yes | Yes | Yes | No | N/A |
| WIP Outside Processing Report | No | Yes | Yes | Yes | Yes | Yes | No | N/A |
| WIP Offsetting Account Report | Yes | Yes | Yes | Yes | Yes | Yes | Yes | N/A |
| WIP Value Report | No | Yes | Yes | Yes | Yes | Yes | No | N/A |
Note: Reports that are printed with processes, such as importing and purging jobs and schedules, are not included in the above table.