Bills of Material

Routing Basics

A routing defines the step-by-step operations you perform to manufacture a product. Each routing can have any number of operations. For each operation you specify a department that determines the resources you may use for that operation.

A primary routing is the list of operations most frequently performed to build a product. You can define one primary routing and many alternate routings an item. When you define a new primary routing, you specify only the item (no alternate name) and you can assign a routing revision. For example, you can define a routing for an item that includes two operations-an assembly and a testing operation. You typically build your product with these operations, so you define this routing as the primary routing for the item.

The following table presents an example primary routing.

Manufacturing Scheduling

Oracle Manufacturing schedules production orders and operation dates using three scheduling methods:

• Detailed scheduling
• Repetitive line scheduling
• Dynamic lead time offsetting

• Promise ship dates for orders
• Plan material
• Plan resources
• Purchase material
• Schedule material
• Schedule resources

Manufacturing Lead Times

This chapter tells you everything you need to know about manufacturing lead times. This chapter covers the following topics:

• Overview of Lead Time Management
• Calculating Lead Times

 

Manufacturing Lead Time Computations

Oracle Manufacturing uses Item, routing, operation, and resource information to compute fixed, variable, and processing lead times for manufactured items.Item and routing information is updated as part of the computation. Lead times are not calculated for purchased items even if they have a routing.

When computing manufacturing lead times, primary routings are automatically updated with lead time and offset percents. As with the item lead time attributes, you can also manually assign these values.

Lead Time Percent
Oracle Manufacturing stores the lead time percent for each routing operation as the percent of manufacturing (processing) lead time required for previous operations, calculated from the start of a job to the start of an operation.

For example, if an item's manufacturing lead time is two days and the primary routing has two operations with the same duration (1 day), the first operation's lead time percent is zero and the second operation's lead time percent is 50%.

Offset Percent
Oracle Manufacturing stores the offset percent for each resource on a routing operation as the percent of manufacturing (processing) lead time required for previous operations, calculated from the start of the job to the start time of a resource at an operation.

For example, both operations in the previous example for lead time percent require one day (eight hours) to perform. If you have two different resources assigned to the second operation, and each resource requires four hours to complete their task, the offset percent is 50% for the first resource and 75% for the second resource.

Lead Time Lot Size
Processing lead time is computed as the time required to complete 1 lead time lot size of an item (the time required to complete the second scheduled job). Bills of Material determines an item's lead time lot size from two item master fields: standard lot size and lead time lot size.

For items that you plan and cost by the same lot size, you can specify a value only for the standard lot size. Bills of Material then computes manufacturing lead time using the standard lot size quantity.

For items that you plan with one lot size and cost with a different lot size, you can enter a lead time lot size. Bills of Material then calculates manufacturing lead time using this value (rather than the standard lot size). If an item does not have a value for the standard or lead time lot size, Bills of Material uses a quantity of one to compute manufacturing lead times.

Fixed and Variable Lead Times
You can automatically compute processing, fixed, and variable lead times for manufactured items, whether they are produced using discrete jobs or repetitive schedules.

A value of zero is assigned to the fixed, variable, and processing lead times of a manufactured item that does not have a routing and is not assigned to a production line

Bills of Material

Oracle Manufacturing and Oracle Order Management use bills of material to store lists of items that are associated with a parent item and information about how each item is related to its parent. Oracle Manufacturing supports standard, model, option class, and planning bills of material.

Standard Bill of Material
A standard bill of material is the most common type of bill and lists the mandatory components, the required quantity of each component, and information to control work in process, material planning, and other Oracle Manufacturing functions.
Examples : include bills for manufacturing assemblies, pick-to-order bills, kit bills, and phantoms.

A configuration bill (a type of standard bill) is a set of option choices made from a model bill that comprise a buildable, sellable product. Configuration items and bills are automatically created from model bills after a customer chooses options on a sales order. Or, you can manually create configuration bills by choosing options directly from a model bill.

Model Bill of Material
A model bill of material defines the list of options and option classes you can choose in Oracle Order Management to order a configuration. A model bill also specifies mandatory components or included items that are required for each configuration of
that model.

• You do not order or build the model itself: you order and build configurations of the model.
• A model bill can be either assemble-to-order or pick-to-order.

WIP Fields

Count Point and Autocharge
When you define operations in Oracle Bills of Material, you can specify whether an operation is a count point and whether resources at that operation should be automatically charged during a move transaction. You can update this information in Work in Process using the Operations window. Operations that are non-count point/autocharge operations must be defined as backflush operations.

You can define which operations in a routing record move transactions (and there by do the backflushing if its enabled) by defining how resources are consumed at that operation. The Count Point and Autocharge check boxes work together. In the following discussion, the Count Point and Autocharge check boxes can be set to either on or off. However, you cannot set Count Point on and Autocharge off.

When you move assemblies from an operation with Count Point on / Autocharge on operation to another count point operation set the same way, Work in Process automatically completes all Count Point off / Autocharge on count point operations between them.

To transact a Count Point off / Autocharge off count point operation, you must explicitly move assemblies into and out of that operation. Moving assemblies past a Count Point off / Autocharge off count point operation acts as though the operation did not exist in the routing. This is particularly useful for rework or debug operations that are performed on a portion of the assemblies you process.

If you issue components with a supply type of Operation pull to an assembly at a Count Point off / Autocharge off count point operation, Work in Process backflushes these components when you move out of the Count Point off / Autocharge off count point operation into a count point operation that allows backflushing. Work in Process never pulls components with a supply type of Assembly pull from Count Point off/ Autocharge off count point operations. However, you must turn Backflush on for Count Point off / Autocharge off count point operations. The Backflush field should always be turned on for the last operation in a routing.
Notes
1. If count point is on then auto charge needs to be on.
2. If Both count point and auto charge are off then backflush needs to be on.
3. When count point is on and blackflush is on we dont need to explicitly do the move transaction to and from the operation to do material transaction but if count point is off(and thus autocharge) and balckflush is on then we need to do a move transaction to and from that operation to make the backflush takes place
Ex:
OP seq    Count-Point    Autocharge    Backflush
10           Y                         Y             Y
20           N                         N             Y
30           N                         Y             Y
40           Y                         Y             Y

In the above example if we move from Op 10 to 40(To Move) then resource charges takes place @10,30 & 40 but backflush takes place only @ 10 and 40 though 20 and 30 are also backflush enabled.
To make backflush @20 we need to explicitly move to OP20. i.e we need to do move transaction from OP10 to OP20 and then OP20 to OP 40
Again if we need backflush @30 then we need to from OP20 to OP30 and then OP30 to OP40.

Effects when Count point is OFF
Let consider a routing as shown below

Bills of Material Parameters

Use bill of material parameters to define modes of operation and default values for an organization that affect functions such as bill definition, bill deletion, and assemble-to-order configuration numbering.

Define bill of material parameters for each organization in which you use bills or routings. (Bill parameters are specific to, and must be defined for, each organization.) Doing so ensures access to resource, outside processing, and overhead cost information for certain cost management functions.

• No (default value) : The system creates supply only for the top level assemble to order (ATO) item or configuration.
• Auto Created Configuration Items Only : Creates supply for any lower level configuration generated because of the specific sales order configuration.                                                                                                                      Note: This option does not create supply for any lower level configuration that was matched to a preconfigured item.
  
• Auto Created Configuration Items and ATO Items : Creates lower level supply for all ATO items, preconfigured items, and autocreated configured items.                                                                                                                              Note: Supply is created even for ATO items set up as standard mandatory components on the model bill. Only use this option if you do not expect to have inventory on hand for your ATO items and preconfigured items.

• Yes: If you select this value, phantom routing components and resources and overheads are included in the cost of the higher level assembly. Routing resource costs are also included in capacity planning.
• No: This is the default. This value specifies that only components are included in the higher assembly's cost, not resources and overheads.

• Yes: This is the default. This value specifies that phantom subassembly components inherit the operation sequence number of their parent or higher level assemblies.
• No: If you select this value, phantom subassembly components maintain their own operation sequence numbers

Creating Alternates

An alternate bill describes an alternate list of component items that produce an assembly. An alternate routing describes an alternate manufacturing process that produces an assembly.

Custom Deletion Statements and Constraints

You can create custom deletion statements to specify from which database table to delete data that meets the deletion constraint criteria. Create custom deletion constraints to enforce your unique business rules. Custom deletion constraints identify the rows in a table that meet certain conditions for deletion.

Oracle provides seeded deletion statements and constraints, which you can view using the Deletion Statements and Deletion Constraints windows. You cannot modify seeded deletion statements and constraints, though.

To create a custom deletion constraint:

1. Navigate to the Deletion Constraints window.
2. Enter a name for the deletion constraint.
3. Indicate whether the constraint is enabled. An enabled deletion constraint means that it is in effect when the delete concurrent program runs.
4. Select what kind of delete entity the constraint applies to: item, bill, routing, component, or operation.
5. Select the name of the product that applies to this deletion constraint. The Product Name field enables you to group deletion constraints by product.
6. Enter the SQL Select Statement that the delete concurrent program is to execute. You cannot update SQL statements for predefined deletion constraints.
7. Indicate whether to delete if there are rows found or no rows found by the SQL Select Statement.
8. Enter a failure message from Oracle Application Object Library's message dictionary to display if the delete fails.

To create a custom delete statement:

Department

• A department is an area within your organization that consists of one or more people, machines, or suppliers, where you want to collect costs(using resources), apply overhead, and compare load to capacity.
• You assign a department to each operation in a routing, and assign resources that are available for that department.

Department Class

Use department classes to group departments for shop floor scheduling and control, and to identify manufacturing cells and flexible machine centers. Department classes are used for reporting purposes.

Resource

Use resources to define the time an assembly spends at an operation and the cost you incur at the operation (Both Resource and Resource Over Head). A resource is anything you require to perform, schedule, or cost, including but not limited to: employees, machines, miscellenous, Amount and currency (outside processing services can be any of these type). A resource and usage rate for all scheduled activities is required in a routing. Scheduled resources can include queue, setup, run, and move time.

When you define your departments, you assign the resources available in each department and the shifts that each resource is available. For each operation you define, you specify a department and list of resources and usages. An operation can use any resource that is available in the department, but you do not need to use all resources assigned to the department.

• Before you can define resources, set up your units of measure and unit of measure conversion rates. Some resources may represent currency such as a fixed charge resource, but currency resources cannot be scheduled since their unit of measure is not time-based.
• Set the site level profile option BOM: Hour UOM to hold the unit of measure that represents an hour. Oracle Work in Process prevents you from scheduling resources whose unit of measure is not in the same unit of measure class as the hour unit or measure and has no conversions defined to the hour unit or measure.

More On Resource

Outside Processing
Indicate whether to enable the outside processing resource, and if so, enter its item number.
Important: If you specify PO Move or PO Receipt, Oracle Purchasing uses this item when it creates requisitions for your
outside processing resource

Billing
If this resource services requests for maintaining assets, you can optionally enter the billable item in the Billing region Item field.
Oracle Enterprise Asset Management (eAM) can use Oracle Bills of Material resources to service requests for asset maintenance. Identifying the billable item for the resource enables eAM to determine the cost of work performed by the resource for the item.

• Competence
• Skill Level
• Qualification

Equipment

To group similar types of equipment by resource:
You can define Equipment Types to group similar types of resources. For example, you can define an Equipment Type of Forklift.

Pre-requisities
Define an item of type equipment i.e. Enable the equipment check box in the physical attribute tab.
Equipments are invenotry expense items.

Employees

You can define the roles which represent what an employee can do for a required task. For example, a role could be defined as Cycle Counter, or a Case Picker.

To group employees by resource:


1. Navigate to the Employees window. Do this by choosing the Employees button from the Resources window. You can choose the Employees button if the Resource is a Person type.

2. Select an Employee from the list of values to associate with the resource. If you defined skills in the Resources window, then only those employees that have the competence, skill level, and qualification required for the resource appear in the
list of values.

3. Save your work.

Note: If you have Warehouse Management installed, you can use the Resources form to define employees qualified for each resource. For example, a hazardous materials manual resource is indicated by entering the resource name and description, as well as which employees are capable of performing hazardous material tasks. See:

Resource Setup Information

You can create a performance model for machine and resource setups to include time from one setup to another, including the time required to perform the work. If one of your scheduling objectives is to sequence or group jobs based on their required setup, you can also include a penalty factor—or weighted value—in the scheduling
calculation.

Resources defined in the Operation Resources window can have multiple setup types. You can define these setup types with an identifying user code or a numerical value. Any two setup types within a resource can have a transition time and a transition
penalty, which means that the scheduler needs the specified time to transition from the former setup to the latter. Also in doing so a certain transition penalty is incurred. This penalty is used to weigh the relative merits of doing the setup versus delaying the job versus cycle time.

The setups for a resource are independent of the department that the resource belongs to.
The setup type for a particular operation resource is defined in the Operation Resources window. This data displays in the Resource Requirements window during routing explosion. Setup resources and resource instances are only exploded during scheduling.

To define machine and resource setup types:

Reason for a resource capacity change

You can assign a reason for a resource capacity change in the Capacity Changes window by selecting the reason from a list
of values. Define the reasons for this list of values in the Resource Capacity Change Reasons window.
Pre-requisities
The resource capacity change reasons list of values are defined as lookups. Lookup codes must be decided upon and defined during the implementation process.

Machine Down Codes

The Machine Down Codes can be accessed and modified from lookup types menu:

Resource Group

Assigning Resources to a Department

avigate to the Resources window. You can do this by choosing the Resources button from the Departments window.

The Resources window is split into owned and borrowed resources.

Workday Calendar

A workday calendar defines the valid working days for a manufacturing organization and consists of repeating pattern of days on and days off and exceptions to that pattern. This allows you to, for example, designate a normal workday as a scheduled downtime day, or designate a holiday as a workday.

You can define one or more workday calendars and assign them to any number of organizations, and any number of organizations can share a calendar. You can specify the start and end dates, and the weekend schedule for each calendar.

Shifts

For a given workday calendar, you can specify any number of shifts. Each shift can have a different weekend schedule and a list of specific work interval start and end times. For both calendars and shifts, you can assign sets of workday exceptions and repeating workday patterns.

Shifts inherit workday exceptions and workday patterns from the base calendar. Shift exceptions can either add to or override those of the base calendar. If an exception on the base calendar changes, those shifts that do not have an overriding exception on that date will automatically reflect the change. Those shifts that do have an overriding exception on that date will not reflect the change and must be changed manually if they are to reflect the change in the base calendar.

Shift exceptions are applied to a calendar the same way as workday calendar exceptions by selecting individual exception days, by defining exception templates, or by copying a set of exceptions from another shift. The following diagram illustrates the steps Bills of Material uses to determine workdays from an organization's workday calendar and exception template information.

Workday Patterns

You can also define a series of repeating workday patterns for a given calendar. For example, you have a repeating two-week pattern where you work five days the first week, and three days the second week. Or, you have a repeating pattern of 17
consecutive workdays, followed by four days off. When you build the calendar, Oracle Bills of Material automatically determines the valid workdays for you, based on the patterns you specify.

Workday Exceptions

There are three ways to apply exceptions to the workday calendar:

• selecting individual exception days
• loading them from an exception template, another calendar, and another calendar shift
• copying a set of exceptions from another calendar

Set ups

BOM Business Terminologies

Assembly
It is the product which is manufactured in the Plant.  It need not be the Finished goods which are shipped to ultimate customer.  The intermediate product which are manufactured in the plant can also be an assembly (it could rather be called as Sub-Assembly).

Component
These are basically materials which are used for manufacturing the assembly.  These components could be raw materials, consumables, by-products etc.

Valid Parent/Component Relationships
The following table lists valid components for each parent item type.

• 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.
• When model or option class bills are components to another bill of material, the component supply type is phantom.

A primary bill is a list of the components you most frequently use to build a product. An alternate bill is another list of components for the same basic assembly. The primary bill is the default for rolling up costs, defining a job, and calculating cumulative item lead times.

• You must define a primary bill before you define an alternate. A primary bill can have many alternate bills. Any bill of material type can have an alternate.
• Oracle Master Scheduling/MRP uses the primary bill to plan your material. Oracle Order Management uses the primary bill for model and option class products to list available options.
• When you build an item, roll up costs, and perform other functions that use bills of material, you can specify whether to use the primary bill (the default) or an alternate bill. You can also use engineering change orders to control changes to primary and alternate bills of material.
• You can use an alternate to define an engineering bill or routing. The alternate used as a prototype variation from the primary manufacturing bill that produces essentially the same assembly.
• Bills and routings can share alternate labels. If you create an alternate bill with the same label as an alternate routing, components are assigned to operations on the alternate routing. If there is no routing with the same alternate label, components are assigned to operations on the primary routing.

• Assign each revision a unique three character alphanumeric revision identifier (such as A, B, B1, and so on) and a revision date. Revisions are sorted according to ASCII rules.
• Each revision must be greater than the previous revision. Therefore, you cannot use revision 10 after revision 9 because, according to ASCII sorting, 10 precedes 9.
• Use letters and/or numbers to label revisions. Letters are always upper case and numbers may include decimals. To ensure that revisions sort properly (according to ASCII sorting rules), decimals should always be followed by a number. Therefore, valid revisions can include: A, B, 1, 2, A1, B1, 1A, 1B, 0.0, 0.1, A.0, A.1, and so on. When you create an item or a routing, the beginning revision defaults to the value for Starting Revision in the Organization Parameters window.
• When you create or update a bill of material or routing, you can choose to create a new revision or modify an existing revision. When adding new revisions, you should be sure that the revision date you enter does not overlap with other existing revision dates. Revisions are time-stamped, so you can determine the latest revision for multiple revisions defined on the same date. New revision numbers must be greater than the revision number of the currently effective revision.
• Different versions of a bill of material or routing can be defined within the same revision. You can change component information for bills or operation information for routings without modifying the revision.

•  BOM: Standard Item Access
•  BOM: Planning Item Access
•  BOM: Model Item Access (also controls access to option class items)

Creating a Bill of Material

A bill of material contains information on the parent item, components, attachments, and descriptive elements.
You can create an engineering, manufacturing, or asset (maintenance) bill, copy an existing bill, or reference a common bill. When you create a bill, it exists only in the current organization. To use a bill in another organization, you must either copy it or reference it as a common.

• You can define the Basis field as Item or Lot for mandatory components in an ATO Option Class or an ATO Model bill of material.
• You can only define the Basis field as Item for option items, option classes or submodels in an ATO Option Class or ATO Model bill of material.
• You can only define the Basis field as Item when the WIP Supply Type is Phantom

• Pick-to-order bills cannot have fractional component quantities if Oracle Order Management is installed.
• Pick-to-order option class components cannot have negative values.
• Components with Check ATP turned on cannot have negative or zero quantities.
• If the component has Quantity Related turned on, then the component quantity cannot be fractional or negative.
• If an implemented component has Quantity Related turned on, then the component quantity must be equal to the number of reference designators.
  

Date/Unit Effectivity

• 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.

ECO tabbed region

Open the ECO tabbed region and verify the following:
The Implemented check box indicates whether the component is implemented.
Unchecked: Component is on a pending Engineering Change Order (ECO)
Checked: Component is on an implemented ECO or was added directly to the bill If the component is part of a pending or implemented ECO, the ECO field displays this ECO.

Component Details

• 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.

Mat. Control (Subinventory and Locator)

Order Manegment

• the Check ATP field has a value other than None
• the ATP Components field has a value other than None

 

Shipping Details Fields

Populating Oracle Configurator Schema (CZ)

Enterprise Item data is created and maintained in the Oracle Inventory and Bills are maintained in Oracle Bills of Material. This data imported into the Oracle Configurator schema as read-only data for access by Configurator Developer and the run-time Configurator.

The Oracle Configurator schema includes a specialized control table CZ_DB_SETTINGS for custom data import.
The data stored in the CZ schema includes:

• Configuration models
• Item and Model structure data
• Configuration rules
• User interface definitions
• Publication records
• Configurations

• Populate Configuration Models
• Refresh a Single Configuration Model
• Refresh All Imported Configuration Models
• Disable/Enable Refresh of a Configuration Model

Bill / Component Validation Rules

The following bill and component validation rules apply when defining, copying, or mass changing bills of material:

1. Depending on the setting of the profiles that limit access to different bill types (BOM: Model Item Access, BOM: Planning Item Access, BOM: Standard Item Access), you may not be able to modify bills.
2. You cannot add a component with an operation sequence number that does not exist in the routing. The only exception is for operation sequences that are equal to 1.
3. You cannot add a component to a bill where the component item is the same as the parent.
4. You cannot add a component to a bill where the same component, with the same operation sequence and effectivity, already exists on the bill.
5. Only manufacturing items can be added to manufacturing bills.
6. You cannot add a component to a bill that is being referenced as a common bill from another organization, where the component does not exist in the other organization.
7. You cannot add components to common bills.
8. For ATO, PTO, and phantom bills where the parent item has ATP Components set to No, you receive a warning when you add a component that has either the item attributes Check ATP set to Yes or ATP Components set to Yes. The warning says "Order details for the parent item specifies NO for ATP Components", but you can add the component.
9. You cannot add an optional component to a bill that is neither model or option class.
10. You cannot add a component, whose planning percent is not equal to 100, to a standard bill.
11. You cannot add a mandatory component, whose planning percent is not equal to 100 and has the Forecast Control attribute set to Consume or None, to a model or option class bill.
12. When adding a component to a bill, the mass change will set the Check ATP component attribute to No if the component quantity is less than or equal to 0.

Creating a Product Family

A product family is a grouping of products whose similarity in resource usage, design, and manufacturing process facilitates planning at an aggregate level. A product family cannot be a part of a Standard, Model, Option Class, or Planning Bill of Material. Consequently, a product family is a single level bill. Members of a product family can belong to one and only one product family.

You will be able to plan based on the planning percentages and effectivity of the product family members.
Caution: You must make sure that the Product Family flex structure is configured to match the System Items structure. If the System Items structure is changed it should be reflected in the Product Family structure as well.

To create a product family item:
1. Navigate to the Master Item window.
Note: If you are a Flow Manufacturing customer, select Product Family from the Flow Manufacturing window. The product family template is automatically applied.
2. Apply the product family template.
To define a default template for product family items, you must select a template from the INV: Product Family Item Template Name profile option. The template assigned in this profile option will be automatically applied when you create a new product family item.

Main tab : Operations

To define a routing operation you first specify an operation sequence number to indicate the order to perform operations. Components in your bill of material can reference an operation sequence. Next, you can choose either a standard operation, or you can enter a new operation.

Date Effectivity

Open the Date Effectivity tabbed region and enter an effective date range.

Other fields in line level

Operation Yield

Routing Details

Routing revision

Operations Resources

You can associate multiple resources with an operation on a routing. For each resource, you can determine if you want to include that resource in scheduling and lead time calculations. You can also collect costs for a resource on a routing if you specified the resource as a costed resource. If a resource is unavailable, you can define alternate resources. An alternate resource can be a single resource or a set of resources.

Resource parents and resource sets are used to group similar resources. Routings can then be defined with their general resource requirements, while WIP lots are tracked with the usage of the specific resources. While a resource can belong to several resource sets, a resource can only belong to one parent resource. When a WIP lot is at an operation with a parent resource or resource set attached to it, you are prompted to enter a valid resource used in processing the WIP lot.

To assign a resource to a routing operation:
Navigate to the Operation Resources window. You can do this by choosing the Operation Resources button from the Routings window.

1. Yes: Include this resource when scheduling an operation from a job or repetitive schedule and calculating manufacturing lead time for the assembly.
2. No: Do not include scheduling the operation or calculating the lead time.
3. Prior: Include this resource when scheduling a job or schedule by backward scheduling the previous operation from the end of this resource. Use this option when setup resources can work in parallel with previous operations. The lead timeis calculated the same way Work in Process schedules the job or repetitive schedule.
4. Next: Include this resource when scheduling a job or repetitive schedule by forward scheduling the next operation from the start of this resource. Use this option when the teardown of the current operation can overlap with the execution of the next

• Manual: Work in Process does not automatically charge this type of resource to a job or repetitive schedule. You must manually charge it to a job or repetitive schedule using Work in Process.
• PO Receipt: Automatically charge this resource upon receipt of a purchase order in Oracle Purchasing. The assemblies are not automatically moved to the next operation upon receipt, so you must manually move them using Work in Process.
• PO Move: Automatically charge this resource upon receipt of a purchase order in Oracle Purchasing and move the assemblies to the Queue intraoperation step of the next operation, or to the To move intraoperation step if this is the last operation.
• WIP Move: Work in Process automatically charges this type of resource to a job or repetitive schedule when you complete an operation.

Lead Time Offsetting Computations

Bills of Material lets you automatically compute item, bill of material and routing information required for dynamic lead time offsetting. You can also maintain lead time information manually.
Manufactured Items
Dynamic lead time offsetting uses the following lead time attributes for discretely manufactured items:

• fixed lead time
• variable lead time
• preprocessing lead time

• processing lead time
• fixed lead time

• preprocessing time
•  processing lead time
• post-processing lead time

Dynamic Manufacturing Lead Times

Oracle Bills of Material computes the fixed and variable portions of manufacturing (processing) lead time using routings and detailed scheduling.

• Fixed lead time: That portion of time required to build an assembly that is independent of order quantity—for example, setup or teardown.The fixed lead time is calculated by scheduling a job for a quantity of zero with the current date as the job start date.
  Because all lead-time offsetting uses the fixed and variable lead time of an item, the processing lead time represents an estimated lead time. Processing lead time represents the typical time required to build a typical number of units.

Bills of Material uses the following formulas to compute fixed lead times:
Schedule a job for zero quantity beginning on the system date and compute fixed lead
time as follows:
completion date (of one item) - system date

• Variable lead time: That time required to produce one additional unit of an assembly. The variable lead time is calculated by scheduling a second job for the lead time lot size quantity, with the system date as the job start date.
  Variable lead time is expressed as days per unit.

• Processing (manufacturing) lead time

• Lead time lot size = 10 units
• System date = 01-JAN
• End date for work in process job for 1 unit = 10-JAN
• End date for work in process job for 10 units = 13-JAN

Optional and Mutually Exclusive

BOM of the option class Samsung Monitor has 4 options  14”M, 15”M, 16”M and 17”M

Case1 : None are optional and None are mutually exclusive => As none is optional you have to select all the options

Case2: One/more than one are optional But None are mutually exclusive => out of the two optional you can select one or/none

Case 3 : Out of 14” and 15”, one can select one/none. 16” is optional, can be selected if required.17” need to be selected

Case 4 : All are optional but None are mutually exclusive  => Chose any number or  no options on the option class bill

Case 5 : None are optional but All are mutually exclusive => Choose one and only one option from the option class

Case 6 : All are optional and All are mutually exclusive => Choose one or no options from the option class