This section describes the use of certain major fields.
The item sequence indicates the sequence of the item on the bill. It is used to sort components on reports and when choosing options from a model bill in Oracle Order Management. This defaults to the value of the highest existing component item sequence plus the value of the BOM: Component Item Sequence Increment profile option. If this profile option is not set, the default is 10. You can override or change this number.
Every routing carries operations. You can use the Routings form to assign operations to routings. Each operation must have a sequence number called the Operation Sequence Number.
On a bill, the operation sequence indicates the order in which you perform operations on a routing. You can have the system automatically generate Operation Sequence Numbers using a user-defined increment factor. A profile must be created where you can indicate how much the Operation Sequence Number will increment every time a new operation is generated. You can change the generated value if necessary in the Routings form. Valid values range from 1 to 9999999.
You can assign any component to any operation on the routing, including all components to the same operation (such as the first operation). The planning process assigns material requirement dates based on the operations to which you assign each component.
You can define bills of material for items with or without routings. If you use routings, you can either define the bill first or the routing first.
With component-to-operation assignments, you can schedule and issue component material to the operation that requires the component on the exact requirement date. You can also assign the same component on the bill to different operations on the routing, with different usage quantities for each assignment.
If no routing exists for the item, all components default to operation sequence 1. You cannot change this value until you define a routing for the item. After you define the routing, you can update your bill of material with routing operations if you want specific component-to-operation assignments.
If you define the routing before you define a bill, assign components to valid routing operations, or an operation sequence 1 when you define the bill. If you define an alternate routing and then define the alternate bill, you can assign components to the alternate routing operations. If you define an alternate bill and no alternate routing exists, you can assign components to the primary routing operations.
Effective date fields appear throughout Oracle Manufacturing products. These are defined as follows:
Effective From / Effectivity Date: First date and time the component or operation becomes effective. For components, the effective date is the first day a component becomes effective for a bill. For routings, it is the first day an operation becomes effective in a routing.
Effective To / Disable Date: Last date and time the component or operation is effective. After this date, you can no longer assign the operation to a routing. From this date, you can no longer assign the component to a bill.
Inactive On: The first date and time the component or operation is inactive. As of 12:00AM on this date, you can no longer assign the component to a bill or the operation to a routing. If this date equals the effective date, the component or operation is inactive.
To avoid confusion, make sure that effective dates for one revision do not overlap with those of another.
For example, if you must introduce three new components to a bill in a specific order, you should assign each change to the appropriate parent item revision. So, component 1 of revision B may be effective today, component 2 of revision C tomorrow, then component 3 of revision D may be effective the following day. If there are two operations on a routing and you replace the first operation with a new operation, you should set the effective date for the new operation to the date the operation you are replacing becomes inactive.
Effective dates can be either the current date or a date in the future; you cannot enter a date in the past.
For components, the default effective date is the later of the current date or the date entered for the bill. If an inactive date already exists for the operation sequence/item combination, the default effective date of any subsequent rows with the same operation sequence/item combination is the same as the inactive date. That means that the subsequent operation sequence/item combination becomes effective immediately after the previous one becomes inactive.
You cannot assign duplicate components to the same operation with overlapping effective date ranges. For example, suppose component A001 at operation 10 is effective from 10-JAN to 14-FEB. You may not add another component A001 at operation 10 to the bill with an effective date of 10-FEB.
Use Oracle Master Scheduling/MRP to identify any overlapping effective dates.
The yield is the percentage of the component that survives the manufacturing process. A yield factor of 0.90 means that only 90% of the usage quantity of the component on a bill actually survives to be incorporated into the finished assembly.
To compensate for the expected gain or loss, any function that explodes a bill of material increases or decreases the material requirements for the component, based on the yield.
| component requirements = component usage quantity / component yield |
For example, when Master Scheduling/MRP plans a component with a usage quantity of 10 units per assembly and a component yield of 50% (or 0.5), the resulting component requirements increase to 20 units per assembly.
Note: You cannot enter component yield for an option class item or for any components of a planning bill.
The default is 1, indicating 100% yield (no loss or gain).
Master Scheduling/MRP uses component planning percentages in forecast explosions through planning, model, and option class bills of material.
Assign planning percentages to components on model, option class, and planning bills.
Note: You can assign planning percents to mandatory components on model or option class bills only if the Forecast Control attribute is set to Consume and Derive.
Enter a component planning percent to specify a distribution percentage for the components. You can enter a planning percent greater than 100 to overplan a component. The default is 100.
The Enforce Integer Requirements attribute enables you to generate demand in integer quantities and eliminate pegging partial quantities across the demand. If you pass the demand in integer values for lower level components in the BOM, you avoid passing fractional values across the BOM. This enables pegging to reflect the true integer nature of supply and demand. You can select from one of three following values:
Up: The system rounds the gross requirements for every demand for the component to the next higher integer value. To set the value to up, you must set the item master attribute Rounding in Oracle Inventory.
Down: The system rounds the gross requirements for every demand for the component to the next lower integer value.
None: This is the default value. Leaving the value at none allows pegging in fractional quantities across the BOM.
Additional Information: If you use Oracle Work in Process, select None. Oracle Work in Process does not support Enforce Integer Requirements.
The extended quantity of the component used in the parent item is calculated as follows:
| ((explosion quantity of parent item x component usage quantity) / component yield) / (1 - shrinkage rate for parent) |
Work in Process pulls components from the supply subinventory and the locator within the subinventory during backflushing.
Assign a supply subinventory and locator, if applicable, to components that have a supply type of Assembly pull or Operation pull. You must specify a supply locator if you have mandatory locator control for the supply subinventory. The system validates any item subinventory and locator restrictions you defined during your Oracle Inventory setup.
The following pertains to options for model and option class bills. All components are mandatory on standard and planning bills. Model and option class bills can have both mandatory and optional components.
The Optional field indicates whether the component is mandatory or optional. The Mutually Exclusive field applies only to option class bills and indicates whether you can choose one or many options within an option class.
Oracle Order Management uses the Mutually Exclusive check box in combination with the Optional check box to determine the number of option items you can or must choose to order the components of the option class bill. Refer to the table below for details on how the Optional check box and the Mutually Exclusive check box work together.
| Description | [ ] Mutually Exclusive(default) | [X] Mutually Exclusive |
|---|---|---|
| [X] Optional | Choose any number or no options on the option class bill | Choose one or no options on the option class bill |
| [ ] Optional (default) | Choose at least one option on the option class bill | Choose one, and only one, option on the option class bill |
Check ATP indicates whether to perform an ATP check on the component along with the item if the following conditions exist for the item in the Organization Items window, Oracle Inventory:
the Check ATP field has a value other than None
the ATP Components field has a value other than None
When you add the component to the bill of material, Check ATP is automatically selected if, in the Organization Items window for the component, the Check ATP field has a value other than None. You can select or unselect Check ATP for components in the Bills of Material window, overriding the value defaulted from the Organization Items window.
See: Order Management Attribute Group.
Oracle Order Management uses the minimum and maximum quantities to determine the number of optional items available when orders are placed for components on option class bills. If you enter a minimum sales order quantity, you must also enter a maximum sales order quantity. You can only enter a minimum and maximum quantity range that contains the quantity for the component. If you update the component quantity, the minimum and maximum values are changed to include the new component quantity.
Caution: These attributes do not apply to mandatory standard components.
If the component is an option class item, you must indicate whether you want to override the default quantity for the option class when a sales order is entered (the default). Option class quantities affect the mandatory standard components assigned to the option class.
If you select None for the Sales Order Basis field, Oracle Order Management can override the default quantity for the option class. Order Management defaults the total quantity to release as the component quantity multiplied by the option class extended quantity.
If you select Option class for the Sales Order Basis field, Order Management cannot override the default quantity for the option class. Order Management calculates the total quantity to release as the component quantity multiplied by the option class extended quantity.
Note: Set the sales order basis to Option class for an ATO option class component. When creating a configuration bill, Oracle Manufacturing computes the total quantity required for a mandatory standard component as the component quantity multiplied by the option class extended quantity-regardless of the quantity entered on the sales order.
Shippable: Indicates whether the component item is shippable. The default is determined by the value of the Shippable Item attribute in the item master.
Include on Ship Docs: Indicates whether Oracle Order Management prints the components on external shipping documents, such as pack slips and commercial invoices. The default is off.
Required to Ship: Indicates whether the component is required to ship the order. You can only update this check box if the Assemble to Order item attribute for the assembly item in the Define Item window is disabled. This attribute only affects PTO included items (not ATO items or configurations).
Required for Revenue: Indicates whether the component is required to recognize revenue before you ship the order. You can only update this check box if the Assemble to Order item attribute for the assembly item in the Define Item window is disabled. This attribute is recognized by the Receivables Interface in Order Management. Required for Revenue components prevent their parent item from invoicing until they are shipped. For example, if you have an option class bill with a non-optional component with the Required for Revenue attribute set to Yes, then the option class will not invoice until the non-optional component has shipped. This field does not affect mandatory or optional components for an ATO item or configuration.
Other Sources
Overview of Material Requirements Planning, Oracle MRP User's Guide
Overview of Material Requirements Planning, Oracle MRP User's Guide
Overview of Material Requirements Planning, Oracle MRP User's Guide
Overview of Material Requirements Planning, Oracle MRP User's Guide
Overview of Two-Level Master Scheduling, Oracle MRP User's Guide
Overview of Two-Level Master Scheduling, Oracle MRP User's Guide