Professional Documents
Culture Documents
Bill of Materials Training Documentation
Bill of Materials Training Documentation
Training Documentation
Table of Contents
Page 1 of 13
Bills Of Materials Features
Users can now switch alternate routing with the existing primary routing. When an alternate routing is
switched to primary, the primary routing becomes an alternate routing automatically.
Note that the item lead time is calculated based on primary routing and the BOM prior to the switch, so
switching routing does not update lead time automatically. At the same token, if an alternate common
routing is defined and had been switched, there is a need to reassign the common routing if required.
Cost roll up and lead time roll up need to be re-performed to get the correct info since switching routing
does not update any item attribute. There is no functionality to switch primary and alternate bom.
In 11i, when you create a work order, you can refer to primary bom and alternate routing.
Page 2 of 13
PREREQS Prerequisites Required
Responsibility: Inventory
We define a Finished Good FG-Maxima. We will be creating Primary and Alternate routings for this. Then
we will test the switch the Alternate routing to Primary routing.
Page 3 of 13
Bom 2 Define Alternate Names
Page 4 of 13
Bom 3 Define Primary & Alternate Routings
We define a Primary routing for item FG-Maxima. Operation”PNT1” is associated with the primary routing.
Page 5 of 13
We define an alternate routing for item FG-Maxima. Here we select out alternate name “Altprim” in the
alternate field. Operation”PNT2” is associated with the alternate routing.
Page 6 of 13
Bom 4 Switch Alternate To Primary Routing
Page 7 of 13
From the TOOLs menu we select “Switch to Primary”
A window comes up where we select the Alternate for primary. Now we hit ‘OK’ and proceed.
Page 8 of 13
When you re query up you will see that alternate routing has become the primary routing. In our example
you can see that now the Alternate routing contains operation “PNT1”.
Page 9 of 13
Create Common Bill Across An Hierarchy
Users can now create a Common BOM across an organization hierarchy. Instead of assigning
one inventory organization at a time, assigning it to an organization hierarchy helps streamline
the process for large and multi-organization installation.
The test case scenario below uses the JDSU Hierarchy as an example in creating Common BOM
across the hierarchy.
We create a bill in Seattle Organization(M1), which contains two components. Now we use the same
hierarchy definition used in Eng1 explained in the Top of this document. We have Vision Operations as
Page 10 of 13
our node and subordinate organization S Seattle organization (M1). For Seattle organization (M1) a.
Boston Manufacturing (M2) and b. Dallas Manufacturing (M3) are the child organizations.
We are in Seattle organization and we say create the common bill across the JDSU Organization
Hierarchy. To do this we select “Create Common Bill” from the tools menu. After that the window pops up
and we select Hierarchy radio button and then we select the JDSU Hierarchy from the LOV. Then we
select ‘OK’ button.
Page 11 of 13
Now change organizations to Boston and Dallas and query up the bill. You will see that the common
BOM is created.
Page 12 of 13
Page 13 of 13