How You Resequence Work Order Operations

As a production operator, you can resequence a subsequent operation to be executed next to avoid waiting for availability of resources or materials for an operation. The resequencing of operations enables you to avoid any time delays in executing work order while continuing to make progress.

Let’s take an example of a work order with 5 operations, 10,20, 30, 40, and 50. Now, you define the operations 20, 30, and 40 as resequenceable operations because these can be executed in any sequence. Operations 10 and 50 are count point operations.

As a production operator, when you report completion of operation 10, all the resequenceable operations 20, 30, and 40 are available in the dispatch list for execution. However, the ready quantity is by default available for operation 20. Let’s assume that materials required to perform operation 20 are unavailable and resources required to perform operation 30 are unavailable. Hence you would like to perform operation 40 next to continue to make progress and meet the customer delivery date. To do this, you must invoke the resequence action.

To resequence an operation, follow these steps:

1. On the Review Dispatch List page, search for the work order that has resequenceable operations.
   All resequenceable operations display for the work order. The Ready quantity is available only for the operation that has the next execution sequence. Here’s how the dispatch list looks for our example:

   Work Order - Operation Sequence	Execution Sequence	Status	Start Date	Quantity
   WO1000 - 10	1	Complete	T1	10
   WO1000 - 20	2	Ready	T2	10
   WO1000 - 30	3	Ready	T3	0
   WO1000 - 40	4	Ready	T4	0

2. Select the work order operation that you want to resequence. For example, operation 20.
3. Click the Resequence icon besides the work order operation 20. A dialog opens for you to resequence the operation.
4. Choose an operation that you want the operation to be resequenced as next operation, that’s operation 40.
5. Click Save and Close.

Results:

On the Review Dispatch List page, the operation 40 is now resequenced as a next operation with execution sequence 2. The Ready quantity is now available for the resequenced operation. Also, the operations are rescheduled automatically in the background so that the operation start, and completion dates are now realigned with the execution sequences.

Here is how the dispatch list looks after the resequence action for our example:

Work Order - Operation Sequence	Execution Sequence	Status	Start Date	Quantity
WO1000 - 10	1	Complete	T1	10
WO1000 - 40	2	Ready	T2	10
WO1000 - 20	3	Ready	T3	0
WO1000 - 30	4	Ready	T4	0

You can reject, or scrap and also perform inspections on a resequenceable operation similar to a count point operation. If you complete partial quantities in resequenceable operations, the rest of the quantities must traverse the same path. However, you can reverse the entire quantity in an operation and select a different execution path. You can’t report outputs in resequenceable operations.

Integrating applications like Supply Planning, Production Scheduling, and Costing will consider the execution sequence to plan, schedule, and cost the work order operations respectively. When you complete all the resequenceable operations 40, 20, and 30, the ready quantity moves to the succeeding count point operation 50.

nm

Note: You can’t use FBDI to perform resequence action while transacting operations.

Note: You can't resequence work order operation quantities that are in in process status. If the work order operations are resequenced, then the operation yield values are not recomputed.