24 Feb 10 Supply Types on Oracle Bill Of Material

Bulk

Bulk component requirements can be viewed and are displayed on reports. They can be used to communicate to the shop floor that bulk components must be used but need not be transacted.

Bulk components are not backflushed nor do they default when issuing all components for an assembly. You can, however, manually issue specific bulk components to a discrete job or repetitive schedule.

Supplier

Supplier component requirements can be included on bills of material. Requirements for supplier components are created when you define discrete jobs and repetitive schedules in Work in Process.

Supplier component requirements can be viewed and are displayed on reports. They provide information on the component materials that your suppliers provide but need not be transacted.

Supplier components are not backflushed nor do they default when issuing all components for an assembly. You can, however, manually issue specific supplier components to discrete jobs and repetitive schedules.

Push

Push components can be issued directly to discrete jobs and repetitive schedule as required. You can specify the subinventory from which to issue push components, though Work in Process defaults the supply subinventory associated with the component.

Phantom

Phantom components can be assigned to bill of material component subassemblies and subassembly items in Oracle Bills of Material and Oracle Engineering. Components of phantom subassemblies are used as if they were tied directly to the parent assembly. Phantom supply types cannot be assigned to jobs and repetitive lines/assembly associations in Work in Process. See: Phantoms, Oracle Bills of Material User’s Guide.

Phantoms behave normally when they are top level assemblies, such as when master scheduled or manufactured on a discrete job. As subassemblies, they lose their distinct identity and become a collection of their components. Phantom components (not the phantom itself) are included on discrete jobs and repetitive schedules and are listed on the Discrete Job and Repetitive Schedule Pick List Reports.

Oracle Master Scheduling/MRP and Supply Chain Planning plans phantom subassemblies with lot-for-lot lot sizing. Otherwise, phantoms are planned like other assemblies. You must set the lead time of a phantom to zero to avoid lead time offset during the planning process. Oracle Master Scheduling/MRP and Supply Chain Planning ignores demand time fences, planning time fences, and order modifiers when planning phantom subassemblies.

When assembly costs are rolled up in Oracle Cost Management, the material costs, but not the routing costs, of phantom assemblies are included in the cost of the higher level assemblies that include those phantoms.