BOM & Engg._ep

R12.x Oracle Bills of Material and Engineering Fundamentals Student Guide

D59871GC10

Edition 1.0

September 2009

D60905

Copyright © 2007, 2009, 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. Restricted Rights Notice 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: U.S. GOVERNMENT RIGHTS The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract. Trademark Notice Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Author

Reena Titus

Technical Contributors and Reviewers

Radhakrishnan Angappan, April Nelson

This book was published using: oracletutor

Copyright © Oracle, 2009. All rights reserved.

R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents i

Table of Contents

Defining Items..................................................................................................................................................1-1 Defining Items ...............................................................................................................................................1-3 Objectives ......................................................................................................................................................1-4 Agenda...........................................................................................................................................................1-5 Manufacturing and Engineering Items ..........................................................................................................1-6 Item Functionality..........................................................................................................................................1-7 Steps to Setup, Define and Maintain Items....................................................................................................1-8 Defining Items ...............................................................................................................................................1-9 Quiz ...............................................................................................................................................................1-10 Master Items ..................................................................................................................................................1-11 Master Item Window.....................................................................................................................................1-14 Agenda...........................................................................................................................................................1-15 Item Templates ..............................................................................................................................................1-16 Available Templates ......................................................................................................................................1-17 User Defined Templates ................................................................................................................................1-19 Item Templates Summary..............................................................................................................................1-20 Quiz ...............................................................................................................................................................1-21 Agenda...........................................................................................................................................................1-23 Item Attribute Controls..................................................................................................................................1-24 Item Defining Attributes................................................................................................................................1-26 Item Statuses and Attributes ..........................................................................................................................1-27 Quiz ...............................................................................................................................................................1-28 Item Attribute Groups....................................................................................................................................1-29 Status Attributes and Functionality ...............................................................................................................1-32 Item Status .....................................................................................................................................................1-34 Item Attribute Relationships..........................................................................................................................1-35 Status Attribute Interdependencies ................................................................................................................1-36 Agenda...........................................................................................................................................................1-38 Organization Assignment and Organization Item..........................................................................................1-39 Item Control Level.........................................................................................................................................1-40 Organization Assignments.............................................................................................................................1-42 Creating and Changing Organization Items...................................................................................................1-43 Agenda...........................................................................................................................................................1-44 Searching Items .............................................................................................................................................1-45 Viewing Search Results.................................................................................................................................1-46 Agenda...........................................................................................................................................................1-47 Viewing Item Information .............................................................................................................................1-48 Viewing Item Revisions ................................................................................................................................1-49 Viewing Item Attributes ................................................................................................................................1-50 Viewing Item Categories ...............................................................................................................................1-51 Agenda...........................................................................................................................................................1-52 Overview of Item Cataloging ........................................................................................................................1-53 Creating Item Catalog Groups .......................................................................................................................1-54 Defining Item Catalog Groups.......................................................................................................................1-55 Defining Descriptive Elements......................................................................................................................1-56 Concatenated Item Descriptions ....................................................................................................................1-58 Defining Aliases ............................................................................................................................................1-60 Summary........................................................................................................................................................1-61

Setting Up Bills of Material and Routings.....................................................................................................2-1 Setting Up Bills of Material and Routings.....................................................................................................2-3 Objectives ......................................................................................................................................................2-4 Agenda...........................................................................................................................................................2-5


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents ii

Using the Workday Calendar.........................................................................................................................2-6 Repeating Workday Patterns .........................................................................................................................2-9 Quiz ...............................................................................................................................................................2-11 Workday Exceptions......................................................................................................................................2-12 Shifts..............................................................................................................................................................2-14 Quiz ...............................................................................................................................................................2-17 Defining Lookups..........................................................................................................................................2-18 Agenda...........................................................................................................................................................2-20 Setup for Items and Bills of Material.............................................................................................................2-21 Key Flexfields ...............................................................................................................................................2-22 Bill of Material Parameters............................................................................................................................2-24 Creating Alternates ........................................................................................................................................2-26 Quiz ...............................................................................................................................................................2-27 Creating Custom Deletion Constraints ..........................................................................................................2-28 Defining Department Classes ........................................................................................................................2-30 Defining Departments....................................................................................................................................2-31 Defining Locations ........................................................................................................................................2-33 Defining Resources........................................................................................................................................2-34 Assigning Resources to Departments ............................................................................................................2-38 Assigning Shifts to Resources .......................................................................................................................2-41 Capacity Changes ..........................................................................................................................................2-42 Associating Competencies for Person type Resources ..................................................................................2-43 Quiz ...............................................................................................................................................................2-45 Defining Capacity Changes ...........................................................................................................................2-46 Bill of Material Profiles .................................................................................................................................2-48 Summary........................................................................................................................................................2-50

Creating Bills of Material ...............................................................................................................................3-1 Creating Bills of Material ..............................................................................................................................3-3 Objectives ......................................................................................................................................................3-4 Agenda...........................................................................................................................................................3-5 Bills of Material Overview ............................................................................................................................3-6 Bills of Material.............................................................................................................................................3-7 Types of Bills of Material..............................................................................................................................3-9 Quiz ...............................................................................................................................................................3-11 Example of BOM ..........................................................................................................................................3-12 Phantom Assembly ........................................................................................................................................3-13 Single Organization Bills of Material ............................................................................................................3-15 Integration......................................................................................................................................................3-16 Quiz ...............................................................................................................................................................3-18 Agenda...........................................................................................................................................................3-20 Standard Bills of Material..............................................................................................................................3-21 Valid Parent/Component Relationships.........................................................................................................3-22 Entering Bills of Material ..............................................................................................................................3-23 Quiz ...............................................................................................................................................................3-27 Bill Details.....................................................................................................................................................3-28 Assigning Descriptive Elements....................................................................................................................3-29 Creating Reference Designators ....................................................................................................................3-30 Assigning Substitute Components .................................................................................................................3-32 Capture Inverse Usage...................................................................................................................................3-34 Agenda...........................................................................................................................................................3-35 Primary and Alternate Bills of Material ........................................................................................................3-36 Alternates.......................................................................................................................................................3-38 Agenda...........................................................................................................................................................3-39 Model/Unit Effectivity Overview..................................................................................................................3-40 Model/Unit Effectivity Rules ........................................................................................................................3-41 Model/Unit Effectivity Setup ........................................................................................................................3-43


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents iii

Model/Unit Effectivity Example ...................................................................................................................3-44 Model/Unit Effectivity Features ....................................................................................................................3-46 Viewing Model/Unit Effectivity....................................................................................................................3-47 Summary........................................................................................................................................................3-48

Creating Customized Bills of Material ..........................................................................................................4-1 Creating Customized Bills of Material ..........................................................................................................4-3 Objectives ......................................................................................................................................................4-4 Agenda...........................................................................................................................................................4-5 Overview .......................................................................................................................................................4-6 Item Attributes...............................................................................................................................................4-7 Quiz ...............................................................................................................................................................4-8 Planning Bills of Material..............................................................................................................................4-9 Quiz ...............................................................................................................................................................4-11 Model Bills of Material .................................................................................................................................4-12 Quiz ...............................................................................................................................................................4-15 Option Class Bills of Material .......................................................................................................................4-16 Option Classes ...............................................................................................................................................4-17 Bill of Material Data......................................................................................................................................4-18 Implicit Rules ................................................................................................................................................4-20 Quiz ...............................................................................................................................................................4-22 Optional .........................................................................................................................................................4-23 Mutually Exclusive........................................................................................................................................4-24 Quantity Minimum and Maximum................................................................................................................4-25 Quantity Cascade...........................................................................................................................................4-26 Bill of Material Example ...............................................................................................................................4-27 Agenda...........................................................................................................................................................4-28 Configure To Order Overview.......................................................................................................................4-29 Configure To Order Models ..........................................................................................................................4-31 Configure To Order Process Flow.................................................................................................................4-32 Configure to Order Environments .................................................................................................................4-33 PTO and ATO BOM Models.........................................................................................................................4-35 Assemble To Order Model ............................................................................................................................4-36 Pick To Order Model.....................................................................................................................................4-37 AutoCreate Configuration Items....................................................................................................................4-38 Deactivating Configuration Items..................................................................................................................4-42 Agenda...........................................................................................................................................................4-44 Product Family Overview..............................................................................................................................4-45 Creating Product Families .............................................................................................................................4-46 Assigning Members to a Product Family ......................................................................................................4-47 Assigning Member Planning Percentages .....................................................................................................4-48 Summary........................................................................................................................................................4-49

Maintaining Bills of Material .........................................................................................................................5-1 Maintaining Bills of Material ........................................................................................................................5-3 Objectives ......................................................................................................................................................5-4 Agenda...........................................................................................................................................................5-5 Bill of Material Revisions..............................................................................................................................5-6 Item Revisions ...............................................................................................................................................5-7 Quiz ...............................................................................................................................................................5-8 Agenda...........................................................................................................................................................5-9 Tools Menu Options ......................................................................................................................................5-10 Quiz ...............................................................................................................................................................5-12 Agenda...........................................................................................................................................................5-13 Find Indented Bills ........................................................................................................................................5-14 Indented Bills of Material..............................................................................................................................5-16 Quiz ...............................................................................................................................................................5-17 Agenda...........................................................................................................................................................5-18


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents iv

Comparing Bills of Material ..........................................................................................................................5-19 Finding Bills to Compare ..............................................................................................................................5-20 Comparing Bill Components .........................................................................................................................5-21 Requesting Bills of Material Comparison Report..........................................................................................5-22 Agenda...........................................................................................................................................................5-23 Common Bills of Material .............................................................................................................................5-24 Creating Common Bills of Material ..............................................................................................................5-26 Common Bills of Material Guidelines...........................................................................................................5-28 Agenda...........................................................................................................................................................5-29 Bill of Material Loops ...................................................................................................................................5-30 Checking for Bill Loops ................................................................................................................................5-31 Quiz ...............................................................................................................................................................5-32 Agenda...........................................................................................................................................................5-33 Finding Item WhereUsed...............................................................................................................................5-34 Viewing Item WhereUsed .............................................................................................................................5-35 Agenda...........................................................................................................................................................5-36 Bill / Component Validation Rules................................................................................................................5-37 Agenda...........................................................................................................................................................5-39 Bills of Material Reports ...............................................................................................................................5-40 Agenda...........................................................................................................................................................5-42 Mass Changing Bills of Material ...................................................................................................................5-43 Entering Mass Changes .................................................................................................................................5-45 Entering Component Mass Changes..............................................................................................................5-47 Agenda...........................................................................................................................................................5-49 E-Records for Bills of Material .....................................................................................................................5-50 Agenda...........................................................................................................................................................5-52 Bills of Material Business Events..................................................................................................................5-53 Summary........................................................................................................................................................5-55

Create Routings ...............................................................................................................................................6-1 Creating Routings ..........................................................................................................................................6-3 Objectives ......................................................................................................................................................6-4 Agenda...........................................................................................................................................................6-5 Routings.........................................................................................................................................................6-6 Primary and Alternate Routings ....................................................................................................................6-7 Routings in Multiple Organizations...............................................................................................................6-8 Quiz ...............................................................................................................................................................6-9 Operations......................................................................................................................................................6-12 Resources.......................................................................................................................................................6-14 Creating Routings ..........................................................................................................................................6-17 Routing Operations........................................................................................................................................6-19 Agenda...........................................................................................................................................................6-21 Lead Time Management Overview ...............................................................................................................6-22 Item Lead Time Attributes.............................................................................................................................6-24 Quiz ...............................................................................................................................................................6-26 Manufacturing Lead Time Computations......................................................................................................6-27 Lead Time Lot Size .......................................................................................................................................6-29 Offset Percent ................................................................................................................................................6-31 Lead Time Percent.........................................................................................................................................6-32 Fixed and Variable Lead Times.....................................................................................................................6-33 Cumulative Manufacturing Lead Time..........................................................................................................6-34 Cumulative Total Lead Time.........................................................................................................................6-35 Calculating Lead Times.................................................................................................................................6-36 Summary........................................................................................................................................................6-38

Maintaining Routings......................................................................................................................................7-1 Maintaining Routings ....................................................................................................................................7-3 Objectives ......................................................................................................................................................7-4


R12. Oracle Bills of Material and Engineering Fundamentals Table of Contents v

Agenda...........................................................................................................................................................7-5 Routing Revisions .........................................................................................................................................7-6 Creating Routing Revisions...........................................................................................................................7-7 Agenda...........................................................................................................................................................7-8 Standard Operations ......................................................................................................................................7-9 Creating Standard Operations........................................................................................................................7-10 Quiz ...............................................................................................................................................................7-12 Assigning Resources to Standard Operations ................................................................................................7-13 Defining Operation Competencies for Standard Operations .........................................................................7-16 Quiz ...............................................................................................................................................................7-18 Agenda...........................................................................................................................................................7-20 Resource Usage .............................................................................................................................................7-21 Viewing Resource Usage...............................................................................................................................7-22 Quiz ...............................................................................................................................................................7-23 Summary........................................................................................................................................................7-24

Common Bills of Material and Routing Functionality .................................................................................8-1 Common Bills of Material and Routing Functionality ..................................................................................8-3 Objectives ......................................................................................................................................................8-4 Agenda...........................................................................................................................................................8-5 Copying Bill and Routing Information..........................................................................................................8-6 Copying Bills of Material ..............................................................................................................................8-7 Copy Bill Window.........................................................................................................................................8-9 Copying Routings ..........................................................................................................................................8-10 Copy Routing Window..................................................................................................................................8-11 Quiz ...............................................................................................................................................................8-12 Agenda...........................................................................................................................................................8-15 Referencing Common Bills and Routings .....................................................................................................8-16 Common Bills of Material .............................................................................................................................8-17 Common Bill Window...................................................................................................................................8-19 Common Routings.........................................................................................................................................8-21 Common Routing Window............................................................................................................................8-22 Agenda...........................................................................................................................................................8-23 Bill and Operation Documents ......................................................................................................................8-24 Defining Bill and Operation Documents .......................................................................................................8-25 Attaching Bill and Operation Documents......................................................................................................8-26 Quiz ...............................................................................................................................................................8-27 Agenda...........................................................................................................................................................8-28 Deleting Items, Bills, Routings, Components, and Operations .....................................................................8-29 Information That You Can Delete .................................................................................................................8-30 Deletion Process ............................................................................................................................................8-31 Deletion Constraints ......................................................................................................................................8-32 Deletion Groups.............................................................................................................................................8-34 Deletion Group Details and Results...............................................................................................................8-37 Delete Items Report .......................................................................................................................................8-39 Agenda...........................................................................................................................................................8-41 Bills of Material and Routing Open Interfaces ..............................................................................................8-42 Importing Bills of Material and Routings......................................................................................................8-43 Summary........................................................................................................................................................8-45

Engineering Overview.....................................................................................................................................9-1 Engineering Overview...................................................................................................................................9-3 Objectives ......................................................................................................................................................9-4 Agenda...........................................................................................................................................................9-5 Engineering Overview...................................................................................................................................9-6 Engineering Bills of Material and Routings ..................................................................................................9-9 Quiz ...............................................................................................................................................................9-11 Transferring or Copying Engineering Items, Bills, and Routings .................................................................9-13


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents vi

Quiz ...............................................................................................................................................................9-15 Summary........................................................................................................................................................9-17

Setting Up Engineering ...................................................................................................................................10-1 Setting Up Oracle Engineering......................................................................................................................10-3 Objectives ......................................................................................................................................................10-4 Agenda...........................................................................................................................................................10-5 Engineering Setup Flowchart ........................................................................................................................10-6 Setup Steps ....................................................................................................................................................10-7 Profile Options...............................................................................................................................................10-9 Quiz ...............................................................................................................................................................10-11 Defining ECO Types .....................................................................................................................................10-13 Defining ECO Autonumbering......................................................................................................................10-15 Quiz ...............................................................................................................................................................10-17 Defining ECO Approval Lists .......................................................................................................................10-18 Defining Material Dispositions......................................................................................................................10-19 Defining ECO Reasons..................................................................................................................................10-20 Defining ECO Priorities ................................................................................................................................10-21 Quiz ...............................................................................................................................................................10-22 Starting the AutoImplement Manager ...........................................................................................................10-23 Summary........................................................................................................................................................10-24

Creating Engineering Change Orders ...........................................................................................................11-1 Creating Engineering Change Orders ............................................................................................................11-3 Objectives ......................................................................................................................................................11-5 Agenda...........................................................................................................................................................11-6 Engineering Change Orders Overview ..........................................................................................................11-7 Revised Items, Components, Operations, and Resources..............................................................................11-9 ECO Access Control......................................................................................................................................11-11 Quiz ...............................................................................................................................................................11-13 Agenda...........................................................................................................................................................11-15 Defining Engineering Change Orders............................................................................................................11-16 Creating an ECO............................................................................................................................................11-18 Viewing ECO Approval Status......................................................................................................................11-20 Rescheduling an ECO or Revised Items........................................................................................................11-21 Changing the ECO Status ..............................................................................................................................11-22 Quiz ...............................................................................................................................................................11-23 Defining Implementation Costs .....................................................................................................................11-24 Defining an ECO Revision ............................................................................................................................11-25 Defining ECO Revised Items ........................................................................................................................11-26 Defining Revised Operations.........................................................................................................................11-29 Defining Revised Resources..........................................................................................................................11-31 Defining Revised Components ......................................................................................................................11-33 Assigning or Deleting Substitute Components ..............................................................................................11-35 Assigning Reference Designators..................................................................................................................11-36 Quiz ...............................................................................................................................................................11-38 Agenda...........................................................................................................................................................11-39 ECO Life Cycle .............................................................................................................................................11-40 ECO Revised Item Statuses ...........................................................................................................................11-42 ECO Approval Statuses .................................................................................................................................11-43 ECO Approvals .............................................................................................................................................11-44 ECO Life Cycle Without Approval ...............................................................................................................11-47 ECO Life Cycle With Approval ....................................................................................................................11-48 ECO Approval with Oracle Workflow ..........................................................................................................11-50 Summary........................................................................................................................................................11-52

Maintaining Engineering Change Orders .....................................................................................................12-1 Maintaining Engineering Change Orders ......................................................................................................12-3


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents vii

Objectives ......................................................................................................................................................12-4 Agenda...........................................................................................................................................................12-5 Implementing ECOs ......................................................................................................................................12-6 Manual Implementation.................................................................................................................................12-8 Automatic Implementation ............................................................................................................................12-9 Quiz ...............................................................................................................................................................12-11 Agenda...........................................................................................................................................................12-12 Viewing ECO Schedules ...............................................................................................................................12-13 Viewing ECO Schedule History....................................................................................................................12-15 Viewing Item Revisions ................................................................................................................................12-16 Viewing Routing Revisions...........................................................................................................................12-17 Quiz ...............................................................................................................................................................12-18 Agenda...........................................................................................................................................................12-19 Engineering Change Order Approval Lists Report........................................................................................12-20 Engineering Change Order Detail Report......................................................................................................12-21 Engineering Change Order Priorities Report.................................................................................................12-23 Engineering Change Order Reasons Report ..................................................................................................12-24 Engineering Change Order Schedule Report.................................................................................................12-25 Engineering Change Order Types Report......................................................................................................12-27 Agenda...........................................................................................................................................................12-28 Attaching Files to ECOs ................................................................................................................................12-29 Transfer to Manufacturing from an ECO ......................................................................................................12-30 Quiz ...............................................................................................................................................................12-32 Copy to Manufacturing from an ECO ...........................................................................................................12-33 Mass Changing ECOs....................................................................................................................................12-35 Canceling ECOs and Revised Items ..............................................................................................................12-36 Purging ECOs................................................................................................................................................12-38 Quiz ...............................................................................................................................................................12-39 Agenda...........................................................................................................................................................12-40 ECO Business Object Interface .....................................................................................................................12-41 ECO Object Interface Features......................................................................................................................12-42 Summary........................................................................................................................................................12-43

Transferring and Copying Engineering Items, Bills, and Routings............................................................13-1 Transferring and Copying Engineering Items, Bills, and Routings ...............................................................13-3 Objectives ......................................................................................................................................................13-4 Agenda...........................................................................................................................................................13-5 Transferring and Copying Product Information ............................................................................................13-6 Transferring Information to Manufacturing...................................................................................................13-7 Copying Information to Manufacturing.........................................................................................................13-9 Quiz ...............................................................................................................................................................13-11 Summary........................................................................................................................................................13-15


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents ix

Preface

Profile

Before You Begin This Course

• Thorough knowledge of Oracle Inventory

• Working experience with Oracle Bills of Material

• Working experience with Oracle Engineering

Prerequisites

• There are no prerequisites for this course.

How This Course Is Organized

R12.x 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.


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents x

Related Publications

Oracle Publications Title Part Number

Oracle Bills of Material User's Guide E13688-02

Oracle Engineering User's Guide E13687-02

Additional Publications

• System release bulletins

• Installation and user’s guides

• Read-me files

• International Oracle User’s Group (IOUG) articles

• Oracle Magazine


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents xi

Typographic Conventions

Typographic Conventions in Text Convention Element Example Bold italic Glossary term (if

there is a glossary) The algorithm inserts the new key.

Caps and lowercase

Buttons, check boxes, triggers, windows

Click the Executable button. Select the Can’t Delete Card check box. Assign a When-Validate-Item trigger to the ORD block. Open the Master Schedule window.

Courier new, case sensitive (default is lowercase)

Code output, directory names, filenames, passwords, pathnames, URLs, user input, usernames

Code output: debug.set (‘I”, 300); Directory: bin (DOS), $FMHOME (UNIX) Filename: Locate the init.ora file. Password: User tiger as your password. Pathname: Open c:\my_docs\projects URL: Go to http://www.oracle.com User input: Enter 300 Username: Log on as scott

Initial cap Graphics labels (unless the term is a proper noun)

Customer address (but Oracle Payables)

Italic Emphasized words and phrases, titles of books and courses, variables

Do not save changes to the database. For further information, see Oracle7 Server SQL Language Reference Manual. Enter [email protected], where user_id is the name of the user.

Quotation marks

Interface elements with long names that have only initial caps; lesson and chapter titles in cross-references

Select “Include a reusable module component” and click Finish. This subject is covered in Unit II, Lesson 3, “Working with Objects.”

Uppercase SQL column names, commands, functions, schemas, table names

Use the SELECT command to view information stored in the LAST_NAME column of the EMP table.

Arrow Menu paths Select File > Save. Brackets Key names Press [Enter]. Commas Key sequences Press and release keys one at a time:

[Alternate], [F], [D] Plus signs Key combinations Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents xii

Typographic Conventions in Code Convention Element Example Caps and lowercase

Oracle Forms triggers

When-Validate-Item

Lowercase Colum n names, table names

SELECT last_name FROM s_emp;

Passwords DROP USER scott IDENTIFIED BY tiger;

PL/SQL objects OG_ACTIVATE_LAYER (OG_GET_LAYER (‘prod_pie_layer’))

Lowercase italic

Syntax variables CREATE ROLE role

Uppercase SQL commands and functions

SELECT userid FROM emp;

Typographic Conventions in Oracle Application Navigation Paths

This course uses simplified navigation paths, such as the following example, to direct you through Oracle Applications.

(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve

This simplified path translates to the following:

1. (N) From the Navigator window, select Invoice then Entry then Invoice Batches Summary.

2. (M) From the menu, select Query then Find.

3. (B) Click the Approve button.

Notations:

(N) = Navigator

(M) = Menu

(T) = Tab

(B) = Button

(I) = Icon

(H) = Hyperlink

(ST) = Sub Tab


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents xiii

Typographical Conventions in Oracle Application Help System Paths

This course uses a “navigation path” convention to represent actions you perform to find pertinent information in the Oracle Applications Help System.

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions:

1. In the navigation frame of the help system window, expand the General Ledger entry.

2. Under the General Ledger entry, expand Journals.

3. Under Journals, select Enter Journals.

4. Review the Enter Journals topic that appears in the document frame of the help system window.


R12.x Oracle Bills of Material and Engineering Fundamentals Table of Contents xiv

Copyright © Oracle Corporation, 2009. All rights reserved.

Defining Items Chapter 1 - Page 1

Defining Items Chapter 1





Defining Items



Objectives



Agenda



Manufacturing and Engineering Items

Manufacturing and Engineering Items

Manufacturing items are used in production and are created in Oracle Inventory. 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 attribute flag is not visible in Oracle Inventory. The windows you use to create engineering and manufacturing items are identical. They differ only in the following ways:

• You create and change engineering items using the Oracle Engineering windows. • 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

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 create a manufacturing item with a different item number.



Item Functionality



Steps to Setup, Define and Maintain Items

Steps to Define and Maintain Items

1. Create the item templates. 2. Use the templates and existing items to define items. 3. Enter values for additional item attributes. 4. Assign a status to the item. 5. Assign categories to the item. 6. Enable the item in other organizations. 7. Update the organizational-level attributes values. 8. Define the item relationships. 9. Search for items. 10. Delete items.



Defining Items

Defining Items

Following are the steps for creating and maintaining items: 1. Create the item templates. 2. Use the templates and existing items to define items. 3. Enter values for additional item attributes. 4. Assign a status to the item. 5. Enable the item in other organizations. 6. Update the organizational-level attributes values.



Quiz

Answer: 1



Master Items

Master Items

There are two ways you can define items from the Master Items window. You can use the 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 Item Folder tab enables you to create an item, apply a default template, and assign the item to an organization all in one window. Much of the information for an item is optional. You define only the information you need to maintain the item. Below is a list of the tabs and fields used to define items. Main:

• Primary Unit of Measure, Dual Control, Secondary, Deviation Factor +, Deviation Factor –, User Item Type, Item Status, Conversions, and Long Description.

Inventory: • Inventory Item, Stockable, Transactable, Revision Control, Reservable, Check Material

Shortage, Lot Expiration (Shelf Life) Control, Shelf Life Days, Lot Control, Starting Lot Prefix, Starting Lot Number, Cycle Count Enabled, Negative Measurement Error, Positive Measurement Error, Serial Generation, Starting Serial Prefix, Starting Serial Number, Lot Status Enabled, Serial Status Enabled, Lot Split Enabled, Lot Merge



Enabled, Lot 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, 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, Dimension Height, Collateral Item, Event, Equipment, Electronic Format, Downloadable, and OM Indivisible.

General Planning: • Inventory Planning Method, Planner, Make or Buy, Min–Max Minimum Quantity, Min–

Max Maximum Quantity, Minimum Order Quantity, Maximum Order Quantity, Order Cost, Carrying Cost Percent, Source Type (Replenishment), Source Organization, Source Subinventory, Safety Stock Method, Safety Stock Bucket Days, Safety Stock Percent, Fixed Order Quantity, Fixed Days Supply, and Fixed Lot Multiplier.

MPS/MRP Planning: • Planning Method, Forecast Control, Exception Set, Pegging, Planned Inventory Point,

Create Supply, Shrinkage Rate, Round Order Quantities, Acceptable Early Days, Repetitive Planning, Overrun Percentage, Acceptable Rate Increase, Acceptable Rate Decrease, Calculate ATP, Reduce MPS, Planning Time Fence, Planning Time Fence Days, Demand Time Fence, Demand Time Fence Days, Release Time Fence, Release Time Fence Days, Substitution Window Type, and Substitution Window Days.



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



Master Item Window

Master Item Window

Create Item: • Item • Description • Item attribute groups • Create item catalog • Assign item to organization • Manage attributes at the master level

Organization Item Window: • Manage attributes at the organization level



Agenda



Item Templates

Templates

Oracle Inventory has several predefined templates that you can use to define and update items 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 may want to define item templates to avoid duplicating effort. You can predefine templates with relatively few attributes enabled because you can apply more than one template to define one item. You can enable attributes and assign them values in each template that you create. When you 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. 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 assigned are retained, and blanks don’t overlay assigned values. The order in which templates are applied is important. Item templates change item attributes consistently.



Available Templates

Available Templates

The following is a list of available templates provided by Oracle: • ATO Model • ATO Option Class • ATO Item • Finished Good • Kit • Outside Processing Item • PTO Model • PTO Option Class • Phantom Item • Planning Item • Purchased • Reference Item • Subassem bly



• Supply Item • Freight • Product Family • Equipm ent



User Defined Templates

User Defined Templates

You can define your own templates using the Item Templates window. The window does not 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 are valid for a given item. If an attribute is not updatable for an item, the value from the template is not applied. If a combination of attributes are invalid, a warning appears when you save the item. To make defining templates easier, you can use the Copy From function on the Tools menu in the Item Templates window. This opens the Copy Template window, where you can copy attributes from one or more attribute groups to a new template. You can also create a hybrid template by copying attributes from multiple templates.



Item Templates Summary

Items Templates

Use this window to create and change item attribute templates. The Open button utilizes existing template information. The New button allows for the entering of a new template.



Quiz

Answer: 1



Quiz

Answer: 1



Agenda



Item Attribute Controls

Item Attribute Controls

Item attributes are information about an item, such as order cost, lead time, and revision control. One of the prerequisites for defining items (and assigning values to item attributes) is setting attribute controls. There are two types of attribute control:

• Control level (Master level vs. Org level): Determines whether you have centralized (Master level) or decentralized (Organization level) control of item attributes. Attributes maintained at the Master level have the same attribute values in each organization in 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 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.

• Status control: Describes whether certain status attributes have default values that appear when you assign a status code to an item, and whether status codes control those attribute values after the defaults are assigned to an item. The status attributes are:

- BOM Allowed - Build in WIP



- Customer Orders Enabled - Internal Orders Enabled - Invoice Enabled - Transactable - Purchasable - Stockable



Item Defining Attributes

Item Defining Attributes

An item defining attribute identifies the nature of an item. What designates an item as an 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 want to; simply set Engineering Item, Purchased, and Purchasable to Yes. 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 Item to Yes, the item is automatically assigned to the default category set for the Inventory functional area.



Item Statuses and Attributes

Item Statuses and Attributes

Status attributes enable and disable the functionality of an item over time. Each status attribute 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. The status attributes are related to the item defining attributes. You cannot enable a status attribute if you do not set the corresponding item defining attribute to Yes.



Quiz

Answer: 1



Item Attribute Groups

Item Attribute Groups

Main: • Primary Unit of Measure, Dual Control, Secondary, Deviation Factor +, Deviation Factor

–, User Item Type, Item Status, Conversions, and Long Description. Inventory:

• Inventory Item, Stockable, Transactable, Revision Control, Reservable, Check Material Shortage, Lot Expiration (Shelf Life) Control, Shelf Life Days, Lot Control, Starting Lot Prefix, Starting Lot Number, Cycle Count Enabled, Negative Measurement Error, Positive Measurement Error, Serial Generation, Starting Serial Prefix, Starting Serial Number, Lot Status Enabled, Serial Status Enabled, Lot Split Enabled, Lot Merge Enabled, Lot 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, 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, Dimension Height, Collateral Item, Event, Equipment, Electronic Format, Downloadable, and OM Indivisible.

General Planning: • Inventory Planning Method, Planner, Make or Buy, Min–Max Minimum Quantity, Min–

Max Maximum Quantity, Minimum Order Quantity, Maximum Order Quantity, Order Cost, Carrying Cost Percent, Source Type (Replenishment), Source Organization, Source Subinventory, Safety Stock Method, Safety Stock Bucket Days, Safety Stock Percent, Fixed Order Quantity, Fixed Days Supply, and Fixed Lot Multiplier.

MPS/MRP Planning: • Planning Method, Forecast Control, Exception Set, Pegging, Planned Inventory Point,

Create Supply, Shrinkage Rate, Round Order Quantities, Acceptable Early Days, Repetitive Planning, Overrun Percentage, Acceptable Rate Increase, Acceptable Rate Decrease, Calculate ATP, Reduce MPS, Planning Time Fence, Planning Time Fence Days, Demand Time Fence, Demand Time Fence Days, Release Time Fence, Release Time Fence Days, Substitution Window Type, and Substitution Window Days.

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



Status Attributes and Functionality



Status Attributes and Functionality



Item Status

Item Status

When defining an item, you can use the item attribute Item Status to control status attribute 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. The values are applied to the status attributes when you choose an Item Status Code when 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 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 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. These statuses become effective on their assigned effective dates. You can view the status history of an item if needed.



Item Attribute Relationships

Item Attribute Relationships

Required Attributes • You must enter a value for the attribute based on the settings for other related attributes.

Interdependent Attributes • You can only enter certain values depending on other attribute values.

Updateable Attributes • You can update values under certain conditions.

Control Level Dependencies • You can update the control level of some attributes only under special conditions and

with certain consequences.



Status Attribute Interdependencies



Status Attribute Interdependencies



Agenda



Organization Assignment and Organization Item

Organization Assignment and Organization Item

You can enable your item in all child organizations under your master organization or you can 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 that are enabled in the organization. For example you can select Reorder Point planning for an item in one child organization and select Min-Max planning for the same item in another child organization.



Item Control Level

Item Control Level

An attribute you maintain at the master level has identical values across all organizations that use the item. An attribute you maintain at the organization level may have different values for each organization that uses it. Some attributes can be maintained at only the Master level or the Organizational Level.

• 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

• For example, suppose you want to ensure that items defined in two organizations are transactable at the same time in both organizations. If you make the item not transactable in one organization, you want the same item to become not transactable in the other organization.

Organization-Level Control



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



Organization Assignments

Organization Assignments

Use this window to enable items in organizations. It is not recommended to check Assign All. There are many times items should not be assigned to an organization.



Creating and Changing Organization Items

Creating and Changing Organization Items

Use this window to create and change item attributes in organizations.



Agenda



Searching Items

Searching Items

You can specify as much or as little criteria as you want.



Viewing Search Results



Agenda



Viewing Item Information



Viewing Item Revisions



Viewing Item Attributes



Viewing Item Categories



Agenda



Overview of Item Cataloging

Overview of Item Cataloging

You can use item cataloging to add descriptive information to items and to partition your Item 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. 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 completely describe items belonging to the group. 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 have a descriptive element called Processing Speed. Possible values for Processing Speed might be 100MHZ, 133MHZ, and so on.



Creating Item Catalog Groups



Defining Item Catalog Groups

Defining Item Catalog Groups

To define an item catalog group: 1. Navigate to the Item Catalog Groups window. 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

description is built beginning with the information entered here. You can choose to use the 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 profile option to Yes.

4. Save your work. To make an item catalog group inactive:

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.

To define descriptive elements for an item catalog group: Select an item catalog group and choose Details.



Defining Descriptive Elements

Defining Descriptive Elements

You can define any number of descriptive elements for an item catalog group. You can also 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 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 Default on for any element you want included in a concatenated description. You create a concatenated description when you assign an item to an item catalog group. To define descriptive elements for an item catalog group:

1. Navigate to the Item Catalog Groups window. 2. Select an item catalog group and choose Details. The Item Catalog Group window

appears. 3. Select the Descriptive Elements tabbed region. 4. Enter a unique sequence number. When you assign an item to a group, the descriptive

elements are presented in the order you define here.



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.



Concatenated Item Descriptions

Concatenated Item Descriptions

When you define descriptive elements for an item catalog group, you specify whether the value 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 item, and assign values to the descriptive elements. You can then create a concatenated item description by choosing the Update Description button. If you choose Update Description, Oracle Inventory concatenates the item catalog group information and overwrites the item description with this new information.

Concatenated Item Description Structure Oracle Inventory builds a concatenated item description by combining segments of catalog 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 profile option. Additional segments consist of the values for descriptive elements that have Description Default turned on. The Item Catalog Flexfield separator is used as a delimiter between each segment of the combined description.



When the description is displayed, the delimiters appear even if data is missing for some of the descriptive elements.



Defining Aliases

Defining Aliases

You can specify any number of aliases for the items that belong to the catalog group. This is 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 for any item catalog group, or you can create new aliases. To define an alias for items in a catalog group:

1. Navigate to the Item Catalog Groups window. 2. Select an item catalog group and choose Details. The Item Catalog Group window

appears. 3. Select the Aliases tabbed region. 4. Enter a unique name. 5. Save your work.



Summary

Please refer to the additional guide for labs and/or demos for this lesson.




Setting Up Bills of Material and Routings Chapter 2 - Page 1

Setting Up Bills of Material and Routings Chapter 2





Setting Up Bills of Material and Routings



Objectives



Agenda



Using the Workday Calendar

Using the Workday Calendar

A workday calendar defines the valid working days for a manufacturing organization and consists of repeating pattern of days on and days off and exceptions to that pattern. This enables you to, for example, designate a normal workday as a scheduled downtime day, or designate a holiday as a workday. You can define one or more workday calendars and assign them to any number of organizations, and any number of organizations can share a calendar. You can specify the start and end dates, and the weekend schedule for each calendar.

Creating Workday Calendars A workday calendar consists of a start date, and end date, and on and off days that follow one or more defined workday patterns. A workday calendar can also include shift information and exception dates, such as holidays or scheduled down time. Use a workday calendar for forecasting and planning material requirements, use shift information for job scheduling, and capacity analysis. 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 relevant if a workday exception and a shift exception overlap.



To assign workday exceptions to a workday calendar or calendar shift, either select them intuitively from the Calendar Dates or Shift Calendar Dates window, or apply them from an existing template, calendar, or shift.

1. Navigate to the Workday Calendar window (N) Setup > Calendars. 2. Enter a name for the workday calendar. 3. Select a quarterly calendar type:

- 4/4/5 Week Pattern: Two four-week periods followed by one five-week period. - 5/4/4 Week Pattern: One five-week period followed by two four-week periods. - Calendar Months: Twelve periods per year based on calendar months. - 13 Periods: Thirteen four-week periods per year. - If you use Oracle Master Scheduling/MRP, choose the 4/4/5 Weekly Pattern or the

5/4/4 Weekly Pattern to report MRP information in weeks and months. Otherwise, if you choose the 13 Periods calendar or Calendar Months, you can only report MRP information in monthly buckets.

4. Enter a date range for the workday calendar. The default end date is four years from the start date. Days on and off are calculated based on the start date and the day of the week. For example, if you want a standard five day workweek to start on 01-JAN, you must enter the start date as the Monday before 01-JAN unless 01-JAN falls on a Monday. Set profile option BOM: Week or Period Start Date, to determine the start date. This profile option works in conjunction with the Workday Calendar.

5. Continue creating the workday calendar by choosing one of the following buttons: - Workday Pattern: Set workdays on or off. - Shifts: Assign shifts to the workday calendar. - Dates: Review your work so far and its effect on the workday calendar. Do this

before you build or rebuild the workday calendar you are now creating. (You can only do this after you have defined a workday pattern.) Once you have created a workday pattern, assigned shifts, assigned workday and shift exceptions, and reviewed your work, you must build the calendar and assign it to an organization.

6. Save your work. Copying Calendars or Shifts

You can copy the entire calendar, including workday patterns, exceptions, and all or none of its specific shift information. Or, you can copy a specific shift, including the workday patterns, exceptions, and shift times. Exactly what is copied depends upon how you navigate to the Copy window:

• From the Workday Calendar, Calendar Dates, and Workday Patterns windows, all workday patterns, all exceptions, and selected shift information are copied.

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

If you copy calendar information to an existing calendar, all new information is appended to the existing calendar; existing information, in other words, is retained.

1. Navigate to the Copy window. Do this by choosing Copy from the Tools menu.



2. If you are copying calendar information, enter the calendar to copy information from and indicate if you want none, all, or specific shift information. If you select a specific shift, enter the shift number. If you are copying shift information, enter the calendar you want to copy the shift information from and the specific shift number.

Reviewing Calendars Navigate to the Calendar Dates window or Shift Calendar Dates window. Do this by choosing the Dates button from either the Workday Calendar or Shifts windows.

Building Workday Calendars Rebuilding an existing workday calendar affects all organizations that reference the same calendar and exception template. Changes to your workday information impacts your material plans, capacity plans, scheduling, and any other function in Oracle Manufacturing that uses the workday calendar. This does not apply if you are building a calendar for the first time.

• From the Tools menu, choose Build or Rebuild.



Repeating Workday Patterns

Repeating Workday Patterns

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

Creating Workday Patterns 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.

2. Enter a sequence number in which the workday patterns are applied when the calendar is built.

3. Enter the number for consecutive workdays on and off. For example, if you want Monday through Friday on and Saturday and Sunday off, enter 5 for Days On and 2 for Days Off.

4. Enter a description for the sequence. Repeat the previous three steps for each workday 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, and then 1 again, and so on. For example, assume that sequence 1 is 5 on and 2 off, and sequence 2 is 4 on and 3 off. The calendar shows 5 on, 2 off, 4 on, and 3 off.

5. Save your work. Doing so ensures that you can view calendar dates.



Quiz

Answer: 1



Workday Exceptions

Workday Exceptions

There are three ways to apply exceptions to the workday calendar: • selecting individual exception days • loading them from an exception template, another calendar, and another calendar shift • copying a set of exceptions from another calendar.

An exception template enables you to create groups of exception dates and apply them to different calendars. You can define multiple workday exception templates that define different holidays and scheduled down times for different organizations. Multiple exception templates can be applied to the same calendar. As each template is applied, new exception dates are added to the exception list for that calendar. Conflicts on a particular date between one template and another are resolved as follows:

• 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

has no effect on the calendar • if the exception off day falls on a non-workday, the exception is copied but is redundant

and has no effect on the calendar



This enables you to define different holidays or scheduled down times, for example, for organizations in different countries. Different organizations can use the same calendar, but apply different exception dates. In addition, you can apply the same exception dates to different organizations. You can optionally define exception templates, lists of exception dates, before you set up your workday calendar. Then when you define your calendar, you can choose an exception template, and apply its exception dates to that calendar.

Creating Workday Exception Templates Exception templates define and group deviations to your workday calendar, such as holidays, downtime, or scheduled maintenance. When defining a workday calendar, specify which days or shifts are on and off. The workday calendar, in combination with the exceptions to it, determines the work pattern for each organization.

1. Navigate to the Exception Templates window (N) Setup > Exception Templates. 2. Enter a unique name for the exception template. 3. Enter a date on which this template becomes inactive. 4. Enter all exception dates, and indicate whether each is an on or off workday.

Selecting Workday or Shift Exceptions 1. Navigate to the Calendar Dates window or Shift Calendar Dates window. Do this by

choosing the Dates button from the Workday Calendar window. 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.

Loading Existing Workday or Shift Exceptions 1. Navigate to the Exceptions window. Do this by choosing the Exception List button from

the Calendar Dates window. 2. Choose the Load button and select whether existing exceptions should be applied from a

template, a calendar, or a shift. - If you select Template, enter a template name. - 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. 3. When finished, choose OK to save your work.



Shifts

Shifts

For a given workday calendar, you can specify any number of shifts. Each shift can have a different weekend schedule and a list of specific work interval start and end times. For both calendars and shifts, you can assign sets of workday exceptions and repeating workday patterns. Shifts inherit workday exceptions and workday patterns from the base calendar. Shift exceptions can either add to or override those of the base calendar. If an exception on the base calendar changes, those shifts that do not have an overriding exception on that date will automatically reflect the change. Those shifts that do have an overriding exception on that date will not reflect the change and must be changed manually if they are to reflect the change in the base calendar. Shift exceptions are applied to a calendar the same way as workday calendar exceptions by selecting individual exception days, by defining exception templates, or by copying a set of exceptions from another shift.

Organizations For each organization, you specify the calendar to use. All scheduling functions use the calendar you specify. Detailed scheduling uses specific resource availability information by



department and shift to schedule resources. Dynamic lead time offsetting, however, uses an organization’s workday calendar and does not consider shift information.

Copying Calendars or Shifts You can copy the entire calendar, including workday patterns, exceptions, and all or none of its specific shift information. Or, you can copy a specific shift, including the workday patterns, exceptions, and shift times. Exactly what is copied depends upon how you navigate to the Copy window:

• From the Workday Calendar, Calendar Dates, and Workday Patterns windows, all workday patterns, all exceptions, and selected shift information are copied.

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

If you copy calendar information to an existing calendar, all new information is appended to the existing calendar; existing information, in other words, is retained.

1. Navigate to the Copy window. Do this by choosing Copy from the Tools menu. 2. If you are copying calendar information, enter the calendar to copy information from and

indicate if you want none, all, or specific shift information. If you select a specific shift, enter the shift number. If you are copying shift information, enter the calendar you want to copy the shift information from and the specific shift number.

Creating Shifts and Shift Times 1. Navigate to the Shifts window. You can do this by choosing the Shifts button from the

Workday Calendar window (N) Setup > Calendars (B) Shifts. 2. Enter a shift number and a description. 3. Choose the Times button to open the Shift Times window. 4. Enter the start and stop times for each shift. You can enter multiple start and stop times,

but the start and stop times for a shift cannot overlap. If you create a shift without first creating a workday pattern, a default workday pattern of 5 days on and 2 days off is created. You can then update that workday pattern.

5. Save your work. Selecting Workday or Shift Exceptions

1. Navigate to the Calendar Dates window or Shift Calendar Dates window. Do this by choosing the Dates button from the Workday Calendar window.

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. Loading Existing Workday or Shift Exceptions

1. Navigate to the Exceptions window. Do this by choosing the Exception List button from the Calendar Dates window.

2. Choose the Load button and select whether existing exceptions should be applied from a template, a calendar, or a shift.

- If you select Template, enter a template name. - 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.

3. When finished, choose OK to save your work.



Quiz

Answer: 1 Additional Information

• Exception templates define and group deviations to your workday calendar, such as holidays, downtime, or scheduled maintenance. When defining a workday calendar, you can specify which days or shifts are on and off. The workday calendar, in combination with the exceptions to it, determines the work pattern for each organization.



Defining Lookups

Defining Lookups

To define Bonus Codes: 1. Navigate to the Shop Floor Manager (N) Routings > Bonus Codes window 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: 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

window that appears. Enter numeric value in the Code field. To define Resource Down Codes: 1. Navigate to the Shop Floor Manager (N) Routings > Resource Down Codes window 2. Enter code, Meaning and Description of code in the Manufacturing > Resource Down

Codes Lookups window that appears. Enter numeric value in the Code field. To define Resource Capacity Change Reasons: 1. Navigate to The Resource Capacity Change Reasons window to define reason codes.



2. You can apply reason codes to the capacity changes when defining exceptions in the Bills of Material window or in the workbench.

Note The Meaning and Description defined for the reason codes in the BOM Lookup windows of

Resource/Scrap/Bonus Downcodes are shown as Code and Description, respectively, in the Standard Operations window (Codes and Exclusion window).



Agenda



Setup for Items and Bills of Material



Key Flexfields

Define the System Items Flexfield

You must design and configure your System Items Flexfield before you can start defining 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. Once you define the structure of your flexfield and any applicable value sets, you must freeze and compile your flexfield definition. All Oracle Applications products that reference items share the System Items Flexfield and support multiple segment implementations. Therefore, if you have already configured this flexfield while setting up another product, you do not need to perform this step.

Define the Item Categories Flexfield 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 segments your flexfield has, how many characters each segment has, and whether you want to validate the values that you assign to the segments. Once you define the structure of your 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.



You can define multiple structures for your Item Categories Flexfield, each structure corresponding to a different category grouping scheme. You can then associate these structures with the categories and category sets you define.

Define the Item Catalog Group Flexfield If you make entries for your items in a standard industry catalog or want to group your items according to certain descriptive elements, you need to configure your Item Catalog Group Flexfield. 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. Once you define the structure of your flexfield and any applicable value sets, you must freeze and compile your flexfield definition. Compiling the flexfield definition enables the Item Catalog Group Flexfield pop–up window. Even if you do not use item cataloging, you must enable at least one segment and compile this flexfield before you can define items.



Bill of Material Parameters

Bill of Material Parameters

Use bill of material parameters to define modes of operation and default values for an organization that affect functions such as bill definition, bill deletion, and assemble-to-order configuration numbering. Define bill of material parameters for each organization in which you use bills or routings. Bill parameters are specific to, and must be defined for, each organization. Doing so ensures access to resource, outside processing, and overhead cost information for certain cost management functions. To define bill of material parameters:

1. Navigate to the Parameters window (N) Setup > Parameters. 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. 3. Enter an inactive status. 4. Enter the numbering segment to use when creating configuration item numbers. 5. Select an automatic or user defined numbering method. A unique configuration item

number is automatically assigned based on the numbering method you select:



- Append Sequence: Appends a sequence number to the item segment you entered for the numbering segment.

- Replace with Sequence: Replace the item segment you entered in the numbering segment with a sequence number.

- Replace with Order, Line Number: Replace the item segment you entered for numbering segment with the sales order and line number.

- User Defined: Allows you to define a numbering scheme that meets your business needs.

6. Select one of the following in the Create Lower Level Supply field: - No (default value) - Auto Created Configuration Items Only - Auto Created Configuration Items and ATO Items

7. Check the Config BOM Creation Allowed box to allow the creation of configuration bills of material in the organization.

8. Check the Include Model/Option Class Items in Lead Time Rollup box to include models and option classes when rolling up cumulative lead times. If you leave this box unchecked, the cumulative lead time calculations are not performed for model or option classes.

9. If you would like Work in Process to maintain the individual operation sequence numbers for phantom subassemblies, and to charge their resource and overhead costs to the parent or higher level assembly, you set the following two parameters in Oracle Bills of Material:

- Use Phantom Routings: Set this parameter to specify whether phantom routing resources and overhead costs (including those for outside processing resources assigned to phantom routing operations) are charged to the parent or higher level assembly. Setting this parameter also implies department inheritance for resources; thus, phantom resources can be used by departments that they are not owned by or assigned to as a borrowed resource. You set the parameter at the inventory 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 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 No (this is the default), this value specifies that only components are included in the higher assembly’s cost, not resources and overheads.

- Inherit Phantom Op Seq: Set this parameter to specify whether phantom subassembly components inherit the operation sequence number of their parent or higher level assembly, or maintain their own operation sequence number. This parameter is set at the inventory organization level, and applies to all phantoms within a single inventory organization. The parameter has two values. If you select Yes (this is the default), the phantom subassembly components inherit the operation sequence number of their parent or higher level assemblies. If you select No, phantom subassembly components maintain their own operation sequence numbers.



Creating Alternates

Creating Alternates

An alternate bill describes an alternate list of component items that produce an assembly. An alternate routing describes an alternate manufacturing process that produces an assembly. To create or update an alternate:

1. Navigate to the Alternates window (N) Setup > Alternates. 2. Enter an alphanumeric string to describe a unique alternate. 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.



Quiz


• Bill parameters are specific to, and must be defined for, each organization. Doing so ensures access to resource, outside processing, and overhead cost information for certain cost management functions.



Creating Custom Deletion Constraints

Creating Custom Deletion Constraints

Use custom deletion constraints to enforce specific business rules. Custom deletion constraints prevent the deletion of bills or routings if your data meets the conditions set forth in the constraint. To create a custom deletion constraint:

1. Navigate to the Deletion Constraints window (N) Setup > Delete Constraints. 2. Enter a name for the deletion constraint. 3. Indicate whether the constraint is enabled. An enabled deletion constraint means that it is

in effect when the delete concurrent program runs. 4. Select what kind of delete entity the constraint applies to: item, bill, routing, component, or

operation. 5. Enter the SQL Select Statement that the delete concurrent program is to execute. You

cannot update SQL statements for predefined deletion constraints. 6. Indicate whether to delete if there are rows found or no rows found by the SQL Select

Statement.



7. Enter a failure message from Oracle Application Object Library’s message dictionary to display if the delete fails.



Defining Department Classes

Defining Department Classes

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

1. Navigate to the Department Classes window (N) Setup > Department Classes. 2. Enter text that uniquely describes the department class. For example, you could use ASSY

to group all final assembly departments. 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.

Assign departments to classes when you define departments.



Defining Departments

Defining Departments

A department is an area within your organization that consists of one or more people, 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. 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, you can specify the shifts that the resource is available. For each resource shift, you can also specify capacity modifications that change the available hours per day, units per day, or workdays. To define a department:

1. Navigate to the Departments window (N) Routings > Departments. 2. Enter a name for the department unique for the organization. 3. Optionally, enter a department class. 4. Enter a location for the department. 5. Enter a project expenditure organization.



6. Optionally, enter an inactive date on which you can no longer assign this department to routing operations.

7. Enter the Scrap Account in order to charge the departments that have scrapped material. This field is displayed for Shop Floor Management enabled organizations.

8. Enter the Estimated Absorption Account to estimate the expected scrapped material. This field is displayed for Shop Floor Management enabled organizations that have enabled estimated scrap accounting.

9. Choose the Rates button to view the overhead rates for the department. 10. Choose the Resources button to assign and update resources to the department.

If you have Oracle Warehouse Management installed, the Departments window is used to group resources that may be needed together, to perform tasks. For example, a warehouse may define a refrigerated picking department, which has all the machine and manual resources associated to it that are required to perform a refrigerated picking task. A warehouse can also use a picking department, or a generic task department with all resources associated that are used for warehouse task management.



Defining Locations

Defining Locations

Use the Location window to enter location information. You assign locations to departments that receive deliveries of outside processing items (N) Setup > Locations.



Defining Resources

Defining Resources

Use resources to define the time an assembly spends at an operation and the cost you incur at 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 resource and usage rate for all scheduled activities is required in a routing. Scheduled resources can include queue, setup, run, and move time. When you define your departments, you assign the resources available in each department and the shifts that each resource is available. For each operation you define, you specify a department and list of resources and usages. An operation can use any resource that is available in the department, but you do not need to use all resources assigned to the department. 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 multiple jobs simultaneously, you can prevent a resource from being underutilized. Work scheduled using resource batching is characterized by equivalent work performed with the same manufacturing processes.



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

1. Navigate to the Resources window (N) Routings > Resources. 2. Enter a resource name unique to the organization to describe the resource. For example,

you could assign AS1 to signify assembler grade 1, or WE for welder. 3. Optionally, enter an inactive date after which you can no longer assign this resource. 4. Select a resource type: Amount, Currency (the set of books currency as defined in Oracle

General Ledger), Machine, Miscellaneous, Person, or Physical Space. 5. Enter a unit of measure (UOM) that describes how you measure the resource. You can

update this if the BOM: Update Resource UOM profile option is set to Yes. This field is protected from changes if this resource is used for any operation with the Scheduled field set to Yes, and if you have previously set it as a time-based UOM.

6. Select a charge type. When an operation is completed, Oracle Work in Process records the units applied to the job or repetitive schedule in the resource unit of measure for all resources you charge manually or automatically.

7. Select a basis type by which to charge and schedule the resource. - Item: Charge and schedule the resource where the resource usage quantity is the

amount required per assembly unit you make. - Lot: Charge and schedule the resource where the resource usage quantity is the

amount required per job or schedule. 8. Select an expenditure type for this resource. If the Project Cost Collection Enabled

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 in Process expenditure type class. Expenditure types are defined in Oracle Projects.

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.

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.

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

12. Enable the Costed check box to collect and assign costs to this resource, and if so, optionally enter an activity for the resource. You cannot view costing information if the Privilege To View Cost Information function is excluded from the responsibility. You cannot update costing information if, in addition, the Privilege To Maintain Cost Information function is excluded. You can use activities to group resource charges for cost reporting purposes.



13. If the resource is costed, indicate whether to charge jobs and repetitive schedules based on a standard rate you define. Or, disable Standard Rate to enter a rate to charge the resource in Work in Process for an internal resource, or derive the rate from the purchase order for an outside processing resource. For outside processing resources, if you charge a job or repetitive schedule at the standard rate, a purchase price variance is computed and posted to the rate variance account. If you charge for all other resources, if you charge a job or repetitive schedule at the actual rate, a resource rate variance is computed and posted to the rate variance account.

14. If this resource is costed, enter an absorption account (general ledger account) used to offset resource charges earned in work in process. At period end, you normally compare this account to the resource charges in the general ledger. For outside processing resources, the default is the receiving valuation account from Oracle Purchasing, as defined in the receiving options. For outside processing resources, do not change the default receiving valuation account. When you receive an outside processing purchase order, Oracle Purchasing credits the inventory AP accrual account and debits the receiving valuation account. Bills of Material then debits the work in process outside processing account and credits the receiving valuation account. If you change the above default account, your receiving valuation account will have an incorrect balance.

15. If this resource is costed, enter a variance account (general ledger account) to accumulate resource rate variances for a job or repetitive schedule. For outside processing resources, this is the purchase price variance account.

16. If you have Oracle Manufacturing installed, you can use Resource batching. To enable resource batching, select the Batchable check box in the Batchable region. This enables the other batch fields.

17. Enter the maximum number of units to be batched in the Maximum Batch Capacity field. 18. Enter the minimum number of units to be batched in the Minimum Batch Capacity field 19. Select the unit of measure for the batch capacity from the list of values available in the

Batch UOM window field. 20. Enter the time value for the batching process in the Batching window field. 21. Select the time unit of measure available in the Batching Window UOM field.

To define cost type and resource rate associations: 1. Navigate to the Resource Costs window. Do this by choosing the Rates button from the

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, the Privilege To Maintain Cost Information function is excluded.

2. Enter or select a cost type to associate with each resource overhead rate. 3. Enter the Resource Unit Cost, that is, the resource’s current standard cost per UOM.

To associate overheads with resources: 1. Navigate to the Resource Overhead Associations window. Do this by choosing the

Overheads button from the Resources window. 2. Enter or select the cost type for the resource. The Allow Updates check box indicates

whether the cost type is defined as updatable. 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



frozen unit cost. However, you cannot directly update the frozen unit cost for a previously entered resource.

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

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

2. Enter an Item Number in the Equipment field. 3. Save your work.

If you have Warehouse Management installed, you can use the Resources form to define a class of manual or machine resources. For example, a forklift machine resource is indicated by entering the resource name and description, as well as which equipment items are capable of performing pallet picking. To group employees by resource: You can define the roles that represent what an employee can do for a required task. For example, a role could be defined as Cycle Counter, or a Case Picker.

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

2. Enter an Employee to associate with the resource. 3. Save your work.

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



Assigning Resources to Departments

Assigning Resources to a Department

To assign resources to a department: 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.

2. Enter the resource to assign to the current department. 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. 4. For owned resources, indicate whether this department can share the resource and capacity

with other departments. 5. For borrowed resources, enter the owning department. 6. Enter the number of capacity units (resource units) available for this department, for

example, the number of machines for a machine resource. Each resource can be assigned to any number of departments; multiple resources can be assigned to each department.

7. Optionally, enter a resource group for the resource in this department.



8. Optionally, select the Check CTP check box. The Check CTP check box tells the system to use this resource in a Capable to Promise (CTP) check.

9. Indicate if the department resource should be scheduled to the instance level (specific employee name or piece of equipment). You can only schedule machine type resources by instance, not labor type resources.

10. Optionally, enter an exception set. The exception sets that you assign help identify capacity problems.

11. Enter an expenditure type for the resource. 12. For owned resources that are not available 24 hours, choose the Shifts button to assign

and update shift information for the resource. To define a resource instance: You can optionally de f ne each resource instance (speci f c employee name or piece of equipment) eligible for use. If the resource is a person resource, only certain people may be quali f ed to act as the resource. For example, only certain people are trained to operate a drill press. Before you can specify person resource instances, you must perform the following tasks:

• Optionally, de f ne the person resource skills needed in the Resources window, Skills region.

• Specify the employees that have the necessary skills for the resource. If the resource is an equipment resource, only certain serial-numbered equipment items are usable as the resource. Before you can specify equipment resource instances, you must perform the following tasks:

• Create an equipment item by selecting the Equipment attribute in the Organization Item window, Physical Attributes tab.

• Set up serial number control for the equipment item. • De f ne the equipment item as an equipment type for the resource. 1. Find the resources assigned to a department by navigating to the Departments window,

then choosing Resources. 2. Select a resource, then choose Instances. The Instances window contains different f elds

depending upon whether you select an equipment or person resource. If you select an equipment resource:

3. Enter the equipment item that acts as the resource. 4. Enter the serial number of the speci f c resource instance. Valid serial numbers for the

equipment item appear in the list of values. If you select a person resource:

5. Enter the employee number of the person that acts as the resource. 6. Save your work. The number of resource instances must match the number of units speci

f ed in the Resources window. To assign shift information for the resource:

1. Navigate to the Shifts window. Do this by choosing the Shifts button from the Resources window.



2. Enter a shift number to assign to the resource. The shifts available to assign to the resource are those assigned to the workday calendar assigned to the organization.

3. Choose the Capacity Changes button to define capacity changes for a shift. To define capacity changes: Capacity modifications can add or delete a day, or add or reduce capacity for a shift.

1. Navigate to the Capacity Changes window. Do this by choosing the Capacity Changes button from the Shifts window.

2. Enter or select a simulation set for the capacity change. Use simulation sets for capacity requirements planning in Oracle Capacity.

3. Select the action to take for the department resource: Add: Adds a workday and capacity changes. Delete: Deletes a workday for this department resource. Add or Reduce Capacity: Add or reduce capacity for a resource shift. The capacity

change can fall outside a shift time, so you can add time to a shift. To reduce capacity, enter negative numbers.

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.

5. Enter an effective date and time from which the capacity change starts. If you are adding or reducing capacity, you must also enter a date and time on which the change is no longer in effect. If you are adding a shift’s workday, this is the date of the new workday. If you are deleting a shift’s workday, this is the date of the deleted workday. If you are changing capacity, this is the first day the resource shift’s capacity changes.

6. Select the reason for the resource capacity change from the list of values. 7. Review the Resource Instance Change region for information on the speci f c equipment

capacity changes. Detail Tab: This tab identifies the resource instances impacted by the capacity change. Source Tab: This tab provides detailed information (the downtime source, organization,

work order, and operation) about resource downtime due to scheduled maintenance at the resource instance level.



Assigning Shifts to Resources

Assigning Shifts to Resources

Use the Shifts window to specify resource shifts. 1. Navigate to the Shifts window. Do this by choosing the Shifts button from the Resources

window (N) Routings > Departments (B) Resources (B) Shifts. 2. Enter a shift number to assign to the resource. The shifts available to assign to the resource

are those assigned to the workday calendar assigned to the organization. 3. Choose the Capacity Changes button to define capacity changes for a shift.



Capacity Changes

Capacity Changes

A capacity change is a temporary change to the available capacity of a resource. For example, 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 modifications, the planning and scheduling processes might schedule work on a different day 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 example, a vacation schedule or an end-of-quarter overtime schedule. You can simulate capacity changes by performing a capacity plan using a simulation set.



Associating Competencies for Person type Resources

Defining Competencies for Resources

Defining competencies for a resource enables you to ensure that the operator who handles the manufacturing activities has the right qualifications and required competencies at appropriate skill levels to enable the operator to perform the assigned functions. These requirements ensure that employees understand their duties within the company and are familiar with the industry guidelines and the operator who performs an operation or a quality inspector who performs a quality inspection has the right skills to carry out the assigned functions. This feature, called as the Labor Skills Validation, ensures that the particular operation is carried out by the operator whose skills and competencies have been certified to match the requirements for the operation he or she performs. You can define the competency for a resource while assigning employees to the resources. The competency, skill levels and qualification must match the requirements for the resource. You can only add those resources that meet the requirements to the resource instance. The skill definition of the resource cannot be changed if there are employee instances assigned to the resource.

Defining Competencies for Routings



You can define the competencies required for both standard and non-standard operations and update competencies as required.

Defining Competencies for Standard Operations You can define the competencies of the resource to perform the operation.



Quiz

Answers: 1, 2, 3 Additional Information

• For each resource shift, you can specify capacity modifications that change the available hours per day, units per day, or workdays.



Defining Capacity Changes

Defining Capacity Changes

Use the Capacity Changes window to specify capacity changes. Capacity modifications can add or delete a day, or add or reduce capacity for a shift.

1. Navigate to the Capacity Changes window. Do this by choosing the Capacity Changes button from the Shifts window.

2. Enter or select a simulation set for the capacity change. Use simulation sets for capacity requirements planning in Oracle Capacity.

3. Select the action to take for the department resource: Add: Adds a workday and capacity changes. Delete: Deletes a workday for this department resource. Add or Reduce Capacity: Add or reduce capacity for a resource shift. The capacity

change can fall outside a shift time, so you can add time to a shift. To reduce capacity, enter negative numbers.

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.



5. Enter an effective date and time from which the capacity change starts. If you are adding or reducing capacity, you must also enter a date and time on which the change is no longer in effect. If you are adding a shift’s workday, this is the date of the new workday. If you are deleting a shift’s workday, this is the date of the deleted workday. If you are changing capacity, this is the first day the resource shift’s capacity changes.



Bill of Material Profiles

Bill of Material Profiles

BOM: Automatic Reservations • Indicates whether the system will attempt to automatically reserve existing on hand

inventory after matching a configuration. During Autocreate Configuration, if a match has been found and this profile is set to Yes, CTO will attempt to reserve on hand inventory 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 and reservation performed. If you are using the batch program, the log file provides details of the match and reservations performed.

BOM: Check for Duplicate Configuration • Indicates whether to search for an existing duplicate configuration rather than create a

new item. BOM: Component Item Sequence Increment

• Indicates the value by which to increment the sequence of the component item on the bill. BOM: Configuration Item Delimiter



• Indicates a character used to separate the order and line numbers when you replace the base model’s segment value with the order number/line number.

BOM: Configuration Item Type • Indicates the item type of the new configuration items that the create configuration

program creates. BOM: Default Bill of Material Levels

• Indicates the number of explosion levels to use as a default for bill of material indented explosions.

BOM: Default WIP Supply Values for Components • Indicates whether to default WIP Supply Type, WIP Supply Subinventory, and WIP

Supply Locator from item master for a component item when defining a bill. If set to No, WIP reads the item master.

BOM: Hour UOM • Indicates the unit of measure that represents an hour. You cannot schedule resources

whose unit of measure is not in the same class as the hour unit of measure. BOM: Inherit Option Class Operation Sequence Number

• Indicates whether to allow components on model bills to inherit operation information from parent items.

BOM: Model Item Access • Indicates whether a holder of this responsibility can define and update bills of material

for model and option class items. BOM: Perform Lead Time Calculations

• Indicates whether to perform lead time calculations when you autocreate configuration items.

BOM: Planning Item Access • Indicates whether a holder of this responsibility can define and update bills of material

for planning items. BOM: Standard Item Access

• Indicates whether a holder of this responsibility can define and update bills of material for standard items.

BOM: Update Resource UOM • Indicates whether you can update the resource unit of measure.

BOM: Week or Period Start Day • Indicates whether the workday calendar starts on a weekly or period basis. This profile

option works in conjunction with the Workday Calendar.



Summary



Creating Bills of Material Chapter 3 - Page 1

Creating Bills of Material Chapter 3





Creating Bills of Material



Objectives



Agenda



Bills of Material Overview

Overview of Bills of Material

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



Bills of Material

Specify Components of BOM

Use bills of material to specify the component items that you use to: • Manufacture assemblies and subassemblies (STD) • Configure sales orders (Model) • Explode aggregate forecasts (Planning) • Calculate standard cost (STD)

Engineering and Manufacturing Bills of Material Engineering bills of material are bills of material that your engineering function creates and are not ready for production. Manufacturing bills of material are bills of material that you use in production. You create engineering bills of material in Engineering and you create manufacturing bills of material in Inventory. They differ only in the following ways:

• Engineering bills of material have the check box for the bill of material attribute Engineering preselected.

• Manufacturing bills of material have not preselected the check box for the item attribute Engineering.



The forms that you use to create and change engineering and manufacturing bills of materials are identical. They differ only in the following ways:

• You access them through different navigation paths. • They have different form titles. • You can create and change engineering bills of material using the Oracle Engineering

forms. You can create and change manufacturing bills of material using the Oracle Bills of Material forms.

• You can use engineering and manufacturing items as components in engineering bills of material. You can only use manufacturing items as components in manufacturing bills of material.

• When your engineering bills of material are ready for production, you can transfer or copy them to Oracle Bills of Material as manufacturing bills of material. When you transfer a bill of material, the engineering bill of material becomes a manufacturing bill of material. When you copy a bill of material, the engineering bill of material remains and you create a production bill of material with a different assembly item number.



Types of Bills of Material

Types of Bills of Material Standard Bill of Material

A standard bill of material is the most common type of bill and lists the mandatory components, the required quantity of each component, and information to control work in process, material planning, and other Oracle Manufacturing functions. Examples include bills for manufacturing assemblies, pick-to-order bills, kit bills, and phantoms. A configuration bill (a type of standard bill) is a set of option choices made from a model bill that comprise a buildable, sellable product. Configuration items and bills are automatically created from model bills after a customer chooses options on a sales order. Or, you can manually create configuration bills by choosing options directly from a model bill.

Model Bill of Material A model bill of material defines the list of options and option classes you can choose in Oracle Order Management to order a configuration. A model bill also specifies mandatory components or included items that are required for each configuration of that model. You do not order or build the model itself: you order and build configurations of the model. A model bill can be either assemble-to-order or pick-to-order.

Option Class Bill of Material



An option class is an item that groups optional components on a bill. An option class is an item that becomes a level in your model bill of material. Option classes can also have mandatory components that apply for all of its options. For example, when you order a computer, the monitor is an option class, and the specific type of monitor you order is an option within that option class. An option class bill can be either assemble-to-order or pick-to-order.

Planning Bill of Material A planning bill of material is a bill of material structure that includes a percentage distribution for its components. The percentages associated with the components on a planning bill of material do not need to add to 100%. You can define alternate and common planning bills, where the bill you reference as a common must be another planning bill. Planning items can be nested within one another any number of times. When you nest planning items, Oracle Master Scheduling explodes forecasts level by level and applies planning percentages at each level.



Quiz

Answer: 1



Example of BOM

Connecting Multiple Bills of Material

The bills of material above shows: • A planning bill of material for Italian foods containing items pizza and calzone as

components • Two model bills of material for pizza and calzone (Pizza contains the option class

components sauce and toppings.) • Two option class bills of material for sauce and toppings (Sauce contains standard

components tomato sauce and pesto sauce.) • Two standard bills of material for tomato sauce and pesto sauce (Tomato sauce contains

standard components tomato and oil.)



Phantom Assembly

Phantoms

A phantom assembly is a non-stocked assembly that lets you group together material needed to 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 for one parent item, and a stocked subassembly for another parent item. Oracle Work in Process explodes through a phantom subassembly to the components as if the components were tied directly to the parent assembly. You can define routing for phantoms assemblies the same way as other assemblies. Work in Process ignores phantom assembly routings when you define a job or repetitive schedule. You can compute manufacturing and cumulative lead times for phantom assemblies that have routings. If you do not want to offset the components of a phantom assembly in the planning process, exclude the phantom item from the lead time calculations. In general, phantom assemblies behave like normal assemblies when they represent a top level assembly, such as when you master schedule them or manufacture them using a discrete job. As a subassembly, however, they lose their identity as distinct assemblies and are a collection of their components. The components of the phantom subassembly are included on the job and on the pick list of the job-not the phantom itself.



Oracle Master Scheduling/MRP plans the phantom subassembly using the lot-for-lot lot-sizing technique. Otherwise, the same rules apply to phantoms as for other assemblies. Set the lead time of a phantom to zero to avoid lead time offset during the planning process. When model or option class bills are components to another bill of material, the component supply type is phantom. The cost rollup treats phantom assemblies the same as regular assemblies. The phantom is treated as a distinct entity; the cost elements of the phantom (material, resource, and so on) are added to the cost elements of the higher assembly. Also, the full cost rollup process sets the pending phantom assembly burden to 0.



Single Organization Bills of Material

Single Organization Bills of Material

You create items in the master organization and assign them to the manufacturing and distribution organizations in which you use them. However, you create bills of material in each organization that uses them. Bills of material are always and only single organization entities. You can share the bill of material or copy it across organizations. You could

• Create a bill of material for item A in organization 1 with components item B and item C. • Create a bill of material for item A in organization 2 with components item B and item D.

Create bills of material in the organization that uses them for manufacturing and use the copy bill of material or common bill of material to create them in other organizations that need them.



Integration

Oracle Inventory Integration

You can use items that are defined using Oracle Inventory as both assemblies and components of bills of material.

Oracle Engineering Integration You can use items that are defined using Oracle Engineering as both assemblies and components of engineering bills of material.

Oracle Work In Process Integration When you create discrete jobs and repetitive schedules, Oracle Work In Process bases the pick list on the bill of material of the assembly.

Oracle Purchasing Integration You can purchase engineering items.

Oracle Master Scheduling/MRP and Oracle Supply Chain Planning Integration The requirements explosion passes demand from bill of material assemblies to bill of material components.

Oracle Order Management Integration



When your customer orders configure-to-order items, Oracle Order Management uses bills of material to offer choices. The assemble-to-order processes use model and option class items and bills of material to create configured items and bills of material unique to a sales order line.

Uses in other Oracle Applications Other Oracle manufacturing applications use primary and alternate bills of material in the following ways:

• Oracle material planning uses the primary bill of material when it determines the amount of each item that you need. APS will use alternates to help planning when constraints are encountered.

• When setting the standard cost of a make item, Oracle Cost Management can use the primary bill of material. Costs can be rolled up from the primary or from any selected alternate (it is a roll up parameter).

• When you create discrete jobs and repetitive schedules in Oracle Work in Process, you can specify which bill of material it should use when creating the pick list. If you use an alternate bill of material, you may automatically create a variance.



Quiz


• You can use bills of material to specify the component items that you use to calculate Standard cost.



Quiz

Answer: 1



Agenda



Standard Bills of Material

Creating Standard Bills of Material

Standard bills are bills of material for manufactured products, kits, subassemblies, phantoms, or purchased assemblies. You can order standard items on customer orders and build standard items on discrete jobs and repetitive schedules.

• Select Customer Ordered, Customer Orders Enabled, Internal Ordered, Internal Orders Enabled, and Build WIP in item attributes.

A kit is a standard item that you typically do not build. You pick and ship the components when your customer orders the item.

• Select item attributes Customer Ordered, Customer Orders Enabled, Internal Ordered, and 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 BOM Item Type item attribute value of Standard as components.



Valid Parent/Component Relationships

Components

Bills of Material restricts the types of items you can assign as components based on the type of bill you are defining. The table above lists valid components for each parent item type.



Entering Bills of Material

Creating a Bill of Material

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

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. 2. If you are creating an alternate bill of material, enter the alternate name. You must first

enter alternate names in the Alternates window. If you are creating the primary bill of material, leave this field blank.

3. For model and option class bills of material choose Elements and assign item catalog descriptive elements for the assembly.

Entering Component Bill of Material Information: Main



Item Seq: Defaults from the personal profile value BOM: Component Sequence Item Increment. The item sequence uniquely identifies each component record. Operation Seq: The routing step in which you use the component. If the item has a primary routing, it defaults to the first routing step. If the item does not have a primary routing, it defaults to 1. Use this field if you perform material planning by operation sequence or if you want Oracle Work in Process to lower the inventory balance of discrete job and repetitive schedule components when you backflush at the completion of an operation. A routing must exist before this field can contain meaningful values. Component: The item must have its BOM Allowed item attribute selected. Note the Item Description, Revision, and UOM. Quantity: The amount of the component that you need to make one assembly.

Entering Component Bill of Material Information: Date Effectivity Effectivity Dates From: This is the first date you use the component to make the assembly. Effectivity Dates To: This is the last date that you will use the component to make the assembly. If you leave this field clear, you use this component to make this assembly indefinitely.

Entering Component Bill of Material Information: ECO ECO: Use this field to view an engineering change order number. The Implemented check box indicates whether the component is implemented. Checked: Component is on a pending Engineering Change Order (ECO). Unchecked: Component is on implemented ECO or was added directly to the bill.

Entering Component Bill of Material Information: Component Details Planning %: Master Scheduling/MRP uses component planning percentages in forecast explosions through planning, model, and option class bills of material. Yield: Use for standard bills of material. Enter the percentage by which you want Oracle Material Planning to overplan the component to account for expected loss. The number should represent the percentage of components that will survive the build process. 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.

Entering Component Bill of Material Information: Material Control 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:

• Phantom - Use Phantom to instruct Oracle applications to substitute the components of this item, for the item when working with this item.

• Push - Use when the component should be charged at the beginning of the assembly or 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).

• Operation Pull - Use if you want to decrease component inventory automatically when you complete the routing step in which you use the component. You must have indicated the backflush operation in the Operation Sequence field.

• Assembly Pull - Use if you want to decrease component inventory automatically when you complete a discrete job and repetitive schedule.



• Vendor - Use to indicate that you will not lower the inventory balance because your supplier will provide the material.

• Bulk - Use to indicate that you will not lower the inventory balance because these are expense items.

Subinventory: Use for standard bills of material. Indicate the Subinventory from which you want Push issues to occur and from which you want Pull issues to occur. Enter a value only if you want to override the values in the component item definition. Locator: Use for standard bills of material. Indicate the Locator from which you want Push issues to occur and from which you want Pull issues to occur. Enter this field only if you have indicated that the component is under Locator control and if you want to override the values in the component item definition.

Entering Component Bill of Material Information: Order Management Minimum and Maximum Quantities: Oracle Order Management uses the minimum and maximum quantities to determine the number of optional items available when orders are placed for components on option class bills. If you enter a minimum sales order quantity, you must also enter a maximum sales order quantity. You can only enter a minimum and maximum quantity range that contains the quantity for the component. If you update the component quantity, the minimum and maximum values are changed to include the new component quantity. Check ATP: Check ATP indicates whether to perform an ATP check on the component. The default is enabled if both the parent’s Check Component ATP item attribute is Yes and the component’s Check ATP item attribute is set to Yes. You can update this check box only if all of the following are true:

• Selected the Check ATP attribute of the component item • Selected the Check Component ATP item attribute of the assembly item • Entered a component quantity greater than 0

Mutually Exclusive and Optional Fields: Model and option class bills can have both mandatory and optional components. The Optional field indicates whether the component is mandatory or optional. The Mutually Exclusive field applies only to option class bills and indicates whether you can choose one or many options within an option class. Oracle Order Management uses the Mutually Exclusive check box in combination with the Optional check box to determine the number of option items you can or must choose to order the components of the option class bill. Basis Field: If the component is an option class item, you must indicate whether you want to override the default quantity for the option class when a sales order is entered (the default). Option class quantities affect the mandatory standard components assigned to the option class. If you select None for the Basis field, Oracle Order Management can override the default quantity for the option class. Order Management defaults the total quantity to release as the component quantity multiplied by the option class extended quantity. If you select Option class for the Basis field, Order Management cannot override the default quantity for the option class. Order Management calculates the total quantity to release as the component quantity multiplied by the option class extended quantity.

Entering Component Bill of Material Information: Shipping



Shippable: Select this check box to indicate that the component of a configure-to-order item is shippable. Include on Ship Docs: Select this check box to indicate that the component of configure-to-order item should show on Oracle Order Management documents. Required to Ship: Select this check box to indicate that you must include this component of a pick-to-order item in the first shipment of the pick-to-order item. Required for Revenue: Select this check box to prevent invoicing for the pick-to-order item until you ship this component.

Entering Component Bill of Material Information: Comments Enter your comments in the Comments field to describe how you use the component in the assembly.



Quiz

Answer: 1



Bill Details

Bill Details

Use the Bill Detail window to enter a description of the bill of material or view a specific common bill of material (N) Bills > Bills (B) Bill Details.



Assigning Descriptive Elements

Assigning Descriptive Elements

For each model and option class bills only, you can specify a list of item catalog descriptive 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. For model bills, you must assign the item to a catalog group.

To assign descriptive elements: 1. Navigate to the Descriptive Elements window. Do this by choosing Elements from the

Bills menu option in the Bills of Material window. 2. Enter a descriptive element to assign automatically based on the option chosen in the

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 name from any catalog group. When you order a configuration, Bills of Material automatically creates and assigns the configuration item to the model’s item catalog group, and assigns values to the descriptive elements in this group.



Creating Reference Designators

Using Reference Designators

Reference designators are sequenced comments and instructions that pertain to a component. 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 whether to assign one reference designator for every usage of the component or assign any number of reference designators to the component. Planning bills and model, option class, and planning components cannot have reference designators. Reference designators are sorted in alphanumeric order on inquiries and reports. You can also specify a comment for each reference designator.

Entering Component Bill of Material Information: Reference Designators Qty Related: Select this check box to indicate that you can create only as many reference designators as the usage of the component in the assembly. Reference Designator: Enter the reference designators or choose Add Range to create a range of reference designators automatically.

Creating Reference Designators



1. Navigate to the Reference Designators window. Do this by choosing the Designators button from the Bills of Material window (N) Bills > Bills (B) Designators.

2. Indicate whether you want component quantity related to the number of reference designators.

- Off: Assign any number of reference designators to each component (the default). The number of reference designators is independent of the component quantity. With Quantity Related unchecked, if the usage quantity of the component is four, you could, for example, define six or more reference designators.

- On: Use one reference designator per usage of the component. The component usage quantity must be a positive integer in order for you to use this option. When the bill requires a quantity of four of a given component, you assign four reference designators to that component, one for each usage.

3. Do one of the following: - Enter a reference designator for the component. (A reference designator must be ten

characters or less.) - Choose the Add Range or Delete Range button to open the Range window. Enter a

prefix and a suffix for the range of reference designators to add or delete. For example, if you enter A as the Prefix, 1 and 4 as the starting and ending values, and XYZ as the Suffix; A1XYZ, A2XYZ, A3XYZ, and A4XYZ are the reference designators.

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



Assigning Substitute Components

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 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. Oracle Master Scheduling/MRP reports these substitutes on some planning reports, such as the MRP Detail Report. Oracle Work in Process does not consider substitute items in its pick lists. Planning bills and model, option class, and planning components cannot have substitute components. 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. Quantity: Enter the usage quantity of items that can be substituted for this component.

To assign substitute components:



1. Navigate to the Substitute Components window. Do this by choosing the Substitutes button from the Bills of Material window (N) Bills > Bills (B) Substitutes.

2. Enter a substitute item for the component. If you are using Bills of Material, use a manufacturing item.

3. Enter the quantity of the substitute item needed to replace the full component quantity. This quantity can differ from the bill usage quantity of the component.



Capture Inverse Usage

To capture inverse usage:

1. Navigate to the Bills of Material window. 2. Enter the item number in the Item field. 3. Enter the component name in the Component field. 4. Enter the inverse value of the component in the Inverse Usage field.

After you enter the inverse percentage, the component quantity that you need is displayed 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.



Agenda



Primary and Alternate Bills of Material

Primary and Alternate Bills of Material

A primary bill is a list of the components you most frequently use to build a product. An alternate bill is another list of components for the same basic assembly. The primary bill is the default for rolling up costs, defining a job, and calculating cumulative item lead times. You must define a primary bill before you define an alternate. A primary bill can have many alternate bills. Any bill of material type can have an alternate. Oracle Master Scheduling/MRP uses the primary bill to plan your material. Oracle Order Management uses the primary bill for model and option class products to list available options. When you build an item, roll up costs, and perform other functions that use bills of material, you can specify whether to use the primary bill (the default) or an alternate bill. You can also use engineering change orders to control changes to primary and alternate bills of material. Use alternate bills to account for manufacturing variations that produce the same assembly, by specifying the parent item number and an alternate name when you create a bill. You cannot enter new revisions for alternate bills of material. You can use an alternate to define an engineering bill or routing. The alternate used as a prototype variation from the primary manufacturing bill that produces essentially the same assembly.



Bills and routings can share alternate labels. If you create an alternate bill with the same label as an alternate routing, components are assigned to operations on the alternate routing. If there is no routing with the same alternate label, components are assigned to operations on the primary routing.



Alternates

Alternates

Use this window to create codes for alternate bills of material and for alternate routings. An alternate bill describes an alternate list of component items that produce an assembly. 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 1. Navigate to the Alternates window (N) Setup > Alternates. 2. Enter an alphanumeric string to describe a unique alternate. 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.



Agenda



Model/Unit Effectivity Overview

Model/Unit Effectivity Overview

Model/Unit Effectivity is used in high engineering manufacturing environments such as 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. 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 can now define component effectivity for a range of unit numbers. During planning and production, the system explodes the unit-effective BOMs based on the unit number in the demand. The system also takes unit-effective ECOs into account during these processes. For example, you can use all available components before implementing the ECO. Model/Unit Effectivity is only available when Oracle Project Manufacturing is installed.



Model/Unit Effectivity Rules

Model/Unit Effectivity Rules

You can control the effectivity of changes to bills of material and routings with model/unit 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 and all subsequently produced items, for only one model/unit number of the product family, or 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 products requiring a long lead time. This change can occur at any level in the bill of material structure of the end item. Model/unit effectivity provides many versions of the same end item part number. A model/unit number consists of the alphanumeric prefix for the model/unit number of the end item followed by the specific item number. 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 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 range of model/unit numbers.



You can enter the components as effective for any model/unit number that has been generated using the Generate Model/Unit Numbers concurrent request. It is not necessary that the model/unit number entered on the Bill of Material for an assembly be generated for that assembly.



Model/Unit Effectivity Setup

Model/Unit Effectivity Setup

This slide shows the steps needed to set up model/unit effectivity and the responsibilities for the windows that you will use. The item needs to be defined Serial Controlled on the Inventory page. The item effectivity control needs to be defined Model/Unit Number on the BOM page.

Implementing Considerations for Model/Unit Effectivity 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? • Does your business need to plan, procure, or store by unit number?

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 MDS if necessary. Forecasts are not permitted for a model/unit effectivity item.



Model/Unit Effectivity Example


Unit Effectivity introduces the concept of bills that are effective by an end-item unit number, 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 effectivity. When defining a date-effective BOM all components must be date effective; you cannot have components with unit effectivity. If your parent has model/unit effectivity, you can have date- and unit-effective child components. If your parent has date effectivity, you can only have date-effective child components; you cannot have unit-effective child components.





This example shows the requirements to build Unit 027. You can see the components blocked out are the components needed for units 010–025, units 010–003, and units 001–012. All other components are needed to build Unit 027. Model/unit effectivity allows discrete control over product structure change and less additions 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. The model/unit effectivity feature requires that you have Oracle Project Manufacturing 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 still need to have Oracle Project Manufacturing installed in order to use the feature.



Model/Unit Effectivity Features



Viewing Model/Unit Effectivity

Bills of Material: Viewing Unit Effectivity

Use the Bills of Material window to view your components and ranges of effectivity for the BOM. You can have a quantity of more than 1 for each unit. You would specify quantity on the sales order. Each quantity requires a unique serial number.

Indented Bills of Material: Viewing Unit Effectivity 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 either the date or model/unit From and To values that you have designated for that component.



Summary



Creating Customized Bills of Material Chapter 4 - Page 1

Creating Customized Bills of Material Chapter 4





Creating Customized Bills of Material



Objectives



Agenda



Overview



Item Attributes

BOM Item Type

Verify the assembly's BOM Item Type attribute in the item master specifies the bill of material 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 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 BOM Allowed item attribute, you can use the item as either an assembly or as a component of a bill of material. Before you can select the BOM Allowed item attribute, you must select the Inventory Item attribute.



Quiz

Answer: 1



Planning Bills of Material

Planning Bills of Material

Use planning bills for aggregate forecasting. Planning bills of material specify components that 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 process allocates forecasts of the assembly to the components based on their planning 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 common planning bills, where the bill you reference as a common must be another planning bill. Planning items can be nested within one another any number of times. When you nest planning items, Oracle Master Scheduling explodes forecasts level by level and applies planning percentages at each level. 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 item attribute BOM Item Type value of Planning, Model, Option class, and Standard as components.



Clear item attributes Customer Ordered, Customer Orders Enabled, Internal Orders Enabled, and Build in WIP.



Quiz


• Planning bills of material specify components that belong to the same product line. You can assign planning percentages, as well as quantities per assembly, to the components in proportion to their use in the assembly.



Model Bills of Material


Use model bills of material to specify classes of options from which your customers can choose when they order configurable items. You do not build model assemblies; you assemble a configured item on a final assembly schedule. The configured item has a standard bill of material that contains only the options that the customer selected. Select Customer Ordered, Customer Orders Enabled, Internal Ordered, and Internal Orders Enabled item attributes. Clear the check box for the Build in WIP item attribute. The two types of model bills of material are:

• Pick-to-order: Your customer chooses options, and you pick and ship the components. • Assemble-to-order: Your customer chooses options, and you assemble the components

before shipping. In the example in the slide, each computer is made up of a monitor option class, cpu option class, and an accessories option class.



Each monitor option class is made up of a VGA option class and an EGA option class. The VGA monitor option class has two options, VGA-A and VGA-B, and two components that are always included, the manual and the stand. Use model bills of material for aggregate forecasting. Assign planning percentages to the components in proportion to their use in the model. The forecast explosion process allocates forecasts of the model to the components based on their planning percentages. If the value of the assembly BOM Item Type item attribute is Model, you can use those items with a BOM Item Type item attribute value of Model, Option Class, and Standard as components. Because Oracle Order Management uses model bills of material, you must also define them in the organization designated by profile option OE: Item Validation Organization. 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.





The parent (top level) in a Model bill usually represents a product or service. For example, a Personal Computer system is represented by an item called PC System with the BOM Item Type attribute set to Model. Option Classes, such as Monitor, Keyboard, and so on, are items with the BOM Item Type 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. Optional items can be grouped into Option Classes. For example, the Monitor Option Class can 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 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 check box in the Bills of Material window is not selected.



Quiz

Answer: 1



Option Class Bills of Material

Option Class Bills of Material

Use option class bills of material with model bills of material to specify families of options 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 should clear Customer Ordered, Customer Orders Enabled, Internal Ordered, Internal Orders Enabled, and Build in WIP item attributes. Use option class bills of material for aggregate forecasting. Assign planning percentages to the components in proportion to their use in the assembly. The forecast explosion process allocates 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 with BOM Item Type item attribute value of Model, Option Class, and Standard as components. Since Oracle Order Management uses option class bills of material, you must also define them in the organization designated by profile option OE: Item Validation Organization. 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.



Option Classes

Option Classes

An option class is an element of a Configuration Model. The purpose of option classes is to 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.



Bill of Material Data

Bill of Material Data Planning %

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 Planning uses this percentage to calculate forecasts for the components from forecasts for the product family and model. Use the Planning % field for planning, model, and option class bills of material.

Check ATP 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 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. For example, you might need to check ATP for the keyboard and CPU each time you order 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 Computer and the CPU option class, and you would set the Check ATP Item Master field to



Yes for the Keyboard and CPUs. That way, when you order a Laptop Computer and choose a 486 Processor, Oracle Order Management performs an ATP check for each component in the Laptop Computer bill where Check Component ATP is set to Yes and it would check ATP for the 486 Processor since that option was selected. Oracle supports multiple levels of ATP check components. For example, a standard component of a model could contain a phantom item with ATP check components in its bill. In that case, you would set the ATP Components Item Master field to Yes for both the model and the phantom item. That way, Order Management knows to continue exploding the bill through the phantom item looking for components to include in the group ATP check for the configuration.



Implicit Rules

Implicit Rules

Basic rules are included with Oracle Bills of Material: • Optional or Required • Mutually exclusive • Maximum and minimum quantity • Quantity Cascade

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. For example, whether external speakers are included in an order for a personal computer system is typically an option. In the bill of material the personal computer system, the component item named Speakers is marked as an optional item. An example of a required item 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 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.



An example of a minimum and maximum quantity rule is that a personal computer must have at least one, and not more than four, RAM chips installed. The quantity cascade rule serves as a multiplier in BOM explosion calculations. For example, one automobile wheel requires 5 lug nuts. One automobile requires 4 wheels and therefore 20 lug nuts. Three automobiles require 3 * 4 * 5 = 60 lug nuts.



Quiz

Answer: 1



Optional



Mutually Exclusive

Mutually Exclusive

Used with model and option class bills of material. This component applies if you have taken one of these actions:

• Selected both Mutually Exclusive and Optional, a customer placing a customer order can choose no options or choose one, and only one, option.

• Selected Mutually Exclusive and cleared Optional, a customer placing a customer order must choose one option only.

• Cleared Mutually Exclusive and selected Optional, a customer placing a customer order can choose no options or any number of options.

• Cleared both Mutually Exclusive and Optional, a customer placing a customer order can choose any number of options, but must choose at least one option.



Quantity Minimum and Maximum



Quantity Cascade



Bill of Material Example

Bill of Material Example

Required, mutually exclusive: An ice cream sundae model requires ice cream, but you can only pick one flavor per sundae. 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. Required: You must pick a topping, but you can pick one, some, or all. Optional: You can have a cherry, if you want, but the sundae configuration will be complete without a cherry. 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 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 when the user chooses chocolate ice cream.



Agenda



Configure To Order Overview

Configure To Order Overview

Oracle Manufacturing enables you to define options available for products and to process orders for unique product configurations while maintaining control of inventory, planning, and cost accounting. A Configure to Order environment is one where the product or service is assembled or kitted 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, production, shipping, and financial accounting. Assemble–to–Order Model (ATO Configuration):

• Model bill of material with optional items and option selection rules • Configuration manufactured from mandatory components and selected options, or

purchased from a supplier Assemble-to-Order Item:

• Standard bill of material with mandatory standard components • Item manufactured from mandatory standard components, or purchased from a supplier

Pick-to-Order Model (PTO Configuration):



• Model bill of material with optional items and option selection rules • Pick slip used to kit included items and selected options

Pick-to-Order Item (Kit): • Standard bill of material with mandatory included items • Pick slip used to kit included items

Hybrid: • Pick-to-Order models with optional Assemble-to-Order items • Pick-to-Order model containing Assemble-to-Order model

Multi-Level Assemble-to-Order Model (Multi-Level ATO Configuration): • A model bill of material with a non-phantom model as a component • Configuration manufactured from mandatory components selected options, configured

sub-assemblies, or purchased from a supplier. Multi-Level Assemble-to-Order Items:

• Standard bill of material with standard components and configured components • Item manufactured from standard components and configured components

Multi-Organization Assemble-to-Order Model (Multi-Organization ATO): • An ATO model which will be transferred from another organization.



Configure To Order Models

Configure To Order Models

• ATO example: Final assembly of a custom bicycle based on optional components and 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 assembly process can be tracked to a work order.

• PTO example: Select fruit, cheese, and other produce to create a custom gift basket. PTO costs are not tracked.

• Hybrid example: An ATO Model within a PTO Model, for example, assemble a personal 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 configured personal computer system.

• Pre-configured items example: Using Bills of Material as a hosting application, the Configurator window can be used to construct and maintain pre-configured items for repeat business. For example, a regional transportation district (RTD) repeatedly purchases buses configured to the RTD’s design specifications.



Configure To Order Process Flow



Configure to Order Environments

Configure to Order Environments

You can define model and option class bills of material that list the options your customers can 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 schedules, or purchase orders, you must set the Assemble to Order Item Master field to Yes for the model and option class items. When you assign an option class item to a model or option class bill of material, the component item (option class) must have the same value for the Assemble to Order Item Master field or Pick Components Item Master field as the parent item (model or option class). So, you can only assign assemble to order option classes to assemble to order models and pick-to-order option classes to pick-to-order models. You can also define hybrid model bills where you list some options that you pick and some 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 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 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



included items. Also, an option under a PTO model or option class can be a standard ATO item that requires a manufacturing work order to assemble it, but unlike the ATO model, has no options.



PTO and ATO BOM Models

PTO and ATO BOM Models

A BOM Model is a model that you import from Oracle Bills of Material into Oracle 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 BOM Model in Configurator Developer, but you cannot modify the BOM Model itself or any of its attributes. ATO BOM Models enable you to configure an item online during the order entry process (in OM) and automatically generate a work order in WIP to assemble the resulting item. An ATO Model also enables you to track, at the component level, the costs associated with creating an item. 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 or enable you to track manufacturing costs.



Assemble To Order Model

Assemble To Order Model

After the configured order is submitted: • Inventory: A unique Inventory Item ID is created for the configured end-item. • Bills of Material: A standard bill of material is created for the unique Item ID that lists

the required items and selected options. • Bills of Material: A routing for the configured standard bill of material is created. • 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. • Shipping: The order is picked, shipped, and closed.



Pick To Order Model



AutoCreate Configuration Items

AutoCreate Configuration Items

Once you have entered and scheduled a sales order for an assemble-to-order model, Bills of 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-phantom model in your configuration. These model BOMs and routings are created in the 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 order such that Order Management ships the new item to fulfill the order. Item attributes and sourcing rules for the configuration item are inherited from the base model items.

Steps to AutoCreate Configuration Items Create unique configuration items complete with bills of material and routings (based on the model bill and routing) to fulfill customer orders for manufactured configurations. A cost rollup is performed for each new configuration to establish accurate standard costs that are 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 configuration.



To autocreate configuration items: 1. Navigate to the Submit Requests window. 2. To autocreate a configuration item based on an order number, enter the order number.

Otherwise skip the Sales Order Number field. 3. If you chose not to enter an order number, enter the number of release offset days for the

configuration items. To minimize the impact of order changes, you can delay creating configuration items. You can create configuration items for only those sales orders where the estimated discrete job release date is within the number of days you specify.

4. If you chose not to enter an order number, enter the organization in which you want to autocreate configuration items.

5. Indicate whether to compute the standard lead time for each new configuration item by actually scheduling a test WIP job to be completed on the requirement date. If this is disabled, the default, the configuration item lead time value is derived from the value of the base model.

6. Indicate whether you want to perform flow calculations. If you specify Yes, Total Product Cycle Time, Yield, Net Planning %, and Operation times will be calculated for your processes, operations and events in the configuration flow routing. If you specify No, the data will be copied from the model.

Item Numbering Methods You can choose from four methods to automatically assign item numbers to configuration items:

• Replace model item number with a sequence number • Replace model item number with the order number/line number • Append a sequence to the model number • User defined Configuration Item numbering

For each method, you can specify which segment of the item flexfield you want to either append or replace. For the Order number/line number method, you can specify a delimiter to separate order number and line number.

Match and Reserve Match and Reserve ATO Configurations enable you to check for an existing matching configuration and to reserve against it. While entering an order, you can search for matching 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 items, or auto-created configuration items are matched and used at all levels. You can check for matches from the sales order pad, by choosing the Match action button. You can also match and reserve using the AutoCreate Configuration batch process, accessed from the Assemble To Order submenu, within the BOM responsibility. You can match and reserve 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 whether the match performed uses the standard match function or a custom match function.

Weight and Volume Calculation AutoCreate Configuration Items calculates the weight and volume for the configured item, by rolling up the weight and volume of the components in the OM validation organization. For



Multi level configurations the weight and volume are first calculated for the lowest level configuration and then rolled up until the weight and volume of the top model is determined. The weight and volume are calculated in the unit of measure for the base model. If the unit of measure is not defined on the base model, the system calculates the weight and volume in the base units of the UOM class for one of the components of the model. If the model and options are not all from the same UOM class, the system uses the UOM conversions defined in inventory. If any required UOM conversions have not been defined, the system does not calculate the weight and volume for the configuration.

Resulting Bills of Material Single Level Bill of Material Bills of Material creates the new configuration item and then, if there are no sub-assembly (non-phantom) models in the structure, assigns a single level bill of material with the following components:

• Options from the sales order • Mandatory components of the model and any option class that was included on the sales

order • The Model and each Option Class included on the sales order

The model and option classes appear on configuration bills as phantom components only to consume forecast and to consume master schedules. Material Requirements Planning and Work In Process do not use them since all mandatory components from the model and option classes are also included directly on the single level bill. If you do not forecast or master schedule options and option classes, they perform no function on configuration bills, but they are still included automatically.

Resulting Routings In a discrete environment, Bills of Material automatically assigns a routing to each configuration item by copying the model’s primary routing and then dropping any option dependent routing steps for which no component exists that references that step. Each routing 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 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 had not chosen the 486 processor option. 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 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 If the organization is using a Standard costing method, in a single level environment, a single level Cost Rollup is performed for the configuration item, using the configuration BOM and routing. If the organization is using an Average costing method, the configuration item has zero cost for the Average cost type. 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 schedule relief functions.



Preconfiguring Items You can invoke Oracle Configurator from within Oracle Bills of Material to create a configured bill of material and routing for a pre-defined ATO item. This is very useful in a business to business environment where the same configuration is ordered repeatedly. Preconfigured items can be built to forecast and kept on hand. Customers can order the preconfigured items directly, as they would a standard ATO item. A match is attempted during pre-configuring processing if the profile BOM: Match to Existing Configuration = Yes. If a similar configuration exists, the system gives you a choice to use the existing configuration or to create a new configuration for the pre-defined item. If you choose the existing configuration, the process aborts, and no BOM or Routing is created for the item. If you choose not to use the existing configuration, the system creates a new BOM and Routing for the item, but reuses the lower level matched configurations. The system updates the match tables with the new preconfigured item and BOM, so future matches reflect the new preconfigured item.

Configuration Item Catalog Bills of Material helps you catalog your configurations so you can easily search for a pre-existing configuration item definitions, or on hand configurations. The AutoCreate Configuration Item concurrent program automatically assigns the new configuration item to the same Item Catalog Group as the model and assigns catalog descriptive element values based on the options chosen, depending on how you setup your item catalog and model and option class bills. And, you can specify that certain catalog descriptive elements should become part of the configuration item’s description.



Deactivating Configuration Items

Deactivating Configuration Items

Bills of Material lets you automatically deactivate item numbers associated with completed 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. When you set up Inventory and Bills of Material, you can define an item status to identify 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 item attributes for inactive configuration items:

• BOM allowed • Build in WIP • Transactable • Stockable

When defining bills of material parameters, specify the item status to use for completed configuration items.



You can run the Deactivate Configuration Items concurrent program to automatically deactivate all configuration items that have the following conditions in the organization you run the deactivate program.

• No open demand (sales orders) • No future demand (demand in interface tables) • No open supply (discrete jobs, flow schedules, purchase requisition, or purchase orders) • No material transactions for the number of days ago you specify • Does not exist in a child organization • Does not have a common bill and routing

Each deactivated configuration item has its status updated. BOM components and routing operations are deactivated as well. To deactivate configuration items:

1. Navigate to the Submit Requests window. 2. Select Report and select Deactivate Configuration Items. 3. Enter the organization for which you want to deactivate configuration items that were

completed . 4. Enter the shipped number of days ago. Configuration items with material transaction

within the time frame are evaluated for deactivation. Material transactions include: WIP, Sales Order, and Internal Sales Order. The default number of days is 90.

You can delete item information for completed configurations from the database, including the bills of material and routings. The ability to delete configuration items is subject to the same deletion constraints that operate for other item types as well.



Agenda



Product Family Overview

Product Family Overview

A product family is a grouping of products whose similarity in resource usage, design, and manufacturing process facilitates planning at an aggregate level. A product family cannot be a part of a Standard, Model, Option Class, or Planning Bill of Material. Consequently, a product family is a single level bill. Members of a product family can belong to one and only one product family. You will be able to plan based on the planning percentages and effectivity of the product family members. You may apply the product family template to create your product family consistently. 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%.



Creating Product Families

Creating Product Families

1. Navigate to the Master Item window (N) Inventory > Items > Master Items. If you are a Flow Manufacturing customer, select Product Family from the Flow Manufacturing window. The product family template is automatically applied.

2. Apply the product family template. You are not required to use the product family 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 be Product Family. The item must also be BOM allowed.



Assigning Members to a Product Family

Assigning Members to a Product Family

1. Navigate to the Product Family window (N) Material Planning > Setup > Product Family. 2. Select a product family item. 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 is included in a product family, it will be automatically assigned to the same category as the family item.

4. Commit the record by selecting Save from the File menu. You can commit a record without assigning planning percentages. The default planning percent is 100. The default effectivity date is the system date.



Assigning Member Planning Percentages

Assigning Percentages

1. Navigate to the Product Family window (N) Material Planning > Setup > Product Family. 2. To assign planning percentages for a member item, choose the Allocation button (N)

Material Planning > Setup > Product Family (B) Allocations. 3. Enter the product family member’s planning factor. 4. Enter effectivity dates for the item. Effectivity dates cannot overlap. 5. Optionally, enter comment text. 6. Commit the record by selecting Save from the File menu. You can commit a record

without assigning planning percentages. The default planning percent is 100. The default effectivity date is the system date.



Summary




Maintaining Bills of Material Chapter 5 - Page 1

Maintaining Bills of Material Chapter 5





Maintaining Bills of Material



Objectives



Agenda



Bill of Material Revisions

Bills of Material Revisions

A bill of material revision is an item revision and might indicate that the components of an 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 material. Oracle Engineering and Oracle Bills of Material date stamp and time stamp all changes that you make to bills of material, whether or not you identify the change by increasing the revision. The bill of material revision is the same as the item revision. There is no separate bill of material revision.



Item Revisions

Entering Item Revisions

Define an item revision by entering a revision identifier and effective date (N) Bills > Bills (B) Revision.

• Revision: Enter a new Revision Identifier. You can use up to three alphanumeric characters.

• Effective Date: Enter the date the revision becomes effective.



Quiz

Answer: 1



Agenda



Tools Menu Options

Tools Menu Options

Use the Tools menu to perform the following functions: Copy Bill From

• Use to copy components of another assembly to this assembly. Assign Common Bill

• Use to reference the components of another assembly as the components of this assembly.

Configure Bill • Use to launch the ATO processes.

Check for Loops • Use to check for bill of material loops in the multilevel bill of material for this assembly.

Rollup Costs • Use to calculate the cost of this assembly.

Rollup Lead Times • Use to calculate the lead times for this assembly.



Indented Bills • Use to view the multilevel bill of material for this assembly.

Item Where Used • Use to view assemblies that contain the specified component.

Bill Compare • Use to compare the components of two bills of material.

Routings • Use to enter or view the routing for this assembly.

Find ECO Schedules • Use to view engineering change orders.

View On-Hand Balances • Use to view inventory balances.

Item Details • Use to view item information.

Item Costs • Use to view item costs.



Quiz

Answer: 1



Agenda



Find Indented Bills

Find Indented Bills

Use the Find Indented Bills of Material window to enter parameter information you want to 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:

1. Navigate to the Find Indented Bill of Material window (N) Bills > Indented Bills. 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. 4. Select a Display option: All, Current, or Future and Current components effective as of the

revision date you specify. Use the Implemented Only field to further restrict the components displayed.

5. Select a sort option for each level of the bill, by operation sequence then item sequence, or item sequence then operation sequence.

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 Privilege to View Cost security function must be enabled for the responsibility. Indicate



whether to view lead time and/or material control information, and whether to use planning percents when calculating component quantities. Any field that is checked here causes a corresponding tabbed region to appear on the Indented Bill of Material window.

7. Choose the Find button to explode the bill. The Indented Bill of Material window appears and displays the first level of the bill. The Components window contains the following tabbed regions, some of which may be disabled according the display options you selected: Item Details, Bill Details, Quantities, Effectivity, Material Control, Lead Time, Order Entry, Costing, and Shipping.



Indented Bills of Material

Viewing Indented Bills of Material

Use the Indented Bill of Material window to view an indented bill of material (N) Bills > Indented Bills (B) Find. An indented bill of material is a bill of material that is exploded through many lower levels. You can choose the number of lower levels that you want to see—up to 60—both by setting the personal profile value BOM: Default Bill of Material Levels and by choosing a value when you request the indented bill of material. Item numbers preceded by a plus sign (+) have components; double-click the Item number to view the components. If lower-level components already appear, a minus sign (-) precedes their assembly item number. To remove the components from view, double-click the item number or click the double minus sign -- icon.



Quiz


• An indented manufacturing bill of material displays the structure of a manufacturing item and not the assembly. You can also use the Find Indented Bills of Material window to enter parameter information that you want to view on an indented bill of material.



Agenda



Comparing Bills of Material

Comparing Bills of Material

You can compare any two bills. For example, compare the primary to an alternate bill, the 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.



Finding Bills to Compare

Finding Bills to Compare

Use the Find Bills to Compare window to enter information about two bills of material that you want to compare.

1. Navigate to the Find Bills to Compare window. 2. In the Find Bills to Compare window, enter selection criteria for Bill 1. Do the same for

Bill 2. 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

sequence then item sequence. 5. To view only the differences between bills, check the Differences Only check box. 6. Choose the Compare button to compare the bills online.



Comparing Bill Components

Bill Components Comparison

Use the Bill Components Comparison window to view information about the components of two bills of material (N) Bills > Comparison (B) Compare. The Bill Components Comparison window displays both bills. Two columns of check boxes, one for assembly 1 and one for assembly 2, indicate if the component appears in the assembly. The Main tabbed region displays the item and operation sequences, the planning percent, the quantity, and whether the item is optional. The Effectivity tabbed region displays the effective date range and whether the item is implemented.



Requesting Bills of Material Comparison Report

Bill of Material Comparison Report

Use the Bill of Material Comparison Report to report the comparison between two manufacturing assemblies. You can compare primary bills, manufacturing and engineering bills, alternates, and different revisions. Based on your comparison criteria, if the assemblies have identical components, item sequences, operation sequences, yields, quantities, and implementations, one line is printed for each identical component. Otherwise, the report prints a separate line for each different component. To submit the Bill of Material Comparison Report:

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 supply when comparing bills of material online.

2. Choose Report.



Agenda



Common Bills of Material


If two or more organizations manufacture the same item using the same bill of material, you can define the bill in one organization and reference it from the other organizations. Necessary changes must then be made to the referenced bill. You can create a common bill within the same organization, and across multiple organizations. 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 same item master organization as the current organization and are accessible by the user responsibility. Sharing bills across multiple organizations minimizes the maintenance of your bills of material. 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 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. 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 bill of material.



The following apply to bills of material: • You can only reference bills from organizations that have the same item master

organization as the current organization. • If components already exist for the new bill, you cannot reference another bill as a

common. • If your new assembly is in a different organization than the bill you reference, all

component items must exist in the new bill’s organization. This also applies to substitute components.



Creating Common Bills of Material

Creating Common Bills of Material

To create a common bill: 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.

2. Enter the organization for the item to reference as a common bill. 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: - Single Organization/Organization Hierarchy/All Organizations - Select one of the

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



- Organization Hierarchy. - Organization. - Item .

5. Choose OK. In addition to navigating to the Define Bills window, you can also reference common bills by running the stand alone concurrent program (N) Bills > Create Common Bills.



Common Bills of Material Guidelines

Common Bills of Material Guidelines

Any two items that are of the same bill type can share common bills. If two different items share the same bill, you can define the bill once and then maintain one copy instead of two.



Agenda



Bill of Material Loops

Bill of Material Loops

A bill of material loop is a situation in which a multilevel bill of material contains the same 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 bill of material loop usually fail entirely or refuse to process the multilevel bill of material containing the loop. You can detect bill of material loops by taking these actions:

• Request the Check for Loops concurrent process. • 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.



Checking for Bill Loops

Checking for Bill Loops

The Check for Loops program can be run from the Tools menu of the Bills of Material window. To check for bill loops:

1. Navigate to the Bills of Material window (N) Bills > Bills. Check for Loops on the Tools menu is only available after saving a bill.

2. Choose Check for Loops from the Tools menu (N) Bills > Bills (M) Tools > Check for Loops.



Quiz

Answer: 1



Agenda



Finding Item WhereUsed

Find Item WhereUsed

View an imploded list of all the using assemblies for a specified component. For example, if 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:

1. Navigate to the Find Item Where Used window (N) Bills > Item WhereUsed. 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 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, 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 organization. You have the ability to specify the organization hierarchy name because current organizations can be accessed from more than one organization hierarchy. Use the Implemented Only field to further restrict the components to display.

4. Choose the Find button to open the Item Where Used window.



Viewing Item WhereUsed

Viewing Item WhereUsed

Use the Item WhereUsed window to view the assemblies in which a component appears. 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). The Item Where Used window has three tabbed regions: Item Details, Bill Details, and Effectivity.

• The Item Details tabbed region displays the revision, the type, and the status for the component.

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

Use the control buttons to expand or collapse portions of the indented item usages.



Agenda



Bill / Component Validation Rules

Bill/Component Validation Rules

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

• Depending on the setting of the profiles that limit access to different bill types (BOM: Model Item Access, BOM: Planning Item Access, BOM: Standard Item Access), you may not be able to modify bills.

• You cannot add a component with an operation sequence number that does not exist in the routing. The only exception is for operation sequences that are equal to 1.

• You cannot add a component to a bill where the same component, with the same operation sequence and effectivity, already exists on the bill.

• You cannot add components to common bills. • For ATO, PTO, and phantom bills where the parent item has ATP Components set to No,

you cannot add a component that has either the item attributes Check ATP set to Yes or ATP Components set to Yes.

• You cannot add an optional component to a bill that is neither model or option class.



• You cannot add a component, whose planning percent is not equal to 100, to a standard bill.

• You cannot add a mandatory component, whose planning percent is not equal to 100 and has the Forecast Control attribute set to Consume or None, to a model or option class bill.

• When adding a component to a bill, the mass change will set the Check ATP component attribute to No if the component quantity is less than or equal to 0.



Agenda



Bills of Material Reports

Bill of Material Comparison Report

Use the Bill of Material Comparison Report to report the comparison between two manufacturing assemblies. You can compare primary bills, manufacturing and engineering bills, alternates, and different revisions. Based on your comparison criteria, if the assemblies have identical components, item sequences, operation sequences, yields, quantities, and implementations, one line is printed for each identical component. Otherwise, the report prints a separate line for each different component.

Bill of Material Listing Use the Bill of Material Listing to report manufacturing and engineering bills without any associated component or routing information.

Bill of Material Loop Report Use the Bill of Material Loop Report to check for loops in a bill of material. Bill loops occur when you assign an assembly as a component to itself somewhere in the multilevel structure. You must fix loops before you can run an accurate MRP, or define a discrete job or repetitive schedule for the assembly. If no loop exists, No Data Found is printed on the report.

Bill of Material Structure Report



Use the Bill of Material Structure Report to report the detail for all levels of an engineering or manufacturing bill of material. You can multiply the component usage by an explosion quantity to get an extended quantity.

Bills of Material Parameters Report Use the Bills of Material Parameters Report to report bill of material default parameters. Use these parameters to define modes of operation and default values for Oracle Bills of Material.

Consolidated Bill of Material Report Use the Consolidated Bill of Material Report to summarize component usage at all levels for a manufacturing bill of material.



Agenda



Mass Changing Bills of Material

Mass Changing Bills of Material

Use the Mass Change Bills window to mass change your manufacturing bills of material. You 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 or choose a subset of bills by item range, item category, or item type. You can mass change 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. Bills of Material take into account all the actions you enter to determine if the change is applicable. For example, suppose you add component A and delete component B. This change is made only if component A does not exist and component B does exist on the selected bills. The change is applied only if both conditions are met. In this example, two records are affected. When you make mass changes to bills of material, you can perform the following actions:

• Change information about an existing component. • Add a component. • Replace one component with another.



• Delete a component. • Alter a component quantity or yield.

You cannot make mass changes to a bill of material type—Standard, Option Class, Model, or Planning—if you do not have personal profile permission to change that bill of material type manually.



Entering Mass Changes

Entering Mass Changes

To mass change bills of material: 1. Navigate to the Mass Change Bills window (N) Bills > Mass Changes. 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. 4. Indicate whether to increment the parent item’s revision by 1 (numeric based revisions

only). 5. Indicate whether to update Work in Process material requirements of any unreleased

discrete job, or any release or unreleased repetitive schedule associated with the parent items.

6. Specify the parent items to change. You can use a category set, a category range, or an item range. Alternatively, indicate whether to change all primary bills, all primary and alternate bills, or a specific alternate bill. Optionally, enter a base model to mass change configuration items related to this model that meets your other selection criteria.

7. Enter an item type for the parent items.



8. Choose the Changes button to enter component changes. If you do not wish to replace the values for the Supply Type, Supply Subinventory, and Supply Locator fields, you must enter the current value when executing a mass change. If you leave the Supply Type, Supply Subinventory, and Supply Locator fields blank when entering component changes, their values will be replaced by the blank (null) value when the mass change is executed.

9. When finished, select the action(s) to take. For Bills of Material, select Report (to see affected bills), Implement (to perform the mass change), both, or neither. If you make no selection, the mass change order is saved for you to work on later. You cannot undo a mass change. However, you can create another mass change to reverse the effects of a previous mass change.

10. Choose the Submit button to launch the selected actions.



Entering Component Mass Changes

Entering Component Mass Changes

To enter component changes: 1. Choose the Changes button on the Mass Change Bills window (N) Bills > Mass Changes

(B) Changes. 2. For each component item to change, indicate the action to perform. You can add or delete

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.

3. In the Main tabbed region, enter the item sequence, operation sequence, the quantity, and the inactive date for each component.

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

5. Open the Material Control tabbed region and enter the supply type. Enter the supply subinventory and locator identifiers.



6. For model, option class, and kit bills, open the Order Entry tabbed region and enter the minimum and maximum sales order quantities. Indicate whether to check ATP. Indicate whether the component is optional and mutually exclusive.

7. Open the Shipping tabbed region, and choose whether the component should be listed on shipping documents, required to ship, or required for revenue.



Agenda



E-Records for Bills of Material

Bill Creation or Update

The Bills of Material window starts the signature capturing process whenever a bill is created or 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.

Routing Creation or Update The Routings window starts the signature capturing process whenever a routing is created or updated. While the event is happening in the window, required signatures can be captured online. Select e-Record Details from the Actions menu to view the e-record associated with the routing.

Mass Change Bills The Mass Change Bills window starts the online signature capturing process in different ways, depending on how you access the window:

• If you access the window by navigating to Bills of Materials > Bills > Mass Changes, the online signature capturing process begins once you select the Implement box and choose Submit.



• If you access the window by navigating to Engineering > ECOs > Mass Changes, the online signature capturing process begins once you select the Create ECO box and choose Submit.



Agenda



Bills of Material Business Events

Bills of Material Business Events

Using Oracle Workflow, you can automatically trigger actions based on the following Oracle Bills of Material Business Events:

• Bill of material creation. • Modification to a bill of material header, component or component attribute. • Bill of material deletion. • Error during a bill of material deletion. • Creation or modification of a substitute component, reference designator or component

operation. • Component deletion using a delete group. • Error during a component deletion.

Business Event Examples The following scenarios show how subscribing to a business event can simplify business processes:



A business needs to notify a contract manufacturer each time a bill of material changes. The business can set up Oracle Workflow to automatically send the contract manufacturer an email each time this occurs. A business maintains bills of material in the master organization. Every time a bill of material is created in the master organization, the business needs to copy the bill or create a common bill in the child organizations.



Summary





Create Routings Chapter 6 - Page 1

Create Routings Chapter 6





Creating Routings



Objectives



Agenda



Routings

Routings

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



Primary and Alternate Routings

Primary and Alternate Routings

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



Routings in Multiple Organizations

Routings in Multiple Organizations

You create items in the master organization and assign them to the manufacturing and distribution organizations in which you use them. Within the assigned organization, you create routings. In the example above, the routing for item A in organization 1 has operation step 10 in 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.



Quiz

Answer: 1



Quiz

Answer: 1



Quiz


• You must create resources and departments before creating routings.



Operations

Operations

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

Sequence of Operations 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 assembly. You can use operations to identify the location, the quantity, and the state of 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 operation sequence where you require the item. You can then issue material where and when it is needed.

Standard Operations A standard operation is a commonly used operation that you define as a template to default 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



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.



Resources

Resource Usage

You can associate multiple resources with an operation on a routing. For each resource, you can determine if you want to include that resource in scheduling and lead time calculations. You can also collect costs for a resource on a routing if you specified the resource as a costed resource. Resource parents and resource sets are used to group similar resources. Routings can then be defined with their general resource requirements, while WIP lots are tracked with the usage of the specific resources. While a resource can belong to several resource sets, a resource can only belong to one parent resource. When a WIP lot is at an operation with a parent resource or resource set attached to it, you are prompted to enter a valid resource used in processing the WIP lot.

Item or Lot-Based Resources You can specify resource usage as a fixed rate per job for activities such as setup and teardown, and variable rates for resources whose usage depends on the number of units 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 variable.



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 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. Work in Process schedules assuming that the department uses up to the number of assigned units of the resource simultaneously - up to the number that exist in the department. If you specify that a resource is available 24 hours (such as time in a drying area), Work in Process schedules it around the clock regardless of shifts.

Resource Charging Method You can associate multiple resources with an operation on a routing, and for each resource you can determine how the resource is charged. You can automatically charge resources in Work in 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.

Resource Capacity Modifications For each resource on a shift, you can override the number of resource units available (such as 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 can use later when you generate a capacity plan or schedule discrete jobs or repetitive schedules to simulate capacity changes.

Resource Usage Rate or Amount The usage rate or amount is the amount of the resource consumed at the operation, either the quantity per item or per lot. If you assign more than one resource unit to work at an operation, 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



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.

Labor Skills Validation You can define competencies for a resource to perform a particular operation. Labor Skills Validation ensures that job operations are performed by competent operators who have the required qualifications, competencies and certifications. This prevents potential errors and issues that arise from incompetent operators performing job operations.



Creating Routings

Creating Routings

1. Navigate to the Routings window. 2. Enter a manufacturing item to create a routing for. 3. If you are creating an alternate routing, enter an alternate. For a primary routing, do not

enter an alternate. 4. If you are updating an existing routing, enter the routing revision and the effective date. To

update the revision, choose the Routing Revisions button to open the Routing Revisions window.

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

6. Select a display option to display All, Current, or Future and Current operations effective as of the revision date you specify. To enter completion subinventory and locator information, or view a common routing, choose the Routing Details button to open the Routing Details window.



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 transfer quantity of assemblies to move from this operation to the next. Work in Process 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.

14. Open the Operation Yield tabbed region. You can define routing networks for Standard, 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 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.

15. Indicate whether the operation yield is to be considered in the rollup, as required by the costing team.



Routing Operations

Describing Routing Operations Using Serial Number Tracking at an Operation

You can track items using serial numbers prior to the completed transaction by using the Routing Details button. The Serialization Start Op Seq flag in the Routings window indicates that item tracking with serial numbers begins at the particular operation.

Defining Competencies for Performing Routing Operations You can define competencies for person type resource to perform a particular operation. This

ensures that job operations are performed by competent operators who have the required qualification, skills, and certifications.

1. Navigate to the Routings window. 2. Query on the manufacturing item’s routing. 3. Select the Check Skill check box for the operation sequence for which you would like to

define the competence. Note: Check Skill check box will not be enabled if both Count Point and Auto Charge are not

selected.



4. Click on the Operation Competencies button. Operation Competencies button will be enabled only when you select Check Skill check box.

5. Select the Competence level for the operation sequence. 6. Based on the Competence selected, the skill level values for the selected competence

appear in the drop down menu of the Skill Level field. 7. Enter the skill level. 8. Enter the qualification required for the competence.

Creating or Updating a Routing Revision Using the Routing Revisions button, you can define any number of routing revisions for an

item's routing. Assigning a Resource to a Routing Operation

Using the Operation Resources button, you can assign a resource to a routing operation.



Agenda



Lead Time Management Overview

Lead Time Management Overview

Oracle Manufacturing uses dynamic (quantity dependent) lead times to plan material and resource requirements, and to determine material requirement dates for available to promise (ATP) calculations. When computing requirement dates, both the fixed and variable components of an item’s manufacturing lead time are used. When setting time fences for planning and available to promise calculations, an item’s cumulative lead times are used.

Lead Times Lead times are item, operation, and operation resource attributes that refer to the amount of time you need to obtain or manufacture an item. You can:

• Plan material and resources quickly and accurately. • Establish appropriate planning time fences for products. • Create purchase orders for material, accounting for vendor lead time. • Schedule material to arrive at an operation where it is consumed. • Schedule each resource at an operation where it is consumed. • Promise accurate product shipment dates.



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.



Item Lead Time Attributes

Item Lead Time Attributes

For all scheduled time elements, which are less than the standard workday, the system will 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:

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

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

• Preprocessing Lead Time: A component of total lead time that represents the time required to release a purchase order or create a job from the time you learn of the requirement. You can manually enter preprocessing lead time for both manufactured and purchased items.

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

• Cum ulative 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 level. Bills of Material automatically calculates this value, or you can manually assign a value.



Quiz

Answer: 1



Manufacturing Lead Time Computations

Manufacturing Lead Time Computations

Bills of Material computes manufacturing lead times from item, routing and resource availability information. Item and routing information is updated as part of the computation.

Lead Time Lot Size Processing lead time is computed as the time required to complete 1 lead time lot size of an item (the time required to complete the second scheduled job). Bills of Material determines an item’s lead time lot size from two item master fields: standard lot size and lead time lot size. For items that you plan and cost by the same lot size, you can specify a value only for the standard lot size.

Routings 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 purchased items even if they have a routing. When computing manufacturing lead times, primary routings are automatically updated with lead time and offset percents. As with the item lead time attributes, you can also manually assign these values.

Lead Time Percent



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

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.



Lead Time Lot Size

Lead Time Lot Size

Processing lead time is computed as the time required to complete 1 lead time lot size of an item (the time required to complete the second scheduled job). Bills of Material determines an item’s lead time lot size from two item master fields: standard lot size and lead time lot size. For items that you plan and cost by the same lot size, you can specify a value only for the standard lot size. Bills of Material then computes manufacturing lead time using the standard lot size quantity. 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’ 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 time lot size. Bills of Material then calculates manufacturing lead time using this value rather than the standard lot size. If an item does not have a value for the standard or lead time lot size, Bills of Material uses a quantity of 1 to compute manufacturing lead times.



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.



Offset Percent

Resource Offsets

Oracle Manufacturing stores the offset percent for each resource on a routing operation as the percent of manufacturing (processing) lead time required for previous operations, calculated from the start of the job to the start time of a resource at an operation. For example, both operations in the previous example for lead time percent require one day (eight hours) to perform. If you have two different resources assigned to the second operation, and each resource requires four hours to complete their task, the offset percent is 50% for the first resource and 75% for the second resource. 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 operation and resource offsets, as well as detailed usage information, to plan operation resources.



Lead Time Percent

Lead Time Percent

Oracle Manufacturing stores the lead time percent for each routing operation as the percent of manufacturing (processing) lead time required for previous operations, calculated from the start of a job to the start of an operation. For example, if an item’s manufacturing lead time is two days and the primary routing has two operations with the same duration (1 day), the first operation’s lead time percent is zero and the second operation’s lead time percent is 50%. You can override lead time percent calculations in the Main region of the Routings window. Schedule material to arrive when an operation requires it.



Fixed and Variable Lead Times

Fixed and Variable Lead Times

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 two scheduled jobs. In other words, Bills of Material plots total time required for a work in process job as a function of order quantity for both order quantities and computes the slope of the line that the two points define. Bills of Material uses the following formulas to compute fixed and variable lead times: Schedule a job for zero quantity beginning on the system date and compute fixed lead time as follows: completion date (of one item) - system date. Schedule a job for the lead time lot size beginning on the system date and compute variable lead time (rate) as follows: [(completion date (of all items) - system date) - fixed lead time] / lead time lot size.



Cumulative Manufacturing Lead Time

Cumulative Manufacturing Lead Time

Bills of Material sets an item’s cumulative manufacturing lead time equal to its own 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 for the operation where the component is used times the item’s manufacturing lead time (based on one lead time lot size). Purchasing items have no cumulative manufacturing lead time. Oracle Bills of Material uses the following formula to compute cumulative manufacturing lead time: Manufacturing lead time for item + maximum [(Cumulative manufacturing lead time – Offset days of any component)]. Set planning time fences for items based on cumulative manufacturing or cumulative total lead time.



Cumulative Total Lead Time

Cumulative Total Lead Time

Bills of Material sets an item’s cumulative total lead time to its own total lead time plus the 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 component is used times the item’s manufacturing lead time (based on one lead time lot size). 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].



Calculating Lead Times

Calculating Lead Times

You can calculate manufacturing lead times for one item, a range of items, or a category of 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 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. Using item categories, you can segregate the manufactured items whose lead times you 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 item categories.

Re-computing Lead Times Changes to routing and resource usages can impact an item’s lead times. After each change you make to a routing (adjusting usages, adding operations, and so on), recalculate the manufacturing lead time for the item.

The Lead Time Calculation Process To calculate lead times:



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: 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. 2. Select Request for the Type. 3. Select Rollup Cumulative Lead Times for the Name. 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. 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. 9. If you chose to roll up cumulative lead times for a range of items, you may enter a

category set to roll up the cumulative lead times of the items associated with this category set. The default is the category set you defined for your functional area.

10. If you chose to enter a category set, enter a beginning and ending category.



Summary



Maintaining Routings Chapter 7 - Page 1

Maintaining Routings Chapter 7





Maintaining Routings



Objectives



Agenda



Routing Revisions

Routing Revisions

A routing revision helps you indicate that the operations and resources of an item have 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.



Creating Routing Revisions

Creating Routing Revisions

If you are updating an existing routing, enter the routing revision and the effective date. To update the revision, choose the Routing Revisions button to open the Routing Revisions window.

1. Navigate to the Routing Revisions window. You can do this by choosing the Revision button from the Routings window (N) Routings > (B) Routing Revisions.

2. Enter the routing revision. 3. Enter an effective date and time.

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 Engineering, the ECO text is displayed.



Agenda



Standard Operations

Standard Operations

Standard operations are commonly used operations you can define as a template for use in 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 defining. You can then modify the operation information in your new operation. 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. You can also create setup standard operations that are used only when setting up machine type resources. When defining resource setup information, you have the option of specifying the standard operations used during changeovers.



Creating Standard Operations

Creating Standard Operations

1. Navigate to the Standard Operations window (N) Routings > Standard Operations. 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 of a given department are required in order to perform a warehouse task. Oracle 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 picking task may require a forklift machine and a pallet picker manual resource. Oracle Warehouse Management uses a rules based system to determine the task type, or standard operation; each task should be associated with. Tasks of a given type are then dispatched to users associated with the resource definition, who have the qualified equipment for the task available to them.

3. Enter the department where the operation is performed. 4. Enter the minimum transfer quantity of assemblies to move from this operation to the next. 5. 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.

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



Quiz


• A standard operation is not the same as a standard bill of material.



Assigning Resources to Standard Operations

Assigning Resources to Standard Operations

1. Navigate to the Resources window (N) Routings > Standard Operations (B) Operation Resources. Choose the Operation Resources button to assign resources to the standard operation.

2. Enter the sequence number of the resource and the resource name. You can use any resource assigned to the department. Valid values for sequence range from 1 to 9999999 and must be unique for the operation.

3. Select a basis type by which to charge and schedule the resource. The default is the basis 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 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 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 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



have usage rates greater than zero. Enter an inverse when you know the number of units a 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 automatically calculated when you compute the lead time for the assembly.

10. Indicate which resource is the principle resource, within a group of simultaneous resources.

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 activity associated with the resource.

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 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, Oracle Purchasing computes any purchase price variance and posts it to the rate variance account.

13. Select a charge type. The default is the charge type specified for the resource. 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 replace the primary resource group.

15. Enter the substitute resource name. This is one of the resources that may replace the resource group.

16. Enter the Replacement Group Number. This is used to group substitute resources together, to substitute a resource group.



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.



Defining Operation Competencies for Standard Operations

Defining Operation Competencies for Standard Operations

You can enter the competencies required for a resource to carry out the standard operations. Add the competencies defined in the resource definition to the operation by choosing the assigned resources from the list. You can add the competency for one resource only once and cannot have duplicate records in the operation competency set.

For standard operations and routing, the Check Skill option will remain unchecked when imported. For discrete jobs created through the interface, the job operations will have competencies and check Skill values inherited from the routing. While adding standard operations through the interface the values for Check Skill and competencies will be inherited from standard operation.

Competence and Skill Level are related fields. The Skill Level field is enabled if you enter value in the Competence field and tab out and the Skill Level will have the values relevant to that Competence.

The competencies defined in the resource definition are added to the operation by selecting the assigned resources in the list of values and clicking the Add button.

To Define Operation competencies for Standard Operation



1. Navigate to the Operation Competencies window by choosing Operation Competencies from the Standard Operations window.

2. Create a standard operation. 3. Select the Check Skill check box. 4. Click on the Operation Competencies button. Operation Competencies button will be

enabled only when you select Check Skill check box. Based on the Competence selected, the skill level values for the selected competence appear in the drop down menu of the Skill Level field.

5. Enter the skill level. 6. Enter the qualification required for the competence.



Quiz

Answer: 1



Quiz

Answer: 1



Agenda



Resource Usage

Resource Usage

You can view the operations and routings that use a particular resource in the Resource Where Used window. The Resource Where Used window contains four tabbed regions: Operation Details, Resource Details, Descriptions, and More. The Operation Details tabbed region displays the operation sequence, department, the effective date range, and the routing in which the resource is used. The Resource Details tabbed region displays the resource, the basis type, the usage rate (or 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 scheduling type (Yes, No, Prior, Next), and whether this is an engineering routing.



Viewing Resource Usage

Viewing Resource Usage

1. Navigate to the Resource Where Used window (N) Routings > Resource Where Used. 2. Enter the name of the resource for which to view the operation and routing usage. 3. Enter an effective date. Operation information effective on this date is displayed.



Quiz


• You can use the Resource Where Used window to view the operations and routings that use a particular resource and not an item.



Summary



Common Bills of Material and Routing Functionality Chapter 8 - Page 1

Common Bills of Material and Routing Functionality Chapter 8





Common Bills of Material and Routing Functionality



Objectives



Agenda



Copying Bill and Routing Information

Copying Bill and Routing Information

You can save time defining new, similar bills or routings by copying their information rather than creating them manually. You can copy a bill or routing from your current organization or from another organization that shares your same item master organization. You can then modify your new bill or routing as necessary. You can copy any revision of a primary or alternate bill or routing. Subinventory and locator information are not copied across organizations.



Copying Bills of Material

Copying Bills of Material

You can save time when you create bills of material by using the Copy feature. Several of the items that you manufacture, sell, or plan have similar bills of material. If you want to create similar, alternate bills of material for an item, use the Copy Bills of Material feature. You create a bill of material by copying from these areas:

• The same or a different item number • The primary or an alternate bill for that item number • The same or a different organization

The item from which you copy retains its components. The item to which you copy contains the same components as the item from which you copy. You can change anything on the copied bill of material except the item number. The assembly and components must exist in the organization from which you are copying. After you copy, the two bills of material are no longer related. If you change one bill of material, you will not see the same change in the other bill of material. Once you create a copied bill of material, you must use the Bill of Material Delete function to delete it.



When you copy bills from your current organization, everything is copied to the new bill including the supply type and the supply subinventories and locators. You can only copy bills between items having the same BOM Item Type attribute. For example, if the new bill is a model bill, you can only copy existing bills that are model bills. Know the structure of the bill you are copying, since the copy function only copies single level components of the bill. For example, if the parent item whose bill you want to copy has single level components that are subassemblies, the bill copy function will not copy the components of the subassembly. When you copy the bill from another organization, the components on the bill you are copying must exist in the target organization. The supply subinventories and locators are not copied. Substitute component items must also exist in the target organization to be copied.



Copy Bill Window

Copy Bill Information

1. Navigate to the Copy Bill window (N) Bills > Bills (M) Tools > Copy Bill From. Do this by choosing the Tools menu item and then choosing Copy Bill.

2. Enter the organization, item, alternate, revision, and revision date for the bill to copy. 3. Select a copy option:

- Current: components or operations effective on the revision date - Future and Current: same as current and all future components and operations

4. Choose the Copy and Save button. Doing so copies the appropriate components and automatically saves the new bill.



Copying Routings

Copying Routings

When you want to create similar, alternate routings for an item, you can save time creating routings by using the Copy Routing feature. You create a routing by copying from:

• The same or a different item number • The primary or an alternate bill for that item number

The item from which you copy retains its operations and resources. The item to which you copy contains the same operations and resources as the item from which you copy. You can change anything on the copied routing except the item number and the operation number. After copying, the two routings are no longer related. If you change one routing, you do not see the same change in the other routing. When copying from another organization, only operations occurring in departments that exist in both organizations are copied. Similarly, only resources that exist in both organizations are copied. The resource must also belong to the same department in the target organization.



Copy Routing Window

Copy Routing Information

1. Navigate to the Copy Routing window (N) Routings > Routings (M) Tools > Copy Routing From. Do this by choosing the Tools menu item and then choosing Copy Rtg From.

2. Enter the organization, item, alternate, revision, and revision date for the routing to copy. 3. Select a copy option:

- Current: components or operations effective on the revision date - Future and Current: same as current and all future components and operations - Note: after you have copied information, you can update it as you see fit.

4. Choose the Copy and Save button. Doing so copies the appropriate components or operations and automatically saves the new routing.



Quiz

Answer: 1



Quiz

Answer: 1



Quiz


• You can change anything on the copied routing except the item number and the operation number.



Agenda



Referencing Common Bills and Routings

Referencing Common Bills and Routings

Any two items that are of the same bill type can share common bills and routings. If two different items share the same bill or routing, you can define the bill or routing once and then maintain one copy instead of two. The following notes apply to both bills and routings:

• You cannot reference another bill or routing as a common if that bill or routing also references a common. In other words, you cannot create a chain of common references.

• You can only reference another bill or routing as a common if it has the same alternate name assigned to it.

• If the current bill you are creating is a manufacturing bill, the common bill must also be a manufacturing bill.





If two or more organizations manufacture the same item using the same bill of material, you can define the bill in one organization and reference it from the other organizations. Necessary changes must then be made to the referenced bill. Optionally, you can reference all but the following five fields in a bill, maintaining these fields by individual bill of material.

• Supply Type • Sub-inventory • Locator • Operation Sequence • Include In Cost Rollup

You can create a common bill within the same organization, and across multiple organizations. 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 same item master organization as the current organization and are accessible by the user responsibility. Sharing bills across multiple organizations minimizes the maintenance of your bills of material.



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 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. 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 bill of material. The following notes apply to bills of material:

• You can only reference bills from organizations that have the same item master organization as the current organization.

• If components already exist for the new bill, you cannot reference another bill as a common.

• If your new assembly is in a different organization than the bill you reference, all component items must exist in the new bill’s organization. This also applies to substitute components.

When you use common bills of material, you lose the ability to make organization-specific bill of material changes.



Common Bill Window

Referencing a Common Bill

• In the Bills of Material window, locate the bill that you want to use as the source, or common, bill.

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

• In the Scope region, select one of the following three options: Single Organization

Hierarchy

All Organizations

• If you select Single Organization, enter the organization and item that will reference the common bill. If you select Organization Hierarchy, enter the required name of the organization hierarchy. In this case, the common bill created is referenced by all organizations below the current organization in the chosen organization hierarchy. If you select All Organizations, then the common bill created is referenced by all organizations that have the same item master organization as the current organization.



• Optionally, select the Enable attributes update box. Selecting this box enables you to update the following fields in the bills that reference this common bill.

Supply Type

Sub-inventory

Locator

Operation Sequence

Include in Cost Rollup

Note:

Initially, the values in the above fields within the bills that reference the source bill are copied from the source bill, but you can change these values at a later time.

Once you enable the material control attributes in a common bill and save the bill, you cannot disable the attributes. If you need to disable the attributes, then delete the bill and enter a new bill.

You can choose to enable the above attributes at a later time, too. To do this find a common bill. Select one of the above five fields. A message appears and asks if you would like to edit any of the five attributes. Choose Yes. You can now update the above five fields.

• Choose OK. • In addition to navigating to the Create Common Bills window, you can also create

common bills by running the concurrent program Create Common Bills.



Common Routings

Common Routings

You cannot reference a routing outside your current organization. If an item’s routing references another item’s routing as a common, you should set both items’ lead time lot size to the same value. The lead time lot size and the routing information are used to compute lead times.



Common Routing Window

Referencing a Common Routing:

1. In the Routings window, enter the item for which you want to create a routing. 2. Navigate to the Common Routing window from the Routings window (N) Routings >

Routings (M) Tools > Assign Common Routing. Do this by choosing Assign Common Routing from the Tools menu.

3. In the Common Item field, select the item routing that you want to use as the source (common) routing.

4. Choose OK. The operations from the common routing default into the

Operations region.

5. Save your work.



Agenda



Bill and Operation Documents



Defining Bill and Operation Documents

Defining Bill or Routing Operation Documents

You can attach documents to bills of material or to routing operations. Navigate to either the Bill Documents or Operation Documents window (N) Bills or Routings > Documents.



Attaching Bill and Operation Documents

Attaching Files

You can attach text and files, such as spreadsheets, graphics, and OLE objects to bills of material and routing operations. For example, an attached file may include comments, such as a graphical representation of the bill structure, or detailed instructions and schematic diagrams for routing operations.

To attach files From the Bills of Material or Routings window, choose the Attachments icon (N) Bills or Routings (I) Attachments (B) Document Catalog (B) Attach. To attach a file to a bill, position the cursor in the Header region. To attach a file to a routing operation, position the cursor in the Operations region.



Quiz

Answers: 1, 2, 3, 4



Agenda



Deleting Items, Bills, Routings, Components, and Operations

Deleting Items, Bills, Routings, Components, and Operations

Deleting physically removes information from the database tables. Deleted bill or routing information can be archived to database tables. (You cannot archive item-level information.) You can then write custom programs to report on the archived data. Summary information is saved for all deletion groups. You can report on deletion groups. Files or objects that are attached to bills or routings are not deleted. Instead, the link between the bill or routing and the attached file is severed. The files themselves remain intact in their original location.



Information That You Can Delete

Information That You Can Delete

Set up groups of entities to check, delete and optionally archive. Entities can include items, bills of material, components, routings, or operations. What entities you can delete depends on what Oracle application you are currently using and what applications you have installed.

• If you are using Oracle Bills of Material, you can delete bills, routings, components, and operations.

• If you are using Oracle Engineering, you can delete any engineering entity except ECOs. • If you are using Oracle Inventory and you do not have Bills of Material installed, you can

only delete manufacturing items. • If you are using Oracle Inventory and you do have Bills of Material installed, you can

only delete items, bills, and routings.



Deletion Process

Deletion Process

Several deletion constraints are installed with Oracle Bills of Material. However, you can define custom deletion constraints. If what you are attempting to delete does not pass deletion constraints, it is not deleted. For example, you can define a constraint that prevents you from deleting a bill of material for an assembly that has an item status of active. When you delete an entire bill, you delete all the components for the assembly along with their reference designators and substitute items. When you delete a routing, all operations are deleted. For both bills and routings, any links to attachments are severed. Oracle Work in Process reflects any changes to the bills or routings using the delete functionality only if you re-explode the bill or routing in Work in Process.



Deletion Constraints

Deletion Constraints

Predefined constraints for deleting bills of material or routings are as follows: • a primary bill if an alternate exists • a bill if it is used as a common in another bill • a bill if a repetitive schedule references the bill • a bill if a discrete job references the bill • a bill if any sales orders are open for the parent item • a bill if any demand exists for the parent item • a model bill if any configuration items exist for the model • an option class bill if it is a component of another bill • a primary routing if an alternate exists • a routing if it is used as a common routing • a routing if a repetitive schedule references the routing • a routing if a discrete job references the routing



• a component where the parent item is an option class or model and there is an open sales order for the parent item

• an item, bill, or component that is affected by a pending ECO • mandatory standard components if there is demand for it



Deletion Groups

Defining Deletion Groups

1. Navigate to the Deletion Groups window (N) Delete Groups. If you are updating an existing deletion group, the date it was last submitted (if applicable) is displayed.

2. Enter a group name to identify the group of entities to delete. 3. Select what type of entity to delete. If the type of entity to delete is a bill, then the

checkbox, Common Bills Only, is enabled. If you check this box, only bills referencing the specified bill entities are considered for deletion. If you do not check this box, then both bills referencing the specified bill entities and non-specified bill entities are considered for deletion.

4. Indicate whether to create a delete group for the current organization, an organization hierarchy, or all organizations. Create a delete group for the current organization by specifying the entities (Item, Bill, Routing) and subentities (Component, Routing) to be deleted. You can enter an organization hierarchy name while creating the delete group for the current organization. In this case, processing is done for all subordinate organizations in the chosen organization hierarchy. You can create a delete group for all organizations. In this case, processing is done for all organizations having the same item master organization as the current organization.



5. Indicate whether to archive the deleted entities in the archive tables. You can archive bill and routing information, but not item information. The option to archive is not available if you are deleting only items.

6. Enter the item, bill, or routing to delete, or from which to delete components or operations. The Details tabbed region displays the organization the entity belongs to, its type, and the alternate (if applicable). The Effectivity tabbed region displays the effective date range. The Results tabbed region displays the delete status and the date of deletion (if applicable).

7. To delete an alternate bill or routing, enter the alternate. 8. If you are deleting components, choose the Components button; if you are deleting

operations, choose the Operations button. 9. When finished, choose either the Delete Group button or the Check Group button.

Specifying Components to Delete 1. Navigate to the Components window. Do this by choosing the Components button from

the Deletion Groups window. 2. Enter a component item to delete. The Results tabbed region displays the status as Error,

Check OK, or Deleted. A status of Pending indicates the delete program has not run yet. The Effectivity tabbed region displays the effective date range of the component. If the status is listed as Error, choose the Error button to review why the deletion failed.

Specifying Operations to Delete 1. Navigate to the Operations window. Do this by choosing the Operations button from the

Deletion Groups window. 2. Enter the operation sequence to delete. The Results tabbed region displays the status as

Error, Check OK, or Deleted. A status of Pending indicates the delete program has not run yet. The Effectivity tabbed region displays the effective date range of the operation. If the status is listed as Error, choose the Error button to review why the deletion failed.

Deleting Components and Operations You can delete components from the Bills of Material or operations from the Routings window.

1. Navigate to either the Bills of Material or Routings windows. 2. Do one of the following:

- If deleting a component, select a component. - If deleting an operation, select an operation.

3. Choose either the Delete Record icon, or Delete from the Edit menu. The Delete Component or Delete Operation window appears. A default value for the delete group name may appear, depending upon the last entity deleted.

4. Do one of the following: - accept the default delete group name - select or enter an existing delete group name - enter a new delete group name

5. If you are entering a new delete group name, enter a description for the group. 6. Choose OK.



7. Navigate to the Delete Groups window and run the Delete Group concurrent process. Components and operations are not assigned to the delete group until you save the bill or routing. If you do not save the bill or routing, components and operations are not assigned to the delete group.



Deletion Group Details and Results

Checking Entities for Deletion

Choose the Check Group button to verify whether any deletion constraints are violated. The delete concurrent program updates the entity’s status to Error, or Check OK. A status of Pending indicates the delete program has not run yet. If you perform a check on the item, bill, and routing, the check program will return an Error status for the item. This simply indicates that the item’s bill or routing still exists. In this case, disregard the Error status for the item.

Submitting Entities for Deletion Choose the Delete Group button to submit the delete concurrent program. The delete concurrent program first performs a check for all the entities listed for deletion. Once the check succeeds, the entities are deleted. The delete concurrent program updates the entity’s status to Error, Check OK, or Deleted. A status of Pending indicates the delete program has not run yet. You can subscribe to an Oracle Workflow success or failure business event for item, structure, or component deletions in addition to verifying entity deletion from the Deletion Groups window. These workflow events tell you if an entity is successfully deleted or if there is an error associated with the deletion. You can also find out if an item is marked for deletion.

Reviewing Errors



1. Choose the Errors button to see why the entity could not be deleted. Do this from either the Components, Operations, or Delete Groups windows.

2. Choose the View Constraint button or the drill down indicator to see the violated deletion constraint.



Delete Items Report

Delete Items Report

Use the Delete Items Report to report the delete history for items, components, bills of material, operations, and routings. To submit the Delete Items Report:

1. In the Submit Requests window, select Delete Items Report from the Name list of values. The Parameters window opens. Enter values for the following parameters:

- Delete Group From/To (Optional) - To restrict the report to a range of delete groups, select the beginning and ending delete group.

- Item (Required, Default) - Indicate whether to print delete groups that delete items. - Bill of Material (Required, Default) - Indicate whether to print delete groups that

delete bills of material. - Routing (Required, Default) - Indicate whether to print delete groups that delete

routings. - Bill and Routing (Required, Default) - Indicate whether to print delete groups that

delete bills and routings.



- Item, Bill and Routing (Required, Default) - Indicate whether to print delete groups that delete items, bills, and routings.

- Com ponent (Required, Default) - Indicate whether to print delete groups that delete components.

- Operation (Required, Default) - Indicate whether to print delete groups that delete operations.

- Pending Status (Required, Default) - Indicate whether to print delete groups that have entities waiting to be checked or deleted.

- Check Ok Status (Required, Default) - Indicate whether to print delete groups that have entities that were successfully checked and are eligible to be deleted.

- Error Status (Required, Default) - Indicate whether to print delete groups that have entities that could not be checked or deleted because of an error.

- Deleted Status (Required, Default) - Indicate whether to print delete groups that you have successfully deleted entities from.

2. Choose OK. 3. Choose Submit.



Agenda



Bills of Material and Routing Open Interfaces

Bills of Material API

The Bills of Material API enables you to import your Bills of Material information from a legacy or product data management (PDM) system into Oracle Bills of Material. When you import a bill of material, you can include revision information, bill comments, components, substitute component and reference designator information. The Bills of Material API can process all types of bills. The Bills of Material Object Interface insures that your imported bills of material contain the same detail as those you enter manually in the Define Bill of Material window.

Routing API The Routing API enables you to import routing information from a legacy system. You can create, update, and delete routing information. You can automatically process routing data without inserting system specific information. It processes the information within a routing synchronously and stills you to process more than one routing simultaneously.



Importing Bills of Material and Routings

Importing Bills and Routings

The Bill and Routing Open Interface programs enable you to import bill and routing information. Imported bills include revision, component, substitute component, and reference designator information. Imported routings include routing revision, operation, instruction, and resource information. The Routing Open Interface program imports network routings as well as single routings. To import bills and routings

1. Navigate to the Import Bills and Routings window (N) Bills or Routings > Import. 2. Indicate whether to include all organization codes in the bill of material and routing

interface tables, or just the current organization. If you specify just the current organization, rows in the interface tables that do not have either an organization code or an organization ID assigned are ignored.

3. Indicate whether to import routings from the interface tables. 4. Indicate whether to import bills of material from the interface tables.



5. Indicate whether to delete processed rows from the bill of material and routing interface tables.



Summary





Engineering Overview Chapter 9 - Page 1

Engineering Overview Chapter 9





Engineering Overview



Objectives



Agenda



Engineering Overview

Overview of Engineering Prototype Environment

Oracle Engineering enables you to move toward concurrent engineering by integrating engineering prototype data with manufacturing data. Each department that accesses engineering item information can perform the same functions on prototypes as all departments do for manufactured assemblies. With engineering item information, you can separate released product designs, controlled distribution products, and alternate manufacturing methods for existing products from your manufacturing data. Engineering enables you to create engineering items, bills of material and routings the same way you define manufacturing item information. Each item defined in Engineering is assigned to engineering. You can define engineering items and assign item attribute details as you do for manufacturing items.

Item Catalog for Group Technology When you design new products, search for existing items that meet your requirements before you define a new engineering item. Doing so can help prevent duplicate items. When you define an engineering or manufacturing item, you can classify the item by any number of characteristics.



For example, you can catalog manufacturing items and engineering items by three descriptive elements-form, fit, and function. Before you create a new engineering item, search the item catalog for all items that match any combination of these elements, such as heated plastic and fastener. You can further restrict your search with other item details, including organization, item type, item category, and item status. If an item that meets your search criteria does not exist, you can create a new engineering item and assign the values of heated plastic to form and fastener to function.

Engineering Item Status You can define item statuses for each phase of your product life cycle. Engineering enables you to control engineering item attribute information by item status, so you can manage the introduction of new products. For example, you may define an item status Design Released and assign this status to all engineering product designs released from Design Engineering to your organization. You can control a Design Released item so that it cannot be built, purchased, or sold. As your product design matures, you can assign an item status of Alpha to your item so you can build or purchase it, but not include it on customer orders. After the product design and process stabilize, you may assign a Beta item status to your item so you can build, purchase, and sell the item in small quantities.

Engineering Item Costing You can specify item costs, roll up costs, and update frozen standard costs for engineering items. When you assign item costs, you can specify cost elements, sub-elements, activities, basis and rates, the same way you assign costs for manufacturing items. Oracle Cost Management lets you roll up and update manufacturing and engineering item costs by item, category, or across all items. After you assign, roll up, and update item costs, you can review cost information for all cost types available to engineering. You can restrict access to item cost details in Engineering by cost type.

Engineering Item Purchasing For each engineering item you define, you can enable the item for use in Oracle Purchasing. To include engineering items on your purchase orders and requisitions, you can assign default buyer, supplier, price tolerance, and account information the same way you assign purchasing details to manufacturing items. You can receive, return, or adjust engineering items the same way you receive manufacturing items on purchase orders. For costed engineering items, you can track purchase price and compute purchase price variance the same way you cost other purchased items. With item status control, Engineering also enables you to control purchasing functions at any point in an engineering item’s life cycle.

Engineering Item Planning Engineering enables you to plan engineering items in Oracle Advanced Supply Chain Planning (ASCP) the same way you plan manufacturing items. When you define an engineering item, you can assign a planning method, planning time fence, shrinkage rate, and other planning details. In ASCP, you can forecast engineering items and manufacturing items, load forecast details, and consume forecasts with existing sales orders. ASCP computes material requirements for engineering and manufacturing items using the master schedule, engineering or manufacturing bills of material, scheduled receipts, and inventory information. You can also control planning functions for engineering items by item status to track an engineering item’s life cycle.

Discrete Jobs for Engineering Items



When you define an engineering item, you can enable the item for use in Work in Process. To build an engineering assembly or prototype a new process, you define a discrete job using an engineering bill of material or routing. You can issue engineering and manufacturing items to jobs, as well as collect resource, material, and overhead costs based on an engineering routing. You can place finished engineering assemblies into inventory the same way you place manufacturing assemblies into inventory. To track an engineering item’s life cycle, you can update item status and control when to build an engineering item or prototype a new process in Work in Process.

Item Types and Bill of Material Types Each item can be identified as an engineering item and enabled for use in Engineering using two item master attributes, Engineering Item and BOM Item Type. The BOM Allowed item attribute must also be set to Yes. The Engineering Item attribute indicates whether the item exists in engineering. If not, it is a manufacturing item. This attribute is not updatable when defining the engineering item. When an item is transferred to manufacturing, the Engineering Item attribute is disabled. You can enable any item for use in Engineering when you assign one of the following four values for the BOM Item Type item attribute: standard, model, option class, or planning. You can define an engineering item and an engineering bill of material for a manufacturing item enabled in Oracle Bills of Material, but you cannot define manufacturing bills of material for engineering items.



Engineering Bills of Material and Routings

Engineering Bills of Material and Routings

You can define an engineering bill of material or routing as alternates for a manufacturing bill or routing. This enables you to prototype variations from the primary bill of material that produces the same assembly. You can specify a list of item catalog descriptive elements for model and option class engineering bills. After you release the engineering bill to manufacturing and take customer orders for specific configurations, Bills of Material creates the new configuration item and automatically assigns values to each catalog descriptive element. Engineering lets you assign manufacturing and engineering items as components to the engineering bill of material. Each routing you define can exist either in engineering or in manufacturing, and both engineering and manufacturing routings share the same resource, department, and standard operation information. You can calculate manufacturing and cumulative lead times for engineering items.

ECOs on Engineering Items and Bills



Engineering enables you to define engineering change orders (ECOs) for manufacturing and engineering items. You can also mass change engineering bills of material the same way you manage mass changes to manufacturing bills of material.

ECO Types Engineering controls the access to ECOs and the changes you can specify on an ECO. For each ECO type, you can specify if ECOs of this type can update engineering items. Only users whose profile option indicates they can update engineering items can choose ECO types that update engineering item information. If you define a new bill of material using an ECO with an ECO type that updates engineering items, Engineering creates the bill as an engineering bill when you implement the ECO.

Profile Options Engineering uses the following four profile options to control the types of items you can change on an ECO:

• ENG: Engineering Item Change Order Access (engineering items) • ENG: Model Item Change Order Access (model and option class items) • ENG: Planning Item Change Order Access (planning items) • ENG: Standard Item Change Order Access (standard items)



Quiz

Answer: 1



Quiz

Answer: 1



Transferring or Copying Engineering Items, Bills, and Routings

Transferring or Copying Engineering Items, Bills, and Routings

You must transfer an engineering item prior to, or simultaneously with, its engineering bill of material and/or routing. When copying items, bills, and routings, all information must be copied simultaneously. Engineering does not transfer or copy an item, bill, or routing if it already exists in manufacturing. Transferring and copying engineering data is organization specific. You can only transfer or copy an engineering item, bill, or routing to manufacturing within the same organization.

Engineering Items All information associated with the engineering item is transferred or copied. If you copy an engineering item, you must provide a new name and description. The original item information is retained in engineering. When you transfer an engineering item assigned to a category set different from the inventory category set, Engineering automatically assigns the new manufacturing item to the inventory category set. Engineering also enables you to assign a new item revision and lets you reference an ECO when you transfer an engineering item.



Engineering Bills of Material All bill information including all engineering item components on a single level bill for an item is transferred (or copied). For multiple levels of engineering item components, you must transfer each engineering bill level by level, starting from the lowest level. You can assign a new item revision and reference an ECO when you transfer an engineering bill of material. When you transfer an engineering bill of material, you can specify whether to transfer all components, current effective components, or current and future effective components. You can also specify whether to transfer pending component information from an ECO. With this transfer criteria, Engineering transfers all engineering items that meet your criteria and that are components on the single level bill of material. For bills of material that reference a common engineering bill, you must transfer the common bill to manufacturing before you transfer any engineering bills that reference the common bill.

Engineering Routings When you transfer a bill of material without transferring the engineering routing, all components on the manufacturing bill report to the operation sequence 1, regardless of the operations on the engineering routing. If components of the bill of material overlap (the same component item appears twice) at operation sequence one, Engineering does not transfer the engineering bill of material until you also transfer the engineering routing. If you transfer the engineering bill of material and routing simultaneously, components on the manufacturing bill report to the appropriate operation on the manufacturing routing. When you transfer a routing, you can also specify a new routing revision and reference an ECO. Engineering transfers all operations, current effective operations, or future effective operations depending on your transfer criteria. For routings that reference a common engineering routing, you must transfer the common routing to manufacturing before you transfer any engineering routings that reference the common routing.



Quiz


• Engineering enables you to define engineering change orders (ECOs) for manufacturing and engineering items.



Quiz


• The fourth profile option is: ENG: Standard Item Change Order Access (standard items). BOM: Automatic Reservations is not a profile option of Oracle Engineering.



Summary





Setting Up Engineering Chapter 10 - Page 1

Setting Up Engineering Chapter 10





Setting Up Oracle Engineering



Objectives



Agenda



Engineering Setup Flowchart



Setup Steps

Setup Steps

• Set Profile Options (Required) - Profile options specify how Oracle Engineering controls access to and processes data. In general, profile options can be set at one or more of the following levels: site, application, responsibility, and user. Use the Update Personal Profile Options form to set profile options at the user level. System administrators use the Update System Profile Options form to set profile options at the site, application, responsibility, and user levels. Perform this step once for each entity, that is, site, application, responsibility, or user.

• Enter Employee (Required) - Define employees for your organization. ECO requestors and approvers must be defined as employees. If you do not install Oracle Human Resource Management Systems with Oracle Engineering, use the Enter Employee form to define and maintain employees in Oracle Engineering. If you install Oracle Human Resource Management Systems, use the forms in Oracle Human Resource Management Systems instead to enter and maintain employees. Perform this step once for each entity organization.

• Define Change Order Types (Optional) - You can assign a change order type to your ECOs, either using the ECO change order type that Oracle Engineering provides or choosing a change order type from any number of types you define using your own



terminology, such as Design Revision, Manufacturing Change Order, or Substitution Waiver. You can create change order types for ECOs with manufacturing items, or manufacturing and engineering items. If you skip this step, Oracle shipped change order types will be used as the default values. Perform this step once per installation.

• Define ECO Departments (Optional) - You can group users that use the engineering change order (ECO) system through ECO departments, creating multiple ECO departments within your Inventory organization. You can restrict access to ECOs by ECO department and require an ECO department on all ECOs-changing the responsible ECO department as the ECO moves through multiple departments. Perform this step once per organization.

• Define Autonumbering (Optional) - You can define customized autonumbering (for a user, organization, or site) for new ECOs or mass change orders. You can use the autonumber default value when you define an engineering or mass change order, or you can override the autonumber default and assign your own number. Perform this step once per organizational user.

• Define Approval Lists (Optional) - You can define lists of approvers required to approve an ECO before it can be released. Oracle Engineering notifies the people on the list, using an alert, that the ECO requires their approval. Perform this step once per installation.

• Define Material Dispositions (Optional) - You can define your own customized material dispositions, and then assign them to revised items when defining ECOs.

• Define Reasons (Optional) - You can define reasons for engineering change orders using your own terminology, such as Model Year, Design, Safety, and Ergonomic. ECO reasons are for your reference use only. If you skip this step, Oracle shipped reasons will be used as the default values. Perform this step once per organization.

• Define Priorities (Optional) - You can define scheduling priorities for engineering changes to describe the urgency of your ECO. Priorities are for your reference use only. If you skip this step Oracle shipped priorities will be used as the default value. Perform this step once per organization.

• Start AutoImplement Manager (Optional) - If you automatically implement ECOs, you must specify the frequency that you want the AutoImplement manager to run. Once an ECO has been released to the autoimplement manager, you can automatically implement all scheduled ECO revised items whose effective date is less than or equal to the current date.



Profile Options

Profile Options

ENG: Change order Autonumbering-System Administrator Access • Indicate whether you can define ECO autonumbering for all users or for yourself only.

ENG: ECO Department • Indicate the default department Engineering uses when you define an ECO. An ECO

department is the department currently responsible for an ECO. It restricts departments from updating ECOs for which they are not responsible.

ENG: ECO Revision Warning • Indicate whether to raise a warning but still implement ECO revisions with pending

lower level revisions (Yes), or to raise an error and not perform the implementation (No or blank). A blank (or “null") value is equivalent to No.

ENG: Engineering Item Change Order Access • Indicate whether you can revise engineering items on ECOs.

ENG: Mandatory ECO Departments • Indicate whether it is mandatory to assign a department to each ECO so you can enforce a

security policy.



ENG: Model Item Change Order Access • Indicate whether you can revise model and option class items on ECOs.

ENG: Planning Item Change Order Access • Indicate whether you can revise planning items on ECOs.

ENG: Require Revised Item New Revision • Indicate whether it is mandatory to assign a new revision to revised items on ECOs. A

blank (or “null") value is equivalent to No. ENG:Standard Item Change Order Access

• Indicate whether you can revise standard items on ECOs. ENG:Allow ENG COMPS for MFG Items in ECO

• Indicate whether you can allow engineering components for MFG revised items in ECO. ENG:MRP Active flag default for ECO

• Indicate the default active flag for ECO revised items. ENG:Update Unreleased WIP Jobs

• Indicate if you can update unreleased WIP jobs.



Quiz

Answer: 1



Quiz


• You can use the Update Personal Profile Options window to set profile options at the user level. System administrators use the Update System Profile Options window to set profile options at the site, application, responsibility, and user levels. Perform this step once for each entity, that is, site, application, responsibility, or user.



Defining ECO Types

Defining ECO Types

Engineering change order (ECO) types help classify engineering and mass change orders to items and bills of material, and determine whether such orders apply to engineering in addition to manufacturing.

An ECO type can be associated with an Oracle Workflow process. If so, a priority can optionally be associated with the ECO type. If you define an ECO using a type and priority combination (even if the priority is blank) that is associated with a workflow process, Workflow will control the ECO approval process. If the type and priority combination is not associated with a workflow process, the ECO approval status defaults to Approved.

Use the Change Types window to define and update change order types that determine the types of items and bills of material you can modify on mass change orders.

You can create a change order type in the Change Types window with a name of up to 80 characters in length in the Type field. You can also set up Engineering change order types in the Change Types window in multiple languages.

To define an ECO type: 1. Navigate to the Change Types window (N) Setup > Change Types. 2. Enter alphanumeric text for a unique change order type.



3. Indicate whether the change order type can revise both engineering and manufacturing items and bills. ECOs with an engineering change type can include both engineering and manufacturing items; ECOs with a manufacturing change type cannot include engineering items. If an ECO with a status of Open, Hold, Release, or Schedule is using this ECO type, this value cannot be updated.

4. Optionally, enter a description for the change order type. 5. Enter a date to inactivate the change order type. As of this date, you can no longer assign

this change order type to a change order. 6. To associate this ECO type with a Workflow process, choose the Processes button. If you

do not associate this ECO type with a Workflow process, any ECO using this type will default to Approved.

To associate an ECO type with a Workflow process: 1. Navigate to the Change Type Processes window. Do this by choosing the Processes

button from the Change Types window. 2. Optionally, select an ECO priority. ECO types are not organization-specific. However,

ECO priorities are organization-specific. This ECO type-priority combination will only be available in the current organization.

3. Select a workflow process to associate with this ECO type. Whenever this type and priority combination (even if priority is blank) is used for an ECO, Workflow will control the ECO approval process.



Defining ECO Autonumbering

Defining ECO Autonumbering

You can define and update customized autonumbering to use as defaults when creating new engineering change orders (ECOs) and mass change orders.

Define autonumbering for a particular user in an organization, a user across all organizations, all users in one organization, or all users across all organizations.

When you first define an ECO, Engineering uses the following hierarchy to determine the prefix to use for autonumbering:

• specific prefix for you and your current organization • specific prefix for you across all organizations • specific prefix for all users for your current organization • specific prefix for all users across all organizations

For example, if a prefix is set up for you and the current organization, it supersedes a prefix defined for you across all organizations.

When defining an ECO, you can either accept a default ECO number or manually enter one. Engineering displays the prefix along with the next available number. If Engineering does not find an autonumbering prefix, you must assign an ECO number manually. When



creating an ECO, once a default ECO autonumber displays, Engineering considers that number used-even if you do not save your changes and create the ECO using that number. For example, if you begin to define an ECO called ABC234, and then decide to abandon your changes, Engineering presents the next ECO number as ABC235. You can manually change this number.

To define ECO autonumbering: 1. Navigate to the ECO Autonumbering window (N) Setup > AutoNumbering. 2. Enter or select a specific User Name to define autonumbering for a particular user, or

select the All Other Users record to define autonumbering for all other users. If you only have privilege to define autonumbering for yourself, the default is your username.

3. Enter a specific organization to define autonumbering for a particular organization, or select the All Other Organizations record to define autonumbering for all other organizations. The information you provide in the Organizations region is associated with the specific user or the All Other Users record in the Users region.

4. Enter a prefix to use as the first characters for each defaulted ECO identifier for the specific user or All Other Users, whichever is currently selected. You can define only one prefix per user per organization. You can define only one prefix per user across all other organizations.

5. Enter a Next Number to use as the base of the numeric portion of ECO autonumbering. The combined prefix and next number (the autonumber) is incremented when each ECO is created. For example, if you enter 100 and your prefix is ABC, the first ECO number is ABC100. The next will then be ABC101. Each new ECO number is defaulted to one integer plus the last used ECO number. When defining a new ECO, you can override this with a higher value. The next ECO number will then be one integer greater. For example, assuming ABC as the prefix and no ECOs defined using ABC, ABC1 is the default. If you have defined an ECO called ABC234, ABC235 is the default. You cannot enter a prefix and next number that, when used together, exceeds ten alphanumeric characters.



Quiz


• Engineering change orders also determine whether such orders apply to engineering in addition to manufacturing.



Defining ECO Approval Lists

Defining ECO Approval Lists

Engineering lets you define lists of approvers for ECOs. Each approval list can be used as a role by Oracle Workflow.

One workflow process, named Standard Approval Process, is installed with Engineering. To define an ECO approval list:

1. Navigate to the Approval Lists window (N) Setup > Approval Lists. 2. Enter the approval list name, a description, and, optionally, a date on which you can no

longer assign the approval list to an ECO. 3. Enter a sequence for the approver. This number indicates the sequence of the approver

for the ECO. Engineering uses this for information purposes only. 4. Enter an employee name for the approver. 5. Enter a date for this approver on this approval list. As of this date, the approver is no

longer notified when an ECO requires their approval.



Defining Material Dispositions

Defining Material Dispositions

Engineering enables you to define customized material dispositions. You can then assign them to revised items when defining an ECO.

To define a material disposition: 1. Navigate to the Material Dispositions lookups window and define your material

disposition (N) Setup > Material Dispositions. 2. Enter a new code and description for your material disposition. 3. Save your work. 4. Navigate to the Revised Items window and assign your material disposition to revised

items.



Defining ECO Reasons

Defining ECO Reasons

Use engineering change reasons to categorize and identify causes for ECOs. Engineering uses ECO reasons for reference only.

To define an ECO reason: 1. Navigate to the ECO Reasons window (N) Setup > Reasons. 2. Enter alphanumeric text to describe a unique reason for initiating an engineering change.

For example, you could define a reason OBSOLETE to indicate an obsolete part, or WAIVER to indicate a component change on a bill of material.

3. Enter a description of the ECO reason. 4. Enter a date on which the reason becomes inactive. As of this date, you can no longer

assign the reason to an ECO.



Defining ECO Priorities

Defining ECO Priorities

Engineering change priorities let you specify the urgency of the engineering change order. You can define a priority, enter a description, and enter a priority level between zero and nine. ECO priorities can be specified when associating ECO types with Oracle Workflow processes, which are used for ECO approvals.

To define an ECO priority: 1. Navigate to the ECO Priorities window (N) Setup > Priorities. 2. Enter alphanumeric text to describe a unique priority for an ECO. For example, you could

enter 1 to indicate an important priority. 3. Enter a priority sequence. This is a number between 0 and 9. For example, you can use 0

to denote the highest priority and 9 the lowest. 4. Enter a description for the priority. 5. Optionally, enter a date on which the priority becomes inactive. As of this date, you can

no longer assign the priority to an ECO.



Quiz

Answer: 1



Starting the AutoImplement Manager

Starting the AutoImplement Manager

The AutoImplement Manager runs at the specified dates and times and automatically implements items whose schedule dates occur on or before the current date. Engineering change orders or revised items whose status is Scheduled are automatically implemented.

To start the AutoImplement Manager: 1. Navigate to the Start AutoImplement Manager window (N) Setup > AutoImplement. 2. Enter or select the Automatic Engineering Change Order Implementation program. 3. Enter the dates and times when to run the ECO auto implement process.



Summary



Creating Engineering Change Orders Chapter 11 - Page 1

Creating Engineering Change Orders Chapter 11





Creating Engineering Change Orders

Oracle Engineering > Reference DesignatorsDistribution

Job Title*



Creating Engineering Change Orders



Objectives



Agenda



Engineering Change Orders Overview

Overview of Engineering Change Orders

Engineering Change Orders (ECOs) enable you to control new item revisions and bill of material changes. With one ECO, you can group several bill of material changes that affect one or more bills. You can define ECOs for all types of items and bills, including:

• manufacturing and engineering items • bills and their components • planning, model, option class, and standard items • primary and alternate bills of material

An ECO specifies changes to one or more items that are logically related to each other, such as a new product introduction. Each ECO specifies changes for one or more revised items and each revised item can have one or more revised components. Depending on the ECO type, an ECO can update manufacturing bills only or both manufacturing and engineering bills. You can add either engineering or manufacturing items as components on engineering bills. However, you can only add manufacturing items as components on manufacturing bills.



You can create ECOs for routings. This is the process of revising engineering and manufacturing routings with change orders for both flow and non-flow environments. You can transfer or copy engineering items, bills, and routing to manufacturing as part of an ECO.



Revised Items, Components, Operations, and Resources

Revised Items

Revised items can be either items or bills. If a revised item is a bill, you can change the item revision and component information (revised components). If a revised item defines a new bill, you can create revised components by copying an existing bill. Engineering changes can be defined by date and or model/unit number effectivity. You should assign an effective date and model / unit number for each revised item on an ECO. Engineering uses this information to implement the ECO and to identify past due ECOs. Each time you change a revised item’s effective date, Engineering adds an entry to list effective date changes. You can also specify an early effective date that determines the earliest date that you can manually implement a change. If you do not enter an early effective date, you can manually implement the change at any time. You can reschedule an ECO by entering a new effective date. A date effective revised item can only have date effective revised components. A unit effective revised item can have both unit and/or date effective components. All unit effective revised items must have a from end item unit number specified, if the effectivity profile is set to Unit effectivity. The from end item unit number will be null and non-updatable for date effective revised items. The to end item unit number field will also be null and non-updatable for revised components of date effective revised items. If you are implementing an



ECO for a unit effective component, the from unit number needs to be specified in the revised item block and the to unit number needs to be specified in the revised components block. There are two conditions under which revised items are not implemented: if the early effective date is greater than the current date, and if you do not have access to the item type of the revised item. For example, if the revised item is a model item and you do not have access to model items, the revised item is not implemented. The same is true for option class, planning, and standard items. You can control whether Oracle Master Scheduling/MRP plans your proposed changes before implementation. If you have engineering changes that are firm, but whose effective date is in the future, you may want planning to consider those changes. You can choose to plan changes on any pending ECO regardless of the ECO status. Changes to the ECO status or the revised item status will automatically update the MRP active attribute. However, you can always manually set the MRP active attribute as desired. For each revised item, you can also specify whether Engineering should update work in process material requirements. When you implement such an ECO revised item, Engineering automatically re-explodes and updates the bill of material for all unreleased jobs and repetitive schedules for that item. Engineering also updates repetitive schedules with statuses of Released, Complete, or On hold accordingly.

Revised Components You can add, change, or delete bill of material components and their attributes. The components and their attributes have the same restrictions as when you define a bill using Oracle Bills of Material. For example, you can only add components that are standard, model, or option class items for revised items that are model items.

Revised Operations You can define an ECO for Operations. You can add, disable, and change department information, Effective dates, Minimum Transfer quantities, and many other attributes.

Revised Resources You can define an ECO for Resources. You can add, change, and disable resource information.



ECO Access Control

ECO Access Control

Oracle Engineering controls the access to ECOs and the changes you can specify on them using profile options, security functions, item types, ECO types, and ECO departments.

ECO Types For each ECO type, you specify if it can update engineering items. Only users whose profile option indicates they can update engineering items can choose ECO types that update engineering items.

Item Types Oracle Bills of Material and Engineering use two item master attributes to control access to items and to determine the types of items that can be on a bill: BOM Item Type and Engineering Item. The BOM Item Type item master field divides items into four major types: planning items, model items, option class items, and standard items.

User Profile Options



User profile options control the types of items you can revise on an ECO. You can specify whether a user or responsibility can revise model and option class items, planning items, standard items, or engineering items on ECOs. Engineering uses the following four profile options to control the types of items you can change on an ECO:

• ENG: Engineering Item Change Order Access (engineering items) • ENG: Model Item Change Order Access (model and option class items) • ENG: Planning Item Change Order Access (planning items) • ENG: Standard Item Change Order Access (standard items)

Engineering enforces security for engineering items by only letting users that are allowed to update engineering items choose ECO types that update engineering items. In addition, to update engineering bills of material for manufacturing items, you must choose ECO types that update engineering items. Each time you try to add a revised item to an ECO, Engineering checks to see if you can update that item based on its BOM Item Type and your profile options. For example, you might define several ECO types that can update manufacturing items, and only define one type that can update engineering items.

Profile Settings for Changing Bills Only With ECOs To limit user’s access to bills of material only through ECOs, set the following Bills of Material profile options to No:

• BOM: Standard Item Access • BOM: Planning Item Access • BOM: Model Item Access

And the following Engineering profile options to Yes: • ENG: Standard Item Change Order Access • ENG: Planning Item Change Order Access • ENG: Model Item Change Order Access • ENG: Engineering Item Change Order Access.

Profile Settings for Changing Bills With or Without ECOs With the same seven profile options listed above all set to Yes, bills can be changed with or without ECOs.

ECO Departments You can assign users to departments and secure each ECO to a department so that only users in that department can access the ECO. If you do not specify a department for an ECO, any user can access it. If you do not assign a user to a department, they can access all ECOs. Setting the ENG: Mandatory ECO Departments to Yes requires you to specify a responsible department on every ECO. You can update the responsible department as you release an ECO from the current ECO department. For example, if Product Engineering releases an ECO to Manufacturing Engineering, they can reassign the responsible department so it becomes visible and updatable to users assigned to the Manufacturing Engineering ECO department.



Quiz

Answer: 1



Quiz

Answer: 1



Agenda



Defining Engineering Change Orders

Defining Engineering Change Orders

An engineering change order (ECO) controls item revisions and bill of material changes. ECOs specify changes to one or more items and each of these items can have one or more revised components. To define Engineering Change Orders:

1. Navigate to the Engineering Change Orders window. 2. Create the ECO. 3. Assign an ECO approval list and status. 4. Define implementation costs. 5. Define an ECO revision. 6. Define revised items. 7. Review ECO scheduling. 8. Review item revisions. 9. Define revised components. 10. Review substitute components and reference designators.



11. Optionally, attach files to ECOs. 12. Submit the ECO for approval or set approval status to Ready to Approve. 13. Transfer or Copy the ECO to manufacturing.



Creating an ECO

Creating an ECO

An ECO’s approval status must be Approved before the ECO can be implemented. If the approval status is Approval Requested, you cannot modify the ECO. If the approval status is Approved and the ECO is modified, the approval status will be set back to Not Submitted for Approval. When ECO types are defined, they can optionally be associated with a priority as they are being associated with an Oracle Workflow process. When creating the ECO, if the selected ECO type / priority combination matches a defined ECO type/priority combination, the associated workflow process defaults. The approval status is set to Not Submitted for Approval until the Submit button is chosen. If there is no match between entered values and existing ECO type / priority combinations, the approval status is set to Approved and you can enter an approval list. You can create, update, and delete ECOs for the current organization, or for the current organization and all subordinate organizations in a given organization hierarchy. To create an ECO:

1. Navigate to the Engineering Change Orders window (N) Engineering > ECOs > ECOs.



2. Enter an alphanumeric ECO identifier. If you use ECO autonumbering, the next identifier is defaulted.

3. Enter or select an ECO type. You can only select ECO types that can revise engineering items and bills if the ENG: Engineering Item Change Order Access profile option is set to Yes. If the selected ECO type updates engineering and manufacturing items and bills, any new bills defined on the ECO are engineering bills.

4. Indicate whether to process the ECO across all organizations within the given organization hierarchy, or for the current organization. If the checkbox is not checked, then the ECO applies to the current organization. If the checkbox is checked and a value is provided in the Organization Hierarchy field, then the ECO applies to the current organization and all subordinate organizations under the given organization hierarchy structure. The Organization Hierarchy driver fields apply to the ECO Header, ECO Revisions, Revised Items, Revised Components, Reference Designators and Substitute Components.

5. Optionally, enter the requestor of the ECO. 6. Optionally, enter the ECO department responsible for the ECO. This can be used to

transition the ECO from one department to another, for example, from manufacturing engineering to operations. For new ECOs, the default is derived from the ENG: ECO Department profile option. If you specify that each ECO must have an ECO department, that is, the ENG: Mandatory ECO Departments profile option is set to Yes, then you must specify a responsible department. Access to ECOs by ECO department is as follows:

- You can only view and update ECOs with the same ECO department as your ENG: ECO Department profile option.

- If you do not have a value for the profile option ENG: ECO Department, you can query and update any ECO.

- Any user can query and update ECOs with no department reference. 7. Optionally, enter a reason for the engineering change. 8. Optionally, enter or select a priority for the ECO. If the ECO type and the priority

combination are associated with an Oracle Workflow process, you cannot use an approval list.

9. If a workflow process is not associated with the ECO, you can enter an approval list. If you do not enter an approval list, the ECO approval status defaults to Approved without any kind of approval process.

10. Optionally, enter the approval status for the ECO. 11. Choose the ECO Revisions button to define ECO revisions. 12. Choose the Revised Items button to define revised items. 13. Select the ECO status from the Tools menu. If the ECO status is Implement or Canceled,

the date of either status change is displayed. 14. If a workflow process is associated with the ECO, choose the Submit button to start the

process.



Viewing ECO Approval Status

Viewing ECO Approval Status

If an approval list is used, the approval status can only be changed manually, pending formal approval from a list member. If a workflow process is associated with the ECO (based on the ECO type / priority combination), the approval status is changed automatically. If neither a list nor a process is used, you must manually select either Approved or Rejected. To view approval dates:

Select View Dates from the Tools menu (N) ECOs > ECOs (M) Tools > View Dates. The approval request date, the approved date (if applicable), and the days to approve are displayed for reference.

To view workflow approval status: 1. If a workflow process is associated with an ECO, Select View Approvals from the Tools

menu to view the approval status of the ECO. 2. Highlight the desired Approval Process, and select the Status button.



Rescheduling an ECO or Revised Items

Rescheduling an ECO or Revised Items

You can reschedule ECOs or ECO revised items unless their status is Canceled or Implemented. Rescheduling does not change the ECO or revised item status, only the dates. To reschedule an ECO or Revised Items:

1. Choose Reschedule from the Tools menu from either the Engineering Change Orders window or the Revised Items window (N) ECOs > ECOs (M) Tools > Reschedule.

2. Do one of the following: - If you are rescheduling an ECO, select an effective date from the calendar. - If you are rescheduling revised items, select a use-up date.

3. Enter the requestor of the rescheduled ECO. 4. Choose OK to save your work.

If you entered this window from the Engineering Change Orders window, choosing OK will reschedule all pending revised items (those with the status of Open, Hold, Schedule, or Release) for this ECO. If you entered this window from the Revised Items window, this will reschedule only the selected revised item.



Changing the ECO Status

Changing the ECO Status

You can change the ECO status and the ECO revised item’s status to Open, Hold, Release, Schedule, Implement, or Cancel. An ECO’s approval status must be Approved before the ECO can be implemented. To change the ECO status:

1. Navigate to the Engineering Change Orders window. 2. From the Tools menu, choose the status (Open, Hold, Release, Schedule, Implement, or

Cancel). 3. If you are canceling the ECO, select the Cancel Comments pop list to enter comments. 4. Save your work.



Quiz


• An ECO’s approval status must be Approved before the ECO can be implemented. If the approval status is Approval Requested, you cannot modify the ECO. If the approval status is Approved and the ECO is modified, the approval status will be set back to Not Submitted for Approval.



Defining Implementation Costs

Defining Implementation Costs

Estimate the implementation costs to engineering and to manufacturing of the ECO. Oracle Engineering uses this information for reference purposes only. To define manufacturing and engineering costs:

1. Choose Enter Costs from the Tools menu (N) ECOs > ECOs (M) Tools > Enter Costs. 2. Enter a cost for engineering 3. Enter a cost for manufacturing.



Defining an ECO Revision

Defining an ECO Revision

To define an ECO revision: 1. Navigate to the ECO Revisions window. Do this by choosing the ECO Revisions button

from the Engineering Change Orders window (N) ECOs > ECOs (B) ECO Revisions. 2. Enter a revision for the ECO. The date that you entered the ECO is displayed for reference. 3. Save your work.



Defining ECO Revised Items

Defining ECO Revised Items

Each ECO can list one or more revised items whose form, fit, or function needs revision. Any revised item can have an associated bill of material. You can create a bill for a revised item (if one does not exist) by copying it from another bill or by adding components to it. To define revised items:

1. Navigate to the Revised Items window. Do this by choosing the Revised Items button from the Engineering Change Orders window (N) ECOs > ECOs (B) Revised Items.

2. Enter or select an item to change with this ECO. You can create a bill for the item (if one does not exist) by choosing the Components button and adding components in the Revised Components window.

3. Optionally, enter an alternate for the item. You can create or update alternate bills using an ECO.

4. Optionally, enter a new revision for the revised item. This must be greater than or equal to the current revision. If you create or update an alternate bill of material, you cannot assign a new item revision. You must enter a new revision for the revised item if you set the ENG: Require Revised Item New Revision profile option to Yes.



5. Optionally, enter an item Description. You do not have the ability to enter an item description if you enter an alternate for the item.

6. Optionally, enter a Routing Revision. This must be greater than or equal to existing revisions. You cannot enter any revisions if you selected a Model/Unit effectivity item in the Item field. If you entered a revised item that should not have routings, then the Routing Revision field will be disabled.

7. Enter an effective date for the item and component changes. This date is used to implement the revised item and identify past due revised items. If you select a use-up date for this item and its components, a record is created that indicates that this revised item is based on the use-up date of the item. If the MRP planning process computes a new use-up date before this revised item is implemented, Engineering automatically sends an alert to the planner.

8. Choose a status for the ECO revised item from the Tools menu. You can set the revised item status to Hold, Released, Implemented, or Canceled only if the ECO status is Open. Otherwise, the revised item status defaults from the ECO status. If the ECO has a Workflow process and the item or its components are changed, the revised item’s status is changed from Scheduled to Open and the approval status is changed to Not Submitted for Approval.

9. Indicate whether the revised item is MRP Active. The default is No if the Status is Hold; Yes if the Status is Open, Release, or Schedule. If the ECO lists engineering changes and has an effective date in the future, you may want the planning process to consider those changes.

10. Open the Item Details tabbed region and view the description and the user-defined item type for that item.

11. Optionally, open the Dates tabbed region and enter the Early Effective date. This is the earliest date you can manually implement the revised item. If applicable, the Canceled date for the changes of the revised item and its components, or the Implemented date for the revised item is displayed. The Implemented Immediately check box, if enabled, indicates the item was implemented manually from the Tools menu. If disabled, the item is scheduled for automatic implementation.

12. Open the Use Up Details tabbed region and do the following: - If not already selected, enter the item whose use-up date is tied to the revised item

effective date. The use-up item can be the revised item itself or a component of the revised item.

- View the use-up item associated with the use-up date selected as the effective date. - View the name of the MRP plan to use for determining item use-up dates.

13. Open the Routing Details tabbed region and do the following: - Indicate whether CTP is enabled. This attribute is derived from the routing header

information if the revised item has existing routing information. If routing information does not exist, routing header information is created automatically when you enable this attribute.

- Enter a priority value for this item. - Choose a valid subinventory.



- Enter Locator information. If the completion subinventory does not have a valid location, or the revised item’s Locator Control attribute is set to No Control, then this field is disabled. If the revised item’s Locator Control attribute is set to Dynamic Entry, then this field is enabled.

14. Open the Work in Process tabbed region and indicate whether to update WIP requirements for unreleased jobs or schedules when the revised item is implemented.

15. Select a disposition for inventory and work in process inventory affected by the ECO. 16. Open the Cancel Details tabbed region to view the cancellation date and cancel

comments. 17. Choose the History button to view revised item effective date history and track schedule

changes to the revised item. Choose the Revisions button to view item revisions. Choose the Components button to add, change, or disable components.



Defining Revised Operations

Defining Revised Operations

Enter, disable, and update information for a revised item’s operations. To define revised operations:

1. Navigate to the Revised Operations window. Do this by choosing the Operations button from the Revised Items window (N) ECOs > ECOs (B) Revised Items (B) Operations.

2. Enter or select an action to take: - Add: Add an operation and the operation’s resources. If there is no existing

operation, then a new routing header should be created. - Change: Change operation attribute and resource information. - Disable: Disable the operation from the revised item’s bill. The resources that are

associated with the operation should be disabled. 3. Enter the Operation Sequence Number of the target operation. If you selected the Add

action, enter a new operation sequence number. If you selected the Change or Disable actions, enter an existing operation sequence number.



4. Indicate whether this operation will be referenced if you selected the Add action. If you selected a standard operation, then this flag is turned on automatically. If you selected the Change action, then this flag is disabled.

5. Enter the Department Code. If you selected the Add action, or the Change action and a standard operation, enter an existing department code.

6. Enter the date the operation is to be disabled in the Disable Date field. If you selected the Disable action, the system date is entered automatically.

7. Indicate whether this operation is option dependent if you selected the Add action, or the Change action and did not select the reference flag.

8. Enter the Operation Lead Time if you selected the Add or Change actions. If an operation lead time is smaller than zero or greater than 100, then an error message will be shown.

9. Open the WIP tabbed region and enter the following attributes: - If you selected the Add action, or the Change action and did not select the reference

flag, you can update the Count Point flag. - If you selected the Add action, you can update the Autocharge flag. - If you selected the Add action, or the Change action and did not select the reference

flag, you can update the Backflush flag. - If you selected the Add action, or the Change action and did not select the reference

flag, you can enter the Minimum Transfer Quantity. 10. Open the Operation Yield tabbed region and do the following:

- Enter the Yield if you selected the Add or Change actions. Operation Yield is applicable to lot-based jobs, and is used to track variances between estimated and actual scrap absorption.

- Enter the Cumulative Yield if you selected the Add or Change actions. - These fields can be updated for operations belonging to lot-based routings, and are

applicable for Shop Floor Management enabled organizations.



Defining Revised Resources

Defining Revised Resources

Enter or disable information for a revised operation’s resources. If the Reference Flag in the Revised Operations window is selected, then you cannot add or disable resources. To define revised resources:

1. Navigate to the Operation Resources window. Do this by choosing the Revised Resources button from the Revised Operations window (N) ECOs > ECOs (B) Revised Items (B) Operations (B) Revised Resources.

2. Enter or select an action to take: - Add: Add a resource to the operation. - Change: Change existing resource information. - Disable: Disable the resource from the operation. Designate an existing resource

sequence number. 3. Enter the Resource Sequence Number. If you selected the Add action, enter a new resource

sequence number. If you selected the Disable action, enter an existing operation sequence number.



4. Enter the Resource Code. If you selected the Add action, select a resource belonging to the selected department in the Revised Operations window. The UOM field is derived from the Resource attribute and is read-only.

5. Enter the Basis Type. If you selected the Add or Change actions, select Item or Lot. 6. Enter the Usage Rate or Amount if you selected the Add or Change actions. Once you

enter or change this value, the Inverse will be calculated automatically. 7. Enter the Inverse Rate or Amount if you selected the Add or Change actions. Once you

enter or change this value, the Usage will be calculated automatically. 8. Open the Scheduling tabbed region and do the following:

- Indicate whether this resource is available 24 hours. Once selected, you cannot update this value.

- If you selected the Add or Change actions, enter a Schedule Sequence Number. - Enter the number of units assigned to this resource. - Select the Schedule option. Available options are Yes, No, Prior, and Next. - If you selected the Add or Change actions, enter the Offset percentage. This number

should be greater than or equal to zero, and less than or equal to 100. - Indicate whether this is the principle resource in the operation, if you selected the

Add or Change actions. - Enter the Setup Type Code for this resource.

9. Open the Costing tabbed region and do the following: - Select an Action. You can Add or Change costing information. Costing information

must be defined for each resource. - Select whether to cost at the standard rate. - Select a Charge Type if you selected the Add action. If you selected the Change

action, you can change the Charge Type but cannot enter an autocharge type of PO Move or PO Receipt for a resource without Outside Processing enabled. You can select Manual or WIP Move.



Defining Revised Components

Defining Revised Components

Enter and update change information for a revised item’s components. To define revised components:

1. Navigate to the Revised Components window. Do this by choosing the Components button from the Revised Items window (N) ECOs > ECOs (B) Revised Items (B) Components.

2. Enter or select an action to take: - Add: Add a component to the revised item’s bill of material. If a bill does not

already exist, adding components creates one. - Change: Change usage information for the component of the revised item’s bill. - Disable: Disable the component from the revised item’s bill.

3. Enter a component on the bill. 4. Do the following:

- If you are changing component information, enter the old operation sequence where the component is currently assigned.



- If you are changing the component’s operation sequence, enter a new operation sequence (from the routing) for the component of the revised item. The default is 1 for components being added where no routing exists.

- Enter the item sequence of the item on the bill of material. The default is the next highest item sequence.

- Enter the component quantity used by this particular revised item. For components you are changing, you can see the old component’s quantity in the Old Quantity field when you change or disable a component. The default is the quantity used by the revised item, 0 for components you are deleting, and 1 for components you are adding.

- For components you are adding or changing, enter an inactive date for the revised component.

5. Review the item’s description, revision, and whether it is an engineering item in the Item Details tabbed region.

6. Open the Component Details tabbed region and do the following: - Enter the planning percent for optional components on model and option class bills,

and all components on planning bills. Oracle Master Scheduling/MRP uses planning percentages for planning bill explosions. You can enter quantities over 100 percent to overplan.

- Enter a component yield factor. You cannot enter component yield for an option class item or for any components of a planning bill. The default is 1, indicating 100% yield.

- Indicate whether to include the cost of this component in the cost of its parent item for the cost rollup.

- View the component item type and status. 7. Open the Material Control tabbed region and select a supply type, a subinventory, and a

locator. 8. Open the Order Entry tabbed region and do the following:

- Indicate whether to Check ATP. - Indicate whether the component is optional and mutually exclusive. - For optional components, enter the minimum and maximum sales order quantities. - Select a basis.

9. Open the Shipping tabbed region and indicate whether the component should be listed on shipping documents, required to ship, or required for revenue.

10. If the component is canceled, open the Cancel Details tabbed region. Once the component is canceled, you can no longer update any information about the revised component on this ECO. You can cancel revised components by choosing Cancel from the Tools menu.

11. Choose the Substitutes button to open the Substitute Components window. Choose the Designators button to open the Reference Designators window.



Assigning or Deleting Substitute Components

Assigning or Deleting Substitute Components

Assign or delete suggested substitute items for the revised component. You can assign any number of substitute items to each bill component and you can assign the same substitute item to more than one component. To assign or delete substitute components:

1. Navigate to the Substitute Components window. Do this by choosing the Substitutes button from the Revised Components window (N) ECOs > ECOs (B) Revised Items (B) Components (B) Substitutes.

2. Enter an action: add a substitute item to, or delete a substitute item from the revised component.

3. Enter or select a substitute item for the revised component. This must be a manufacturing item.

4. Enter the quantity of the substitute item needed to replace the full component quantity. This can differ from the bill usage quantity of the component. The default is the usage quantity of the component.



Assigning Reference Designators

Assigning Reference Designators

To assign reference designators to the revised component: 1. Navigate to the Reference Designators window. Do this by choosing the Designators

button from the Revised Components window N) ECOs > ECOs (B) Revised Items (B) Components (B) Designators.

2. Indicate whether to relate component quantity to the number of reference designators. - Off: Assign any number of reference designators to each component (the default).

The number of reference designators is independent of the component quantity. With Quantity Related unchecked, if the usage quantity of the component is four, you could, for example, define six or more reference designators.

- On: Use one reference designator per usage of the component. The component usage quantity must be a positive integer in order for you to use this option. When the bill requires a quantity of four of a given component, you assign four reference designators to that component, one for each usage.

- The number of reference designators implemented for the revised component is displayed. This value is 0 until the ECO is implemented.



- The total number of reference designators currently defined for the revised component is displayed.

3. Select an action: add to or delete a range of reference designators from the revised component. Engineering enables you to view a prefix, suffix, and number range to assign to a sequence of reference designators.



Quiz

Answer: 1



Agenda



ECO Life Cycle

ECO Life Cycle

When processing ECO’s you typically follow a set pattern of action. These actions correspond to the ECO revised item statuses and ECO approval statuses. ECO revised item status refers to the overall status of the ECO and to the individual status of each revised item on the ECO. ECO approval status refers to the process of requesting and obtaining approval for the ECO from a list of approvers.



ECO Life Cycle

ECO Life Cycle

You can change an ECO’s status. You can open, hold, release, schedule, implement, or cancel a revised item or an ECO. Engineering does not let you set the ECO Status field to Implemented or Scheduled if the approval status has not been set to Approved.



ECO Revised Item Statuses

ECO Revised Item Statuses

Open • You are preparing the information.

Release • You can manually implement the change.

Schedule • The implementation concurrent process implements the change.

Implement • You have successfully changed the bill of material.

Hold • You have temporarily decided not to implement a Released or Scheduled change.

Cancel • You have permanently decided not to implement the change.



ECO Approval Statuses

ECO Approval Statuses

Not Ready • You are not ready to ask for approval.

Ready to Approve • You are ready to ask the approvers to review.

Approval Requested • Approvers have been asked to review.

Approved • The decision has been made to approve the ECO.

Rejected • The decision has been made to reject the ECO.

Processing Error • An error occurred in the workflow approval process.



ECO Approvals

ECO Approvals

ECOs can be approved in three ways, two of which require an approval process. The third requires no approval process. First, the ECO, based on the ECO type in combination with the ECO priority, can be associated with an Oracle Workflow process. Once approval is granted, Workflow automatically updates the approval status. Second, a simple approval list can be used, which sends an Oracle Alert to all those listed requesting their approval. Once approved, you must manually update the approval status. This approval option does not require an Oracle Workflow process. The third method is to use neither of the above; the ECO needs no formal approval process and is given the status of Approved. If the ECO is associated with an Oracle Workflow process, only Workflow may set the status to Approved. If the ECO has an approval list, you must set the status to Approved manually after the ECO has been approved by the appropriate member(s) on the approval list. If neither is used, the ECO is set to Approved but can be manually rejected.

Workflow for ECO Approvals



Most organizations have some form of approval process before engineering change orders (ECOs) are implemented. By using Oracle Workflow, the approval process can be customized to meet each organization’s needs. Business rules for the approval of ECOs are defined in a workflow process. For each ECO, Workflow manages adherence to these business rules, including:

• submission of the completed ECO for approval via Workflow • enforced approval process for an ECO type • communication of messages via Notification Viewer, electronic mail, or web browser • review of ECO from Notification Viewer • automatic processing of user responses and update of system • workflow status indicator for ECOs • usage of current approval lists (roles) in the workflow process

Once the ECO is created, Workflow takes over processing. When Workflow is in control of the approval process, the ECO approval status is set to Approval Requested. Before the approval status is changed, the workflow approval process can be aborted. Workflow manages the approval process until the entire approval flow is complete. Only then is the ECO approval status updated to either Approved or Rejected. If an error occurs during the Workflow approval process, the approval status is set to Processing Error.

Standard Workflow Process One workflow process, named Standard Approval Process, is predefined when Engineering is installed, regardless whether the entire Oracle Workflow product is installed. If the entire Workflow product is installed, you can modify this process or create new processes. If you use the Standard Workflow Process, you must assign a role to the Standard Approval Notification activity. Otherwise, the process will fail. If the Workflow product is not fully installed, you can alter only the Standard Approval Process.

ECO Approval List Setup Workflow can use roles whenever an activity involves several users. Approval lists defined in Engineering can be used to create roles. Roles are made up of either one approval list or one employee previously defined with the Enter Person window. The ECO workflow approval process will notify all persons in the role, regardless if the role is defined using an approval list or an individual employee. To approve (or reject) the ECO, approvers must respond to the notification. If the approver has an Oracle Applications Object Library account, they can respond to ECO approval requests using either a web browser or the Notification Viewer. If not, the approver can respond via electronic mail, provided their address is defined in the Enter Person window.

ECO Types and Priorities Setup ECO types can be associated with a workflow process. If you do not associate an ECO type with a workflow process, there can be no workflow approval process for ECOs using that ECO type. If there is an approval list, the ECO cannot be associated with a process.



ECO types that are associated with a workflow process can optionally be associated with an ECO priority. If so, ECOs that use the type/priority combination are approved via Workflow. Doing so enables workflow approval processes to be ranked according to priority.

ECO Approval The only user intervention required for a workflow approval process is for individual approvers to respond to an ECO approval notification. Once the process is complete, Workflow automatically updates the ECO approval status.



ECO Life Cycle Without Approval

To implement ECO’s without an approval process:

Enter the change information • ECO approval status = Approved. • ECO revised item status = Open.

Implement the change • ECO approval status = Approved. • ECO revised item status = Released or Scheduled (for manual or auto implementation).

After the change is completed • ECO approval status = Approved. • ECO revised item status = Implemented.



ECO Life Cycle With Approval

To implement ECO’s with an approval process:

Enter the change information • ECO approval status = Not Ready. • ECO revised item status = Open.

Prepare the change information for review • ECO approval status = Ready to Approve. • ECO revised item status = Open.

Send the information to the approvers • ECO approval status = Approval Requested. • ECO revised item status = Open.

Change is not approved • ECO approval status = Rejected. • ECO revised item status = Canceled.

Change is approved • ECO approval status = Approved.



• ECO revised item status = Open. Implement the approved change

• ECO approval status = Approved. • ECO revised item status = Released or Scheduled (for manual or auto implementation).

After the approved change is completed • ECO approval status = Approved. • ECO revised item status = Implemented.

ECO Approval: Oracle Engineering Managing the approval process using Oracle Engineering:

• Set up the approval process. - Create approval lists. - Assign an approval list to the ECO. - Assign an ECO change type to the ECO (one not associated with an Oracle

Workflow). • The approval process steps:

- Set ECO approval status to Approval Requested. - Oracle Alert sends email to the reviewers. - Each approver responds either approved or rejected. - The responses are reviewed and the ECO approval status is set to Approved or

Rejected.



ECO Approval with Oracle Workflow

Standard Workflow Process

One workflow process, named Standard Approval Process, is predefined when Engineering is installed, regardless whether the entire Oracle Workflow product is installed. If the entire Workflow product is installed, you can modify this process or create new processes. If you use the Standard Workflow Process, you must assign a role to the Standard Approval Notification activity. Otherwise, the process will fail. If the Workflow product is not fully installed, you can alter only the Standard Approval Process.

ECO Approval List Setup Workflow can use roles whenever an activity involves several users. Approval lists defined in Engineering can be used to create roles. Roles are made up of either one approval list or one employee previously defined with the Enter Person window. The ECO workflow approval process will notify all persons in the role, regardless if the role is defined using an approval list or an individual employee. To approve (or reject) the ECO, approvers must respond to the notification. If the approver has an Oracle Applications Object Library account, they can respond to ECO approval requests



using either a web browser or the Notification Viewer. If not, the approver can respond via electronic mail, provided their address is defined in the Enter Person window.

ECO Types and Priorities Setup ECO types can be associated with a workflow process. If you do not associate an ECO type with a workflow process, there can be no workflow approval process for ECOs using that ECO type. If there is an approval list, the ECO cannot be associated with a process. ECO types that are associated with a workflow process can optionally be associated with an ECO priority. If so, ECOs that use the type/priority combination are approved via Workflow. Doing so enables workflow approval processes to be ranked according to priority.

ECO Approval The only user intervention required for a workflow approval process is for individual approvers to respond to an ECO approval notification. Once the process is complete, Workflow automatically updates the ECO approval status.

ECO Approval with Oracle Workflow The standard approval processing workflow delivered in Oracle Engineering:

• Requires unanimous approval from the reviewers to approve the ECO. • Sets MRP Active to selected or clear. • Sets the ECO approval status to Approved or Rejected.

Managing the approval process using Workflow: • Setup the workflow approval process:

- Create a workflow or use a seeded workflow for approval with processes to perform actions and notifications to contact employees for decisions.

- Assign an approvers list as a role to the workflow notification activity. - Assign the workflow to an ECO change type. - Assign the ECO change type to the ECO.

The workflow approval process steps: • Choose submit on the Engineering Change Orders window:

- The workflow notifies all employees in the role. - Each approver responds: approved/rejected. - Oracle Workflow tabulates the responses, makes an approval decision, performs

follow up activities and returns control to Oracle Engineering. - If an error occurs, the ECO approval status becomes Processing Error.



Summary


Maintaining Engineering Change Orders Chapter 12 - Page 1

Maintaining Engineering Change Orders Chapter 12





Maintaining Engineering Change Orders



Objectives



Agenda



Implementing ECOs

Implementing ECOs

When you implement an ECO, each revised item’s status is marked as implemented; you can no longer reschedule it. You can implement all revised items on an ECO, or implement each revised item on a different date. Engineering only lets you implement ECOs that do not have an approval status of Rejected, or do not have an ECO status of Hold or Cancelled. Once you implement an ECO or revised item, you can no longer make any revised item changes. You can manually implement revised items on an ECO or you can automatically implement each revised item on its effective date. Engineering updates the actual implementation date for each revised item when it is implemented. When all of the revised items on an ECO have been implemented, the ECO is completely implemented and can be purged. Engineering implements an ECO over time from the earliest revised item effective date to the latest revised item effective date. When you spread multiple changes across several ECOs, you should ensure that the effective date ranges for the ECOs do not overlap. For example, if you implement changes to a bill of material across many ECOs, you should make sure the revised item effective dates do not overlap. If you implement one change using the current revision, you should implement all other changes to the current revision before you implement changes against future revisions.



You must implement new revisions in ascending order. If you implement a later revision for an item on one ECO, Engineering ensures that you implement any subsequent revisions for the item in ascending order.



Manual Implementation

Manual Implementation

For an ECO, you can specify whether to implement all or specific revised items. An ECO can be implemented today, but will not make the changes to the revised items effective until the date specified on the change order. To manually implement an ECO:

1. Navigate to the Engineering Change Orders window. 2. Enter or select an ECO to implement. 3. Choose Implement from the Tools menu. Doing so automatically changes the status of all

revised items. To manually implement a revised item on an ECO:

1. Navigate to the Revised Items window. 2. Select a revised item to implement. 3. Choose Implement from the Tools menu.

A warning message appears if the ECO does not have a Workflow process and the revised item’s effective date is in the future.



Automatic Implementation

Automatic Implementation

To AutoImplement a revised item on an ECO, you mark the revised item status as scheduled and specify an effective date. You can schedule all revised items on an ECO for auto-implementation, or schedule each revised item individually. Engineering automatically implements scheduled changes on their effective dates. You can automatically implement scheduled ECOs in the current organization, or the current organization including all subordinate organizations. You have the ability to specify the organization hierarchy name, since the current organization can be accessed from more than one organization hierarchy. You can also automatically implement scheduled ECOs in all organizations having the same item master organization as the current organization, and if they are accessible by the user responsibility. Start the AutoImplement Manager process so Engineering implements scheduled changes daily. To automatically implement an ECO:

1. Navigate to the Engineering Change Order window. 2. Enter or select an ECO to implement. 3. Set the ECOs status and/or the status of revised items to Scheduled.



4. Save your work. 5. Start the AutoImplement Manager. The following parameters are provided:

- All Organizations - Organizatio n Hierarchy

If the All Organizations parameter is set to Yes, then processing is done for all organizations having the same item master organization as the current organization. If All Organizations is set to No, and a value is provided in the Organization Hierarchy field, then processing is done for the current organization and all subordinate organizations. If the Organization Hierarchy field is left blank, then the ECO is implemented only for the current organization. For processing, an organization must be accessible by the user responsibility. You can specify a periodic schedule for the concurrent program. In this case, the user should set the processing interval, start date, and end date.



Quiz

Answer: 1



Agenda



Viewing ECO Schedules

Viewing ECO Schedules

View ECO information, including scheduling information, pending and implemented ECOs, approval status, revised item status, and so on. To view ECO schedules:

1. Navigate to the View ECOs window (N) ECOs > Schedules. 2. Enter search criteria in the Find ECOs window 3. Select how to sort ECOs-by ECO identifier then effective date, or by effective date then

ECO identifier. 4. Optionally, enter revised item information:

- an effective date range - a revised item - a revised component - whether to query for revised item status, and if so, any combination of revised item

statuses.



5. Choose the Find button to find ECOs based on your search criteria. This opens the View ECOs folder window, which has three tabbed regions, each containing specific ECO information: Revised Items, ECO Details, and Use Up.

6. Choose the New and Open buttons to navigate to the Engineering Change Orders window. Using the New button enables you to create a new ECO; using the Open button enables you to view an existing ECO.



Viewing ECO Schedule History

Viewing ECO Schedule History

View revised item effective date history and track schedule changes to revised items. To view ECO schedule history:

1. Navigate to the History window. Do this by choosing the History button from the Revised Items window (N) ECOs > ECOs (B) Revised Items (B) History. A history of all previous effective dates and their entry date is listed for the revised item.

2. View the employee who initiated the change to the effective date and any comments describing the change to the effective date.





To view item revisions: 1. Navigate to the Item Revisions window. Do this by choosing the Revisions button from

the Revised Items window (N) ECOs > ECOs (B) Revised Items (B) Revisions. 2. Review the displayed information: The revision, the effective date and time, the

implementation date, the initiation date, and the ECO are displayed for information purposes.



Viewing Routing Revisions

Viewing Routing Revisions

To view routing revisions: 1. Navigate to the Routing Revisions window (N) ECOs > ECOs (B) Revised Items (B)

Routing Revisions. Do this by choosing the Routing Revisions button from the Revised Items window.

2. Review the displayed information: The revision, the effective date and time, the implementation date, and the related ECO are displayed for information purposes.



Quiz

Answers: 1, 2, 3, 4



Agenda



Engineering Change Order Approval Lists Report

Engineering Change Order Approval Lists Report

Report Submission • In the Submit Requests window, select Engineering Change Order Approval Lists Report

in the Name field. Approval List Names From/To

• To restrict the report to a range of approval list names, select beginning and ending approval list names.



Engineering Change Order Detail Report

Engineering Change Order Detail Report

Report Submission • In the Submit Requests window, select Engineering Change Order Detail Report in the

Name field. All Organizations

• Choose one of the following options: - No: Report ECO information for the current organization. - Yes: Report ECO information for all organizations having the same item master

organization as the current organization, and for those organizations accessible by the user responsibility.

Organization Hierarchy • Enter a valid organization hierarchy name from the list of values. If the value for the All

Organizations parameter is set to No, and you have provided a value for the Organization Hierarchy parameter, then the report will provide ECO information for the current organization and all organizations below the current organization in the specified organization hierarchy. If this parameter is left blank, and the All Organizations



parameter is set to No, then the report will provide ECO information for the current organization. You can enter a value in this field only if you have entered No in the All Organizations field.

Engineering Change Orders From/To • To restrict the report to a range of engineering change orders, select the beginning and

ending engineering change orders. Dates From/To

• To restrict the report to a range of dates, select the beginning and ending dates. Status

• Enter Open, Hold, Scheduled, Cancelled, Implemented, or Released to indicate the status of the ECO to print.

Additional Component Detail • Enter Yes or No to indicate whether to print ECO component detail.

Order Entry Component Detail • Enter Yes or No to indicate whether to print ECO order entry component detail.



Engineering Change Order Priorities Report

Engineering Change Order Priorities Report

Report Submission • In the Submit Requests window, select Engineering Change Order Priorities Report in the

Name field.



Engineering Change Order Reasons Report

Engineering Change Order Reasons Report

Report Submission • In the Submit Requests window, select Engineering Change Order Reasons Report in the

Name field.



Engineering Change Order Schedule Report

Engineering Change Order Schedule Report

Report Submission • In the Submit Requests window, select Engineering Change Order Schedule Report in the

Name field. Print Components

• Enter either Yes or No to indicate whether you want to print revised components associated with the revised item.

Engineering Change Order Type • Enter an engineering change order type to print engineering change orders associated

with it. Engineering Change Orders From/To

• To restrict the report to a range of Engineering Change Orders, select the beginning and ending Engineering Change Orders.

Effective Dates From/To • To restrict the report to a range of dates, select the beginning and ending dates.

Revised Item Status



• Enter Open, Hold, Scheduled, Cancelled, Implemented, or Released to indicate the status of the revised item to print.

Display Option • Choose one of the following options:

- All: Report the pending and implemented engineering change orders. - Historical changes: Report the implemented engineering change orders. - Pending changes: Report the current engineering change orders. Oracle Engineering

displays this option as the default. Revised Item

• Enter a revised item to print. Revised Component

• Enter a revised component to print. Sort Criteria 1

• Choose one of the following options. The report sorts ECOs first in this order, then in the specified order for Sort Criteria 2 and Sort Criteria 3.

- ECO: Sort ECOs first by ECO. Oracle Engineering displays this option as the default.

- Effective date: Sort ECOs first by effective date. - Item number: Sort ECOs first by item number.

Sort Criteria 2 • Choose one of the following options. Engineering sorts the ECOs by the first sort type

and then by this sort type within the first type. - ECO: Sort ECOs by ECO. - Effective date: Sort ECOs by effective date. - Item number: Sort ECOs by item number. Oracle Engineering displays this option

as the default. Sort Criteria 3

• Choose one of the following options. Engineering sorts the ECOs by the first sort type, then by the second sort type within the first type, and finally by this sort type within the second type.

- ECO: Sort ECOs by ECO. - Effective date: Sort ECOs by effective date. Oracle Engineering displays this option

as the default. - Item number: Sort ECOs by item number.



Engineering Change Order Types Report

Engineering Change Order Types Report

Report Submission • In the Submit Requests window, select Engineering Change Order Types Report in the

Name field.



Agenda



Attaching Files to ECOs

Attaching Files to ECOs

You can attach text and files, such as spreadsheets, graphics, and OLE objects to engineering change orders. For example, an attached file may include comments, such as a graphical representation of the bill structure or detailed instructions. To attach files to ECOs:

• From the Engineering Change Orders window, choose the Attachments icon.



Transfer to Manufacturing from an ECO

Transfer to Manufacturing from an ECO

You can transfer engineering items, bills, and routing to manufacturing from within an ECO. To transfer entities to manufacturing from within an ECO:

1. Navigate to the Engineering Change Orders window. 2. Select the Transfer Button from the Engineering Change Orders window. 3. Enter an Item and select Bill and Routing if applicable. 4. Enter the Effective Date of the item. 5. Enter the Early Effective date if applicable. 6. Select the Selections tabbed region. 7. Select the Selection Option from the list. The available selections are:

- All: All past, current, or future components and or operation steps associated with the assembly.

- Current: All current components and or operation steps associated with the assembly that are effective on the Selection Date.

- Future and Current: All current and future components and or operation steps associated with the assembly.



8. Enter the Selection Date. 9. Enter the Unit Number if applicable. 10. Save your work. 11. Select the History button to view the transaction history.



Quiz


• You can transfer engineering items, bills, and routing to manufacturing from within an ECO.



Copy to Manufacturing from an ECO

Copy to Manufacturing from an ECO

You can copy engineering items, bills, and routing to manufacturing from within an ECO. To copy entities to manufacturing from within an ECO:

1. Navigate to the Engineering Change Orders window. 2. Select the Copy Button from the Engineering Change Orders window. 3. Enter an Item and select Bill and Routing if applicable. 4. Enter the Effective Date of the item. 5. Enter the Early Effective date if applicable. 6. Select the Revisions tabbed region. 7. Select the Selections tabbed region. 8. Select the Selection Option from the list. The available selections are:

- All: All past, current, or future components and or operation steps associated with the assembly.

- Current: All current components and or operation steps associated with the assembly that are effective on the Selection Date.



- Future and Current: All current and future components and or operation steps associated with the assembly.

9. Enter the Selection Date. 10. Enter the Unit Number if applicable. 11. Select the Manufacturing Items tabbed region. 12. Enter a new item name and description. 13. Save your work. 14. Select the History button to view the transaction history.



Mass Changing ECOs

Mass Changing ECOs

You 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 or choose a subset of bills by item range, item category, or item type. Engineering lets you create an ECO based on your parent item and component criteria. A mass change ECO lists all using assemblies that meet your search criteria as revised items, and assigns all component changes as revised components. You can manage and implement each revised item, or the entire ECO, the same way you maintain revised items you manually assign to an ECO. In Bills of Material, mass changes take place immediately. However, in Engineering, an ECO is created that must be implemented to take effect. To mass change ECOs:

• Mass change the bills of material as needed. Be sure to set ECO options.



Canceling ECOs and Revised Items

Canceling ECOs and Revised Items

You can cancel an entire ECO, a revised item on an ECO, or the individual revised components on an ECO before it is implemented. When you cancel an ECO, you can enter comments that explain the reason for cancellation. Canceling an entire ECO cancels all the revised item changes and the changes to their associated revised components. Canceling a specific revised item cancels only the changes that affect that item and its revised components. Once you cancel an ECO you cannot update it, but you can view a cancelled ECO. Canceling a revised component only affects that revised component for that revised item. The cancelled component can be viewed in the Cancellation tabbed region. To cancel the entire Engineering Change Order:

1. Navigate to the Engineering Change Order window (N) ECOs > ECOs (M) Tools > Cancel.

2. Find the ECO to cancel. 3. Choose Cancel from the Tools menu. 4. Save your work.



- Cancel the ECO, its revised items, and the associated revised components by choosing Cancel from the Tools menu.

- Cancel a revised item by choosing the Revised Items button on the Engineering Change Orders window, and choosing Cancel from the Tools menu.

- Cancel a revised component by choosing the Components button from the Revised Items window and choosing Cancel from the Tools menu.

5. Save your work. To cancel an ECO’s revised items:

1. Navigate to the Engineering Change Order window. 2. Find the ECO containing revised items to cancel. 3. Choose the Revised Items button. 4. Select the revised items to cancel. 5. Choose Cancel from the Tools menu. 6. Save your work.

To cancel components of a revised item: 1. Navigate to the Engineering Change Order window. 2. Find the ECO containing components of revised items to cancel. 3. Choose the Revised Items button. 4. Select the revised item containing components to cancel. 5. Choose the Components button. 6. Select the components to cancel. 7. Choose Cancel from the Tools menu. 8. Save your work.



Purging ECOs

Purging ECOs

You can purge fully implemented engineering change information from the database. You can choose a range of ECOs and a date. Engineering purges all fully implemented or cancelled ECOs on or before that date. When you purge ECOs, Engineering removes all implemented and cancelled ECOs as of that date from the database, along with all related information (except for the revision history of the bill itself). You cannot view or report ECO information once you purge it. To purge an ECO:

1. Navigate to the Purge Engineering Change Order window (N) ECOs > Delete. 2. Enter a range of ECOs to purge. 3. Indicate whether to purge implemented ECOs. 4. Indicate whether to purge cancelled ECOs. 5. Enter a date on or before which all implemented and/or cancelled ECOs are purged.



Quiz

Answer: 1



Agenda



ECO Business Object Interface



ECO Object Interface Features

ECO Object Interface Features

• Common, flexible, and robust. • Import capabilities to create, update, delete. • Synchronous—not batch API. • Validates change information. • Provides error messages.



Summary




Transferring and Copying Engineering Items, Bills, and Routings Chapter 13 - Page 1

Transferring and Copying Engineering Items, Bills, and Routings Chapter 13





Transferring and Copying Engineering Items, Bills, and Routings



Objectives



Agenda



Transferring and Copying Product Information

Transferring and Copying Product Information

When you decide the engineering information is ready for production, you transfer or copy the product information (items, bills of material, and routing) from engineering to manufacturing. When you transfer engineering information, you transform the engineering item into a manufacturing item and the engineering item ceases to exist. When you copy engineering information, you save the engineering information and copy it to manufacturing as another item number. The transfer and copy sequence is a one-way process. You cannot transfer or copy product information from manufacturing to engineering.



Transferring Information to Manufacturing

Transferring Information to Manufacturing

Transfer engineering information like items, bills, and routings to production. To transfer engineering items data to manufacturing:

1. Navigate to the Transfer to Manufacturing window (N) Prototypes > Transfer to Manufacturing.

2. Enter an item and indicate you want to transfer the item, bill, and routing data (if applicable).

3. Optionally, enter a new item or routing revision (if applicable). The revision must be higher than the current revision and can be alphanumeric.

4. Optionally, open the Alternates tabbed region and for Selection, select Specific to transfer a specific alternate, select Primary to transfer the primary alternate, or select All to transfer all alternates. Leaving this blank will transfer the primary and all alternates (if any). To transfer a specific alternate, you must enter its name.

5. Open the ECO, Description tabbed region and enter an ECO. This is for informational purposes only.

6. Indicate if only implemented components should be transferred.



7. Select whether to transfer All past, Current (effective on the specified revision date), or Future components and/or operation steps associated with the assembly. The default is Current. If you select Current or Future and Current, enter an effective date.

8. Choose the Transfer button. Transferring information to Manufacturing reduces data entry. The item transfer occurs at the

organization level. Transfer bills of material and routings that you reference in common bills of material and

routings before transferring the bills of material that contain the reference. If you transfer an assembly bill of material and have not transferred the component items in the

bill of material, the transfer process will transfer the component item information before transferring the bill of material.



Copying Information to Manufacturing

Copying Information to Manufacturing

Use the Copy to Manufacturing window to copy engineering prototype items, bills, and routings to production. To copy engineering items data to manufacturing:

1. Navigate to the Copy to Manufacturing window (N) Prototypes > Copy to Manufacturing.

2. Enter an item and indicate you want to copy the item, bill, and routing data. When copying an engineering bill to manufacturing, you must copy the item simultaneously with its bill and/or routing.

3. Optionally, enter a new item or routing revision (if applicable). The revision must be higher than the current revision and can be alphanumeric.

4. Optionally, open the Alternates tabbed region and for Selection, select Specific to copy a specific alternate, select Primary to copy the primary alternate, or select All to copy all alternates. Leaving this blank will copy the primary and all alternates (if any). To copy a specific alternate, you must enter its name.

5. Open the ECO, Description tabbed region and enter an ECO. This is for informational purposes only.

6. Open the Manufacturing Items tabbed region and enter a new item name and description.



7. Indicate if only implemented components should be copied. 8. Select whether to copy All past, Current (effective on the specified revision date), or

Future components and/or operation steps associated with the assembly. The default is Current. If you select Current or Future and Current, enter an effective date.

9. Choose the Copy button. If you copy an assembly bill of material and have not transferred the component item in the bill

of material, the BOM structure will not copy the component item.



Quiz

Answer: 1



Quiz

Answer: 1



Quiz


• The correct answer is: Transferring information to Manufacturing reduces data entry. The item transfer occurs at the organization level.



Quiz

Answer: 1



Summary


