Completing Repetitive Schedules (Oracle Work in Process)


	Previous	Next		Contents	Index	Glossary	Library

Completing Repetitive Schedules

You can complete repetitive assemblies from repetitive schedules into inventory using the Completion Transactions and Move Transactions windows. You can also return completed assemblies back to schedules using these windows.

Note: You can also complete WIP assemblies using the Inventory Transaction Interface and the Open Move Transaction Interface.

Routings

When you complete an assembly from a repetitive schedule with a routing, assemblies are transacted from the To move intraoperation step in the last operation of the schedule into the completion subinventory and, if required, locator for the line. You cannot complete more assemblies than are in the To move intraoperation step of the last operation. If you did not specify a completion subinventory and locator for the line, then you must specify a subinventory and possibly a locator when you perform the completion transaction.

Complete versus Complete-No Charges

When the number of assemblies completed equals the number of planned assemblies, the schedule is complete and the status of the schedule changes to either Complete or Complete-No Charges. The difference between these two statuses depends upon whether a future schedule exists. The end date of the schedule does not determine when a schedule is complete, and a repetitive schedule can be active after its end date.

If there is a subsequent schedule with a status of Unreleased within the autorelease days time fence, or a schedule with a status of Released, Complete, or On Hold, then the status of the current schedule changes to Complete-No Charges and is automatically released the next schedule if appropriate. If there is no subsequent schedule that meets this requirement, then the status of the current schedule changes to Complete. This keeps the current schedule active so that you can transact any unused or excess material and perform delayed resource and material transactions.

Multiple Schedules

When you have more than one active schedule open for an assembly on a line at one time, the completion transactions automatically allocate the correct completion quantity to each schedule starting with the oldest schedules.

For example, a repetitive schedule is scheduled to complete 100 assemblies on 10-JAN and 200 assemblies on 11-JAN. On 11-JAN when you complete 200 assemblies, the transaction completes 100 assemblies to the first schedule and the remaining 100 assemblies to the second schedule.

Rolling Material Forward

When the number of assemblies completed plus the assemblies in the Scrap intraoperation steps equals the number of assemblies planned, the schedule is checked for any excess material. Over-issuing results in excess material. This can occur as a result of pushing too much material to the schedule or from reducing the total quantity of the schedule.

If there is any excess material, the system checks to see if there is a future schedule with a status of Unreleased within the autorelease days time frame, or a schedule with a status of Released, Complete, or On Hold following the newly completed schedule. If so, this excess material charge rolls forward to the next schedule, the next schedule is released (if appropriate), and the status of the completed schedule changes to Complete-No Charges. If an appropriate schedule is not found, the status changes to Complete and the excess material charges do not roll forward. You can then analyze the schedule and transact the excess material.

Roll forward also occurs if you cancel a schedule and there is an existing Unreleased schedule within the time fence specified by the Repetitive Autorelease Days Parameter. See: Repetitive Manufactuing Parameters.

Determines the time period within which the system automatically releases the next Unreleased schedule.

When you complete a repetitive schedule, the system searches within the autorelease time frame for an Unreleased schedule, or for a schedule with a status of Released, Complete, or On Hold. If one exists, the status of the newly completed schedule changes to Complete-No Charges and the future schedule is automatically released. If no such schedule exists, the status of the schedule changes to Complete. If more than one schedule exists within the autorelease time frame, only one schedule is released.

Stopping Repetitive Schedules

Repetitive schedules stop when the number of assemblies completed plus the assemblies in the Scrap intraoperation steps equals the number of planned assemblies. No further action is needed. You do not close repetitive schedules. To prevent accidental charges, change the status of any Complete schedules to Cancelled or Complete-No Charges.

Over-completion

You can complete more assemblies than are scheduled on a line. For example, if the production process yields a few more assemblies than planned, you can complete the extra assemblies using the Completion Transactions window. Completions are allocated across schedules on a first in-first out basis until only one schedule remains with a status of Complete.

If the remaining schedule does not have a routing, you can complete a quantity of assemblies greater than the total quantity on the schedule. If the remaining schedule does have a routing, you must first increase the total quantity on the schedule by either increasing the total quantity, increasing the daily quantity, or by increasing the processing days before you can overcomplete this schedule. You must then move these additional assemblies from the Queue intraoperation step of the first operation sequence to the To move intraoperation step of the last operation sequence. You now have sufficient quantity in the To move intraoperation step of the last operation sequence to complete from the schedule without overcompleting. You can optionally define an additional schedule so you can complete from the line without overcompleting from any schedule.