This section describes the use of certain major fields.
In a routing, you can define the completion subinventory and locator where you store finished assemblies upon completion. When you define a job or repetitive schedule, Work in Process uses these values as the default, and you can change the completion subinventory and locator if necessary. Upon completion of assemblies, the completion subinventory and locator you defined for the job and repetitive schedule is the default, and you can change these values if necessary.
You can define which operations in a routing record move transactions by defining how resources are consumed at that operation.
The Count Point and Autocharge check boxes work together. In the following discussion, the Count Point and Autocharge check boxes can be set to either on or off. However, you cannot set Count Point on and Autocharge off.
When you move assemblies from an operation with Count Point on / Autocharge on operation to another count point operation set the same way, Work in Process automatically completes all Count Point off / Autocharge on count point operations between them.
To transact a Count Point off / Autocharge off count point operation, you must explicitly move assemblies into and out of that operation. Moving assemblies past a Count Point off / Autocharge off count point operation acts as though the operation did not exist in the routing. This is particularly useful for rework or debug operations that are performed on a portion of the assemblies you process.
If you issue components with a supply type of Operation pull to an assembly at a Count Point off / Autocharge off count point operation, Work in Process backflushes these components when you move out of the Count Point off / Autocharge off count point operation into a count point operation that allows backflushing. Work in Process never pulls components with a supply type of Assembly pull from Count Point off/ Autocharge off count point operations. However, you must turn Backflush on for Count Point off / Autocharge off count point operations. The Backflush field should always be turned on for the last operation in a routing. See: Overview of Shop Floor Control.
In the following example, the routing has five operations. The second and fourth operations are not count points, and you must explicitly move units in and out of the fourth operation if you want to charge the job or repetitive schedule for the consumed resources.
The following table presents an example of count point operations.
Count Point Operations
| Operation Sequence | Description | Count Point | Backflush | Instructions |
|---|---|---|---|---|
| 10 | Assembly 1 | Yes-Autocharge | Yes | n/a |
| 20 | Assembly 2 | No-Autocharge | No | n/a |
| 30 | Painting | Yes-Autocharge | Yes | If color and texture do not meet standards, send to Op 40. If job meets standards, send to Op 50. |
| 40 | Painting Rework | No-Direct charge | Yes | Sand finish and repaint to meet standards. |
| 50 | Packaging | Yes-Autocharge | Yes | Ship directly to customer site when finished with this operation. |
Assign this count point to operations that you always perform in a routing, but where you do not want to monitor assembly moves into, out of, and through the operation. For example, choose this count point for non-bottleneck operations that are not labor or time-intensive, such as inspection or minor assembly operations.
Work in Process automatically completes the operation and charges its WIP move resources to your job or schedule when you record a move transaction through or beyond the operation, as with Count Point on / Autocharge on count point operations.
Work in Process does not default the operation, unlike Count Point on / Autocharge on count point operations. You can still record movements into, out of, and through the operation by overriding the default in Work in Process.
Assign this count point to operations that you do not typically perform in a routing. For example, a rework operation that you only perform on occasion. If you choose this count point for an operation, Work in Process does not complete the operation and charge its resources to your job or schedule unless you explicitly record a move transaction into and through the operation.
Work in Process does not default the operation. You can still record movements into, out of, and through the operation by overriding the default in Work in Process.
Assign this count point to operations you want to automatically default as destination operations in the Move Transactions window. You should always assign this count point to the final operation in a routing, to insure that you record move transactions into the operation, and then record completion transactions.
You can automatically complete and charge operations in a routing with this count point. Work in Process automatically completes an operation and charges its WIP Move resources to your job or schedule when you record a move transaction through or beyond the operation.
For operations that you always perform in a routing, you can also monitor assembly moves into, out of, and through the operation. For example, choose this count point for critical, time-intensive, or bottleneck operations.
Yes: Include this resource when scheduling an operation from a job or repetitive schedule and calculating manufacturing lead time for the assembly.
No: Do not include scheduling the operation or calculating the lead time.
Prior: Include this resource when scheduling a job or schedule by backward scheduling the previous operation from the end of this resource. Use this option when setup resources can work in parallel with previous operations. The lead time is calculated the same way Work in Process schedules the job or repetitive schedule.
Next: Include this resource when scheduling a job or repetitive schedule by forward scheduling the next operation from the start of this resource. Use this option when the teardown of the current operation can overlap with the execution of the next operation. The lead time is calculated the same way Work in Process schedules the job or repetitive schedule.
You can determine how each resource is charged in Work in Process. When an operation completes, Work in Process records the units applied to the job or repetitive schedule in the resource unit of measure. You can charge resources manually or automatically.
Manual: Work in Process does not automatically charge this type of resource to a job or repetitive schedule. You must manually charge it to a job or repetitive schedule using Work in Process.
PO Receipt: Automatically charge this resource upon receipt of a purchase order in Oracle Purchasing. The assemblies are not automatically moved to the next operation upon receipt, so you must manually move them using Work in Process.
PO Move: Automatically charge this resource upon receipt of a purchase order in Oracle Purchasing and move the assemblies to the Queue intraoperation step of the next operation, or to the To move intraoperation step if this is the last operation.
WIP Move: Work in Process automatically charges this type of resource to a job or repetitive schedule when you complete an operation.