Professional Documents
Culture Documents
R12 BOM Vol 1 PDF
R12 BOM Vol 1 PDF
and Engineering
Fundamentals
m y
Volume - 1 Student Guide
d e
c a
e A
c l
r a
O ly
l & On
D50083GC10
Edition 1.0
n a e
August 2007
D52045
t e r U s
I n
c l e
r a
O
Copyright © 2005, 2007, Oracle. All rights reserved.
Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
Author
Debani Banerjee
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Table of Contents
c a
Item Control Level.........................................................................................................................................1-35
Organization Assignments.............................................................................................................................1-37
Creating and Changing Organization Items...................................................................................................1-38
e A
Agenda...........................................................................................................................................................1-39
Searching Items .............................................................................................................................................1-40
c l
Search Results ...............................................................................................................................................1-41
Agenda...........................................................................................................................................................1-42
r a
Viewing Item Information .............................................................................................................................1-43
Viewing Item Revisions ................................................................................................................................1-44
O ly
Viewing Item Attributes ................................................................................................................................1-45
Viewing Item Categories ...............................................................................................................................1-46
l & On
Agenda...........................................................................................................................................................1-47
Overview of Item Cataloging ........................................................................................................................1-48
n a e
Creating Item Catalog Groups .......................................................................................................................1-49
Defining Item Catalog Groups.......................................................................................................................1-50
r s
Defining Descriptive Elements......................................................................................................................1-51
e
Concatenated Item Descriptions ....................................................................................................................1-53
t U
Defining Aliases ............................................................................................................................................1-55
I n
Practice Overview: Creating Items ...............................................................................................................1-56
Practice - Creating Items ...........................................................................................................................1-57
l e
Solution – Creating Items ..........................................................................................................................1-59
c
Practice Overview: Defining and Assigning Item Statuses ..........................................................................1-67
d
c a
Creating Bills of Material ...............................................................................................................................3-1
Creating Bills of Material ..............................................................................................................................3-2
Objectives ......................................................................................................................................................3-3
e A
Agenda...........................................................................................................................................................3-4
Bills of Material Overview ............................................................................................................................3-5
c l
Bills of Material.............................................................................................................................................3-6
Types of Bills of Material..............................................................................................................................3-8
r a
Example of BOM ..........................................................................................................................................3-10
Phantom Assembly ........................................................................................................................................3-11
O ly
Single Organization Bills of Material............................................................................................................3-13
Integration......................................................................................................................................................3-14
l & On
Agenda...........................................................................................................................................................3-16
Standard Bills of Material..............................................................................................................................3-17
n a e
Valid Parent/Component Relationships.........................................................................................................3-18
Entering Bills of Material ..............................................................................................................................3-19
t r s
Bill Details.....................................................................................................................................................3-23
e
Assigning Descriptive Elements....................................................................................................................3-24
U
Creating Reference Designators ....................................................................................................................3-25
I n
Assigning Substitute Components .................................................................................................................3-27
Capture Inverse Usage...................................................................................................................................3-29
l e
Agenda...........................................................................................................................................................3-30
c
Primary and Alternate Bills of Material ........................................................................................................3-31
r a
Alternates.......................................................................................................................................................3-33
Agenda...........................................................................................................................................................3-34
Model/Unit Effectivity Overview..................................................................................................................3-35
d e
Configure To Order Process Flow .................................................................................................................4-27
Configure to Order Environments .................................................................................................................4-28
c a
PTO and ATO BOM Models.........................................................................................................................4-30
Assemble To Order Model ............................................................................................................................4-31
Pick To Order Model.....................................................................................................................................4-32
e A
AutoCreate Configuration Items....................................................................................................................4-33
Deactivating Configuration Items..................................................................................................................4-37
c l
Agenda...........................................................................................................................................................4-39
Product Family Overview..............................................................................................................................4-40
r a
Creating Product Families .............................................................................................................................4-41
Assigning Members to a Product Family ......................................................................................................4-42
O ly
Assigning Member Planning Percentages .....................................................................................................4-43
Summary........................................................................................................................................................4-44
l & On
Maintaining Bills of Material .........................................................................................................................5-1
a e
Maintaining Bills of Material ........................................................................................................................5-2
Objectives ......................................................................................................................................................5-3
n
e r
Agenda...........................................................................................................................................................5-4
s
Bill of Material Revisions..............................................................................................................................5-5
t U
Item Revisions ...............................................................................................................................................5-6
I n
Agenda...........................................................................................................................................................5-7
Tools Menu Options ......................................................................................................................................5-8
e
Agenda...........................................................................................................................................................5-10
l
Find Indented Bills ........................................................................................................................................5-11
c
Indented Bills of Material..............................................................................................................................5-13
r a
Agenda...........................................................................................................................................................5-14
Comparing Bills of Material..........................................................................................................................5-15
d e
Creating Routings ..........................................................................................................................................6-2
Objectives ......................................................................................................................................................6-3
c a
Agenda...........................................................................................................................................................6-4
Routings.........................................................................................................................................................6-5
Primary and Alternate Routings ....................................................................................................................6-6
e A
Routings in Multiple Organizations...............................................................................................................6-7
Operations......................................................................................................................................................6-8
c l
Resources.......................................................................................................................................................6-10
Creating Routings ..........................................................................................................................................6-13
r a
Agenda...........................................................................................................................................................6-15
Lead Time Management Overview ...............................................................................................................6-16
O ly
Item Lead Time Attributes.............................................................................................................................6-18
Manufacturing Lead Time Computations......................................................................................................6-20
l & On
Lead Time Lot Size .......................................................................................................................................6-22
Offset Percent ................................................................................................................................................6-24
n a e
Lead Time Percent.........................................................................................................................................6-25
Fixed and Variable Lead Times.....................................................................................................................6-26
t r s
Cumulative Manufacturing Lead Time..........................................................................................................6-27
e
Cumulative Total Lead Time.........................................................................................................................6-28
U
Calculating Lead Times.................................................................................................................................6-29
I n
Practice Overview: Defining Routings .........................................................................................................6-31
Practice - Defining Routings .....................................................................................................................6-32
l e
Solution – Defining Routings ....................................................................................................................6-34
c
Practice Overview: Entering and Calculating Lead Times ...........................................................................6-41
OMaintaining Routings......................................................................................................................................7-1
d e
Common Bill Window...................................................................................................................................8-15
Common Routings.........................................................................................................................................8-17
c a
Common Routing Window............................................................................................................................8-18
Agenda...........................................................................................................................................................8-19
Bill and Operation Documents ......................................................................................................................8-20
e A
Defining Bill and Operation Documents .......................................................................................................8-21
Attaching Bill and Operation Documents......................................................................................................8-22
c l
Agenda...........................................................................................................................................................8-23
Deleting Items, Bills, Routings, Components, and Operations .....................................................................8-24
r a
Information That You Can Delete .................................................................................................................8-25
Deletion Process ............................................................................................................................................8-26
O ly
Deletion Constraints ......................................................................................................................................8-27
Deletion Groups.............................................................................................................................................8-29
l & On
Deletion Group Details and Results...............................................................................................................8-32
Delete Items Report .......................................................................................................................................8-34
n a e
Agenda...........................................................................................................................................................8-36
Bills of Material and Routing Open Interfaces ..............................................................................................8-37
t r s
Importing Bills of Material and Routings......................................................................................................8-38
e
Practice Overview: Copying Bills of Material..............................................................................................8-40
U
Practice - Copying Bills of Material ..........................................................................................................8-41
I n
Solution – Copying Bills of Material.........................................................................................................8-42
Practice Overview: Deleting Records...........................................................................................................8-46
l e
Practice - Deleting Records .......................................................................................................................8-47
c
Solution – Deleting Records ......................................................................................................................8-48
r a
Summary........................................................................................................................................................8-53
Engineering Overview.....................................................................................................................................9-1
O Engineering Overview...................................................................................................................................9-2
Objectives ......................................................................................................................................................9-3
m y
Objectives ......................................................................................................................................................11-4
Agenda...........................................................................................................................................................11-5
Engineering Change Orders Overview ..........................................................................................................11-6
Revised Items, Components, Operations, and Resources..............................................................................11-8
d e
ECO Access Control......................................................................................................................................11-10
c a
Agenda...........................................................................................................................................................11-12
Defining Engineering Change Orders............................................................................................................11-13
A
Creating an ECO............................................................................................................................................11-15
Viewing ECO Approval Status......................................................................................................................11-17
e
c l
Rescheduling an ECO or Revised Items........................................................................................................11-18
Changing the ECO Status ..............................................................................................................................11-19
r a
Defining Implementation Costs.....................................................................................................................11-20
Defining an ECO Revision ............................................................................................................................11-21
O ly
Defining ECO Revised Items ........................................................................................................................11-22
Defining Revised Operations.........................................................................................................................11-25
l & On
Defining Revised Resources..........................................................................................................................11-27
Defining Revised Components ......................................................................................................................11-29
a e
Assigning or Deleting Substitute Components ..............................................................................................11-31
Assigning Reference Designators..................................................................................................................11-32
n
e r
Agenda...........................................................................................................................................................11-34
s
ECO Life Cycle .............................................................................................................................................11-35
t U
ECO Revised Item Statuses ...........................................................................................................................11-37
I n
ECO Approval Statuses .................................................................................................................................11-38
ECO Approvals .............................................................................................................................................11-39
e
ECO Life Cycle Without Approval ...............................................................................................................11-42
l
ECO Life Cycle With Approval ....................................................................................................................11-43
c
ECO Approval with Oracle Workflow ..........................................................................................................11-45
r a
Summary........................................................................................................................................................11-47
d e
Summary........................................................................................................................................................12-50
c
Transferring and Copying Items, Bills and Routings...................................................................................13-1
Transferring and Copying Engineering Items, Bills, and Routings ...............................................................13-2
a
e A
Objectives ......................................................................................................................................................13-3
Agenda...........................................................................................................................................................13-4
c l
Transferring and Copying Product Information ............................................................................................13-5
Transferring Information to Manufacturing...................................................................................................13-6
r a
Copying Information to Manufacturing.........................................................................................................13-8
Practice Overview: Transferring Engineering Items ....................................................................................13-10
O ly
Transferring Engineering Items to Manufacturing ....................................................................................13-11
Solution – Transferring Engineering Items to Manufacturing...................................................................13-12
l & On
Practice Overview: Copying Engineering Items...........................................................................................13-14
Copying Engineering Items to Manufacturing ..........................................................................................13-15
n a e
Solution – Copying Engineering Items to Manufacturing .........................................................................13-16
Summary........................................................................................................................................................13-22
e r s
Setting Engineering Profile Values and Security Functions ........................................................................14-1
t U
Setting Engineering Profile Values and Security Functions..........................................................................14-2
I n
Objectives ......................................................................................................................................................14-3
Agenda...........................................................................................................................................................14-4
e
Engineering Setup Flowchart ........................................................................................................................14-5
l
Setup Steps ....................................................................................................................................................14-6
c
Profile Options...............................................................................................................................................14-8
r a
Defining ECO Types .....................................................................................................................................14-10
Defining ECO Autonumbering......................................................................................................................14-12
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Prerequisites
R12 Oracle Bills of Material and Engineering Fundamentals is an instructor-led course featuring
lecture and hands-on exercises. Online demonstrations and written practice sessions reinforce the
concepts and skills introduced.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 1
Defining Items
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 2
Objectives
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 3
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 4
Manufacturing and Engineering Items
m y
d e
ca
e A
Manufacturing and Engineering Items
c l
Manufacturing items are used in production and are created in Oracle Inventory.
r a
Engineering items are created in Oracle Engineering and are not ready for production. They are
called prototypes. Engineering items are not visible in Oracle Inventory. The Engineering Item
O ly
attribute flag is not visible in Oracle Inventory.
n a e
• You create and change engineering items using the Oracle Engineering windows.
t e r U s
• You create and change manufacturing items using the Oracle Inventory windows.
• When your engineering items are ready for production, you can transfer or copy them to
I n
Oracle Inventory as manufacturing items. When you transfer an engineering item, it
becomes a manufacturing item. When you copy an engineering item, it remains and you
l e
create a manufacturing item with a different item number.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 5
Item Functionality
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 6
Steps to Setup, Define and Maintain Items
m y
d e
ca
e A
Steps to Define and Maintain Items
1. Create the item templates
c l
r a
2. Use the templates and existing items to define items
O ly
3. Enter values for additional item attributes
4. Assign a status to the item
l & On
5. Assign categories to the item
a e
6. Enable the item in other organizations
n
t e r
7. Update the organizational-level attributes values
s
8. Define the item relationships
U
I
10. Delete items n
9. Search for items
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 7
Defining Items
m y
d e
ca
e A
Defining Items
c l
Following are the steps for creating and maintaining items:
1. Create the item templates.
r a
O ly
2. Use the templates and existing items to define items.
3. Enter values for additional item attributes.
l & On
4. Assign a status to the item.
a e
5. Enable the item in other organizations.
n
t e r
6. Update the organizational-level attributes values.
U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 8
Master Items
m y
d e
ca
e A
Master Items
c l
There are two ways you can define items from the Master Items window. You can use the
r a
Attribute Groups tab, or the Item Folder tab. The Attributes Group tab allows you to select
individual attributes, and use the tool menu to apply templates and assign organizations The
O ly
Item Folder tab enables you to create an item, apply a default template, and assign the item to
l & On
an organization all in one window.
Much of the information for an item is optional. You define only the information you need to
a e
maintain the item. Below is a list of the tabs and fields used to define items.
n
Main:
t e r U s
• Primary Unit of Measure, Dual Control, Secondary, Deviation Factor +, Deviation Factor
Inventory: I n
–, User Item Type, Item Status, Conversions, and Long Description
l e
• Inventory Item, Stockable, Transactable, Revision Control, Reservable, Check Material
c
Shortage, Lot Expiration (Shelf Life) Control, Shelf Life Days, Lot Control, Starting Lot
r a Prefix, Starting Lot Number, Cycle Count Enabled, Negative Measurement Error, Positive
Measurement Error, Serial Generation, Starting Serial Prefix, Starting Serial Number, Lot
O Status Enabled, Serial Status Enabled, Lot Split Enabled, Lot Merge Enabled, Lot
Defining Items
Chapter 1 - Page 9
Translate Enabled, Lot Substitution Enabled, Bulk Picked, Locator Control, Restrict
Subinventories, Restrict Locators, Default Move Order Receipts Subinventory, Default
Receiving Subinventory, and Default Shipping Subinventory
Bills of Material:
• BOM Allowed, BOM Item Type, Base Model, Engineering Item (Oracle Engineering
only), Effectivity Control, and Configurator Model Type
Asset Management:
• Asset Item Type, Activity Type, Activity Cause, Shutdown Type, and Activity
Notification Required
Costing:
• Costing Enabled, Inventory Asset Value, Include in Rollup, Cost of Goods Sold Account,
and Standard Lot Size
Purchasing:
• Purchased, Purchasable, Use Approved Supplier, Allow Description Update, RFQ
Required, Outside Processing Item, Outside Processing Unit Type, Taxable, Tax Code,
Receipt Required (Three–Way Invoice Matching), Inspection Required (Four–Way
Invoice Matching), Default Buyer, Unit of Issue, Receipt Close Tolerance, Invoice Close
Tolerance, UN Number, Hazard Class, List Price, Market Price, Price Tolerance,
Rounding Factor, Encumbrance Account, Expense Account, and Asset Category
Receiving:
• Receipt Date Action, Receipt Days Early, Receipt Days Late, Overreceipt Quantity
Control Action, Overreceipt Quantity Control Tolerance, Allow Substitute Receipts,
m y
Allow Unordered Receipts, Allow Express Transactions, Receipt Routing, and Enforce
Ship–To
d e
Physical Attributes:
ca
e
Vehicle, Container Type, Internal Volume, Maximum Load Weight, Minimum FillA
• Weight Unit of Measure, Unit Weight, Volume Unit of Measure, Unit Volume, Container,
c l
Percentage, Dimension Unit of Measure, Dimension Length, Dimension Width,
Dimension Height, Collateral Item, Event, Equipment, Electronic Format, Downloadable,
and OM Indivisible
r a
General Planning:
O ly
• Inventory Planning Method, Planner, Make or Buy, Min–Max Minimum Quantity, Min–
l & On
Max Maximum Quantity, Minimum Order Quantity, Maximum Order Quantity, Order
n a e
Cost, Carrying Cost Percent, Source Type (Replenishment), Source Organization, Source
Subinventory, Safety Stock Method, Safety Stock Bucket Days, Safety Stock Percent,
MPS/MRP Planning:
t e r U s
Fixed Order Quantity, Fixed Days Supply, and Fixed Lot Multiplier
I n
• Planning Method, Forecast Control, Exception Set, Pegging, Planned Inventory Point,
Create Supply, Shrinkage Rate, Round Order Quantities, Acceptable Early Days,
l e
Repetitive Planning, Overrun Percentage, Acceptable Rate Increase, Acceptable Rate
c
Decrease, Calculate ATP, Reduce MPS, Planning Time Fence, Planning Time Fence
r a Days, Demand Time Fence, Demand Time Fence Days, Release Time Fence, Release
O Time Fence Days, Substitution Window Type, and Substitution Window Days
Defining Items
Chapter 1 - Page 10
Lead Times:
• Preprocessing, Processing, Postprocessing, Fixed, Variable, Cumulative Manufacturing,
Cumulative Total, and Lead Time Lot Size
Work in Process:
• Build in WIP, Supply Type, Supply Subinventory, Supply Locator, Overcompletion
Tolerance Type, Overcompletion Tolerance Value, Scheduling Penalty Inventory Carry,
and Scheduling Penalty Operation Slack
Order Management:
• Customer Ordered, Customer Orders Enabled, Shippable, Internal Ordered, Internal
Orders Enabled, OE Transactable, Pick Components, Assemble to Order, ATP
Components, Ship Model Complete, Check ATP, ATP Rule, Picking Rule, Default
Shipping Organization, Default SO Source Type, Returnable, RMA Inspection Required,
Financing Allowed, Over Shipment Tolerance, Under Shipment Tolerance, Over Return
Tolerance, and Under Return Tolerance
Invoicing:
• Invoiceable Item, Invoice Enabled, Accounting Rule, Invoicing Rule, Tax Code, Sales
Account, and Payment Terms
Service:
• Contract Item Type, Contract Duration, Contract Duration Period, Service Duration,
Subscription Dependency Enabled, Service Importance Level, Billing Type, Service
Request Enabled, Provisionable, Serviceable Product, Service Billing Enabled, Defect
m y
Tracking Enabled, Recovered Part Disposition, Installed Base Tracking, Asset Creation,
Starting Delay (Days), and Instance Class
Web Option:
d e
c
• Web Status, Orderable On the Web, Back Orderable, and Minimum License Quantitya
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 11
Master Item Window
m y
d e
ca
e A
Master Item Window
Create Item:
c l
• Item
r a
• Description
• Item attribute groups O ly
• Create item catalog
l & On
a e
• Assign item to organization
n
t e r
• Manage attributes at the master level
Organization Item Window:
U s
n
• Manage attributes at the organization level
I
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 12
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 13
Item Templates
m y
d e
ca
e A
Templates
c l
Oracle Inventory has several predefined templates that you can use to define and update items
r a
or you can create your own templates. Templates make initial item definition easier.
If you regularly define many items that share the same values for a number of attributes, you
O ly
may want to define item templates to avoid duplicating effort. You can predefine templates
one item.
l & On
with relatively few attributes enabled because you can apply more than one template to define
a e
You can enable attributes and assign them values in each template that you create. When you
n
t e r s
apply a template to an item, Oracle Inventory updates only the attributes that are enabled for
the template. If an attribute item template is null, it will not change a pre-set item attribute.
U
I n
When you apply a template to an item, you copy all existing, non-blank attribute values from
the template to the item. You may apply multiple templates to a single item. The last values
l e
assigned are retained, and blanks don’t overlay assigned values. The order in which templates
c
are applied is important.
a
Item templates change item attributes consistently.
r
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 14
Available Templates
m y
d e
ca
e A
Available Templates
c l
The following is a list of available templates provided by Oracle:
• ATO Model
r a
• ATO Option Class
• ATO Item O ly
• Finished Good
l & On
• Kit
n a e
• PTO Model
t e r
• Outside Processing Item
U s
• PTO Option Class
• Phantom Item I n
l e
• Planning Item
c
• Purchased
r a
• Reference Item
O • Subassembly
Defining Items
Chapter 1 - Page 15
• Supply Item
• Freight
• Product Family
• Equipment
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 16
User Defined Templates
m y
d e
ca
e A
User Defined Templates
c l
You can define your own templates using the Item Templates window. The window does not
r a
validate the template attributes. You can define a template with contradictory attributes. When
you use a user defined template to define an item, Oracle Inventory then verifies the attributes
O ly
are valid for a given item. If an attribute is not updatable for an item, the value from the
a e
To make defining templates easier, you can use the Copy From function on the Tools menu in
n
e r
the Item Templates window. This opens the Copy Template window, where you can copy
s
attributes from one or more attribute groups to a new template. You can also create a hybrid
t U
template by copying attributes from multiple templates.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 17
Item Templates Summary
m y
d e
ca
e A
Items Templates
c l
Use this window to create and change item attribute templates.
r a
The Open button utilizes existing template information.
O ly
The New button allows for the entering of a new template.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 18
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 19
Item Attribute Controls
m y
d e
ca
e A
Item Attribute Controls
c l
Item attributes are information about an item, such as order cost, lead time, and revision
control.
r a
One of the prerequisites for defining items (and assigning values to item attributes) is setting
O ly
attribute controls. There are two types of attribute control:
l & On
• Control level (Master level vs. Org level): Determines whether you have centralized
(Master level) or decentralized (Organization level) control of item attributes. Attributes
a e
maintained at the Master level have the same attribute values in each organization in
n
t e r s
which an item is assigned. For example, you maintain an item’s primary unit of measure at
the Master level. Attributes maintained at the Organization level may have different
U
I n
attribute values in different organizations. For example, an item may be min–max planned
in a distribution organization but MRP planned in a production organization.
l e
• Status control: Describes whether certain status attributes have default values that appear
c
when you assign a status code to an item, and whether status codes control those attribute
r a values after the defaults are assigned to an item. The status attributes are:
- BOM Allowed
O - Build in WIP
Defining Items
Chapter 1 - Page 20
- Customer Orders Enabled
- Internal Orders Enabled
- Invoice Enabled
- Transactable
- Purchasable
- Stockable
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 21
Item Defining Attributes
m y
d e
ca
e A
Item Defining Attributes
c l
An item defining attribute identifies the nature of an item. What designates an item as an
r a
engineering item is the attribute Engineering Item, but what controls the functionality of the
item are the collection of attributes that describe it. You can buy an engineering item if you
O ly
want to; simply set Engineering Item, Purchased, and Purchasable to Yes.
l & On
When you set an item defining attribute to Yes, the item is automatically assigned to the
default category set of the corresponding functional area. For example, if you set Inventory
a e
Item to Yes, the item is automatically assigned to the default category set for the Inventory
n
functional area.
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 22
Item Statuses and Attributes
m y
d e
ca
e A
Item Statuses and Attributes
c l
Status attributes enable and disable the functionality of an item over time. Each status attribute
r a
allows you to enable the item for a particular use. For example, if you set the status attribute
Purchasable to Yes, you can put the item on a purchase order.
O ly
The status attributes are related to the item defining attributes. You cannot enable a status
& On
attribute if you do not set the corresponding item defining attribute to Yes.
l
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 23
Item Attribute Groups
m y
d e
ca
e A
Item Attribute Groups
c l
Refer to the Oracle Inventory User’s Guide for more information on Item Attributes.
Main:
r a
O ly
• Primary Unit of Measure, Dual Control, Secondary, Deviation Factor +, Deviation Factor
–, User Item Type, Item Status, Conversions, and Long Description
Inventory:
l & On
n a e
• Inventory Item, Stockable, Transactable, Revision Control, Reservable, Check Material
Shortage, Lot Expiration (Shelf Life) Control, Shelf Life Days, Lot Control, Starting Lot
t e r U s
Prefix, Starting Lot Number, Cycle Count Enabled, Negative Measurement Error, Positive
Measurement Error, Serial Generation, Starting Serial Prefix, Starting Serial Number, Lot
I n
Status Enabled, Serial Status Enabled, Lot Split Enabled, Lot Merge Enabled, Lot
Translate Enabled, Lot Substitution Enabled, Bulk Picked, Locator Control, Restrict
l e
Subinventories, Restrict Locators, Default Move Order Receipts Subinventory, Default
c
Receiving Subinventory, and Default Shipping Subinventory
r a
Bills of Material:
O • BOM Allowed, BOM Item Type, Base Model, Engineering Item (Oracle Engineering
only), Effectivity Control, and Configurator Model Type
Defining Items
Chapter 1 - Page 24
Asset Management:
• Asset Item Type, Activity Type, Activity Cause, Shutdown Type, and Activity
Notification Required
Costing:
• Costing Enabled, Inventory Asset Value, Include in Rollup, Cost of Goods Sold Account,
and Standard Lot Size
Purchasing:
• Purchased, Purchasable, Use Approved Supplier, Allow Description Update, RFQ
Required, Outside Processing Item, Outside Processing Unit Type, Taxable, Tax Code,
Receipt Required (Three–Way Invoice Matching), Inspection Required (Four–Way
Invoice Matching), Default Buyer, Unit of Issue, Receipt Close Tolerance, Invoice Close
Tolerance, UN Number, Hazard Class, List Price, Market Price, Price Tolerance,
Rounding Factor, Encumbrance Account, Expense Account, and Asset Category
Receiving:
• Receipt Date Action, Receipt Days Early, Receipt Days Late, Overreceipt Quantity
Control Action, Overreceipt Quantity Control Tolerance, Allow Substitute Receipts,
Allow Unordered Receipts, Allow Express Transactions, Receipt Routing, and Enforce
Ship–To
Physical Attributes:
• Weight Unit of Measure, Unit Weight, Volume Unit of Measure, Unit Volume, Container,
Vehicle, Container Type, Internal Volume, Maximum Load Weight, Minimum Fill
Percentage, Dimension Unit of Measure, Dimension Length, Dimension Width,
m y
and OM Indivisible
d e
Dimension Height, Collateral Item, Event, Equipment, Electronic Format, Downloadable,
General Planning:
ca
Max Maximum Quantity, Minimum Order Quantity, Maximum Order Quantity, Order
e A
• Inventory Planning Method, Planner, Make or Buy, Min–Max Minimum Quantity, Min–
c l
Cost, Carrying Cost Percent, Source Type (Replenishment), Source Organization, Source
Subinventory, Safety Stock Method, Safety Stock Bucket Days, Safety Stock Percent,
r a
Fixed Order Quantity, Fixed Days Supply, and Fixed Lot Multiplier
MPS/MRP Planning:
O ly
• Planning Method, Forecast Control, Exception Set, Pegging, Planned Inventory Point,
l & On
Create Supply, Shrinkage Rate, Round Order Quantities, Acceptable Early Days,
Repetitive Planning, Overrun Percentage, Acceptable Rate Increase, Acceptable Rate
n a e
Decrease, Calculate ATP, Reduce MPS, Planning Time Fence, Planning Time Fence
t e r U s
Days, Demand Time Fence, Demand Time Fence Days, Release Time Fence, Release
Time Fence Days, Substitution Window Type, and Substitution Window Days
Lead Times:
I n
• Preprocessing, Processing, Postprocessing, Fixed, Variable, Cumulative Manufacturing,
l e
Cumulative Total, and Lead Time Lot Size
c
Work in Process:
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 25
• Build in WIP, Supply Type, Supply Subinventory, Supply Locator, Overcompletion
Tolerance Type, Overcompletion Tolerance Value, Scheduling Penalty Inventory Carry,
and Scheduling Penalty Operation Slack
Order Management:
• Customer Ordered, Customer Orders Enabled, Shippable, Internal Ordered, Internal
Orders Enabled, OE Transactable, Pick Components, Assemble to Order, ATP
Components, Ship Model Complete, Check ATP, ATP Rule, Picking Rule, Default
Shipping Organization, Default SO Source Type, Returnable, RMA Inspection Required,
Financing Allowed, Over Shipment Tolerance, Under Shipment Tolerance, Over Return
Tolerance, and Under Return Tolerance
Invoicing:
• Invoiceable Item, Invoice Enabled, Accounting Rule, Invoicing Rule, Tax Code, Sales
Account, and Payment Terms
Service:
• Contract Item Type, Contract Duration, Contract Duration Period, Service Duration,
Subscription Dependency Enabled, Service Importance Level, Billing Type, Service
Request Enabled, Provisionable, Serviceable Product, Service Billing Enabled, Defect
Tracking Enabled, Recovered Part Disposition, Installed Base Tracking, Asset Creation,
Starting Delay (Days), and Instance Class
Web Option:
• Web Status, Orderable On the Web, Back Orderable, and Minimum License Quantity
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 26
Status Attributes and Functionality
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 27
Status Attributes and Functionality
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 28
Item Status
m y
d e
ca
e A
Item Status
c l
When defining an item, you can use the item attribute Item Status to control status attribute
r a
values. You determine the list of values for the Item Status attribute by defining Item Status
Codes. An Item Status Code has a user–defined set of Yes/No values for the status attributes.
O ly
The values are applied to the status attributes when you choose an Item Status Code when
l & On
defining an item. For example, assume you define an Item Status named Prototype with all
status attributes set to Yes except for Customer Orders Enabled. Next, you define another Item
n a e
Status, Active, with all status attributes set to Yes. In the beginning of a product development
cycle, assign the status code Prototype to an item so that you cannot place the item on a sales
t e r U s
order. Later, assign the status code Active to allow all functions for the item.
You can assign one or more pending statuses for an item, to be implemented on future dates.
I n
These statuses become effective on their assigned effective dates. You can view the status
history of an item if needed.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 29
Item Attribute Relationships
m y
d e
ca
e A
Item Attribute Relationships
Required Attributes
c l
r a
• You must enter a value for the attribute based on the settings for other related attributes.
Interdependent Attributes
O ly
• You can only enter certain values depending on other attribute values.
Updateable Attributes
l & On
a e
• You can update values under certain conditions.
n
t e r
Control Level Dependencies
s
• You can update the control level of some attributes only under special conditions and with
U
n
certain consequences.
I
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 30
Status Attribute Interdependencies
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 31
Status Attribute Interdependencies
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 32
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 33
Organization Assignment and Organization Item
m y
d e
ca
e A
c l
Organization Assignment and Organization Item
You can enable your item in all child organizations under your master organization or you can
r a
choose to enable your item in specific child organizations. You can use the master item
window, in each organization, to enter or change organization-level attribute values for items
O ly
that are enabled in the organization. For example you can select Reorder Point planning for an
organization.
l & On
item in one child organization and select Min-Max planning for the same item in another child
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 34
Item Control Level
m y
d e
ca
e A
Item Control Level
c l
An attribute you maintain at the master level has identical values across all organizations that
use the item.
r a
An attribute you maintain at the organization level may have different values for each
organization that uses it. O ly
& On
Some attributes can be maintained at only the Master level or the Organizational Level.
l
n a e
• Unit of Measure must be entered at the Master level.
• If using multiple organizations, the Min-Max attribute should be maintained at the
organization level.
Master-Level Control
t e r U s
I n
• For example, suppose you want to ensure that items defined in two organizations are
e
transactable at the same time in both organizations. If you make the item not transactable
l
in one organization, you want the same item to become not transactable in the other
c
organization.
r a
Organization-Level Control
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 35
• Suppose only one of the two organizations in your Oracle Inventory implementation
performs manufacturing operations, while the other organization is strictly a distribution
warehouse. For a finished good item used in both organizations, you would want the
flexibility to select the Build in WIP status attribute check box in the manufacturing
organization, and clear the Build in WIP status attribute check box in the distribution
organization.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 36
Organization Assignments
m y
d e
ca
e A
Organization Assignments
c l
Use this window to enable items in organizations. It is not recommended to check Assign All.
a
There are many times items should not be assigned to an organization.
r
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 37
Creating and Changing Organization Items
m y
d e
ca
e A
Creating and Changing Organization Items
c l
Use this window to create and change item attributes in organizations.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 38
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 39
Searching Items
m y
d e
ca
e A
Searching Items
c l
You can specify as much or as little criteria as you want.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 40
Search Results
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 41
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 42
Viewing Item Information
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 43
Viewing Item Revisions
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 44
Viewing Item Attributes
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 45
Viewing Item Categories
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 46
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 47
Overview of Item Cataloging
m y
d e
ca
e A
Overview of Item Cataloging
c l
You can use item cataloging to add descriptive information to items and to partition your Item
r a
Master into groups of items that share common characteristics. You configure in advance what
is required to uniquely define an item in each group. When you define your items, you assign
them to an item catalog group.
O ly
l & On
To define your catalog, you set up as many distinct item catalog groups as you need to partition
your Item Master. Each group has unique characteristics, called descriptive elements, which
a e
completely describe items belonging to the group.
n
t e r s
When you assign an item to an item catalog group, you define values for the descriptive
elements that apply to your item. For example, an item catalog group called Computer could
U
I n
have a descriptive element called Processing Speed. Possible values for Processing Speed
might be 100MHZ, 133MHZ, and so on.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 48
Creating Item Catalog Groups
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 49
Defining Item Catalog Groups
m y
d e
ca
e A
Defining Item Catalog Groups
To define an item catalog group:
c l
r a
1. Navigate to the Item Catalog Groups window.
O ly
2. Enter a unique name for the group.
3. Enter a description. If you choose to build an item’s description from the catalog, the
& On
description is built beginning with the information entered here. You can choose to use the
l
n a e
Catalog Name instead of the Description as the first element in a concatenated item
catalog description. To do this change the INV:Use catalog name in the item description
U s
I n
To make an item catalog group inactive:
l e
1. Enter the date on which the catalog group becomes inactive. As of this date you can no
longer assign items to this group. You can use an inactive group in reports and searches.
c
r a
To define descriptive elements for an item catalog group:
1. Select an item catalog group and choose Details.
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 50
Defining Descriptive Elements
m y
d e
ca
e A
Defining Descriptive Elements
c l
You can define any number of descriptive elements for an item catalog group. You can also
r a
describe whether the descriptive element is required at item definition, and whether the
descriptive element value is included by default in the item catalog description.
Description Default O ly
l & On
Descriptive element values can be concatenated and used to create an item’s description. You
turn this feature off or on for each descriptive element in a catalog group. Turn description
a e
Default on for any element you want included in a concatenated description. You create a
n
t e r U s
concatenated description when you assign an item to an item catalog group.
To define descriptive elements for an item catalog group:
I n
1. Navigate to the Item Catalog Groups window.
2. Select an item catalog group and choose Details. The Item Catalog Group window
l e
appears.
c
3. Select the Descriptive Elements tabbed region.
r a
4. Enter a unique sequence number. When you assign an item to a group, the descriptive
Defining Items
Chapter 1 - Page 51
5. Enter the name of a new descriptive element. Examples: Color, height, texture.
6. Determine whether the descriptive element is required for this catalog group. When you
assign an item to a catalog group, you must enter a value for required descriptive elements
in order for the catalog to be considered complete. If an element is not required, entering a
value is optional.
7. Determine whether the descriptive element is automatically used to create the catalog
description (Description Default). If you choose to concatenate the value of the descriptive
element to create the catalog description, you can use this description to overwrite an
existing item description.
8. Save your work.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 52
Concatenated Item Descriptions
m y
d e
ca
e A
Concatenated Item Descriptions
c l
When you define descriptive elements for an item catalog group, you specify whether the value
r a
of a particular descriptive element can be concatenated and used as an item’s description.
When you assign an item to a catalog group, you choose descriptive elements that apply to the
O ly
item, and assign values to the descriptive elements. You can then create a concatenated item
l & On
description by choosing the Update Description button. If you choose Update Description,
Oracle Inventory concatenates the item catalog group information and overwrites the item
a e
description with this new information.
n
t e r U s
Concatenated Item Description Structure
Oracle Inventory builds a concatenated item description by combining segments of catalog
I n
information. The first segment is either the catalog group Description or the Catalog Name.
You can choose which to use by setting the INV:Use catalog name in the item description
l e
profile option.
c
Additional segments consist of the values for descriptive elements that have Description
r a
Default turned on.
The Item Catalog Flexfield separator is used as a delimiter between each segment of the
O combined description.
Defining Items
Chapter 1 - Page 53
When the description is displayed, the delimiters appear even if data is missing for some of the
descriptive elements.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 54
Defining Aliases
m y
d e
ca
e A
Defining Aliases
c l
You can specify any number of aliases for the items that belong to the catalog group. This is
r a
for information/reporting purposes only. You can print the list of aliases and use the list as
recommended item cross references, for example. You can choose any alias you have defined
O ly
for any item catalog group, or you can create new aliases.
l & On
To define an alias for items in a catalog group:
1. Navigate to the Item Catalog Groups window.
n a e
2. Select an item catalog group and choose Details. The Item Catalog Group window
appears.
t e r U s
3. Select the Aliases tabbed region.
I n
4. Enter a unique name.
c l e
5. Save your work.
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 55
Practice Overview: Creating Items
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 56
Practice - Creating Items
Overview
In this practice you will create items. In addition to creating the items, you will also review the
newly creating items. The items created in this practice will be used for the remaining practices
in this course.
Assumptions
• Use the Manufacturing and Distribution Manager responsibility to complete this
practice.
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Creating Items
Use the following table to create items. After you create the items, be sure to assign the items to
the M1-Seatlle Manufacturing organization. ## is your unique identifier.
m y
Item Number Description Template Type
d e
Copied Item
##1000 Pentium Computer Finished Good
c a
##1010 17” Monitor
e
Purchased Item
A
##1020
##1030
101 Keyboard
Mouse
c l ##1010
##1010
##1040
r a
CPU Chassis Subassembly
##2010
O ly
Motherboard ##1040
##2011
& On
New Motherboard
l
##1040
##2020
a e
Serial Board
n
##1010
##2030
##2040
t e r 1.6 GB Hard Drive
U s
3.5 Disk Drive
##1010
##1010
##3010
I n Blank Board ##1010
##3020
c
##3030l e 586 133mHz IC
Resistor
##1010
##1010
O ra ##3031
##3040
New Resistor
Integrated Circuit
##1010
##1010
Defining Items
Chapter 1 - Page 57
Searching Items
Using the Item Search window, perform a search for all your newly created items. When you
finish searching for your ## items, perform a search for all Pentium computers.
Reviewing Items
Using the Find Item Information window, review one or more of your items. Look at the
attributes for one of your ## items.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 58
Solution – Creating Items
Creating Items
1. Use the following table to create items. After you create the items, be sure to assign the
items to the M1-Seatlle Manufacturing organization. ## is your unique identifier.
m y
##2030
##2040
1.6 GB Hard Drive
3.5 Disk Drive
##1010
d
##1010 e
##3010 Blank Board
c a
##1010
##3020 586 133mHz IC
e A##1010
##3030
##3031
Resistor
New Resistor
c l ##1010
##1010
##3040
r a
Integrated Circuit ##1010
O ly
2.
l & On
Navigate to the Master Items window.
n a e
3.
•
t e r U s
(N) Inventory > Items > Master Items
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 59
m y
4. Apply a template or copied item. Enter a value for Template Type or Copied Item.
d e
• (M) Tools > Copy From
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r
5.
a Select Apply, and then Done.
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 60
m y
6. Save your item.
d e
7. Assign your item to the M1-Seattle Manufacturing organization.
ca
• (M) Tools > Organization Assignment
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 61
m y
8. Save your work
d e
9. Repeat these steps to create all the items in the table.
ca
Searching Items
e A
c l
10. Using the Item Search window, perform a search for all your newly created items. When
you finish searching for your ## items, perform a search for all Pentium computers.
r
11. Navigate to the Item Search window.
a
O ly
•
& On
(N) Inventory > Items > Item Search
l
a e
12. In the Item Mask field enter ##%. (## is your unique identifier)
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 62
m y
d e
ca
e A
13. Select Find.
c l
• (B) Find r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 63
m y
d e
ca
e
14. After reviewing the search results, close the Item Search window. A
c l
15. Search for all Pentium computers.
r a
O ly
16. In the Find Items window enter %entium% in the Description field.
l & On
• (B) Find
n a e
e r
18. Review the search results.
t U s
Reviewing Items
I n
l e
19. Using the Find Item Information window, review the attributes for one or more of your ##
c
items.
r a
20. Navigate to the Find Item Information window.
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 64
• (N) Inventory > Items > Item Information
m y
22. Select Attributes.
d e
• (B) Attributes
ca
23. If you receive an error, select OK.
e A
• (B) OK
c l
24. Review the attribute information.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 65
25. Close the Item Attributes window.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 66
Practice Overview: Defining and Assigning Item Statuses
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 67
Practice - Defining and Assigning Item Statuses
Overview
In this practice you will define a new item status code. In addition to creating the item status
code, you will create a new inventory item and assign the newly defined item status code to the
item.
Assumptions
• Use the Manufacturing and Distribution Manager responsibility to complete this
practice.
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Creating Item Status Codes
Define a Prototype status using your unique identifier ##. Use the following information to
complete the task.
− Status ##PROTO
m y
− Description
− BOM Allowed
## Prototype Status
Yes
d e
− Build in WIP No
ca
− Customer Orders Enabled
− Internal Orders Enabled
No
Yes
e A
− Invoice Enabled
− Purchasable
c l No
No
− Stockable
− Transactable r a Yes
O ly Yes
Defining Items
l & On
organization.
n a e
Define a new finished good item called ##_NP and assign it to the M1-Seattle Manufacturing
t e
Reviewing Item Information
r U s
I n
Review the status and attributes.
c l e
What is the status of your part? __________________________________________
Defining Items
Chapter 1 - Page 68
Build in WIP _____________________________________________________
Purchasable ______________________________________________________
Stockable ________________________________________________________
Transactable ______________________________________________________
In the Item Master window change your item’s status to ##PROTO and save your work. Query
the item again and note the values for the item attributes.
Is this consistent with the values for the prototype item status? __________________
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 69
Solution – Defining and Assigning Item Statuses
Creating Item Status Codes
1. Define a Prototype status using your unique identifier ##. Use the following information to
complete the task.
− Status ##PROTO
− Description ## Prototype Status
− BOM Allowed Yes
− Build in WIP No
− Customer Orders Enabled No
− Internal Orders Enabled Yes
− Invoice Enabled No
− Purchasable No
− Stockable Yes
− Transactable Yes
Defining Items
Chapter 1 - Page 70
4. Save your work.
Defining Items
5. Define a new finished good item called ##_NP and assign it to the M1-Seattle
Manufacturing organization.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 71
10. Save your work.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
15. Enter your item ##_NP and select Attributes.
•
n
(B) Attributes
I
c l e
16. Answer the following questions:
Defining Items
Chapter 1 - Page 72
BOM Allowed: Yes
Purchasable: Yes
Stockable: Yes
Transactable: Yes
19. In the Main tab of the Master Item window, change the Item Status to ##PROTO.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 73
20. Save your work.
21. Query item ##_NP again and note the values for the item attributes.
Which attributes changed? Build in WIP, Customer Orders Enabled, Invoice Enabled, and
Purchasable
Is this consistent with the values for the prototype item status? Yes
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 74
Summary
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Defining Items
Chapter 1 - Page 75
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Setting Up Bills of Material
and Routings
Chapter 2
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Using the Workday Calendar
c l
A workday calendar defines the valid working days for a manufacturing organization and
r a
consists of repeating pattern of days on and days off and exceptions to that pattern. This
enables you to, for example, designate a normal workday as a scheduled downtime day, or
designate a holiday as a workday.
O ly
l & On
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
a e
and end dates, and the weekend schedule for each calendar.
n
Creating Workday Calendars
t e r U s
A workday calendar consists of a start date, and end date, and on and off days that follow one
I n
or more defined workday patterns. A workday calendar can also include shift information and
exception dates, such as holidays or scheduled down time.
l e
Use a workday calendar for forecasting and planning material requirements, use shift
c
information for job scheduling, and capacity analysis.
r a
Workday exceptions identify deviations to the workday calendar. Shift exceptions identify
deviations for a shift. Shift exceptions take precedence over workday exceptions. This is only
O relevant if a workday exception and a shift exception overlap.
e A
pattern, assigned shifts, assigned workday and shift exceptions, and reviewed your
c l
work, you must build the calendar and assign it to an organization.
6. Save your work.
Copying Calendars or Shifts r a
O ly
You can copy the entire calendar, including workday patterns, exceptions, and all or none of its
a e
Exactly what is copied depends upon how you navigate to the Copy window:
n
t e r U s
• From the Workday Calendar, Calendar Dates, and Workday Patterns windows, all
workday patterns, all exceptions, and selected shift information are copied.
I n
• From the Shifts, Shift Times, Shift Dates, or Shift Workday Patterns windows, the shift
workday patterns, shift exceptions, and all shift times for the specified shift are copied.
l e
If you copy calendar information to an existing calendar, all new information is appended to
c
the existing calendar; existing information, in other words, is retained.
r a
1. Navigate to the Copy window. Do this by choosing Copy from the Tools menu.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Repeating Workday Patterns
c l
You can also define a series of repeating workday patterns for a given calendar. For example,
r a
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
O ly
four days off. When you build the calendar, Oracle Bills of Material automatically determines
l & On
the valid workdays for you, based on the patterns you specify.
You can also specify repeating workday patterns for shifts.
Creating Workday Patterns
n a e
t e r U s
1. Navigate to the Workday Patterns or Shift Workday Patterns window. You can do this by
choosing the Workday Pattern button from either the Workday Calendar or Shifts window.
built. I n
2. Enter a sequence number in which the workday patterns are applied when the calendar is
l e
3. Enter the number for consecutive workdays on and off. For example, if you want Monday
c
through Friday on and Saturday and Sunday off, enter 5 for Days On and 2 for Days Off.
r a
4. Enter a description for the sequence. Repeat the previous three steps for each workday
O pattern to create. All defined sequences are repeated for the duration of the workday
calendar. If there are two sequences, sequence 1 will be in effect first, then sequence 2,
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Workday Exceptions
c l
There are three ways to apply exceptions to the workday calendar:
• selecting individual exception days
r a
O ly
• loading them from an exception template, another calendar, and another calendar shift
• copying a set of exceptions from another calendar.
l & On
An exception template enables you to create groups of exception dates and apply them to
n a e
different calendars. You can define multiple workday exception templates that define different
holidays and scheduled down times for different organizations. Multiple exception templates
t e r U s
can be applied to the same calendar. As each template is applied, new exception dates are
added to the exception list for that calendar.
I n
Conflicts on a particular date between one template and another are resolved as follows:
c l e
• if the exception date already exists in the target calendar, it is not copied
• if the exception on day falls on a workday, the exception is copied but is redundant and
e A
template, a calendar, or a shift.
c l
2. Choose the Load button and select whether existing exceptions should be applied from a
r a
- If you select Template, enter a template name.
O ly
- If you select Calendar, enter a calendar name.
- If you select Shift, enter the calendar name that the shift belongs to and the shift
number.
l & On
a e
3. When finished, choose OK to save your work.
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Shifts
c l
For a given workday calendar, you can specify any number of shifts. Each shift can have a
r 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.
O ly
l & On
Shifts inherit workday exceptions and workday patterns from the base calendar. Shift
exceptions can either add to or override those of the base calendar.
a e
If an exception on the base calendar changes, those shifts that do not have an overriding
n
t e r s
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
U
I n
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
l e
selecting individual exception days, by defining exception templates, or by copying a set of
c
exceptions from another shift.
r a
Organizations
For each organization, you specify the calendar to use. All scheduling functions use the
O calendar you specify. Detailed scheduling uses specific resource availability information by
e
created. You can then update that workday pattern. A
5. Save your work.
c l
Selecting Workday or Shift Exceptions
r a
1. Navigate to the Calendar Dates window or Shift Calendar Dates window. Do this by
O ly
choosing the Dates button from the Workday Calendar window.
l & On
2. Select individual days of the month to toggle them on or off. Days you change become
either workday or shift exceptions, depending on how you entered the window.
3. Save your work.
n a e
t e r U s
Loading Existing Workday or Shift Exceptions
1. Navigate to the Exceptions window. Do this by choosing the Exception List button from
I n
the Calendar Dates window.
l e
2. Choose the Load button and select whether existing exceptions should be applied from a
template, a calendar, or a shift.
c
r a - If you select Template, enter a template name.
- If you select Calendar, enter a calendar name.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Defining Lookups
To define Bonus Codes
c l
r a
1. Navigate to the Shop Floor Manager (N) Routings > Bonus Codes window
O ly
2. Enter code, Meaning and Description of code in the Manufacturing > Bonus Codes
Lookups window that appears. Enter numeric value in the Code field.
To define Scrap Codes
l & On
n a e
1. Navigate to the Shop Floor Manager (N) Routings > Scrap Codes window
2. Enter code, Meaning and Description of code in the Manufacturing > Scrap Codes Lookups
e r s
window that appears. Enter numeric value in the Code field.
t
To define Resource Down Codes
U
I n
1. Navigate to the Shop Floor Manager (N) Routings > Resource Down Codes window
l e
2. Enter code, Meaning and Description of code in the Manufacturing > Resource Down
c
Codes Lookups window that appears. Enter numeric value in the Code field.
r a
To define Resource Capacity Change Reasons
1. Navigate to The Resource Capacity Change Reasons window to define reason codes.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Assumptions
• Use the Manufacturing and Distribution Manager responsibility to complete this
practice.
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
m y
Defining Workday Exception Sets
d e
Define a workday exception set named ##-EXCEPT. Enter three exception dates in 2006.
ca
Defining Workday Calendars
e A
c l
Define a calendar workday pattern with the information below. Load the workday exception set
you created earlier and then build your calendar.
− Name
− Description r a ##-CAL
I n
Reviewing Calendar Information
l e
Review your new calendar in the Inventory responsibility. Verify the exception dates appear.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
1. Define a workday exception set named ##-EXCEPT. Enter three exception dates in 2006.
3. Enter ##-EXCEPT in the Template field, a description in the Description field, and three
exception dates in the Date fields
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
4. Save your work.
I n
5.
c e
Defining Workday Calendars
l
Define a calendar workday pattern with the information below. Load the workday exception
O − Name
− Description
##-CAL
Calendar for ##
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
8. Select Workday Pattern.
•
t
(B) Workday Patterne r U s
9. I n
Enter the following information:
c l
− Seq
e
− Days On
1
5
r a − Days Off 2
e A
• (B) Exception List
c l
14. Select Load.
r a
• (B) Load
O ly
l & On
15. In the Template field, select the exception set you created earlier.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
• (B) OK
17. You should see your calendar with the exceptions on it.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
20. A concurrent process is run to build the calendar/exceptions. Note the concurrent process
number ____________________ and select OK.
22. Review your new calendar in the Inventory responsibility. Verify the exception dates
appear.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Define the System Items Flexfield
c l
You must design and configure your System Items Flexfield before you can start defining
r a
items. You must indicate how many separate segments your flexfield has, how many characters
each segment has, and whether you want to validate the values that you assign to the segments.
O ly
Once you define the structure of your flexfield and any applicable value sets, you must freeze
l & On
and compile your flexfield definition.
All Oracle Applications products that reference items share the System Items Flexfield and
a e
support multiple segment implementations. Therefore, if you have already configured this
n
t e r
flexfield while setting up another product, you do not need to perform this step.
Define the Item Categories Flexfield
U s
I n
You must design and configure your Item Categories Flexfield before you can start defining
items since all items must be assigned to categories. You must indicate how many separate
l e
segments your flexfield has, how many characters each segment has, and whether you want to
c
validate the values that you assign to the segments. Once you define the structure of your
r a
flexfield and any applicable value sets, you must freeze and compile your flexfield definition.
Compiling the flexfield definition enables the Item Categories Flexfield pop–up window.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill of Material Parameters
c l
Use bill of material parameters to define modes of operation and default values for an
configuration numbering. r a
organization that affect functions such as bill definition, bill deletion, and assemble-to-order
O ly
Define bill of material parameters for each organization in which you use bills or routings. Bill
l & On
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.
n a e
t e r U s
To define bill of material parameters:
1. Navigate to the Parameters window (N) Setup > Parameters.
I n
2. Enter the maximum bill levels to explode. The maximum is 60. For configurations only -
All fields in the Configuration Options box apply only to configured items.
l e
3. Enter an inactive status.
c
4. Enter the numbering segment to use when creating configuration item numbers.
r a5. Select an automatic or user defined numbering method. A unique configuration item
ca
assembly. Setting this parameter also implies department inheritance for resources;
c l
organization level and it then applies to all phantoms within a single inventory
organization. There are its two values. If you select Yes, phantom routing
r a
components and resources and overheads are included in the cost of the higher level
assembly. Routing resource costs are also included in capacity planning. If you select
O ly
No (this is the default), this value specifies that only components are included in the
l & On
higher assembly’s cost, not resources and overheads.
- Inherit Phantom Op Seq: Set this parameter to specify whether phantom subassembly
a e
components inherit the operation sequence number of their parent or higher level
n
r s
assembly, or maintain their own operation sequence number. This parameter is set at
e
the inventory organization level, and applies to all phantoms within a single inventory
t U
organization. The parameter has two values. If you select Yes (this is the default), the
I n
phantom subassembly components inherit the operation sequence number of their
c l e
parent or higher level assemblies. If you select No, phantom subassembly
components maintain their own operation sequence numbers.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Creating Alternates
c l
An alternate bill describes an alternate list of component items that produce an assembly. An
O ly
1. Navigate to the Alternates window (N) Setup > Alternates.
& On
2. Enter an alphanumeric string to describe a unique alternate.
l
n a e
3. Enter a date that the alternate is inactive on. As of the inactive date, you can no longer
assign the alternate to a bill of material or routing.
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Creating Custom Deletion Constraints
c l
Use custom deletion constraints to enforce specific business rules. Custom deletion constraints
constraint. r a
prevent the deletion of bills or routings if your data meets the conditions set forth in the
t e r U s
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.
I n
l e
5. Enter the SQL Select Statement that the delete concurrent program is to execute. You
cannot update SQL statements for predefined deletion constraints.
c
r a
6. Indicate whether to delete if there are rows found or no rows found by the SQL Select
Statement.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Defining Department Classes
c l
Use department classes to group departments for shop floor scheduling and control, and to
reporting purposes. r a
identify manufacturing cells and flexible machine centers. Department classes are used for
t e r U s
3. Choose the Departments button to display the departments assigned to this department
class and the dates when these departments can no longer be assigned to routing
operations.
I n
Assign departments to classes when you define departments.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Defining Departments
c l
A department is an area within your organization that consists of one or more people,
r a
machines, or suppliers, where you want to collect costs, 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.
O ly
l & On
When you define a department, you specify any department overhead costs and the resources
that are available. You can enter multiple resources for each department. For each resource,
a e
you can specify the shifts that the resource is available. For each resource shift, you can also
n
workdays.
t e r
specify capacity modifications that change the available hours per day, units per day, or
U s
To define a department:
I n
1. Navigate to the Departments window (N) Routings > Departments.
l e
2. Enter a name for the department unique for the organization.
c
3. Optionally, enter a department class.
r a
4. Enter a location for the department.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Defining Locations
c l
Use the Location window to enter location information. You assign locations to departments
a
that receive deliveries of outside processing items (N) Setup > Locations.
r
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Defining Resources
c l
Use resources to define the time an assembly spends at an operation and the cost you incur at
r a
the operation. A resource is anything you require to perform, schedule, or cost, including but
not limited to: employees, machines, outside processing services, and physical space. A
O ly
resource and usage rate for all scheduled activities is required in a routing. Scheduled resources
l & On
can include queue, setup, run, and move time.
When you define your departments, you assign the resources available in each department and
a e
the shifts that each resource is available. For each operation you define, you specify a
n
t e r
department and list of resources and usages. An operation can use any resource that is available
s
in the department, but you do not need to use all resources assigned to the department.
U
I n
If you have Oracle Manufacturing installed, you can use Resource batching. Resource batching
enables you to use resources across multiple jobs. By using a single resource to process
l e
multiple jobs simultaneously, you can prevent a resource from being underutilized. Work
scheduled using resource batching is characterized by equivalent work performed with the
c
a
same manufacturing processes.
r
O
Copyright © Oracle, 2007. All rights reserved.
e
8. Select an expenditure type for this resource. If the Project Cost Collection Enabled A
c l
parameter is set in the Organization Parameters window, you must associate the resource
with an expenditure type. You can only select expenditure types that belong to the Work
r a
in Process expenditure type class. Expenditure types are defined in Oracle Projects.
O ly
9. Optionally, enter the supply subinventory if the resource is a machine. The system uses
the supply subinventory specified for the resource if the routing does not specify a supply
subinventory.
l & On
n a e
10. Optionally, enter the supply locator if the resource is a machine. The system uses the
supply locator specified for the resource if the routing does not specify a supply locator.
e r s
11. Indicate whether to enable the outside processing resource, and if so, enter its item
t U
number. If you specify PO Move or PO Receipt, Oracle Purchasing uses this item when it
I n
creates requisitions for your outside processing resource.
12. Enable the Costed check box to collect and assign costs to this resource, and if so,
l e
optionally enter an activity for the resource. You cannot view costing information if the
c
Privilege To View Cost Information function is excluded from the responsibility. You
r a cannot update costing information if, in addition, the Privilege To Maintain Cost
O Information function is excluded. You can use activities to group resource charges for cost
reporting purposes.
l
20. Enter the time value for the batching process in the Batching window field.
c
r a
21. Select the time unit of measure available in the Batching Window UOM field.
To define cost type and resource rate associations:
O ly
1. Navigate to the Resource Costs window. Do this by choosing the Rates button from the
l & On
Resources window. You cannot view costing information if the Privilege To View Cost
Information function is excluded. You cannot update costing information if, in addition,
a e
the Privilege To Maintain Cost Information function is excluded.
n
t e r
2. Enter or select a cost type to associate with each resource overhead rate.
s
3. Enter the Resource Unit Cost, that is, the resource’s current standard cost per UOM.
U
I n
To associate overheads with resources:
1. Navigate to the Resource Overhead Associations window. Do this by choosing the
l e
Overheads button from the Resources window.
c
2. Enter or select the cost type for the resource. The Allow Updates check box indicates
O 3. Enter or select the overhead to associate with the resource. For example, you could assign
resource cost as dollars per hour. If you enter a new resource, you can directly enter a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Assigning Resources to a Department
To assign resources to a department:
c l
r a
1. Navigate 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. O ly
& On
2. Enter the resource to assign to the current department.
l
n a e
3. Optionally, for owned resources, indicate whether the resource is available 24 hours a day.
You cannot assign shifts to a resource that is available 24 hours a day.
t
with other departments.
e r U s
4. For owned resources, indicate whether this department can share the resource and capacity
I n
5. For borrowed resources, enter the owning department.
e
6. Enter the number of capacity units (resource units) available for this department, for
l
example, the number of machines for a machine resource. Each resource can be assigned
c
to any number of departments; multiple resources can be assigned to each department.
r a
7. Optionally, enter a resource group for the resource in this department.
O
Copyright © Oracle, 2007. All rights reserved.
e A
then choosing Resources.
c l
1. Find the resources assigned to a department by navigating to the Departments window,
r a
2. Select a resource, then choose Instances. The Instances window contains different fields
depending upon whether you select an equipment or person resource.
If you select an equipment resource: O ly
& On
3. Enter the equipment item that acts as the resource.
l
n a e
4. Enter the serial number of the speci fic resource instance. Valid serial numbers for the
equipment item appear in the list of values.
t e r
If you select a person resource:
U s
5. Enter the employee number of the person that acts as the resource.
I n
6. Save your work. The number of resource instances must match the number of units speci
c l e
fied in the Resources window.
To assign shift information for the resource:
r a1. Navigate to the Shifts window. Do this by choosing the Shifts button from the Resources
window.
O
Copyright © Oracle, 2007. All rights reserved.
e A
change.
c l
- Source Tab: This tab provides detailed information (the downtime source,
r a
organization, work order, and operation) about resource downtime due to scheduled
maintenance at the resource instance level.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Assigning Shifts to Resources
c l
Use the Shifts window to specify resource shifts.
r a
1. Navigate to the Shifts window. Do this by choosing the Shifts button from the Resources
window (N) Routings > Departments (B) Resources (B) Shifts.
O ly
2. Enter a shift number to assign to the resource. The shifts available to assign to the resource
& On
are those assigned to the workday calendar assigned to the organization.
l
a e
3. Choose the Capacity Changes button to define capacity changes for a shift.
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Capacity Changes
c l
A capacity change is a temporary change to the available capacity of a resource. For example,
r a
work on a specific Saturday. You identify a capacity modification for a resource within a shift
for a resource. When you plan capacity or detail schedule a resource that has capacity
O ly
modifications, the planning and scheduling processes might schedule work on a different day
l & On
than they would have scheduled the same work if there were no capacity change.
A simulation set is the label for a group of capacity changes needed for a specific purpose. For
a e
example, a vacation schedule or an end-of-quarter overtime schedule. You can simulate
n
t e r
capacity changes by performing a capacity plan using a simulation set.
U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Defining Capacity Changes
c l
Use the Capacity Changes window to specify capacity changes.
r a
Capacity modifications can add or delete a day, or add or reduce capacity for a shift.
O ly
1. Navigate to the Capacity Changes window. Do this by choosing the Capacity Changes
button from the Shifts window.
& On
2. Enter or select a simulation set for the capacity change. Use simulation sets for capacity
l
n a e
requirements planning in Oracle Capacity.
3. Select the action to take for the department resource:
e r s
- Add: Adds a workday and capacity changes.
t U
- Delete: Deletes a workday for this department resource.
I n
- Add or Reduce Capacity: Add or reduce capacity for a resource shift. The capacity
c l e
change can fall outside a shift time, so you can add time to a shift. To reduce
capacity, enter negative numbers.
r a
4. Enter the number of resource units to increase or decrease capacity (if applicable). Make
sure to use a negative number if you are reducing capacity.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill of Material Profiles
BOM: Automatic Reservations
c l
r a
• Indicates whether the system will attempt to automatically reserve existing on hand
inventory after matching a configuration. During Autocreate Configuration, if a match has
O ly
been found and this profile is set to Yes, CTO will attempt to reserve on hand inventory
l & On
for any order line having a schedule date within the OM: Reservation Time Fence. If
progressing the order via the workflow, a message will display with details of the match
a e
and reservation performed. If you are using the batch program, the log file provides details
n
t e r
of the match and reservations performed.
s
BOM: Check for Duplicate Configuration
U
item.
I n
• Indicates whether to search for an existing duplicate configuration rather than create a new
l e
BOM: Component Item Sequence Increment
c
• Indicates the value by which to increment the sequence of the component item on the bill.
r a
BOM: Configuration Item Delimiter
O
Copyright © Oracle, 2007. All rights reserved.
r a
• Indicates whether a holder of this responsibility can define and update bills of material for
standard items.
O ly
BOM: Update Resource UOM
l & On
• Indicates whether you can update the resource unit of measure.
BOM: Week or Period Start Day
n a e
t e r U s
• Indicates whether the workday calendar starts on a weekly or period basis. This profile
option works in conjunction with the Workday Calendar.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Assumptions
• Use the Manufacturing and Distribution Manager responsibility to complete this
practice.
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Defining Department Class Codes
Defining Resources
m y
Define resources using the information below:
d e
Resource Description
c a
Type
##Inserter Auto Inserter
e A
Machine
##Assblr
c l
Labor Grade 1 Person
##Tester
r a Tester Person
O ly
& On
For each resource use the additional information below:
l
− UOM
− Charge Type
n a eHR
WIP Move
− Default Basis
− Costed
t e r U s
Item
Yes
I
− Standard Rate
n
− Absorption Account
Yes
Use any account number
c l e
− Variance Account
− Overheads
Use any account number
Blank
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
4. Save your work.
t e r U s
Defining Resources
I n
5.
e
Navigate to the Resources window.
c l
r a • (N) Bills of Material > Routings > Resources
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
e A
Defining Departments
c l
8. Navigate to the Departments window.
r a
•
O ly
(N) Bills of Material > Routings > Departments
9.
l & On
Define departments using the table information below:
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
11. Select Resources.
t e r U s
• (B) Resources
I n
c l e
12. Enter Resource, Available 24 Hours, Share, and Units.
r a
O
Copyright © Oracle, 2007. All rights reserved.
ca
• (B) Shifts
e A
14. Enter the shift information.
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Overview of Bills of Material
c l
Oracle Manufacturing and Oracle Order Management use bills of material to store lists of
r a
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.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Specify Components of BOM
c l
Use bills of material to specify the component items that you use to:
r a
• Manufacture assemblies and subassemblies (STD)
• Configure sales orders (Model)
O ly
• Explode aggregate forecasts (Planning)
• Calculate standard cost (STD)
l & On
a e
Engineering and Manufacturing Bills of Material
n
e r
Engineering bills of material are bills of material that your engineering function creates and are
s
not ready for production. Manufacturing bills of material are bills of material that you use in
t U
production. You create engineering bills of material in Engineering and you create
I n
manufacturing bills of material in Inventory. They differ only in the following ways:
c l e
• Engineering bills of material have the check box for the bill of material attribute
Engineering preselected.
r a
• Manufacturing bills of material have not preselected the check box for the item attribute
Engineering.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Types of Bills of Material
Standard Bill of Material
c l
r a
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
O ly
process, material planning, and other Oracle Manufacturing functions. Examples include bills
l & On
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
a e
that comprise a buildable, sellable product. Configuration items and bills are automatically
n
t e r s
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.
U
Model Bill of Material
I n
A model bill of material defines the list of options and option classes you can choose in Oracle
l e
Order Management to order a configuration. A model bill also specifies mandatory
c
components or included items that are required for each configuration of that model. You do
r a
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.
O Option Class Bill of Material
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Connecting Multiple Bills of Material
The bills of material above shows:
c l
r a
• A planning bill of material for Italian foods containing items pizza and calzone as
components
O ly
• Two model bills of material for pizza and calzone (Pizza contains the option class
components sauce and toppings.)
l & On
n a e
• Two option class bills of material for sauce and toppings (Sauce contains standard
components tomato sauce and pesto sauce.)
t e r U s
• Two standard bills of material for tomato sauce and pesto sauce (Tomato sauce contains
standard components tomato and oil.)
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Phantoms
c l
A phantom assembly is a non-stocked assembly that lets you group together material needed to
r a
produce a subassembly. When you create a bill of material for a parent item, you can specify
whether a component is a phantom. One bill of material can represent a phantom subassembly
O ly
for one parent item, and a stocked subassembly for another parent item.
l & On
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
a e
assemblies the same way as other assemblies. Work in Process ignores phantom assembly
n
t e r
routings when you define a job or repetitive schedule.
s
You can compute manufacturing and cumulative lead times for phantom assemblies that have
U
I n
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.
l e
In general, phantom assemblies behave like normal assemblies when they represent a top level
c
assembly, such as when you master schedule them or manufacture them using a discrete job.
r a
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
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Single Organization Bills of Material
c l
You create items in the master organization and assign them to the manufacturing and
r a
distribution organizations in which you use them.
However, you create bills of material in each organization that uses them.
O ly
Bills of material are always and only single organization entities. You can share the bill of
& On
material or copy it across organizations.
l
You could
n a e
• Create a bill of material for item A in organization 1 with components item B and item C.
e r s
• Create a bill of material for item A in organization 2 with components item B and item D.
t U
Create bills of material in the organization that uses them for manufacturing and use the copy
I n
bill of material or common bill of material to create them in other organizations that need them.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Oracle Inventory Integration
c l
You can use items that are defined using Oracle Inventory as both assemblies and components
of bills of material.
Oracle Engineering Integration r a
O ly
You can use items that are defined using Oracle Engineering as both assemblies and
& On
components of engineering bills of material.
l
Oracle Work In Process Integration
n a e
When you create discrete jobs and repetitive schedules, Oracle Work In Process bases the pick
t
Oracle Purchasing Integration e r U s
list on the bill of material of the assembly.
I n
You can purchase engineering items.
c l e
Oracle Master Scheduling/MRP and Oracle Supply Chain Planning Integration
The requirements explosion passes demand from bill of material assemblies to bill of material
r a
components.
Oracle Order Management Integration
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Creating Standard Bills of Material
c l
Standard bills are bills of material for manufactured products, kits, subassemblies, phantoms,
or purchased assemblies.
r a
You can order standard items on customer orders and build standard items on discrete jobs and
repetitive schedules. O ly
l & On
• Select Customer Ordered, Customer Orders Enabled, Internal Ordered, Internal Orders
Enabled, and Build WIP in item attributes.
n a e
A kit is a standard item that you typically do not build. You pick and ship the components
t e r
when your customer orders the item.
U s
• Select item attributes Customer Ordered, Customer Orders Enabled, Internal Ordered, and
I n
Internal Orders. Clear Build in WIP item attribute.
If the assembly BOM Item Type item attribute value is Standard, you can use those items with
l e
BOM Item Type item attribute value of Standard as components.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Components
c l
Bills of Material restricts the types of items you can assign as components based on the type of
bill you are defining.
r a
The table above lists valid components for each parent item type.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Creating a Bill of Material
c l
A bill of material contains information on the parent item, components, attachments, and
O ly
You can create an engineering, manufacturing, or asset (maintenance) bill, copy an existing
l & On
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.
n a e
t e r U s
Entering Assembly Bill of Material Information
1. Enter the parent item number (N) Bills > Bills. The item must have its BOM Allowed item
attribute selected.
I n
2. If you are creating an alternate bill of material, enter the alternate name. You must first
l e
enter alternate names in the Alternates window. If you are creating the primary bill of
c
material, leave this field blank.
r a
3. For model and option class bills of material choose Elements and assign item catalog
descriptive elements for the assembly.
OEntering Component Bill of Material Information: Main
represent the percentage of components that will survive the build process.
e A
Material Planning to overplan the component to account for expected loss. The number should
c l
Include in Cost Rollup: Use for standard bills of material. Select the check box to include the
material cost of this component in the standard cost of the assembly.
r a
Entering Component Bill of Material Information: Material Control
O ly
Use the following choices with standard BOM when you want to have WIP lower the
inventory balance of a discrete job and repetitive schedule.
Supply Type:
l & On
a e
• Phantom - Use Phantom to instruct Oracle applications to substitute the components of
n
t e r
this item, for the item when working with this item.
s
• Push - Use when the component should be charged at the beginning of the assembly or
U
I n
operation. This will lower your inventory at the same time. A component that must be
explicitly issued (pushed) from inventory to the discrete job (or repetitive schedule).
l e
• Operation Pull - Use if you want to decrease component inventory automatically when
c
you complete the routing step in which you use the component. You must have indicated
r a
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
O ly
the number of option items you can or must choose to order the components of the option class
bill.
l & On
Basis Field: If the component is an option class item, you must indicate whether you want to
a e
override the default quantity for the option class when a sales order is entered (the default).
n
e r
Option class quantities affect the mandatory standard components assigned to the option class.
s
If you select None for the Basis field, Oracle Order Management can override the default
t U
quantity for the option class. Order Management defaults the total quantity to release as the
I n
component quantity multiplied by the option class extended quantity. If you select Option class
for the Basis field, Order Management cannot override the default quantity for the option class.
l e
Order Management calculates the total quantity to release as the component quantity multiplied
c
by the option class extended quantity.
r a
Entering Component Bill of Material Information: Shipping
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill Details
c l
Use the Bill Detail window to enter a description of the bill of material or view a specific
a
common bill of material (N) Bills > Bills (B) Bill Details.
r
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Assigning Descriptive Elements
c l
For each model and option class bills only, you can specify a list of item catalog descriptive
r a
elements. Values are assigned to catalog descriptive elements when new configuration item are
created. The descriptive element value of the chosen option is assigned for each descriptive
element.
O ly
To assign descriptive elements:
l & On
For model bills, you must assign the item to a catalog group.
n a e
1. Navigate to the Descriptive Elements window. Do this by choosing Elements from the
t e r U s
Bills menu option in the Bills of Material window.
2. Enter a descriptive element to assign automatically based on the option chosen in the
I n
current bill. For model bills, you can only specify a descriptive element name within the
model item catalog group. For option class bills, you can specify a descriptive element
l e
name from any catalog group. When you order a configuration, Bills of Material
c
automatically creates and assigns the configuration item to the model’s item catalog
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Using Reference Designators
c l
Reference designators are sequenced comments and instructions that pertain to a component.
r a
For example, you may have drawings that clarify the assembly process for certain components,
or further instructions for the use of a large quantity of the same component. You can specify
O ly
whether to assign one reference designator for every usage of the component or assign any
l & On
number of reference designators to the component.
Planning bills and model, option class, and planning components cannot have reference
designators.
n a e
t e r s
Reference designators are sorted in alphanumeric order on inquiries and reports. You can also
specify a comment for each reference designator.
U
I n
Entering Component Bill of Material Information: Reference Designators
Qty Related: Select this check box to indicate that you can create only as many reference
l e
designators as the usage of the component in the assembly.
c
Reference Designator: Enter the reference designators or choose Add Range to create a range
r a
of reference designators automatically.
m y
- To number reference designators, use the Starting Value field to define the beginning
value for a range of reference designators. Then either enter the number of values to
add or delete, or define the ending value in the Ending field.
4. Save your work.
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
Entering Component Bill of Material Information: Substitute Components
You can assign any number of substitute items to each bill component and you can assign the
r a
same substitute item to more than one component. The substitute item quantity is the quantity
needed to replace the full component quantity. The quantity can differ from the component
usage quantity.
O ly
MRP Detail Report.
l & On
Oracle Master Scheduling/MRP reports these substitutes on some planning reports, such as the
a e
Oracle Work in Process does not consider substitute items in its pick lists.
n
components.
t e r U s
Planning bills and model, option class, and planning components cannot have substitute
I n
APS will consider substitute components when attempting to plan around constraints.
Substitute Component: Enter the item numbers of items that can be substituted for this
component.
c l e
Quantity: Enter the usage quantity of items that can be substituted for this component.
r a
To assign substitute components:
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
To capture inverse usage
c l
1. Navigate to the Bills of Material window.
r a
2. Enter the item number in the Item field.
O ly
3. Enter the component name in the Component field.
4. Enter the inverse value of the component in the Inverse Usage field.
l & On
After you enter the inverse percentage, the component quantity that you need is displayed
n a e
accurately in the Quantity field. The inverse usage value will also be displayed on the Bill
of Material or in the Bills of Material reports.
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Primary and Alternate Bills of Material
c l
A primary bill is a list of the components you most frequently use to build a product. An
r a
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.
O ly
You must define a primary bill before you define an alternate. A primary bill can have many
l & On
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
a e
Management uses the primary bill for model and option class products to list available options.
n
t e r U s
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
I n
use engineering change orders to control changes to primary and alternate bills of material.
Use alternate bills to account for manufacturing variations that produce the same assembly, by
l e
specifying the parent item number and an alternate name when you create a bill. You cannot
c
enter new revisions for alternate bills of material.
r a
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
O assembly.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Alternates
c l
Use this window to create codes for alternate bills of material and for alternate routings.
r a
An alternate bill describes an alternate list of component items that produce an assembly.
O ly
You can use an alternate code for as many item numbers as you want. You can use the same
alternate code for both a bill of material and a routing for the same assembly.
Create or Updating Alternates
l & On
n a e
1. Navigate to the Alternates window (N) Setup > Alternates.
2. Enter an alphanumeric string to describe a unique alternate.
e r s
3. Enter a date that the alternate is inactive on. As of the inactive date, you can no longer
t U
assign the alternate to a bill of material or routing.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Model/Unit Effectivity Overview
c l
Model/Unit Effectivity is used in high engineering manufacturing environments such as
r a
aerospace and defense industries. Unit Effectivity is generally used for high dollar or critical
assemblies. You would have unit effectivity at top levels of the BOM and date effectivity at
lower levels of the BOM.
O ly
l & On
This gives your business an alternative to date effectivity. You can define, plan, and produce
unit effective BOMs and implement unit-effective ECOs. In addition to date effectivity, you
a e
can now define component effectivity for a range of unit numbers. During planning and
n
e r
production, the system explodes the unit-effective BOMs based on the unit number in the
s
demand. The system also takes unit-effective ECOs into account during these processes. For
t U
example, you can use all available components before implementing the ECO.
I n
Model/Unit Effectivity is only available when Oracle Project Manufacturing is installed.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Model/Unit Effectivity Rules
c l
You can control the effectivity of changes to bills of material and routings with model/unit
r a
number effectivity. When you specify a model/unit number as the effectivity, you can enter a
particular change for a specific deliverable end item. The change can be effective for that item
O ly
and all subsequently produced items, for only one model/unit number of the product family, or
l & On
for a contiguous block of model/unit numbers. This technique does not use date to control
effectivity and therefore provides a convenient way to specify engineering changes for
e r s
Model/unit effectivity provides many versions of the same end item part number. A model/unit
t U
number consists of the alphanumeric prefix for the model/unit number of the end item followed
I n
by the specific item number.
c l e
Model/Unit Effectivity is not available unless Oracle Project Manufacturing is also installed.
All component items, including date effective component, within the bill of a model/unit
r a
effective item should be specified with valid model/unit numbers. You can define components
of a model/unit effective item as effective for a single model/unit number or effective for a
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Model/Unit Effectivity Setup
c l
This slide shows the steps needed to set up model/unit effectivity and the responsibilities for
the windows that you will use.
r a
The item needs to be defined Serial Controlled on the Inventory page.
O ly
The item effectivity control needs to be defined Model/Unit Number on the BOM page.
& On
Implementing Considerations for Model/Unit Effectivity
l
n a e
You should ask the following questions to decide whether to implement model/unit effectivity.
• Does your business need to track your production by unit or date effectivity?
e r s
• Does your business need to plan, procure, or store by unit number?
t U
I n
When you plan by unit number, you are restricted to the master demand schedule MDS and the
MDS creates demand for the material requirement plan (MRP). You can manually change the
c l e
MDS if necessary. Forecasts are not permitted for a model/unit effectivity item.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Model/Unit Effectivity Example
c l
Unit Effectivity introduces the concept of bills that are effective by an end-item unit number,
r a
as opposed to an effectivity by date. This example shows a unit-effective BOM.
When defining a unit-effective BOM, you can have components with date effectivity and unit
O ly
effectivity. When defining a date-effective BOM all components must be date effective; you
l & On
cannot have components with unit effectivity.
If your parent has model/unit effectivity, you can have date- and unit-effective child
a e
components. If your parent has date effectivity, you can only have date-effective child
n
t e r U s
components; you cannot have unit-effective child components.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Model/Unit Effectivity Example
c l
This example shows the requirements to build Unit 027. You can see the components blocked
O ly
Model/unit effectivity allows discrete control over product structure change and less additions
l & On
of a part numbers, as well as separating product structure from the schedule.
You should still follow the form/fit/function rules that you have set up for your business needs.
n a e
The model/unit effectivity feature requires that you have Oracle Project Manufacturing
t e r U s
installed, and it should be used in project-oriented manufacturing and with low-volume
schedules. This feature can also be used by non project-oriented manufacturing, but you will
n
still need to have Oracle Project Manufacturing installed in order to use the feature.
I
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bills of Material: Viewing Unit Effectivity
c l
Use the Bills of Material window to view your components and ranges of effectivity for the
BOM.
r a
You can have a quantity of more than 1 for each unit. You would specify quantity on the sales
O ly
order. Each quantity requires a unique serial number.
& On
Indented Bills of Material: Viewing Unit Effectivity
l
n a e
Use the Indented Bills of Material window to look at your indented BOMs. The Unit
Effectivity tab shows you the effectivity control for each component in the family tree and
t e r U s
either the date or model/unit From and To values that you have designated for that component.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Assumptions
• Use the Manufacturing and Distribution Manager responsibility to complete this
practice.
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Creating Standard Bills of Material
Create three bills of material for items ##1000, ##1040, and ##2010.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
1. Create three bills of material for items ##1000, ##1040, and ##2010.
3. The following diagram represents the structures you will create. Enter components and
quantities; leave all other information as it defaults. Be careful to include the correct
quantities of components in your bills.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
BOM Item Type
c l
Verify the assembly's BOM Item Type attribute in the item master specifies the bill of material
r a
type you want to create. For example, to create a model bill of material, select Model from the
drop down list as the value of the BOM Item Type item attribute.
BOM Allowed O ly
l & On
You must select the BOM Allowed item attribute for both the assembly item and all of the
component items from which you want to construct a bill of material. When you select the
a e
BOM Allowed item attribute, you can use the item as either an assembly or as a component of
n
Inventory Item attribute.
t e r U s
a bill of material. Before you can select the BOM Allowed item attribute, you must select the
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Planning Bills of Material
c l
Use planning bills for aggregate forecasting. Planning bills of material specify components that
r a
belong to the same product line. Assign planning percentages, as well as quantities per
assembly, to the components in proportion to their use in the assembly. The forecast explosion
O ly
process allocates forecasts of the assembly to the components based on their planning
l & On
percentages and their quantities per assembly. The percentages associated with the components
on a planning bill of material do not need to add to 100%. You can define alternate and
bill.
n a e
common planning bills, where the bill you reference as a common must be another planning
e r s
Planning items can be nested within one another any number of times. When you nest planning
t U
items, Oracle Master Scheduling explodes forecasts level by level and applies planning
I n
percentages at each level.
c l e
You neither order nor build planning assemblies.
If the top level item attribute BOM Item Type value is Planning, you can use those items with
r a
item attribute BOM Item Type value of Planning, Model, Option class, and Standard as
components.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Model Bills of Material
c l
Use model bills of material to specify classes of options from which your customers can
r a
choose when they order configurable items.
You do not build model assemblies; you assemble a configured item on a final assembly
O ly
schedule. The configured item has a standard bill of material that contains only the options that
the customer selected.
l & On
Select Customer Ordered, Customer Orders Enabled, Internal Ordered, and Internal Orders
a e
Enabled item attributes. Clear the check box for the Build in WIP item attribute.
n
t e r U s
The two types of model bills of material are:
• Pick-to-order: Your customer chooses options, and you pick and ship the components.
I n
• Assemble-to-order: Your customer chooses options, and you assemble the components
before shipping.
l e
In the example in the slide, each computer is made up of a monitor option class, cpu option
c
class, and an accessories option class.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Model Bills of Material
c l
The parent (top level) in a Model bill usually represents a product or service. For example, a
O ly
Option Classes, such as Monitor, Keyboard, and so on, are items with the BOM Item Type
l & On
attribute set to Option Class. The Model bill for the PC System would show the PC System as
the parent and the Option Classes named Monitor and Keyboard as components.
a e
Optional items can be grouped into Option Classes. For example, the Monitor Option Class can
n
t e r s
be used to group different sizes and types of optional monitors. The optional Monitor Items are
standard items (because the BOM Item Type attribute for these items is set to Standard), and
U
I n
they are appearing as components in the Monitor Option Class bill of material.
Standard items can also be required in a bill of material. An item is required when the Optional
l e
check box in the Bills of Material window is not selected.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Option Class Bills of Material
c l
Use option class bills of material with model bills of material to specify families of options
r a
from which your customers can choose when ordering configurable items.
You neither order nor build option class assemblies; you order and build the options. You
O ly
should clear Customer Ordered, Customer Orders Enabled, Internal Ordered, Internal Orders
l & On
Enabled, and Build in WIP item attributes.
Use option class bills of material for aggregate forecasting. Assign planning percentages to the
a e
components in proportion to their use in the assembly. The forecast explosion process allocates
n
t e r U s
forecasts of the assembly to the components based on their planning percentages.
If the assembly BOM Item Type item attribute value is Option Class, you can use those items
components.
I n
with BOM Item Type item attribute value of Model, Option Class, and Standard as
l e
Since Oracle Order Management uses option class bills of material, you must also define them
c
in the organization designated by profile option OE: Item Validation Organization.
r a
Do not create alternate bills of material for model and option class bills of material. You cannot
choose alternate bills of material when you configure an order.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Option Classes
c l
An option class is an element of a Configuration Model. The purpose of option classes is to
r a
group and present viable alternatives. You typically select one or more options from each
option class during runtime to create a valid configuration. An option class is designated by
BOM Item Type set to Option Class.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill of Material Data
Planning %
c l
r a
Enter the percentage of assembly sales that this component usually contributes. The planning
percentages for all the components on a bill of material may total more than 100%. Oracle
O ly
Planning uses this percentage to calculate forecasts for the components from forecasts for the
product family and model.
l & On
Use the Planning % field for planning, model, and option class bills of material.
Check ATP
n a e
t e r U s
Use Check ATP for model and option class bills of material. Select the check box to indicate
that the available-to-promise feature in Oracle Order Management should check the availability
I n
of this component when suggesting a promise date for a customer order. You can select this
check box if you have selected the item attribute Check ATP for both the assembly and the
component.
c l e
For example, you might need to check ATP for the keyboard and CPU each time you order a
r a
Laptop Computer configuration but the supply of all other components is not constrained. In
that case, you would set the ATP Components Item Master field to Yes for the Laptop
O Computer and the CPU option class, and you would set the Check ATP Item Master field to
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Implicit Rules
c l
Basic rules are included with Oracle Bills of Material:
• Optional or Required
r a
• Mutually exclusive
• Maximum and minimum quantity O ly
• Quantity Cascade
l & On
n a e
The rules provided by Oracle Bills of Material are called implicit rules. Oracle Configurator
honors these rules as well as the rules defined using Oracle Configurator Developer.
e r s
For example, whether external speakers are included in an order for a personal computer
t U
system is typically an option. In the bill of material the personal computer system, the
I n
component item named Speakers is marked as an optional item. An example of a required item
c l e
is a power supply cord that is provided with every personal computer.
Mutually exclusive options require that when one option is chosen on an order, a conflicting
r a
option be excluded. For example, choosing an internal flexible disk drive in a laptop computer
excludes the internal compact disk drive because they occupy the same space.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Mutually Exclusive
c l
Used with model and option class bills of material. This component applies if you have taken
one of these actions:
r a
• Selected both Mutually Exclusive and Optional, a customer placing a customer order can
O ly
choose no options or choose one, and only one, option.
n a e
• Cleared Mutually Exclusive and selected Optional, a customer placing a customer order
t e r U s
can choose no options or any number of options.
• Cleared both Mutually Exclusive and Optional, a customer placing a customer order can
n
choose any number of options, but must choose at least one option.
I
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill of Material Example
c l
Required, mutually exclusive: An ice cream sundae model requires ice cream, but you can only
pick one flavor per sundae.
r a
Optional, mutually exclusive: You do not have to select a syrup, but if you do, you can only
pick one kind of syrup per sundae. O ly
& On
Required: You must pick a topping, but you can pick one, some, or all.
l
without a cherry.
n a e
Optional: You can have a cherry, if you want, but the sundae configuration will be complete
t e r U s
Additionally, the BOM Model can define minimum and maximum quantities on the options.
With Oracle Configurator, you can define additional rules that further constrain valid sundaes
I n
configurations. For instance, you can limit the model to some maximum number of toppings
that is less than all the available toppings or you can define a rule that excludes fudge syrup
l e
when the user chooses chocolate ice cream.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Configure To Order Overview
c l
Oracle Manufacturing enables you to define options available for products and to process
cost accounting. r a
orders for unique product configurations while maintaining control of inventory, planning, and
O ly
A Configure to Order environment is one where the product or service is assembled or kitted
l & On
on receipt of the sales order. Oracle Applications supports the Configure to Order environment
with a range of features in order management, demand forecasting, master scheduling,
a e
production, shipping, and financial accounting.
n
t e r U s
Assemble–to–Order Model (ATO Configuration):
• Model bill of material with optional items and option selection rules
I n
• Configuration manufactured from mandatory components and selected options, or
purchased from a supplier
l e
Assemble-to-Order Item:
c
• Standard bill of material with mandatory standard components
r a
• Item manufactured from mandatory standard components, or purchased from a supplier
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Configure To Order Models
c l
• ATO example: Final assembly of a custom bicycle based on optional components and
r a
modular subassemblies specified on a customer sales order. Automobiles and personal
computers are other examples of items that can be assembled to order. Costs of the final
O ly
assembly process can be tracked to a work order.
a e
• Hybrid example: An ATO Model within a PTO Model, for example, assemble a personal
n
t e r s
computer to order (ATO). Then pick to order (PTO) the personal computer and selected
optional items, such as keyboard, monitor, and audio speakers to fulfill a sales order for a
U
I n
configured personal computer system.
• Pre-configured items example: Using Bills of Material as a hosting application, the
l e
Configurator window can be used to construct and maintain pre-configured items for
c
repeat business. For example, a regional transportation district (RTD) repeatedly
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Configure to Order Environments
c l
You can define model and option class bills of material that list the options your customers can
r a
choose from when they place a sales order for an assemble to order configuration. To define
assemble to order models whose configurations you assemble using work order, flow
O ly
schedules, or purchase orders, you must set the Assemble to Order Item Master field to Yes for
the model and option class items.
l & On
When you assign an option class item to a model or option class bill of material, the
a e
component item (option class) must have the same value for the Assemble to Order Item
n
e r
Master field or Pick Components Item Master field as the parent item (model or option class).
s
So, you can only assign assemble to order option classes to assemble to order models and pick-
t U
to-order option classes to pick-to-order models.
I n
You can also define hybrid model bills where you list some options that you pick and some
l e
options that you assemble using a final assembly order. When you place an order, your
customers can choose the options for the assembled configurations as well as the picked
c
r a
options that ship with the order. For each of these hybrid model bills, you set the Pick
Components Item Master field to Yes for the top model item and assign assemble to order
O model items as components (where the Assemble to Order Item Master field is Yes). So the
components of a PTO model can include ATO models as well as PTO option classes and
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
PTO and ATO BOM Models
c l
A BOM Model is a model that you import from Oracle Bills of Material into Oracle
r a
Configurator Developer. When you import a BOM Model, effective dates, BOM rules, and
other data are also imported into Configurator Developer. You can extend the structure of the
O ly
BOM Model in Configurator Developer, but you cannot modify the BOM Model itself or any
of its attributes.
l & On
ATO BOM Models enable you to configure an item online during the order entry process (in
a e
OM) and automatically generate a work order in WIP to assemble the resulting item. An ATO
n
item.
t e r
Model also enables you to track, at the component level, the costs associated with creating an
U s
I n
PTO BOM Models also enable you to configure the item during order entry, which
automatically generates a pick list. A PTO Model does not automatically generate a work order
c l e
or enable you to track manufacturing costs.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Assemble To Order Model
After the configured order is submitted:
c l
r a
• Inventory: A unique Inventory Item ID is created for the configured end-item.
O ly
• Bills of Material: A standard bill of material is created for the unique Item ID that lists the
required items and selected options.
& On
• Bills of Material: A routing for the configured standard bill of material is created.
l
n a e
• Planning: Lead-time calculations are performed and replenishment orders are scheduled.
• WIP, Flow Manufacturing, and Purchasing: The plan is executed, and the product or
service is created.
t e r U s
• Shipping: The order is picked, shipped, and closed.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
AutoCreate Configuration Items
c l
Once you have entered and scheduled a sales order for an assemble-to-order model, Bills of
r a
Material automatically defines a new, unique configuration item complete with a bill of
material and routing (based on the model primary bill and primary routing) for every non-
O ly
phantom model in your configuration. These model BOMs and routings are created in the
l & On
manufacturing organization defined by your sourcing rules. When Bills of Material creates a
configuration item for a sales order, it links the new top level configuration item to the sales
a e
order such that Order Management ships the new item to fulfill the order.
n
items.
t e r
Item attributes and sourcing rules for the configuration item are inherited from the base model
U s
I n
Steps to AutoCreate Configuration Items
Create unique configuration items complete with bills of material and routings (based on the
l e
model bill and routing) to fulfill customer orders for manufactured configurations. A cost
c
rollup is performed for each new configuration to establish accurate standard costs that are
r a
posted to cost of goods sold. Lead time rollup is performed for configuration items with
discrete routing, in order to calculate an accurate manufacturing lead time for the
O configuration.
e A
append or replace. For the Order number/line number method, you can specify a delimiter to
separate order number and line number.
c l
Match and Reserve
r a
Match and Reserve ATO Configurations enable you to check for an existing matching
O ly
configuration and to reserve against it. While entering an order, you can search for matching
l & On
active ATO configurations or pre-configured items, and reserve any available on-hand material
that is in the shipping organization. If the match profile is on, existing pre-configured ATO
a e
items, or auto-created configuration items are matched and used at all levels.
n
e r
You can check for matches from the sales order pad, by choosing the Match action button. You
s
can also match and reserve using the AutoCreate Configuration batch process, accessed from
t U
the Assemble To Order submenu, within the BOM responsibility. You can match and reserve
I n
using the Create Configuration Item Workflow activity. Finally, you can match and reserve by
creating your own custom matching. The profile, BOM: Use Custom Match Function, controls
l e
whether the match performed uses the standard match function or a custom match function.
c
r a
Weight and Volume Calculation
AutoCreate Configuration Items calculates the weight and volume for the configured item, by
O rolling up the weight and volume of the components in the OM validation organization. For
e
c l
step it includes has the Option Dependent operation field set to No, since the new item is a
mandatory item with no options in its bill. The routing for the Laptop Computer configuration
r a
includes step 25 to Clean processor since the 486 processor was chosen which referenced step
25. Since step 25 is Option Dependent in the model routing, it would have been dropped if you
O ly
had not chosen the 486 processor option.
l & On
You can create ATO configurations with flow routings. You can define multiple routings for
an ATO model, and designate them as a flow or non-flow routing. AutoCreate Configuration
n a e
Items uses the primary routing of the base model and creates a flow routing if the primary
routing is a flow routing, and vice versa.
Cost Rollup
t e r U s
If the organization is using a Standard costing method, in a single level environment, a single
I n
level Cost Rollup is performed for the configuration item, using the configuration BOM and
l e
routing. If the organization is using an Average costing method, the configuration item has
zero cost for the Average cost type.
c
r a
Configuration items do not pick up any cost from models or option classes in their single level
bill. Models and option classes are only considered by forecast consumption and master
m y
d e
ca
e A
Deactivating Configuration Items
c l
Bills of Material lets you automatically deactivate item numbers associated with completed
r a
configuration orders. You can also deactivate configuration items to remove them from item
master reports and screens before you actually purge them from the database.
O ly
When you set up Inventory and Bills of Material, you can define an item status to identify
l & On
inactive configuration items. You can use this status to disable the configuration item from all
Oracle Manufacturing functions. You would normally specify No for each of the following
a e
item attributes for inactive configuration items:
n
• BOM allowed
• Build in WIP
t e r U s
• Transactable
• Stockable I n
l e
When defining bills of material parameters, specify the item status to use for completed
c
configuration items.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m
bills of material and routings. The ability to delete configuration items is subject to the same
y
deletion constraints that operate for other item types as well.
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Product Family Overview
c l
A product family is a grouping of products whose similarity in resource usage, design, and
r a
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
O ly
family is a single level bill. Members of a product family can belong to one and only one
a e
You may apply the product family template to create your product family consistently.
n
t e r U s
You must define the product family item and all the family members as items.
If you do not assign planning percentages, the Oracle database will assign the default
percentage of 100%.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Creating Product Families
c l
1. Navigate to the Master Item window (N) Inventory > Items > Master Items. If you are a
r a
Flow Manufacturing customer, select Product Family from the Flow Manufacturing
window. The product family template is automatically applied.
O ly
2. Apply the product family template. You are not required to use the product family
l & On
template. If you choose not to do so, make sure you define the correct product family
attributes. Specifically, the item must be an inventory item and the BOM Item Type must
a e
be Product Family. The item must also be BOM allowed.
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Assigning Members to a Product Family
c l
1. Navigate to the Product Family window (N) Material Planning > Setup > Product Family.
2. Select a product family item.
r a
O ly
3. Select item members of the product family. The description, type, forecast control, and
planning method for the member items are displayed for the items selected. When an item
n a e
4. Commit the record by selecting Save from the File menu. You can commit a record
t e r U s
without assigning planning percentages. The default planning percent is 100. The default
effectivity date is the system date.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Assigning Percentages
c l
1. Navigate to the Product Family window (N) Material Planning > Setup > Product Family.
r a
2. To assign planning percentages for a member item, choose the Allocation button (N)
Material Planning > Setup > Product Family (B) Allocations.
O ly
3. Enter the product family member’s planning factor.
& On
4. Enter effectivity dates for the item. Effectivity dates cannot overlap.
l
n a e
5. Optionally, enter comment text.
6. Commit the record by selecting Save from the File menu. You can commit a record
e r s
without assigning planning percentages. The default planning percent is 100. The default
t U
effectivity date is the system date.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bills of Material Revisions
c l
A bill of material revision is an item revision and might indicate that the components of an
r a
item have changed. You do not have to use item revisions when you change bills of material,
however, in some industries, it is best to create a new item revision when you change a bill of
O ly
material. Oracle Engineering and Oracle Bills of Material date stamp and time stamp all
a e
The bill of material revision is the same as the item revision. There is no separate bill of
n
material revision.
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Entering Item Revisions
c l
Define an item revision by entering a revision identifier and effective date (N) Bills > Bills (B)
Revision.
r a
• Revision: Enter a new Revision Identifier. You can use up to three alphanumeric
characters. O ly
& On
• Effective Date: Enter the date the revision becomes effective.
l
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Tools Menu Options
c l
Use the Tools menu to perform the following functions:
Copy Bill From
r a
O ly
• Use to copy components of another assembly to this assembly.
Assign Common Bill
l & On
• Use to reference the components of another assembly as the components of this assembly.
Configure Bill
n a e
Check for Loops
t e r
• Use to launch the ATO processes.
U s
Rollup Costs I n
• Use to check for bill of material loops in the multilevel bill of material for this assembly.
l e
• Use to calculate the cost of this assembly.
c
Rollup Lead Times
r a
• Use to calculate the lead times for this assembly.
O Indented Bills
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Find Indented Bills
c l
Use the Find Indented Bills of Material window to enter parameter information you want to
r a
view on an indented bill of material. An indented (multilevel, exploded) manufacturing bill of
material displays the structure of a manufacturing item.
To view an indented bill of material: O ly
& On
1. Navigate to the Find Indented Bill of Material window (N) Bills > Indented Bills.
l
n a e
2. In the Find Indented Bills window, enter the item and/or the alternate for the bill.
3. Enter the revision, the revision date, and the number of levels to explode for this bill.
e r s
4. Select a Display option: All, Current, or Future and Current components effective as of the
t U
revision date you specify. Use the Implemented Only field to further restrict the
I n
components displayed.
l e
5. Select a sort option for each level of the bill, by operation sequence then item sequence, or
item sequence then operation sequence.
c
r a
6. Indicate whether to see costing information, and if so, enter the cost type. You can
simulate product costs for budgeting and planning analysis purposes. To do so, the
O Privilege to View Cost security function must be enabled for the responsibility. Indicate
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Viewing Indented Bills of Material
c l
Use the Indented Bill of Material window to view an indented bill of material (N) Bills >
Indented Bills (B) Find.
r a
An indented bill of material is a bill of material that is exploded through many lower levels.
O ly
You can choose the number of lower levels that you want to see—up to 60—both by setting
l & On
the personal profile value BOM: Default Bill of Material Levels and by choosing a value when
you request the indented bill of material.
a e
Item numbers preceded by a plus sign (+) have components; double-click the Item number to
n
view the components.
t e r U s
If lower-level components already appear, a minus sign (-) precedes their assembly item
I n
number. To remove the components from view, double-click the item number or click the
double minus sign -- icon.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Comparing Bills of Material
c l
You can compare any two bills. For example, compare the primary to an alternate bill, the
r a
same bill across organizations, or the current revision of an item to a future revision. The two
assemblies and their attributes are referred to as Bill 1 and Bill 2, or simply as 1 and 2.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Finding Bills to Compare
c l
Use the Find Bills to Compare window to enter information about two bills of material that you
want to compare.
r a
1. Navigate to the Find Bills to Compare window.
O ly
2. In the Find Bills to Compare window, enter selection criteria for Bill 1. Do the same for
Bill 2.
l & On
n a e
3. Check comparison criteria check boxes for the attributes to compare the bills on.
4. Select an Order By option: by item sequence then operation sequence, or by operation
t e r
sequence then item sequence.
U s
5. To view only the differences between bills, check the Differences Only check box.
I n
6. Choose the Compare button to compare the bills online.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill Components Comparison
c l
Use the Bill Components Comparison window to view information about the components of
r a
two bills of material (N) Bills > Comparison (B) Compare.
The Bill Components Comparison window displays both bills. Two columns of check boxes,
O ly
one for assembly 1 and one for assembly 2, indicate if the component appears in the assembly.
l & On
The Main tabbed region displays the item and operation sequences, the planning percent, the
quantity, and whether the item is optional.
n a e
The Effectivity tabbed region displays the effective date range and whether the item is
implemented.
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill of Material Comparison Report
c l
Use the Bill of Material Comparison Report to report the comparison between two
r a
manufacturing assemblies. You can compare primary bills, manufacturing and engineering
bills, alternates, and different revisions. Based on your comparison criteria, if the assemblies
O ly
have identical components, item sequences, operation sequences, yields, quantities, and
l & On
implementations, one line is printed for each identical component. Otherwise, the report prints
a separate line for each different component.
a e
To submit the Bill of Material Comparison Report:
n
t e r s
1. Navigate to the Report Bill of Material Comparison window (N) Reports > Comparison.
The parameters for the Bill of Material Comparison Report are identical to those you
U
2. Choose Report.
I n
supply when comparing bills of material online.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Common Bills of Material
c l
If two or more organizations manufacture the same item using the same bill of material, you
r a
can define the bill in one organization and reference it from the other organizations. Necessary
changes must then be made to the referenced bill.
O ly
You can create a common bill within the same organization, and across multiple organizations.
l & On
You have the option to create common bills in all organizations under the current organization
in the chosen organization hierarchy, or create common bills in all organizations that have the
a e
same item master organization as the current organization and are accessible by the user
n
bills of material.
t e r
responsibility. Sharing bills across multiple organizations minimizes the maintenance of your
U s
I n
When you enter orders for models, kits, and assemblies in Oracle Order Management, you
must define all bills of material in your item master organization (your OE: Item Validation
l e
Organization profile option value). Using common bills of material, you can share bills of
material that exist in your manufacturing organizations with your item master organization.
c
r a
When you define a bill for a new assembly, you can reference another assembly and
organization as a common bill of material. You do not need to make any further entries for the
O bill of material.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Creating Common Bills of Material
To create a common bill:
c l
r a
1. Navigate to the Common Bill window from the Bills of Material window (N) Bills > Bills
(M) Tools > Create Common Bill. Do this by choosing Create Common Bill from the
Tools menu. O ly
& On
2. Enter the organization for the item to reference as a common bill.
l
n a e
3. Enter the bill to use as a common.
4. From the Special Menu, launch the Create Common Bills concurrent program. Enter the
following parameters:
t e r U s
- Single Organization/Organization Hierarchy/All Organizations - Select one of the
I n
three options. If you select Single Organization, enter the organization and item
names where the common bill needs to be created. If you select Organization
c l e
Hierarchy, enter the required name of the organization hierarchy. In this case, the
processing is done for all organizations below the current organization in the chosen
r a organization hierarchy. If you select All Organizations, then processing is done for all
organizations that have the same item master organization as the current organization.
O - Organization Hierarchy
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Common Bills of Material Guidelines
c l
Any two items that are of the same bill type can share common bills. If two different items
a
share the same bill, you can define the bill once and then maintain one copy instead of two.
r
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill of Material Loops
c l
A bill of material loop is a situation in which a multilevel bill of material contains the same
r a
item as the top assembly and as a component. Because you create multilevel bills of material
one level at a time, you can inadvertently create a bill of material loop. Processes that detect a
O ly
bill of material loop usually fail entirely or refuse to process the multilevel bill of material
containing the loop.
l & On
You can detect bill of material loops by taking these actions:
a e
• Request the Check for Loops concurrent process.
n
t e r U s
• Wait for a concurrent process that uses bills of material to fail entirely or refuses to
process the multilevel bill of material containing the loop.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Checking for Bill Loops
c l
The Check for Loops program can be run from the Tools menu of the Bills of Material
window.
To check for bill loops: r a
O ly
1. Navigate to the Bills of Material window (N) Bills > Bills. Check for Loops on the Tools
& On
menu is only available after saving a bill.
l
Loops.
n a e
2. Choose Check for Loops from the Tools menu (N) Bills > Bills (M) Tools > Check for
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Find Item WhereUsed
c l
View an imploded list of all the using assemblies for a specified component. For example, if
r a
you are proposing a change to a component in multiple bills of material, you can see the
number of assemblies that you would affect.
To view item where used: O ly
& On
1. Navigate to the Find Item Where Used window (N) Bills > Item WhereUsed.
l
n a e
2. In the Find Item Where Used window, enter the item, the revision, the revision date, and
the number of levels to implode for this bill of material. Only current components
t e r U s
effective as of the revision date you specify will be displayed.
3. Indicate whether you need to inquire about component usage for the current organization,
I n
the current organization and all subordinate organizations in the chosen organization
hierarchy, or all organizations that have the same item master organization as the current
l e
organization. You have the ability to specify the organization hierarchy name because
c
current organizations can be accessed from more than one organization hierarchy. Use the
m y
d e
ca
e A
Viewing Item WhereUsed
c l
Use the Item WhereUsed window to view the assemblies in which a component appears.
r a
The level bill of material where the inventory item appears in the using assembly is displayed,
starting at 1 (level 2 signifies the parent of level 1; level 3 signifies the parent of level 2).
O ly
The Item Where Used window has three tabbed regions: Item Details, Bill Details, and
Effectivity.
l & On
component.
n a e
• The Item Details tabbed region displays the revision, the type, and the status for the
t e r U s
• The Bill Details tabbed region displays the alternate, whether the bill is an engineering
bill, the usage quantity (of the item in the immediate parent assembly), the ECO that
I n
implemented the component (if it has been implemented), and the operation sequence.
• The Effectivity tabbed region displays the effective date range and whether the item is
l e
implemented.
c
Use the control buttons to expand or collapse portions of the indented item usages.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill / Component Validation Rules
c l
The following bill and component validation rules apply when defining, copying, or mass
changing bills of material:
r a
• Depending on the setting of the profiles that limit access to different bill types (BOM:
O ly
Model Item Access, BOM: Planning Item Access, BOM: Standard Item Access), you may
not be able to modify bills.
l & On
• You cannot add a component with an operation sequence number that does not exist in the
a e
routing. The only exception is for operation sequences that are equal to 1.
n
t e r U s
• You cannot add a component to a bill where the same component, with the same operation
sequence and effectivity, already exists on the bill.
I n
• You cannot add components to common bills.
• For ATO, PTO, and phantom bills where the parent item has ATP Components set to No,
l e
you cannot add a component that has either the item attributes Check ATP set to Yes or
c
ATP Components set to Yes.
r a• You cannot add an optional component to a bill that is neither model or option class.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill of Material Comparison Report
c l
Use the Bill of Material Comparison Report to report the comparison between two
r a
manufacturing assemblies. You can compare primary bills, manufacturing and engineering
bills, alternates, and different revisions. Based on your comparison criteria, if the assemblies
O ly
have identical components, item sequences, operation sequences, yields, quantities, and
l & On
implementations, one line is printed for each identical component. Otherwise, the report prints
a separate line for each different component.
Bill of Material Listing
n a e
t e r s
Use the Bill of Material Listing to report manufacturing and engineering bills without any
associated component or routing information.
U
I n
Bill of Material Loop Report
Use the Bill of Material Loop Report to check for loops in a bill of material. Bill loops occur
l e
when you assign an assembly as a component to itself somewhere in the multilevel structure.
c
You must fix loops before you can run an accurate MRP, or define a discrete job or repetitive
r a
schedule for the assembly. If no loop exists, No Data Found is printed on the report.
Bill of Material Structure Report
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Mass Changing Bills of Material
c l
Use the Mass Change Bills window to mass change your manufacturing bills of material. You
r a
can define a mass change to add, delete or replace a component, alter a component quantity or
yield, or change other component information. You can mass change all using bills of material
O ly
or choose a subset of bills by item range, item category, or item type. You can mass change
l & On
primary and alternate bills of material for each using assembly. For manufacturing bills, you
can implement the changes immediately. You can also report effective changes for all using
assemblies or components.
n a e
e r
Bills of Material take into account all the actions you enter to determine if the change is
s
applicable. For example, suppose you add component A and delete component B. This change
t U
is made only if component A does not exist and component B does exist on the selected bills.
I n
The change is applied only if both conditions are met. In this example, two records are
affected.
l e
When you make mass changes to bills of material, you can perform the following actions:
c
r a
• Change information about an existing component
• Add a component
O • Replace one component with another
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Entering Mass Changes
To mass change bills of material:
c l
r a
1. Navigate to the Mass Change Bills window (N) Bills > Mass Changes.
O ly
2. Enter a mass change order number and a change order type. The change order type
describes your changes and determines the type of bills to modify.
3. Select a single item unit number.
l & On
only).
n a e
4 Indicate whether to increment the parent item’s revision by 1 (numeric based revisions
e r s
5. Indicate whether to update Work in Process material requirements of any unreleased
t U
discrete job, or any release or unreleased repetitive schedule associated with the parent
items.
I n
e
6. Specify the parent items to change. You can use a category set, a category range, or an
l
item range. Alternatively, indicate whether to change all primary bills, all primary and
c
alternate bills, or a specific alternate bill. Optionally, enter a base model to mass change
r a configuration items related to this model that meets your other selection criteria.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Entering Component Mass Changes
To enter component changes:
c l
r a
1. Choose the Changes button on the Mass Change Bills window (N) Bills > Mass Changes
(B) Changes.
O ly
2. For each component item to change, indicate the action to perform. You can add or delete
l & On
components to or from a parent item. Or, you can update existing information about the
component on the parent item. With this option a new row is created that you enter new
information into.
n a e
t e r U s
3. In the Main tabbed region, enter the item sequence, operation sequence, the quantity, and
the inactive date for each component.
I n
4. Open the Component Detail tabbed region and enter the planning percent. Enter the yield
and indicate whether the component should be quantity related and included in cost
l
rollups.
c e
5. Open the Material Control tabbed region and enter the supply type. Enter the supply
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bill Creation or Update
c l
The Bills of Material window starts the signature capturing process whenever a bill is created or
r a
updated. While the event is happening in the window, required signatures can be captured online.
Select e-Record Details from the Bills menu to view the e-record associated with the bill of
material.
O ly
Routing Creation or Update
l & On
The Routings window starts the signature capturing process whenever a routing is created or
a e
updated. While the event is happening in the window, required signatures can be captured online.
n
Mass Change Bills
t e r U s
Select e-Record Details from the Actions menu to view the e-record associated with the routing.
I n
The Mass Change Bills window starts the online signature capturing process in different ways,
depending on how you access the window:
l e
• If you access the window by navigating to Bills of Materials > Bills > Mass Changes, the
c
online signature capturing process begins once you select the Implement box and choose
r a Submit.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
Bills of Material Business Events
c l
Using Oracle Workflow, you can automatically trigger actions based on the following Oracle
Bills of Material Business Events:
• Bill of material creation r a
O ly
• Modification to a bill of material header, component or component attribute
• Bill of material deletion
l & On
n a e
• Error during a bill of material deletion
• Creation or modification of a substitute component, reference designator or component
operation
t e r U s
• Component deletion using a delete group
I n
• Error during a component deletion
l e
Business Event examples
c
The following scenarios show how subscribing to a business event can simplify business
r a
processes:
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Assumptions
• Use the Manufacturing and Distribution Manager responsibility to complete this
practice.
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Comparing Bills of Material
e A
l
Enabling Items and Copying Bills of Material in Different Organizations
c
r a
Enable items ##2010, ##3010, ##3020, and ##3030 in organization M2-Boston Manufacturing.
O ly
Copy item’s ##2010 bill of material from the M1-Seattle Manufacturing organization to the M2-
Boston Manufacturing organization.
l & On
Performing Loop Checks
n a e
t e r
Perform a loop check for item ##1000.
U s
Attaching Text Documents
I n
c l e
Attach a text document to item ##1000.
r a
View the indented bill of material for item ##1000.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
4. Select Compare.
I n
•
l e
(B) Compare
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
10. Create an alternate bill of material for item ##2010 using the alternate name ##SUB.
Replace item ##3010 with a different ##3010 for your alternate bill of material.
m y
11. Navigate to the Bills of Material window.
d e
• (N) Bills of Material > Bills > Bills
ca
12. Enter your item ##2010, then from the LOV in the Alternate field, select ##SUB.
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
ca
• (M) Tools > Copy Bill From
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
ca
Enabling Items and Copying Bills of Material in Different Organizations
e A
Manufacturing.
c l
16. Enable items ##2010, ##3010, ##3020, and ##3030 in organization M2-Boston
l & On
18. Query items ##2010, ##3010, ##3020, and ##3030 and enable them in organization M2-
Boston Manufacturing.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
• O ly
(N) Bills of Material > Bills > Bills
l & On
22. Copy bill of material ##2010 from organization M1.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O30. A note displays. Select OK.
34. In the Attachments window, click in the category field and choose Miscellaneous from the
LOV.
ca
39. Close the Attachments window.
e A
l
40. Test your attachment. Query on item ##1000 again.
c
a
41. Is the paper clip icon different? ___________
r
O ly
42. Select the paper clip and review the attachment.
l e
45. Enter item ##1000 and select Find.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 1
Creating Routings
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 2
Objectives
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 3
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 4
Routings
m y
d e
ca
e A
Routings
c l
A routing defines the step-by-step operations you perform to manufacture a product. Each
r a
routing can have any number of operations. For each operation you specify a department that
determines the resources you may use for that operation.
O ly
You must create resources and departments before you create routings.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 5
Primary and Alternate Routings
m y
d e
ca
e A
Primary and Alternate Routings
c l
A primary routing is the list of operations most frequently performed to build a product. You
r a
can define one primary routing and many alternate routings for an item. When you define a
new primary routing, you specify only the item (no alternate name) and you can assign a
O ly
routing revision. For example, you can define a routing for an item that includes two
l & On
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.
a e
You can define an alternate routing to describe a different manufacturing process used to
n
e r
produce the same product. Unlike a new primary routing, specify the item and alternate name
s
to define an alternate routing. You must define a primary routing before you can define
t U
alternate routings, and you can define any number of alternate routings for an item.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 6
Routings in Multiple Organizations
m y
d e
ca
e A
Routings in Multiple Organizations
c l
You create items in the master organization and assign them to the manufacturing and
routings. r a
distribution organizations in which you use them. Within the assigned organization, you create
O ly
In the example above, the routing for item A in organization 1 has operation step 10 in
l & On
department A and operation step 20 in department B. The routing for item A in organization 2
has operation step 10 in department 111 and operation step 20 in department 222.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 7
Operations
m y
d e
ca
e A
Operations
c l
To define a routing operation you first specify an operation sequence number to indicate the
r a
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.
Sequence of Operations O ly
l & On
Routings define the step-by-step descriptions, or operations, for manufacturing an assembly.
Each operation on a routing defines a specific portion of the manufacturing process for the
a e
assembly. You can use operations to identify the location, the quantity, and the state of
n
t e r U s
completion of the assemblies you are currently manufacturing.
For each component item on the bill of material associated with a routing, you can specify the
is needed.
I n
operation sequence where you require the item. You can then issue material where and when it
l e
Standard Operations
c
A standard operation is a commonly used operation that you define as a template to default
r a
operation information when you define routings. When you define a new operation on a
routing, you can specify a standard operation whose information Bills of Material copies into
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 8
the operation you are currently defining. You can then change any of the copied information
for the new operation.
Backflushing Transactions
You can specify at what point in the routing you backflush component material. Moves
automatically backflush the appropriate components at the time they are needed. You can
postpone the backflush of material at time-critical operations until a later operation.
Minimum Transfer Quantities
You can set the minimum quantity that you move from an operation when you define a routing.
The Shop Floor Transaction window issues a warning when you move a quantity less than this
minimum.
Attachments
You can attach files, which may include instructions, to routing operations.
Option Dependent Operations
When you define routings for model and option class items, you can indicate the operations
that appear in a configuration item’s routing only if you choose an option that references that
operation. Bills of Material automatically creates a configuration item’s routing including all
operations that are not option-dependent and any option-dependent operations referenced by a
chosen option.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 9
Resources
m y
d e
ca
e A
Resource Usage
c l
You can associate multiple resources with an operation on a routing. For each resource, you
r a
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.
O ly
l & On
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
a e
the specific resources. While a resource can belong to several resource sets, a resource can only
n
e r
belong to one parent resource. When a WIP lot is at an operation with a parent resource or
s
resource set attached to it, you are prompted to enter a valid resource used in processing the
WIP lot.
t U
I n
Item or Lot-Based Resources
l e
You can specify resource usage as a fixed rate per job for activities such as setup and
c
teardown, and variable rates for resources whose usage depends on the number of units
r a
processed. For lot based resources you choose the Lot basis type and your usage rate is fixed,
and for item based resources you choose the Item basis type to indicate that your usage rate is
O variable.
Create Routings
Chapter 6 - Page 10
Oracle Cost Management divides lot based resource usages by lot size to determine item costs.
For example, you might define a lot based resource that represents time spent setting up a
machine, and a resource that represents the time to tear down the machine for the next job or
schedule. You could schedule and collect costs for both the setup and tear down resources.
Resource Scheduling
You can specify usage rates either as resource units per item unit, or the inverse - item units per
resource unit. For example, you could specify usage rate for a machine hour resource in either
units per hour, or hours per unit. For each routing operation, you can specify multiple resources
and usage rates.
For each resource, you can specify whether to schedule it, and whether it overlaps the prior or
next operation. If you specify that a resource overlaps the prior operation, Oracle Work in
Process schedules the resource so that the last resource on the prior operation ends at the same
time as this resource. Conversely, if you specify a resource that overlaps the next operation,
Work in Process schedules the resource so that the first resource on the next operation begins
at the same time as this resource.
Resources can be defined as simultaneous or alternates with other resources, independent of an
assembly’s routing. Two or more resources can be scheduled to be working concurrently
within the same job operation. For example, a drilling machine and machinist must be
scheduled at the same time. Each operation contains a scheduled sequence of resources. You
can define the sequence in which resources are consumed. You can create a different resource
or group of resources that can be used to substitute the primary resource or group of resources
m y
within a job operation. For example, if unskilled labor is unavailable to perform a task, it can
be substituted with skilled labor. The scheduling system will schedule the skilled labor if the
unskilled labor is fully committed. This is referred to as alternative scheduling.
d
Work in Process schedules assuming that the department uses up to the number of assigned e
c
units of the resource simultaneously - up to the number that exist in the department.
a
Process schedules it around the clock regardless of shifts.
e A
If you specify that a resource is available 24 hours (such as time in a drying area), Work in
O ly
Process based on move transactions and purchase order receipts for outside processing. You
can also manually charge resources. You can collect and group resource charges by activity for
cost reporting.
l & On
Resource Capacity Modifications
n a e
For each resource on a shift, you can override the number of resource units available (such as
t e r U s
number of machines) and specify additions or reductions to the amount of time the resource is
available on that shift. These capacity modifications are assigned to simulation sets that you
I n
can use later when you generate a capacity plan or schedule discrete jobs or repetitive
schedules to simulate capacity changes.
l e
Resource Usage Rate or Amount
c
The usage rate or amount is the amount of the resource consumed at the operation, either the
r a
quantity per item or per lot. If you assign more than one resource unit to work at an operation,
O Work in Process considers the number of units when scheduling a resource at an operation.
Assign the usage rate for the resource as the total quantity per item or lot, regardless of the
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 11
number of resource units you specify. For example, if you define a machine resource to require
10 hours per item and you assign 2 resource units to the resource, Work in Process
automatically schedules 2 machines for 5 hours.
Standard Resource Costs
When you define a routing, you specify the resources you use to build the items, and each
resource has costs associated with it. By defining the routing with specific resources, you
establish standard resource costs for any item that uses the routing.
Outside Processing
You can define outside processing resources and then assign these resources to operations on a
routing. Work in Process considers any operation that has an outside processing resource as an
outside operation.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 12
Creating Routings
m y
d e
ca
e A
Creating Routings
1. Navigate to the Routings window.
c l
r a
2. Enter a manufacturing item to create a routing for.
O ly
3. If you are creating an alternate routing, enter an alternate. For a primary routing, do not
enter an alternate.
& On
4. If you are updating an existing routing, enter the routing revision and the effective date.
l
Revisions window.
n a e
To update the revision, choose the Routing Revisions button to open the Routing
t e r U s
5. If you would like this routing to be capable to promise, then choose the Capable to
Promise button. Capable to promise describes an available to promise calculation that
I n
considers both available material and capacity of manufacturing and distribution
resources. You are able to define one and only one CTP routing for each item.
l e
6. Select a display option to display All, Current, or Future and Current operations effective
c
as of the revision date you specify. To enter completion subinventory and locator
r a information, or view a common routing, choose the Routing Details button to open the
Routing Details window.
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 13
7. Enter the operation sequence, or let the system automatically generate it for you,
according to your profile setup.
8. 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 Tools menu. If you use a standard operation code, the operation information for that
code will be copied into the operation you are currently defining. You can then update that
information as desired. You can assign the same standard operation to more than one
operation sequence within the same routing. The Routings window has five tabbed
regions: Main, WIP, Operation Yield, ECO, and Description.
9. Enter the department in which the operation is performed.
10. Enter an effective date range.
11. For operations in ATO model or option class routings only, indicate whether the
operation is option dependant, that is, whether the operation is dependant on the choice of
an optional component. All mandatory components and their related operations appear on
the routing for each configuration. The default is enabled.
12. Optionally, enter the item’s manufacturing lead time percent required to complete all
previous operations on the routing. If the manufacturing lead time equals 10 days and all
previous operations combined require 2 days, the lead time percent is 20%.
13. Open the WIP tabbed region and select Count Point and Autocharge options. Indicate
whether to backflush components on shop floor moves at this operation. A backflush
transaction automatically pulls Operation pull components from inventory. Work in
Process also pulls all Operation pull components at non-backflush operations preceding
this operation through the previous completed backflush operation. Enter the minimum
m y
d e
transfer quantity of assemblies to move from this operation to the next. Work in Process
ca
will warn you if you attempt to move a number less than this value. If you used a standard
operation, this value defaults to minimum transfer quantity defined for the standard
operation. Otherwise the default is 0.
A
14. Open the Operation Yield tabbed region. You can define routing networks for Standard,
e
c l
Flow, and Lot-based routings. If the routing is lot-based, then the Yield, CUM Yield,
Reverse CUM Yield, and Include in Rollup fields will display. To enable Operation Yield
r a
in Shop Floor Management, enter expected operation yields for each operation listed. For
example, enter 0.9 for a 90% yield. These fields are displayed for Shop Floor Management
enabled organizations. O ly
costing team.
l & On
15. Indicate whether the operation yield is to be considered in the rollup, as required by the
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 14
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 15
Lead Time Management Overview
m y
d e
ca
e A
Lead Time Management Overview
c l
Oracle Manufacturing uses dynamic (quantity dependent) lead times to plan material and
r a
resource requirements, and to determine material requirement dates for available to promise
(ATP) calculations. When computing requirement dates, both the fixed and variable
O ly
components of an item’s manufacturing lead time are used. When setting time fences for
Lead Times
l & On
planning and available to promise calculations, an item’s cumulative lead times are used.
a e
Lead times are item, operation, and operation resource attributes that refer to the amount of
n
You can:
t e r U s
time you need to obtain or manufacture an item.
I n
• Plan material and resources quickly and accurately.
• Establish appropriate planning time fences for products.
l e
• Create purchase orders for material, accounting for vendor lead time.
c
r a
• Schedule material to arrive at an operation where it is consumed.
• Schedule each resource at an operation where it is consumed.
Create Routings
Chapter 6 - Page 16
Computed vs. Assigned Lead Times
For manufactured items, you can automatically compute manufacturing and cumulative lead
times for a specific item or a range of items. You can also maintain this information manually.
You must manually assign all lead time information for purchased items.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 17
Item Lead Time Attributes
m y
d e
ca
e A
Item Lead Time Attributes
c l
For all scheduled time elements, which are less than the standard workday, the system will
r a
compute the lead time day by dividing the lead time element by 24. The standard workday is
defined in the workday calendar. Oracle Manufacturing stores the following lead time
information for each item:
O ly
l & On
• Fixed Lead Time: The portion of manufacturing lead time that is independent of order
quantity. You can enter this factor manually for an item, or compute it automatically for
manufactured items.
n a e
t e r s
• Variable Lead Time: The portion of manufacturing lead time that is dependent on order
quantity. You can enter this factor manually for an item, or compute it automatically for
U
I n
manufactured items.
• Preprocessing Lead Time: A component of total lead time that represents the time required
l e
to release a purchase order or create a job from the time you learn of the requirement. You
c
can manually enter preprocessing lead time for both manufactured and purchased items.
r a• Post Processing Lead Time: A component of total lead time that represents the time to
make a purchased item available in inventory from the time you receive it. Manually enter
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 18
postprocessing lead time for each purchased item. Postprocessing lead time for
manufactured items is not recognized.
• Processing Lead Time: The time required to procure or manufacture an item. You can
compute processing lead time for a manufactured item, or manually assign a value.
Processing lead time is computed as the time as total integer days required to manufacture
1 lead time lot size of an item. You must manually assign a processing lead time for
purchased items. Processing lead time does not include preprocessing and postprocessing
lead times.
• Lead Time Lot Size: The quantity you use to calculate manufacturing lead times. You can
specify an item’s lead time lot size to be different from the standard lot size.
• Dynamic Lead Time Offsetting: A scheduling method that quickly estimates the start date
of an order, operation, or resource. Dynamic lead time offsetting schedules using the
organization workday calendar.
• Total Lead Time: The fixed lead time plus the variable lead time multiplied by the order
quantity. The planning process uses the total lead time for an item in its scheduling logic
to calculate order start dates from order due dates.
• Cumulative Manufacturing Lead Time: The total time required to make an item if you had
all raw materials in stock but had to make all subassemblies level by level. Oracle Bills of
Material automatically calculates this value, or you can manually assign a value.
• Cumulative Total Lead Time: The total time required to make an item if no inventory
existed and you had to order all the raw materials and make all subassemblies level by
y
level. Bills of Material automatically calculates this value, or you can manually assign a
value.
m
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 19
Manufacturing Lead Time Computations
m y
d e
ca
e A
Manufacturing Lead Time Computations
c l
Bills of Material computes manufacturing lead times from item, routing and resource
O ly
Processing lead time is computed as the time required to complete 1 lead time lot size of an
l & On
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.
a e
For items that you plan and cost by the same lot size, you can specify a value only for the
n
standard lot size.
Routings
t e r U s
I n
Oracle Manufacturing uses routing, operation, and resource information to compute fixed,
variable, and processing lead times for manufactured items. Lead times are not calculated for
l e
purchased items even if they have a routing. When computing manufacturing lead times,
c
primary routings are automatically updated with lead time and offset percents. As with the item
r a
lead time attributes, you can also manually assign these values.
Lead Time Percent
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 20
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.
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.
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 computes manufacturing lead time by forward scheduling two jobs: the first
job is scheduled for a quantity of zero and the second job is scheduled for a quantity equal to
the item’s lead time lot size. The first job determines the fixed lead time and the second job
determines the variable and processing lead times. Using detailed scheduling, fixed and
variable lead times are computed as the difference between the total time required for the two
scheduled jobs.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 21
Lead Time Lot Size
m y
d e
ca
e A
Lead Time Lot Size
c l
Processing lead time is computed as the time required to complete 1 lead time lot size of an
r a
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. O ly
l & On
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.
n a e
t e r U s
If an item’s routing references another item’s routing as a common, set both items’ lead time
lot size to the same value. If you do not specify a lead time lot size, ensure that both items’
I n
standard lot sizes are equal.
For items that you plan with one lot size and cost with a different lot size, you can enter a lead
l e
time lot size. Bills of Material then calculates manufacturing lead time using this value rather
c
than the standard lot size.
r a
If an item does not have a value for the standard or lead time lot size, Bills of Material uses a
quantity of 1 to compute manufacturing lead times.
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 22
If you enter a lead time lot size for an item, consider the item’s planning lot size to accurately
offset lead times. For planned items with a fixed order quantity, set the lead time lot size to the
fixed order quantity. If a planned item has varying lot sizes, assign a lead time lot size that
represents the typical lot size.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 23
Offset Percent
m y
d e
ca
e A
Resource Offsets
c l
Oracle Manufacturing stores the offset percent for each resource on a routing operation as the
r a
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.
O ly
For example, both operations in the previous example for lead time percent require one day
l & On
(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
a e
first resource and 75% for the second resource.
n
t e r U s
You can override offset percentage calculations in the Resource region of the Routing window.
Schedule resources at an operation exactly when they are required. Oracle Capacity uses
resources.
I n
operation and resource offsets, as well as detailed usage information, to plan operation
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 24
Lead Time Percent
m y
d e
ca
e A
Lead Time Percent
c l
Oracle Manufacturing stores the lead time percent for each routing operation as the percent of
r a
manufacturing (processing) lead time required for previous operations, calculated from the
start of a job to the start of an operation.
O ly
For example, if an item’s manufacturing lead time is two days and the primary routing has two
l & On
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%.
a e
You can override lead time percent calculations in the Main region of the Routings window.
n
t e r U s
Schedule material to arrive when an operation requires it.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 25
Fixed and Variable Lead Times
m y
d e
ca
e A
Fixed and Variable Lead Times
c l
Bills of Material computes manufacturing lead time by forward scheduling two jobs: the first
r a
job is scheduled for a quantity of zero and the second job is scheduled for a quantity equal to
the item’s lead time lot size. The first job determines the fixed lead time and the second job
O ly
determines the variable and processing lead times.
l & On
Using detailed scheduling, fixed and variable lead times are computed as the difference
between the total time required for two scheduled jobs. In other words, Bills of Material plots
a e
total time required for a work in process job as a function of order quantity for both order
n
t e r
quantities and computes the slope of the line that the two points define.
s
Bills of Material uses the following formulas to compute fixed and variable lead times:
U
I n
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.
l e
Schedule a job for the lead time lot size beginning on the system date and compute variable
c
lead time (rate) as follows: [(completion date (of all items) - system date) - fixed lead time] /
a
lead time lot size.
r
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 26
Cumulative Manufacturing Lead Time
m y
d e
ca
e A
Cumulative Manufacturing Lead Time
c l
Bills of Material sets an item’s cumulative manufacturing lead time equal to its own
r a
manufacturing lead time plus the maximum value of the cumulative manufacturing lead time
for any component, adjusted for operation offset. The operation offset is the lead time percent
O ly
for the operation where the component is used times the item’s manufacturing lead time (based
on one lead time lot size).
l & On
Purchasing items have no cumulative manufacturing lead time.
a e
Oracle Bills of Material uses the following formula to compute cumulative manufacturing lead
n
t e r
Offset days of any component)].
U s
time: Manufacturing lead time for item + maximum [(Cumulative manufacturing lead time –
time.
I n
Set planning time fences for items based on cumulative manufacturing or cumulative total lead
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 27
Cumulative Total Lead Time
m y
d e
ca
e A
Cumulative Total Lead Time
c l
Bills of Material sets an item’s cumulative total lead time to its own total lead time plus the
r a
maximum value of cumulative total lead time less operation offset for any component.
Operation offset for a component is the lead time percent for the operation where the
O ly
component is used times the item’s manufacturing lead time (based on one lead time lot size).
l & On
Bills of Material calculates cumulative total lead time using the following equation: total lead
time for item + maximum [(cumulative total lead time - offset days) for any component].
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 28
Calculating Lead Times
m y
d e
ca
e A
Calculating Lead Times
c l
You can calculate manufacturing lead times for one item, a range of items, or a category of
r a
items. The calculation updates the lead time attributes of all manufacturing items that you
include, regardless of whether you manually maintain an item’s lead times.
Lead Times By Item Category O ly
l & On
You can limit the items included in the manufacturing lead time calculation by specifying an
item range or item category range when you submit the manufacturing lead time program.
a e
Using item categories, you can segregate the manufactured items whose lead times you
n
t e r s
manually maintain from those items you include in the manufacturing lead time calculation.
You can also limit the parent items included in the cumulative lead time calculations by using
U
item categories.
I n
Re-computing Lead Times
l e
Changes to routing and resource usages can impact an item’s lead times. After each change
c
you make to a routing (adjusting usages, adding operations, and so on), recalculate the
r a
manufacturing lead time for the item.
The Lead Time Calculation Process
O To calculate lead times:
Create Routings
Chapter 6 - Page 29
1. Navigate to the Calculate Lead Times window.
2. Select a Type:
- Request: calculate or roll up lead times without a report.
- Set: calculate lead times and produce either the Bills of Material Structure Report or
the Routing Report.
3. If you selected Set in the previous step, select one of the following: Calculate Cumulative
Lead Times Set GUI: calculates cumulative lead times and produces the Bills of Material
Structure Report or Calculate Manufacturing Lead Times Set GUI: calculates
manufacturing lead times and produces the Routing Report. If you selected Request in the
previous step, select Calculate Manufacturing Lead Times.
4. Indicate a range of items or a specific item.
5. If you chose a specific item, enter the item.
6. Optionally, enter a revision for the item. Enter the date and time to snapshot the bill or
routing. All data effective as of this date and time are included in the calculation.
7. If you chose to calculate lead times for a range of items, enter a beginning and ending
range.
8. If you chose to calculate lead times for a range of items, you may enter a category set to
calculate the lead times of the items associated with this category set. The default is the
category set you defined for your functional area.
9. If you chose to enter a category set, enter a beginning and ending category.
To roll up cumulative lead times:
m y
d e
Changes to the indented bill of material and component lead times can impact a parent item’s
cumulative lead times. After each change made to a bill (adding components, assigning to a
different operation or the item lead times, roll up the cumulative lead times.
1. Navigate to the Calculate Lead Times window.
ca
2. Select Request for the Type.
e A
c l
3. Select Rollup Cumulative Lead Times for the Name.
4. Indicate a range of items or a specific item.
r a
5. If you chose a specific item, enter the item.
O ly
6. Optionally, enter a revision for the item.
l & On
7. Enter the date and time to explode the bill of material.
8. If you chose to roll up cumulative lead times for a range of items, enter a beginning and
ending range.
n a e
e r
9. If you chose to roll up cumulative lead times for a range of items, you may enter a
s
category set to roll up the cumulative lead times of the items associated with this category
t U
set. The default is the category set you defined for your functional area.
I n
10. If you chose to enter a category set, enter a beginning and ending category.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 30
Practice Overview: Defining Routings
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 31
Practice - Defining Routings
Overview
In this practice you will define routings for items ##1000, ##1040, and ##2010.
Assumptions
• Use the Manufacturing and Distribution Manager responsibility to complete this
practice.
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Defining Routings
1. Create a routing for item ##1000 using the table below. For each resource use HR for UOM
and Yes for Schedule.
d eUnits
100 ##PCFINAL Assemble
PC
10 ##Assblr Item .25
c a 4
e
10 ##Tester Item
A .5 1
c l
2.
r a
Create a routing for item ##1040 using the table below. For each resource use HR for UOM
and Yes for Schedule.
O ly
l & On
Operation Department Description Resource Resource Basis Usage Assigned
Sequence
n a e Sequence Name Rate Units
100
t e r
CPU
U s
##PCFINAL Assemble 10 ##Assblr Item .5 4
200 I n Chassis
##PCFINAL Test CPU 10 ##Tester Item 1 1
c l e Chassis
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 32
3. Create a routing for item ##2010 using the table below. For each resource use HR for UOM
and Yes for Schedule.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 33
Solution – Defining Routings
Defining Routings
2. Create a routing for item ##1000 using the table below. For each resource use HR for UOM
and Yes for Schedule.
3. Enter Operation Sequence and Department in the Routings window under the Main tab. m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 34
m y
d e
4. Enter Description under the Description tab in the Routings window.
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 35
m y
d e
5. Select Operation Resources.
ca
• (B) Operation Resources
e A
6.
l
Enter Resource Sequence, Resource Name, UOM, Basis, and Usage Rate under the Main tab
in the Operation Resources window.
c
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 36
m y
7. Enter Assigned Units and Schedule under the Scheduling tab.
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 37
m y
8. Save your work.
d e
9.
a
Return to the Routings window and enter the remaining information for Operation Sequence
200 for item ##1000.
c
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 38
m y
d e
10. Create a routing for item ##1040 using the table below. For each resource use HR for UOM
and Yes for Schedule.
c a
e A
Operation Department Description
Sequence
c l Resource
Sequence
Resource
Name
Basis Usage
Rate
Assigned
Units
100 ##PCFinal
r
Assemble a 10 ##Assblr Item .5 4
CPU
O ly
Chassis
200 ##PCFinal
l & On
Test CPU 10 ##Tester Item 1 1
n a e
Chassis
t e r U s
I n
11. Create a routing for item ##2010 using the table below. For each resource use HR for UOM
and Yes for Schedule.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 39
Operation Department Description Resource Resource Basis Usage Assigned
Sequence Sequence Name Rate Units
100 ##AutoIns Machine 10 ##Inserter Lot 2 1
install
components
20 ##Inserter Item 1 1
200 ##ManAssy Hand install 10 ##Assblr Item .1 10
components
300 ##Test Test 10 ##Tester Item 2 1
motherboard
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 40
Practice Overview: Entering and Calculating Lead Times
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 41
Practice - Entering and Calculating Lead Times
Overview
In this practice you will enter lead times. In addition to entering the lead times, you will also
calculate and review the lead times.
Assumptions
• Use the Manufacturing and Distribution Manager responsibility to complete this
practice.
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Entering Lead Times
1. Enter lead times for your buy items in organization M1 using the following table. ## is your
unique identifier.
m y
Item Number Preprocessing LT Processing LT
e
Postprocessing LT
d
##1010
##1020
5
5
5
5
c a
##1030 5
e
5 A
##2020 5
c l 5 2
##2030
##2040
5
5 r a 5
5
##3010 5 O ly 10 2
##3020 5
l & On 60 1
##3030 5
n a e 5
##3040
t e r 5
U s 30 1
I n
2.
e
Enter lot sizes of 100 pieces for items ##1000, ##1040, and ##2010.
c l
a
Calculating Lead Times
r
O3. Calculate lead times for items ##2010, ##1040, and ##1000.
Create Routings
Chapter 6 - Page 42
4. View the fixed, variable, and processing lead times for items ##2010, ##1040, and ##1000.
7. View the indented bill of material for item ##1000. Review the lead times for the
components.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 43
Solution – Entering and Calculating Lead Times
Entering Lead Times
1. Enter lead times for your buy items in organization M1 using the table below. ## is your
unique identifier.
e
60
A1
##3030
##3040
5
5
c l 5
30 1
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 44
m y
4. Enter lot sizes of 100 pieces for items ##1000, ##1040, and ##2010.
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 45
m y
Calculating Lead Times
d e
5. Calculate lead times for items ##2010, ##1040, and ##1000.
ca
6. Navigate to the Lead Time window.
e A
•
l
(N) Bills of Material > Routings > Lead Times
c
7. Select Single Request and OK.
r a
8. O ly
Select Calculate Manufacturing Lead Times in the LOV for the Request Name.
9.
l & On
Enter specific item ##2010 in the Parameters window.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 46
m y
d e
ca
12. View the fixed, variable, and processing lead times for items ##2010, ##1040, and ##1000.
r a
14. Find the items and select the Lead Time tab to review the lead times.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 47
m y
15. Roll up the cumulative lead time for item ##1000.
d e
16. Navigate to the Lead Time window.
ca
• (N) Bills of Material > Routings > Lead Times
e A
17. Select Single Request and OK.
c l
r a
18. In the Name field, select Rollup Cumulative Lead Times.
Create Routings
Chapter 6 - Page 48
m y
d e
21. View the cumulative lead times for item ##1000. ca
22. Navigate to the Organization Item window.
e A
c l
•
a
Inventory > Items > Organization Items
r
O ly
23. Find item ##1000 and select the Lead Time tab.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 49
m y
24. View the indented bill of material for item ##1000. Review the lead times for the
components.
d e
25. Navigate to the Find Indented Bills of Material window.
ca
•
e
(N) Bills of Material > Bills > Indented Bills A
c l
a
26. Enter item ##1000 and select the Lead Time check box.
r
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 50
m y
27. Select Find.
d e
• (B) Find
ca
28. Review the lead times for the components.
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 51
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 52
Summary
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Create Routings
Chapter 6 - Page 53
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Maintaining Routings
Chapter 7
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 1
Maintaining Routings
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 2
Objectives
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 3
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 4
Routing Revisions
m y
d e
ca
e A
Routing Revisions
c l
A routing revision helps you indicate that the operations and resources of an item have
r a
changed. You do not have to use routing revisions when you change routings. Oracle Bills of
Material date stamp all changes that you make to routings when you increase the revision.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 5
Creating Routing Revisions
m y
d e
ca
e A
Creating Routing Revisions
c l
If you are updating an existing routing, enter the routing revision and the effective date. To
window. r a
update the revision, choose the Routing Revisions button to open the Routing Revisions
O ly
1. Navigate to the Routing Revisions window. You can do this by choosing the Revision
n a e
3. Enter an effective date and time.
t e r U s
The implementation date, which is either the date the revision was added or the date the routing
was transferred from Oracle Engineering, is displayed. If the routing was transferred from
n
Engineering, the ECO text is displayed.
I
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 6
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 7
Standard Operations
m y
d e
ca
e A
Standard Operations
c l
Standard operations are commonly used operations you can define as a template for use in
r a
defining future routing operations. If you assign the operation code of standard operation in a
routing, the standard operation information is copied into the operation you are currently
O ly
defining. You can then modify the operation information in your new operation.
l & On
You must define at least one department before you can define a standard operation.
A standard operation is not the same as a standard bill of material.
n a e
You can also create setup standard operations that are used only when setting up machine type
t e r U s
resources. When defining resource setup information, you have the option of specifying the
standard operations used during changeovers.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 8
Creating Standard Operations
m y
d e
ca
e A
Creating Standard Operations
c l
1. Navigate to the Standard Operations window (N) Routings > Standard Operations.
r a
2. Enter a unique operation code to identify a standard operation. If Oracle Warehouse
Management is installed, the Standard Operations form is used to define which resources
O ly
of a given department are required in order to perform a warehouse task. Oracle
l & On
Warehouse Management refers to standard operations as Task Types. The rules engine
uses the Code defined for the Standard Operation to reference the Task Type. A bulk
a e
picking task may require a forklift machine and a pallet picker manual resource. Oracle
n
e r
Warehouse Management uses a rules based system to determine the task type, or standard
s
operation; each task should be associated with. Tasks of a given type are then dispatched
t U
to users associated with the resource definition, who have the qualified equipment for the
I n
task available to them.
c l e
3. Enter the department where the operation is performed.
4. Enter the minimum transfer quantity of assemblies to move from this operation to the
r a next.
5. For operations in ATO model or option class routings only, indicate whether the
O operation is option dependant, that is, whether the operation is dependant on the choice of
Maintaining Routings
Chapter 7 - Page 9
an optional component. All mandatory components and their related operations appear on
the routing for each configuration. The default is enabled.
6. Select your Count Point and Autocharge options.
7. Indicate whether to backflush components on shop floor moves at this operation. A
backflush transaction automatically pulls Operation pull components from inventory.
Work in Process also pulls all Operation pull components at non-backflush operations
preceding this operation (through the previous completed backflush operation.)
8. To enable operation yield in Shop Floor Management, enter the Operation Yield for each
operation listed. The valid values range between zero and one. This field is displayed for
Shop Floor Management enabled organizations.
9. Indicate whether this operation yield needs to be considered in the cost rollup, as required
by the costing team. This field is displayed for Shop Floor Management enabled
organizations.
10. Choose the Operation Resources button to assign resources to the standard operation.
To Create a Setup Standard Operation
Use a setup standard operation only when specifying the standard operation used during a
changeover in the Changeover Times window. You cannot use a setup standard operation
as a routing operation.
1. Create a setup standard operation the same way you create a standard operation omitting
the steps used to create standard operations for a Shop Floor Management enabled
organization.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 10
Assigning Resources to Standard Operations
m y
d e
ca
e A
Assigning Resources to Standard Operations
c l
1. Navigate to the Resources window (N) Routings > Standard Operations (B) Operation
operation. r a
Resources. Choose the Operation Resources button to assign resources to the standard
O ly
2. Enter the sequence number of the resource and the resource name. You can use any
l & On
resource assigned to the department. Valid values for sequence range from 1 to 9999999
and must be unique for the operation.
a e
3. Select a basis type by which to charge and schedule the resource. The default is the basis
n
t e r s
specified for the resource. Item: Charge and schedule the resource by multiplying the
usage rate by the job or schedule quantity for the assembly. Select Item when your charges
U
I n
fluctuate with quantity change. Lot: Charge and schedule the resource by charging the
usage rate or amount once per job or schedule. Select Lot when your resource usage
c l e
quantity is the amount required per job or schedule, for example, setup charges.
4. Enter a value for the Rate or Amount in either the Usage or Inverse fields. Enter the
r a resource consumed at the operation (per item or per lot) or it’s inverse. Entering a value
for either field updates the other field. Resources with time-based unit of measures must
O have usage rates greater than zero. Enter an inverse when you know the number of units a
Maintaining Routings
Chapter 7 - Page 11
resource can process (rather than the duration an assembly unit consumes the resource).
For example, if you know a resource can process 10 units per hour, enter 10 for the
inverse. Usage or Inverse can be negative only for resources that cannot be scheduled and
where the charge type is neither PO move nor PO receipt.
5. Open the Scheduling tabbed region and enter the Schedule Sequence Number. Two or
more resources can be scheduled to be working concurrently within the same job
operation. Simultaneity is implemented by having more than one resource with the same
Schedule Sequence Number. The Schedule Sequence Number field is independent of the
resource sequence, which is used only as part of the primary key to list the resources. The
Schedule Sequence Number shows the actual sequence of each resource used in the
operation.
6. Optionally, enter the Substitute Group Number. Resources with the same substitute group
number are substituted together with alternate resources that have the same substitute
group number as the operation resource and the same replacement group number.
7. Enter the number of assigned units to the resource.
8. If the unit of measure of the resource is time-based, select a schedule value. When
defining either primary or alternate resources within the same Schedule Sequence
Number, you must set the Schedule field value for the next resource to either Prior or No,
if another resource within the same Schedule Sequence Number has a Schedule field value
of Prior or Next or No, if another resource within the same Schedule Sequence Number
has a Schedule field value of Next.
9. Enter the resource offset percent within this routing. For example, a value of 50 means
that you utilize the resource when the routing is half completed. This value is
m y
automatically calculated when you compute the lead time for the assembly.
d e
resources.
ca
10. Indicate which resource is the principle resource, within a group of simultaneous
A
11. Open the Costing tabbed region and enter an activity to perform when you use the
resource. Use activities to group resource charges for cost reporting. The default is the
e
activity associated with the resource.
c l
r a
12. Indicate whether to charge jobs or schedules based on the standard rate defined for the
resource (default). Off: Use this option if you import charges from an outside labor system
O ly
and want to record actual costs, or to record the labor rate of an employee. On: For outside
processing resources, if you charge a job and repetitive schedule at the standard rate,
account.
l & On
Oracle Purchasing computes any purchase price variance and posts it to the rate variance
n a e
13. Select a charge type. The default is the charge type specified for the resource.
t e r U s
14. Select the Alternates button. Optionally, you can define substitute resources for each
primary resource group defined. This enables you to specify resource sequences that can
I n
replace the primary resource group.
15. Enter the substitute resource name. This is one of the resources that may replace the
l e
resource group.
c
16. Enter the Replacement Group Number. This is used to group substitute resources
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 12
17. Select a basis type by which to charge and schedule the resource. The default is the basis
specified for the resource.
18. Enter a value for the Rate or Amount in either the Usage or Inverse fields. That is, enter
the resource consumed at the operation (per item or per lot) or it’s inverse. Entering a
value for either field updates the other field.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 13
Agenda
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 14
Resource Usage
m y
d e
ca
e A
Resource Usage
c l
You can view the operations and routings that use a particular resource in the Resource Where
Used window.
r a
The Resource Where Used window contains four tabbed regions: Operation Details, Resource
Details, Descriptions, and More. O ly
l & On
The Operation Details tabbed region displays the operation sequence, department, the effective
date range, and the routing in which the resource is used.
n a e
The Resource Details tabbed region displays the resource, the basis type, the usage rate (or
t e r U s
amount) and its inverse, and the number of resource units assigned.
The More tabbed region displays the resource sequence, the activity for the resource, the
n
scheduling type (Yes, No, Prior, Next), and whether this is an engineering routing.
I
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 15
Viewing Resource Usage
m y
d e
ca
e A
Viewing Resource Usage
c l
1. Navigate to the Resource Where Used window (N) Routings > Resource Where Used.
r a
2. Enter the name of the resource for which to view the operation and routing usage.
O ly
3. Enter an effective date. Operation information effective on this date is displayed.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 16
Practice Overview: Defining Standard Operations
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 17
Practice - Defining Standard Operations
Overview
In this practice you will define a standard operation and create an alternate routing.
Assumptions
• Use the Manufacturing and Distribution Manager responsibility to complete this
practice.
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Defining Standard Operations
1. Create a standard operation for the test operation called ##TE using the table below.
Department Resource
Sequence
Description Resource
Name
UOM Basis Usage
Rate
y
Assigned
m
Units
##Test 10 Test
motherboard
##Tester HR Item
a
2
de
1
A c
Defining Alternate Routings
c l e
2. Create an Alternate Name called ##ALT.
r a
3.
O ly
Create an alternate routing using ##ALT for item ##2010 using the table below.
l & On
Department Operation
Sequence
n a e
Description Resource
Sequence
Resource
Name
Usage
Rate
Basis Assigned
Units
##AutoIns 100
t e r U s
Machine
install
10 ##Inserter 2 Lot 1
I n components
c l e
##ManAssy 200 Hand install
20
10
##Inserter
##Assblr
1
.1
Item
Item
1
10
r a components
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 18
4. Add Operation Sequence 300 to your alternate routing for item ##2010. Enter your standard
operation ##TE for Operation Sequence 300.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 19
Solution – Defining Standard Operations
Defining Standard Operations
1. Create a standard operation for the test operation called ##TE using the table below.
3. Enter the Code, Description, and Department in the Standard Operations window.
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r
4. a Select Operation Resources.
Maintaining Routings
Chapter 7 - Page 20
5. Enter Resource Sequence, Resource Name, UOM, Basis, and Usage Rate in the Resources
window under the Main tab.
m y
d e
6. Enter Assigned Units under the Schedule tab.
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 21
7. Save your work.
r a
11. Save your work.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 22
12. Navigate to the Routings window.
m y
13. Create an alternate routing using ##ALT for item ##2010 using the table below.
d e
Operation Department Description Resource Resource Basis
c a
Usage Assigned
Sequence
e
Sequence Name
A Rate Units
100 ##AutoIns Machine
install
c l 10 ##Inserter Lot 2 1
components
r a 20 ##Inserter Item 1 1
200 ##ManAssy O ly
Hand install 10 ##Assblr Item .1 10
& On
components
l
n a e
e r s
14. Add Operation Sequence 300 to your alternate routing for item ##2010. Enter your standard
t U
operation ##TE for Operation Sequence 300. Check the referenced checkbox.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 23
m y
d e
15. Save your work.
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 24
Summary
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Maintaining Routings
Chapter 7 - Page 25
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O