Previous | Next | Contents | Index | Glossary | Library |
The five intraoperation steps -- Queue, Run, Reject, To Move, and Scrap -- are defined as follows:
Queue | Assemblies in the Queue intraoperation step of an operation are waiting for you to perform work on them. Queue is the default intraoperation step for every operation in a routing. |
When you release jobs and repetitive schedules, the assembly quantity is automatically loaded into the Queue intraoperation step of the first operation. You can move assemblies from the Queue intraoperation step to any other enabled intraoperation step. | |
Run | Assemblies in the Run intraoperation step are ready to be worked on. You can move assemblies from the Run step to any other enabled intraoperation step in the routing. |
To Move | Assemblies in the To move intraoperation step of an operation have been completed and are waiting to be moved to the next operation. You can move assemblies from the To move intraoperation step to any other enabled intraoperation step in the routing. |
Before you can use the Completion Transactions window to complete assembles from jobs and schedules with routings, you must move the 'to be completed' assemblies into the To Move intraoperation step of the last operation. For this reason, the To Move intraoperation step is automatically enabled for all final routing operations. See: Assembly Pull Backflush Transactions. | |
Assemblies in the To Move step are considered complete for the operation. | |
Reject | Assemblies in the Reject intraoperation step of an operation have been rejected and are waiting to be repaired (reworked) or scrapped. You can move assemblies from the Reject intraoperation step to any other enabled intraoperation step in the routing. |
Assemblies in the Reject step may not be useable, but they are considered complete for the operation because components and resources have been consumed in their production. | |
Scrap | Assemblies in the Scrap intraoperation step are considered unusable. This step is for those assemblies whose yield loss you want to consider as a variance on the discrete job or repetitive schedule. (In some industries, scrap is considered yield loss.) You can incur this variance immediately by entering a scrap account as you move assemblies into this step. However, you can wait until the job is closed (standard and non-standard asset discrete jobs) or the period is closed (repetitive schedules and non-standard expense discrete jobs) to incur the variance. Oracle Master Scheduling/MRP and Supply Chain Planning does not consider assemblies that in Scrap steps in the MRP planning process. |
Assemblies in the Scrap intraoperation step are usually not useable. They are considered complete for the operation because components and resources have been consumed in their production. They can be recovered from scrap by moving them to another intraoperation or operation step. |
Conversely, if you are a 'push' manufacturer you might enable just the Queue and Run intraoperation steps. You would do this to simplify the process of pushing (issuing) components to assemblies in the Queue intraoperation step of the operation before you moving them to the Run step of the same operation.
Overview of Discrete Job Close
Previous | Next | Contents | Index | Glossary | Library |