Previous	Next		Contents	Index	Navigation	Glossary	Library

Oracle Work in Process explodes through a phantom subassembly to the components as if the components were tied directly to the parent assembly. You can define routing for phantoms assemblies the same way as other assemblies. Work in Process ignores phantom assembly routings when you define a job or repetitive schedule.

You can compute manufacturing and cumulative lead times for phantom assemblies that have routings. If you do not want to offset the components of a phantom assembly in the planning process, exclude the phantom item from the lead time calculations.

In general, phantom assemblies behave like normal assemblies when they represent a top level assembly, such as when you master schedule them or manufacture them using a discrete job. As a subassembly, however, they lose their identity as distinct assemblies and are a collection of their components. The components of the phantom subassembly are included on the job and on the pick list of the job--not the phantom itself.

Oracle Master Scheduling/MRP plans the phantom subassembly using the lot-for-lot lot-sizing technique. Otherwise, the same rules apply to phantoms as for other assemblies. Set the lead time of a phantom to zero to avoid lead time offset during the planning process.

When model or option class bills are components to another bill of material, the component supply type is phantom. See: Two-Level Master Scheduling.

The cost rollup treats phantom assemblies the same as regular assemblies. The phantom is treated as a distinct entity; the cost elements of the phantom (material, resource, and so on) are added to the cost elements of the higher assembly. Also, the full cost rollup process sets the pending phantom assembly burden to 0.

See Also

Item Attributes Listed in Alphabetical Order