Supply Types (Oracle Work in Process)


	Previous	Next		Contents	Index	Glossary	Library

Supply Types

Supply types control how component materials are supplied to discrete jobs and repetitive schedules in Oracle Work in Process, how materials are planned in Oracle Master Scheduling/MRP and Supply Chain Planning, and how materials are costed in Oracle Cost Management.

You can assign supply types to the items you define in Oracle Inventory. You can also assign supply types to components when you create bills of material in Oracle Bills of Material and Oracle Engineering. See: Defining Items, Work In Process Attribute Group, and Creating a Bill of Material.

In Oracle Work in Process, you can change the defaulted Based on Bill (see below) supply type that is assigned as you define jobs and schedules.

Below is a list of the supply types and their uses:

Assembly Pull Assembly Pull components are issued to discrete jobs and repetitive schedules when you complete assemblies in Work in Process. They are pulled from the supply subinventory assigned to the component requirement.

If you must assign pull components to a bill of material or job that is not associated with a routing, you must assign an Assembly Pull, rather than operation pull, supply type.

You cannot assign this supply type to a non-standard discrete job if you have not specified an assembly or bill of material reference for that job.

Based on Bill The Based on Bill supply type is Work in Process specific. When you define a discrete job or a repetitive line/assembly association in Oracle Work in Process, the supply type for the assembly defaults to Based on Bill and assembly components are supplied based upon their bill of material supply types. See: Creating a Bill of Material.

If the supply type for a job or line/assembly association is changed, the new supply type is applied to all component material requirements. For example, if you change the supply type of a job assembly from Based on Bill to Assembly Pull, the supply types of all assembly components are changed to Assembly pull. You can update the supply types of individual material requirements using the Material Requirements window in Oracle Work in Process. See: Adding and Updating Material Requirements.

The system automatically changes components with a supply type of Operation Pull to Assembly Pull, when the Based on Bill supply type is applied to a job or repetitive schedule that has a bill of material but lacks a routing or operations.

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.

Operation Pull Operation pull components are issued to discrete jobs and repetitive schedules when you complete backflush operations. Components are pulled the supply subinventory assigned to the component.

You cannot assign this supply type to an assenbly without a routing or a non-standard discrete job without a routing.

You can assign this supply type to assemblies that have routings with no operations or when the routing has disabled operations. However, all components with a supply type of operation pull are automatically changed to assembly pull.

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.

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.

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.

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.

Assembly Pull	Assembly Pull components are issued to discrete jobs and repetitive schedules when you complete assemblies in Work in Process. They are pulled from the supply subinventory assigned to the component requirement.
	If you must assign pull components to a bill of material or job that is not associated with a routing, you must assign an Assembly Pull, rather than operation pull, supply type.
	You cannot assign this supply type to a non-standard discrete job if you have not specified an assembly or bill of material reference for that job.
Based on Bill	The Based on Bill supply type is Work in Process specific. When you define a discrete job or a repetitive line/assembly association in Oracle Work in Process, the supply type for the assembly defaults to Based on Bill and assembly components are supplied based upon their bill of material supply types. See: Creating a Bill of Material.
	If the supply type for a job or line/assembly association is changed, the new supply type is applied to all component material requirements. For example, if you change the supply type of a job assembly from Based on Bill to Assembly Pull, the supply types of all assembly components are changed to Assembly pull. You can update the supply types of individual material requirements using the Material Requirements window in Oracle Work in Process. See: Adding and Updating Material Requirements.
	The system automatically changes components with a supply type of Operation Pull to Assembly Pull, when the Based on Bill supply type is applied to a job or repetitive schedule that has a bill of material but lacks a routing or operations.
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.
Operation Pull	Operation pull components are issued to discrete jobs and repetitive schedules when you complete backflush operations. Components are pulled the supply subinventory assigned to the component.
	You cannot assign this supply type to an assenbly without a routing or a non-standard discrete job without a routing.
	You can assign this supply type to assemblies that have routings with no operations or when the routing has disabled operations. However, all components with a supply type of operation pull are automatically changed to assembly pull.
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.
	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.
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.
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.

Supply Types

See Also