Oracle Bills of Material Documentation Updates
This section contains important information. Please read this section for the latest updates and additions to your user's guide.
Creating a Routing
Step 8 currently reads as follows:
To use a standard operation, choose Copy Standard Operation from the Special menu and select a standard operation code.
Instead, it should read as follows:
To copy or reference standard operations into a routing, use the Operation Code list of values. You can define a new standard operation by selecting Standard Operations from the Special menu.
See:
Creating a Routing
Creating a Standard Operation
Mass Changing Bills of Material
If you do not wish to replace the values for the Suppy Type, Supply Subinventory, and Supply Locator fields, you must enter the current value when executing a mass change. If you leave the Supply Type, Supply Subinventory, and Supply Locator fields blank when entering component changes, their values will be replaced by the blank (null) value when the mass change is executed.
See: Mass Changing Bills of Material
Assigning Resources to a Department
The Resources window has two new fields. They are the Exception Set field and the Check CTP check box. The Check CTP check box tells the system to use this resource in a Capable to Promise (CTP) check. The Exception Set field was added to accommodate online capacity planning.
See: Assigning Resources to a Department
Creating a Product Family
Item Categories Flexfield Structure Configuration
You must configure the Product Family structure of the Item Categories Flexfield to exactly match System Items structure of the System Items Flexfield. These structures must remain in sync whenever system items are changed.
Defining Profile Options for Product Family Item 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.
Product Family Categories
Each product family corresponds to an item category. A new category is added for each product family item that is defined. The relationship between the product family item and the product family category is established by the equality of their concatenated key flexfield segment values. The category has the same name as the product family item. Consequently, product family item categories have the same flexfield structure as the System Items Flexfield. A new structure called Product Family has been defined for the Item Categories Flexfield. Each product family member item and the product family item itself are assigned to the corresponding category within the Product Family category set. The assignment is removed when an item is no longer a member of a product family.
See:
Creating a Product Family
Overview of Item Categories
Defining Category Sets
Flow Manufacturing
Overview of Flow Manufacturing Procedures
Product Synchronization (Sync)
When creating product sync for a standard item or a product family item you do not have to create a forecast, master demand schedule and / or master production schedule. This step is not part of the product sync procedure and can be performed at any time before generating the mixed model map.
Also, creating flow routings for product family items is optional.
See: Overview of Flow Manufacturing Procedures, Product Sync
Defining Flow Manufacturing Standard Processes
The introductory paragraph on Standard Processes currently reads as follows:
Standard Operations for flow manufacturing allow you to create standard processes for a regular manufacturing line as well as a flow manufacturing line.
Instead, it should read as follows:
Standard Processes can only be created and used with Oracle Flow Manufacturing.
Note: Operations and standard operations can only be created and used with Oracle Bills of Material.
When defining a Standard Process, you must select a department.
See: Defining Flow Manufacturing Standard Processes
Defining Flow Manufacturing Standard Events
The introductory paragraph on Standard Events currently reads as follows:
Standard Operations for flow manufacturing allow you to create standard events for a regular manufacturing line as well as a flow manufacturing line.
Instead, it should read as follows:
Standard Events can only be created and used with Oracle Flow Manufacturing.
Note: Operations and standard operations can only be created and used with Oracle Bills of Material.
The Operation Resources button described in Step 3 has been changed to Event Resources.
See: Defining Flow Manufacturing Standard Events
Defining Flow Manufacturing Line Operations
Line Operations can only be created and used with Oracle Flow Manufacturing.
The introductory paragraph on Standard Events currently reads as follows:
Standard Operations for flow manufacturing allow you to create line operations for a regular manufacturing line as well as a flow manufacturing line.
Instead, it should read as follows:
Line Operations can only be created and used with Oracle Flow Manufacturing.
Note: Operations and standard operations can only be created and used with Oracle Bills of Material.
See: Defining Flow Manufacturing Line Operations
Creating a Flow Routing
The note between steps 3 and 4 currently reads as follows:
You can also create alternate standard (non-flow) routings for the same item.
Instead, it should read as follows:
To create a standard (non-flow) routing for the same item, you must first switch to the Bills of Material responsibility.
WIP Alternative Region
The fields in the WIP alternative region described in step 16 are available but not necessarily applicable to Flow Manufacturing users.
Product Family Field
The Product Family field in the Routing Details window, described in step 19, indicates whether an item is a member of a product family. This field is read-only and will only contain data if an item is a member of a product family.
Operation Times and Yields
Whenever changes are made to a flow routing, the operation times, operation yields, and total product cycle time should be recalculated. These operation times and operation yields are used in the mixed model map calculations.
The term "system calculated"as used in Step 23 has been changed to "rolled-up." Step 23 currently reads:
To use system calculated operation times, select Calculate Operation Times from the Special menu.
Instead, it should read:
To use rolled-up operation times, select Calculate Operation Times from the Special menu.
Attention: In all other occurrences of the description "system calculated," substitute "rolled-up."
After you calculate operation times in step 23, perform the following steps:
1. Switch to the Operation Times alternative region and optionally enter operation yield values for processes and / or line operations
Note: Operation yield values are required to perform calculation of operation yields.
2. To calculate cumulative yield, reverse cumulative yield, and net planning percent select Calculate Operation Yields from the Special menu.
Note: You can also manually enter these values.
See: Creating a Flow Routing
Calculating Operation Times
The Attention in this section currently reads as follows:
The mixed model map calculations are based exclusively on the system calculated operation times.
Instead, it should read as follows:
The user determines whether the mixed model map calculations are based on rolled-up or user entered times.
The term total time has been changed to elapsed time. Elapsed time will always refer to user elapsed time or system elapsed time.
In the Flow Routing window the unit of measure for all times is hours.
See: Calculating Operation Times
Operation Times Calculations
The way that operation times are calculated has changed. The scheduled flag is not considered when calculating labor time or machine time. Consequently, regardless of whether the resource is scheduled it will be considered in the machine time and labor time calculations. However, the calculation for system elapsed time does consider the scheduled flag. Only resources that are scheduled will contribute to the system elapsed time.
Note: If you have parallel processes and / or line operations, the process and / or line operation with the longest resource time should be scheduled because the system elapsed time calculation should always consider the longest resource time.
See: Operation Times Calculations
Entering Mixed Model Map Parameters
Demand Type poplist described in Step 4 allows you to select forecast, master demand schedule (MDS) or master production schedule (MPS).
See: Entering Mixed Model Map Parameters
Saving a Baseline
The first paragraph is misleading. Only one baseline can be saved for each product family and line combination.
In the Saved Baseline window you can select the Find button to view all of the saved baselines.
See: Saving a Baseline
Operation Yields Calculations
Calculating Net Planning Percentages does not include processes or line operations that are option dependent.
The Net Planning Percent example is misleading. The following table illustrates the net planning percent calculations in more detail.
| 10
| 1
| 1 .
|
| 20
| .80
| (1)(.80) + (.05)(1)(.80)
|
| 30
| 1
| (1)(.80)(1) + (.05)(1)(.80)(1)
|
| 40
| 1
| (1)(.80)(1)(1) + (.05)(1)(.80)(1)(1)
|
See: Operation Yields Calculations
