Repetitive Component Issues and Returns
To issue components from inventory to repetitive schedules or to return components from repetitive schedules to inventory, you must select a repetitive assembly and line.
Repetitive Component Issues
When you issue to a repetitive schedule, the system determines which components must be issued based on the start date and number of schedule days entered.
Positive Requirements
For positive requirements, WIP component issue transactions are automatically allocated to specific repetitive schedules on a first in-first out basis based on the schedule's start date. If there is more than one open schedule, issues are allocated to each schedule until there are no more open schedules. If you over-issue, the entire over-issue quantity is allocated to the last open schedule.
For positive requirements, WIP component return transactions are allocated on a last in - first out basis, based on the schedule's start date.
Negative Requirements
For negative requirements, WIP negative component issue transactions are automatically allocated to specific schedules on a first in - first out basis. WIP negative component issue transactions supply the components to Oracle Inventory as a part of normal production. If there is more than one open repetitive schedule, negative component issues are allocated to each schedule until there are no open schedules to allocate to. If you over-issue a negative component, the entire over-issue quantity is allocated to the last open schedule.
Multiple Schedules
When you have more than one active schedule for an assembly on a line, material transactions automatically allocate the correct amount of material to each schedule. The system assumes that you work on older schedules first and charges the earliest schedule first followed by the next earliest schedule and so on.
For example, suppose a repetitive schedule has been released to produce 100 assemblies ABC on 10-JAN and 200 assemblies ABC on 11-JAN. If you issue 200 assemblies' worth of components on 11-JAN, then 100 assemblies' worth of components are charged to the first schedule and the remaining 100 assemblies worth of components to the second schedule.
Phantoms
Phantom assemblies can be used in repetitive schedules. At the time the schedule is defined, the phantom's requirements are exploded and added to the schedule at the operation where the phantom was assigned.
Repetitive Component Returns
When you return components from a repetitive schedule, you must enter a start date and number of schedule days to default the return quantities.
Positive Requirements
For positive requirements, WIP component return transactions are automatically allocated to specific repetitive schedules on a last in-first out basis. If there is more than one open repetitive schedule, each schedule is allocated until there are no more open repetitive schedules to allocate to. If you over-return, the entire over-return quantity is allocated to the first open repetitive schedule.
Negative Requirements
For negative requirements, WIP negative component return transactions are automatically allocated to specific repetitive schedules on a last in-first out basis. If there is more than one open repetitive schedule, negative component returns are allocated to each schedule until there are no more open repetitive schedules to allocate to. If you over-return, the entire over-return quantity is allocated to the last open repetitive schedule.
See Also
Issuing and Returning Specific Components
Issuing and Returning All Push Components
WIP Material Transaction Types
By-Product Recovery
