Intraoperation Steps (Oracle Work in Process)


	Previous	Next		Contents	Index	Glossary	Library

Intraoperation Steps

Intraoperation steps are used to control move and resource transactions within and between operations and to track assemblies within operations. You can only move assemblies to intraoperation steps that are enabled. See: Interoperation Steps Parameter.

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.

Complete/Incomplete Operation Steps

Assemblies are considered incomplete at an operation if they are in the Queue or Run intraoperation steps. Assemblies are considered complete at an operation if they are in the To Move, Reject, or Scrap intraoperation step. When assemblies are completed at an operation, the system automatically backflushes Operation Pull components and charges resources. See: Operation Completion Moves.

Using Intraoperation Steps

The intraoperation steps that you enable and use depend on your manufacturing environment and your information requirements.

Manufacturing Environment

For example, if you are a 'pull' manufacturer you might enable just the Run and To Move intraoperations. You would do this to simplify the process of pulling assemblies into the Run step of an operation from the To Move step of a prior operation.

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.

Processing Times

As you move assemblies from one intraoperation or interoperation step to another the dates and times of these transactions are recorded. For example, you can use this information to help you determine how long assemblies spend waiting to be worked on (Queue time) and how much time they are actually being worked on (Run time).

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.

Intraoperation Steps

Complete/Incomplete Operation Steps

Using Intraoperation Steps

Manufacturing Environment

Processing Times

See Also