Oracle® MRP: User's Guide Release 12.1

Oracle MRP
User's Guide
Release 12.1
Part No. E15188-05
July 2013
Oracle MRP User's Guide, Release 12.1

Part No. E15188-05
Copyright 2009, 2013, Oracle and/or its affiliates. All rights reserved.
Primary Author: Margot Murray, Tom Myers
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation
of the programs, including any operating system, integrated software, any programs installed on the
hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the
programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
This software or hardware and documentation may provide access to or information on content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your
access to or use of third-party content, products, or services.

Contents
Send Us Your Comments

Preface
1
Setting Up
Overview of Setting Up............................................................................................................. 1-1
Related Product Setup Steps..................................................................................................... 1-1
Setup Checklist.......................................................................................................................... 1-4
Setup Steps................................................................................................................................ 1-6
Supply Chain Planning Setup Steps...................................................................................... 1-12
Defining Planning Parameters................................................................................................ 1-13
Starting the Planning Manager............................................................................................... 1-16
Defining Planners................................................................................................................... 1-17
Creating Planning Exception Sets........................................................................................... 1-17
Creating Demand Classes....................................................................................................... 1-19
Creating Source Lists............................................................................................................... 1-21
Setting Up Planner Workbench.............................................................................................. 1-22
Setting Up Line Scheduling Workbench................................................................................ 1-24
Changing Your Organization.................................................................................................. 1-25
Profile Options........................................................................................................................ 1-25
Forecasting
Overview of Forecasting ...........................................................................................................2-1
Generating Forecasts from Historical Information.................................................................. 2-4
Defining Forecast Sets............................................................................................................... 2-6
Defining Forecasts..................................................................................................................... 2-7
iii
Copying and Merging Forecasts .............................................................................................. 2-9

Reviewing Forecast Detail Information ................................................................................. 2-11
Reviewing Bucketed Information .......................................................................................... 2-12
Forecast Consumption............................................................................................................. 2-13
Forecast Consumption Considerations................................................................................... 2-19
Time Buckets in Forecast Consumption................................................................................. 2-20
Time Bucket Considerations................................................................................................... 2-24
Tracking Forecast Consumption............................................................................................. 2-25
Forecast Explosion................................................................................................................... 2-26
Forecast Explosion Considerations ........................................................................................ 2-28
Configure to Order Models..................................................................................................... 2-28
Configure to Order Forecast Control...................................................................................... 2-30
Configure to Order Forecast Control Considerations............................................................ 2-33
Configure to Order Forecast Explosion.................................................................................. 2-36
Configure to Order Forecast Explosion Considerations.........................................................2-38
Configure to Order Forecast Consumption............................................................................ 2-39
Master Scheduling
Overview of Master Scheduling............................................................................................... 3-1
Master Demand Schedule......................................................................................................... 3-2
Master Production Schedule (MPS) ......................................................................................... 3-2
Main Features of Master Scheduling ....................................................................................... 3-3
Defining a Schedule Name ...................................................................................................... 3-6
Defining Schedule Entries Manually ...................................................................................... 3-7
Loading a Master Schedule from an Internal Source............................................................... 3-9
Interorg Planned Orders .........................................................................................................3-10
Specific MDS or Specific MPS ...............................................................................................3-11
Selecting Master Schedule Load Options .............................................................................. 3-12
Additional Factors Affecting a Master Schedule Load ..........................................................3-14
How Forecasted Discrete Items Appear in the Master Schedule........................................... 3-15
How Forecasted Repetitive Items Appear in the Master Schedule........................................3-17
Planning Spares Demand ....................................................................................................... 3-19
Schedule Relief........................................................................................................................ 3-20
Viewing Master Schedule Relief Information ...................................................................... 3-21
Profile Options for Master Schedule Relief .......................................................................... 3-22
Planning Manager and Schedule Relief ................................................................................ 3-22
Tracking Demand Schedule Reliefs ...................................................................................... 3-23
Rough Cut Capacity Planning................................................................................................. 3-24
iv
Material Requirements Planning

Overview of Material Requirements Planning ....................................................................... 4-1
Overview of Planning Logic .................................................................................................... 4-2
MRP Planning Methods in Oracle Inventory .......................................................................... 4-3
Overview of Plan Generation .................................................................................................. 4-5
MPS Plan Generation ............................................................................................................... 4-5
MRP Generation ....................................................................................................................... 4-6
Defining MRP Names .............................................................................................................. 4-6
Launching the Planning Process .............................................................................................. 4-7
Making a Copy of a Completed Plan ....................................................................................... 4-8
Reviewing or Adding Plan Options .......................................................................................4-10
Order Modifier........................................................................................................................ 4-13
Item and Bill of Material Attributes ...................................................................................... 4-16
Standard Bills and Routings Only ......................................................................................... 4-17
Phantom Bills of Material ...................................................................................................... 4-17
Manufactured or Purchased ................................................................................................... 4-17
Bulk Items ............................................................................................................................... 4-18
Shrinkage Rate ....................................................................................................................... 4-19
Component Yield .................................................................................................................... 4-20
Safety Stock ............................................................................................................................ 4-20
Lot Expirations ........................................................................................................................ 4-21
Overview of Plan Control ...................................................................................................... 4-22
Time Fence Control ................................................................................................................ 4-24
Release Time Fence ................................................................................................................ 4-24
Auto-Release Planned Orders ................................................................................................ 4-25
Firm Order Planning .............................................................................................................. 4-27
Overwrite Options .................................................................................................................. 4-28
Overwrite Outside Planning Time Fence Append Planned Orders ..................................... 4-30
Overwrite None Append Planned Orders ............................................................................. 4-31
Overwrite None Do Not Append Planned Orders ................................................................ 4-32
Gross to Net Explosion ........................................................................................................... 4-34
Phases of the Planning Process .............................................................................................. 4-35
Locking Tables within the Snapshot ..................................................................................... 4-37
Locking Tables within the Snapshot Example ...................................................................... 4-37
Specifying Items for the Planning Process ............................................................................ 4-39
Material Scheduling Method Example .................................................................................. 4-40
Netting Supply and Demand ................................................................................................. 4-40
Net Purchases ......................................................................................................................... 4-41
Planning Dates ....................................................................................................................... 4-42
Receiving Inspection Inventory ............................................................................................. 4-42

Internal Requisitions .............................................................................................................. 4-42
Net Work in Process ............................................................................................................... 4-43
Standard Discrete Jobs ........................................................................................................... 4-43
Non-Standard Discrete Jobs ................................................................................................... 4-43
Repetitive Schedules .............................................................................................................. 4-44
Net Reservations ..................................................................................................................... 4-45
Overview of Engineering Change Planning .......................................................................... 4-46
Engineering Change Orders ................................................................................................... 4-46
Supply Chain Planning

Overview................................................................................................................................... 5-1
The Multiple Organization Model .......................................................................................... 5-3
Supply Chain Supply and Demand Schedules........................................................................ 5-5
Setting Up the Supply Chain.................................................................................................... 5-8
Displaying an Indented Where Used..................................................................................... 5-23
Displaying an Indented Bill.................................................................................................... 5-24
Viewing the Sourcing Assignment Hierarchy........................................................................ 5-25
Material and Distribution Requirements Planning............................................................... 5-25
Overview of Supply Chain Planning Logic............................................................................5-27
Defining MRP and DRP Names in Supply Chain Planning................................................. 5-31
Launching the Supply Chain Planning Process..................................................................... 5-31
Reviewing or Adding Supply Chain Plan Options................................................................ 5-32
Overview of Plan Generation in Supply Chain Planning .................................................... 5-36
MPS Plan Generation in Supply Chain Planning.................................................................. 5-39
MRP and DRP Generation in Supply Chain Planning.......................................................... 5-40
Planning Organizations.......................................................................................................... 5-43
Netting Supply and Demand in Supply Chain Planning...................................................... 5-44
Overview of the Supply Chain Planner Workbench............................................................. 5-45
Reviewing Source and Destination Organizations................................................................ 5-46
Supply Chain Master Schedule Types................................................................................... 5-48
Defining a Supply Chain MPS Name.....................................................................................5-49
Defining Supply Chain MPS Entries Manually.....................................................................5-50
Loading a Supply Chain MPS from an Internal Source.........................................................5-51
Planner Workbench
Overview of Planner Workbench............................................................................................. 6-1
Quick Access to Particular Documents .................................................................................... 6-2
Reviewing Planning Information ............................................................................................ 6-2
Reviewing Item Planning Information .................................................................................... 6-4
vi
Viewing On-hand Quantities ...................................................................................................6-5

Reviewing Supply and Demand .............................................................................................. 6-5
Supply and Demand Fields ...................................................................................................... 6-6
Reviewing the Horizontal Plan .............................................................................................. 6-10
Displaying the Enterprise View ............................................................................................. 6-11
Reviewing Current Data ......................................................................................................... 6-12
Generating a Graphical Display of Planning Data ............................................................... 6-13
Reviewing Planning Exceptions ............................................................................................ 6-13
Planning Exception Sets ......................................................................................................... 6-17
Overview of Net Change Replan ........................................................................................... 6-18
Batch Mode Planner ............................................................................................................... 6-19
Replanning Net Changes - Batch Mode Planner ................................................................... 6-20
Replanning Net Changes-Online Planner ............................................................................. 6-21
Overview of Graphical Pegging ............................................................................................. 6-23
Available to Promise............................................................................................................... 6-26
Calculating ATP ..................................................................................................................... 6-26
Calculating ATP for Product Family Items ............................................................................ 6-27
Negative ATP .......................................................................................................................... 6-28
Inventory Snapshot ................................................................................................................ 6-29
Supply Chain ATP.................................................................................................................. 6-29
Capable to Promise.................................................................................................................. 6-30
Implementing Planning Recommendations .......................................................................... 6-32
Creating Firm Planned Orders ............................................................................................... 6-33
Implementing Planned Orders .............................................................................................. 6-34
Error Message Processing ....................................................................................................... 6-36
Implementing Repetitive Schedules ......................................................................................6-38
Implementing Planned Orders as Firm Jobs ......................................................................... 6-39
How Purchase Requisitions are Created ................................................................................6-41
Rescheduling Scheduled Receipts ......................................................................................... 6-41
Walking Up and Down a Bill of Material .............................................................................. 6-42
Reviewing Assembly Components ........................................................................................ 6-43
End Assembly Pegging ........................................................................................................... 6-44
Reviewing Using Assemblies ................................................................................................ 6-44
Reviewing End Assemblies .................................................................................................... 6-45
Capacity Planning .................................................................................................................. 6-45
Capacity Requirements Planning........................................................................................... 6-45
Viewing Capacity Information from the Planner Workbench ..............................................6-46
Identifying Capacity Problems .............................................................................................. 6-48
Testing What-if Scenarios ...................................................................................................... 6-49
Plan Status .............................................................................................................................. 6-50
vii
Demand Classes
Overview of Demand Classes................................................................................................... 7-1
Demand Class Forecasting ....................................................................................................... 7-2
Forecast Consumption .............................................................................................................. 7-3
Demand Class Master Scheduling ........................................................................................... 7-5
Demand Class ATP Calculation ............................................................................................... 7-6
Net Inventory by Demand Class .............................................................................................. 7-6
Time Fence Control

Overview of Time Fence Planning........................................................................................... 8-1
Time Fences for Items ......................................................................................................... 8-1
Master Schedule Creation Using the Demand Time Fence ................................................. 8-1
Material Planning with the Demand and Planning Time Fences ........................................ 8-1
Material Planning with the Release Time Fence ..................................................................8-2
Time Fence Control .................................................................................................................. 8-2
Master Schedule Load .............................................................................................................. 8-5
Planning Process Execution ...................................................................................................... 8-6
Master Production Schedule Maintenance .............................................................................. 8-6
Production Plan Monitoring .................................................................................................... 8-7
Time Fence Planning Example ................................................................................................. 8-8
Two-Level Master Scheduling

Overview of Two-Level Master Scheduling............................................................................. 9-1
Production Planning.................................................................................................................. 9-3
Example Bill of Material for Two-Level Master Scheduling .................................................. 9-4
Forecasting Planning Bills ........................................................................................................ 9-7
Forecasting Models ................................................................................................................... 9-8
Forecasting Predefined Configurations ................................................................................. 9-10
10
Repetitive Planning
Overview of Repetitive Planning .......................................................................................... 10-1
Overview of Repetitive Planning Concepts .......................................................................... 10-2
MPS and MRP Planning for Repetitive Assemblies ............................................................. 10-6
Safety Stock and Order Modifiers ......................................................................................... 10-7
Anchor Date ............................................................................................................................ 10-9
Repetitive Schedule Allocation .............................................................................................. 10-9
Firm Repetitive Schedules ................................................................................................... 10-10
Repetitive Planning Control ................................................................................................ 10-12
viii
Repetitive Schedule Relief ................................................................................................... 10-14

Repetitive Schedule Implementation .................................................................................. 10-14
11
Reports
Overview of Reports............................................................................................................... 11-1
Audit Information Report....................................................................................................... 11-1
Current Projected On Hand vs. Projected Available Graphical Report for Supply Chain
Planning................................................................................................................................... 11-7
Demand vs. Replenishment Graphical Report for Supply Chain Planning....................... 11-10
Financial Analysis Report for Supply Chain Planning........................................................11-13
Forecast Comparison Report ................................................................................................ 11-14
Forecast Detail Report........................................................................................................... 11-18
Late Order Report for Supply Chain Planning.....................................................................11-21
Master Schedule Comparison Report................................................................................... 11-23
Master Schedule Detail Report............................................................................................. 11-26
Master Schedule Status Report for Supply Chain Planning................................................11-30
Planning Manager Worker once-a-day tasks........................................................................ 11-32
Planning Parameters Report................................................................................................. 11-33
CRP Reports........................................................................................................................... 11-33
Order Reschedule Report for Supply Chain Planning.........................................................11-33
Planned Order Report for Supply Chain Planning.............................................................. 11-36
Planning Detail Report for Supply Chain Planning............................................................ 11-39
Planning Exception Sets Report ........................................................................................... 11-43
12
Kanban Planning
Overview of Kanban Planning .............................................................................................. 12-1
Using the Kanban Calculation Program ................................................................................ 12-5
Viewing and Updating Kanban Calculations.........................................................................12-8
Kanban Tools Menu.............................................................................................................. 12-10
13
Project MRP
Overview of Project MRP ....................................................................................................... 13-1
Establishing a Project MRP Environment ............................................................................. 13-2
Overview of Project MRP Setup Tasks...................................................................................13-2
Setting Up Project MRP in Oracle Projects.............................................................................13-3
Setting Up Project MRP in Oracle Inventory......................................................................... 13-3
Setting Up Project MRP in MRP ............................................................................................ 13-5
Reviewing or Adding Project MRP Plan Options Prerequisite ............................................ 13-6
Launching a Project MRP Plan................................................................................................13-7
Setting Up Project MRP in Oracle Project Manufacturing ....................................................13-7
ix
Project MRP Planning Logic .................................................................................................. 13-8

Project Netting Example for Hard Pegging............................................................................ 13-8
Project Netting Example for Soft Pegging............................................................................ 13-10
Netting Behavior .................................................................................................................. 13-11
14
Parallel Processing
Overview of Parallel Processing............................................................................................. 14-1
Process Control........................................................................................................................ 14-1
Inter-process Communication................................................................................................. 14-2
Single Processor Machine....................................................................................................... 14-2
Snapshot.................................................................................................................................. 14-4
Snapshot Parallel Processing.................................................................................................. 14-8
Planner Parallel Processing..................................................................................................... 14-8
Planning Manager................................................................................................................... 14-9
Tools Menu
Tools Menu............................................................................................................................... A-1
Windows and Navigator Paths

Windows and Navigator Paths................................................................................................. B-1
Alerts
Alerts ........................................................................................................................................ C-1
Customized Find Windows

Customized Find Windows ..................................................................................................... D-1
Workflow - Planning Exception Messages

Planning Exception Messages Workflow................................................................................. E-1
Forecasting - Statistical and Focus

Forecasts - Statistical and Focus................................................................................................ F-1
Memory-based Planning Engine

Memory-based Planning Engine.............................................................................................. G-1
Configuring the Memorybased Planning Engine................................................................ G-12
Character Mode Forms and GUI Windows

Character Mode Forms and Corresponding GUI Windows ................................................... H-1
Glossary
Index
xi

Send Us Your Comments
Oracle MRP User's Guide, Release 12.1
Part No. E15188-05
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
Are the implementation steps correct and complete?

Did you understand the context of the procedures?
Did you find any errors in the information?
Does the structure of the information help you with your tasks?
Do you need different information or graphics? If so, where, and in what format?
Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
xiii

Preface
Intended Audience
Welcome to Release 12.1 of the Oracle MRP User's Guide.
Casual User and Implementer
See Related Information Sources on page xvi for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Structure
1 Setting Up
2 Forecasting
3 Master Scheduling
4 Material Requirements Planning
5 Supply Chain Planning
6 Planner Workbench
7 Demand Classes
8 Time Fence Control
9 Two-Level Master Scheduling
10 Repetitive Planning
xv
11 Reports
12 Kanban Planning
13 Project MRP
14 Parallel Processing
A Tools Menu
B Windows and Navigator Paths
C Alerts
D Customized Find Windows
E Workflow - Planning Exception Messages
F Forecasting - Statistical and Focus
G Memory-based Planning Engine
H Character Mode Forms and GUI Windows
Glossary
Related Information Sources

Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your
instance is patched, the repository is automatically updated with content appropriate
for the precise revisions of interfaces in your environment.
You can navigate to the Oracle Integration Repository through Oracle E-Business Suite
Integrated SOA Gateway.
Online Documentation
All Oracle E-Business Suite documentation is available online (HTML or PDF).
xvi
Online Help - Online help patches (HTML) are available on My Oracle Support.
PDF Documentation - See the Oracle E-Business Suite Documentation Library for
current PDF documentation for your product with each release. The Oracle
E-Business Suite Documentation Library is also available on My Oracle Support and
is updated frequently.
Release Notes - For information about changes in this release, including new
features, known issues, and other details, see the release notes for the relevant
product, available on My Oracle Support.
Oracle Electronic Technical Reference Manual - The Oracle Electronic Technical

Reference Manual (eTRM) contains database diagrams and a detailed description of
database tables, forms, reports, and programs for each Oracle E-Business Suite
product. This information helps you convert data from your existing applications
and integrate Oracle E-Business Suite data with non-Oracle applications, and write
custom reports for Oracle E-Business Suite products. The Oracle eTRM is available
on My Oracle Support.
Related Guides
User Guides Related to All Products
Oracle E-Business Suite User's Guide
Oracle Alert User Guide
Oracle E-Business Suite Developer's Guide
Oracle E-Business Suite User Interface Standards for Forms-Based Products
Oracle E-Business Suite Flexfields Guide
Oracle Workflow Developer's Guide
User Guides Related to This Product
Oracle Bills of Material User's Guide
Oracle Capacity User's Guide
Oracle Flow Manufacturing User's Guide
Oracle Inventory User's Guide
Oracle Order Management User's Guide
Oracle Project Manufacturing User's Guide
Oracle Purchasing User's Guide
Oracle Supplier Scheduling User's Guide
Oracle Work in Process User's Guide
Installation and System Administration Guides
Oracle E-Business Suite Concepts
Oracle E-Business Suite Installation Guide: Using Rapid Install
The Oracle E-Business Suite Upgrade Guides
xvii
Oracle E-Business Suite Setup Guide
Oracle E-Business Suite Maintenance Guide
Oracle E-Business Suite Security Guide
Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle E-Business Suite data
unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of
your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an
Oracle E-Business Suite form can update many tables at once. But when you modify
Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you
may change a row in one table without making corresponding changes in related tables.
If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite
automatically checks that your changes are valid. Oracle E-Business Suite also keeps
track of who changes information. If you enter information into database tables using
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.
xviii
1
Setting Up
Overview of Setting Up
This section contains an overview of each task you need to complete to set up Oracle
MRP.
Before you set up , you should:
Set up an Oracle Applications System Administrator responsibility. See: System

Administration Setup Tasksr, Oracle E-Business Suite Setup Guide.
Set up your Oracle Applications Set of Books. See: Defining Sets of Books, Oracle
General Ledger User's Guide.
Related Product Setup Steps

Set Up Oracle Applications Technology
The setup steps in this chapter tell you how to implement the parts of Oracle
Applications specific to.
You need to complete several setup steps, including:
Performing system-wide setup tasks such as configuring concurrent managers and

printers
Managing data security, which includes setting up responsibilities to allow access

to a specific set of business data and complete a specific set of transactions, and
assigning individual users to one or more of these responsibilities
Also, if your product uses Oracle Workflow to, for example, manage the approval of
business documents or to derive Accounting Flexfield values via the Account
Generator, you need to set up Oracle Workflow.
See also Oracle E-Business Suite Setup Guide, Oracle E-Business Suite Maintenance Guide,
Setting Up 1-1
Oracle E-Business Suite Concepts, Oracle E-Business Suite Security Guide, and Oracle
Workflow Guide
Oracle Inventory
Make sure you set up Inventory as described in Overview of Setting Up, Oracle
Inventory User's Guide. Ensure that all the following steps have been completed:
Define your planners.
Define your unit of measure conversions.
Define your item planning information.
If you manufacture your assemblies repetitively ensure that you define your
repetitive planning information.
If you operate in a project-based environment, add pegging levels for Project

Manufacturing.
If you operate in a Flow Manufacturing environment, define items for products,

parts, and optionally, assign members to a product family.
Oracle Purchasing
Make sure you set up Purchasing as described in Overview of Setting Up, Oracle
Purchasing User's Guide. Ensure that all the following steps have been completed:
Define financial options
Define locations
Set up personnel
Define buyers
Set up approval information
Oracle Bills of Material

Make sure you set up Bills of Material as described in Overview of Setting Up, Oracle
Bills of Material User's Guide. In addition to the set up, ensure that all the following steps
have been completed:
Define your organization calendar
Define your bills of material
Define your routings

Define flow routings, items need to be associated to lines through routings
1-2 Oracle MRP User's Guide
Calculate your routing lead times
Define resources
Oracle Work in Process

Make sure you set up Work in Process as described in Overview of Setting Up, Oracle
Work in Process User's Guide. Ensure that all the following optional steps have been
completed:
Define your production lines
Define your repetitive assemblies if you manufacture your assemblies repetitively
Define production lines and line rates for flow schedules if you have a Flow
Manufacturing environment
Oracle Capacity
Make sure you set up Capacity as described in Overview of Setting Up, Oracle Capacity
User's Guide. Ensure that all the following optional steps have been completed:
Define simulation sets
Define resource groups
Define and load bill of resources
Set profile options
Oracle Project Manufacturing

If you work in a projectbased environment, perform the following additional steps to
use Oracle Project Manufacturing:
Perform setup steps in Oracle Projects. See: Setting Up Project MRP in Oracle
Projects.
Perform setup steps in Oracle Inventory
See: Setting Up Project MRP in Oracle Inventory
Perform setup steps in . See: Defining Planning Group Lookups
Perform setup steps in Oracle Project Manufacturing. See: Setting Up Project MRP
in Oracle Project Manufacturing
Oracle Workflow
You can use the Enabled Exception Messages workflow to generate and distribute
messages to those who are the contacts for specific job tasks in order to resolve
problems. See: Setting Up Oracle Workflow, Oracle Workflow Guide.
Setting Up 1-3
Setup Checklist
Complete the following steps, in the order shown, to set up Oracle MRP:
Setup Checklist
Step
Required
Title
Required
Set Up System Administrator
Required
Set Up Key Flexfields
Required
Set Up Calendars, Currencies,

and Set of Books
Required
Set Up Organizations
Optional
Set Up Supplier Planned

Inventories
Optional
Define your Locations
Optional
Define your Employees
Required
Define your Planning

Parameters
Optional
Define your Planning

Exception Sets
10
Optional
Define your Demand Classes
11
Optional
Define your Planners
12
Optional
Define Source Lists
13
Required
Set Up Planner Workbench
14
Optional
Set Up Capacity
15
Required with Defaults
Set Profile Options
Step
Required
Title
16
Optional
Define your Forecast Sets
17
Optional
Define Forecast Rules
18
Optional
Define your MDS Names
19
Optional
Load MDS
20
Optional
Define your MPS Names
21
Optional
Define MPS Options
22
Optional
Define your MRP Names
23
Optional
Define MRP Options
24
Optional
Set Up Workflow Options
25
Optional
Define Shipping Methods
26
Optional
Define Intransit Lead Times
27
Optional
Create your Assignment Sets
28
Optional
Define your Sourcing Rules or

Bills of Distribution
29
Optional
Define your
Inter-organization Shipping
Network
30
Optional
Set Up Supply Chain ATP
31
Optional
Set Up Supply Chain CTP
32
Optional
Define your DRP Names
33
Optional
Define DRP Options
Setting Up 1-5
Step
Required
Title
34
Required
Start the Planning Manager

(Required)
35
Optional - Highly
Recommended
Run the Information Audit
Setup Steps
Step 1 Set Up System Administrator (Required)
This step involves the following tasks:
Define responsibilities. See: Oracle E-Business Suite Setup Guide.
Set up printers (optional). See: Setting Up Your Printers, Oracle E-Business Suite
Setup Guide.
Step 2 Set Up Key Flexfields (Required)

If you are, or will be, fully installing other applications, such as Oracle Human Resource
Management or Oracle Inventory, be sure to coordinate with those products' flexfield
setup before defining the key flexfields here, as it is not recommended to change
flexfields frequently. See: Oracle Applications Flexfields Guide.
For each key flexfield, you perform the following tasks, some of which are optional for
some flexfields:
Define the flexfield structure
Define value sets
Define flexfield segments
Define flexfield segment values
Define security rules
Assign security rules
Define roll-up groups
Define cross-validation rules

Set up the following Accounting flexfield. You may not need to perform this step if
you have already installed and set up Oracle General Ledger or performed a
commonapplications setup. See also: Oracle General Ledger User's Guide.

Set up the following Human Resources key flexfields. You may not need to set up
these key flexfields if you have already installed and set up Oracle Human
Resource Management Systems or performed a common-applications setup. See
also: Oracle Human Resources User's Guide.
Grade flexfield
Job flexfield
Position flexfield
People Group flexfield
Set up the following Inventory key flexfields. You may not need to set up these key
flexfields if you have already installed and set up Oracle Inventory or performed a
common-applications setup. See also: Oracle Inventory User's Guide.
Item Catalog flexfield
Item Category flexfield
System Items flexfield. After you set up the System Items flexfields and compile
them, the item flexfield view concurrent program is submitted automatically.
Stock Locator flexfield
Sales orders flexfield

Note: Even if you do not use item catalogs, stock locators, or sales
orders, you must still compile the respective flexfields because all
Oracle Inventory transactions (such as the Define Items window),
inquiries, and reports require a frozen flexfield definition. However,
you do not need to configure the flexfield in a specific way.
Step 3 Set Up Calendars, Currencies, and Set of Books (Required)

If you have defined your calendars, currencies, and set of books while setting up a
different Oracle Applications product, proceed to the next step. However, if you are
performing a Multi-Org implementation of Oracle MRP, see the note below.
Context: If you are performing a Multi-Org implementation, you may optionally create
more than one calendar, currency, or set of books. See: Multiple Organizations in Oracle
Applications.
This step involves the following tasks:
Set up calendars:
Setting Up 1-7
Define period types. See: Defining Period Types, Oracle General Ledger User's Guide.
Define accounting calendar. See: Defining Calendars, Oracle General Ledger User's
Guide.
Define transaction calendar. See: Defining Transaction Calendars, Oracle General

Ledger User's Guide. (Optional)
Define workday calendar. See: Overview of Workday Calendar, Oracle Bills of

Material User's Guide. (Optional)
Define exception templates. See: Creating a Workday Exception Template, Oracle

Bills of Material User's Guide. (Optional)
Define currencies. See: Defining Currencies, Oracle General Ledger User's Guide.
Define conversion rate types. See: Defining Conversion Rate Types, Oracle General
Ledger User's Guide.
Assign your set of books to a responsibility. See: Oracle General Ledger User's Guide.
Set up currency rates.
Set up accounting code combinations. See: Oracle General Ledger User's Guide.
Open and close accounting periods. See: Opening and Closing Accounting Periods,
Oracle General Ledger User's Guide.
Step 4 Set Up Organizations (Required)

You may not need to perform this step if you have already installed and set up Oracle
Inventory or performed a common-applications setup.
For the following tasks relating to setting up organizations, see: Oracle Human Resources
User's Guide.
Define organization QuickCodes
Define business groups, if you want to define new business groups rather than
using the default Setup Business Group. See the section View-all Responsibility in:
Setting Up Security for Applications Using Some HRMS Windows, Oracle Human
Resources User's Guide.
Define organizations
Define human resources organizations
Define legal entities organizations
Define Oracle users for operating-unit organizations
Assign operating units to legal entities
Set up inventory organizations. For the tasks relating to setting up inventory

organizations, see: Oracle Inventory User's Guide
Define organization hierarchies. See: Oracle Human Resources User's Guide
Assign business groups and operating units to responsibilities. Make sure that the
profile option HR: Business Group is set at the responsibility level to the business
group you want to use for that responsibility. See: Oracle Human Resources User's
Guide
Step 5 Set up Supplier Planned Inventories (Optional)

For instructions on setting up for Supplier Planned Inventories, see the Prerequisites in:
Supplier Planned Inventories.
Step 6 Define Locations (Required)
If you're also setting up other Oracle applications, you may already have defined
locations when you set up those applications.
In Oracle Purchasing, define locations for where you ship, deliver internally, or bill the
goods and services you order. This is a necessary setup if you plan on importing
purchase requisitions from the Planner Workbench into Oracle Purchasing. See: Setting
Up Locations, Oracle Human Resources User's Guide.
Step 7 Define your Employees (Optional)
If you do not install Oracle Human Resource Management Systems with Oracle MRP,
you use the Enter Employee form to define and maintain employees in Oracle MRP.
Otherwise, the forms in Oracle Human Resource Management Systems are used to
enter and maintain employees.
Define every employee who:
Creates requisitions or purchase orders
Authorizes the purchase of goods and services
Receives goods or services
This is a necessary setup if you plan on importing purchase requisitions from the
Planner Workbench into Oracle Purchasing.
Step 8 Define your MRP Planning Parameters (Required)
You need to define different modes of operation and default values that affect other
functions in Oracle MRP. If you manufacture your assemblies repetitively, you can also
set up your repetitive item defaults. See: Defining Planning Parameters.
Setting Up 1-9
Step 9 Create your Planning Exception Sets (Optional)

You can define and update planning exception sets that you can use to identify items
and orders that require attention based upon a set of predefined action messages. This
facilitates control over message sensitivity, message priority, and marking those
messages where action has been taken. See: Creating Planning Exception Sets
Step 10 Create your Demand Classes (Optional)
You can define and update demand classes to group similar customers, demand
channels or sales order types. You can use demand classes as a means of forecasting and
master scheduling different sources of demand separately. See: Creating Demand
Classes.
Step 11 Define your Planners (Optional)
For instructions on defining your planners. See: Defining Planners.
Step 12 Create Source Lists (Optional)
For instructions on creating source lists. See: Creating Source Lists.
Step 13 Set up Planner Workbench (Required)
For instructions on setting up Planner Workbench, see: Setting Up Planner Workbench.
Step 14 Set up Capacity (Optional)
For instructions on setting up Oracle Capacity. See: Set Up Steps, Oracle Capacity User's
Guide.
Step 15 Set Profile Options (Required with Defaults)
Profile options specify how controls access to and processes data. In general, profile
options can be set at one or more levels. System administrators use the Profile Options
form to set profile options at the site, application, responsibility, and user levels.
Oracle MRP users use the Profile Options form to set profile options only at the user
level. You can update your personal profile options if you want to override the defaults
provided by Oracle MRP. Personal profiles allow you to control data access and
processing options at the user level.
For more information about the profile options available in Oracle MRP, see: Oracle
MRP Profile Options.
Step 16 Define your Forecast Sets (Optional)
You can define any number of forecast sets or names. This allows you to define any
number of forecasts, including different types of forecasts, such as by customer or by
item. For each forecast set, you can also specify the number of days that a sales order
looks to consume the forecast and the minimum level of forecast information required
to consume the forecast. See: Defining a Forecast Set
Step 17 Define your Forecast Rules (Optional)
You can define forecast rules to establish the forecast method, bucket type, and sources
of demand that are considered when compiling statistical or focust forecasts. See:
Defining a Forecast Rule, Oracle Inventory User's Guide.

Step 18 Define your MDS Names (Optional)
Define any number of demand schedule names; this allows you to define multiple
master demand schedules, each with a unique name. A master demand schedule is a
statement of anticipated demand that you can use to create a master production
schedule, or as direct input to a material requirements plan. For each master demand
schedule name, you can also signify if sales order shipments relieve the schedule. See:
Defining a Schedule Name.
Step 19 Load MDS (Optional)
For each type of master demand schedule load, you choose a number of load options.
Not all options apply to all load types. See, Loading a Master Schedule from an Internal
Source.
Step 20 Define your MPS Names (Optional)
Define any number of production schedule names; this allows you to define multiple
master production schedules, each with a unique name. A master production schedule
defines the anticipated build schedule for the product family members and other critical
items. For each master production schedule name, you can also signify if the creation of
jobs/repetitive schedules relieves the schedule. See: Defining a Schedule Name.
Step 21 Define MPS Options (Optional)
You can optionally include your MPS plan as available supply and get information on
quantities that have been implemented as discrete jobs, purchase orders, or purchase
requisitions. See: Defining a Schedule Name.
Step 22 Define your MRP Names (Optional)
Define any number of material requirements plan names. This allows you to generate
multiple MRP plans, each with a unique name. A material requirements plan defines a
set of recommendations to release or reschedule orders for material based on the net
material demands. See: Defining MRP Names.
Step 23 Define MRP Options (Optional)
Material requirements planning (MRP) calculates net requirements from gross
requirements by evaluating: the master schedule, bills of material, scheduled receipts,
onhand balances, and lead times. See: Overview of Material Requirements Planning.
Step 24 Set Up Workflow Options (Optional)
You can use Oracle Workflow technology to handle exception messages by routing
them to personnel who have specific job responsibilities in planning. Workflow runs in
the background; it automates the generation and distribution of these messages. See
Oracle Workflow Guide.
Setting Up 1-11
Supply Chain Planning Setup Steps

Step 25 Define Shipping Methods (Optional)
The Shipping Method code defines specific shipping methods. For example: Ground,
Express, or Air. See: Defining Shipping Methods, Oracle Inventory User's Guide.
Step 26 Associate Shipping Methods with Lead Times (Optional)
You can associate shipping methods with lead times in the Inter-org Shipping Methods
window. See: Defining Inter-Organization Shipping Network, Oracle Inventory User's
Guide.
Step 27 Create your Assignment Sets (Optional)
Once you have defined your sourcing rules and bills of distribution, you must assign
them to particular items, categories and/or organizations. A set of such assignments is
called an assignment set. (Later, when you specify plan options for a plan, you will
choose which assignment set you want the plan to use.) See: Assigning Sourcing Rules
and Bills of Distribution.
Step 28 Define your Sourcing Rules and Bills of Distribution (Optional)
Sourcing rules specify how to replenish items in an organization. A bill of distribution
specifies a multilevel replenishment network of warehouses, distribution centers,
manufacturing centers, and trading partners. See: Defining Sourcing Rules, Defining
Bills of Distribution.
Step 29 Define your Inter-organization Shipping Network (Optional)
Inter-organization shipping network information describes the relationships and
accounting information that exists between a shipping organization and a destination
organization. See Defining Inter-Organization Shipping Networks, Oracle Inventory
User's Guide and Defining Shipping Methods, Oracle Inventory User's Guide.
Step 30 Set Up Supply Chain ATP (Optional)
Supply Chain Available to Promise enables you to view detailed availability
information from Oracle Inventory or Oracle Order Entry in order to choose which
supply source you want to use to meet the demand. See Defining Inter-Organization
Shipping Networks, Oracle Inventory User's Guide.
Step 31 Set Up Supply Chain CTP (Optional)
Capable to Promise extends Available to Promise by taking into account capacity
information. See: Capable to Promise.
Step 32 Define your DRP Names (Optional)
Define any number of distribution requirements plan names. This allows you to
generate multiple DRP plans, each with a unique name. A distribution requirements
plan defines a set of recommendations to release or reschedule orders for material
based on the net material demands. See: Defining DRP Names.
Step 33 DRP Options (Optional)

Select different options for your distribution requirements plan. The planning process
uses the input from a supply schedule or a demand schedule to determine the
quantities and timing of the items to be manufactured or purchased. See: Reviewing or
Adding Supply Chain Plan Options.
Step 34 Start the Planning Manager (Required)
You need to activate the planning manager to execute several maintenance tasks such as
forecast consumption and master schedule relief. See: Starting the Planning Manager.
Step 35 Run the Information Audit (Optional-highly recommended)
Audit the information you use to plan your master schedules and material
requirements. Information audits are primarily used to validate the integrity of your
database. For example, you can use the audit to verify the structure of your bills. Oracle
MRP provides a set of predefined audits that can be executed to verify existing data.
See: Audit Information Report.
Defining Planning Parameters

From the Planning Parameters window, you can enable planning functions. You can
also define and update execution options and default values that affect other functions
in Oracle MRP.
To define and update the enable dates and default parameters
1.
Navigate to the Planning Parameters window.
2.
Check Snapshot Lock Tables to lock tables during the snapshot process to ensure
consistent inventory on-hand quantities and order quantities.
3.
Enter a Default ABC Assignment Group to use as the default for items. See: ABC
Assignment Groups, Oracle Inventory User's Guide.
4.
In the Execution Defaults section, check Demand Time Fence Control to consider
any demand from forecasts within the demand time fence. The planning process
does not consider any demand from forecasts within the demand time fence, but
does consider demand from sales orders.
5.
Check Plan Safety Stock to calculate the safety stock for each item. Attention: You
must enter safety stock information for your items before Oracle MRP calculates
safety stock for the items. See: Defining Items, Oracle Inventory User's Guide.
6.
Check Net Purchases to consider approved purchase orders, approved purchase

requisitions, in-transit shipments, purchase orders in receiving, and internal
requisitions when planning an item. If you do not check this, the planning process
does not recommend the rescheduling of purchase orders, and may over plan the
item because it creates additional planned orders.
Setting Up 1-13
7.
Check Planning Time Fence Control to indicate whether the planning process
violates planning time fences for items. If you do not check this, the planning
process plans the items as if no planning time fences exist.
For discrete items or flow schedules, the planning process does not create
planned orders or recommend rescheduling in existing orders within the
planning time fence of the item. The planning process can still recommend
rescheduling orders out..
For repetitive items, the planning process can vary the suggested schedule from
the optimal schedule, within the planning time fence, by the acceptable rate
increase and/or decrease you specified for the item. Discretely planned items
include flow schedules
8.
Check Net WIP to consider standard discrete jobs, nonstandard discrete jobs, or
repetitive schedules when planning an item. If you do not check this, the planning
process does not recommend rescheduling of work orders, and may over plan the
item because it creates additional planned orders.
9.
Check Net Reservations to consider material reservations when planning an item. If

you do not check this, the planning process does not consider material reservations
for the item and may consider the on-hand quantity for the item available for any
demand.
10. Select a Material Scheduling Method:
Operation start date: Schedule material to arrive in inventory for availability on

the start date of a specific operation in the manufacturing process.
Order start date: Schedule material to arrive in inventory for availability on the
work in process order start date.
11. Select the planned items or components to be included in the planning process. See:
Specifying Items for the Planning Process. Supply Chain Planning users can set
additional parameters in the Plan Options window. See: Specifying Items for the
Supply Chain Planning Process.
All planned items
Demand schedule items
Supply schedule items
12. Enter a number of days before the current date to include past due MDS demand in
Include MDS Days. If you do not enter a value, the planning process considers all
past due MDS demand. If you enter zero, the planning process ignores all past due
MDS demand.
13. Save your work.
To assign and update repetitive planning parameters and other repetitive

planning defaults
Repetitive planning uses a series of repetitive planning periods (defined as repetitive
planning horizon and repetitive planning buckets) to level the production rate over
time. When planning the repetitive part, all the demand is grouped by the number of
days you specify, and the supply is averaged out over the period.
1.
2.
Select the type of dates you want to use:
Work dates: Calculate the repetitive planning periods using workdays. This
allows the periods to shift out due to holidays. If a start date falls on a holiday,
the start date is changed to the next valid working day. Each repetitive
planning period consists only of valid working days.
Calendar dates: Calculate the repetitive planning periods using calendar days.
This allows you to fix the length of the periods regardless of the timing of
holidays (non-workdays). A repetitive planning period can start on a holiday
and include holidays.
3.
Enter an Anchor Date from which to calculate the repetitive planning periods. If,
during the planning process, you change the repetitive planning anchor date, this
date is updated to the start date of the first repetitive planning period.
4.
Enter the number of workdays for the first repetitive bucket in First Bucket Days.
For example, you might enter 5 to signify that the first repetitive planning horizon
is grouped into buckets of 5 days.
5.
Enter the number of workdays for the first repetitive horizon in First Horizon. For
example, you might enter 30 to signify the first 30 days of production are grouped
into the first repetitive bucket size you specify.
6.
Enter the number of workdays for the second repetitive bucket in Second Bucket
Days. For example, you might enter 10 to signify that the second repetitive planning
horizon is grouped into buckets of 10 days.
7.
Enter the number of workdays for the second repetitive horizon in Second Horizon.
For example, you might enter 60 to signify the next 60 days of production are
grouped into the second repetitive bucket size you specify.
8.
Enter the number of workdays for the third repetitive bucket in Third Bucket Days.
For example, you might enter 40 to signify that the rest of the repetitive planning
horizon production is grouped into buckets of 40 days.
Setting Up 1-15
9.
Save your work.

See also:
Overview of Time Fence Planning
Overview of Material Requirements Planning
Starting the Planning Manager

The Planning Manager controls a continuous background process that periodically
activates for all organizations. It differs from a normal process in that you need to start
it only once. This process is activated based on the processing interval you define.
Once activated, the Planning Manager executes several maintenance tasks. For example,
the Planning Manager performs forecast consumption, MDS shipment relief, MPS
schedule relief, and forecast and master schedule imports.
Note: You should activate the Planning Manager and leave it running.
The Planning Manager performs maintenance tasks vital to the proper

operation of Oracle MRP.
Note: When it operates, the Planning Manager may run for a very short
time only, making it difficult to determine whether it is running. To be

sure, examine the log file for the concurrent request of the Planning
Manager to verify that it is active.
To start the Planning Manager and to define the processing interval

1.
Navigate to the Planning Manager window.
2.
Enter the Processing Interval for the Planning Manager.

Once you start the Planning Manager, maintenance tasks are executed based on this
interval.
3.
Choose Start to start the Planning Manager for all organizations by issuing a
request to the concurrent manager. The Planning Manager executes tasks
periodically, based on the Processing Interval you entered.
4.
Review the date and time you sent the request to the concurrent manager to start
the Planning Manager. If an error occurs during the Planning Manager maintenance
tasks, the date and time of the error is displayed.
5.
Review the Planning Manager Message associated with the date:
Started: The Planning Manager is started. The processing interval and request
identifier sent to the concurrent manager to start the Planning Manager are
displayed.
Error: An error occurred during one of the Planning Manager maintenance

tasks. Use the error message information, along with your system administrator
or Oracle Customer Support, to help diagnose the error. After you have
diagnosed and corrected the error, you must restart the Planning Manager.
Launched: The Planning Manager launched the daily cleanup worker.
Defining Planners
You can define and update material planners or planning entities for the current
organization and assign them to inventory items at the organization level. See:
Updating Organization Items, Oracle Inventory User's Guide and General Planning
Attribute Group, Oracle Inventory User's Guide.
To define and update material planners or planning entities
1.
Navigate to the Planners window.
2.
Enter a unique planner name. A planner can be a person or an entity, such as a

department or a division.
3.
Enter the electronic mail address of the planner.
4.
Optionally, enter a date on which the planner becomes inactive. From this date on,
you cannot assign this planner to an inventory item.
5.
Save your work.

See also Overview of Inventory Structure, Oracle Inventory User's Guide
Creating Planning Exception Sets

You can define and update planning exception sets to identify items, orders, and
resources that require attention based upon a set of predefined action messages. This
facilitates control over message sensitivity, message priority, and marking those
messages where action has been taken. After you have defined a planning exception set,
you can assign it to the appropriate items when you set the Exception Set attribute for
the MPS/MRP Planning group in Oracle Inventory. (If you're creating an exception set
that includes exceptions involving resources, you also need to associate the exception
set to resources in Bills of Material.) You will see exceptions based on your exception set
associated with your items, and resources.
Setting Up 1-17
To enter and update planning exception sets

1.
Navigate to the Planning Exception Sets window. You will use this window to set
the conditions under which you want to see an exception message.
2.
Select a planning exception set name to identify items, orders, and resources that
require attention based upon a set of predefined action messages.
3.
Save your work.
To enter sensitivity controls for the planning exception set

1.
Navigate to the Planning Exception Sets window.
2.
Enter an excess quantity to use with excess exceptions.
3.
Enter a repetitive variance percentage to use with repetitive variance exceptions.
4.
Enter a resource over-utilization percentage to use with capacity exceptions.
5.
Enter a user-defined time fence (in days) to use when you specify User-defined time
fence in the Exception Time Periods portion of the Planning Exception Sets
window.
6.
Save your work.
To enter exception time period types for monitoring exceptions

1.
Navigate to the Planning Exception Sets window.
2.
Enter exception time period types for monitoring different types of exceptions
within a time period.
An exception will occur only if the type of exception occurs during the specified
time period. The different types of exceptions for which you must specify a time
period type are:
Shortage Exceptions: occur when the projected on-hand quantity of the item is
negative or below safety stock.
Excess Exceptions: occur when the projected on-hand quantity of the item exceeds
zero or safety stock by more than the value you entered in Excess Quantity.
Resource Shortage Exceptions: occur when capacity is overloaded by a percentage
greater than the value entered in the Resource Overloaded field in the Sensitivity
Controls portion of the Planning Exception Sets window. For example, an exception
will occur if you entered 10% in Resource Over-utilized and capacity is overloaded
by 15%.
Resource Excess Exceptions: occur when the capacity is underloaded by a percentage
greater than the value entered in the Resource Underloaded field in the Sensitivity
Controls portion of the Planning Exception Sets window.

Overpromised Exceptions: occur when available to promise quantity for the item is
negative or below safety stock.
Repetitive Variance Exceptions: occur when the suggested aggregate repetitive
schedule differs from the current aggregate repetitive schedule by more than the
value entered in Repetitive Variance.
Note: Some exceptions only occur if you also enable pegging at the
item level (using the Pegging attribute in the MPS/MRP Planning

Group) and the plan level (using the Plan Options form). These
exceptions are: Late order due to resource shortage Late supply
pegged to forecast Late supply pegged to sales order
The different exception time periods are:

Cumulative manufacturing lead time: the processing lead time on a Make end
assembly plus the processing lead time on a Make subassembly
Cumulative total lead time: the cumulative manufacturing lead time plus the
preprocessing, processing, and postprocessing lead time on a Buy component
Planning time fence: the period starting from today's date and continuing for the
number of days specified in the Planning Time Fence item attribute
Total lead time: the preprocessing lead time plus the processing lead time on a Make
end assembly
User-defined time fence: the number of days you specify in the User-defined Time
Fence field in the Sensitivity Controls portion of the window
3.
Save your work.

See also Planning Exception Sets, Reviewing Planning Exceptions, Item Defining
Attributes, Oracle Inventory User's Guide
Creating Demand Classes

You can group similar customers or sales orders by creating demand classes. Demand
classes are a means of grouping different sources of demand separately for
consumption purposes.
When you create a forecast and/or a master schedule, you have the option of associating
a demand class with it. When you book a sales order that has an associated demand
class, the forecast consumption process searches the forecasts for entries that have the
corresponding demand class. The consumption process attempts to consume these
entries first.
The shipment of a sales order or the creation of discrete jobs within a particular demand
class causes relief to occur in any master demand schedule and master production
Setting Up 1-19
schedule that is associated with that demand class.

To create and update demand classes
1.
Navigate to the Demand Class Lookups window.
2.
Verify that the type of lookup you are creating is for a demand class.
3.
Review the Access Level to determine whether you can add new lookups or modify
existing lookups of this type:
4.
User: No restrictions on adding or modifying codes are enforced.
Extensible: New codes may be added, but you can only modify or disable
seeded codes if the application of your responsibility is the same as the
application of this lookup.
System: Only code meanings and descriptions may be modified.
Enter a unique alphanumeric code that describes a demand class. You can define a
maximum of 250 lookups for a single lookup type.
Note: You cannot change the values in this field after committing
them. To remove an obsolete lookup you can either disable the

code, enter an end date, or change the meaning and description to
match a replacement code.
5.
Enter an abbreviated meaning of the demand class.
6.
Enter an extended description of the demand class. You can display the description
along with the meaning to give more information about your lookup.
7.
Enter an effective date (in the From field) on which the demand class becomes
active.
Note: You cannot use the demand class before this date. If you do
not enter an effective date, your demand class is valid immediately.
8.
Enter a disable date (in the To field) on which this demand class expires.
Note: You cannot use the demand class after this date. Once a
demand class expires, you cannot insert additional records using

the demand class, but can query records that already use the
demand class. If you do not enter a disable date, your demand class
is valid indefinitely.
9.
Check Enabled to indicate whether the demand class is enabled. If you do not check
this, you cannot insert additional records using your demand class, but can query
records that already use this demand class.
10. Save your work.
See also Overview of Demand Classes
Creating Source Lists

To create source list
1.
Navigate to the Source List window.
2.
Enter the source list name and description.
3.
See the following table for type, source type, and button values for a source list:
4.
Select the source organization

Field values and button name for each source list window.
Window Name
Type Field Values
Source Type Field

Values
Button Name
Forecast Source List
Copy/Merge
Forecast
Load/Copy/Merge
Forecast Entries
Copy/Merge
Forecast
MDS Source List
Load/Copy/Merge
MDS
Forecast Entries
MDS Entries MPS
Entries MPS Planned
Order Demand MRP
Planned Order
Demand DRP
Planned Order
Demand
Load/Copy/Merge
MDS
MPS Source List
Load MPS
Copy/Merge MPS
Forecast Entries
MDS Entries MPS
Entries MPS Planned
Order Demand MRP
Planned Order
Demand DRP
Planned Order
Demand
Load/Copy/Merge
MPS
Setting Up 1-21
5.
Select the source forecast, forecast set, master demand schedule, or master
production schedule name(s) to create your list.
6.
Choose the Copy/Merge or Load/Copy/Merge button to open the Copy/Merge or

Load/Copy/Merge windows.
7.
Save your work.

See Also
Copying/Merging Forecasts
How Copy/Merge Finds Forecast Entries to Load
Copy/Merge for Planning Bills and Model Forecasts
Loading a Master Schedule from an Internal Source
Additional Factors Affecting a Master Schedule Load
Setting Up Planner Workbench

Before you can implement planning recommendations, you must generate at least one
MRP, DRP or MPS plan, load purchase orders and new purchase requisitions, and
assign purchasing categories and list prices.
Prerequisites for setting up Planner Workbench
To load purchase orders:
Define yourself as an employee and associate your user name to your employee entry.
See: Entering New People, Oracle Human Resources.
To load new purchase requisitions
Define at least one deliver-to location and assign this location to your organization. See:
Site Locations, Oracle Human Resources User's Guide and Representing Organizations,
Oracle Human Resources User's Guide.
To assign purchasing categories and list prices:
Assign purchasing item attributes for purchasing categories and list prices to purchased
inventory items in Oracle Inventory. See: Defining Items, Oracle Inventory User's Guide
and Defining Categories, Oracle Inventory User's Guide.
To implement planned orders as purchase requisitions:
Set requisition numbers to be generated automatically in Oracle Purchasing. See:
Overview of Purchasing Options, Oracle Purchasing User's Guide.
Defining Your Display Preferences
Display preferences control what horizontal material planning data, horizontal capacity
planning data, and supply/demand detail are displayed for each item.
To define your display preferences
1.
Navigate to the Preferences window from the Tools menu.
2.
Choose the Horizontal Material Plan tabbed region.
3.
Enter Display Bucket Type, Display Factor, Decimal Places, Field Width,
Independent Demand Type, and, optionally, Source List to define the way data is
displayed in the Horizontal Material Plan window.
4.
Check each type of plan information you want displayed in your horizontal plan.
Note: See the Oracle MRPg Glossary for descriptions of plan
information settings.
5.
Choose the Horizontal Capacity Planning tabbed region.
6.
Check each type of plan information you want displayed in your horizontal
capacity plan.
Note: See the Oracle MRP Glossary for descriptions of plan
information settings.
7.
Choose the Supply/Demand tabbed region.
8.
In the Supply/Demand tabbed region, enter a Cutoff Date, and Default Job Status.
When the Planner Workbench creates discrete jobs from implemented planned
orders, it assigns the job status you enter in the Preferences window.
9.
Select a Default Job Class. When the Planner Workbench creates discrete jobs from
implemented planned orders, it assigns the job class you enter in the Preferences
window.
Note: Default Job Status and Job Class are used as defaults in the
auto-release of planned orders process. See: Auto-release Planned

Orders.
10. Select a Requisition Load By default. When the Planner Workbench creates
purchase requisitions from implemented planned orders, it assigns the requisition

load group you enter in the Preferences window.
Note: See the Oracle MRP Glossary for descriptions of
Setting Up 1-23
supply/demand settings.
11. Choose Save to use and save your preference selections for current and subsequent
sessions.
12. Choose Apply to use your preference selections for the current session only.
13. Choose Reset to use your previously saved selections.
See Also
Users Window, Oracle Applications User's Guide
How Purchase Requisitions are Created
Reviewing the Horizontal Plan
Displaying the Enterprise View
Reviewing Supply and Demand
Overview of Job and Repetitive Schedule Statuses, Oracle Work in Process User's
Guide
Tools menu
Setting Up Line Scheduling Workbench

Before you can use the Line Scheduling Workbench functionality, you must set up your
information in several places:
Set inventory items for Flow Manufacturing
Define items, including both products and parts. Optionally, assign members to a
product family. See: Overview of Inventory Setup, Oracle Inventory User's Guide
Define a Default Discrete Class
Define Default Discrete Class in the Work in Process parameters, or WIP Accounting
Class if you have an Oracle Project Manufacturing environment. See: WIP Parameters,
Oracle Work in Processing User's Guide
See: Assigning Project Parameters, Oracle Project Manufacturing User's Guide
Define Production Lines and Line Rate
Define production lines and associated line rates for items and product families. See:
Setting Up Production Lines, Oracle Work in Processing User's Guide
Define Resources
Define resources for a flow manufacturing line. See: Overview of Flow Manufacturing
Procedures, Oracle Bills of Material User's Guide
Define Flow Routings
Items need to be associated to lines through routings. See: Creating a Flow Routing,
Run an MRP, DRP, or MPS plan if you are scheduling planned orders
This process is necessary to keep the planned order quantity in synch with the flow
schedules to prevent overstatement of demand.
Changing Your Organization

To change your organization
1.
Navigate to the Change Organization window. The Organizations Find window

displays with a listing of all valid organizations.
2.
Select an organization in the Organizations window.
3.
Choose OK.
Profile Options
This section describes the Oracle MRP profile options. In addition to descriptions, you
can see the default value and updatable level.
Implementing Profile Options Summary
The table below indicates whether you (the User) can view or update the profile option
and at which System Administrator levels the profile options can be updated: at the
user, responsibility, application, or site levels.
A Required profile option requires you to provide a value. An Optional profile option
already provides a default value, so you only need to change it if you don't want to
accept the default.
Profile
Option
User
System
Administ
rator User
System
Administ
rator Responsi
bility
System
Administ
rator Applicati
on
System
Administ
rator Site
Required
?
Default
Value
Setting Up 1-25
MRP:AT
P
Assignme
nt Set
Required
No
Default
MRP:
Calculate
Excess
Exception
s on Time
Fence
Optional
No
MRP:
Calculate
Suggeste
d
Repetitiv
e
Schedule
s
Optional
No
Default
MRP:
Compute
Sales
Order
Changes
Optional
Yes
MRP:
Consume
Forecast
Set
Summary
Optional
No
Default
MRP:
Consume
Forecast
Optional
Yes
MRP:
Consume
MDS
Optional
Yes
MRP:
Consume
MPS
Optional
Yes
MRP:
Cutoff
Date
Offset
Months
Optional
12
MRP:
Debug
Mode
Optional
No
MRP:
Default
DRP Plan
Name
Optional
No
Default
MRP:
Default
Forecast
Date
Optional
Yes
Key
You can update the profile option.
You can view the profile option but cannot change it.
You cannot view or change the profile option value.
Profile
Option
User
System
Administ
rator User
System
Administ
rator Responsi
bility
System
Administ
rator Applicati
on
System
Administ
rator Site
Required
?
Default
Value
MRP:
Default
Forecast
Name
Optional
No
Default
MRP:
Default
Plan
Name
Optional
No
Default
Setting Up 1-27
MRP:
Default
Schedule
Name
Optional
No
Default
MRP:
Default
Sourcing
Assignme
nt Set
Optional
No
Default
MRP:
Demand
Time
Fence
Days
Optional
No
Default
MRP:
Environ
ment
Variable
to Set
Path for
MRP
Files
Optional
No
Default
MRP:
Firm
Planned
Order
Time
Fence
Optional
Yes
MRP:
Firm
Requisiti
ons
within
Time
Fence
Optional
No
Default
MRP:
Include
Schedule
d
Receipts
in Use-up
Calculati
on
Optional
No
MRP:
Interface
Table
History
Days
Optional
No
Default
MRP:
Maintain
Original
Schedule
Version
Optional
No
MRP:
MPS
Relief
Batch
Size
Optional
No
Default
MRP:
MPS
Relief
Direction
Optional
Backwar
d, then
forward
MRP:
Perform
Planning
Manager
Functions
in Loads
Optional
Yes
MRP:
Plan
Revenue
Discount
Percent
Optional
Setting Up 1-29
MRP:
Plan
Revenue
Price List
Required
No
Default
MRP:
Planning
Manager
Batch
Size
Optional
No
Default
MRP:
Planning
Manager
Max
Workers
Optional
10
MRP:
Purchasi
ng by
Revision
Optional
No
Default
Key
Profile
Option
User
System
Administ
rator User
System
Administ
rator Responsi
bility
System
Administ
rator Applicati
on
System
Administ
rator Site
Required
?
Default
Value
MRP:
Purge
Batch
Size
Optional
25000
MRP:
Requisiti
on Load
Group
Option
Optional
Suppliers
MRP:
Retain
Dates
within
Calendar
Boundary
Optional
Yes
MRP:
Snapshot
Pause for
Lock
(Minutes)
Optional
MRP:
Snapshot
Workers
Optional
MRP:
Sourcing
Rule
Category
Set
Optional
No
Default
MRP:
Time
Fence
Warning
Optional
Yes
MRP:
Trace
Mode
Optional
No
MRP: Use
Direct
Load
Option
Optional
No
MRP: Use
Ship
Arrived
Flag
Optional
No
Key
Setting Up 1-31
MRP:ATP Assignment Set

Indicates the name of the assignment set to use for Supply Chain ATP.
MRP:Calculate Excess Exceptions on Time Fence
Indicates whether to calculate excess exceptions at the time fence, instead of up to the
time fence.
This profile has a predefined value of No upon installation.
MRP:Calculate Suggested Repetitive Schedules
Indicates whether to calculate and use suggested repetitive schedules to perform
forecast consumption. Available values are listed below:
Yes - Calculate and use suggested repetitive schedule information.
No - Do not calculate and use suggested repetitive schedule information.
MRP:Compute Sales Order Changes
Indicates whether to calculate and use sales order demand to perform forecast
consumption and track sales order information. Available values are listed below:
Yes - Calculate and use sales order information.
No - Do not calculate and use sales order information.
Oracle MRP predefines a value of Yes for this profile for the site upon installation. You
may set this value to No if you wish to disable forecast consumption and sales order
tracking in Oracle MRP permanently.
This profile has a predefined value of Yes for this profile for the site upon installation.
MRP:Consume Forecast Set Summary
Indicates whether to enable or temporarily disable forecast set consumption. Forecast
set consumption is the process that replaces forecasted set demand with actual demand
and is handled by the Planning Manager process. Available values are listed below:
Yes - Enable forecast set consumption. Update the forecast set when you place sales
order demand.
No - Disable forecast set consumption. Do not update the forecast set when you place
sales order demand.
MRP:Consume Forecast
Indicates whether to enable or temporarily disable forecast consumption. Forecast
consumption is the process that replaces forecasted demand with actual demand and is
handled by the Planning Manager process. Available values are listed below:
Yes - Enable forecast consumption. Update the forecast set when you place sales order
demand.
No - Disable forecast consumption. Do not update the forecast set when you place sales
order demand.
The planning manager verifies the setting of this option before performing forecast
consumption. If it is set to No, the planning manager does not update forecast entries.
The planning manager processes any sales order demand occurring while this profile is
set to No when you set the profile option back to Yes.
This profile has a predefined value of Yes upon installation.
MRP:Consume MDS
Indicates whether to enable or temporarily disable shipment relief of a master demand
schedule. Available values are listed below:
Yes - Enable shipment relief.
No - Disable shipment relief.
The planning manager verifies the setting of this option before performing shipment
relief. If it is set to No, the planning manager does not update MDS entries. The
planning manager processes any sales order shipments occurring while this profile is
set to No when you set the profile option back to Yes.
MRP:Consume MPS
Indicates whether to enable or temporarily disable production relief of a master
production schedule. Available values are listed below:
Yes - Enable production relief.
No - Disable production relief.
The planning manager verifies the setting of this option before performing production
relief. If it is set to No, the planning manager does not update MPS entries. The
planning manager processes any purchase requisitions and discrete jobs occurring
while this profile is set to No when you set the profile option back to Yes.
MRP:Cutoff Date Offset Months
Specifies the number of months from today to default the cutoff date for all forecasting,
scheduling and planning forms. Oracle MRP loads the forecast, master scheduling, and
material requirement entries from the current date up to and including this date.
MRP:Debug Mode
Indicates whether to enable debug messages within Oracle MRP. Available values are
listed below:
Yes - Enable debug messages.
No - Do not enable debug messages.
MRP:Default DRP Plan Name
Setting Up 1-33
Specifies the DRP plan name that defaults when navigating to the Plan Options
window, Plan Status window, or the Planner Workbench.
MRP:Default Forecast Date
Indicates whether to default the forecast date to the next valid day/week/period in the
Enter Forecast Entries window. Available values are listed below:
Yes - Default the forecast date to the next valid day/week/period in the Enter Forecast
Entries form.
No - Do not default the forecast date to the next valid day/week/period in the Enter
Forecast Entries form.
MRP:Default Forecast Name
Specifies the forecast name that defaults when navigating to any of the forecasting
forms.
MRP:Default Plan Name
Specifies the MRP or MPS plan name that defaults when navigating to any of the
planning forms.
MRP:Default Schedule Name
Specifies the schedule name that defaults when navigating to any of the scheduling
forms.
MRP:Default Sourcing Assignment Set
Determines the sourcing assignment set that Oracle Purchasing uses to assign sources to
requisitions.
MRP:Demand Time Fence Days
Indicates the number of time fence days for forecast set consumption and MDS (sales
order) load.
MRP:Environment Variable to Set Path for MRP Files
Specifies the appropriate path for the MRP files. If this profile is not used, the files are
written to $MRP_TOP/$APPLOUT.
This profile contains no pathname following the installation.
MRP:Firm Planned Order Time Fence
Indicates whether to form natural time fences for your MRP firm planned orders when
launching the planning process. A MRP firm planned order is an order that is frozen in
quantity and time (unavailable for rescheduling). Available values are listed below:
Yes - Form natural time fences for your MRP firm planned orders when launching the
planning process.
No - Do not form natural time fences for your MRP firm planned orders when
launching the planning process.

MRP:Firm Requisitions within Time Fence
Indicates whether to form natural time fences for your firm requisitions when
launching the planning process. Available values are listed below:
Yes - Form natural time fences for your MRP firm requisitions when launching the
planning process.
No - Do not form natural time fences for your MRP firm requisitions when launching
the planning process.
MRP:Include Scheduled Receipts in Use-up Calculation
Enables the Memory-based Planning Engine to include scheduled receipts in calculating
use-up date. The scheduled receipts included will be Discrete Jobs, Approved Purchase
Orders, Receipts, and Shipments. Purchase Requisitions and Non-Standard Jobs will be
excluded.
MRP:Interface Table History Days
Indicates the number of days that Oracle MRP saves rows in the forecast, schedule, and
workbench temporary interface tables after they have been processed.
This profile has a predefined value of 5 upon installation.
MRP:Maintain Original Schedule Version
Indicates whether to maintain the original master schedule version. The original
schedule version is the earliest copy of schedule dates and quantities, and often may not
serve a useful purpose. This gives you the ability to disable the original schedule
version if you do not intend to use it as part of your business procedures and do not
want to contend with the additional overhead required by Oracle MRP to maintain it.
If you change this profile option, you must start the concurrent manager and the
planning manager so that the new setting of the profile option is detected.
Available values are listed below:
Yes - Maintain the original master schedule version.
No - Do not maintain the original master schedule version.
Oracle MRP predefines a value of No for this profile for the site upon installation.
MRP:MPS Relief Batch Size
Indicates the batch size for production relief when relieving master production schedule
entries.
MRP:MPS Relief Direction
Setting Up 1-35
Indicates the direction in which the production relief takes place when relieving master
production schedule entries. Available values are listed below:
Backward, then Forward - Oracle Master Scheduling relieves master production
schedule entries backwards from the discrete job due date, then forwards until it finds
enough schedule quantity to relieve.
Forward only - Oracle Master Scheduling relieves master production schedule entries
only forward from the discrete job due date until it finds enough schedule quantity to
relieve.
Attention: When you change any of these profile options you must restart the planning
manager to activate the new profil option.
This profile has a predefined value of Backward, then forward upon installation.
Note: The name of this profile option in Release 10 is MRP:Relief
Directional Control.
MRP:Perform Planning Manager Functions in Loads

Ensures that the forecast and master schedule load programs perform all planning
manager functions: compute sales order changes, forecast consumption, and MDS relief.
MRP:Plan Revenue Discount Percent
Specifies the average discount percent that is applied to all items in a plan. This value is
a key performance indicator used to calculate performance in a plan for Business
Intelligence reports.
This profile can be a value between 0 and 100, decimal values are permitted.
MRP:Plan Revenue Price List
Specifies the sales order price list that is applied to items in a plan. This value is used to
calculate the plan margin key performance indicators for Business Intelligence reports.
MRP:Planning Manager Batch Size
Indicates the batch size for the number of rows in a set that the planning manager
processes. You use this profile option during a forecast and master schedule load to
determine the number of rows to process in batch. Oracle MRP also uses this profile
option during forecast consumption and master schedule relief to determine the
number of items to process.
A larger batch size is more efficient, because a process needs to make fewer database
hits. For example, if there are 1000 rows or items to process, and you have set the profile
to 100, the process needs to access the database 10 times to retrieve information on all
1000 rows or items. Setting the profile to 200 means that the process needs to access the
database only 5 times.
A smaller batch size means that the work may be divided across more workers. Using
the example above, a value of 100 means that the Planning Manager could divide the
work across 10 processes, while a value of 200 means that only 5 processes could
operate simultaneously.
MRP:Planning Manager Max Workers
Indicates the maximum number of workers to be launched by the planning manager. If
there are many rows processing, the planning manager continues to spawn more
workers, until all rows have been processed, or the number of Planning Manager
Workers running or pending matches or exceeds the value of MRP:Planning Manager
Workers.
A larger value for this profile means that the Planning Manager can use more workers
to process tasks. However, a larger value could also mean that the concurrent manager
queue becomes filled with workers, and other processes do not run.
In general, do not define a value that exceeds the maximum number of concurrent
programs that can run simultaneously.
MRP:Purchasing by Revision
Indicates whether to pass on item revision to the purchase requisition.
MRP:Purge Batch Size
Indicates the batch size for the number of rows that the planning purge process deletes
between commits. The larger the number, the faster the purge processes performs. The
lower the number, the smaller the rollback segments required.
MRP:Requisition Load Group Option
Indicates the group by option used when loading requisitions using the Planner
Workbench form. Available values are listed below:
All on one - Create one purchase requisition for all recommended orders.
Buyer - Create one purchase requisition for buyer. Within each requisition, create one
line for each planned order for the buyer.
Category - Create one purchase requisition for each category of items. Within each
requisition, create one line for each planned order for the category.
Inventory item - Create one purchase requisition for each inventory item. Within each
requisition, create one line for each planned order for the item.
One each - Create one purchase requisition for recommended order.
Planner - Create one purchase requisition for each planner. Within each requisition,
create one line for each planned order for the planner.
Supplier - Create one purchase requisition for each supplier. Within each requisition,
create one line for each planned order for the supplier.
Setting Up 1-37
MRP:Retain Dates within Calendar Boundary

Ensures that dates stay within the calendar boundary.
MRP:Snapshot Pause for Lock (Minutes)
Indicates the number of minutes to pause execution of the Snapshot process while
waiting to acquire locks on tables.
MRP:Snapshot Workers
Indicates the number of workers that are launched during the execution of the Snapshot
process. A larger value means that more tasks are performed in parallel. Too many
workers, however, can result in system degradation and diminishing performance
benefits.
In general, do not define a value for this profile that exceeds the maximum number of
concurrent programs that can run simultaneously.
MRP:Sourcing Rule Category Set
Indicates the category set used when Oracle Supply Chain Planning or Oracle
Purchasing creates sourcing assignments at category-org or category level.
MRP:Time Fence Warning
Indicates whether to receive a warning if you modify a master production schedule
within the planning time fence or master demand schedule within the demand time
fence. Available values are listed below:
Yes - Receive a warning modify a master production schedule within the planning time
fence or master demand schedule within the demand time fence.
No - Do not receive a warning if you modify a master schedule within the planning or
demand time fence.
MRP:Trace Mode
Indicates whether to enable the trace option within Oracle MRP. Available values are
listed below:
Yes - Enable the trace option within Oracle MRP.
No - Do not enable the trace option within Oracle MRP.
MRP:Use Direct Load Option
Enables the Loader Worker to use the direct load option instead of conventional loads.
This profile has a predefined value of No upon installation. You can update this profile
at all levels.
MRP:Use Ship Arrived Flag
Indicates how to treat sales orders shipped to customers. You can automatically treat
sales orders as "arrived" at a customer site after the intransit lead time has expired, or
you can manually update the ARRIVED_FLAG in SO_PICKING_HEADERS.
This profile is used by the Memory-based Planning Engine when a customer is
modelled as an organization.
This profile has a predefined value of No upon installation. Available values are listed
below:
Yes - Use arrived flag in SO_PICKING_HEADERS.
No - Use intransit time between source and the destination organizations.
See Also
Overview of User Profiles, Oracle Applications User's Guide,
Setting Your Personal User Profile, Oracle Applications User's Guide,
Common User Profile Options, Oracle Applications User's Guide,
Profile Options in Oracle Application Object Library, Oracle Applications User's

Guide
Setting Up 1-39
2
Forecasting
Overview of Forecasting
You can estimate future demand for items using any combination of historical,
statistical, and intuitive forecasting techniques. You can create multiple forecasts and
group complimenting forecasts into forecast sets.
Forecasts are consumed each time your customers place sales order demand for a
forecasted product. You can load forecasts, together with sales orders, into master
demand and production schedules, and use the master schedules to drive material
requirements planning.
Forecasts and Sets

Forecast sets consist of one or more forecasts. Sets group complimenting forecasts into a
meaningful whole. For example, a forecast set could contain separate forecasts by
region.
Forecast Set Defaults

Each forecast inherits the forecast level, consumption options, and other defaults
defined for the set. You can override these defaults for each forecast in a set.
Time Buckets
You can forecast with daily buckets in the short term, weekly buckets in the midterm,
and periodic buckets in the longer term.
Entry Options
You can define a forecast for a particular item by entering a single date and quantity.
You can also specify a start and end date, and a quantity.
Forecasting 2-1
Planning Bills and Models

You can include planning bills and models in forecasts. You can explode forecasts for
planning items and models when loading one forecast into another, or when loading a
forecast into a master schedule.
Alternate Bills
You can associate alternate bills of material to multiple forecasts for the same item,
exploding different components, usages, and planning percentages.
Consumption
You can manually or automatically consume forecasted demand with sales order
(actual) demand.
Consume by Demand Class

You can define demand classes that represent groupings of similar customers or order
types. This allows you to consume forecasts by sales orders of a specific demand class,
for example.
Consume by Item, Customer, Bill to Address, or Ship to Address

You can consume forecasts at four different forecast levels: item, customer, billto
address, or shipto address forecast level. This allows you to consume forecasts by sales
orders for a specific customer.
Copy
To help manage and consolidate your forecast information, you can create new
forecasts from existing forecasts or forecast sets. You can copy forecasts from your own
organization or from any other organization.
Modify for Simulation

You can use modification factors and/or carry forward days to modify existing
forecasts. This allows you to quickly generate forecasts, for simulation purposes, for the
same collection of items using modified forecast dates and quantities.
Forecast Rules
You can define item forecast rules in Oracle Inventory to establish the forecast method,
bucket type, and sources of demand that are considered when compiling a statistical or
focus forecast.
Generate Focus and Statistical Forecasts

You can create forecasts by applying statistical and focus forecasting techniques that use
historical (transaction) information.
Import Forecasts from Outside Sources

With the Open Forecast Interface you can import forecast information generated by
other systems.
Load Forecasts into the Master Schedule

You can use forecasts or forecast sets to generate master demand or master production
schedules.
Review
You can review all aspects of your forecasts using online inquiries and reports. This
information can be viewed by forecast set or individual forecast.
Deleting Forecasts and Forecast Sets

You can delete forecast and forecast sets. Before you can delete forecast sets, you must
delete all forecasts contained within the set.
Important: Deleting removes the forecasts, forecast sets, and all related
information from the database. You cannot view or report on forecasts

and forecast sets once you delete them.
Project and Seiban References

If you are working in a project-based or Seiban environment, you can include
project/Seiban and task references to your forecast entries if organizational parameters
allow. These references will accompany forecast copies, loads, merges, and explosion.
See: Defining a Forecast, page 2-6.
See Also
Overview of Two Level Master Scheduling, page 9-1
Overview of Master Scheduling, page 3-1
Production Forecast Establishment, page 9-7
Forecast Control, page 2-33
Forecasting 2-3
Generating Forecasts from Historical Information

Overview of Forecast Generation
Another way to define a forecast is to generate it automatically based on historical
demand information, such as inventory transactions. You can then load these forecasts
into another forecast or into a master schedule.
The two methods of generating forecasts are:
Focus forecasting which produces only single period forecasts
Statistical forecasting which you can use to forecast any number of periods into the
future
See Also
Defining Forecast Rules
Defining Forecast Rules

Before you can generate a focus or statistical forecast, you first define a forecast rule in
Oracle Inventory. Forecast rules define the bucket type, forecast method, and the
sources of demand. If the rule is a statistical forecast, the exponential smoothing factor
(alpha), trend smoothing factor (beta), and seasonality smoothing factor (gamma) are
also part of the rule.
See Also
Defining a Forecast Rule, Oracle Inventory User's Guide
Generating a Forecast
To generate a focus or statistical forecast:
1.
Navigate to the Generate Forecast window.
2.
In the Parameters window, select a forecast name and forecast rule.
3.
Pick a range of items to forecast for: all items, a specific item, a category of items, or
all items in a category set.
4.
Select an overwrite option:

All Entries: Deletes everything on the forecast before loading new information.
No: Deletes nothing and adds new entries to existing entries during the load.
Schedule entries are not combined. You can get multiple forecast entries for the
same item on the same day.

Same Source Only: Deletes the entries that have the same source as those you load.
You can replace entries on the forecast that were previously loaded from the same
source without affecting other entries on the forecast.
5.
Enter a start date and cutoff date.
6.
Choose OK.
7.
In the Generate Forecast window, choose Submit.
See Also
Submitting a Request, Oracle Applications User's Guide
Forecast Levels
In addition to designating the minimum level of detail for which the forecast is defined,
the forecast level also serves as a consumption level. You can define the forecast level
with or without the demand class that also controls the consumption of forecasts. You
can define the following consumption levels for a forecast set:
item level
customer level
bill - to address level
ship - to address level

Important: If you have not installed Oracle Order Management or
Oracle Receivables, you can only consume forecasts by item level.
While attempting to consume a forecast, the consumption process looks for a forecast
containing an item that corresponds to the sales order information. When it finds an
entry, it checks the forecast using the criteria you defined for the forecast level. For
example, if you define the forecast level to be ship to, the forecast consumption process
searches the forecasts for the customer/ship - to address associated with the sales order.
Important: If you enter customer information but do not specify the
correct forecast level, the forecast consumption process ignores the

customer information.
Forecasting 2-5
Defining Forecast Sets

Defining a Forecast Set
Before you define a forecast, you first define a set. Forecast sets:
Group complimenting forecasts that sum together to a meaningful whole
Group forecasts that represent different scenarios. See: Forecast Set Examples.
You can associate a forecast to one forecast set only.

Some forecast set information - such as forecast level - defaults to the forecasts you
create within the set. You can keep or override these defaults for a specific forecast.
To define a forecast set:

1.
Navigate to the Forecast Sets window.
2.
Enter a unique name.
3.
Select a bucket type to group forecast entries by days, weeks, or accounting periods.
4.
Select the level that determines how forecasts in the set are defined and consumed.
See: Forecast Levels.
Ship - To: Item, customer, and shipping identifier
Bill - To: Item, customer, and billing identifier
Customer: Item and customer
Item: This is the only option available if you are not using Oracle Order
Management or Oracle Receivables.
5.
Select consumption options.

If you turn consumption on, sales orders you create consume forecast entries in this
set. See: Consumption within a Forecast Set.
The outlier update is the maximum percentage of a forecast entry that a single sales
order can consume.
Forward and backward days describe the number of work dates from the sales
order schedule date that forecast consumption looks backward or forward for a
forecast entry to consume. Non - workdays are not counted in these calculations.
See: Backward and Forward Consumption Days.
6.
Save your work.
Important: All the items within a forecast set are shown, including
overconsumption when this window is accessed in the view mode

through the Inquiry menu. However, only overconsumed items are
shown when you access the Forecast Set Items window through the
Forecast Sets window.
To disable a forecast set:

1.
Enter a disable date. After this date, you can no longer define a forecast name for
the set. You can view disabled forecasts but not modify them.
Defining Forecasts
Forecasts by Region
You have three forecasts named FCA, FCB, and FCC within a forecast set. Salesperson
A, responsible for the Eastern region, maintains FCA. Salesperson B maintains FCB for
the Midwest. Salesperson C maintains FCC for the Western region. In this situation,
FCA, FCB, and FCC each represent a part of the whole forecast. Together, their sum
represents the total forecast.
Forecast Scenarios
You have three forecast sets named SETA, SETB, and SETC. These forecast sets
represent different scenarios. SETA is the forecast for the bestcase scenario year of sales,
while SETB is the planned scenario year of sales. SETC shows the worst-case scenario
year of sales. You may want to maintain all three forecast sets simultaneously, so you
can compare and contrast the effect each has on your material plan.
Defining a Forecast
A forecast shows predicted future demand for items over time.
You can assign any number of items to a forecast, and use the same item in multiple
forecasts. For each item you enter the days, weeks, or periods and the quantities that
you expect to ship.
A forecast entry with a forecast end date specifies the same quantity scheduled for each
day, week, or period until the forecast end date. A forecast entry without a forecast end
date is valid only for the date and time bucket specified.
Prerequisites
Define at least one forecast set. See: Defining a Forecast Set.
Forecasting 2-7
To define a forecast:
1.
2.
Query a forecast set.
3.
Enter a unique name for the forecast.
4.
Choose the Forecast Items button to open the Forecast Items window.
You can choose the Folder menu to customize your display. See: Customizing the
Presentation of Data in a Folder, Oracle Applications User's Guide
5.
Enter an item.
6.
Choose the Detail button to open the Forecast Entries window.
7.
Select a bucket type of days, weeks, or accounting periods.
8.
Enter a date. This is typically the date you expect to ship the item or the beginning
of the week or period that you expect to ship the item.
9.
Enter an optional end Date. This creates forecast entries of the same quantity for
each day, week, or period until the end date. A forecast entry without an end date is
valid just for the date and time bucket specified.
10. Enter a current quantity. This also becomes the original quantity and the total.
Forecast consumption reduces the current quantity. Forecast consumption plus the
current quantity equals the total.
11. Enter an optional confidence percentage that the forecasted item will become actual
demand. Oracle MRP multiplies this percentage by the forecast quantity when you
load it into a master schedule.
12. If you are working in a project environment, enter a valid project and task
reference. After entering a valid reference, you can select a price list and an average
discount in the flexfield.
Note: Your ability to enter project and task references is determined
by organization parameters set in Oracle Inventory. If the project

control level is set to project, then the task column will be dimmed,
preventing you from entering task references. If the control level is
set to task, you can enter references into both columns. See: Setting
Up Project MRP in Oracle Inventory.
13. Save your work.
Copying and Merging Forecasts

You can copy forecasts from within your own organization, from any other
organization, or from any focus or statistical forecast.
You can modify existing forecasts while merging them into new ones. This allows you
to forecast (for simulation purposes) the same collection of items, but with altered
forecast rates and percentages, using a series of modification factors and/or carry
forward days.
When copying from existing forecasts, you have the option to copy original or current
forecast quantities. When you merge a forecast, you can selectively overwrite the
existing forecast, or you can consolidate forecasts by not overwriting previous forecast
entries.
If you load source forecasts with one demand class into a destination forecast with a
different demand class, Oracle MRP warns you that the demand classes are different. It
associates the new entries in the destination forecast with the demand class of the
destination forecast.
To copy or merge forecasts:

1.
Navigate to the Copy/Merge Forecast window.
2.
In the Parameters window, select a destination forecast and source type:

Forecast Source List: A source list defined in the Source Lists window.
Specific Forecast: One of your forecasts.
3.
Select the forecast organization.
4.
Select the forecast/load source list. Select either one of your source lists or one of
your forecasts, according to the source type you selected above.
5.
Select an Overwrite option:

All Entries: Deletes everything on the forecast before merging new information.
No: Deletes nothing and adds new entries to existing entries during the merge.
Schedule entries are not combined. You can get multiple forecast entries for the
same item on the same day.
Same Source Only: Deletes the entries that have the same source as those you merge.
You can replace entries on the forecast that were previously loaded from the same
source without affecting other entries on the forecast.
For example, suppose you merge forecasts FCA and FCB into FCC. On a
subsequent merge you select Same Source Only and merge FCB into FCC. The result
is that FCC contains forecasts from the first merge of FCA and the second merge of
Forecasting 2-9
FCB.
6.
Enter the start and cutoff dates for the forecast merge. Forecast entries are merged
from the start date to the cutoff date. If you specify carry forward days, the number
of days are subtracted from the cutoff date so that all merged entries have dates
before the cutoff date.
7.
Select the explode option.
8.
Select the quantity type:

Current: The current forecast quantity is the original forecast quantity minus any
consumption quantities. When you choose this option, you cannot choose to
consume the forecast since the forecast quantities already reflect sales order
demand that has been placed.
Original: This is the quantity of the forecast without any consumption. When you
choose this option, you should choose to consume the forecast if you intend to
generate a master schedule using forecasts and sales orders. Consuming the
original forecast ensures that demand is not overstated by balancing the forecast
and sales order demand.
9.
Select the consume option.
10. Select the modification percent.

11. Enter the number of carry forward days.
12. Choose OK.
13. In the Copy/Merge Forecast window, choose Submit.
See Also

Forecast entries are loaded according to an established, current time frame with a start
date and end date. All forecast entries are loaded between the start and end date. The
start date, cutoff date, and carry forward days are used as you enter them at the time of
the load, together with the backward consumption days you define at the forecast set
level. If the calculated date is not a valid workday, it will be adjusted to the previous
valid workday.
start date = start date + carry forward days backward consumption days
end date = cutoff date + carry forward days
If you specify backward consumption days for the forecast, Oracle MRP uses it to adjust
the start date because it defines the consumption window in which forecast
consumption consumes forecasts. Oracle MRP loads any forecast within that window so
that it can consider the forecast for consumption purposes. This may include past due
forecasts.
If you specify carry forward days, Oracle MRP uses them to determine which entries
are within the current time frame since they shift the forecast dates during the forecast
load. For example, if the start date is 16-MAR and you enter a cutoff date of 20-MAR
and specify four carry forward days, the forecast load process recalculates the current
time frame to 12-MAR through 16-MAR. Suppose the source forecast has entries of
13-MAR and 17-MAR. Based on this, Oracle MRP considers the forecast defined on
13-MAR as the only eligible forecast. When you load this forecast, the forecast load
process adjusts the date to 17-MAR to add in the carry forward days.
When you use weekly and period bucket types, these dates are recalculated by
identifying the beginning date of the workweek and period that the start date falls into.
The same calculation is applied to the end date.
A forecast entry with a forecast end date is considered current if the range that it covers
includes any part of the current time frame established above. This would include past
due entries.

In addition to merging an existing forecast into a new forecast, you can explode
planning and model forecasts to the destination forecast. See: Copying/Merging
Forecasts.
Note: You cannot order a planning bill of material item, but you can
order the components under it. If you want to ensure that you forecast
the components, as well as the planning item itself, you can explode the
planning item during a forecast merge.
When you explode a forecast for a model, you can track which forecasted end model
generated the forecast for the lower level components. This allows you to trace the
forecasted demand for a component if it is defined in more than one model. You can
also trace exploded forecasts to planning bills.
You can also explode a product-family forecast to the member items, and see which
product family generated the forecast for all the items at lower levels.
Reviewing Forecast Detail Information

You can also review and update forecast information in the Items Forecast Entries
Forecasting 2-11
window. This window displays the same information as the Forecast Entries window
with the difference that it contains a listing of the all the items in a forecast set. From
here you can access bucketed and consumption details.
To display item forecast detail information:

1.
Navigate to the Item Forecast Entries window.
2.
Query a forecast set. To update information, see Defining a Forecast, Steps
See Also
Overview of Forecast Consumption
Reviewing Bucketed Information
Reviewing Bucketed Information

To display forecast bucketed entries:
1.
Navigate to the Forecast Bucketed Entries window.
2.
Select a bucket type to be displayed: days, weeks, or periods.
3.
Select the Include Entries Before Start Date check box if you want to display forecast
entries, bucketed in the first bucket, before the start date you enter.
4.
Select the quantity display for bucketed forecast entries: Units (item quantity) or
Values (item quantity multiplied by the standard cost).
5.
Select the date range for which you want to display forecast bucketed information.
You can enter dates in the past to review historic forecast information.
6.
If you select the check box that beside the bucket dates, the data in this window is
refreshed automatically. If the check box is blank, data is refreshed only in the fields
where you place the cursor.
7.
Choose Detail to view detail forecast entries for an item in the Forecast Entries
window. If you do not select a bucket range, detail forecast entries for an item for all
bucketed dates between the start date and cutoff date of the bucket options display.
Forecast Consumption
Forecast consumption replaces forecasted demand with actual sales order demand.
Each time you create a sales order line, you create actual demand. If the actual demand
is already forecasted, the forecast demand must be decremented by the sales order
quantity to avoid counting the same demand twice.
For example, this table shows the forecast and sales orders for item 1.
Order Type
Quantity
Date
Forecast
50
June 1
SO1 (sales order 1)
10
June 1
SO2
25
June 1
This table shows the forecast and sales orders for item 1 after forecast consumption.
Order Type
Quantity
Date
Forecast
15 (50 - (10 + 25))
June 1
SO1
10
June 1
SO 2
25
June 1
Forecast consumption relieves forecast items based on the sales order line schedule
date. When an exact date match is found, consumption decrements the forecast entry by
the sales order quantity. Other factors that may affect the forecast consumption process
are backward and forward consumption days and forecast bucket type.
When you create a new forecast, especially from an external source, you can also apply
consumption that has already occurred for other forecasts to the new one.
Forecast Control
You control forecast consumption against each component by setting its organization
item attribute Forecast control:
Forecasting 2-13
Consume: Sales orders for this item consume forecasts for this item in the same
organization.
Consume and derive: Sales orders for this item consume forecasts for this item in
the same organization. Select this option if you will also do forecast explosion
against the item; see Forecast Explosion, page 2-26.
None: Sales orders for this item do not consume forecasts for this item.
Consumption within a Forecast Set

Consumption for an item and its corresponding sales order demand only occurs once
within a forecast set. For example:
Forecast Set #1 contains Forecast #1 and Forecast #2. The same item, Item A, belongs to
both forecasts within the set. Some possible scenarios and how consumption would
work are:
If the sales order quantity is less than the forecast quantity of each forecast, only one
of the forecasts for Item A is consumed.
If one of the two forecasts for Item A were on the same day as the sales order line
schedule date, that forecast would be consumed first.
If the forecast for Item A is for the same day in both forecasts, the forecasts are
consumed in alphanumeric order by forecast name.
For example, if each forecast for Item A is for a quantity of 100 and you place sales
order demand for 20, the consumption process would decrement only Forecast #1 to 80.
However, if the sales order quantity is for 120, Forecast #1 is decremented from
100 to zero and Forecast #2 is decremented from 100 to 80.
Consumption for a Product Family

Forecasts can be created and maintained at the product family level, and exploded
down to the members of the family based on the planning percentages and effectivity
dates in the bill of materials. Forecast consumption depends on the Forecast Control
item attribute: if Forecast Control for the product family item is set to Consume and at all
levels below that to Consume and Derive, a sales order added for member items
consumes its own forecast and the forecast for the product family. For example:
Suppose that the planning percentages for the member items are:
60% for B
40% for C
Also assume a product-family forecast for A of 100.

After forecast explosion, a sales order of 20 for item B consumes the forecast, leaving the
following forecast:
100 - 20 = 80 for A
60 - 20 = 40 for B
40 - 0 = 40 for C
Forecasting 2-15
Similarly, if item B is a model and if Forecast Control for both D and E is set to Consume
and Derive, then the forecast for item D gets consumed by 20 and the forecast for item E
gets consumed by 20. The forecasts for items F and G remain the same.
Consumption Across Forecast Sets

Consumption can occur multiple times if an item appears in more than one forecast set.
For example:
Forecast Set #1 contains Forecast #1 and Forecast Set #2 contains Forecast #2. The same
item, Item A, belongs to both forecasts within each set.
When you create a sales order, both forecasts for Item A in Forecast Set #1 and Forecast
Set #2 are consumed. This is because consumption occurs against each forecast set, and
Item A exists in both forecast sets.
For example, if each forecast for Item A is quantity 100 and you place sales order
demand for 20, the consumption process would decrement each forecast in each set
from 100 to 80.
Note: In this example, Forecast Set #1 and Forecast Set #2 are most
likely alternative scenarios two different sets for comparison purposes,

so that consumption occurs for the same item in both sets. If you want
to consume an item only once, define all forecasts for an item within a
single set.
Consumption Level
You can specify consumption levels in the forecast set:
Item level: Consumption occurs when item numbers match between the forecast
entry and the sales order line.
Customer Level: Consumption occurs when item numbers and customer numbers
match between the forecast entry and the sales order line.
Ship-to level: Consumption occurs when item numbers, customer numbers, and
customer ship-to addresses match between the forecast entry and the sales order
line
Bill-to level: Consumption occurs when item numbers, customer numbers, and
customer bill-to addresses match between the forecast entry and the sales order line
Backward and Forward Consumption Days

Use consumption days if:
You do not always have an exact match between the sales order line schedule dates
and forecast entry dates.
Your forecast entry quantity is not always sufficient to cover the sales order
quantities.
Forecast consumption works as follows:
It searches backward from the sales order line schedule date, workday by workday,
for forecast quantities to consume.
If that search is not successful in consuming the entire sales order line quantity, it
searches forward from the sales order line schedule date, workday by workday, for
forecast quantities to consume.
If that search is not successful in consuming the entire sales order line quantity, it
creates an overconsumption (negative demand) entry on the sales order line
schedule date.
Consumption and Demand Classes

You can assign a demand class to a forecast. When you create a sales order with a
demand class, consumption searches for forecasts that have the same demand class.
Consumption attempts to consume these forecasts first. If it does not find matching
entries, it tries to consume forecasts that do not have a demand class.
For sales orders without an associated demand class, consumption attempts to consume
Forecasting 2-17
forecasts that match the default demand class for the organization first, and then
consumes forecast entries that have no demand class defined.
Overconsumption
When consumption cannot find an appropriate forecast entry to consume, it creates, for
information purposes only, a new forecast entry at the forecast set level. This entry has
a zero original quantity and a negative current quantity equal to the unconsumed
demand.
The entry is marked with an origination of overconsumption.
Outlier Update Percent

This controls the effects of abnormal demand with a maximum percent of the original
quantity forecast that a single sales order can consume.
Example
You have several customers. Each typically orders 100 units in a given period. One of
the customers is having a special promotion that could increase demand significantly.
Use the outlier update percentage to ensure that these "one time" sales orders do not
overconsume the forecast.
In the above example, daily forecast exists for 20 on the 2nd and the 9th with an outlier
update percent of 50 on each forecast. When you place sales order demand for 50 on the
9th, the forecast consumption process attempts to consume on the sales order line
schedule date only, since the forecast is stated in daily buckets and no backward
consumption days exist. Because an outlier update percent of 50 exists on the forecast,
the consumption process consumes only 50% of the forecast. The outlier update percent
applies to how much of the original forecast quantity, not the sales order, the
consumption process can consume. In this example, the consumption process consumes
50% of the forecast (10) and the rest of the sales order quantity (40) is overconsumed. If
there were a backward consumption days of 5, 50% of the forecast on the 2nd would
also be consumed, and the overconsumed quantity would be 30.
Using the same example, if another sales order for 50 is placed on the 9th, it consumes
50% of the original forecast quantity (10) and the current forecast quantity on the 9th
becomes zero. Overconsumption is increased by an additional 40 to a new total on the
9th (80).
Forecast Consumption Considerations

Assemble to Order
Oracle MRP does not perform multi-level assemble to order forecast consumption. It
does not see component demand below the model.
Use Oracle Advanced Supply Chain Planning to handle this situation
Forecast Consumption Processing

The Planning Manager is a background concurrent process that performs automatic
forecast consumption as you create sales orders.
Unconsumption
When you decrease the order quantity on a sales order line item, Oracle MRP
unconsumes (increments) the appropriate forecast entry, according to the criteria
described for consumption. This process is also called deconsumption.
This process attempts to remove overconsumption entries at the forecast set level first,
before searching for an appropriate forecast entry to unconsume. See:
Overconsumption.
Note: Return Material Authorizations (RMAs) do not trigger the
uncomsumption process.
If you change a sales order line schedule date, Oracle MRP unconsumes the sales order
quantity based on the old schedule date and reconsumes the sales order quantity based
on the new schedule date.
Note: You can create sales orders with due datesthe manufacturing
calendar to express future demand that has uncertain due dates. Oracle
MRP consumes the forecast on the last valid workday in the
manufacturing calendar. When the sales order schedule date is
changed, it unconsumes on the last workday and reconsumes on the
sales order line schedule date.
Forecasting 2-19
Time Buckets in Forecast Consumption

Consumption with Daily Buckets
The process tries to consume a forecast entry on the 12th (the sales order date) because
the forecast is stated in daily buckets and no backward consumption days exist. Since
there are no forecasts on the 12th, an overconsumption entry is created on the 12th and
the forecasts remain the same.
Here, the process tries to consume a forecast entry between the 12th (the sales order
date) and the 9th (backward 3 days). The forecast entry of 20 each on the 9th is
consumed. The remaining sales order quantity of 5 creates an overconsumption entry.
In this example, the process tries to consume a forecast entry between the 2nd (back 3
days from the sales order date of the 5th) and the 10th (forward 3 workdays, skipping
the weekend). Going backward, the forecast entry of 20 each on the 2nd is consumed.
Going forward, the forecast entry of 20 on the 9th is reduced to 15 each.
Consumption with Weekly Buckets
In the above example, weekly forecasts exists for 20 on the 2nd and the 9th. When you
place sales order demand for 25 on the 12th, the forecast consumption process attempts
to consume in the week of the sales order only, since the forecast is stated in weekly
buckets and no backward consumption days exist. Since there is a forecast in the week
of the 12th, the entire forecast of 20 is consumed by the sales order for
25 and the remainder of the sales order becomes an overconsumption of 5 on the sales
order line schedule date.
Forecasting 2-21
In the above example, weekly forecasts exists for 20 on the 2nd and the 9th. When you
place sales order demand for 25 on the 12th, the forecast consumption process attempts
to consume in the week of the sales order first and then backwards for the number of
backward consumption days.
In this example, the backward consumption days of 5 causes the consumption process
to go into another weekly bucket where it also consumes anything from that week.
Since there is a forecast in the week of the 12th, the sales order for 25 consumes the
entire forecast of 20 and then consumes the remainder of the sales order quantity (5)
from the forecast on the 2nd.
Note: When you use weekly or periodic buckets and the consumption
days carry the consumption process into a different week or period, the
consumption process consumes from anywhere in the week or period,
regardless of whether the consumption days span the entire week or
period.
In this example, the process subtracts the backward consumption days from the 12th
(excluding non-workdays) to day 5. Since day 5 is in the previous week, it consumes
forecasts anywhere within the bucket; in this case, on the 2nd.
The consumption process consumes any forecasts that are included in the time fence
created by the backward or forward consumption days, and then any other forecasts
that are in the week or period. However, it does not consume a daily forecast that exists
in the week or period if it is not covered by the time fence. In the above example, a daily
forecast for the same item on the 4th would not have been consumed by the sales order;
however, a daily forecast on the 5th would have since it is in the period included in the
backward consumption days.
Consumption with Periodic Buckets
In the above example, a periodic forecast exists for 20 on the 2nd, the first day of the
period. When you place sales order demand for 25 on the 12th (assuming it is in the
same period), the forecast consumption process attempts to consume in the period of
the sales order only, since the forecast is stated in periodic buckets and no backward
consumption days exist. Since there is a forecast in the period starting on the 2nd, the
entire forecast of 20 is consumed by the sales order for 25 and the remainder of the sales
order becomes an overconsumption of 5.
In the above example, a periodic forecast exists for 20 on the 2nd, the first day of the
period. When you place sales order demand for 25 on the 12th (assuming it is in the
same period), the forecast consumption process attempts to consume in the period of
the sales order line schedule date first and then backwards for the number of backward
consumption days.
In this example, the backward consumption days does not cause the consumption
process to go into another periodic bucket. It behaves the same as if there were no
backward consumption days. Since there is a forecast in the period of the 2nd, the sales
order for 25 consumes, and the remainder of the sales order becomes an
Forecasting 2-23
overconsumption of 5 on the 12th. However, if the backward consumption days are

large enough to carry forecast consumption into the previous period, forecast
consumption can consume any forecasts in that period also.
Note: When you have a mix of daily, weekly, and periodic forecast
entries, forecast consumption first consumes the daily entries, then the
weekly entries, and lastly the periodic forecast entries that are included
in the time fence created by the backward and/or forward consumption
days.
Time Bucket Considerations

Consuming New Forecasts
Automatic forecast consumption, as controlled by the Planning Manager, consumes
existing forecasts with each sales order created. New forecasts you create are consumed
only by the sales orders created after forecast creation. You can, however, apply sales
orders already consumed by other forecasts to the new one.
Note: This process does not replace the automatic consumption
function of the Planning Manager.
To consume a new forecast:

1.
Navigate to the Forecast Sets window. Query the set name that includes the new
forecast. Choose the Consume button to open the Consume Forecast Set window.
or:
2.
Navigate directly to the Consume Forecast Set window. Select the set name that
includes the new forecast.
3.
Select a number of sales orders within the demand time fence to include. Including
only sales orders from today forward is useful if your forecast begins today, and/or
if the forecast begins on the first day of a period, rather than in the middle of a
period.
4.
Choose OK.
5.
Choose Submit to begin the process.

Note: This process considers only sales orders that have already
been consumed by automatic forecast consumption through the
Planning Manager. It does not consider sales orders pending in the

Planner Manager that have not been processed.
See Also
Submitting a Request, Oracle Applications Users Guide
Planning Manager
Tracking Forecast Consumption

You can track forecast consumption for both the product family and the member items.
The procedure for tracking forecasts for a product family item is the same as that for
any individual item.
To see which sales orders consumed the product family forecast:

1.
Navigate to the Item Forecast Entries window.
2.
Query to find the forecast you're interested in tracking.
3.
Navigate to the Forecast Entry for the product family item.
4.
Choose Consumptions to see the consumed quantity for each order.
To see which product family items are overconsumed, do this:

1.
2.
Query to find the forecast set you're interested in.
3.
Click the Forecast Set Items button to see which items on the forecast set were
overconsumed.
The Forecast Items window that appears shows both individual items and product
family items.
Note: Only overconsumed items are shown when you access the
Forecast Set Items window through the Forecast Sets window.

However, all the items within a forecast set are shown, including
overconsumption, when this window is accessed in the view mode
through the Inquiry menu.
Forecasting 2-25
To be notified whenever a product family item is overconsumed, do this:

1.
Create an Oracle Alert for this event.
See: Creating an Event Alert, Oracle Alert User's Guide.

See Also
Overview of Production Planning
Defining a Forecast Set
Overconsumption
Tracking Demand Schedule Reliefs
Planning Models, Option Classes, and Product Families
Forecast Explosion
You can define and maintain forecasts for any item, at any level on your bills of
material. Forecast explosion is a process that creates forecasts for components from the
forecasts of their parents. It occurs in the following situations:
Product family forecasts to product family member item forecasts. The planning
engine considers these exploded forecasts as independent demand and uses
pegging to link then to their product family forecast.
Model forecasts to other model, option class, option item, and included item
forecasts. See Configure to Order Forecast Explosion, Oracle Advanced Supply Chain
Planning Implementation and User's Guide.
Forecasting Planning Bills of Material

In Oracle Bills of Material, you can define multilevel planning bills, with multiple levels
of planning items, to represent groups of related products that you want to forecast by
family.
Typically, you can order components of a planning bill, but not the planning item itself.
The planning item is an artificial grouping of products that helps you to improve the
accuracy of your forecasting since, generally, the higher the level of aggregation, the
more accurate the forecast.
Before you can perform forecast explosion, set up planning percentages in the product
family and model bills of material. Planning percentage is the percent of the parent
forecast that is attributable to the component. For example:
In a product family bill of material, product family member item A has planning
percentage 30%, product family member item B has planning percentage 50%, and
5-56 product family member item C has planning percentage 20%.
A product family forecast entry has quantity 1000
After forecast explosion, the forecast quantity for product family member item A is
300, for product family member item B is 500, and for product family member item
C is 200.
See Creating a Bill of Material, Oracle Bills of Material User's Guide and attend to tab
Component Details, field Planning %.
The following table illustrates a planning bill for Training Computer, a planning item
that represents a planning bill for three types of computers: laptop, desktop, and server.
The planning percent assigned to each member of the planning bill represents
anticipated future demand for each product.
Level
Item
BOM Item Type
Planning %
Training Computer
Planning
.2
. Laptop Computer
Model
60%
.2
. Desktop Computer
Model
20%
.2
. Server Computer
Model
20%
The following table illustrates forecast explosion, via the planning bill described in the
previous table, for a forecast of 100 Training Computers. The table also illustrates
forecast consumption after you place sales order demand for 20 Laptop Computers.
Original forecast shows forecast quantities before forecast consumption. Current
forecast shows forecast quantities after consumption by sales order demand.
Level
Item
Original Forecast
Current Forecast
Training Computer
100
100
.2
. Laptop Computer
60
40
.2
. Desktop Computer
20
20
.2
. Server Computer
20
20
The planning percentages of all of the components of a parent can add to more than
100%.
Forecasting 2-27
You control forecast explosion to each component by setting its organization item
attribute Forecast control:
Consume: There is no planning engine forecast explosion to this component.
Consume and derive: There can be planning engine forecast explosion for models
depending on plan option Explode Forecast. The planning engine does not explode
multi-organization models.
None: There can be planning engine forecast explosion for product families
depending on plan option Explode Forecast.
For information about forecast explosion for model forecasts, see Configure to Order
Forecast Explosion, page 2-36.
Forecast Explosion Considerations

This topic lists forecast considerations for Oracle MRP.
Load/Copy/Merge Process
When you use the Load/Copy/Merge window to load a planning item forecast into
another forecast, you can choose to explode the aggregate forecast for the planning item
into detailed forecasts for each of the components defined on the planning bill. The
forecast quantities exploded to the components are calculated by extending the
planning item forecast by the component usages and planning percents defined on the
planning bill. You can also choose to explode forecasts when you load a planning item
forecast into a master schedule.
Configure to Order Models

A model is an item with some configurable components. A configurable component is a
component that different customers may order differently, for example, a color of paint.
There are these types of models:
Assemble-to-order: The manufacturer or distributor assembles the components and

ships the configured item, for example, an automobile.
Pick-to-order: The components are shipped separately and assembled by the

recipient, for example, a childrens' outdoor play set. Oracle Advanced Supply
Chain Planning uses the pick-to-order model item for forecast explosion; it does not
plan it.
The components of a model are:
Option classes: A bill of material structure whose components are the options that
the customer can select, for example, paint color.
Standard items: The options from which the customer chooses, for example, red,
green, and blue. They are components of the option classes.
Included items (also known as mandatory components): A standard item that the
customer receives regardless of options selected, for example, an instruction
brochure. They are components of the model item.
Another model: For example, a personal computer. The customer chooses the main
components and the manufacturer assembles them into a case (assemble-to-order).
The customer also chooses peripheral items that the manufacturer or distributor
ships separately from the main unit and that the recipient attaches to the main unit.
The personal computer is a pick-to-order model, the main unit is an
assemble-to-order model component under the pick-to-order model, and the
peripherals are option class components under the pick-to-order model.
Oracle does not recommend placing an assemble-to-order model as a member of a

product family.
The following table illustrates a model bill for Laptop Computer, a model that includes
two mandatory components and three option classes. The planning percent assigned to
optional option classes represents anticipated demand for the option class. In this
example, 90% of Laptop Computers are expected to be sold with an operating system,
and the remaining 10% are expected to be sold without.
Level
Item
BOM Item Type
Optional
Planning %
.2
. Laptop Computer
Model
No
60%
..3
. . Carrying Case
Standard
No
100%
..3
. . Keyboard
Standard
No
100%
..3
. . CPU
Option Class
No
100%
..3
. . Monitor
Option Class
No
100%
..3
. . Operating System
Option Class
Yes
90%
Option Class Bills

The following example illustrates the option class bills for the Monitor, VGA, and EGA
option classes. The planning percent assigned to each option within each option class
represents anticipated demand for the option. In this example, 70% of all Laptop
Computers are expected to be sold with a VGA monitor, and the remaining 30% are
Forecasting 2-29
expected to be sold with an EGA monitor. Notice that the Monitor option class is not
optional. This means that customers must always choose one of the Monitor options
when ordering Laptop Computer. Of the 70% of Laptop Computers sold with a VGA
monitor, 50% are expected to be sold with the VGA1 monitor and 50% are expected to
be sold with the VGA2 monitor. The VGA option class also includes a mandatory
component, VGA Manual, that is always shipped with Laptop Computer if the VGA
monitor option class is chosen, regardless of the VGA option.
Level
Item
BOM Item Type
Optional
Planning %
..3
. . Monitor
Option Class
No
100%
...4
. . . VGA
Option Class
Yes
70%
....5
. . . . VGA Manual
Standard
No
100%
....5
. . . . VGA1
Standard
Yes
50%
....5
. . . . VGA2
Standard
Yes
50%
...4
. . . EGA
Option Class
Yes
30%
....5
. . . . EGA1
Standard
No
55%
....5
. . . . EGA2
Standard
Yes
45%
Forecasting Predefined Configurations

Predefined configurations are configurations that you have defined as standard items,
with standard bills and standard routings. You might define a predefined configuration
because you often use the configuration in sales promotions, or the configuration is one
of your most commonly ordered configurations, and you want to build it to stock to
reduce delivery lead times and improve customer service levels. Your customers can
order predefined configurations by item number, just as they order any other standard
item.
Forecast consumption, forecast explosion, master scheduling, planning, production
relief, and shipment relief for predefined configurations behave as they do for any other
standard item.
Configure to Order Forecast Control

Use item attribute Forecast Control to specify the types of demand that you place for
models, option classes, options, and mandatory components. The configure to order
processes uses the Forecast Control value that you assign to each assemble-to-order and
pick-to-order item to guide the behavior of those processes.

The following section discusses the four types of demand that you can place for an item,
and identifies the appropriate Forecast Control attribute value for each type of demand.
Choosing a Value for Forecast Control

There are the types of demand that you can place for your models, option classes,
options, and mandatory components:
Independent forecast demand
Exploded forecast demand
Sales order demand
Derived sales order demand
Independent Forecast Demand

Independent forecast demand is demand that you place for an item by entering
forecasts for the item directly, rather than exploding forecast to the item using forecast
explosion. You typically define direct forecasts for items, such as a planning items or
models, whose demand is independent of any other item. Define direct forecasts by
entering them manually, or by loading them from other products or systems.
If you forecast demand directly for an item, then set Forecast Control to Consume.
Exploded Forecast Demand
Exploded forecast demand is demand that you generate for an item when you explode
forecasts to the item using forecast explosion. You typically generate exploded forecast
demand for items, such as option classes and options, whose demand is directly related
to or derived from the bill of material structure for other items.
If you forecast demand for an item by exploding demand from a higher level item in a
bill of material, set Forecast Control to Consume and Derive.
In some cases, you may have items that are subject to both types of forecast demand.
For example, the keyboard that is forecast and sold as a mandatory component with a
Laptop Computer may also be forecast and sold separately as a spare or service part.
You use Forecast Control to control which models, option classes, options, and
mandatory components in a model bill receive exploded forecasts, since forecast
explosion only generates exploded forecast demand for items where you have set
Forecast Control to Consume and Derive.
Important: Set Forecast Control to None to identify items that have
dependent demand that should be calculated by the planning process,

using standard planning logic, rather than through forecast explosion.
An example of this type of item is a user manual that is either
Forecasting 2-31
gross-to-net or minmax planned and replenished.
If you forecast demand for an item directly, and explode forecast demand to the item,
set Forecast Control to Consume and Derive.
Sales Order Demand
Sales order demand is demand that you place when your customers order
configurations. As your customers order configurations, Oracle Order Management
automatically places sales order demand for each model, option class, and option
selected by your customer when they place the order.
If you place sales order demand for an item, but do not forecast the item, set Forecast
Control to None.
Derived Sales Order Demand
Under normal circumstances, Oracle Order Management does not place sales order
demand for mandatory components when your customers order configurations. If you
are forecasting key mandatory components, however, you will usually want to
maintain your forecasts by generating sales order demand for the mandatory
components and consuming the forecasts as your customers place sales orders.
You can set the Forecast Control attribute to Consume or Consume and Derive to
automatically place demand and consume forecasts for mandatory components when
you place sales orders demand for configurations that include the mandatory
components.
If you forecast demand for a mandatory component, either directly or through forecast
explosion, set Forecast Control to Consume or Consume and Derive.
Summary
The following table summarizes, for each type of item, the types of demand that
configure to order assumes you place for different values of Forecast Control.
Item Type
Forecast
Control
Forecast
Expl
oded
Forec
ast
Exploded
Sales
Order
Derived Sales
Order
Models and Option

Classes
Consume
Yes
Yes
Models and Option

Classes
Consume and
Derive
Yes
Yes
Yes
Option
Consume
Yes
Yes
Option
Consume and
Derive
Option
None
Mandatory
Component
Consume
Mandatory
Component
Consume and
Derive
Mandatory
Component
None
Product Family
Consume
Product Family
Consume and
Derive
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Configure to Order Forecast Control Considerations

Oracle MRP lets you master schedule any planned item on your master schedules,
including models and option classes.
With the two-level master scheduling approach, you typically master schedule your key
subassemblies your options and mandatory components since they are the highest level
buildable items in your model bills.
Although models and option classes are not buildable items, you may want to master
schedule them so that you can calculate available-to-promise (ATP) information for
promising order ship dates by model or option class. You might also want to master
schedule your models and option classes so that you can perform rough cut capacity
checks by model and option class. This is particularly valid when different
configurations of your models have very similar capacity requirements.
Note: Oracle MRPg does not support planning for picktoorder models
and option classes.
Two-Level Master Scheduling Processes

The following table summarizes the effect of Forecast Control on the following major
processes that Oracle MRP uses to implement twolevel master scheduling:
Forecasting 2-33
forecast explosion
forecast consumption
master demand schedule load
planning
production relief
Shipment relief
Forecast Consumption (a) and Forecast Consumption (b) represent forecast consumption
before and after the Auto-Create Configuration process creates the configuration item
and single-level bill for a configuration. CD represents component demand, NR
represents net requirements, SO represents sales order demand, and FC represents
forecast demand.
Note: Notice that the only difference between the Consume option and
the Consume and Derive option is that forecast explosion generates

exploded forecast demand for items where Forecast Control is set to
Consume and Derive.
Forecast
Control
Process
Models and
Option Classes
Options
Mandatory
Components
Consume
Forecast
Explosion
Do not generate
exploded forecast
demand
Do not generate
exploded forecast
demand
Do not generate
exploded forecast
demand
Forecast
Consumptio
n (a)
Consume actual
sales order
demand
Consume actual
sales order demand
Consume derived
sales order demand
Forecast
Consumptio
n (b)
Consume
configuration
component
demand
Consume
configuration
component demand
Consume
configuration
component demand
MDS Load
Load actual sales

order demand
Load actual sales

order demand
Load derived sales

order demand
Forecast
Control
Consume
and Derive
None
Process
Models and
Option Classes
Options
Mandatory
Components
Production
Relief
Relieve when
configuration
work order is
created
Relieve when option

work order is
created
Relieve when
component work
order is created
Shipment
Relief
Relieve when
configuration sales
order is shipped
Relieve when
configuration sales
order is shipped
Relieve when
configuration sales
order is shipped
Forecast
Explosion
Generate exploded
forecast demand
Generate exploded
forecast demand
Generate exploded
forecast demand
Forecast
Consumptio
n (a)
As above
As above
As above
Forecast
Consumptio
n (b)
As above
As above
As above
MDS Load
As above
As above
As above
Production
Relief
As above
As above
As above
Shipment
Relief
As above
As above
As above
Forecast
Explosion
Not applicable
Do not generate
exploded forecast
demand
Do not generate
exploded forecast
demand
Forecast
Consumptio
n (a)
Not applicable
Consume actual
sales order demand
Do not consume
Forecast
Consumptio
n (b)
Not applicable
Do not consume
Do not consume
MDS Load
Not applicable
Load actual sales

order demand
Do not load derived

sales order demand
Forecasting 2-35
Forecast
Control
Process
Models and
Option Classes
Options
Mandatory
Components
Production
Relief
Not applicable
Relieve when option

work order is
created
Relieve when
component work
order is created
Shipment
Relief
Not applicable
Do not relieve
Do not relieve
Configure to Order Forecast Explosion

You can use the Bills of Material window in Oracle Bills of Material to define model and
option class bills with multiple levels of option classes, options, and mandatory
components to represent your complex configure-to-order products. You can then use
forecast explosion to explode model and option class forecasts the same way you
explode forecasts for planning items.
The logic for exploding models and option classes is the same as the logic used to
explode planning items. You can choose to explode model and option class forecasts,
just as you can choose to explode planning item forecasts when loading forecasts into
other forecasts or master schedules.
The following diagram illustrates the forecast explosion logic.
Exploding Forecasts from Using Assemblies

The following table illustrates when forecast explosion explodes forecast from a parent
item to its components. 'Always' means 'Always explode forecasts from this item', and
'Never' means 'Never explode forecasts from this item.'
Planning
Item
ATO
Model
ATO
Option
Class
ATO
Std. Item
PTO
Model
PTO
Option
Class
PTO
Std.
Item
Std. Item
Always
Always
Always
Never
Always
Always
Always
Never
Exploding Forecasts to Components

The following table illustrates when forecast explosion explodes forecast to a
component from its parent item. 'Always' means 'Always explode forecasts from this
item', 'Check' means 'Explode forecasts to this item if Forecast Control is set to Consume
and Derive', and 'Never' means 'Never explode forecasts from this item.'
Forecasting 2-37
Product
Family
Planning
Item
ATO
Model
ATO
Option
Class
ATO
Std.
Item
PTO
Model
PTO
Option
Class
PTO
Std.
Item
Std.
Item
Check
Check
Check
Check
Check
Check
Check
Check
Check
Forecast Explosion Example

The following table illustrates how forecast explosion explodes a forecast for 100 Laptop
Computers. The FC column shows forecast quantities.
Level
Item
BOM Item
Type
Forecast
Control
Optional
Plan %
FC
.2
. Laptop
Computer
Model
Consume
No
..3
. . Carrying
Case
Standard
Consume
and Derive
No
100%
100
..3
. . Keyboard
Standard
Consume
and Derive
No
100%
100
..3
. . CPU
Option
Class
Consume
and Derive
No
100%
100
...4
. . . 386
Processor
Standard
Consume
and Derive
Yes
65%
65
...4
. . . 486
Processor
Standard
Consume
and Derive
Yes
35%
35
100
Configure to Order Forecast Explosion Considerations

You explode forecasts by choosing the Explode option when loading a forecast into
another forecast or a master schedule.
Re-exploding Forecasts
You can change your planning and model forecasts at any time and reexplode new
forecasts to your option classes, options, and mandatory components. You can choose
to reconsume your new forecasts using the sales order demand history maintained by
Oracle MRP. This lets you quickly adjust your exploded forecasts in response to forecast
or bill of material changes.
Configure to Order Forecast Consumption

Forecast consumption is the process that replaces forecast demand with sales order
demand. Each time you place a sales order, you create actual demand. If the actual
demand is forecasted, you typically want to reduce the forecast demand by the sales
order quantity to avoid overstating demand.
For source instance forecasts, the consumption occurs against forecasts for product
families, configurations, models, option classes, and options when you place sales order
demand for configurations. By default, forecast consumption consumes forecasts by
item.
If you want to consume your forecasts by distribution channel, customer type, or order
type, use demand classes to control forecast consumption. You can also choose to
consume your forecasts by one of the following forecast consumption levels:
Item
Customer
Customer bill-to address
Customer ship-to address
With inline forecast consumption, toe consumption occurs at the beginning of the
planning run, using the forecasts and sales orders that you use to drive the plan.
Consumption of Models
Forecast consumption takes place both before and after the AutoCreate Configuration
process creates a configuration item, bill, and routing for a configuration. The configure
to order process ensures that forecast consumption is consistent before and after the
creation of the configuration item.
Note: The fact that forecast consumption takes place twice, both before
and after the creation of the configuration item, is transparent to the

user. The purpose of this section is only to provide detailed
information.
Forecast Consumption: Before AutoCreate Configuration

When your customers order configurations, Oracle Order Management places sales
order demand for all ordered models, option classes, and options.
Forecasting 2-39
Note: Under normal circumstances, no sales order demand is placed for
mandatory components. You can also generate derived sales order

demand for selected mandatory components, since forecast
consumption generates derived sales order demand for all items where
you have set Forecast Control to Consume or Consume and Derive. This
lets you define and maintain forecasts for key mandatory components
as well as models, option classes, and options.
Before you run the AutoCreate Configuration process, forecast consumption uses actual
sales order demand for models, option classes, options, and derived sales order demand
for selected mandatory components, to consume your forecasts.
Example: Before AutoCreate Configuration
The following example illustrates how forecast consumption consumes an exploded
forecast for 100 Laptop Computers when a customer places a sales order for 10 Laptop
Computers with 486 processors, VGA1 monitors, and DOS operating system. The SO
column shows sales order quantities. Notice that forecast consumption generates and
consumes derived sales order demand for each mandatory component where you have
set Forecast Control to Consume or Consume and Derive.
Forecast Consumption (1 of 2)
Level
Item
BOM Item
Type
Forecast
Control
Optional
Plan %
FC/ SO
.2
. Laptop
Computer
Model
Consume
90 10
..3
. . Carrying
Case
Standard
Consume
and Derive
No
100%
90 10
..3
..
Keyboard
Standard
Consume
and Derive
No
100%
90 10
Level
Item
BOM Item
Forecast
Optional
Plan
FC/
Type
Control
SO
..3
. . CPU
Option
Class
Consume
and Derive
No
100%
90 10
...4
. . . 386
Processor
Standard
Consume
and Derive
Yes
65%
65
...4
. . . 486
Processor
Standard
Consume
and Derive
Yes
35%
25 10
..3
. . Monitor
Option
Class
Consume
and Derive
No
100%
90 10
...4
. . . VGA
Option
Class
Consume
and Derive
Yes
70%
60 10
....5
. . . . VGA
Manual
Standard
Consume
and Derive
No
100%
60 10
....5
. . . . VGA1
Standard
Consume
and Derive
Yes
50%
25 10
....5
. . . . VGA2
Standard
Consume
and Derive
Yes
50%
35
...4
. . . EGA
Option
Class
Consume
and Derive
Yes
30%
30
....5
. . . . EGA1
Standard
Consume
and Derive
Yes
55%
16.5
....5
. . . . EGA2
Standard
Consume
and Derive
Yes
45%
13.5
...4
. . . Monitor
Manual
Standard
None
No
100%
..3
..
Operating
System
Option
Class
Consume
and Derive
Yes
90%
80 10
...4
. . DOS
Standard
Consume
and Derive
Yes
80%
62 10
Forecasting 2-41
..4
. . UNIX
Standard
Consume
and Derive
Yes
20%
18
Forecast Consumption: After AutoCreate Configuration

The AutoCreate Configuration process replaces sales order demand for ordered models,
option classes, and options with sales order demand for the newly created
configuration item. This prompts forecast consumption to unconsume forecasts for the
models, option classes, options, and selected mandatory components, and consume
forecasts for the new configuration item and its components.
When creating the configuration item, the AutoCreate Configuration process also
creates a single level bill of material for the configuration item. The single level bill
includes all ordered options, all mandatory components of all ordered models and
options classes, and each ordered model and option class. The models and option
classes appear on the configuration bill as phantoms, and are only there to consume
forecasts and relieve master schedules. They are not used by the planning process or
Oracle Work in Process since all mandatory components from the model and option
class bills are also included directly on the single level bill.
The following table illustrates the single level configuration bill created by the
AutoCreate Configuration process in response to the sales order for 10 Laptop
Computers with 486 processors, VGA1 monitors, and DOS operating system.
Single Level Bill for Laptop Configuration
Level
Item
BOM Item Type
Optional
Laptop Computer001
Standard
No
Laptop Computer
Model
No
Carrying Case
Standard
No
Keyboard
Standard
No
CPU
Option Class
No
486 Processor
Standard
No
Monitor
Option Class
No
VGA
Option Class
No
VGA Manual
Standard
No
VGA1
Standard
No
Monitor Manual
Standard
No
Operating System
Option Class
No
DOS
Standard
No
In the post configuration stage, forecast consumption uses the sales order demand for
the new configuration item to consume forecasts. Typically, you do not have any
forecasts defined for unique configurations. Therefore, forecast consumption does not
find any forecasts to consume. If forecast explosion cannot find any forecasts to
consume, it explodes the configuration bill and consumes forecasts for each model and
option class on the bill. It also consumes forecasts for each standard item on the
configuration bill where Forecast Control is set to Consume or Consume and Derive.
To ensure that forecast consumption is consistent before and after the AutoCreate
Configuration process, forecast consumption only consumes forecasts for standard
items on configuration bills where Forecast Control is set to Consume or Consume and
Derive.
Note: If you set Forecast Control to None for an option, and then define
forecasts for the option, you get inconsistent forecast consumption

before and after the AutoCreate Configuration process. Before the
AutoCreate Configuration process, forecast consumption uses actual
sales order demand to consume any existing forecasts. After the
AutoCreate Configuration process, forecast consumption does not
consume those same forecasts since it only consumes forecasts for
standard items on configuration bills where Forecast Control is set to
Consume or Consume and Derive.
Example: After AutoCreate Configuration

The following table shows how forecast consumption consumes the exploded forecast
for 100 Laptop Computers after the AutoCreate Configuration process replaces sales
order demand for the model, option classes, and options with sales order demand for
the newly created configuration item.
Forecasting 2-43
Sales Order Demand for the Configuration Item

Level
Item
BOM Item
Type
Forecast
Control
Optional
Plan %
FC/ SO
Laptop
Computer0
01
Standard
Consume
10
Level
Item
BOM Item
Type
Forecast
Control
Optional
Plan %
FC/ SO
Laptop
Computer
Model
Consume
90
.3
. Carrying
Case
Standard
Consume
and Derive
No
100%
90
Level
Item
BOM Item
Type
Forecast
Control
Optional
Plan %
FC/ SO
.3
. Keyboard
Standard
Consume
and Derive
No
100%
90
.3
. CPU
Option
Class
Consume
and Derive
No
100%
90
..4
. . 386
Processor
Standard
Consume
and Derive
Yes
65%
65
..4
. . 486
Processor
Standard
Consume
and Derive
Yes
35%
25
.3
. Monitor
Option
Class
Consume
and Derive
No
100%
90
..4
. . VGA
Option
Class
Consume
and Derive
Yes
70%
60
....5
. . . . VGA
Manual
Standard
Consume
and Derive
No
100%
60
....5
. . . . VGA1
Standard
Consume
and Derive
Yes
50%
25
....5
. . . . VGA2
Standard
Consume
and Derive
Yes
50%
35
...4
. . . EGA
Option
Class
Consume
and Derive
Yes
30%
30
....5
. . . . EGA1
Standard
Consume
and Derive
Yes
55%
16.5
....5
. . . . EGA2
Standard
Consume
and Derive
Yes
45%
13.5
...4
. . . Monitor
Manual
Standard
None
No
100%
..3
..
Operating
System
Option
Class
Consume
and Derive
Yes
90%
80
...4
. . . DOS
Standard
Consume
and Derive
Yes
80%
62
...4
. . . UNIX
Standard
Consume
and Derive
Yes
20%
18
Consumption of Predefined Configurations

Forecast consumption for predefined configurations is exactly the same as forecast
consumption for configuration items created automatically from sales orders for ATO
models. Typically, if you have created a predefined configuration, you have also
defined forecasts for it. If so, forecast consumption finds and consumes forecasts for the
predefined configuration. If you have not defined forecasts for the predefined
configuration item, then forecast consumption explodes the configuration bill and
consumes forecasts for each model and option class on the bill. It also consumes
forecasts for each standard item on the configuration bill where Forecast Control is set
Forecasting 2-45
to Consume or Consume and Derive.

The following table illustrates a predefined configuration for a commonly ordered
version of Laptop Computer called Laptop Basic.
Predefined Configuration
Level
Item
BOM Item Type
Optional
Laptop Basic
Standard
No
.2
. Laptop Computer
Model
No
.2
. Carrying Case
Standard
No
.2
. Keyboard
Standard
No
.2
. CPU
Option Class
No
.2
. 486 Processor
Standard
No
.2
. Monitor
Option Class
No
.2
. VGA
Option Class
No
.2
. VGA Manual
Standard
No
.2
. VGA1
Standard
No
.2
. Monitor Manual
Standard
No
.2
. Operating System
Option Class
No
.2
. DOS
Standard
No
The following table illustrates consumption of a forecast for 100 Laptop Basics after a
customer places a sales order for 10 units.
Item
Original Forecast
Current Forecast
Laptop Basic
100
90
If you have not defined forecasts for the predefined configuration, forecast
consumption explodes the configuration bill and consumes forecasts for each model
and option class. Forecast consumption also consumes forecasts for each standard item
on the configuration bill where Forecast Control is set to Consume or Consume and Derive
.
The following table illustrates consumption of the same sales order for 10 Laptop Basics
when you have not defined a forecast for Laptop Basic. Note that the original forecast
quantities for Laptop Basic's components have not been exploded from Laptop Basic,
since you cannot explode forecasts from a standard item. Any forecasts that do exist for
Laptop Basic's components must have been entered manually or exploded from a
planning item, model, or option class forecast. This example assumes that Forecast
Control is set to Consume or Consume and Derive for all standard components on Laptop
Basic's configuration bill.
Item
Original Forecast
Current Forecast
Laptop Computer
20
10
Carrying Case
20
10
Keyboard
20
10
CPU
30
20
486 Processor
50
40
Monitor
40
30
VGA
40
20
VGA Manual
50
40
VGA1
20
10
Forecasting 2-47
Monitor Manual
30
20
Operating System
30
20
DOS
30
20
3
Master Scheduling
Overview of Master Scheduling

Supply Chain Planning users can employ additional functionality to manage demand
and schedule production across multiple, interdependent organizations. See: Master
Scheduling in Supply Chain Planning
Master scheduling is used for:
demand management
scheduling production
validating the production schedule
managing the production schedule
You use the schedules generated by master scheduling as input to other manufacturing
functions, such as material requirements planning and rough-cut capacity planning.
Note: The planning products support Oracle Project Manufacturing's
end item model/unit effectivity. The end-item model Unit Number field
is visible if this featured is enabled allowing you to:
Enter schedule entries by model/unit
Load sales orders into a MDS, and have the specified unit number
carried over to the schedule entry
Create demand and generate planned orders with unit number

specified
Master Scheduling 3-1
Master Demand Schedule

The MDS is a statement of demand and contains details of the anticipated shipment
schedule. You can consolidate all sources of demand into a master demand schedule to
represent a statement of total anticipated shipments. The master demand schedule
provides an extra level of control that allows you to view and modify your statement of
demand before creating a detailed production schedule. You can use the time-phased
master demand schedule as input to the master production scheduling process or the
material requirements planning process.
Some of the demand types that the MDS considers are:
item forecasts
spares demand
sales orders
internal requisitions
Supply Chain Planning users can also manage interorganizational demand and create
distribution requirements plans (DRP) from an MDS. See: Master Scheduling in Supply
Chain Planning
Master Production Schedule (MPS)

The MPS is a statement of supply required to meet the demand for the items contained
in the MDS. The master production schedule defines the anticipated build schedule for
critical items. An effective master production schedule provides the basis for order
promising and links the aggregate production plan to manufacturing by specific items,
dates, and quantities. You can use the MPS to level or smooth production so that you
effectively utilize capacity to drive the material requirements plan.
Note: Master Demand Scheduling (MDS) and Master Production
Scheduling (MPS) have similar windows and functionality. Therefore,

the documentation often refers to the more generic "Master Scheduling"
. This document may use "Master Scheduling" to refer to "Master
Demand Scheduling" or "Master Production Scheduling".
Supply Chain Planning users can also run a multi-organization MPS and create
distribution requirements plans (DRP) from an MPS. See: Master Scheduling in Supply
Chain Planning
Main Features of Master Scheduling

Discrete and Repetitive Scheduling
The master schedule can include discrete and repetitive items. Discretely planned items
include flow schedules. A specific schedule date and quantity defines a master schedule
entry for a discretely manufactured item. A schedule start date, a rate end date, and a
daily quantity define a master schedule entry for a repetitively manufactured item.
MDS
For a master demand schedule, the schedule date for a discrete item may or may not be
a valid workday. The start and end dates for a repetitive item must be valid workdays
since repetitive planning does not consider non-workdays.
MPS
For a master production schedule, the schedule date for discrete items and the start and
end dates for repetitive items must be valid workdays.
Master Schedule Entries for Product Family Items
The master schedule shows sales order entries for product family items when you load
sales orders for their member items. They also show demand schedule entries for
product family items loaded from the forecasts.
Roll the MPS Plan Forward
You can append planned orders to the MPS plan as time passes without affecting the
existing plan.
Forecast and Planning Configurations
You can schedule configurations on your master schedule. Configurations may
represent unique, one time combinations of options that were ordered, or they may
represent standard, often-ordered sets of options.
Identify Conflicts in Schedules
You can identify conflicts between desirable schedules and attainable schedules using
rough-cut capacity planning. Rough-cut capacity planning converts the master schedule
into an assessment of available and required capacity and its impact on key resources
such as bottleneck work centers and long lead time items/equipment. It lets you
evaluate the probability of success before implementation. You can use rough-cut
capacity to simulate different scenarios and compare multiple master schedules.
Schedule Spares Demand
You introduce spare parts demand into an MPS plan by manually defining spares
requirements as master demand schedule entries. You can also forecast spares demand
and load the forecast into the master schedule.
Available to Promise
You can include a master production schedule as supply for your available to promise
calculations.
Add MPS Firm Planned Orders
An order for an MPS Planned item can be modified or added in the Planner
Workbench.
Master Schedule at Any Level
You can master schedule items that exist at any level of the bill of material. The master
production schedule then operates separately from the material requirements plan,
although it might include demand for items that are also parents of MPS items.
Similarly, the MRP plan may also include both MPS planned and MRP planned items.
Project and Seiban References
If you are working in a project-based or Seiban environment, you can include
project/Seiban and task references to your schedule entries. These references will
accompany and drive the material planning process. See: Defining Schedule Entries
Manually
Loading the Master Schedule from Multiple Sources
You can derive the master schedule from a forecast, another master schedule, source
lists, or directly from sales orders. You can define your master schedule or modify
entries loaded from other sources.
Supply Chain Planning users can also load DRP planned orders. See: Loading the
Supply Chain Master Schedule from Multiple Sources
When you derive your master schedule from an existing schedule, you can modify your
master schedule quantities using a modification percentage or you can shift master
schedule dates by specifying a number of carry forward days.
Interorganization Orders
You can load planned order demand from a requesting organization into the master
demand schedule of the supplying organization. Supply Chain Planning users can run a
sequence of MRP processes for organizations to produce valid multi-organizational
material plans.
Supply Chain Planning users can define multiorganization replenishment strategies
with sourcing rules and bills of distribution. See: Sourcing Rules and Bills of
Distribution
Import Master Schedules from Outside Sources

You can import master schedule information generated by other systems into Oracle
MRP through the Open Master Schedule Interface. Oracle MRP validates the imported
information before it loads the information into a master schedule.
Oracle MRP gives you the option to define work date control when importing master
schedules. You can choose to reject master schedules entries that are submitted on
invalid workdays or can choose to have them move forward or backward to the next
valid workday.
Schedule Management
You can monitor your master demand schedule as customer shipments occur by
utilizing the MDS relief process.
You can maintain credible priorities or schedule dates and update your master
production schedule either manually or automatically through the MPS relief process.
You can report and implement the MPS by exception, only for those items that require
attention.
Various reports and inquiries are available to give you detailed information on your
master schedule status.
Automatic MPS Relief
You can automatically maintain your master production schedule with the auto-reduce
MPS attribute you specify for the item in the item master in Oracle Inventory. For each
item, you can specify a point in time after which you no longer want the item to appear
on the MPS. This point in time can be the demand time fence, the planning time fence,
or the current date depending on your business practices.
Master Scheduling by Demand Class
You can optionally associate a demand class to a master demand schedule or master
production schedule when you define the master schedule name. When you ship a sales
order or create a discrete job, that sales order or discrete job relieves the master
schedules that are associated with the demand class of the sales order or discrete job.
You can load a subset of the sales orders into your master schedule for a specific
demand class.
See also Overview of Capacity Planning, Oracle Capacity User's Guide
MPS Explosion Level

For MDS entries, this defines the lowest level at which an MPS planned part appears in
the bill of material structure for the item. When you generate an MPS plan, the process
does not explode beyond this level. This reduces MPS processing time.
The default value comes from the Max Bill Levels field in the Bill of Materials
Parameters window. Enter a value in the Master Demand Schedule Items window to
override the default. This value must be an integer and cannot be greater than 60.
Note: You should be extremely cautious when entering a value here. If
you are unsure of the lowest level that an MPS part exists, use the
default value. The explosion process explodes through the entire bill of
material. See: Defining Bills of Material Parameters, Oracle Bills of
Material User's Guide.
See also Defining Schedule Entries Manually
Defining a Schedule Name

Before you define a master schedule manually or load a schedule from another source,
you first define a name. You can also set several options for each name.
Defining an MPS name in Supply Chain Planning involves extra steps. Supply Chain
Planning users should refer to Defining a Supply Chain MPS Name for further
instructions.
If you launch a plan with an MPS names, you can also make a copy that is identical to
the original. You can then view, implement, and replan either copy, discarding the
altered plan at any time and preserving the original data. See: Making a Copy of a
Completed Plan
To define a schedule name:

1.
Navigate to the Master Demand Schedules or Master Production Schedules

window (MDS Names and MPS Names in the menu).
2.
Enter a name and description.
3.
Optionally, select a demand class.
4.
Save your work.

You can now define a master schedule manually, or load a schedule from another
source, with the name(s) you created.
To set additional MPS options:

1.
In the MPS window check Inventory ATP. You can optionally include your MPS
plan as available supply when you calculate available to promise information in
Oracle Inventory.
2.
In the MPS window, check Feedback to monitor the quantity of the planned order
that has been implemented as discrete jobs, purchase orders, or purchase
requisitions. This provides the planner visibility of the status of the plan at any
point in time.
3.
In the MPS window, check Production to enable a plan to auto-release planned

orders. See: Auto-release Planned Orders
To set relief options for a schedule name:

In addition to the steps above, enter the following information:
1.
Check Relieve to relieve schedule entries.

For master demand schedules, all sales order shipments relieve the appropriate
schedule entries (shipment relief). For master production schedules, when you
create discrete jobs, flow schedules, purchase orders, or purchase requisitions, you
relieve schedule entries (production relief).
If you associate a demand class with your schedule, the relief process updates those
schedule entries whose demand class matches a sales order, discrete job, flow
schedule, purchase order, or purchase requisition.
2.
Save your work.
To disable a schedule name:

Note: You can view disabled schedules but not modify them.
1.

window.
2.
Query a schedule name.
3.
Enter an inactive-on date.
4.
Save your work.

See Also
Defining Schedule Entries Manually
Schedule Relief
Available to Promise (ATP)

A schedule entry is a unique relationship between an item, date, and quantity on a
master schedule. You define schedule entries by adding items to schedule names, then
defining detailed date and quantity information for each item.
Manually defining an MPS entry in Supply Chain Planning involves extra steps. Supply
Chain Planning users should refer to Defining a Supply Chain MPS Entry Manually for
further instructions.
To define schedule entries manually
1.

window (MDS Names or MPS Names in the menu).
2.
Select a schedule name.
3.
Choose Items to open the Master Demand Schedule Items or Master Production
Schedule Items window.
You can choose the Folder menu to customize your display. See: Customizing the
Presentation of Data in a Folder, Oracle Applications User's Guide.
4.
Enter an item with an MRP planning method of MPS Planning. See: Defining Items:
5.
Enter a different MPS explosion level, if you want to change the default. See: MPS
Explosion Level
6.
Choose Detail to open the Master Demand Schedule Entries window or Master
Production Schedule Entries window.
7.
Enter a date.
For MDS, this is the date of shipment. For an MPS, this is the completion date of
production.
For repetitive items, whether MDS or MPS, this is the start date of production
8.
For repetitive items, enter an end date of production.
9.
Enter a current quantity.

This also becomes the original quantity and the total. Schedule reliefs reduce the
current quantity. Schedule reliefs plus the current quantity equals the total.
10. If you are working in a project environment, enter a valid project and task
reference.
Note: Your ability to enter project and task references is determined
by the organization parameters set in Oracle Inventory. If the

project control level is set to project, then the task column will be
dimmed, preventing you from entering task references. If the
control level is set to task, you can enter references into both
columns. See: Setting Up Project MRP in Oracle Inventory
Note: The Unit Number. field is visible if you have enabled Oracle
Project Manufacturing's end item model/unit effectivity feature.

See: Model/Unit Effectivity, Oracle Project Manufacturing
Implementation Manual.
11. Check Reliefs if you want this entry to be decremented when you create purchase
orders, purchase requisitions or discrete jobs - whether you define the purchase
requisitions or jobs manually or load them with the Planner Workbench.
12. Save your work.
See Also
Schedule Relief
Source Flag
Loading a Master Schedule from an Internal Source

To load a master schedule from an internal source
1.
Navigate to the Load/Copy/Merge Master Demand Schedule or Load/Copy/Merge

Master Production Schedule window.
2.
Choose one of the following names:
Load/Copy/Merge MDS
Copy/Merge MPS
Load MPS
3.
In the Parameters window, enter a destination schedule.
4.
Select a source type. See: Source Type Field
5.
Select a source organization.
6.
Select source name.
7.
Select a start date and a cutoff date.
8.
Select from a number of load options. See: Selecting Master Schedule Load Options
9.
Choose Submit Request.
Source Type Filed:

You can load a master schedule from any of the following internal sources:
specific forecast
interorg planned orders
sales orders only
specific MDS or specific MPS
source lists
Loading a master schedule in Supply Chain Planning involves extra steps. See: Loading
a Supply Chain MPS from and Internal Source
Specific Forecast:
When you load a master schedule from a forecast, Oracle MRP includes forecast entries
as follows:
From
To
Start day minus backward consumption days
Cutoff date
The load converts forecast entries for repetitive items into repetitive entries in the
master schedule - even if the original forecast entry does not have a forecast end date.
Master demand and production schedule entries for repetitive items must fall on valid
workdays.
Interorg Planned Orders

You can load planned order demand from one or more requesting organizations into
the master demand schedule of a supplying organization.
For example, Org 1 is the requesting organization. Org 1 considers the workstation an
MRP-planned item, internally replenished by Org 2. Org 2 manufactures the
workstation, where it is an MPS-planned item. The manufactured workstation includes
a monitor that Org 2 receives from Org 3.
To produce a valid multi-organization material plan, you:
generate planned orders for workstations in Org 1
load the master demand schedule for Org 2 with inter-organization planned orders
from Org 1
generate planned orders for monitors in Org 2
load the master demand schedule for Org 3 with inter-organization planned orders
from Org 2; this drives the planning process for Org 3
Sales Orders Only

With this source type, you can load either:
all sales orders
sales orders from today forward

Note: The Planning Manager must be running to guarantee a consistent
picture of demand. The load master schedule process does not pick up
any demand for sales orders that you place more recently than the last
execution of the planning manager.
Specific MDS or Specific MPS

You can:
load a schedule from one organization to another
copy a schedule within an organization
This feature is most useful to copy an existing schedule and modify the copy. You can
apply a modification percent to the new schedule and/or move schedule entries forward
or backward by a specific number of days.
Modification Percent
To increase the quantity of the new schedule, specify a percent by which to multiply the
schedule entries. Oracle MRP adds the result of the multiplication to the existing
quantities. To decrease the new schedule, enter a negative percent.
For example, to increase an existing schedule entry of 100 by 10 percent, specify a
modification percent of 10. The resulting schedule entry is 110. To decrease an existing
schedule entry of 100 by 10 percent, enter a modification percent of -10. The resulting
schedule entry is 90.
Carry Forward Days
To move schedule entries forward in time, specify a number of workdays. To move
schedule entries backward, enter a negative number. Holidays are not recognized as
workdays; the previous valid workday is used instead.
For example, the existing schedule contains an entry of 100 on Monday. Wednesday is a
holiday. The following Saturday and Sunday are not workdays. If you wish to move the
schedule entry to the next Monday, specify four carry forward days.
Source Lists
With this source type you can:
consolidate master schedules, plans, and forecasts from multiple organizations into
a single source
load multiple sources into a master schedule in one transaction
Selecting Master Schedule Load Options

For each type of master schedule load (for example, from a forecast or from
interorganization planned orders), you choose a number of load options. Not all options
apply to all load types.
Include Sales Orders:
To include sales orders in the load, select:
All sales orders: Include sales orders past due, up to the cutoff date.
Sales orders from start date forward: Include sales orders up to the cutoff date.
Sales Order Demand Class:

To limit the sales orders loaded to a particular demand class, select a demand class.
Only sales order items from this demand class are loaded.
Demand Time Fence:
To limit the source forecast with a demand time fence, select:
Load forecast outside demand time fence only: Ignore forecast entries on and within the
demand time fence. When you include sales orders and consume forecasts, this option
loads sales orders within the demand time fence, and the greater of sales orders and
forecasts outside the demand time fence.
Load orders within and forecast outside demand time fence: Load only sales orders on and
within the demand time fence, and only forecast entries outside the demand time fence.
Ignore demand time fence: Ignore the demand time fence. When you include sales orders
and consume forecasts, this option loads all forecast demand across the planning
horizon.
Note: Use the include sales orders option to also load sales order
demand across the planning horizon.
Overwrite
Overwrite To overwrite the existing entries of the destination schedule, select: All
entries: Erase all existing master schedule entries associated with the master schedule
name and load new entries.
For example, if you load master schedules MS-A and MS-B into master schedule MS-C
the first time and then load master schedule MS-B into master schedule MS-C the
second time, the result is that MS-C contains master schedules from the second load of
MS-B.
Same source only: Erase only the entries with a source that has been previously loaded
into the master schedule. This allows you to update master schedule information with
the latest picture of the sales orders, updated forecasts or master schedules.
For example, if you load master schedules MS-A and MS-B into master schedule MS-C
the first time and then load master schedule MS-B into master schedule MS-C the
second time, the result is that MS-C contains master schedules from the first load of
MS-A and the second load of MS-B.
Or, if you load sales orders into master schedule MS-C the first time and then load sales
orders again using this option. Master schedule MS-C reflects all the current sales
orders including those booked in the interim of the first and second loads.
To add new entries to the destination schedule, select:
No: This loads new entries, but does not erase existing master schedule entries.
Start Date
Select the start date of your schedule.
If you specify a start date Oracle MRP first selects the planning BOM entries that start
outside the start date, then explodes those entries. When you load a forecast into an
MDS, the master schedule load inserts all the forecast entries after the start date minus
backward update consumption days for the forecast set. The start date does not apply
to exploded entries that fall before start date due lead time offsetting from planning
BOM entries that start after the forecast load start date.
Cutoff Date
Select the cutoff date of your schedule.
When you load a forecast into an MDS, the master schedule load inserts all the forecast
entries prior to the cutoff date and adds forward update consumptions days for the
forecast set.
Explode
Select Yes to explode the schedule entries, down to the MPS explosion level. See MPS
Explosion Level.
Quantity Type:
To load forecast quantities, select:
Current: This loads the original forecast quantity minus any consumption quantities.
When you choose this option, you cannot choose to consume the forecast, since the
forecast quantities have already subtracted sales order demand.
Original: This loads the forecast without any consumption. When you choose this
option, you should choose to consume the forecast if you intend to load the master
schedule using forecasts and sales orders. Consuming the original forecast ensures that
demand is not overstated.

Note: To ensure a consistent picture of demand, you should load sales
orders and forecasts during the same load process, rather then loading
them in two separate steps. If you load them separately, and you create
sales orders in the interim, you could overstate or understate demand.
For example, suppose you define a forecast entry for 100 on 01-FEB and
load it into the master schedule. You create a sales order for 30 on
01-FEB. The forecast is consumed to 70, but the master schedule
remains at 100. You then load sales orders as a separate step. The total
demand for 01-FEB becomes 130, which overstates the actual and
forecasted demand. If you launched a single process instead of two,
you would see a forecast of 100 and no sales order demand, or a
forecast of 70 and a sales order for 30. Either way, the correct demand
of 100 results
Consume
Select Yes to consume the forecast. See Forecast Consumption.
Modification Percent
Enter a percent by which to multiple the schedule entries.
Carry Forward Days
Enter a number of workdays to move the schedule forward in time. To move the
schedule backward, enter a negative number.
Note: When you specify carry forward days, the start date and cutoff
date apply to the destination schedule, This allows schedule entries

before the start date or after the cutoff date to be loaded.
Backward Consumption Days

Enter a number of workdays the consumption process will move backward when
looking for a forecast quantity to consume. See: Backward and Forward Consumption
Days.
Outlier Percent
Enter the maximum percent of the original forecast that a sales order can consume. See:
Outlier Update Percent
Additional Factors Affecting a Master Schedule Load

There are several additional factors that can cause the destination master schedule to
differ from the source forecast or source master schedule:
if the source dates do not fall on a valid workday, Oracle MRP adjusts them to a
previous valid workday.
When loading a forecast or master schedule from another organization where the
workday calendar is different, the load process ensures that the schedule dates
match the workday calendar of the destination organization.
When loading a forecast or master schedule from another organization and the item
planning method is different (for example, repetitive vs. discrete) the load process
converts the schedule quantities accordingly.
When loading a forecast or master schedule from another organization and the item
unit of measure is different, the load process converts the unit of measure from the
source organization to the unit of measure of the item at the destination
organization.
Source Flag
Oracle MRP stores the source of each master schedule entry. This allows you to later
trace the source of master schedule entries.
Note: If you manually update a master schedule entry in the item
Master Schedule Entries window, Oracle MRP changes the source to

Manual.
How Forecasted Discrete Items Appear in the Master Schedule

When you load a forecast entry with no end date into the master schedule for a
discretely planned item, the schedule entry consists of a schedule date and quantity.
If the forecast is bucketed in days, the schedule date on the master schedule reflects
each day of the forecast. If the forecast is bucketed into weeks or periods, the schedule
date on the master schedule reflects the first day of either the weekly or periodic bucket.
For example:
Forecast for Discrete Item
Bucket
Forecast Date
Rate End Date
Forecast Quantity
Days
04-Jan
100
Weeks
17-Jan
200
Periods
31-Jan
400
Forecast Loaded into Master Schedule

Schedule Date
Rate End Date
Quantity
Daily Quantity
04-Jan
100
17-Jan
200
31-Jan
400
When you load a forecast entry with an end date into the master schedule, the schedule
entry consists of a schedule date and quantity. If the forecast is bucketed into days,
there is a schedule entry for each day between the forecast date and the forecast end
date. If the forecast entry is in weekly or periodic buckets, the schedule date is the first
day of either the weekly or periodic bucket.
For example:
Bucket
Forecast Date
Rate End Date
Forecast Quantity
Days
04-Jan
06-Jan
100
Weeks
17-Jan
24-Jan
200
Periods
31-Jan
28-Feb
400

Schedule Date
Rate End Date
Quantity
Daily Quantity
04-Jan
100
05-Jan
100
06-Jan
200
17-Jan
200
Schedule Date
Rate End Date
Quantity
Daily Quantity
24-Jan
200
31-Jan
400
28-Feb
400
How Forecasted Repetitive Items Appear in the Master Schedule

When you load a forecast entry with no end date into the master schedule for a
repetitively planned item, the schedule entry consists of a schedule date rate end date.
The rate end date on a weekly or periodic forecast is the last bucket that Oracle MRP
loads into the master schedule. If it falls before the cutoff date you enter daily quantity.
If the forecast is in daily buckets, the schedule date and the rate end date are the same.
If the forecast is bucketed in weeks or periods, the schedule date is the first day of the
week or period, and the schedule end date is the end of that week or period. The daily
quantity is what was forecasted for that week or period divided by the number of days
in that time frame. For example:
Bucket
Forecast Date
Rate End Date
Forecast Quantity
Days
04-Jan
100
Weeks
17-Jan
200
Periods
31-Jan
400

Schedule Date
Rate End Date
Quantity
Daily Quantity
04-Jan
04-Jan.
100.
17-Jan
21-Jan.
40 (assuming 5
workdays)
Schedule Date
Rate End Date
Quantity
Daily Quantity
31-Jan
26-Feb.
20 (assuming 20
workdays)
When you load a forecast entry with an end date into the master schedule for a
repetitively planned item, the schedule entry consists of a schedule date, a rate end
date, and a daily quantity. If the forecast is in daily buckets, the schedule date is the
same as the forecast date, and the rate end date is the same as the forecast end date. The
forecasted quantity becomes the daily quantity. If the forecast is in weekly or periodic
buckets, the schedule date is the first day of the week or period, and the schedule end
date is the end of that week or period. The daily quantity is what was forecast for that
week or period divided by the number of days in that time frame.
For example:
Forecast for Repetitive Item
Bucket
Forecast Date
Rate End Date
Forecast Quantity
Days
04-Jan
06-Jan
100
Weeks
17-Jan
24-Jan
200
Periods
31-Jan
28-Feb
400

Schedule Date
Rate End Date
Quantity
Daily Quantity
04-Jan
04-Jan.
100.
17-Jan
21-Jan.
40 (assuming 5
workdays)
24-Jan
28-Jan
40
31-Jan
26-Feb.
20 (assuming 20
workdays)
Schedule Date
Rate End Date
Quantity
Daily Quantity
28-Feb
26-Mar
20
If you specify rounding control for an item, the load process does round up any
fractional quantities. The load process considers any additional quantity calculated due
to rounding as excess when calculating future time buckets.
For example:
Forecast for Repetitive Item with Rounding
Bucket
Forecast Date
Rate End Date
Forecast Quantity
Days
08-Feb
11-Feb
100
Weeks
14-Feb
11-Mar
518
Forecast Loaded into Master Schedule with Rounding

Schedule Date
Rate End Date
Quantity
Daily Quantity
08-Feb
11-Feb
100.
14-Feb
18-Feb
104
21-Feb
25-Feb
104
28-Feb
04-Mar
103
07-Mar
11-Mar
104
Note the period from 28-FEB through 04-MAR only requires 103 a day since the
previous periods spanning 14-FEB through 25-FEB are overestimates due to rounding.
Planning Spares Demand

Master scheduling is effective for planning spares demand, when spares items are also
components of end products. Demand for spares or replacements is another form of
independent demand.
The planning method appropriate for spares demand may be MPS planning or MRP
planning. Use MPS planning if the item has spares demand and still requires personal
control. The MPS planning process plans the spares demand, and you can manually
adjust the quantities/dates of the resulting master schedule entries before you use the
master schedule for your material requirements plan.
To manually include spares demand in the master schedule:
Follow the procedure for defining a master schedule manually. See: Defining Schedule
Entries Manually.
To forecast spares demand and load results into the master schedule:
Follow the procedure for loading a master schedule from a forecast. See: Loading a
Master Schedule From an Internal Source.
Schedule Relief
Shipment Relief
Oracle MRP relieves (updates) MDS schedule quantities when you ship sales order
items. Shipment (MDS) relief prevents the duplication of demand that could result if
you load sales orders into the master demand schedule, but do not relieve the master
demand schedule upon shipment. Without relief, you would need to reload and replan
your master schedule just before planning material requirements each time to obtain an
accurate picture of supply and demand for your independent demand items.
Shipping a sales order item relieves each MDS name for which you set the check Relieve.
You set shipment relief when you define the master schedule name before you define or
load a schedule for that name. If you associate a demand class with your MDS, the
shipment relief process relieves the MDS entries that correspond to the demand class
associated with the sales order.
You can change the shipment relief option after initially creating your master schedule.
If you change the shipment relief on an MDS from On to Off, shipment relief stops
occurring against that master schedule. If you change the shipment relief option from
Off to On, shipment relief occurs on that master schedule from the date you change the
option onward.
For repetitive master demand schedule items, the Planning Manager begins at the start
date of the schedule rate and relieves the schedule entry by eliminating days according
to the rate. For example, suppose you have a master demand schedule with a daily
quantity of 10 per day over 5 days, beginning on Monday. You ship a sales order with a
quantity of 12. The planning manager consumes the first day of the rate, accounting for
10 out of 12 shipped units. For the remaining 2 units, the planning manager creates a
new schedule entry beginning and ending on Tuesday, with a daily quantity of 8 (10
minus 2). The planning manager then resets the start date of the first schedule entry
from Monday to Wednesday, and maintains the daily quantity of 10 per day.
Production Relief
Oracle MRP relieves (updates) MPS schedule quantities when you create purchase
orders, purchase requisitions or discrete jobs - whether you define the purchase
requisitions or jobs manually or load them with the Planner Workbench.
Production (MPS) relief prevents the duplication of supply. Without relief, you would
need to replan your master schedule just before planning material requirements each
time to obtain an accurate picture of supply and demand for your MPS planned items.
Creating a purchase order, purchase requisition, or discrete job relieves each MPS name
for which you check Relieve. You set production relief when you define the master
schedule name - before you enter or load a schedule for that name. If you associate a
demand class with your MPS, the production relief process relieves the MPS entries that
correspond to the demand class associated with the discrete job.
You can change the production relief option after initially creating your master
schedule. If you set or unset the production relief on an MPS name, production relief
stops occurring against that master schedule. If you change the production relief option
from Off to On, production relief occurs on that master schedule from the date you
change the option onward.
Oracle MRP also updates the MPS schedule quantities when you reschedule discrete
jobs, or when you change discrete job, purchase order, or purchase requisition
quantities.
Note: Oracle MRP does not consume MPS entries for repetitive items.
Repetitive schedules are recalculated each time the planning process

runs. Therefore, it does not decrease the MPS for repetitive items.
MPS Relief of Phantoms

If you define any phantom items with a planning method of MPS Planned, production
relief occurs when the discrete job for the phantom's parent is created.
Supply Chain Planning users can also relieve production schedules for phantom items
with a planning method of MPS/DRP Planned.
Maintaining the Accuracy of the MPS
Typically, when Oracle MRP relieves a master production schedule, it decrements
(decreases) one or more schedule entries because you created a discrete job or purchase
requisition, or increased the quantity on an existing job or requisition. However, when
you decrease the quantity on an existing job or purchase requisition, close the job short of
the full job quantity, or cancel the requisition line, Oracle MRP increments (increases)
one or more schedule entries, if possible. Oracle MRP never increments a schedule entry
by more than the original schedule amount.
Viewing Master Schedule Relief Information

You can view itemized information about the sales order shipments and discrete jobs
that relieve your master demand and master production schedules respectively with the
MDS Reliefs or MPS Reliefs window. The original schedule quantity shows you the
quantity before schedule relief. The current schedule quantity is the relieved schedule
quantity. The difference between the original and current quantity is the sum of all
relief activity against the master schedule entry.
To compare this picture of your master schedule with previous or future versions, you
can copy your master schedule periodically (by using the Load/Copy/Merge Master
Schedule window) and store the copy for later comparison. Use the Schedule
Comparison report to compare the different schedules.
Profile Options for Master Schedule Relief

You have the option to temporarily disable shipment and production relief by setting
the MRP:Consume MDS profile and MRP:Consume MPS profile options to No. The
Planning Manager verifies the setting of this option before performing shipment and/or
production relief. If it is set to No, the Planning Manager does not update MDS and/or
MPS entries. The Planning Manager processes any sales order shipments and/or
purchase requisitions and discrete jobs occurring while this profile is set to No when
you set the profile option back to Yes.
Note that this affects all master demand and master production schedules that have
relief set to Yes.
You can also specify the direction in which the production relief takes place by using
the MRP: MPS Relief Direction profile option. If you specify Backward, then forward,
Oracle Master Scheduling and Supply Chain Planning relieves master production
schedule entries backwards from the discrete job due date then forwards until it finds
enough schedule quantity to relieve. If you specify Forward only, Oracle Master
Scheduling and Supply Chain Planning relieves master production schedule entries
only forward from the discrete job due date until it finds enough schedule quantity to
relieve.
Note: When you change any of these profile options you must restart
the Planning Manager to activate the new profile option.
Planning Manager and Schedule Relief
Planning Manager and Schedule Relief

The Planning Manager is the background process that manages shipment and
production relief.
For shipment relief, the Planning Manager first looks for the specific sales order entry to
find a specific schedule entry to relieve. If it does not find an entry for that exact sales
order date, the Planning Manager begins at the oldest schedule entry for the item and
moves forward in time, decrementing schedule entry quantities until is reaches the sales
order shipment quantity.
For example, suppose you have MDS entries of 10 each on Monday, Tuesday, and
Wednesday. If you ship a sales order for 25 on Tuesday, the relief process deducts 10 on
Tuesday (leaving 0), deducts 10 on Monday (leaving 0), and deducts the remaining 5 on
Wednesday (leaving 5). Thus, the new master schedule entries are quantity 0, 0, and 5
on Monday, Tuesday, and Wednesday, respectively.
For production relief, the Planning Manager first looks at the discrete job due date to
find an MPS schedule entry to relieve. It then looks backward, up to the first schedule
entry, and then forward until it finds enough schedule quantity to relieve.
For example, suppose you have MPS entries of 10 each on Monday, Tuesday, and
Wednesday and you specify the MRP: MPS Relief Direction profile option as
Backward, then forward. If you create a discrete job for 25 on Tuesday, the relief
process deducts 10 on Tuesday (leaving 0), deducts 10 on Monday (leaving 0), and
deducts the remaining 5 on Wednesday (leaving 5). Thus, the new master schedule
entries are quantity 0, 0, and 5 on Monday, Tuesday, and Wednesday, respectively.
Note: When it operates, the Planning Manager may run for a very short
time only, making it difficult to determine whether is it running. To be

sure, examine the messages in the Planning Manager window.
Messages should increment periodically. Whether you use shipment or
production relief, you should activate the planning manager and leave
it running. The planning manager performs maintenance tasks vital to
the proper operation of Oracle MRP.
See Also
Tracking Demand Schedule Reliefs

You can track reliefs against a Master Demand Schedule for both the product family
and the member items. You cannot track reliefs against a Master Production Schedule at
the product family item level because the MPS for a product family item does not get
relieved when the MPS for the member item gets relieved.
The procedure for tracking reliefs for a product family item is the same as that for any
individual item.
To see which orders relieved the MDS, do this:
1.
Navigate to the Item Master Demand Schedule Entries window.
2.
Query to find the schedule you are interested in tracking.
3.
Navigate to the Schedule Entry for the product family item.
4.
Click the Reliefs button to see the order quantity and relief quantity for each order.
See Also
Overview of Production Planning
Production Planning
Tracking Forecast Consumptions
Consumption for a Product Family
Rough Cut Capacity Planning

RCCP verifies that you have sufficient capacity available to meet the capacity
requirements for your master schedules. It is a long-term capacity planning tool used to
balance required and available capacity, and to negotiate changes to the master
schedule and/or available capacity. You can change your master schedules by changing
master schedule dates and increasing or decreasing master schedule quantities. You can
change your available capacity by adding or removing shifts, using overtime or
subcontracted labor, and adding or removing machines.
Use RCCP to validate your master schedules against key and critical resources before
you use the planning process to generate detailed MRP plans. You can perform rough
cut capacity planning at two levels:
Routing-based to plan rough cut capacity by resource
Rate-based to plan your rough cut capacity by production line
See Also
Overview of Rough Cut Capacity Planning, Oracle Capacity User's Guide
Routing-Based RCCP, Oracle Capacity User's Guide
Rate-Based RCCP, Oracle Capacity User's Guide
Generating RCCP, Oracle Capacity User's Guide
Viewing RCCP, Oracle Capacity User's Guide
4
Material Requirements Planning

Supply Chain Planning users can employ additional functionality to generate and
manage their material and distribution requirements across multiple, interdependent
organizations. See: The Multiple Organization Model and Material and Distribution
Requirements Planning.
Material requirements planning (MRP) calculates net requirements from gross
requirements by evaluating:
The master schedule
Bills of material
Scheduled receipts
On-hand inventory balances
Lead times
Order modifiers
It then plans replenishments by creating a set of recommendations to release or

reschedule orders for material based on net material requirements. These planned
recommendations are stated in:
discrete quantities, with due dates
repetitive build rates, with first and last unit start dates
Oracle MRP assumes infinite capacity is available to meet the material requirements
plan. However, you can use capacity planning to verify that sufficient capacity exists to
support your material plan.
Material Requirements Planning 4-1
Supply Chain Planning users can also generate distribution requirements plans (DRP)
and manage their material requirements across multiple, interdependent organizations.
See: Material and Distribution Requirements Planning.
Note: The planning products support Oracle Project Manufacturing's
end item model/unit effectivity. The Unit Number field is visible if this
featured is enabled allowing you to do the following tasks:
Load sales orders into a MDS, and have the specified unit number
carried over to the schedule entry.
Create demand and generate planned orders with unit number

specified.
See Also
Overview of Planning Logic, Overview of Capacity Planning, Oracle Capacity User's
Guide Model/Unit Effectivity, Oracle Project Manufacturing Implementation Manual
Overview of Planning Logic

Oracle MRP provide many different item and plan level attributes that give you the
flexibility for generating material and distribution requirements plans that satisfy your
business needs.
The planning process calculates net material requirements from:
the master schedule
bills of material
scheduled receipts on-hand inventory balances
lead times
order modifiers
The purpose of the planning process is to derive an MPS, DRP or MRP that meets
schedule dates while maintaining inventory levels within your "material" policies.
You can validate a material plan against available capacity using rough cut capacity
planning (RCCP) or detailed capacity requirements planning (CRP).
You can create multiple MPSs, MRPs or DRPs for simulation purposes and for testing
different business scenarios. If you use the Memory-based Planning Engine, you can
simulate changes to any MPS or MRP.
Supply Chain planning logic is further described in Overview of Supply Chain
Planning Logic.
See Also
Overview of Supply Chain Planning Logic
Supply Chain Planning Methods
MRP Planning Methods in Oracle Inventory

You can define an MRP planning method for an item when you define an item in Oracle
Inventory. Items that are considered by the planning process must have one of the
following MRP planning methods:
MPS Planning
MRP Planning
Oracle Supply Chain Planning users can define three additional attributes (See: Supply
Chain Planning Methods):
DRP Planning
MPS and DRP planning
MRP and DRP Planning
MPS Planning
Select MPS planning for items that you want to master schedule and maintain personal
control. MPS planning is most effective for:
planning items with independent demand
items that are critical to the business
items that control critical resources
MRP Planning
If your demand is smooth or predictable, you may not require master production
scheduling. Select MRP Planning for these items and use the master demand schedule
to drive the material requirements plan.
Or, you can select MRP Planning for those items with dependent demand that you want
the planning process to plan and maintain. You can also select MRP Planning for those
items with independent demand that do not require personal control.
Suggestion: You can set the MRP planning method item attribute to MPS Planning so
that the long-term material requirements for an item are generated.
Inventory Planning Methods
In addition to an MRP planning method, you can use the following inventory planning
methods for an item:
Min-Max Planning Reorder Point Planning Min-Max Planning Select Min-max
planning to define a minimum quantity that you want on hand. When you reach this
quantity, you reorder. You also define a maximum on-hand quantity that you do not
want to exceed.Reorder Point Planning You may also want to set the Inventory
Planning Method item attribute to Reorder Point planning to facilitate automatic order
execution.
Refer to the topic Requesting the Reorder Point Planning Report, , in the Inventory
User's Guide.
See Also Defining Items, Oracle Inventory User's Guide
Overview of Plan Generation

The Oracle planning process explodes through the bill of material to generate
component requirements by evaluating:
order modifiers
lead times
bill of material changes
engineering changes
item information
It then calculates time-phased material requirements. Each item may have different
attributes that affect the recommendations generated by the planning process.
Supply Chain Planning users can also generate DRP and supply chain MRP and MPS
plans. Supply Chain Planning users should refer to Overview of Plan Generation in
Supply Chain Planning for further information.
MPS Plan Generation

You can launch the planning process for an MPS plan from a master demand schedule.
This generates an MPS plan for all your MPS planned items. Oracle MRP also plans any
MRP planned items that have an MPS planned component. This ensures that all derived
demand is correctly passed down.
Once you have generated an MPS plan, you can make a copy of the plan that is identical
to the original. You can then view, implement, and replan either copy, discarding the
altered plan at any time and preserving the original data.
See Also
Material Requirements Plan Generation
MRP Planning Methods
Launching the Planning Process
Reviewing or Adding Plan Options
MRP Generation
You can launch the planning process for an MRP plan from a master demand schedule
or a master production schedule. This generates planning recommendations for all
planned items.
Once you have generated an MRP plan, you can make a copy of the plan that is
identical to the original. You can then view, implement, and replan either copy,
discarding the altered plan at any time and preserving the original data.
From a Master Demand Schedule
If you do not need to smooth production or otherwise manually manipulate a master
production schedule, you can generate a plan directly from a master demand schedule.
The planning process overrides the MRP planning method and treats MPS planned
items as MRP planned items, DRP planned items, or DRP/MRP planned items. As a
result, the planning process generates planned orders and reschedules
recommendations for your MPS, MRP, and DRP planned items.
From a Master Production Schedule
You can also generate an MRP plan from a master production schedule. For each MPS
planned item, the planning process considers projected gross requirements, current
orders for the item, the master production schedule, and on-hand quantities over time.
The planning process calculates the projected quantity on hand and generates exception
messages to signal any potential imbalances in the material plan. By default, the
planning process generates firmed planned orders for MPS planned items.
Note: A warning message displays informing you when releasing MPS
planned orders in MRP. Items planned in MPS are not replanned in

MRP.
See Also
MPS Plan Generation
Defining MRP Names

By defining multiple MRP names, you can define any number of material requirement
plans. You can use multiple plan names to simulate MRP for different sets of data.
Supply Chain Planning users can also define DRP and multi-organization MRP. Supply
Chain Planning users should refer to Defining MRP/DRP Names in Supply Chain
Planning for further instruction.
To define an MRP name :

1.
Navigate to the MRP Names window.
2.
Enter an alphanumeric name to identify a unique material requirements.
3.
Check Feedback to monitor the quantity of the planned order that has been
implemented as discrete jobs, purchase orders, or purchase requisitions. This
provides the planner visibility of the status of the plan at any point in time.
4.
Check Production to enable a plan to auto-release planned orders. See: Auto-release

Planned Orders.
5.
Enter an inactive on date on which to disable the plan. As of this date, you can no
longer update the plan, nor use the plan name in the planning process. You are still
able to view information and run reports for disabled names.
6.
Save your work

See Also Planner Workbench Reviewing or Adding Plan Options

You can launch the planning process for a material requirements plan (MRP) or a
master production schedule (MPS). The planning process involves three phases for
defining the MRP or MPS. It uses the input from a master demand schedule or master
production schedule to determine the quantities and timing of the items to be
manufactured or purchased.
Note: If you're using the Drop Shipment feature of Order Entry and
Purchasing, you've set up logical orgs for P.O. receipts. Do not use
these logical orgs for planning purposes.
Supply Chain Planning users can also launch a DRP and supply chain MRP and MPS
plan. Supply Chain Planning users should refer to Launching the Supply Chain
Planning Process for further instruction.
Prerequisites
Before you can launch the planning process, you must:
For MPS or MRP: define at least one master demand schedule or master production
schedule. See: Defining a Schedule Name.
Define at least one master production schedule and create at least one MRP name.
See: Defining MRP Names.
To launch a planning process

1.
Navigate to the Launch MPS or Launch MRP window.
2.
In the parameters window, select a plan name and launch options.

Note: You must launch the Planner if you enter Yes to launch the
Snapshot.
Anchor Date: Enter a date, earlier or equal to the current date, that will act as a start
date for repetitive planning periods.
Plan Horizon: Enter a date, greater than the current date, up to which the planning
process creates an MRP or MPS. The default horizon is the current date plus the
number of offset months set in the profile MRP:Cutoff Date Offset Months.
Note: You may want to enter a date earlier than the default to save
processing time or to cut down on the volume of information

generated.
3.
Choose OK.
4.
In the Launch window, choose Submit.

See Also
Overview of the Memory-based Planning Engine
Phases of the Planning Process
Overview of Capacity Planning, Oracle Capacity User's Guide Submitting a

Request, Oracle Applications User's Guide Reviewing or Adding Plan Options
Making a Copy of a Completed Plan

Once you have generated an MPS, MRP, or DRP plan, you can make a copy that is
identical to the original. The copy will contain all the supply/demand records and
options that are in the source plan. You can then view, implement, and replan either
copy, discarding the altered plan at any time and preserving the original data.
Prerequisites
Before you can copy a plan, you must:
Define an MPS, MRP, or DRP name and run a plan under that name. This will be
your source plan.
Define a plan name of the same type as your source plan (MPS, MRP, DRP). This
will be your destination plan.
Restrictions
The source and destination plans must be the same type. For instance, you cannot
copy an MRP source plan into an MPS destination plan.
The same organization must own both source and destination plans.
You must log into the same organization that owns the source and destination
plans.
The responsibility of the user that generated the source plan must be the same as
the user that defined the destination plan. For instance, a source plan generated by
a user with material planner responsibilities cannot be copied into a destination
plan defined by a user with supply chain planner responsibilities.
The production and feedback flags, and all plan options are copied from the source
to the destination plan. Any flags or options you set will be overwritten during the
copy process.
To copy a previously generated plan

1.
Navigate to the Launch Copy Plan window.
2.
In the Parameters window, select a source plan name and a destination plan name.
Note: If you see the error message, No entries found for List of Values,
you have not defined a valid source or destination plan. Refer to

the prerequisites and restrictions listed above if you see this
message.
3.
Choose OK.
4.
In the Launch Copy Plan window, choose Submit.

See Also
Defining MRP Names
Defining a Supply Chain MPS Name
Launching the MPS/MRP Planning Process
Launching the Supply Chain Planning Process

You can enter additional plan options for any plan. You can also view plan options in
the Plan Status window.
Note: If you are launching the planning process for this plan name for
the first time, the plan options you defined in the setup parameters are
displayed. Otherwise, the plan options you chose for the last launch of
the planning process are displayed.
Supply Chain Planning users can also launch a DRP and supply chain MRP and MPS
plan. Supply Chain Planning users should refer to Reviewing or Adding Supply Chain
Plan Options.
To add plan options

1.
Navigate to the Plan Options window.
2.
Query a plan name.
3.

All: For an MPS plan, overwrite all entries and regenerate new MPS entries based
on the source master demand schedule.
For an MRP, overwrite all planned orders and MRP firm planned orders for MRP
items.
This option is displayed when you generate a plan for the first time.
Note: Be very cautious when using this option since it overwrites
firm planned orders and/or master schedule entries. If you do not

want to overwrite MRP firm planned orders, select None.
Outside planning time fence: For an MPS plan, overwrite all MPS entries outside the
planning time fence.
For an MRP, overwrite all planned orders and firm planned orders outside the
Note: Be very cautious when using this option since it overwrites
MRP firm planned orders and master schedule entries outside the
planning time fence. If you do not want to overwrite MRP firm
planned orders, select None.
None: Do not overwrite any firm planned orders for MPS or MRP plans and net
change replan.
4.
Check Append Planned Orders to append new planned orders in the following
situations:
If the MPS plan name has an existing schedule associated with it and you enter
None as the overwrite option, the planning process does not recommend
rescheduling or suggest new planned orders before the end of the existing MPS (the
last planned order) even if so indicated by new demand from the master demand
schedule. This is analogous to firming your master production schedule. By not
overwriting, the master scheduler is taking responsibility for manually planning
items. For an MRP plan name, this option creates planned orders where needed,
considering existing MRP firm planned orders.
Note: If you want to add firm planned orders using net change
replan, set the overwrite option to Outside planning time fence or

None.
If the plan name has an existing MPS or MRP associated with it and you enter All as
the overwrite option, the planning process deletes all previous planned entries and
creates new planned orders based on the source master schedule.
If the plan name has an existing MPS or MRP associated with it and you enter
Outside planning time fence as the overwrite option, the planning process deletes all
planned entries after the planning time fence and creates new planned orders after
that date. In this case, since you are overwriting after the planning time fence, you
are also appending new planned orders after that date.
If the plan name has an existing MPS or MRP associated with it and you enter None
as the overwrite option and do not check this, the planning process reports the
instances where the plan is out of balance with the source master schedule. It does
not recommend any new orders. Instead it lets you manually solve any problems in
the process. This gives maximum control to the master scheduler and/or material
planner.
5.
Check Demand Time Fence Control to indicate whether the planning process
considers any demand from forecasts within the demand time fence.
The planning process does not consider demand from forecasts within the demand
time fence, but considers demand from sales orders.
6.
Check Net WIP to indicate whether the planning process considers standard
discrete jobs, non-standard discrete jobs, or repetitive schedules when planning
items during the last plan execution.
7.
Check Net Reservations to indicate whether the planning process considers stock
designated for a specific order when planning the items during the last execution of
the plan.
8.
Check Snapshot Lock Tables to indicate whether tables are locked during the
snapshot process to guarantee consistent data.
This option temporarily prevents other users from processing certain transactions.
9.
violates planning time fences for items.
For discrete items, the planning process does not create planned orders or
recommend to reschedule in existing orders within the planning time fence of the
item. The planning process can still recommend to reschedule orders out.
For repetitive items, the planning process can vary the suggested schedule from the
optimal schedule, within the planning time fence, by the acceptable rate increase
and/or decrease you specified for the item.
Note: For purchase requisitions and internal requisitions, the
planning process ignores the planning time fence in all cases.
10. Check Net Purchases to indicate whether the planning process considers approved
purchase requisitions when planning the items during the last execution of the plan
11. Check Plan Safety Stock to indicate whether the planning process calculates safety
stock for each item during the last plan execution.

12. Check Plan Capacity to indicate whether you want to generate a capacity plan.
13. If you checked Plan Capacity, specify the Bill of Resources (for MPS plans only)
and, optionally, a Simulation Set. See: Capacity Modifications and Simulation,

Oracle Capacity User's Guide and Bills of Resources, Oracle Capacity User's Guide.
14. Check Pegging to calculate graphical pegging information. See: Overview of
Graphical Pegging. The planning process then traces supply information for an item
to its corresponding end demand details, which you then can view in a graphical
display.
15. If you are working in a project environment, set a Reservation Level and
(optionally) a Hard Pegging Level. See: Reviewing or Adding Project MRP Plan
Options.
Operation start date: Schedule material to arrive in inventory for availability on the
start date of a specific operation in the manufacturing process.
Order start date: Schedule material to arrive in inventory for availability on the work
in process order start date.
17. Specify which planned items or components you want included:
Note: If you are launching the planning process for a master
production schedule, you cannot edit or enter data in MDS/MPS

components fields.
All planned items: Include all planned items in the planning process. You would
chose this option to be certain that all item are planned, such as those you add to a
job or schedule that are not components on any bill.
Note: You may want to plan using this option to avoid missing
items you want to plan. For items you do not want to plan, define
them with an MRP planning method of Not planned when you
define an item in Oracle Inventory.
Demand schedule items only Supply schedule items only Demand
and supply schedule items
18. Save your work.
See Also
Planner Status:
Planner Workbench
Time Fence Planning
Defining Items, Oracle Inventory User's Guide
Viewing Pegged Supply and Demand
Order Modifier
Order sizing is a set of item attributes that allow you to control the recommended order
quantities for planned orders. The planning process creates planned orders using basic
lot-for-lot sizing logic.
Note: The planning process ignores order modifiers for items that have
a phantom supply type. See: Supply Types, Oracle Work In Process

User's Guide.
Lot-for-Lot
Lot-for-lot generates planned orders in quantities equal to the net requirements for each
day. To modify the lot size recommended by the planning process, you can use several
different order modifiers.
Your company may have order policies for dependent demand items that differ from
the lot-for-lot order sizing technique. You can express your company's order policies for
these items using order modifiers. Order modifiers regulate the size and timing of
planned orders, both discrete (quantity) and repetitive (rate).
For a given inventory item, you can establish order quantities as fixed or variable.
Fixed order quantity fixes the size of the order, but the time interval between orders
depends on actual demand.
Variable order quantity policies include: fixed lot multiple, minimum and maximum
order quantity, and fixed days supply.
Fixed Order Quantity
The planning process places one or more orders for the user-defined quantity or
repetitive rate.
For discretely planned items, when the requirement for a given date exceeds the
fixed order quantity, place multiple orders.
For repetitively planned items, either recommend a rate equal to the fixed order
quantity or a rate of zero.
Fixed Lot Multiple

The planning process places single orders in quantities that are multiples of the
user-defined quantity or rate.
For example, when the fixed lot multiple quantity is 100 and the requirement equals 110
units, place a single order for 200 units.
Minimum and Maximum Order Quantity
The planning process places one or more orders for at least the minimum quantity, but
no greater than the maximum quantity.
For discretely planned items, when the requirement for a given date exceeds the
maximum order quantity, the planning process places multiple orders.
Fixed Days Supply
The planning process places single orders for the quantity that covers the requirements
for the user-defined number of days. When suggesting planned orders, the planning
process looks forward this many days and accumulates all of the demand in that time
period. It then suggests a planned order to satisfy the total quantity required for that
time period.
Rounding Order Quantities
You can define, for each inventory item, whether the planning process should round
order quantities when the actual order quantity is calculated as a fraction. If you choose
to round, order quantities are rounded to the next highest whole number.
Note: By rounding up, the planning process may suggest a planned
order for more than what is actually needed. This extra quantity is
carried over into the next period as supply; therefore, the planning
engine rounds other orders down to account for the excess supply from
the last period.
Order Modifiers Logic

The following diagram shows the logic that the planning process uses when planning
with order modifiers.
See Also
Item and Bill of Material Attributes

Planning recommendations are created based on many different bill of material and
item attributes. Shrinkage rates, component yield and safety stock are some examples of
attributes that affect the outcome of the planning process. There are various bill of
material and item attributes that you can use to adjust the planning recommendations
so that they conform to your manufacturing policies.
Standard Bills and Routings Only

For planned orders, only standard bills and routings are planned. Alternate bills or
routings are not considered. For a discrete job, you may specify an alternate bill and/or
routing. The planning process sees component requirements of the alternate routing for
that job.
Phantom Bills of Material

A phantom bill (also known as a phantom assembly) describes a normally non-stocked
assembly or subassembly. One purpose of a phantom bill of material is to allow you to
manufacture and stock the assembly when necessary. You can use phantoms, for
example, to build and stock occasional spares for field service requirements.
When you implement planned orders for the parent of the phantom, Oracle Work in
Process blows through the phantom and creates requirements for its components,
ignoring any on-hand quantities of the phantom. Typically you set the lead time of the
phantom to zero to avoid any additional lead time offset for the components.
Oracle MRP uses the bill of material attribute to determine a phantom. Instead of
passing the parent's planned orders to the phantom, netting the phantom and passing
requirements to the phantom's components, the engine blows through the phantom to
create component planned orders.
Using the bill of material attribute to determine phantoms has two advantages: it allows
for more flexibility, since a component can be a phantom in one bill and not another,
and it makes treatment of phantoms in Oracle MRP consistent with Oracle Work in
Process.
Manufactured or Purchased
Three item attributes are evaluated to determine if planned orders are generated and
implemented into discrete jobs, repetitive schedules, or purchase requisitions.
Supply Chain Planning users can supplement and refine this behavior with sourcing
rules and bills of distribution. See: Sourcing Rules and Bills of Distribution
Make or Buy
This item attribute determines how the item is planned. The planning process looks at
the Make or Buy item attribute to determine whether to generate component
requirements. The attribute can have a value of Make or Buy and is directly related to
the Build in WIP and Purchasable item attributes.
When implementing orders via the Planner Workbench, the make or buy attribute is
used as the default for the type of planned order you can implement, either purchased
or manufactured.
Build in WIP
This item attribute establishes if the item can be manufactured.

Purchasable
This item attribute allows you to establish whether the item can be placed on purchase
orders or requisitions.
The following table illustrates the impact of these item attributes on the planning
process:
Make or Buy
Build in WIP
Purchasable
Planning Recommendation
Make
Yes
No
Plan manufactured planned orders when

needed and pass down component demand.
You can only implement discrete jobs, flow
schedules, or repetitive schedules for this
item. Purchase orders or requistions cannot be
created.
Make
Yes
Yes
Plan manufactured planned orders when

necessary and pass down component demand.
When implementing planning
recommendations you have the option to
implement a manufactured order (default) or
a purchase requistion.
Buy
No
Yes
Plan purchase requisitons when needed and

do not pass down component demand. You
can only implement purchase requistions for
this item. Discrete jobs, flow schedules, or
repetitive schedules cannot be created.
Buy
Yes
Yes
Plan purchase requistions when needed and

do not pass down component demand. When
implementing planning recommendations you
have the option to implement a purchase
requistion (default) or a manufactured order.
Bulk Items
Bulk items are those you issue in bulk to work in process, to cover a period of time, or
to fill a fixed size container. Normally, you do not issue these items to specific discrete
jobs, flow schedules, or repetitive schedules.
You might designate an item as Bulk for many reasons. Perhaps it is not cost effective to
transact these items for each individual job or schedule. Or, a bulk item might be easier
to manage if you place a large quantity in a central floor stock location.
For example, bulk items might be nuts, bolts, and other hardware used in the
manufacturing process. You issue quantities of 10,000, for instance, to a floor stock
location using the account issue transaction provided by Oracle Inventory. Work in
process obtains the hardware from floor stock when needed. By making this hardware
available in floor stock, and not pushing or pulling it to each job or schedule, you can
save the cost of performing additional transactions.
The planning process creates planned demand for bulk items by exploding their usage
on a bill of material. It creates recommendations to replenish bulk material based on
these demands and considering any on-hand inventory for the item. Note that when
you issue the material to the floor stock location, it is no longer seen as available supply.
During the planning cycle, the need for bulk items according to the material plan rise
and fall based on the timing of issues from nettable subinventories to the expense
account.
Suggestion: Designate a general ledger expense account as Floor stock. Periodically
issue large quantities of bulk items to this account.
Shrinkage Rate
For a particular inventory item, you can define a shrinkage rate to describe expected
scrap or other loss. Using this factor, the planning process creates additional demand
for shrinkage requirements for the item to compensate for the loss and maintain supply.
For example, if you have a demand of 100 and a discrete job for 60, the planning process
would suggest a planned order for 40 to meet the net requirements, assuming no
shrinkage rate exists.
With a shrinkage rate of .2 (20%), Oracle MRP assumes you lose 20% of any current
discrete jobs and 20% of any suggested planned orders. In this example, since you have
a discrete job for 60, assume you lose 20% of that discrete job, or 60 times 20%, or 12
units. The net supply from the discrete job is 48. Since you have a total demand of 100
and supply of 48, you have a net requirement of 52 units. Instead of suggesting a
planned order for 52, the planning process has to consider that 20% of that planned
order is also lost to shrinkage.
The planning process creates additional demand called shrinkage demand to create an
increased suggested planned order to provide for the lost supply. The planning process
inflates the planned order of 52 by dividing 52 by (1 - .2) = 65.
inflated planner order = demand / (1 - shrinkage rate)
shrinkage demand = [demand / (1 - shrinkage rate)] x
shrinkage rate
With the a shrinkage rate of .2, the planning process would result in:
total demand = original demand +
discrete job shrinkage +

planned order shrinkage
125 = 100 + 12 + 13
total supply = discrete job + planned order

125 = 60 + 65
Component Yield
Component yield is the percentage of a component on a bill of material that survives
the manufacturing process. A yield factor of 0.90 indicates that only 90% of the usage
quantity of the component on the bill actually survives to be incorporated into the
finished assembly.
To account for the loss, the planning process inflates the demand quantities for the
component (similar in concept to shrink factor). To increase demand, the usage quantity
is divided by the yield factor.
For example, when you define the component usage quantity as 2 and the component
yield as 0.90, the usage is recalculated as 2 divided by 0.90, or 2.22.
new component usage = usage / yield factor
The difference between a shrink rate and component yield is that Oracle MRP applies
the same shrink rate to every use of an item on a bill, whereas you can vary the
component yield factor you assign to each occurrence of an item on a bill. Another
difference is that shrinkage demand is calculated at the parent assembly level and
passed down to components. Component yield is calculated at the component level.
Safety Stock
Safety stock is a quantity of stock you plan to remain in inventory to protect against
fluctuations in demand or supply. Safety stock is sometimes referred to as
overplanning, forecast, or a market hedge. In the context of master scheduling, safety
stock refers to additional inventory planned as protection against forecast errors or
short term changes in the backlog. You can specify safety stock days together with
safety stock percent as item attributes in Oracle Inventory.
You establish the default use of safety stock calculation when you define your planning
parameters. You can override this option for individual material plans when you
generate an MRP or MPS using the Launch window. See: Defining Planning Parameters
and Launching the Planning Process

When launching the planning process, you can choose whether to calculate safety stock
when generating suggested planned orders and repetitive schedules in the Plan Options
window. If you choose to run the planning process with the safety stock option, Oracle
MRP looks at each item to determine the method of safety stock calculation. You can
define safety stock methods for each item using in Oracle Inventory. See: Entering and
Reloading Item Safety Stocks, Oracle Inventory User's Guide.
MRP Planned Percent
If you choose a safety stock method of MRP planned percent for an item, safety stock is
dynamically calculated during the planning process.
For discretely manufactured items, the safety stock quantity is dynamically calculated
by multiplying the safety stock percentage you define by the average of gross
requirements for a period of time defined by the safety stock days.
For repetitively manufactured items, the planning process multiplies the percentage
you define by the average daily demand for a given repetitive planning period. The
planning process recalculates the safety stock quantity for each repetitive period in the
planning horizon.
Inventory Methods
Oracle Inventory provides several different methods for calculating safety stock. See:
Entering and Reloading Item Safety Stocks, Oracle Inventory User's Guide.
The following methods are available within Oracle Inventory for calculating safety
stock and are used during the planning process if your safety stock method is Non-MRP
planned:
Mean absolute Calculate safety stock as the mean absolute deviation (MAD) deviation
(MAD).
User-defined Calculate safety stock using the percentage you percentage define times
the average monthly demand.
User-defined Use a fixed safety stock quantity you define. quantity
Safety stock quantities generated in Oracle Inventory according to effectivity dates are
included in planning. Instead of manually changing the user-defined safety stock
quantity each time a change is needed, the user can now set effectivity dates for when a
change in quantity takes place.
Lot Expirations
For items under lot control, you can define the shelf life of lots that controls when the
lot expires. The planning process tracks lots and their expiration dates. If the expiration
date for a lot occurs before the lot is used to satisfy gross requirements, the unused
portion of the lot as expired is considered. An expired lot gross requirement is created
to offset any remaining portion of the expired inventory lot.
For example, the following item has a quantity on hand of 300 that consists of 3 lots of
100 each, due to expire on days 5, 10, and 15 respectively. The item has gross
requirements of 150 on day 4 and 50 on day 12. The plan would look as follows:
Lot Expiration MRP Plan
Beginning QOH =
300
Demand Type
Quantity
Projected QOH
Day 4
Gross requirement
150
150
Day 10
Lot expiration
50
100
Day 12
Gross requirement
50
50
Only 50 units from the second inventory lot were used before they were due to expire
on Day 10. Therefore, a gross requirement with a type of lot expiration to offset the
quantity of the inventory lot that is projected to expire is created.
See Also
Implementing Planned Orders
Phantoms, Oracle Bills of Material User's Guide
Creating a Bill of Material, Oracle Bills of Material User's Guide Defining Items, Oracle
Inventory User's Guide
Overview of Material Control, Oracle Work in Process User's Guide
Overview of Plan Control

You can reduce the nervousness of your material plan by using time fences, firm orders,
and other item attribute settings. These controls allow you to minimize the action
messages and reschedule recommendations that the planning process creates.
Acceptable Early Days Delivery
You can define a number of days that you allow orders to arrive before they are needed.
The Acceptable Early Days item attribute is defined in Oracle Inventory. Oracle MRP
does not generate a reschedule out recommendation if the number of days the order is
going to arrive early is less than the acceptable early days delivery. This allows you to
reduce the amount of rescheduling activity within a material plan. You can make a
business decision that it is acceptable to temporarily carry more inventory to reduce the
nervousness of the material plan.
For example, suppose you define 2 days as acceptable for early delivery, and the
current date of an order is Day 2. If the planning process determines that the actual due
date should be Day 3 or Day 4, the planning process does not suggest rescheduling of
the order. Oracle MRP suggests rescheduling only when the new need date is Day 5 or
later.
Note: Acceptable early days delivery only has an effect
On orders that are due to arrive earlier than they are needed. Oracle MRP always
generates a reschedule in message if an order is scheduled to arrive later than it is
required.
Although the planning process may suggest rescheduling some scheduled receipts and
may not suggest rescheduling others because of the acceptable early days limit, it does
not violate the order of the current scheduled receipts. In other words, if one scheduled
receipt is not rescheduled (because it falls within the acceptable early days delivery)
and the planning process wants to suggest rescheduling another scheduled receipt out
past the first scheduled receipt, Oracle MRP does not suggest rescheduling either.
For example, if the material plan for an item looks as follows:
Material Plan
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Gross Requirements
100
100
Scheduled Receipts
100
100
Discrete job A is due on Day 3 and discrete job B is due on Day 5.

If you have defined acceptable early days delivery to be zero, Oracle MRP recommends
that the discrete job B be rescheduled from Day 5 to Day 7, and that discrete job A be
rescheduled from Day 3 to Day 6.
If you have defined acceptable early days delivery to be 2 days, Oracle MRP does not
recommend either scheduled receipt to be rescheduled. Rescheduling the discrete job B
to Day 7 does not occur because Oracle MRP would only be recommending a
reschedule out message of 2 days, which is equal to the acceptable early days delivery.
In the previous example, Oracle MRP recommended that the discrete job A be
rescheduled to Day 6. In this case, however, Oracle MRP would only recommend
rescheduling discrete job A to Day 5 to preserve the original order of the scheduled
receipts. However, rescheduling from Day 3 to Day 5 is a reschedule out
recommendation of only 2 days, that equals the acceptable early days delivery.
Therefore, in this scenario, Oracle MRP would not recommend either job be
rescheduled.
See Also:
Time Fence Control

Time fence control is a policy or guideline you establish to note where various
restrictions or changes in operating procedures take place. For example, you can easily
change the master production schedule for an item beyond its cumulative lead time
with little effect on related material and capacity plans. However, changes inside the
cumulative lead time cause increasing difficulty, reaching a point where you should
resist such changes because of their effect on other plans. You can use time fences to
define these points of policy change. Oracle MRP offers three types of time fences:
planning time fence
demand time fence
release time fence
You can determine whether to consider the time fence when planning a material plan or
a master schedule if you select Yes for Demand or Planning Time Fence Control on the
Plan Options window, or (for the Release Time Fence) if you check Production on the
DRP, MPS or MRP Names window. If you are using either the planning, demand, or
release time fence, the planning process looks at the item attributes for each item in the
Master Item window to determine the selected time fence for each item. The three time
fences are calculated by adding one of the following to the plan date (or the next valid
workday, if the plan was run on an invalid workday): total lead time, cumulative
manufacturing lead time, cumulative total lead time or a user-defined time fence.
For discrete items, you can recommend that an order be rescheduled out or cancelled,
but cannot recommend reschedule in messages or create new planned orders within the
planning time fence for an item. For repetitive items, you can limit the changes Oracle
MRP can recommend within the planning time fence by the acceptable rate increase or
decrease.
The planning time fence does not apply to purchase requisitions or internal requisitions.
If you specify demand time fence control when launching the planning process, the
planning process only considers actual demand within the demand time fence specified
for an item (such as forecasted demand is not considered).
Release Time Fence

If you define a release time fence attribute for your item, and you specify release time
fence control when defining a DRP, MPS or MRP name, you can automatically release
planned orders as WIP jobs. Planned orders for purchased items are released as
purchase requisitions. The planned orders must meet the following auto-release criteria:
new order placement date within the auto-release time fence
must not have compressed lead time
must be for standard items (the planning process will not automatically release
models, option classes, and planning items)
the orders are not for Kanban items
DRP items in a DRP plan, MPS planned items in an MPS plan, or MRP planned
items in an MRP plan See: Implementing Planned Orders.
the release time fence option is defined as anything other than Do not auto-release,
Do not release (Kanban), or Null
Auto-release for WIP jobs is not applicable for repetitively planned items. No material
availability check is performed before WIP jobs are released.
See Also
Repetitive Planning
Time Fence Planning
MPS/MRP Planning Attribute Group, Oracle Inventory User's Guide
Auto-Release Planned Orders

Instead of implementing and releasing planned orders by hand, you can enable the
planning process to automatically release planned orders. During the planning run, all
qualifying planned orders that fall within the release time fence will be released. Unlike
manual release, you cannot modify order dates and quantities or the default
implementation details.
Prerequisites
Before the planning process can release planned orders automatically, you must:
Define an employee, associate a user name to the employee entry, and associate the
employee to the application user. See Entering a New Person: Oracle Human
Resources.
Define a planner or planning entity and associate this planner with items you want
controlled by the auto-release function. See Defining Planners and Defining Items:
Oracle Inventory User's Guide.
Supply Chain Planning users must define a material planner, supply chain planner
or planning entity for the current organization and assign them to inventory items
at the organization level. See: Updating Organization Items, Oracle Inventory User's
Guide and General Planning Attribute Group, Oracle Inventory User's Guide.
Define Default Job Status and Job Class values for a user on the Planner Workbench
Preferences window. These settings are in the Supply/Demand region and are used
as defaults in the process of automatically releasing planned orders.
In addition, the planned orders must meet the following auto-release criteria:
the new start date lies within the auto-release time fence
the lead time is not compressed
the orders are for standard items (will not release models, option classes, and
planning items)
the orders are for DRP planned items in a DRP plan, MPS planned items in an MPS
plan, or MRP planned items in an MRP plan See: .Implementing Planned Orders.
Auto-release of repetitive schedules is not applicable to repetitively planned items. No

material availability check is performed before WIP jobs are released.
To enable the auto-release function
1.
Navigate to the DRP, MPS, or MRP Names window.
2.
Enter an alphanumeric name that identifies a unique material requirements.
3.
implemented as discrete jobs, flow schedules, purchase orders, or purchase
requisitions.
This provides the planner visibility of the status of the plan at any point in time.
4.
Check Production to enable a plan to auto-release planned orders.
5.
Enter an inactive on date on which to disable the plan.

As of this date, you can no longer update the plan, nor use the plan name in the
planning process. You are still able to view information and run reports for
disabled names.
6.
Save your work.

See Also
Time Fence Control: Release Time Fence
Firm Order Planning

Oracle Manufacturing provides three types of firm orders:
Firm MRP Planned Order
A firm MRP planned order represents a planned replenishment that is "firmed" using
the Planner Workbench for MRP planned items. This allows the planner to stabilize
portions of the MRP without creating discrete jobs or purchase requisitions. Unlike a
firm scheduled receipt described below, a firm MRP planned order does not implicitly
create a time fence for an item unless you set the MRP:Firm Planned Order Time Fence
profile option to Yes.
Depending on the overwrite options you choose when launching MRP, you can either
allow the planning process to delete firm MRP planned orders, or restrict it from
making any recommendations against them.
Firm MRP Implemented Order
An order can be firmed during the load process into WIP when releasing implemented
planned orders via the Planner Workbench, or you can use forms provided by Oracle
Work in Process and Oracle Purchasing to firm discrete jobs and purchase orders
individually. An order is firmed so that the planner responsible for the item can take
manual control of the material replenishments. Once a firmed implemented order is
released, the planning process treats it as a firm scheduled receipt.
A firm status on a discrete job or purchase order automatically creates a time fence for
an item if it exists beyond the predefined planning time fence.
Firm Scheduled Receipt
A firm scheduled receipt represents a replenishment order that is not modified by the
planning process. It may be a purchase order or discrete job for a DRP (for Supply
Chain Planning users), MPS or MRP planned item. A firm scheduled receipt is not
subject to the overwrite options you choose when launching a plan. An order can be
firmed during the load process into WIP when releasing implemented planned orders
via the Planner Workbench, or you can use forms provided by Oracle Work in Process
and Oracle Purchasing to firm discrete jobs and purchase orders individually.
Note: If a job is released and firmed, and the component requirement is
past due - the due date of the order is moved to the plan date.
See Also
Time Fence Planning
Profile Options
Implementing Repetitive Schedules
Creating Firm Planned Orders
Creating Firm Implemented Orders
Rescheduling Scheduled Receipts
Overwrite Options
Overwrite When you launch the planning process, you generate new planned orders
and suggested repetitive schedules to meet your net requirements. Since you can firm a
DRP, MPS, or MRP planned order, you may not want the planning process to overwrite
any firm planned orders. You can use the Overwrite and Append plan level options to
limit how the planning process reacts to firm planned orders and to stabilize the short
term material plan.
When you enter All in the Overwrite field, the planning process overwrites all entries,
planned and firm planned, from the current material plan.
When you enter None in the Overwrite field, the planning process does not overwrite
any firm planned orders. It does, however, overwrite any suggested planned orders
that are not firm.
When you enter Outside planning time fence in the Overwrite field, the planning process
overwrites all entries from the current plan, planned and firm planned, outside the
planning time fence, and overwrites only planned orders inside the planning time
fence. It does not overwrite any firm planned orders within the planning time fence.
The planning time fence can be different for each item, so the planning process looks at
the planning time fence for each item when choosing what to delete.
Append Planned Orders
When you enter No in the Append Planned Orders field, the planning process does not
append any planned orders to the current plan. Additional demand does not cause
planned order recommendations. Instead, the projected quantity on hand may go
negative in response to demand that was not met by a suggested planned order.
When you enter Yes in the Append Planned Orders field, the planning process appends
additional planned orders after the last entry on the current material plan to meet any
additional demand.
The overwrite and append options work in combinations, as described below.
Overwrite All, Append Planned Orders
This option allows you to create a new material requirements plan for the plan name
you specify, deleting all previous planned and firm planned entries while regenerating
new planned orders. You can use this combination the first time you run your plan or if
you want your plan to reflect all sources of new demand.

For example, if an existing material plan has the following orders for an item:
MRP Plan
Schedule Date
Quantity
Order Status
01-FEB
100
Planned
08-FEB
200
MRP firm planned
15-FEB
300
Planned
And the following MDS is used to plan the material plan using All in the Overwrite
field and Yes in the Append Planned Orders field:
MDS Schedule
Schedule Date
Quantity
02-FEB
110
09-FEB
220
16-FEB
330
Resulting MRP Plan

Schedule Date
Quantity
Order Status
02-FEB
110
Planned
09-FEB
220
Planned
16-FEB
330
Planned
The planning process always suggests planned orders. You can change planned orders to
a firm status using the Items window in the Planner Workbench.
Overwrite Outside Planning Time Fence Append Planned Orders

This option allows you to create an extension to the material requirements plan for the
plan name you specify, deleting planned and firm planned orders outside the planning
time fence and deleting all planned entries inside the planning time fence for each item.
The planning process creates (appends) new planned orders after the planning time
fence date. In this case, since you are overwriting after the planning time fence, you are
also appending new planned orders after that date. You can use this combination to
stabilize the short-term plan and allow the long-term plan to react to new sources of
demand.
Note: If an item has no time fence specified and this option is chosen,
all planned and firm planned orders are overwritten.
For example, if an existing MRP has the following orders for an item:
MRP Plan
Schedule Date
Quantity
Order Status
01-FEB
100
Planned
08-FEB
200
MRP firm planned
15-FEB
300
Planned
And the following MDS is used to plan the MRP using Outside Planning Time Fence
in the Overwrite field and Yes in the Append Planned Orders field:
MDS Schedule
Schedule Date
Quantity
02-FEB
110
09-FEB
220
16-FEB
330
Then the resulting material plan would have the following suggestions for planned
orders, assuming the planning time fence is 05-FEB:
Resulting MRP Plan

Schedule Date
Quantity
Order Status
05-FEB
110
Planned
09-FEB
220
Planned
16-FEB
330
Planned
Since the entry on 01-FEB is not firmed, the MRP planning process overwrites this
entry. If it was firmed, the process would not overwrite the entry. The additional
demand from the MDS of 110 on 02-FEB was appended on the planning time fence date
of 05-FEB. The MRP firm planned order on 08-FEB was deleted because it falls outside
the planning time fence of 05-FEB.
The planning process always suggests planned orders. You can change planned orders to
a MRP firm status using the Items window in the Planner Workbench.
Overwrite None Append Planned Orders

When you choose not to overwrite an existing plan, the planning process does not
overwrite existing firm planned orders, but deletes any suggested planned orders. The
planning process then creates (appends) new planned orders after the planning time
fence date. This is analogous to firming sections of your short-term material
requirements plan. You can extend the plan horizon without altering existing firm
planned orders.
For example, if an existing MRP has the following suggested planned orders for an
item:
MRP Plan (
Schedule Date
Quantity
Order Status
01-FEB
100
Planned
08-FEB
200
MRP firm planned
15-FEB
300
Planned
And the following MDS is used to plan the MRP using None in the Overwrite field and
Yes in the Append Planned Orders field:
MDS Schedule
Schedule Date
Quantity
02-FEB
110
09-FEB
220
16-FEB
330
Resulting MRP Plan

Schedule Date
Quantity
Order Status
05-FEB
110
Planned
08-FEB
200
MRP firm planned
09-FEB
20
Planned
16-FEB
330
Planned
The firm order on 08-FEB remains on the MRP since the overwrite is None. However,
the planned entries are deleted. Although additional demand exists on the MDS, no
planned orders are suggested until the planning time fence (on 05-FEB). The MDS
demand of 110 on 02-FEB was satisfied by a new planned order for 110 on 05-FEB. The
demand for 220 on 09-FEB was partially met by the firm MRP planned order on 08-FEB.
Thus an additional planned order was suggested on 09-FEB for 20 to meet the MDS
demand of 220. A suggested planned order was created on 16-FEB for 330 to meet the
demand from the MDS on 16-FEB.
Overwrite None Do Not Append Planned Orders

In this case, the planning process does not overwrite existing firm planned entries, but
deletes any suggested planned orders. In addition, it does not append additional
demand to the end of the plan. Instead, it reports the instances where the material
requirements plan is out of balance with the master demand schedule, and allows you
to solve these problems by manipulating the plan manually. This gives maximum
control to the material planner. For example, if an existing material plan has the
following orders:
MRP Plan
Schedule Date
Quantity
Order Status
01-FEB
100
Planned
08-FEB
200
MRP firm planned
15-FEB
300
Planned
And the following MDS is used to plan the MRP using None in the Overwrite field and
No in the Append Planned Orders field:
MDS Schedule
Schedule Date
Quantity
02-FEB
110
09-FEB
220
16-FEB
330
The resulting MRP would suggestions for planned orders:

Resulting MRP Plan
Schedule Date
Quantity
Order Status
08-Feb
200
MRP firm Planned
The reason the additional demand from 02-FEB, 09-FEB, and 16-FEB was not planned
for is because with the Overwrite None and Do Not Append Planned Orders, you choose
not to overwrite firm planned orders nor create new planned orders to meet additional
demand. In this case, the projected quantity on hand would go negative since no
planned orders were suggested to meet the additional demand. The material planner
can use on-line inquiries and reports with exception messages to identify material
shortages.
Gross to Net Explosion

Gross to net explosion is the process that translates using assembly requirements into
component requirements, taking into account existing inventories and scheduled
receipts.
Component due dates are offset from the due date of the using assembly by the lead
time of the assembly. The gross to net explosion process determines, for each item, the
quantities and due dates of all components needed to satisfy its requirements.
See Also
Gross to Net Explosion Example
Locking Tables within a Snapshot
Time-Phasing Requirements
Gross to Net Explosion Example

In the following diagram, the suggested planned orders for the end assembly are offset
by the lead time, one period, and passed down to the component during the planning
process.
The planned order for the end assembly in period 2 becomes the gross requirements for
the component in period 1.
In period 1, the gross requirements (100) and the safety stock level (50) represent the
total demand. The scheduled receipts (110) and quantity on hand (20) represent the total
supply. The net requirements, total demand (150) minus total supply (130), equals 20.
The planning process suggests a planned order in period 1 of 20 to meet the net
requirements.
There is no recommendation for safety stock in each period unless the demand in that
period is driven less than the safety stock level.
Note: Planned orders in period 4 are not suggested since the projected
on hand is at the safety stock level.
See Also
Overview of Gross to Net Explosion

You calculate material requirements by launching the planning process from the
Launch Planning Process window. The phases of the planning process that calculate
material requirements are the:
maintain repetitive planning periods phase
snapshot phase
planner phase
auto-release
Maintain Repetitive Planning Periods Phase

When you specify a new anchor date, the maintain repetitive planning periods phase
uses that date as its new starting point for calculating repetitive planning periods.
Snapshot Phase
The snapshot phase:
determines the component usages of the assemblies included in the planning

process, beginning at the top level of the assemblies and working down through the
product structure
calculates low-level codes and checks for loops in your bill of material structures
collects inventory on-hand quantities and scheduled receipts
stores this information for further use
captures sourcing rules, bills of distribution, and master demand schedules for
supply chain planning
captures resource information that is used for capacity planning
Planner Phase
The planner phase:
performs the gross-to-net explosion, calculating net requirements from gross
requirements, using on-hand inventory and scheduled receipts, exploding the
requirements down through the bill of material
suggests the rescheduling of existing orders and the planning of new orders based on
the net requirements
calculates the resource requirements for supply orders Note: This step is performed if
Capacity Plan is enabled.
Auto-Release Phase
The auto-release phase:
releases planned orders for items whose order date falls within their release time fence
Note: This step is performed for plans that have the Production flag
enabled. The recommendations generated by the planning process feed

the capacity requirements planning, shop floor control, and purchasing
activities of the organization.
See Also
Planner
Snapshot
Locking Tables within the Snapshot
Locking Tables within the Snapshot Example
Overview of Supply Chain Planning
Overview of Capacity Planning, Oracle Capacity User's Guide

The snapshot takes a copy, or "snapshot", of all the information used by the planning
process so that the planning process can operate on a picture of the data frozen at a
point in time, and report against that "snapshot" at any future time.
You can choose to lock tables during the snapshot process to guarantee consistent data.
Locking tables controls the degree of read consistency. With unlocked tables, you can
still get a high level of data consistency. However, if you feel you must lock tables,
tables lock for only a brief period, reducing inconvenience to users.
See Also

Consider a situation where you have a subinventory with a quantity of 100 units, and a
discrete job for 25 units.
Between the time the snapshot reads the inventory information and the time the
snapshot reads the discrete job information, 10 units are completed from the job. If you
ran the snapshot and choose to lock tables, you would guarantee that the snapshot
would read either 100 units in the subinventory and 25 units outstanding on the
discrete job, or 110 units in the subinventory and 15 units outstanding on the discrete
job.
If you ran the snapshot and selected not to lock tables, there is a chance the Snapshot
would read 100 units in the subinventory and 15 units outstanding on the discrete job.
The chances of inconsistencies caused by launching the snapshot without locked tables
is remote. The results you get from locked tables are better than those you get from the
unlocked tables. However, you can still choose to run the Planning Engine with
unlocked tables.
See Also
Time-Phasing Requirements
The planning process time-phases material requirements and expresses future demand,
supply, and inventories by time period. Time-phasing delays release of orders for
components until they are needed and offsets the requirements by item lead time (lead
time offset). Oracle MRP plans to the exact date of demand, although some reports and
inquiries show requirements bucketed by weeks or months.
If you execute the planning process on a non-valid workday, the planning process
considers the next valid workday as the day the plan is generated.
For example, if you execute the planning process on a Saturday, the planning process
would generate planned orders at the earliest for the following Monday.
Past Due Supply and Demand
The planning process considers past due supply and demand as if it were due today (in
other words, the start date of the plan). Reports and on-line inquiries that bucket
demand in weeks or periods show past due demand in the first bucket.
Material Scheduling Method
The material scheduling method controls how the planning process calculates the exact
date of demand: the start date of the operation generating the demand, or the start date
of the order generating the demand.
For each material requirement, the planning process schedules material to arrive in
inventory on the day that corresponds to the method you choose. This affects
time-phasing of requirements for discrete jobs, flow schedules, repetitive schedules and
planned orders. See: Material Scheduling Method Example.
Lead Time Percent
Lead time percent is used when you choose a material scheduling method of Operation
start date when launching the planning process.
For a particular operation, the lead time percent is the percent of total lead time from
the start of the first operation on the routing to the start of the current operation.
For example, if the lead time of the assembly equals 10 days and this operation starts
after 2 days (on day 3) the lead time percent is 20%.
Oracle Bills of Material calculates lead time percent values when you calculate
manufacturing lead times.
Oracle MRP uses the lead time percent to schedule material requirements at a
particular operation.
Oracle Capacity uses the lead time percentage to plan capacity requirements at a
particular operation.
Manufacturing Lead Time Calculation

You calculate the processing lead times for assemblies in Oracle Bills of Material. For a
particular assembly, the processing lead time is the sum of the operation lead times for
the standard routing of the assembly. See: Calculating Manufacturing Lead Times,
Oracle Bills of Material User's Guide.
Dynamic Lead Time Calculations
Oracle Bills of Material calculates fixed and variable portions of lead time for your
manufactured items. You can use dynamic lead times to accurately compute start dates
for planned orders generated by Oracle MRP. Dynamic lead times are more accurate
than fixed lead times because lead time can vary based on order quantity.
Lead time for planned orders is computed as:
planned order lead time = fixed lead time + (order quantity x variable leadtime)
See Also
Launch Planning Process
Item Lead Time Attributes, Oracle Bills of Material User's Guide Manufacturing Lead
Time Computation, Oracle Bills of Material User's Guide
Overview of Lead Time Management, Oracle Bills of Material User's Guide Dynamic
Lead Time Offsetting, Oracle Bills of Material User's Guide
Specifying Items for the Planning Process

You can set the following parameters in the Plan Options window:
All planned items
Demand schedule items only
Supply schedule items only
Demand and supply schedule items only
See: Specifying Items for the Supply Chain Planning Process

To specify items that are included in the planning process
1.
2.
Select one of the following options from the Planned Items poplist:
All planned items Demand schedule items only
Suggestion: It is recommended that you use the All planned items option, to avoid
missing items you want to plan and to guarantee that all sources of demand are
considered by the planning process. Under certain circumstances, including
demand schedule item components or supply schedule item components only may
mean that not all demand for an item appears in the material plan. For items you do
not want to plan, assign an MRP Planning Method item attribute of Not planned
when you define an item in Oracle Inventory.
3.
Save your work.

See Also
Material Scheduling Method Example

You are manufacturing a computer that has a lead time of five days. The last operation
step in assembling the computer is to attach the label on the case of the computer. The
label is not actually required until the fourth day of the assembly process.
If the planning process recommends a planned order for 10 computers to be completed
on day 5, and you choose the material scheduling method to be Operation start date, the
planning process schedules the component requirements for the label to be required on
day 4.
If you choose a material scheduling method to be Order start date, the planning process
schedules the component requirements for the label to be required on day 1 (i.e. the
start date of the order).
Suggestion: You might choose scheduling to Order start date so that all the components
are issued at the start of the job. This can save time and paperwork, especially for items
with short lead times. You might choose scheduling to Operation start date if your lead
times are long or have expensive inventory carrying costs for your components. This
method plans the demand for the component based on the start date of the operation
where it is required. You can set this method for all material plans in the Define
Planning Parameters window, and override your choice for individual material plans.
See Also
Netting Supply and Demand

The netting parameters allow you to control the different sources of visible supply and
demand when calculating net requirements. You can optionally choose to net WIP,
Purchases, Reservations and Subinventories when launching the planning process.
Supply Chain Planning users can net subinventories for multiple organizations. See:
Netting Supply and Demand for Multiple Organizations
To net Purchases, WIP, and Reservations:
1.
2.
Check Net Purchases, Net WIP, and Net Reservations to net supply and demand for
these items.
3.
Save your work.

You can also override these default options for individual plans, from the Plan
Options window, when you generate a plan.
To net Subinventories
1.
Navigate to the Subinventory Netting window from the Plan Options window.
2.
Check Net to indicate that you want to net supply and demand for these
subinventories.
Note: You assign a netting type when you define a subinventory in
Oracle Inventory. The planning process considers the inventory in

a nettable subinventory as supply. You can override the netting
type for a specific subinventory when you launch the planning
process.
3.
Save your work.

See Also
Net Purchases
Net Work in Process
Net Reservations
Net Purchases
When you choose to net purchases, the planning process considers approved purchase
requisitions and approved purchase orders as scheduled receipts (supply). If you do not
choose to net purchases, the planning process ignores this purchasing information.
Note: This option may be useful when performing simulations to see
the impact on the material plan if scheduled purchase receipts are not
available as supply.
The planning process ignores unapproved purchase requisitions, but plans using
approved requisitions and both approved and unapproved purchase orders as valid
scheduled receipts.
Note: The planning process only nets purchase requisitions and
purchase orders that have a purchasing location that is associated to the

inventory organization launching the MPS, MRP, or DRP
Planning Dates
Oracle Purchasing requires a promised-by date or need-by date on a purchase order for
planned items. If only one of these dates is defined, the planning process considers the
date specified (either the promised-by date or need-by date) to be the dock date for the
purchase order. If you have defined both dates on the purchase order, the planning
process considers the promised-by date to be the dock date when calculating order
dates.
Purchase requisitions and purchase orders are planned based on several key dates:
Promised-by DateOn a purchase order, this is the date the supplier promises to deliver.
Need-by date:On a purchase requisition and purchase order, this is the internal date of
need.
Dock date vs.order due date: If the promised-by date exists, the planning process
designates it as the dock date (the date you expect the order to arrive on the receiving
dock). Otherwise, the need-by date is the dock date. To the dock date, the planning
process adds post-processing lead time to arrive at the order planning date: the date
that the planning process plans the supply as available for use.
Receiving Inspection Inventory

The planning process considers receiving inspection inventory by calculating a planned
receipt date. The post-processing lead time for the item is added to the dock date to
determine the planned receipt date. The purchase order quantity in receiving is
considered as available supply on this calculated date.
Internal Requisitions
The planning process plans internally sourced requisitions in the same manner as it
plans externally sourced requisitions. Oracle MRP recommends that you set up a
separate Planner Code and associate it to your internally sourced items. This lets you
manage your planned internal requisitions by requesting key reports and windows
using the Planner Code associated to your internally sourced items.
See Also
Site Locations, Oracle Human Resource Management Systems User's Guide
Overview of Internal Requisitions, Oracle Purchasing User's Guide
Net Work in Process
Net Reservations
Net Work in Process

When you choose to net WIP, the planning process considers work in process standard
and non-standard discrete job, flow schedules, and repetitive schedules as scheduled
receipts (supply).
If you do not choose to net WIP, the planning process ignores work in process standard
and non-standard discrete jobs, flow schedules, and repetitive schedules, regardless of
MRP netting information defined on these entities. The calculation of WIP supply and
demand is affected by several attributes defined on the discrete job.
Standard Discrete Jobs

Assembly supplies and component demands from standard discrete jobs with the
following statuses are included:
Unreleased
Released
Complete
On hold
Note: If a job is released and firmed, and the component requirement is
past due - the due date of the order is moved to the plan date.
Non-Standard Discrete Jobs

A non-standard discrete job controls material and collects costs for miscellaneous
manufacturing activities.
For example, these manufacturing activities may include activities with no defined
standards, such as items without a bill of material and routing. These miscellaneous
activities can include rework, field service repair, engineering projects, and tool or
machine creation/maintenance.
Oracle MRP does not net the material requirements of Complex Maintenance Repair
and Overhaul work orders.
Repetitive Schedules
Since Oracle MRP uses different planning algorithms for repetitive manufacturing,
repetitive schedule statuses do not impact how repetitive schedule supplies and
demands are viewed.
MRP Net Quantity
MRP Net Component
Assembly supplies and component demands from non-standard discrete jobs with
the following statuses are included:
Unreleased
Released
Complete
Hold
Since a non-standard discrete job is created manually and does not explode a bill of
material, it does not automatically create material requirements. However, you can
manually create material requirements with the WIP Material Transactions window.
Oracle MRP recognizes only these requirements.
Note: The planning process does not recommend rescheduling of
existing non-standard jobs.
In Oracle Work in Process, you can specify an MRP net quantity for the standard and
non-standard discrete jobs. The net quantity may differ from the job quantity for many
reasons.
For example, you would set the net quantity to zero if you receive the discrete job
quantity into a non-nettable completion subinventory.
When you choose to net WIP, the planning process uses the MRP net quantity on the
order header to calculate available supply. See: Defining Discrete Jobs Manually, Oracle
Work in Process User's Guide.
At the component level, you can enter a value for the MRP Net field to establish if the
planning process should net the requirement when calculating component demand.
You may choose to enter No for a particular component if it is issued from a
non-nettable subinventory.
When you choose to net WIP, the planning process uses the MRP net value at the
component level to determine if the component requirement is included as demand.
Supplier Components
Negative Requirements
If you specify a WIP supply type of supplier for an item or component, the planning
process ignores the requirement.
You can define negative usages for component items on a bill of material in Oracle Bills
of Material. You can add negative requirements (byproducts) to discrete jobs using
Oracle Work in Process. See: By-Product Recovery, Oracle Work in Process User's Guide.
Oracle MRP includes negative requirements on standard and non-standard discrete jobs
and components with a negative usage on a bill of material when netting supply and
demand. This type of component requirement is considered as supply available on the
job completion date. The MRP Net field on the Discrete Jobs window, in Oracle Work in
Process, must have a value in order for negative requirements to be treated as supply.
Note: You can manually add a negative requirement to a non-standard
job in Oracle Work in Process to manage components that result in

disassembly. You could use this option for repairing assembly units. It
allows you to track the item that is issued to the job as available supply
on completion of the repair job. See: Component Issues and Returns,
Oracle Work in Process User's Guide and WIP Material Transaction
Types, Oracle Work in Process User's Guide.
Byproduct planning information is included in the following reports:
Current Projected On Hand vs. Projected Available Report
Demand vs. Replenishment Graphical Report
Planning Detail Report
See Also
Discrete Job Statuses, Oracle Work in Process User's Guide
Repetitive Schedule Statuses, Oracle Work in Process User's Guide
Net Purchase
Net Reservations
Net Reservations
When you choose to net reservations, the planning process recognizes hard reservations
that represent sales order demand. If you do not choose to net reservations, the
planning process recognizes all sales order demand as soft reservations only. The
planning process always plans to satisfy hard reservations before soft reservations.
Note: By definition, sales order demand is a soft reservation. A hard
reservation is sales order demand that you firm by reserving selected

inventory for the purposes of material planning, available to promise
calculations and customer service issues
See Also
Viewing Item Reservations, Oracle Inventory User's Guide Net Purchases
Net Work in Process
Overview of Engineering Change Planning

Engineering change planning involves planned modifications of bills of material. These
planned changes affect the demand calculated and the orders rescheduled or created by
the planning process.
Engineering Change Orders

Oracle MRP evaluates the engineering change orders as of their scheduled effective
date. You can order material and plan resources that you need for new revisions ahead
of time.
Note: The planning process only suggests implementing engineering
change orders when the start date of the planned order is later than the
effective date. Oracle MRP does not suggest a planned order using an
ECO if the planned order needs to start before the effective date of the
ECO.
For a pending ECO, you can specify whether to include the engineering changes during
the planning process. Set the MRP Active Flag to Yes in the Engineering Change Order
window if you want the planning process to consider the engineering changes on the
ECO.
Oracle MRP considers engineering changes when generating component requirements
for planned orders and suggested repetitive schedules. The quantity specified by an
engineering change order is considered if the scheduled effective date of the ECO is
before the suggested start date of the order.
For example, if you have defined the following bill of material:
Assembly A has a lead time of 2 days. Component B has a usage of 2. You defined an
engineering change order that changes the usage of B to 3. The ECO has a scheduled
effective date of Day 4. If the material plan for Assembly A is:
Material Plan for Assembly A
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Gross Requirements
100
100
100
100
Planned Orders
100
100
100
100
The planned orders for Assembly A with due dates of Day 4 and Day 5 have start days
of Day 2 and Day 3 respectively when offset by the lead time of 2 days. Since neither
planned order has a start date that is on or after the scheduled effective date of the
engineering change order, the component requirements are generated based on the
current bill of material that specifies a usage of 2 Bs.
The planned orders for Assembly A with due dates of Day 6 and Day 7 have start dates
of Day 4 and Day 5 respectively when offset by the lead time of 2 days. Since both
planned orders have a start date that is on or after the scheduled effective date of the
engineering change order, the component requirements are generated based on the
revised usage of 3 Bs.
The material plan for component B is:
Material Plan for Component B

Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Gross Requirements
200
200
300
300
Planned Orders
200
200
300
300
See Also
Defining Engineering Change Orders, Oracle Engineering User's Guide
Use-Up Date
The use-up date determines when the current on-hand quantity for an item is exhausted
based on projected gross requirements. This date is calculated for all items during the
planning process. The use-up date is calculated by applying on-hand quantity in
inventory (supply) against any gross requirements (demand), and adding the next work
date to the day it is depleted. The planning process does not consider repetitive
schedules as supply when calculating the use-up date. It does consider schedule
receipts if the profile option, MRP:Include Scheduled Receipts in Use-up Calculation, is
set to yes.
For example, if the material plan for an item is as follows:
Material Plan for Item
Beginning QOH = 600
Day 2
Day 3
Day 4
Day 5
Day 6
Gross Requirements
200
200
300
300
Oracle MRP calculates, based on the projected gross requirements for this item, that the
current quantity on hand is exhausted on Day 4. Therefore, the planning process sets
the use-up date for this item to be Day 5.
When you define a revised item for an ECO, you can specify whether the planning
process should recommend a suggested effective date for the revised item. If you
indicate that the planning process should calculate the suggested effective date, you
also specify a use-up item. Oracle MRP recommends a suggested effective date based
on the use-up date of the use-up item.
For example, you may want to change how you build an assembly. You manufacture a
board, that has Chip A as a component:
You have decided to change the Assembly Board to use a new and improved Chip B
instead of Chip A.
You define an ECO with the Board assembly as the revised item. You specify Chip A as
a revised component with a usage quantity of 0, and Chip B as a revised component
with a usage quantity of 1. You'd like to use up the Chip A's you have in stock before
beginning to use the Chip B's. Therefore, you would define the ECO as use-up and set
the use-up item to be Chip A. Oracle MRP suggests an effective date based on the
use-up date of Chip A.
Note: While Oracle MRP calculates the use-up date as the basis for
suggesting an effective date for the ECO, the planning process uses the
current effective date instead of the suggested effective date when
generating component requirements. The only case where Oracle MRP
considers the suggested effective date of the ECO when generating
component demand is when the use-up item is the assembly (in our
example, the Board assembly) instead of one of the components.
See Also
Defining Engineering Change Orders, Oracle Engineering User's Guide

Bill of Material Changes
In addition to engineering change orders, you can also make manual modifications to a
bill directly, using the Bill of Material window. Oracle MRP plans for component items
as of their effective date for a given revision.
Oracle MRP plans bill of material changes and ECS's similarly. The planning process
creates planned orders that incorporate all bill of material changes that are effective as
of the start date of the planned order. See: Creating a Bill of Material, Oracle Bills of
Engineering Items
An engineering item is primarily used for prototypes and research. Oracle MRP plans
engineering items exactly as it does manufacturing items. All engineering components
are planned for accordingly and are visible on inquiries and reports.
Note: You must set up all appropriate planning attributes when you
define an item. See: Defining Items, Oracle Inventory User's Guide.
5
Overview
Oracle Supply Chain Planning is a powerful tool that integrates manufacturing and
distribution into a single planning process. With Oracle Supply Chain Planning, you
can generate plans that include the entire supply chain. In a single step you can
schedule and plan material and distribution requirements for multiple organizations, or
centrally plan the entire enterprise. You can also include customer and supplier
inventories in the supply chain planning process.
Oracle Supply Chain Planning lets you plan finished products, as well as intermediate
assemblies and purchased items, for all facilities in your supply chain. Material plans
for feeder plants and distribution centers automatically consider requirements
originating from any number of other facilities. You can load planned order demand
from multiple using-organizations into the master schedule of supplying organizations.
In addition to planning the material requirements of your supply chain, you can plan
the requirements for your distribution network. This includes all warehouses,
distribution centers, and any location that ships products. You can use these
distribution requirements plans (DRPs) as input for your material plans.
You can combine centralized distribution and material planning, for items with
significant interorganization supply or demand, with decentralized planning, where
you prefer autonomous, local planning. Output from the central plan can go into plant
level material plans and vice versa.
Oracle Supply Chain Planning gives you a transparent view of the virtual enterprise,
where all inventory locations participate in the planning process.
Note: All help on Supply Chain Planning assumes a knowledge of MRP
and will refer users to MRP topics when they compliment Supply
Chain functionality
Main Features of Oracle Supply Chain Planning
Supply Chain Planning 5-1
With Oracle Supply Chain Planning, you can:
Configure your supply chain
Determine a sourcing strategy for your supply chain
Apply the sourcing strategy to all your items
Use a graphical pegging display to directly identify the end customer orders
affected by shortages of items at any level in the supply chain
Consolidate demand statements across many organizations
Consider supply and demand from customer and supplier inventories in plans
Use supply statements from many organizations in your overall supply chain
Simultaneously plan for the material requirements of multiple organizations in

your supply chain
View exception messages for a consolidated supply chain material plan See:
Reviewing Planning Exceptions
Simulate and replan changes (e.g., quantity and date) to supply and demand
records See: Replanning Net Changes
Review updated exception messages to verify that your simulated changes resolve
supply or demand problems
Use a graphical display to visualize your supply chain
Analyze supply and demand records across multiple organizations in the Supply
Chain Planner Workbench
Receive support to create internal requisitions
See Also
The Multiple Organization Model
Setting Up and Implementing Sourcing Strategies
Master Scheduling in Supply Chain Planning
Material and Distribution Requirements Planning
Supply Chain Planner Workbench
The Multiple Organization Model

Large manufacturing and distribution enterprises, often made of a complex and
interdependent network of separate inventory locations and business entities, require
flexible, modular, and easily maintained plans. By consolidating enterprise-wide
planning activity into a single process, Oracle Supply Chain Planning automates much
of the implementation and control of material policies, reducing the need for
labor-intensive monitoring and manual control of the planning process.
In Oracle MRP, the planning process satisfies requirements for multiple inventory
locations, but within a single network. For example, demand is passed down from Org
1 (SAC) to Org 2 (AUS) and a Org 3 (SFO), and the supply is replenished in the opposite
direction.
The disadvantage is that this model requires at least two planning runs, as each
organization plans its own specific requirements. It also requires significant human
intervention to ensure that information generated by one organization is passed to the
other. If, for instance, SAC wanted to replenish its workstations from an additional
organization (NYC), SAC would have to maintain a separate set of plans, and manually
coordinate the supply coming from both.
Oracle Supply Chain Planning makes it possible to support a much more diverse and
flexible enterprise. Demand for an item may be met through one or more networks of
replenishment organizations. These organizations may be geographically remote,
clustered into interdependent groups, but remain semiautonomous within the
enterprise; they may also be members of a supplier's or customer's enterprise.
In the supply chain model, SAC produces final assemblies, which it distributes through
SFD and NYD. SAC is replenished by AUS, which supplies one purchased component
and one assembled component.
The advantage is that all this planning occurs with a single planning run, with
attendant gains in runtime and consistency. Requirements of different organizations are
planned transparently and seamlessly. You no longer need to load interorg planned
orders separately. The enterprise-wide distribution requirements have been
incorporated into the planning process. Sourcing strategies, formerly controlled
manually by a planner implementing planned orders, can now be automatically
assigned to the correct source, whether that is an internal organization or a supplier.
Oracle Supply Chain Planning also allows you to expand your planning capability as
your enterprise expands. SAC can easily incorporate NYC and Supplier 3 into the
global plan.
See Also
Supply Chain Supply and Demand Schedules
Managing Supply and Demand
Sourcing and Replenishment Network
Supply Chain Supply and Demand Schedules

Oracle Supply Chain Planning employs an advanced planning logic to enable you to
systematically and simultaneously generate distribution and material requirements
plans across the supply chain in a single planning run. Oracle Supply Chain Planning
can also support regional, decentralized planning activity. Owning organizations may
be responsible for certain links in the supply chain.
For each organization controlled by the plan, the planning engine loads firm
planned orders, supply and demand schedules, and sourcing information. Planned
order demand from one organization automatically and immediately appears in the
schedules of the supplying organization. The controlling plan can combine the
demand from multiple organizations, make rescheduling recommendations, and
generate exception messages on their behalf.
The netting process nets supply and demand for all items in your schedules, for all
organizations in your plan. In addition to creating and rescheduling planned
orders, the netting process assigns sources to the planned orders and generates
dependent demand. You can assign multiple sources to an item or category of
items, with split percentages, and these assignments can be phased in and out over
time.
DRP plans include intransit lead times when creating timephased demand and
create the corresponding demand in the shipping organization.
Demand Schedules
Demand schedules in Supply Chain Planning includes the master demand schedules,
and by extension all valid sources of demand. See: Master Schedule Typesfor a list of
valid sources.
Supply Schedules
Supply schedules can include MPS/MRP/DRP plans. If you include one of these supply
schedules in your supply chain plan, firm planned orders (along with orders for their
components) from the supply schedule will be treated as supply in the plan. Material
plans generated by the controlling organization can produce net requirements for all
organizations controlled by the plan. Distribution plans include distribution
requirements for all included items across multiple organizations. Included items can
be DRP planned, DRP/MPS planned, or DRP/MRP planned.
See Also

In the multiple organization environment, the Planner Workbench combines supply
and demand information on all items in all organizations across the planning horizon.
With Graphical Pegging, you can quickly trace component demand back to its source
item or order, or you can follow supply from the end item down to the lowest level.
With the Planner Workbench, you can simulate changes in the current plan, checking
the possible effects (across the entire enterprise) of firming planned orders, canceling
orders, changing dates, and adding new demand.
Note: The supply chain planning process does not recognize firmed
planned orders in a net change simulation under the following

conditions.
The planned order was not firmed in the organization that generated
the supply chain plan.
The planned order was firmed after last planning run See: Overview of
Net Change Replan for more information.
See Also
Supplier Planned Inventories
With supplier planned inventories you can integrate external supplier and customer
inventory information with that of manufacturing and distribution organizations. Such
information gives you an overall picture of the supply chain, including advanced
warning of stock outs, abnormal swings in demand, and capacity problems.
Once you model customers and suppliers as organizations, all relevant supply/demand
information for an item can be exchanged between your enterprise and supplier or
customer organizations. You can also net supply and demand of external organizations,
covert material needs of consuming organizations into demand at the replenishing
organization, and maintain capacity information (for the supplier organization).
Prerequisites
To model customers as organizations
1.
Define a customer name. See: Entering Customers, Oracle Receivables User's Guide.
2.
Use your customer name to define an organization. See: Creating an Organization,

Oracle Human Resource Management Systems User's Guide.
3.
Associate an inventory organization with a customer. See: Creating an

Organization, Oracle Human Resource Management Systems User's Guide.
To model suppliers as organizations

1.
Define a supplier name. See: Entering Suppliers, Oracle Payables User's Guide.
2.
Use your supplier name to define an organization. See: Creating an Organization,

3.
Associate an inventory organization with a supplier. See: Creating an Organization,

Note: You cannot implement planned orders in customer or supplier
organizations
See Also
Defining Sourcing Rules
Assigning Sourcing Rules and Bills of Distribution

You can define the rules that govern the movement of goods throughout your supply
chain. This network is the backbone of your material flow, but you can further control
its behavior by defining a time-phased replenishment strategy. Oracle Supply Chain
Planning does this with sourcing rules and bills of distribution. Sourcing rules and bills
of distribution both describe sourcing supply; i.e., for any organization, they answer the
question "where do I get part A from?". (They never say "where do I send part A to".)
Sourcing rules apply the answer to one organization or all the organizations in your
enterprise. Bills of distribution define this behavior across multiple organizations (not
just one or all).
See Also

A sourcing strategy allows a supply chain planner to gather all possible replenishment
scenarios and apply them globally, or to any item, category of items, or organization.
This allows the enterprise, or an individual organization, to adopt the most efficient
method of fulfilling net requirements.
Oracle Supply Chain Planning minimizes the effort required to set up, implement, and
maintain this strategy with sourcing rules and bills of distribution.
Setting Up the Supply Chain

Sourcing rules and bills of distribution determine the movement of materials
throughout your supply chain; these include items that you buy from your suppliers
and make at your manufacturing organizations.
Sourcing rules and bills of distribution both specify date-effective sourcing strategies,
combining replenishment sources with split allocation percentages and rankings. A
replenishment source is:
An inter-organization transfer (Transfer From)
The replenished organization manufactures the item (Make At)
An external supplier (Buy From)
An organization repairs the item (Repair at)
Sourcing rules and BODs both describe sourcing supply; in other words, for any
organization, they answer the question Where do I get part A? (They never ask Where
do I send part A?) Sourcing rules apply the answer to one organization or all the
organizations in your enterprise. BODs define this behavior across multiple
organizations (not just one or all).

In a sourcing rule, time-phasing applies only to the shipping organizations; the
receiving organization remains static for the life of the sourcing rule. In a bill of
distribution, time-phasing applies both to shipping and receiving organizations.
For each item in a rule or bill, you can define effectivity dates to switch sourcing
between make and buy, and set intransit lead times. If an item does not appear in a rule
or bill, the item attribute determines the status; when these attributes conflict with a
sourcing rule or bill of distribution, the rule or bill takes precedence. (See: Item and Bill
of Material Attributes, and Defining Items, Oracle Inventory User's Guide.)
The following features are provided in Oracle Supply Chain Planning sourcing logic:
Alternate source search if allocation exceeds supplier capacity
Control over Make/Buy attributes
Delivery frequency calendars
Historical information used in allocations
Ranking sources and defining allocation percentages
Splitting demand according to sourcing percentages
Supplier capacity constraints
Supplier specific lead times
Supplier specific order modifiers
Tolerance fences
Sourcing Rules
Sourcing rules define inventory replenishment methods for either a single organization
or all organizations in your enterprise. Time-phasing in a sourcing rule determines
when each group of shipping method - ship org combinations is in effect, as in this
example:
In the first phase of SR-C01, SAC is replenished equally by AUS and NYC. From
01-JUL-1997, AUS no longer supplies SAC, which receives all transfers from NYC:
(mrp_suprulex.if)
This sourcing rule can apply to one org (SAC, in this example), or to all your
organizations. However, you cannot choose a single organization in one phase and all
organizations in another phase. That would require two sourcing rules, with
consecutive effectivity dates. If you assign the sourcing rule to one receiving
organization (SAC in this example), it is a local sourcing rule; if you assign it to multiple
organizations, it is a global sourcing rule.
You cannot apply sourcing rules and bills of distribution (make them Planning Active)
until the sum of the allocation percentages equals 100. Secondly, sourcing rules and bills
of distribution do not take effect until they are assigned to a part or a range of parts.
(See: Assigning Sourcing Rules and Bills of Distribution.)
Bills of Distribution
Bills of distribution define the sourcing strategies of several organizations. In other
words, a bill of distribution is library of sourcing strategies. For instance, the sourcing
strategy described in SRC01 could apply to different organizations at different periods.
You cannot do this with sourcing rules because you have to apply the strategy to one
organization or all organizations.
In another example, an item is made in a manufacturing center and supplied to a
distribution center, which in turn supplies three sales offices. Instead of using five
different local sourcing rules, you could set up a three-level replenishment hierarchy
with a bill of distribution for the item. This bill would specify how the item is sourced at
each level.
Both sourcing rules and bills of distribution have effective dates, periods during which
the scheme is valid. For each period, you can specify a list of sources, type, allocation
percentage, rank, shipping method, and intransit time.
You cannot apply sourcing rules and bills of distribution (make them Planning Active)
until the sum of the allocation percentages equals 100. Secondly, sourcing rules and bills
of distribution do not take effect until they are assigned to a part or a range of parts.
(See: Assigning Sourcing Rules and Bills of Distribution.)
Example - Sourcing Rule/Bills of Distribution
In the following scenario, distribution centers SFD and NYD receive finished goods
from manufacturing plan SAC:
Sourcing rule SR-C02 describes the replenishment of SFD by SAC. Since no other plants
supply the part (which is assigned to this rule separately), the allocation is 100%.
SR-C02 is a local sourcing rule because it applies to SFD only. Similarly, SR-C03
describes the replenishment of NYD by SAC.
The bill of distribution (BRE01 in this example) can define a specific set of receiving
organizations, and for each organization it can define any number of shipping
organizations - each with its own allocation percentage, ranking, and shipping method.
Bills of distribution are more flexible than sourcing rules because, for each organization
you list in the bill, you define a range of dates and a sourcing strategy to apply within
those dates. Sourcing rules can only define the dates and strategy for one organization
or all the organizations in your enterprise.
The following scenario illustrates this flexibility:
As the demand from NYD expands and exceeds SAC's capacity to meet the demand,
the enterprise decides to build a new plant, called NYC. While NYC is brought online,
SAC continues to meet 100% of demand from NYD. From 1-JUL, however, NYC begins
to supply a small percentage of this demand, taking some of the burden away from
SAC. The planning process can quickly and easily support this transition. Sourcing rule
SR-C04 can define the dates during which the transition will occur, include NYC, and
split the demand replenishment between it and SAC. Bill of distribution BR-E01 can
accomplish this as well, but the bill can incorporate it into an enterprisewide sourcing
strategy.

You can define sourcing rules that specify how to replenish items in an organization,
such as purchased items in plants. Sourcing rules can also specify how to replenish all
organizations, as when the entire enterprise gets a subassembly from a particular
organization.
If there are conflicts in Sourcing, a predetermined hierarchy will resolve the sourcing
conflict. For instance, if you assign a bill of distribution to an organization AUS that tells
it to source the part from another organization NYC, you can still define a local
sourcing rule at organization AUS to source the part from yet another organization
SAC. In this case, the local sourcing rule overrides the bill of distribution.
The planning assignment set holds information for:
Sales order global distribution
Organization-to-organization sourcing
Watch for conflicts between sourcing rules for external demands and sourcing rules for
internal demands. For example:
External demand for an item is sourced globally from either organizations M1 or

M2. The sourcing rule is Transfer from with M1, M2. assigned at the item level
Internal demand at organization M1 is sourced from organization M3. The sourcing

rule is Transfer from with M3 assigned at the item/org level. The item/org
assignment tells the planning engine that this sourcing rule applies to the sourcing
for internal demand and not for the external demand.
If you assign a sourcing rule for external demand at the item level, then you cannot
assign a sourcing rule for internal demand at that level.
Ship methods apply to Buy from and Transfer from sourcing rules. To create the ship
methods:
Navigate to Oracle Inventory > Shipping Networks
Navigate to the detail region
Navigate (M) Tools> Shipping Methods
To define a sourcing rule

1.
Navigate to the Sourcing Rule window.
2.
Enter a unique sourcing rule name.
3.
Indicate whether this sourcing rule is used for all organizations (global) or a single
organization (local). If the sourcing rule is local, you must enter an organization
name; otherwise, your current organization will be the receiving organization.
4.
Choose Copy From to copy the effectivity dates and shipping organization from
another sourcing rule into this one.
5.
Enter effectivity dates. You must enter a start date, but entering an end date is
optional.
6.
For each range of effectivity dates, you can include multiple shipping organizations.
For each shipping organization you want to include, select a sourcing type to
specify whether you make, buy, or internally transfer the item. You can also copy a
list of shipping organizations from an existing sourcing rule. If you enter a
customer organization as the receiving organization, then you cannot select a
supplier organization as the shipping organization.
7.
Enter an allocation percentage for each shipping organization. Allocation

percentage includes the number of planned orders issued to the part for the entire
the planning horizon. Your total allocation may not exceed 100. If the allocation
percentage for all the shipping organizations included within a range of effectivity
dates equals 100, Planning Active is checked. If the sourcing rule is not planning
active, the planning process will not use the rule to assign planned orders.
8.
Enter a numeric rank value to prioritize each sourcing type. If you have two sources
with the same allocation percentage, planned orders are sourced from the highest
rank first.
9.
Select a shipping method, such as FEDEX, UPS, or rail. (See: Defining Shipping
Methods, Oracle Inventory User's Guide.
10. Save your work.
To copy shipping organizations from an existing sourcing rule

This feature allows you to include long, previously defined lists of shipping
organizations without manual entry.
1.
Select a sourcing type to specify whether you make, buy, or internally transfer the
item.
2.
Choose Copy Shipping Orgs From.
3.
In the Find window, select a sourcing rule that includes the shipping organizations
you want to duplicate in this new sourcing rule.
4.
Choose OK.
To purge a sourcing rule

1.
Select a sourcing rule name.
2.
Choose Purge.
Defining Bills of Distribution

You can define bills of distribution that specify a multilevel replenishment network of
warehouses, distribution centers, manufacturing centers (plants), and trading partners.
To define a bill of distribution
1.
Navigate to the Bill of Distribution window.
2.
Enter a unique bill of distribution name.
3.
If the allocation percentage for this bill of distribution equals 100, Planning Active is
checked. (See Step 7.)

Note: You cannot set the allocation percentage to less than or
greater than 100 for sourcing rules that are already assigned in
assignment sets
4.
Choose Copy From to copy the receiving and shipping organization information
from another bill of distribution into this one.
5.
Enter the effectivity dates for each receiving organization in this bill of distribution.
6.
For each receiving organization, you can enter a number of shipping organizations.
For each shipping organization, select a sourcing type to specify whether you make,
buy, or internally transfer the item. You can also copy a list of shipping
organizations from an existing bill of distribution.
Note: Suppliers and supplier sites must be predefined in Oracle
Payables. See: About Suppliers, Oracle Payables User's Guide
7.
Enter an allocation percentage for each shipping organization. Allocation

percentage includes the number of planned orders issued to the part for the entire
the planning horizon. Your total allocation may not exceed 100. If the allocation
percentage for all the shipping organizations included within a range of effectivity
dates equals 100, Planning Active is checked. If the sourcing rule is not planning
active, the planning process will use the rule to assign planned orders.
Note: For bills of distribution that are already named in assignment
sets, you cannot set the allocation percentage to less than or greater
than 10
8.
Enter a numeric rank value to prioritize each sourcing type. If you have two sources
with the same allocation percentage, planned orders are sourced in rank order.
9.
Select a shipping method, such as FEDEX, UPS, or rail. See: Defining Shipping
Methods, Oracle Inventory User's Guide.
10. Save your work.
To copy shipping organizations from an existing bill of distribution

This feature allows you to include long, previously defined lists of shipping
organizations without manual entry.
1.
Select a sourcing type to specify whether you make, buy, or internally transfer the
item.
2.
Choose Copy Shipping Orgs From.
3.
In the Find window, select a bill of distribution that includes the shipping
organizations you want to duplicate in this new bill of distribution.
4.
Choose OK.
To purge a bill of distribution

1.
Select a bill of distribution name.
2.
Choose Purge.

them to particular items and/or organizations. These assignments are grouped together
in assignment sets. This is where your various sourcing strategies define a particular
supply chain network.
Each assignment set to represents selection of organizations and/or items you want
planned. To influence the planning process, you must include an assignment set in your
plan options.
In an assignment set can assign your sourcing rules and bills of distribution at different
levels, as follows:
Item-Instance: An item across all organizations. If the Item field is empty, use the
Reduce Criteria Window to restrict the selection.
Item-Instance-Organization: A single item in an inventory organization
Instance-Organization: All items in an inventory organization
Category-Instance: Categories of items
Category-Instance-Organization: Categories of items in an inventory organization
Instance: All organizations
These levels allow you to assign a replenishment rule to as many or as few items as
possible. For example, a category of items could be defined as packaging material, and a
sourcing rule that identifies the suppliers could be assigned.
When you specify a customer in an assignment:
You cannot specify an organization in the same row
The planning engine does not split planned orders by customer. If you want the
planning engine to split planned orders by customer, use project manufacturing.
Create one project per customer so all of the sales orders for each customer peg to
one project.
To assign a sourcing rule or bill of distribution
1.
Navigate to the Sourcing Rule/Bill of Distribution Assignments window.
2.
Enter an assignment set name and description.

Note: The assignment specified in profile option MRP: Default
Sourcing Assignment Set is the only one used by Oracle Purchasing

for its processing
3.
Select an Assigned To type.

Note: You can assign a sourcing rule or bill of distribution to a
category only if you have updated the profile option MRP:Sourcing

Rule Category Set. See: MRP:Sourcing Rule Category Set
4.
Enter an organization name, if the Assigned To type requires one.

Note: You cannot assign customers modelled as organizations to a
global sourcing rule
5.
Enter the name of the customer to which you want to assign a sourcing rule or bill
of distribution.
6.
Enter the specific site to which you want to assign a sourcing rule or bill of
distribution.
7.
Enter an Item/Category if you selected Item or Item-Org as the Assign To type.
8.
Enter the sourcing rule or bill of distribution as the Type.
9.
Enter the name of the sourcing rule or bill of distribution.
10. Enter Condition if the source is Repair at or Transfer fromfective and usable items
in asset intensive planning. It is the condition of the repairable at he end of the

process.
11. Save your work.
To purge a sourcing rule or bill of distribution

1.
Select an assignment set name.
2.
Choose Purge.
Assignments Hierarchy
In the following table, rows below override rows above them. Columns on the right
override columns on the left.
A global sourcing rule has an unspecified receiving organization.
Sourcing Rules vs. Bill of Distribution Assignments
Assignment Scope
Global Sourcing
Rule*
Local Sourcing
Rule
Bill of
Distribution
Global
Yes
No
Yes
Organization
No
Yes
No
Category of Item
Yes
No
Yes
Category of Items in an
Organization
No
Yes
No
Item
Yes
No
Yes
Items in an Organization
No
Yes
No
Since not all assignment types are valid for both sourcing rules and bills of distribution,
the effect of the Sourcing Rules vs. Bill of Distribution Assignments table is illustrated in
a linear hierarchy in the following table. The rows below override rows above them.
Assignment to Levels
Assignment Scope
Sourcing Mechanism
Global
Global Sourcing Rule
Global
Bill of Distribution
Organization
Local Sourcing Rule
Category of Item
Global Sourcing Rule
Assignment Scope
Sourcing Mechanism
Category of Item
Category of Items
Local Sourcing Rule
in an Organization
Item
Local Sourcing Rule
Item
Items in an Organization
Local Sourcing Rule
Viewing Sourcing Rules

You can quickly and easily retrieve sourcing rules for reference. After retrieving a
sourcing rule, you can display it in a convenient, hierarchical representation, or you can
locate the assignment sets in which it is assigned.
To view sourcing rules
1.
Navigate to the View Sourcing Rule or Sourcing Rule window.
2.
Place your cursor in the Name or Description field and select Find or Find All from
the query menu.
3.
Choose View to launch the Object Navigator and display the graphical view of your
sourcing rule.
With the Object Navigator, you can display your sourcing rule in a visual hierarchy.
Each element in the sourcing rule is displayed in a rectangular node, with
connecting lines that depict the nodes' relationships to each another (known as the
data flow). The nodes are also color-coded for easy identification, and other aspects
of the data flow can be changed to meet specific requirements.
To view assignments for your sourcing rules

Sourcing rules govern replenishment of specific items in your enterprise based on the
rule's assignment. Sourcing rules can be assigned to an item, and item in an
organization, an organization, a category of items, a category of items in an
organization, or to all items.
When modifying or viewing a sourcing rule, you can quickly refer to all the assignment
sets in which the rule participates. You can also refer to the assignment level assigned to
the rule. For more information about assignment sets, see: Assigning Sourcing Rules
and Bills of Distribution.

1.
Navigate to the View Sourcing Rule or Sourcing Rule window.
2.
the Query menu.
3.
Choose Assignment Set. The list that appears includes all sets in which the current
rule participates.
For each Sourcing Rule and Bill of Distribution in the Assignment Set, you can review
the following information:
Assigned to: Each Sourcing and Bill of Distribution can be assigned:
A single item (across all organizations)
An item in a specific organization
All items in a specific organization
A category of items
A category of items in an organization
All items in all organizations (globally)

Note: You can assign a sourcing rule to a category only if you have
updated the profile option MRP:Sourcing Rule Category Set. See:

MRP:Sourcing Rule Category Set
Organization: Rules or bills assigned to an organization, a category of items in an

organization, or an item in an organization will also display the name of that
organization.
Customer and Customer Site: Rules or bills associated with a customer will also
display this information.
Item/Category: Rules or bills assigned to an item or an item in an organization will

display with the associated item or category of items (if the profile option has been
updated to include categories).
Viewing Bills of Distribution

You can quickly and easily retrieve bills of distribution for reference. After retrieving a
bill of distribution, you can display it in a convenient, hierarchical representation, or
you can locate the assignment sets in which it is assigned.
To view bills of distribution

1.
Navigate to the View Bill of Distribution or Bill of Distribution window
2.
the Query menu.
3.
Choose View to launch the Object Navigator and display the graphical view of your
bill of distribution.
With the Object Navigator, you can display your bill of distribution in a visual
hierarchy. Each element in the bill is displayed in a rectangular node, with
connecting lines that depict the nodes' relationships to each another (known as the
data flow). The nodes are also colorcoded for easy identification, and other aspects
of the data flow can be changed to meet specific requirements.
To view assignments for your bills of distribution

Bills of distribution govern replenishment of specific items in your enterprise based on
the bill's assignment. Bills of distribution can be assigned to an item, and item in an
organization, an organization, a category of items, a category of items in an
organization, or to all items.
When modifying or viewing a bill of distribution, you can quickly refer to all the
assignment sets in which the bill participates. You can also refer to the assignment level
assigned to the rule. For more information about assignment sets, see: Assigning
Sourcing Rules and Bills of Distribution.
1.
Navigate to the View Bills of Distribution or Bill of Distribution window
2.
the Query menu.
3.
Choose Assignment Set. The list that appears includes all sets in which the current
bill participates.
A category of items

Note: You can assign a sourcing rule to a category only if you
have updated the profile option MRP:Sourcing Rule Category

Set. See: MRP:Sourcing Rule Category Set

organization.
Customer and Customer Site: Rules or bills associated with a customer will also
display this information.

Viewing Sourcing Rule and Bill of Distribution Assignments

them to particular items and/or organizations. These assignments are grouped together
in assignment sets. This is where your various sourcing strategies define a particular
supply chain network.
You can quickly view your assignment sets to review particular sourcing schemes,
locate particular assignments of sourcing rules or bills of distribution, or view the
supply chain bill for a particular assignment set.
To view sourcing rule and bill of distribution assignments
1.
Navigate to the Sourcing Rule/Bill of Distribution Assignments window.
2.
Place your cursor in the Assignment Set or Description field and select Find or Find
All from the Query menu.
3.
Select an assignment set from the list.
A category of items

Note: You can assign a sourcing rule to a category only if you
have updated the profile option MRP:Sourcing Rule Category

Set. See: MRP:Sourcing Rule Category Set.

organization.

To view details of a particular rule or bill

When viewing an assignment set, you can quickly retrieve full details on any sourcing
rule or bill of distribution named in the set.
1.
In the Assignments region, place your cursor in any field on the row containing the
rule or bill you want.
2.
Choose View Sourcing Rule/BOD
Displaying an Indented Where Used

To display an indented where used information for an item
1.
Navigate to the View Supply Chain Bill window.
2.
Enter the name of an assignment set.
3.
Enter an organization.
4.
Enter an item and date.
5.
Choose View Indented Where Used to launch the Object Navigator and display the
graphical view of item's indented where used information.
With the Object Navigator, you can display your data in a visual hierarchy. Each
element in the sourcing rule is displayed in a rectangular node, with connecting
lines that depict the nodes' relationships to each another (known as the data flow).
The nodes are also colorcoded for easy identification, and other aspects of the data
flow can be changed to meet specific requirements.
See Also
Sourcing Rules and Bills of Distribution
Viewing the Sourcing Assignment Hierarchy
Displaying an Indented Bill

To display indented bill for an item
1.
2.
3.
4.
5.
Choose View Indented Bill to launch the Object Navigator and display the
graphical view of item's indented where bill information.
The nodes are also color-coded for easy identification, and other aspects of the data
flow can be changed to meet specific requirements.
See Also

Use this window to display all the assignment levels and identify the active assignment
level.
To view the sourcing assignment hierarchy for an item

1.
2.
3.
4.
5.
Choose View Sourcing Hierarchy.
See Also

Material requirements planning (MRP) and distribution requirements planning (DRP)
calculates organization-specific net requirements from gross requirements by
evaluating:
The master schedule
Bills of material
Sourcing rules
Supply chain bills
Scheduled receipts
Production and transportation lead times
Order modifiers
It then plans replenishments by creating a set of recommendations to release or

reschedule orders for material based on net material requirements. These planned
orders are assigned to a predefined replenishment structure, stated in:
Discrete quantities with due dates
Repetitive build rates with first/last unit start dates

Chain functionality
See Also
Supply Chain Planning Methods
Overview of Plan Generation in Supply Chain Planning
MPS Plan Generation in Supply Chain Planning
MRP and DRP Generation in Supply Chain Planning
Defining MRP/DRP Names in Supply Chain Planning
Reviewing or Adding Supply Chain Plan Options
Planning Organizations
Netting Supply and Demand in Supply Chain Planning

Oracle Supply Chain Planning applies the basic planning process (described in
Overview of Planning Logic) across multiple organizations. Planned order supply and
sourcing information are loaded according to the list of organizations and supply
schedules defined for the multiple organization plan.
The supply chain planning process calculates net material requirements by evaluating:
Demand and production schedules
Sourcing strategies
Bills of material
Scheduled receipts
Order modifiers
The purpose of the planning process is to derive an MPS, DRP or MRP that meets
schedule dates while maintaining inventory replenishment policies.
The netting process:
Creates and reschedules planned orders
Assigns sources to the planned orders, according to rank and sourcing percentages
Generates dependent demand across multiple organizations See: Netting Supply

and Demand.
When assigning sources to planned orders (according to the percentage splits defined
by the sourcing rules and bills of distribution), planning begins with the organization
that is immediately below its shipping percentage target. See: Assigning Sourcing Rules
and Bills of Distribution and Assignments Hierarchy.
When generating dependent demand for an organization different from the one in the
planned order, planning creates demand for the same item in the other organization
and offsets the demand by the transportation lead time.
Sourcing Assignment Logic
Oracle Supply Chain Planning uses the following components in sourcing assignment
logic in order to allocate planned orders.
Note: Ranking information for suppliers is set in the Sourcing Rule
window or Bill of Distribution window. Planning capacity information

is set in Oracle Purchasing - in the Planning Constraints region of the
Supplier - Item Attributes window.
Alternate Sources
If the primary supplier does not have the capacity to meet demand, alternate suppliers
can be specified according to your priority. The supplier capacity defined in Oracle
Purchasing is used to determine if the primary source can fulfill the order. The ranking
order specified in in the rules and bills determines which sources can be used as
alternates.
Delivery Frequency Calendars
You can specify delivery dates for each supplier or supplier/item combinations and
create a schedule to define the dates an organization is able to receive items. The
planning engine adjusts planned orders so deliveries are scheduled for the dates the
receiving organization is available. You enter processing lead times in Oracle
Purchasing, and then choose a Delivery Calendar pattern. The Delivery Calendar is
independent of your workday calendar.
Historical Allocations
Planning recognizes the historical allocation assigned to each source, organization, or
supplier in recommending sources to new planned orders. Historical allocation includes
all requisitions, purchase orders, and receipts in the case of suppliers. And all discrete
jobs, repetitive schedules, flow schedules, and organization transfers in the case of
Make At organizations.
Rank and Allocation
You can define a rank for each source of supply named in the rules and bills, and then
define a sourcing percentage for each source within a rank. You can also assign
sourcing percentages to these sources allowing you to allocate a portion of the total
orders to each source.
Splitting Of Demand According To Sourcing Percentages
Demand can be divided and allocated to multiple sources according to target sourcing
percentages set in the rules and bills.
The data in these tables demonstrate how allocation percentages for planned orders are
divided according to ranking information.
The demand for Item A on the date of 06/10 is:
Demand
Due Date
Quantity
07/15
300
Item
Source
Rank
Percentage
Effective
From
Effective To
S1
40
05/15
12/31
S2
30
05/15
12/31
S3
30
05/15
12/31
Demand is assigned using the ranking information and calculating the percentages
assigned to each source to calculate the planned orders.
S1: 300 x 0.40 = 120
S2: 300 x 0.30 = 90
S3: 300 x 0.30 = 90
Three planned orders are created for the quantities of 120, 90, and 90 respectively.
Note: All planned orders generated in this process are subject to item
order modifiers
Supplier Capacity Constraints

You can specify the time-phased capacity of individual suppliers to specific items in
Oracle Purchasing. You can allocate planned orders using the constraints of the
suppliers-planned orders are assigned supplier sources in respect to their capacity.
Planning uses the ranking information you specify and first attempts to source the
planned orders with the primary sources. If the capacity to fulfill the demand is not
available, alternative sources are used.
Supplier Specific Lead Times
Processing lead time for each source of an item can be specified so that orders are
placed in time. The lead time information entered on the Supplier - Item Attributes
window in Oracle Purchasing overrides the item master information defined in Oracle
Inventory.
Supplier Specific Order Modifiers
Order modifiers can be specified at the supplier site level, this overrides item level
order modifiers.
Tolerance Fence
You can define capacity tolerance percentages that can vary for each of your items. The
tolerance fence data in Oracle Purchasing is used to adjust production according to
capacity changes for item/supplier combinations when the order is placed. Tolerance
fence values can be specified for the capacity fluctuation allowed for available to
promise; and used to determine demand based on the amount of advanced notice given
to the supplier.
See Also
View Approved Suppliers, Oracle Purchasing User's Guide
Resource Authorizations, Oracle Supplier Scheduling User's Guide
Defining the Supplier and Commodity/Item Combination, Oracle Purchasing User's

Guide
Supply Chain Planning Methods in Oracle Inventory

You can define an MRP planning method for an item when you define an item in Oracle
Inventory. Items that are considered by the planning process must have one of the
following MRP planning methods:
MPS planning
MRP planning
Oracle Supply Chain Planning users can define three additional attributes:
DRP planning
MRP and DRP planning
DRP Planning
Select DRP planning for items that appear in a distribution requirements plan.
MPS and DRP Planning
Select MPS and DRP planning for items that appear in DRP and MPS plans that are
primarily planned in MPS plans.
MRP and DRP Planning
Select MRP and DRP planning for items that appear in MRP and DRP plans, but are
planned in MRP plans.
Note: You can set the MRP Planning method item attribute to MPS and
DRP planning so that the longterm material requirements for an item

are generated
Review Planning Methods for information on planning methods in MRP.
Defining MRP and DRP Names in Supply Chain Planning

By defining multiple MRP/DRP names, you can define any number of material
requirements and distribution requirements plans. You can use multiple plan names to
simulate MRP/DRP for different sets of data. Review Defining MRP Names for
instructions on defining names in MRP.
To define MRP and DRP names

1.
Navigate to the MRP Names or DRP Names window.
2.
Enter an alphanumeric name that identifies a unique material requirements or

distribution requirements plan.
3.
Select an organization selection to indicate if the plan is planning for all

organizations (All) or a list of organizations (Multiple).
4.
implemented as discrete jobs, purchase orders, or purchase requisitions. This
provides the planner visibility of the status of the plan at any point in time.
5.
Check Production to enable a plan to autorelease planned orders. See: Auto

release Planned Orders.
6.
Follow the standard procedure in Defining MRP Names to complete this task.
See Also
Planner Workbench

Supply Chain Planning users can launch the planning process for a multi-organization
material requirements plan (MRP) or master production schedule, or a distribution
requirements plan (DRP). The planning process uses the input from a supply schedule
(a DRP, an MPS, or an MRP) or a demand schedule to determine the quantities and

timing of the items to be manufactured or purchased.
Prerequisites
Before you can launch the planning process, you must:
For MPS, MRP, or DRP: define at least one demand or supply schedule. See:
Defining a Schedule Name and Defining a Supply Chain Schedule Name.
Create at least one MPS, DRP, or MRP plan name. See: Defining MRP Names and
Defining MRP/DRP Names.
To launch a supply chain planning process

1.
Navigate to the Launch MPS, Launch MRP, or Launch DRP window.
2.
In the Parameters window, select a plan name and launch options.
3.
Follow the standard procedure in Launching the Planning Process to complete this
task.
See Also
Overview of the Memorybased Planning Engine
Overview of Capacity Planning, Oracle Capacity User's Guide Submitting a Request,

Oracle Applications User's Guide
Reviewing or Adding Supply Chain Plan Options

You can enter additional plan options for a DRP or multiorganization MRP or MPS.
You can also view plan options in the Plan Status window.
Note: If you are launching the planning process for this plan name for
the first time, the plan options you defined in the setup parameters are
displayed. Otherwise, the plan options you chose for the last launch of
the planning process are displayed. If you are launching a plan for
simulation purposes, do not check these plan options.
To add plan options

1.
2.
Query a plan name.
3.
Enter the Assignment Set name.
4.
All: For an MPS plan, overwrite all entries and regenerate new MPS entries
based on the source master demand schedule.
For an MRP or DRP, overwrite all planned orders and firm planned orders for
MRP or MRP/DRP items.
This option is displayed when you generate a plan for the first time.
Caution: Be very cautious when using this option since it
overwrites firm planned orders and/or master schedule entries.

If you do not want to overwrite MRP or DRP firm planned
orders, select None.
Outside planning time fence: For an MPS plan, overwrite all MPS entries outside
the planning time fence.
For an MRP or DRP, overwrite all planned orders and firm planned orders
outside the planning time fence.
Caution: Be very cautious when using this option since it
overwrites MRP firm planned orders and master schedule

entries outside the planning time fence. If you do not want to
overwrite MRP or DRP firm planned orders, select None.
5.
None: Do not overwrite any firm planned orders for MPS, MRP, or DRP plans
and net change simulation.
Check Append Planned Orders to append new planned orders in the following
situations:
If the MPS plan name has an existing schedule associated with it and you enter
None as the overwrite option, the planning process does not recommend
rescheduling or suggest new planned orders before the end of the existing MPS (the
last planned order) - even if so indicated by new demand from the master demand
schedule. This is analogous to firming your master production schedule. By not
overwriting, the master scheduler is taking responsibility for manually planning
items. For an MRP plan name, this option creates planned orders where needed,
considering existing MRP firm planned orders.
Note: If you want to simulate the addition of new planned orders
using net change replan, set overwrite to Outside planning time fence
or None
If the plan name has an existing MPS, MRP, or DRP associated with it and you enter
All as the overwrite option, the planning process deletes all previous planned
entries and creates new planned orders based on the source master schedule.
Outside planning time fence as the overwrite option, the planning process deletes all
planned entries after the planning time fence and creates new planned orders after
that date. In this case, since you are overwriting after the planning time fence, you
are also appending new planned orders after that date.
None as the overwrite option and do not check this, the planning process reports the
instances where the plan is out of balance with the source master schedule. It does
not recommend any new orders. Instead it lets you manually solve any problems in
the process. This gives maximum control to the master scheduler and/or material
planner.
6.
Check Demand Time Fence Control to indicate whether the planning process
considers any demand from forecasts within the demand time fence.
The planning process does not consider any demand from forecasts within the
demand time fence, but considers demand from sales orders.
7.
Check Snapshot Lock Tables to indicate whether tables are locked during the
snapshot process to guarantee consistent data.
This option temporarily prevents other users from processing certain transactions.
8.
violates planning time fences for items.
For discrete items, the planning process does not create planned orders or
recommend to reschedule in existing orders within the planning time fence of the
item. The planning process can still recommend to reschedule orders out.
For repetitive items, the planning process can vary the suggested schedule from the
optimal schedule, within the planning time fence, by the acceptable rate increase
and/or decrease you specified for the item.
9.
Check Plan Capacity to indicate whether you want to generate a capacity plan.
10. Check Pegging to calculate Graphical Pegging information. See: Overview of
Graphical Pegging. The planning process then traces supply information for an item
to its corresponding end demand details, which you then can view in a
diagrammatic display.
11. If you are working in a project manufacturing environment, set a Reservation Level
and a Hard Pegging Level. This option supports functionality planned for a future
release.
Reservation Level: Set the level at which the planning process will reserve supply
against demand.
Planning Group: Reserve project - specific supply and demand at the planning
group level. Supply for one project can be reserved against demand from
another project, if both projects belong to the same planning group.
Project: Reserve supply for a project against demand from the same project.
Supply for one project-task can be reserved for demand for another project-task,
if both project-tasks belong to the same project.
Task: Reserve supply for a project-task against demand for the same
project-tasks only.
None: The planning process does not operate in a project manufacturing

environment.
Hard Pegging Level: Set the granularity of planned orders in a project manufacturing
environment.
Project: Create planned orders at the project level. The planning process will
generate planned orders with a project reference and associate it to demand at
the project level.
Project-task: Create planned orders at the project-task level. The planning

process will generate planned orders with a project and task reference and
associate them to demand at the project-task level.
None: Create soft-pegging information for the item. This option is valid only
when the item attribute is soft pegging or hard pegging.
Operation Start Date: Schedule material to arrive in inventory for availability on the
start date of a specific operation in the manufacturing process.
Order Start Date: Schedule material to arrive in inventory for availability on the
work in process order start date.
13. Specify which planned items or components you want included:
Note: If you are launching the planning process for a master
production schedule, you cannot edit or enter data in MDS/MPS

components fields
All Planned Items: Include all planned items in the planning process. You would
chose this option to be certain that all items are planned, such as those you add to a
job or schedule that are not components on any bill.
Note: You may want to plan using this option to avoid missing
items you want to plan. For items you do not want to plan, define
them with an MRP Planning Method of Not planned when you
define an item in Oracle Inventory
Demand schedule items only: Include all the items specified in your demand
schedule(s). You can specify more than one MDS per organization.
Supply schedule items only: Include the items with Firm Planned Orders within the
specified supply schedule(s) only. Supply schedules could be MPS (where all
planned orders are firmed automatically), DRP, or MRP schedules.
Supply and demand schedule items only: Include items from both the specified demand
schedule(s) and the Firmed Planned Orders from any specified supply schedule(s).
14. Save your work.
See Also
Planner Workbench
Time Fence Planning
Defining Items, Oracle Inventory User's Guide Viewing Pegged Supply and Demand
Overview of Plan Generation in Supply Chain Planning

Multiorganization material requirements plans (MRP), master production schedules
(MPS), and distribution requirements plans (DRP) explode through the bill of material
to generate component requirements by evaluating:
Order modifiers
Sourcing strategy
Bill of material changes
Engineering changes
Item information
It then calculates time-phased material requirements. Each item may have different
attributes that affect the recommendations generated by the planning process.
Review Plan Generation for information on plan generation in Oracle MRP.
Specifying Items for the Supply Chain Planning Process
The items included the planning process depends on the planning method set for them
(in their item attributes) and on whether you allow the planning process to include
them. In Oracle MRP, you select the type of item subject to the planning process in the
Planning Parameters window. In Oracle Supply Chain Planning, you make this
selection in the Plan Options window.
You can include:
All planned items
Demand schedule items only
The planning process interprets these options differently, depending on the type of plan
you choose to run. The following table compares the effect of the Planned Items option
on an MPS, MRP, and a DRP:
Comparison of Planned Items options in DRP, MPS, and MRP plans

Plan Option
DRP includes...
MPS includes...
MRP includes...
Include all items
All items in the

planned
organizations having
an MRP planning
code of:
All items in the

planned organizations
having an MRP
planning code of:
All items in the planned

organizations except
ones having MRP
planning code of Not
Planned.
DRP planning
MRP and DRP
planning
MPS and DRP
planning
MRP planned and
MPS planned items
that are in between
the above items in the
bill structure. All
items in the input
schedules.
Include demand
schedule items
only
All items in the input

demand schedules,
and all components of
these items that have
an MRP planning
code of:
DRP planning
MRP and DRP
planning
MPS and DRP
planning
MPS and MRP
planned items that
are in between the
above items in the bill
structure.
MPS planning
MRP planned and
MRP/DRP planned
items that are in
between the above
items in the bill
structure.
schedules.

demand schedules, and
all components of these
items that have an MRP
planning code of:

demand schedules, and
planning code of:
MPS planning
MRP planning
Plan Option
DRP includes...
MPS includes...
MRP includes...
Include supply
schedule items
only

supply schedules, and
all components of
these items that have
an MRP planning
code:

planning code of:

planning code of:
MPS planning
MRP planning

demand and supply
schedules, and all
components of these
planning code of:

demand and supply
schedules, and all
components of these
planning code of:
DRP planning
MRP planning
MRP and DRP

planning
DRP planning
MRP and DRP
planning
MPS and DRP
planning
MRP planned and
MPS planned items
that are in between
bill structure.
Include demand
and supply
schedule items
only

demand and supply
schedules, and all
components of these
items that have an
MRP planning code
of:
DRP planning
MRP and DRP
planning
MPS and DRP
planning
MRP planned and
MPS planned items
that are in between
bill structure.

MRP planned and MPS
planned items that are
in between the above
items in the bill
structure.
MPS Plan Generation in Supply Chain Planning

Supply Chain Planning users can launch the planning process for an MPS from an MDS
or another MPS. This generates a plan for all your MPS planned items. Oracle Supply
Chain Planning also plans any MRP planned items that have an MPS planned
component. This ensures that all derived demand is correctly passed down.
See Also
Material Requirements Plan Generation
MRP and DRP Generation in Supply Chain Planning

Supply Chain Planning users can launch the planning process for an MRP or DRP from
a master demand schedule or a master production schedule. This generates planning
recommendations for all MRP and DRP planned items. The following table lists all the
types of items you can include in a supply chain MRP and DRP:
Planned Items options in a DRP and MRP plan
Plan Type
Plan Option
Included Items
DRP
Include all items
All items in planned organizations having an

MRP planning code of:
DRP planning
Also, MRP planned and MPS planned items that
are in between above items in the bill structure.
Also, all items in the input schedules.
Include demand
schedule items only
All items in the input demand schedules. All

components of the above items that have an MRP
planning code of:
DRP planning
MPS a nd DRP planning
Also, MPS and MRP planned items that are in
between the above items in the bill structure.
Plan Type
Plan Option
Included Items
Include supply
schedule items only
All items in the input supply schedules. All

components of the above items that have MRP
planning code:
DRP planning
Also, MRP planned and MPS planned items that
are in between the above items in the bill
structure.
Planned Items options in a DRP and MRP plan

Plan Type
Plan Option
Included Items
Include demand and supply

schedule items only
All items in the input demand

and supply schedules. All
components of the above items
that have MRP planning code of:
DRP planning
Also, MRP planned and MPS
planned items that are in
between the above items in the
bill structure.
MRP
Include all items
All items in the planned

organizations except ones having
MRP planning code of Not
Planned.
Plan Type
Plan Option
Included Items
Include demand schedule

items only

schedules. All components of the
above items that have MRP
planning code of:
MRP planning
Include supply schedule items

only
All items in the input supply

schedules. All components of the
above items that have MRP
planning code of:
MRP planning
Include demand and supply

schedule items only

and supply schedules. All
components of the above items
that have MRP planning code of:
MRP planning:
From a Master Demand Schedule

If you do not need to smooth production or otherwise manually manipulate a master
production schedule, you can generate an MRP or DRP plan directly from a master
demand schedule.
The planning process overrides the MRP planning method and treats MPS planned
items as MRP or MRP/DRP planned items. As a result, the planning process generates
planned orders and reschedules recommendations for your MPS/DRP and MRP/DRP
planned items planned items.
From Supply
You can also generate an MRP, DRP, or MPS plan from an MPS, MRP, or DRP plan. For
plants that are planned in the source supply schedules, the planning process considers
projected gross requirements, current orders for the item, the master production
schedule, and on-hand quantities over time. The planning process calculates the
projected quantity on hand and generates exception messages to signal any potential
imbalances in the material plan.
The planning process does not make any recommendations to change the master
production schedule or existing orders for items based on higher level demand. These
parts are maintained and planned in the source supply schedule.

See Also
MPS Plan Generation
Planning organizations allows you to set plan options specific to each organization, and
to specify different demand and supply schedules.
Note: If you're using the Drop Shipment feature of Order Entry and
Purchasing, you don't need to add the logical org used for P.O. receipts
to the plan
To review or add plan options to multiple organizations

1.
Navigate to the Plan Organizations window.
2.
Query a plan name.
3.
In the Organizations region, select an organization.
4.
For each organization you include, check the following items:

Net WIP: Consider standard discrete jobs, non-standard discrete jobs, firm repetitive
schedules, or flow schedules when planning the items during the last execution of
the plan.
Net Reservations: Consider stock designated for a specific order when planning the
items during the last execution of the plan.
Net Purchases: Consider approved purchase requisitions and approved purchase
orders when planning the items during the last execution of the plan.
Plan Safety Stock: Calculate safety stock for each item during the last execution of the
plan.
5.
If you have chosen to plan capacity (in the Plan Options window), enter values for
the following fields:
Bill of Resource: See: Bills of Resources, Oracle Capacity User's Guide.
Simulation Set: See: Capacity Modifications and Simulation, Oracle Capacity User's
Guide.
6.
In the Demand Schedules region, enter an MDS for each organization you include.
7.
In the Supply Schedules region, enter an MPS, MRP, or DRP for each organization
you include.
Netting Supply and Demand in Supply Chain Planning

The netting parameters allow you to control the different sources of visible supply and
demand when calculating net requirements.
You can optionally choose to net WIP, purchases, reservations and subinventories when
To net purchases, WIP, and reservations

1.
2.
Check Net Purchases, Net WIP, and Net Reservations to net supply and demand for
each.
Net WIP: Consider standard discrete jobs, non-standard discrete jobs, repetitive
schedules, or flow schedules when planning the items during the last execution of
the plan.
Net Reservations: Consider stock designated for a specific order
when planning the items during the last execution of the plan.
Net Purchases: Consider approved purchase requisitions and approved purchase
orders when planning the items during the last execution of the plan.
3.
Save your work.

Note: You can also override these default options for individual plans
and organizations when you generate an MPS, MRP or DRP plan from
the Launch MPS, Launch MRP, or Launch DRP windows. Choose Plan
Organizations in the Launch MPS Launch MRP, or Launch DRP
window
To net subinventories
1.
Navigate to the Plan Organizations window.
2.
Enter a name in the Organizations region and choose Subinventory Netting.
3.
For each item, check Net to indicate that you want to net supply and demand for
these subinventories.
Note: You assign a netting type when you define a subinventory in
Oracle Inventory. The planning process considers the inventory in

a nettable subinventory as supply. You can override the netting
type for a specific subinventory when you launch the planning
process.
4.
Check the unlabeled, coordination check box (next to the Type field) if you want to
constantly update the coordination of records between the Plan Options and
Subinventory Netting windows. See: Masterdetail Relationships.
See: Master-detail Relationships, Getting Started and Using Oracle Applications.
5.
Save your work.
See Also
Net Purchases
Net Work in Process
Net Reservations
Overview of the Supply Chain Planner Workbench

In addition to the recommendations suggested by the planning process with the
Planner Workbench, Supply Chain Planning users can review and selectively
implement these recommendations across multiple organizations.
Review Overview of Planner Workbench for a full description of features available in
Oracle MRP Planner Workbench.
With Planner Workbench, Supply Chain Planning users can:
View the horizontal netting information for an item in several different inventory
locations at once
Display inventory status summary for an item for each organization that carries the
item, including onhand quantities, open customer orders, reservations, open
replenishment orders, and quantities available to reserve
Display data generated at the snapshot (the last planning run) or data in its current
state (including all changes to the plan)
Generate a graphical view of the relationship between item supply and end
demand - at all levels of the bill of materials and at any number of facilities in the
distribution network
Generate a graphical view of the supply chain bill for an item in an organization,
showing all item/location combinations
If you are using supplier planned inventories, the following restrictions apply to
implementing planned orders:
You cannot implement planned orders in supplier organizations.
Planned orders in customer organizations must be implemented as sales orders

rather than internal requisitions.
Planned orders sourced from supplier organizations must be implemented as

purchase requisitions, rather than internal requisitions.
Chain functionality
Reviewing Source and Destination Organizations

You can walk up and down the bill of material and display the organization, effective
dates, and assignment information for the item in your bill.
To review source organizations of the selected item

1.
Navigate to the Items window.
2.
Check the Item.
3.
Choose Sources to display the Sources window.
4.
Choose a tabbed region:

Sourcing: you can review the source organization, supplier, allocation percent, and
ship method.
Effective Dates
Assignment Information: you can review the sourcing rule and assignment type.
To review destination organizations of the selected item

1.
2.
Check the Item.
3.
Choose Destinations to display the Destinations window.
4.

Sourcing: you can review the source organization, supplier, allocation percent, and
ship method.
Effective Dates
Assignment Information: you can review the sourcing rule and assignment type.
See Also

Master scheduling in Supply Chain Planning is used for:
Enterprise-wide demand management
Scheduling production throughout the supply chain
Validating the production schedule
Managing the production schedule
You use the schedules generated by master scheduling as input to other manufacturing
functions, such as material requirements planning, distribution requirements planning,
and rough-cut capacity planning.
Chain functionality
See Also
Supply Chain Master Schedule Types
Defining a Supply Chain MPS Entry Manually
Loading a Supply Chain MPS from an Internal Source Material and Distribution
Requirements Planning

Master Demand Schedule (MDS)
The Supply Chain MDS is a statement of interorganizational demand. It contains details
of the anticipated shipment schedule, loaded from several sources. You can use the time
phased master demand schedule as input to the master production scheduling process,
the material requirements planning process, distribution requirements planning, and,
indirectly, the replenishment strategy.
Some of the demand types that the Supply Chain MDS considers are:
Item forecasts
Spares demand
Sales orders
Internal requisitions
New products
Internal material transfers
Master Production Schedule (MPS)

The Supply Chain MPS is a statement of supply required to meet the demand for the
items contained in an MDS or another MPS. You can use the Supply Chain MPS to level
or smooth production so that you effectively utilize capacity to drive the material
requirements plan or distribution requirements plan
Loading the Supply Chain Master Schedule from Multiple Sources
In addition to standard sources, Supply Chain Planning users can derive the master
schedule from DRP Planned orders. You can manually define your supply chain master
schedule or modify entries loaded from other sources.
Review the section Loading the Master Schedule from Multiple Sources for further
information.
Interorganization Orders
Supply Chain Planning users can load planned order demand from a requesting
organization into the master demand schedule of the supplying organization.
See Also
Master Schedule Types
Defining a Supply Chain MPS Manually
Loading a Supply Chain MPS from an Internal Source

While defining MPS names, Supply Chain Planning users can also indicate if the plan
will apply to several or all organizations in the enterprise.
Review the task Defining a Schedule Name before proceeding with these steps.
To define a schedule name

1.
Navigate to the Master Production Schedules window (called MPS Names in the
navigator). Master demand schedules are always associated with a single
organization.
2.
Enter a name and description.
3.
Select an organization selection to indicate if the plan is planning for all

organizations (All) or a list of organizations (Multiple).
4.
Optionally, select a demand class.
5.
Optionally, select Yes in the flexfield to enable the Memory-based Planning Engine.
Note: You must use the Memorybased Planning Engine to use
Supply Chain Planning functionality.
6.
Follow the standard procedure in Defining a Schedule Name: to complete this task.
See Also
Defining Supply Chain MPS Entries Manually

While manually defining MPS entries, Supply Chain Planning users can also add items
with an item attribute of MPS Planned or MPS/DRP Planned.
Review the task Defining Schedule Entries Manually before proceeding with these
steps.
To define MPS entries manually

1.
Navigate to the Master Production Schedules window (called MPS Names in the
navigator).
2.
3.
Choose Items to open the Master Production Schedule Items window.
4.
If you are creating entries for a demand schedule, enter an item with the following
MRP planning methods (see: Defining Items, Oracle Inventory User's Guide):
MPS
DRP and MPS
5.
Follow the standard procedure in Defining Schedule Entries Manually to complete

this task.
See Also

While loading an MPS from an internal source, Supply Chain Planning users can load
DRP planned orders and include specific sourcing and replenishment schemes.
Review the task Loading the Master Schedule from an Internal Source for further
information.
Source Type Field
You can load a master schedule from any of the following internal sources:
Specific Forecast
Sales Orders Only
Specific MDS or Specific MPS
Source Lists

You can load planned order demand from one or more requesting organizations into
the master schedule of a supplying organization.
See Also
Loading a Master Schedule from an Internal
6
Planner Workbench
Overview of Planner Workbench

You can review and implement recommendations suggested by the planning process
with the Planner Workbench. You can selectively implement these recommendations as
new and rescheduled orders, and release all or some of them.
You can:
review your resources
review item details
review of supply/demand details
review components, using assemblies, and end assemblies
review the horizontal, material, and capacity plan
display a summary supply and demand
implement and maintain planned orders
create planned orders manually
implement repetitive schedules
release implemented orders
create firm planned orders and firm implemented orders
review material and capacity exceptions
display a summary of resource requirements
Planner Workbench 6-1
You can select a predefined set of criteria or any combination of criteria when querying
on the recommendations generated by the DRP, MRP or MPS planning process. The
planner can then:
change parts of the plan, then replan changes and all items affected by them using
either a batch or an online process
load any combination of the selected recommendations into work in process or

purchasing, or firm an implemented order, prior to loading, to create a firm
scheduled receipt
view a plan's resources including items, availability, requirements, and horizontal

plan
firm a planned order or change its quantity and date to stabilize portions of the plan
assign a supplier or transfer source to firm planned order
change the alternate BOM designator or alternate routing designator on planned

orders or discrete jobs, and import into WIP
reschedule current scheduled receipts from work in process or purchasing
change repetitive schedule lines, status, dates, and quantities
view graphical horizontal plan
generate a graphical view of the relationship between item supply and end demand
Supply Chain Planning users can also review and implement recommendations across
multiple, interdependent organization. See: Overview of the Supply Chain Planner
Workbench.
Quick Access to Particular Documents

You can place documents that you reference frequently in the Oracle Applications
Navigator. Placing documents in the Navigator is especially useful when you need to
query large documents. When the document is open, choose Place on Navigator from
the Action menu. When you choose the Documents tabbed region in the Navigator, you
can then access that document directly from within the Navigator. See: Using the
Navigator's Documents Region, Oracle Applications User's Guide.
Reviewing Planning Information

Overview of Reviewing Planning Information
Before implementing planning recommendations, you can review your material plans.
You can review planning exception messages, resource availability, item information,
supply details, the horizontal plan, and a summary of supply and demand.
Supply Chain Planning users can also get a summary of supply and demand for all
organizations included in the plan.
Note: The planning products support Oracle Project Manufacturing 's
model/unit effectivity. The fields of Unit Number, Effectivity Control,

From Unit Number, and To Unit Number are visible if this featured is
enabled. They are displayed in the following windows:
Supply/Demand, Items, End Assemblies, Where Used, and Pegging.
See Also
Reviewing Item Planning Information
Reviewing Resources Information
Reviewing Current Data
Generating a Graphical Display of Planning Data
Online Planner
Net Change Replan
Available to Promise (ATP)
Model/Unit Effectivity, Oracle Project Manufacturing Implementation Manual
Reviewing Resources Information

1.
Navigate to the Planner Workbench window.
2.
Select a plan name.
3.
Choose Resources to display planning information in the Resources window.
4.
In the Find Items folder window, enter your search conditions. See: Customized
Find Windows.
5.
Choose Find.
This window specifies a plan's resources by department or line. In this window you
can also choose buttons to review a resource's items, availability, requirements, and
horizontal plans.

Note: Plan Status can be viewed by selecting Tools from the pull down menu. You can
also initialize Copy Plans by selecting Tools from the pull down menu.
To review item planning information

1.
2.
Select a plan name.
3.
Choose Items to display planning information in the Items window. See: Defining
Items, Oracle Inventory User's Guide.
4.
In the Find Items folder window, enter your search conditions. See: Customized
Find Windows
5.
Choose Find.
6.
Select an item.
You can use this to highlight or drill down into other windows for selected items.
Choose the Attachments toolbar icon to use the Attachments feature. See Working with
Attachments, Oracle Applications User's Guide.
Note: BOM calendar periods are used, not accounting periods.
See Also
Items Find Window
Viewing Onhand Quantities
Reviewing Assembly Components
Reviewing Using Assemblies
Reviewing End Assemblies
Navigating through a Find Window
Searching for Information, Oracle Applications User's Guide Performing

Query-by-Example and Query Count, Oracle Applications User's Guide
Viewing On-hand Quantities

Information about on-hand quantities for selected items includes project and task
references, nettable and non-nettable quantities, and subinventory locations. The values
that appear in the quantities and subinventory fields are based on the plan options.
Note: Project and task references are only on items with project specific
inventory.
To view on-hand quantities for a project:

1.
2.
Select one or more items.
3.
From the Tools menu, select On Hand to display the View On Hand Quantities
window.
For an item in an organization, the View On Hand Quantities window displays

quantities for each subinventory, whether the subinventory is nettable. This gives you a
more detailed picture of nettable and non-nettable quantities than the Items window,
which displays the sum of these quantities across all subinventories. In addition, the
View On Hand Quantities window displays project information, if an item has a
project/task on hand.
See Also
Overview of Project MRP

You can review supply and demand detail information for a plan, based on your
Preferences selection.
To review all supply and demand detail information for a plan

1.
2.
Select a plan name.
3.
Choose one of the following buttons to display the Supply/Demand window:
4.
In the Find Supply/Demand folder window, enter your search conditions.
5.
Choose Find.
6.
Review your supply/demand details. See: Supply and Demand Fields.
7.
Choose the Attachments toolbar icon to use the Attachments feature. See Working
with Attachments, Oracle Applications User's Guide.
8.
Save your work.
See Also
Supply/Demand Find Window
Online Planner
Net Change Replan
Searching for Information, Oracle Applications User's Guide Performing

Query-by-Example and Query Count, Oracle Applications User's Guide
Tools Menu
Supply and Demand Fields

Action
Recommendation from the planning engine for a specific record, such as Reschedule In,
Reschedule Out, Cancel, and Release.
Alternate BOM
Used for net change replanning.
Alternate Routing
BOM Item Type
Type of item, such as: Model, Option class, Planning Standard, and Product Family.
Build Sequence
Displays the build sequence used in releasing planned orders.
Category
Item category.
Compression Days
The number of days that the planning process suggests you compress the order, that is,
reduce the time between the start date and due date.
Days from Today
Displays demand or supply entries that are due within the specified number of days
from the current date.
Firm
Indicates if a supply order was firmed or not.
Implemented Quantity
The quantity of a supply order which has been implemented as a discrete job or
purchase requisition.
Item
The part number.
Last Unit Completion Date (LUCD)
For repetitive or aggregate repetitive schedules, this value is the the last unit completion
date. For repetitive demand, this value is the rate end date. This field name can be
changed to meet your requirements.
Last Unit Start Date (LUSD)
The last unit start date of a repetitive or aggregate repetitive schedule.
Line
New Date
The due date of a firmed supply order. This defaults to the suggested due date of the
order; however, you can manually override this value.
New Quantity
The order quantity of a firmed order. This defaults to the suggested quantity of the
order; however, you can manually override this value.
Old Due Date
The original due date of a rescheduled order.
Old Order Quantity
The original order quantity of a discrete job, repetitive schedule, or flow schedule.
Order Number
The order number of a purchase order, purchase requisition, discrete job, flow schedule,
or sales order.
Order Type
The order type of the supply or demand entry. The supply types are: Purchase order,
Purchase requisition, Discrete job, Suggested aggregate repetitive schedule, Flow
Schedule, Planned order, Non-standard job, PO in receiving, Intransit shipment,
Intransit receipt, Suggested repetitive schedule, Discrete job by-product, Nonstandard
job by-product, Repetitive schedule by-product, Planned order by-product, and
Payback Supply. The demand types are: Planned order, Non-standard job, Discrete job,
Flow Schedule, Repetitive schedule, Expired lot, Sales Order,, Forecast MDS, Manual
MDS, Other independent demand, Hard reservation, MDS independent demand, MPS
compiled demand, Copied schedule demand, Planned order scrap, Discrete job scrap,
Purchase order scrap, Purchase requisition scrap, PO in receiving scrap, Repetitive
schedule scrap, Model/option class/product family demand, Intransit shipment scrap,
Interorganization order, and Payback Demand.
Organization
The organization short code. Use this criteria to display supply or demand entries
within the specified organization.
Planner
The planner associated with an item. This criteria displays items or supply/demand
entries for items that belong to the specified planner.
Project Number
The project number associated with an order. Use this criteria to display
supply/demand associated with the specified project.
Quantity/Rate
The required quantity of a demand entry or the order quantity of a supply entry. For
repetitive demand, this field displays the daily demand quantity. For repetitive supply,
it displays the daily production rate.
Release Errors
Error messages associated with specific records not selected in the Select All for Release
processing.
Repetitive
Indicates if an item is repetitively planned. Use this criteria to display repetitive supply
or demand entries.
Rescheduled
Indicates if a supply order has been rescheduled.
Schedule Group
You can select a schedule group for a planned order and release.
Selected for Release
Indicates if a supply order has been selected for release.
Source Organization
Organization from which a specified supply order is sourced.
Source Supplier
The supplier associated with an item, used as the default for an order.
Source Supplier Site
The location of the source supplier.
Suggested Dock Date
Date that the planning process suggests the supply order is received.
Suggested Due Date
Supply: The date the planning process recommends the item should be available to use
in manufacturing. This is typically when you deliver the item to inventory. This is
calculated by adding any postprocessing lead times for the item to the new dock date.
Demand: The date the using assembly requires the item. If the demand is rate-based, the
start date of the rate of the demand is displayed.
Suggested Order Date
The date the planning process recommends to begin an order so it is completed by the
suggested due date, based on fixed and variable lead time.
Suggested Start Date
Start date of the supply order.
Task
The task number of an order. Use this criteria to display supply/demand associated
with the specified task.
Using Assembly
The parent assembly of an item.
Supplier
The supplier of a purchase order.
See Also

You can review bucketed horizontal planning data, based on your selected display
preferences.
Oracle Master MRP provides two different views of this data: snapshot and current.
Snapshot data is the data produced by your original planning run. Current data
includes all modifications since the planning run.
To review horizontal planning information
1.
2.
Check the item(s).
3.
Choose Horizontal Plan to display your Horizontal Plan window.
4.
Choose All Dates to specify the entire date range used to review supply/demand
detail information.
5.
Choose the Current button to view current supply/demand information; choose the
Snapshot button to view supply/demand information from the latest planning run.
6.
Optionally, choose one of the following buttons to display the Supply/Demand

window:
Supply Demand
Supply/Demand
Note: This is not available when reviewing current data.
7.
Review your supply/demand details. See: Supply and Demand Fields

See Also
Customizing the Presentation of Data in a Folder, Oracle Applications
User's Guide
Tools Menu

You can view a summary of supply and demand for an item, including sales orders,
forecast quantities, dependent and independent demand, expected scrap, gross
requirements, WIP, purchase orders, requisitions, in transit, in receiving, planned
orders, total supply, beginning on hand, and scheduled receipts. This window is
especially useful when you need to see all available supply for an item or a summary of
demand.
Supply Chain Planning users can display this information by organization. If you are in
an owning organization, you have access to all planned items across all planned
organizations in your specific plan. If you are in one of the planned organizations, you
have access to planned items in your own organization.
Enterprise View provides two different views of this data: current and snapshot. The
snapshot data is the data produced by your original planning run; the current data
includes all modifications made following the original run.
To review the enterprise view
1.
2.
Check the item(s).
3.
Choose Enterprise View to display your Enterprise View window.

Note: When you choose the Enterprise View button, the Enterprise
View window displays snapshot data; when you choose the

Current button, the window displays current data. You may toggle
between current and snapshot data.
4.
Choose the Current button to view current supply/demand information; choose the
Snapshot option button to view supply/demand information from the latest
planning run.
See Also
Customizing the Presentation of Data in a Folder, Oracle Applications User's

Guide
Tools Menu

You can view your supply and demand data as it was at the time of the last planning
run or as it is currently, including any changes you have made in the Planner
Workbench. The original data is called snapshot data; data including changes is called
current data.
From the Horizontal Plan and Enterprise View windows, you can view not only the
snapshot supply/demand information, but also the current status of supply/demand
while implementing planned orders at any time. You can navigate to Horizontal
Capacity Plan and view current data on resource requirements. It shows the current
capacity requirements from existing discrete jobs, repetitive schedules, flow schedules,
and unimplemented planned orders.
Note: Current data on resource requirements is not available in MPS
plans. Supply Chain Planning users can also compare snapshot and
current data from the Enterprise View window.
To review the snapshot or current supply and demand data

1.
2.
Check the item(s).
3.
Choose Horizontal Plan. You can also choose Enterprise View.
4.
Choose the Current option button to view current data; choose the Snapshot option
button to view snapshot data.
See Also
Generating a Graphical Display of Planning Data

You can view a graph of the current or snapshot supply/demand information of one or
more items. The graph contains all horizontal plan data for the selected item, rendered
in three charts:
total supply and demand detail
total supply detail
total demand detail
To generate a graphical display of planning data

1.
Navigate to the Resources window.
2.
Check the resource(s).
3.
Choose Horizontal Plan.
4.
Choose the Current option button to view current supply/demand information;

choose the Snapshot option button to view supply/demand information from the
latest planning run.
5.
Choose Graph.
See Also

Oracle MRP provides a range of exception messages for all plans.
You can easily manage your plan by displaying only those items and orders that require
your attention, and you can further narrow your search using other criteria such as by
buyer or by line. For each exception that matches your selection criteria, you can view a
summary of the exception and then drill down to pinpoint orders or items which
caused the exception(s). For these items or orders, you can view item information,
horizontal plan, and supply and demand. By saving the exception messages each time
you replan simulations, you can compare different versions of the same plan or analyze
the strengths and weaknesses of a single plan.
Note: You can only display detailed exception and item planning
information for exceptions generated by the current planning run.

Relaunching the plan from the Launch DRP/MPS/MRP window erases
all exceptions and only rebuilds the current version.
You can use the Planning Exception Messages workflow to route messages to personnel
such as planners, buyers, and suppliers. This allows you to automate the processing of
reviewing exceptions in order to identify potential conflicts before they become
problems.
To review a summary of exceptions

1.
Navigate to the Exception Summary window.

The Exception Summary window displays information about all exception
messages generated by the current planning run, along with all messages saved
from previous simulation runs.
2.
Optionally, enter and run a query to narrow down the list of exceptions.
The types of exceptions you might see are:
Items allocated across projects: items whose supply for one project has been
allocated to the demand of a different project
Items below safety stock: items for which demand, less supply, brings the
projected quantity on hand to a negative level or below safety stock
Items that are over-committed: items for which ATP is negative or below safety
stock
Items with a shortage: items whose quantity on hand is less than the sum of the
requirements plus safety stock, within the exception time fence defined by the
item's planning exception set
Items with a shortage in a project: items whose demand exceeds supply with a
project/task for an item Items with excess inventory: items whose quantity on
hand exceeds the total requirements against the item, within the exception time
fence defined by the item's planning exception set
Items with excess inventory in a project: items whose supply exceeds demand with
a project/task for an item
Items with expired lot: lots that expire within the planning horizon
3.
Items with negative starting on hand: items with a negative onhand beginning
balance
Items with no activity: items with no demand or supply in the current plan
Items with repetitive variance: items with suggested aggregate schedules that
differ from current aggregate schedules by more than a user-defined repetitive
variance percentage, up to the exception date defined by the item's planning
exception set
Late order due to resource shortage: items that will cause a late order because a
resource required to manufacture the item is overloaded
Late supply pegged to forecast: items with shortages that prevent forecast demand
from being met, caused by component shortages
Late supply pegged to sales order: items with shortages that prevent sales order
demand from being met, caused by component shortages
Orders to be cancelled: items with orders that the planning process recommends
be cancelled
Orders to be rescheduled in: items with orders that the planning process
recommends be rescheduled to an earlier date
Orders to be rescheduled out: items with orders that the planning process
recommends be rescheduled to a later date
Orders with compression days: items with planned orders, discrete jobs and
purchase orders that have compression days and need to be expedited
Past due forecast: items with a forecast demand due date earlier than the plan
start date
Past due orders: items with planned orders, discrete jobs and purchase orders
that are past due
Past due sales orders: items with a sales order due date earlier than the plan start
date Resource Overloaded: a resource is overloaded, as defined by the load ratio
entered in the exception set
Resource Underloaded: a resource is underloaded resources, as defined in load

ratio entered in the exception set
Scroll right, if necessary, to see values in the following fields:
Exception Count: the number of exceptions for the given exception type
Org: the organization in which this exception type occurred
Item: the item for which this exception type occurred
Category: the item category associated with items for which you see exceptions
Planner: the planner who is associated with the items for which you see
exceptions
Buyer: the buyer of the item for which this exception type occurred
Planning Group: the planning group, if any, that is associated with the items for
which you see exceptions; only appears if the exception occurred in a
project-related plan
Project: the project, if any, that is associated with the items for which you see
exceptions; only appears if the exception occurred in a project-related plan
Task: the specific project task, if any, that is associated with the items for which
you see exceptions; only appears if the exception occurred in a project-related
plan
Version: the version of the planning run for which this set of exceptions occurs;
the version number gets incremented each time you click Save Exceptions, even
if you do not make changes to the plan
Dept/Line: the department or production line for which this exception type
occurred
Resource: the resource for which this exception type occurred
Resource Type: The resource type for which this exception occurred
If nothing appears in one of these fields, there are likely multiple values for that
field. For example, if the Item field is blank, there may be multiple items for which
the exception occurred. To find out more, query exceptions by the above-mentioned
fields or look at the exception details for the exception type that interests you.
To review details about a particular exception type

1.
Navigate to the Exception Summary window.
2.
Click the box to the left of each exception type for which you want to see detailed
information. You can only check the current version of exceptions.
3.
Click the Exception Details button.
To display item information associated with your selected exception message

1.
Check the exceptions whose message details you want to display. You can only
check the current version of exceptions.
2.
Choose Items to display the Items window.

See: Reviewing Item Planning Information
To view resource information for your selected exception message

Choose Resource to display the Resource window.
See: Viewing Capacity Information from the Planner Workbench
To display the horizontal plan for your selected exception types

1.
Check the exceptions whose items you want to display in a horizontal plan. You
can only check the current version of exceptions.
2.
Choose Horizontal Plan to display the Horizontal Plan window.

See: Reviewing the Horizontal Plan.
To save all exception messages:

Choose Save Exceptions. All previously saved messages retain their current version
number. All current messages will be saved with the next version number ( n + 1 ),
where n is number assigned in the previous save.
See Also
Planning Exception Sets

Planning exception sets specify the sensitivity controls and exception time periods for
each exception message.
Since different sensitivity controls and exception time periods are appropriate for
different types of items, you can define as many planning exception sets as you need.
Assign the appropriate exception set to each item when you define or update the item.
Sensitivity controls that quantify excess and repetitive variance exceptions are:
excess quantity
repetitive variance percentage
resource underloaded
resource overloaded
user-defined time fence (in days)
Exception time period types that define the time period for overcommitted, shortage,
excess, and repetitive variance exceptions are:
cumulative manufacturing lead time
cumulative total lead time
planning time fence
total lead time
user-defined time fence
If you choose to use a user-defined time fence, you must define the number of days that
this time fence corresponds to.
See Also
Overview of Net Change Replan

You can use Planner Workbench to replan manual changes to specific orders and
available resources, the addition of new supply and demand records, and all items
affected by those changes. Net Change Replan is a powerful "what-if" analysis feature
that allows you to update a material plan by planning just the items you have changed
in the Planner Workbench. The replanning is based on the snapshot data gathered
during the original planning run and the changes you have made with the Planner
Workbench. No other transactions, such as receipts in Oracle Inventory, are considered
in the replanning process. You also have the ability to implement the changes
recommended by net change replan.
You can prepare a modified plan by: adding firm planned orders
adding new demand
modifying due dates or quantities of existing demand entries or firm planned

orders
modifying due dates of work orders or purchase orders
firming or unfirming existing work orders and purchase orders
cancelling existing work orders and purchase orders
modifying capacity for a specific resource
modifying alternate BOM and alternate designators for firm planned orders
Note: You cannot replan changes to supply for repetitive items. Items
planned in MPS are not replanned in MRP.
Replanning is based on the snapshot data gathered during the original planning run,
including item, bill of material, resource availability, and sourcing information (if you
are a Supply Chain Planning user). Because the replan does not update this information
with new transactions, you can maintain sets of alternative scenarios, examine the
effects of different changes and implement the changes that best meet your business
requirements.
Note: Until you release your order or schedule, Net Change Replan will
change the item status back to that in effect at the last planning run. It
will also base any new recommendations on the original snapshot data.
Net Change
Replan will correctly replan changes to items only after the items have been released.
Net Change Replan does not consider the transactions that have occurred in the
execution system (including the planned orders released for the plan in question). It
reuses the snapshot of the prior run. Rerun the snapshot to include these changes.
Batch Mode Planner

Batch mode allows you to communicate directly with the database while making and
replanning your changes. While frequent replanning can place an excessive load on
system resources, batch mode gives other users access to the plan while you are
performing simulations. Batch mode is particularly useful when you want to complete a
single replanning cycle.
Online Planner
The online planner allows you to simulate and replan manual changes to supply,
demand, and available resource records without increasing database traffic. Starting an
online session loads all planning data into memory, afterwards, you can make changes
to that data, then replan the changes to see their effect on the rest of the plan. You can
implement and release your changes from within the session, or you can make changes
and replan as many times as necessary before the release.
As a simulation tool, the online planner quickly allows you to see the effect of the
changes you make in the Planner Workbench. As an implementation tool, it reduces
unnecessary database transactions and offers rapid plan revision and execution. As a
monitoring tool, it generates the full set of exception messages following a replan - it
also allows you to save the exceptions generated by previous sessions, offering you
feedback on successive planning decisions.
The online planner is particularly useful when performing frequent simulation on a
single plan. In online mode, you can do this without suffering a significant loss in
performance.
However, there are three restrictions to using the online planner. You cannot make
changes to either item attributes or plan options, the online planner will not evaluate
capacity constraints, and it will lock all other users out of the plan while the session is
active.
See Also
Replanning Net Changes - Batch Mode Planner
Net Changes - Online Planner
Creating Firm Planned Orders:
Adding Plan Options

To replan net changes in batch mode
1.
2.
Select a plan name.
3.
Choose Supply/Demand to display the Supply/Demand window.
4.
Make your changes in the Supply/Demand window.
5.
Save your changes.
6.
In the Planner Workbench window, choose Batch in the Net Change Replan region,
then choose Plan.
Note: The net change replanning process clears all information in
the Planner Workbench window.
7.
Keep a record of the Request ID displayed in the Note window.
8.
Choose OK.
9.
Verify that the net change replanning process has completed. See: Using the
Concurrent Requests Windows, Oracle Applications User's Guide.
10. Re-query the plan to review your changes.

11. If you are not satisfied with the replan results, repeat Steps 2-7 as needed.
To implement and release your modified plan:

See: Implementing Planning Recommendations
See Also
Replanning Net Changes - Online Planner
Overview of Graphical Pegging
Overview of Memory-based Planning Engine
Adding Plan Options
Replanning Net Changes-Online Planner

To start an online planner session: Navigate to the Planner Workbench window. Select a
plan name. Choose Online in the Net Change Replan region and choose Start. Choose
OK to acknowledge that starting this session will prohibit access to the plan by other
users. Make a note of the concurrent request ID and choose OK.
While the online planner loads the data into memory, you will see the Online Planner
Status window. This window displays the progress of the loading and signals you when
the session is ready for planning.
When the status window informs you that the session is ready for planning, close the
window to return to the Planner Workbench.
Your online planner session is now active.
To replan your changes with the online planner

1.
Start your online planner session, as described above.
2.
Navigate to either the Supply/Demand window or the Available Resources

window, whichever is appropriate.
3.
Make your changes in the window.
4.
Save your changes.
5.
In the Planner Workbench window, choose Online in the Net Change Replan
region, then choose Plan.
Note: The online planner will clear and lock all other windows
during the replanning process.
To check the status of an online planner session

1.
region, then choose Status. The online planner will display one of the following
status messages:
Concurrent Request [concurrent request number] pending Loading Data Ready for
Planning, Planning Complete
Loading Data Ready for Planning Planning Complete
To implement and release your modified plan

See: Implementing Planning Recommendations.
To stop an online planner session

1.
region, then choose Stop.
2.
Choose OK to confirm that you want to end your online planner session.
Note: The Net Change Replan region is not yet ready to start a new
batch mode or online planner session. Choose Status to display the

Online Planner Status window. Confirm that the status is Complete and
close the window. You can now start another online planner session, or
start the batch mode planner
To view and interpret online planner results

1.
Navigate to either the Supply/Demand window or the Available Resources

window, whichever is appropriate.
2.
When you first make changes in the window, the changed values are highlighted in
the color pink. After following the procedure for replanning, all changes created by
the online planner are now highlighted in the color blue.
If you make other changes in this replan session, those new changes are highlighted
in pink in the window.
See Also
Overview of Memory-based Planning Engine
Adding Plan Options

You can use the graphical pegging feature to analyze the impact of changing a supply
or demand order at any level of your bill of material. Full pegging traces supply
information for an item to its corresponding end demand details. Full pegging can also
link a demand order to all corresponding supply.
To use graphical pegging, you must enable the Memory-based Planning Engine in your
plan or schedule and select Pegging in the Plan Options window.
Supply information includes:
work orders
purchase orders
planned orders
safety stock
Demand information includes:
sales orders
forecasts
manual master demand schedules

Note: Since planned orders are pegged to top level demand (a project
or contract), resulting work orders and purchase orders are easily

associated to the project or contract.
In graphical pegging, supply information is pegged to all higher level demands, up to

and including the top level assembly. In single level pegging, supply information is
pegged only to the demand at the next higher level.
Suggestion: You can trace a purchased item or subassembly shortage to the sales order
that would be affected. You can use this information to prioritize critical material and
capacity resources.
See Also
Viewing Pegged Supply and Demand
Replanning Net Changes
Viewing Pegged Supply and Demand Prerequisites

1.
You must have Pegging selected as a plan option. See: Reviewing or Adding Plan
Options.
2.
You must have the Pegging item attribute (in Oracle Inventory) set to one of the
following options:
Soft Pegging
End Assembly Pegging
End Assembly/Soft Pegging

If you are working in a project environment, you may also have the Pegging
item attribute set to one of the following options:
Hard Pegging
End Assembly/Hard Pegging

See: MPS/MRP Planning Attribute Group, Oracle Inventory User's Guide.
To view pegged supply information

1.
2.
Select a plan name.
3.
Choose Supply/Demand to display the Supply/Demand window.
4.
In the Find Supply/Demand folder window, enter your search conditions. See:
Using Query Find, Oracle Applications User's Guide, Using Query Operators, Oracle
Applications User's Guide, and Customizing the Presentation of Data in a Folder,
Oracle Applications User's Guide.
5.
Choose Find.
6.
In the Supply/Demand window, select a demand order (indicated by a negative

quantity) to reveal its pegged supply.
7.
Choose Pegging to open the Object Navigator window for a graphical display of
supply/demand relationships for an item.
The nodes are color-coded for easy identification, and other aspects of the data flow
can be changed to meet specific requirements.
To view pegged demand information

1.
Navigate to the Supply/Demand window.
2.
In the Supply/Demand window, select a supply order (indicated by a positive

quantity) to reveal its source of demand.
3.
Choose Pegging to open the Object Navigator window for a graphical display of
supply/demand relationships for an item.
See Also
You can monitor and coordinate customer delivery promises using the available to
promise information in the Horizontal Plan window and Planning Detail report. The
planning process calculates ATP based on the Calculate ATP item attribute. See:
MPS/MRP Planning Attribute Group, Oracle Inventory User's Guide.
ATP is based on a specific MPS, DRP or MRP plan and is non-cumulative. Changes to
on-hand quantities, scheduled receipts, and demands made after the planning process
is completed are not reflected in ATP until the next time the material plan is executed.
Note: Any ATP calculation done through Oracle MRP does not consider
the ATP rules you define in Oracle Inventory. For instructions on

viewing or calculating ATP through Oracle Inventory, see: Viewing
ATP Information, Oracle Inventory User's Guide.
Calculating ATP
Oracle MRP calculates the ATP quantity of an item for each day of planned production
by adding planned production during the period (planned orders and scheduled
receipts) to the quantity on hand, and then subtracting all committed demand for the
period (sales orders, component demand from planned orders, discrete jobs, flow
schedules, and repetitive schedules).
Note: Committed demand does not include forecasted demand or
manually entered master demand schedule entries. Also, the amount

available during each period is not cumulative. Oracle MRP does not
consider ATP quantities from prior periods as supply in future periods.
The Available to Promise formula is:

ATP = on hand + supply - demand
where:
on hand = nettable quantity on hand
supply = planned orders, scheduled receipts (purchase orders, purchase requisitions,
flow schedules, discrete jobs, and suggested repetitive schedules).
demand = sales orders, component demand (from planned orders, discrete jobs, flow
schedules, and suggested repetitive schedules); excludes forecasted demand or manual
entries
Calculating ATP for Product Family Items

An ATP calculation can be performed at either the product family item level or the
member item level. An ATP calculation for the product family item takes into account
demand for member items.
Depending on the ATP rule specified in Oracle Inventory, the ATP formula for a
member item is:
ATP (member item) = MPS (member item) - SO (member item) + WIP jobs (member
item) + PO (member item) + On-hand (member item) The ATP formula for a product
family item is:
ATP (member item) = MPS (product family) - SO (all members) + all demand entries
specified in the ATP rule for all members
Notice that the ATP calculation for a product family item does not consider supply for
member items.
For example, consider a product family item, PF, consisting of member items I1 and I2.
The planning percentages are:
I1: 40%
I2: 60%
Also assume that PF has Forecast Control set to Consume, and I1 and I2 both have
Forecast Control set to Consume and derive.
Now assume the following forecast and sales order:
Forecast: PF (F) 100
Sales Order: I1 (SO) 10 After explosion and consumption, the forecast looks like
this:
Forecast: PF (F) 90
Forecast: I1 (F) 30
Forecast: I2 (F) 60
After loading the forecast and sales order to an MDS, the schedule looks like this:
Schedule: PF (F) 90
Schedule: PF (SO) 10
Schedule: I1 (F) 30
Schedule: I1 (SO) 10
Schedule: I2 (F) 60 The production plan looks like this:
Plan: PF (F) 90
Plan: PF (SO) 10
Plan: I1 (F) 30
Plan: I1 (SO) 10
Plan: I2 (F) 60
The ATP calculation based on this plan looks like this:
ATP: I1 (PF): 100 - 10 = 90 (I1): 40 - 10 + 0 = 30
ATP: I2 (PF): 100 - 10 = 90 (I2): 60 - 0 + 0 = 60
Negative ATP
If ATP goes negative in a period, it rolls backwards to find ATP from a previous period
to cover the demand.
Consider the following simple example:
Type
Beg. Inventory
Period 1
Period 2
Period 3
Period 4
Sales Order
100
300
Schedule Receipt
300
200
ATP (before
adjustment)
200
-100
ATP
100
The available to promise for period 1 is calculated by subtracting the sales order
demand (100) from scheduled receipts (300) giving ATP (200). In period 2, however,
when subtracting sales orders (300) from scheduled receipts (200), the initial result is
negative ATP (-100). Oracle MRP borrows available ATP from the previous period to
compensate for the negative quantity.
Inventory Snapshot
Oracle MRP bases ATP information on the:
snapshot of inventory on hand
scheduled receipts
master schedule entries taken during the latest MPS, DRP or MRP plan
Suggestion: You should re-plan the master schedule or material requirements to get the
latest ATP information.
Choose whether to display ATP information for an item in the Horizontal Plan window
and on the Planning Detail report with the ATP calculation option. Set this option when
you define an item.
See Also
Supply Chain ATP
Capable to Promise
Supply Chain ATP
Snapshot
Product Families, Oracle Bills of Material User's Guide
Supply Chain ATP

Supply Chain Available to Promise (ATP) enables you to view detailed availability
information from Oracle Inventory or Oracle Order Management for an order line, ship
set, or configuration in order to choose which supply source you want to use to meet
the demand. You can perform Supply Chain ATP with or without a customer reference.
In both procedures you set up sourcing rules or bills of distribution specifying the
percentages of each source - and then you create assignment sets.
For example, one sourcing rule, West-2, might specify that the SAC organization should
be the supply source 60% of the time and the AUS organization should be the supply
source 40% of the time.

Then you can create an assignment set in which one of the entries specifies that
Customer 1 at Customer site 1A takes sourcing rule West-2 for item A0007 from SAC,
and another entry specifies that Customer 1 at Customer site 1B takes sourcing rule
West-1 for all items from AUS.
Lead time data between different supply sources and different customer locations is
entered in Oracle Inventory windows. For example, you might specify that the lead
time between SAC and Customer site 1A using Ground transportation is 2 days,
whereas the lead time between AUS and Customer site 1A using Ground transportation
is 3 days.
When you perform an ATP query from Inventory or Order Management, the program
shows all possible sources of supply, using the sourcing information you entered
earlier. (When more than one sourcing rule seems to apply, the sourcing hierarchy
determines which sourcing rule to use.) Supply Chain ATP also calculates the receipt
date from each possibly supply source, using the intransit lead times specified in Oracle
Inventory. In calculating the receipt date, the program uses the calendar of the source
organization.
After you see the different receipt dates, you can choose which supply source you want
to use for each order line, ship set, or configuration.
Capable to Promise
Capable to Promise (CTP) extends Available to Promise by taking into account capacity
information. Whereas ATP only considers material availability and assumes infinite
capacity resources, CTP considers availability of both materials and capacity, giving a
more realistic picture of whether demand can be satisfied within a given time fence.
You can enable the Capable to Promise feature by setting the INV:Capable to Promise
profile option to Enable Product Family ATP and CTP. See: Oracle Inventory Profile
Options, Oracle Inventory User's Guide.
CTP calculations take longer than ordinary ATP calculations, and in some cases you
may not want to spend the extra time considering capacity resources. Therefore, you
can choose at the item level whether you want to check only materials, only capacity
resources, or both in the ATP calculation. To do this, set the Check ATP item attribute in
the Order Management attribute group. See: Order Management Attribute Group,
Oracle Inventory User's Guide.
If you want an ATP calculation on the item to consider resources, you must also define
a CTP routing for the item and check the Capable to Promise check box in the Routing
form. (The CTP calculation only takes into account demand placed on resources by
items whose routings have the Capable to Promise flagged on.) See: Creating a Routing,
Oracle Bills of Material User's Guide. In addition, you must specify by department which
resources should be used in CTP calculations. See: Defining a Department, Oracle Bills of
The ATP Rule can also be associated with a department and resource combination. This
is set in the Oracle Bills of Materials Resource window, or a line as set in the Oracle
Work In Process Production Lines window.
The following settings apply to the CTP function:
The CTP check is based on the ATP rule assigned to the Department/Resource
combination.
The ATP settings of Resource Only, and Material and Resource are allowed only for
ATO (Assembled to Order) models, option classes, and items.
Only one CTP routing is allowed for an item/organization combination.
A value is required for Past Due Demand/Supply Time Fence on an ATP Rule
associated with a Resource. It is recommended that Past Due Supply is set to zero,
since resource supply cannot be accumulated.
A CTP calculation checks availability of components only for assemble-to-order items

(ATO), not standard items. Furthermore, it only checks availability of components if the
ATP components item attribute in the Order Management attribute group is flagged on.
For example, assume item A is a model whose components are items B and C. Suppose
that quantity-on-hand for item A is 0. If you do an ATP check that only considers
materials, the ATP quantity will be 0. If you do a CTP check (that is, an ATP check that
considers both materials and resources), and the Check components item attribute is
turned on for item A, the application will check the availability of items B and C and
will check the resources necessary to make item A to determine how many of item A
can be made. In addition, it will check the resources and materials necessary to make
more of items B and C, to make more of item A, and will report the total in the CTP
calculation. Thus, a CTP calculation that considers both materials and resources might
show a greater ATP quantity than a calculation that only checks materials, particularly
when the item being checked is an assemble-to-order item.
To perform a CTP calculation, see: Viewing ATP Information, Oracle Inventory User's
Guide.
See Also
Oracle Inventory Profile Options, Oracle Inventory User's Guide.
Order Management Attribute Group, Oracle Inventory User's Guide
Creating a Routing, Oracle Bills of Material User's Guide
Defining a Department, Oracle Bills of Material User's Guide
Viewing ATP Information, Oracle Inventory User's Guide.
Item Attributes Used in Order Management, Oracle Order Management User's Guide.
Sales Order Scheduling, Oracle Order Management User's Guide.
Implementing Planning Recommendations

Overview of Implementing Planning Recommendations
After you have reviewed your material plans, you are ready to release the planning
recommendations. You can:
modify recommended due dates and quantities
add firm planned orders for DRP, MRP or MPS items
release planned orders as purchase requisitions, discrete jobs, or flow schedules
release repetitive schedules
release orders
firm planned orders and release planned orders
reschedule scheduled receipts
Alternatively, you can enable the planning process to automatically release planned
orders, without modification to dates and quantities or implementation details.
However, you must manually implement and release repetitive schedules. See:
Auto-release Planned Orders.
Note: You cannot release kanban items. These items have item attribute
Release Time Fence set to Do Not Release (Kanban) in Oracle Inventory.

The planning process will generate planned orders against these items,
but you will not be able to release them into Purchasing or Work in
Process.
A warning message displays informing you when releasing MPS
planned order in MRP
See Also
Implementing Planned Order
Online Planner
Net Change Replan

You can firm the planned orders to stabilize portions of the material plan. You can also
add firm planned orders to the plan manually. When you launch the planning process,
you can choose not to overwrite firm planned orders.
Firming a planned order does not firm the job in Oracle Work in Process. Firming a
planned order only prevents the planning process suggesting changes. See:
Implementing Planned Orders as Firm.
To firm a planned order:

1.
2.
Check the item you want to firm.

Note: You can create firm planned orders for discrete parts and
repetitive schedules only. You cannot firm purchase orders.
3.
Check Firm and, optionally, update the firm date and firm quantity.
4.
Save your work.
To manually add a firm planned order

You can add firm planned orders for DRP-planned, MRP-planned, or MPS-planned
items.
1.
2.
Select New Record from the Edit Menu.
3.
Enter an item and organization.

Note: You can add firm planned orders for discrete parts and
repetitive schedules only. You cannot firm purchase orders
4.
Enter an order type (either Planned Order or Manual MDS).

The Action field is set to Release and the Firm check box is checked automatically.
5.
Enter the firm date and firm quantity.
6.
Check Firm and, optionally, update the firm date and firm quantity.
7.
Optionally, enter a source organization and source supplier.
8.
Optionally, enter the alternate BOM designator and alternate routing designator.
9.
Save your work.

Note: If the item exists in a supply schedule that derives this plan, you
will not be able to add firm planned orders for it.
See Also
Firm Order Planning
Implementing Planned Orders as Firm Jobs
Online Planner
Net Change Replan

You can easily load suggested planned orders into Oracle Work in Process or Oracle
Purchasing from the Planner Workbench to create discrete jobs and purchase
requisitions.
However, you cannot release kanban items. These items have the item attribute Release
Time Fence set to Do Not Release (Kanban) in Oracle Inventory. The planning process will
generate planned orders against these items, but you will not be able to release them
into purchasing or work in process.
Note: You can specify that planned orders be automatically released as
WIP jobs or purchase requisitions. See: Auto-release Planned Orders.
The order type depends upon the Make or Buy item attribute. If an item is defined as
Make, but can be purchased, you can release it as a purchase requisition or a discrete
job. In addition, Supply Chain Planning users can determine the Make/Buy item
attribute with sourcing rules and bills of distribution. For more information, refer to
You can load discrete jobs as firmed and/or released and can view current discrete job
information.
To release a single planned order

1.
2.
Optionally, override the default job class or requisition load group by opening the
Preferences window from the Tools menu.
3.
Check Release in the item row.
4.
In the Implement As column, select:

Discrete Job: Only if the Build in WIP item attribute is Yes. This excludes the
WIP:View Only Released ECOs profile option. This is the default when the Make
or Buy item attribute is Make.
None: Do not release the planned order. This is the default when the planned order
has been fully implemented.
Purchase Requisition: Only if the Purchasable item attribute is Yes.
This is the default when the Make or Buy item attribute is Buy.
Note: You can automatically create releases at the same time you
create requisitions. Set the profile PO:Release During ReqImport

to create releases each time you run the Requisition Import process.
Releases for all blanket-sourced, approved requisitions are
automatically created (and optionally approved).
The Req Import program will be run specific to the operating unit
tied with your responsibility. You may need to run Req Import for
different operating units base on your needs.
5.
Navigate to the Supply/Demand window to change the released quantity.

Note: The schedule group, build sequence, alternate BOM, alternate
routing, and demand class can only be updated for planned orders
being released as discrete jobs or discrete jobs being rescheduled.
The schedule group has a list of values which lists all schedule
groups from WIP for the organization in the supply record. The
build sequence is a number and can only be updated when
schedule group is entered.
6.
Optionally specify line, alternate BOM designator and alternate routing designator.
If you are using Project MRP, optionally specify project and task. For a purchase
requisition, source organization, source supplier, or source supplier site, implement
a discrete job as firm by setting the firm flag.
7.
Save your work.
8.
Choose Release to open the Release window.
9.
Review summary information based on new orders, new schedules, new

requisitions, and changes to existing data.
10. Choose OK.
To release all planned orders and reschedules

1.
2.
Choose Select All for Release, or check Release for each planned order.
During Select All for Release processing, records are posted to the database for
server side processing. After processing is complete, records are automatically
required in the Supply/Demand window. All messages, both error and successful,
are tied to individual records and are displayed in a new field called Release Errors.
Records with error messages are highlighted. You can fix the records with errors
and resubmit them for processing.
3.
Complete Steps 3-6 above, to release a single planned order.
Error Message Processing

Records not selected for release can have one or more error messages associated with
them. Three examples of error messages are listed here:
User name not associated with employee.
Location not entered, default location does not exist.
Implement date must lie on a valid calendar workday.
To take corrective action on error messages

1.
Navigate to the Planner's Workbench window.
2.
From here navigate to the windows or fields that need to be changed or updated
with new information.

For example, if the error message is Location is Missing, you can navigate to the
Release window and select a location.
3.
Save your work.
4.
Choose Select All For Release processing again to process the records.
5.
You can also delete the error message associated with the record after correcting the
error condition.
To delete error messages

1.
After taking corrective action for a record, navigate to the Supply/Demand window.
2.
Delete the error message associated with the record in the Release Errors field.
For example, if the error message is Location is Missing and you corrected the error
by selecting a location on the Release window - you can now delete this message.
3.
Save your work.
4.
Check Release in the item row and complete the steps to release a single planned
order.
See Also
Implementing Repetitive
Online Planner
Net Change Replan
Auto-release Planned Orders

You can modify and/or implement repetitive schedules. Oracle MRP suggests repetitive
schedules by line and divides production according to line priorities established in
Oracle Work in Process.
Before releasing, you can modify the first and last unit completion dates, daily quantity,
processing days, and total quantity of repetitive schedules. These values are
automatically recalculated as you individually change them.
For example, if the daily quantity is currently 10 and processing days is currently 2 and
you change processing days from 2 to 4, the total quantity is automatically updated
from 20 to 40.
To implement repetitive schedules
1.
2.
Check Item.
Note: You can implement repetitive schedules as firm using the
Planner Workbench.
3.
Check Selected to Release in the item row.
4.
Review the implemented date and implemented quantity and change as necessary.
5.
Optionally, override the default job class or requisition load group by opening the
Preferences window from the Tools menu.
6.
In the Implement As column, select Repetitive Schedule.

Note: You can automatically create releases at the same time you
create requisitions. Set the profile PO: Release During ReqImport

to create releases each time you run the Requisition Import process.
Releases for all blanket-sourced, approved requisitions are
automatically created (and optionally approved)
Navigate to the Supply/Demand window to change the released quantity.

The schedule group and build sequence fields can only be updated for planned
orders being released as discrete jobs or discrete jobs being rescheduled. The
schedule group has a list of values which lists all schedule groups from WIP for the
organization in the supply record. The build sequence is a number and can only be
updated when schedule group is entered.
7.
Save your work.
See Also
Implementing Planned Orders as Firm Jobs:
Online Planner
Net Change Replan

You can implement a planned order as a firm discrete job, repetitive schedule, or flow
schedule. When you release the order, it will appear as a firm discrete job in Oracle
Work in Process. When these jobs or schedules are loaded in to work in process, the
planning process treats them as firm scheduled receipts.
Implementing a planned order as firm does not stabilize the item in the material plan.
The planning process will continue to make rescheduling suggestions in future runs
until the order is released and becomes a firm scheduled receipt. Likewise,
implementing planned orders as firm jobs does not prevent the planning process from
rescheduling those items until they are loaded into work in process and become firm
scheduled receipts.
The following list describes firming behavior:
Firm a planned order: the planning process will not reschedule the planned order.
Implement a planned order as a firm job: the planning process will reschedule the
planned order.
Release an order for a job that has been implemented as firm: the planning process
will treat the job as a firm scheduled receipt and will not reschedule the order.
Therefore, to prevent the planning process from making rescheduling suggestions, you
must either firm the planned order or release a planned order that has been
implemented as firm. See: Creating Firm Planned Orders.
To implement a planned order as a firm job or schedule

1.
2.
If you are creating a planned order manually, enter the firm date and firm quantity.
3.
Check Select to Release in the item row.
4.
Review the implemented date and implemented quantity and change as necessary.
5.
Optionally, override the default job class by opening the Preferences window from
the Tools menu.
6.
In the Implement As column, select:

Discrete Job: Only if the Build in WIP item attribute is Yes. This excludes the WIP:
View Only Released ECOs profile option. This is the default when the Make or
Buy item attribute is Make.
None: Do not implement the planned order. This is the default when the planned
order has been fully implemented.
Purchase Requisition: Only if the Purchasable item attribute is Yes. This is the default
when the Make or Buy item attribute is Buy.
7.
Choose Release.
8.
In the Release window, choose OK>

Navigate to the Supply/Demand window to change the released quantity. You
cannot firm implemented orders for purchase requisitions or repetitive schedules.
Note: The schedule group and build sequence fields can only be
updated for planned orders being implemented as discrete jobs or

discrete jobs being rescheduled. The schedule group has a list of
values which lists all schedule groups from WIP for the
organization in the supply record. The build sequence is a number
and can only be updated when schedule group is entered.
9.
Save your work.
See Also
Firm Order Planning
Online Planner
Net Change Replan
How Purchase Requisitions are Created

When you create purchase requisitions using the Planner Workbench, purchase
requisitions are created according to your MRP:Requisition Load Group Option. You
can override the default load group and apply them to selected planned orders by
choosing preferences from the Tools menu.
Note: Firm, reschedule, or cancel purchase orders in Oracle Purchasing.
These functions are not available in the Planner Workbench
See Also
Tools Menu
Profile Options

After you review planning recommendations, you can reschedule or cancel discrete jobs
defined in Oracle Work in Process and reschedule purchase requisitions defined in
Oracle Purchasing. Planning recommendations include:
reschedule in
reschedule out
cancel
Before rescheduling, you can modify dates and quantities of scheduled

receipts and firm discrete jobs in Oracle Work in Process.
Note: You cannot cancel purchase requisitions, orders, or work in
process jobs using the Planner Workbench. You must perform these
functions in Oracle Purchasing or Oracle Work in Process. Cancel
purchase requisitions using the Control Requisitions window. Firm or
reschedule purchase orders using the Purchase Orders window. Cancel
purchase orders using the Control Purchase Orders window.
To reschedule scheduled receipts

1.
2.
Check an Item.
3.
Check Selected to Release.
See Also
Online Planner
Net Change Replan
Document Control, Oracle Purchasing User's Guide Purchase Orders, Oracle

Purchasing User's Guide
Walking Up and Down a Bill of Material

Overview of Bill of Material Review
You can move up and down the bill of material and review planning information for
the components and using assemblies of the item being planned.
Supply Chain Planning users can also review source and destination organizations for
the item being planned. See: Reviewing Source and Destination Organizations.
See Also

You can walk up and down the bill of material and display effectivity and quantity,
use-up information, and item details for the components of the item.
To review component attributes for your selected item
1.
2.
Check the item(s).
3.
Choose Components to display the Components window.
4.

Effectivity and Quantity, Use Up Information, and Item Details
Note: Alternate BOM information is available on the Components
window.
To review supply and demand information for components

1.

Supply, Demand, Supply/Demand
2.

See Also

End assembly pegging ties specific items in the MPS, DRP or MRP plan, identifying the
using assemblies and end assemblies that created the demand for the item.
When you define the item, you can specify whether Oracle MRP computes and displays
end assembly pegging information on the (Supply Chain) Planning Detail Report.
See Also

You can walk up and down the bill of material and display effectivity and quantity,
use-up information, and item details for the using assemblies of the item.
To review using assembly attributes of the selected item
1.
2.
Check the item(s).
3.
Choose Where Used to display the Where Used window.
4.
Choose an alternative region:

Effectivity and Quantity
Use Up Information
Item Details
Note: Alternate BOM information is available on the Components
window
To review supply and demand details for using assemblies

1.

Supply, Demand, Supply/Demand
2.

See Also

To review end assemblies of the selected item:
1.
2.
Check the item(s).
3.
Choose End Assemblies to display the End Assemblies window.
See Also
Capacity Planning
Overview of Online Capacity Planning
Online capacity planning enables you to generate a material and a capacity plan
simultaneously. You can analyze and maintain material and capacity plans from the
same Planner Workbench. You can get immediate information about whether your
material requirements plan is realistic given your capacity constraints. You can also
identify capacity problems - overload or underload - and make changes to balance
capacity requirements with material requirements. Finally, you can run what-if
simulations to see the effects of changing part of your material or capacity plan before
you implement it.
Capacity Requirements Planning

CRP verifies that you have sufficient capacity available to meet the capacity
requirements for your MRP plans. It is a shorter term capacity planning tool than rough
cut capacity planning (RCCP) - but it is also used to balance required and available
capacity, and to negotiate changes to the master schedule and/or capacity requirements.
CRP is a more detailed capacity planning tool than rough cut capacity planning in that
it considers scheduled receipts and on-hand inventory quantities when calculating
capacity requirements.
As with RCCP, you can perform detailed capacity planning at either the resource level,
routing-based, or production line level, rate-based.
See Also
Overview of Capacity Requirements Planning, Oracle Capacity User's Guide
Routing-Based CRP, Oracle Capacity User's Guide
Rate-Based CRP, Oracle Capacity User's Guide
Generating CRP, Oracle Capacity User's Guide
Viewing Capacity Information from the Planner Workbench

You can use the Planner Workbench to view capacity information for a plan, as long as
you have Oracle Capacity installed.
Note: Depending on your setup, capacity information calculated might
include line requirements for discrete jobs and planned orders.
Prerequisites
Before you can view capacity information from the Planner Workbench, you must:
To indicate that you want to plan both materials and capacity, check the Plan Capacity
check box in the Plan Options window before you run the plan. If the plan is an MPS
plan, also assign a Bill of Resource to at least one organization. See: Reviewing or
Adding Plan Options.
Note: The Plan Capacity flag is enabled only when CRP is installed.
Launch the plan.
To view capacity information

1.
Navigate to the Resources window from the Planner Workbench.
2.
Scroll right, if necessary, to see values in the following fields:

Dept/Line: specifies whether the resource is a department or a production line
Resource: the name of the resource
Org:the organization to which the resource belongs; this field only appears if you're
looking at a multi-org plan

Owning Dept:the department that owns the resource
Dept Class:the department class associated with the department
Resource Type:the type of resource, such as person, machine, and so on
Resource Group:the group to which the resource belongs
Min Rate:the minimum hourly rate for a production line
Max Rate: the maximum hourly rate for a production line
To view resource requirements for a particular resource

1.
Navigate to the Resource window.
2.
Select the resource or resources for which you want to see detailed information.
3.
Choose Requirements. The Resource Requirements window appears.
4.
Look at the values in the following fields:

Start Date: the beginning date that the department and resource are required
End Date: the ending date that the department and resource are required
Required Hours: the total number of hours required by a repetitive schedule, or the
number of hours required by a discrete job or planned order
Schedule Quantity: for discretely manufactured items, the quantity of the item
scheduled for the date; for repetitively manufactured items, the total quantity of the
item on the schedule
Using Assembly: the assembly that is the source of the demand
Daily Quantity: the daily production rate for the repetitive schedule, effective from
the schedule start date to the schedule end date
Order Number: the order number that is the source of the demand Order Type: the
type of order that is the source of the demand: Discrete job, Non-standard job,
Planned order, Repetitive Schedule, or Flow Schedule.
Source Item: the item that generates the resource requirement
Op Seq: the operation sequence associated with the department and resource
Daily Hours: the number of hours required by a discrete job or planned order
Schedule Start Date: the start date of the demand
Rate End Date: the date on which the repetitive production rate ends
Load Rate: the load rate for the repetitive schedule; the load rate is the daily quantity
multiplied by the load factor, which is the maximum hourly rate divided by the
production rate for a given repetitive assembly and production line
To view available capacity for a particular resource

1.
2.
Select the resource for which you want to see available capacity.
3.
Choose Availability.
The Resource Availability window appears.
4.
Look at the values in the following fields:

From Date: the beginning date that the department and resource are available
To Date: the ending date that the department and resource are available
Max Rate: the maximum hourly rate for a production line
Capacity Units: number of units of a resource available in a department.
Daily Capacity: the number of hours available per day per resource
Identifying Capacity Problems

By viewing capacity information directly from the Planner Workbench, you can identify
capacity problems right away.
To view the load ratio for a resource
1.
2.
Click the check box next to each resource you want to check.
3.
Click the Horizontal Capacity Plan button. The Horizontal Plan window appears.
4.
In the Type column, look for Capacity Load Ratio. Then read across to see what
percentage of capacity is utilized for each time period.
5.
In the Type column, look for Cum capacity load ratio. Then read across to see what
percentage of capacity is utilized overall.
Note: The Type column only displays information that you've
specified in the Preferences for Planner Workbench. If the

information you're looking for does not appear, choose Preferences
from the Tools menu and, in the window that appears, choose
Horizontal Capacity Plan form the pop-up menu and check
Capacity Load Ratio and Cumulative Capacity Load Ratio in both

the Routing Based and Rate Based columns.
To raise an exception whenever a capacity load ratio problem occurs in a

planning run
1.
Define an exception set, specifying sensitivity controls for underloaded and

overloaded of resources. See: Creating Planning Exception Sets.
2.
Identify the list of routing-based resources (department/resources) and rate-based

resources (lines) for which you want to report exceptions against.
3.
Attach the exception set to the resource by choosing the Exception Set in the
Resources window in Oracle Bills of Material, and the Production Lines window in
4.
Navigate to the Exceptions window to view the capacity exception.
Testing What-if Scenarios

You can make changes to either capacity or materials and see the effects of these
changes on your plan.
To test the effect of a change in resources or materials, do this
1.
Navigate to the Planner Workbench.
2.
Find the plan in which you want to test what-if scenarios.
3.
To make changes to capacity available for this plan, navigate to the Available
Resources window. Then change the date, capacity units, or daily capacity for any
resource.
4.
To make changes to material supply or demand, navigate to the Supply, Demand,

or Supply/Demand window. Then make any changes you want, such as Quantity,
Date, Alternate Routing, Alternative BOM.
5.
Save your changes.
6.
In the Planner Workbench window, choose either Online or Batch in the Net
Change Replan region, then choose Plan.
7.
Re-query the plan to review the effects of your changes.

To implement and release your modified plan:
See: Implementing Planning Recommendations
See Also
Overview of Net Change Replan, Identifying Capacity Problems
Plan Status
You can view the status of the planning options you have submitted and the run times
of the processes in the Plan Status window.
To view the status of your plan options
1.
Navigate to the Plan Status window from the Tools menu.

This window has three tabbed regions related to the plan you are
viewing:
Current Submitted Options: The information on this region is the same as the
data entered on the Plan Options window when you generate this plan.
Last Submitted Options: The information displayed in this region is the historical
record of the options submitted prior to the current job.
Dates: This window displays the run times of the three processes that comprise
the planning engine.
See Also
7
Demand Classes
Overview of Demand Classes

Demand classes allow you to segregate scheduled demand and production into groups,
allowing you to track and consume those groups independently. A demand class may
represent a particular grouping of customers, such as governmental and commercial
customers, or it may represent sales channels or regions. Demand classes may also
represent different sources of demand, such as retail, mail order, and wholesale.
Defining Demand Classes

You can optionally define demand classes to group similar customers or sales orders.
You can use demand classes as a means of forecasting different sources of demand
separately.
Associate Demand Classes to Customer Demand

You can associate a demand class to a customer ship to address in Oracle Receivables
and to an order type in Oracle Order Management. Oracle Order Management
automatically assigns a demand class to a sales order line using either the demand class
associated to the customer ship to address or the order type.
Assign an Organizational Demand Class

You can assign a default demand class to your organization. Oracle MRP uses this
demand class during forecast consumption, and shipment and production relief.
Forecasting by Demand Class

You can optionally associate a demand class to a forecast when you define the forecast
name. When you place sales order demand, the forecast consumption process consumes
the forecast with the same demand class. If the forecast consumption process does not
Demand Classes 7-1
find a forecast, it consumes entries that have no demand class. If you place sales order
demand that does not have an associated demand class, the forecast consumption
process attempts to consume forecast entries associated with the organizational default
demand class first, and then consume entries that have no demand class defined.
Master Scheduling by Demand Class

You can optionally associate a demand class to a master demand schedule or master
production schedule when you define the master schedule name. When you ship a sales
order or create a discrete job, that sales order or discrete job consumes the master
schedules that are associated with the demand class of the sales order or discrete job.
After consuming master schedules with the same demand class as the sales order or
discrete job, Oracle MRP consumes master schedules with no demand class.
You can load a subset of the sales orders into your master schedule for a specific
demand class.
Planning by Demand Class

You can limit the netting of discrete jobs, repetitive schedules, flow schedules,
reservations, and subinventories when planning a master production schedule. If you
are planning a master production schedule that has an associated demand class, it only
nets discrete jobs and repetitive schedules that have the same demand class. You can
segregate your subinventories and reserved inventory by demand class and selectively
net them when launching the planning process.
Demand Class Forecasting

You can use demand classes as a means of forecasting different sources of demand
separately. For example, suppose your company has three primary sources for sales
orders: wholesale sales, retail sales, and mail order sales. Each source has a different
sales force you forecast independently. You may wish to create a separate forecast name
for each source and maintain each forecast independently. However, Oracle MRP
considers all sources of forecasted and sales order demand together.
In the above diagram, your master scheduler has created three forecast names: FC
WHOLESL, FCRETAIL, and FCMAILORDER. You maintain and report on each
forecast independently. Note that these forecasts are defined within a forecast set.
Your master scheduler combines all sources of demand, including the three forecasts
and all sales orders, into a single statement of demandthe master demand schedule.
The master scheduler then plans the master production schedule and the MRP plan
with all the demand combined.
See Also: Overview of Forecasting, page 2-1
You can associate a demand class with each sales order. When you place sales order
demand, the forecast consumption process consumes the forecast with the same
demand class. If the forecast consumption process does not find a forecast, it consumes
entries that have no demand class. If a sales order does not have an associated demand
class, the forecast consumption process attempts to consume forecast entries associated
with the organizational default demand class first, and then consume entries that have
no demand class defined.
Abnormal Demand
Certain sales orders should not consume the forecast, because they are not indicative of
what orders you expect in the future. For example, suppose you manufacture soft
drinks, and have 100 primary distributors to whom you sell. Your sales order demand
is roughly even across those distributors. One of those distributors has a special
promotion on your product, and places orders for ten times their normal amount. The
large order by this one distributor does not mean that your other distributors will order
less. Therefore, you might mark this particular order as abnormal.
Demand Classes 7-3
To prevent a sales order from consuming forecasts, associate the sales order to a
demand class that does not have a corresponding forecast and is not the same as the
demand class for your organization. In this case, the forecast consumption process does
not consume any forecast for the sales order.
Tip: You should define a demand class for abnormal demand and
assign it to an order type that you can associate with sales orders you
might mark as abnormal.
The following diagram depicts the forecast consumption process:
Demand Class Master Scheduling

You may wish to make further use of demand classes by segmenting not only your
forecasted demand, but also your scheduled production by demand class:
In the above diagram, suppose your master scheduler has created three forecast names:
FCWHOLESL, FCRETAIL, and FCMAILORDER. You maintain and consume each
forecast independently. However, rather than combining all forecast and sales order
demand into a single master demand schedule, as was done in the previous diagram,
your master scheduler maintains three demand schedules: WHLSALMDS, RETAIL
MDS, and MAILMDS. Each demand schedule consists of the forecast and actual
demand associated to a specific demand class.
Your master scheduler also maintains three separate master production schedules:
WHLSALMPS, RETAILMPS, and MAILMPS. You plan each master production
schedule independently. In this manner, not only has the master scheduler broken out
the sources of demand into separate groupings, but has also segregated units of
production by demand class as well.
To drive the MRP plan, the master scheduler combines all sources of production into a
single master production schedule, thus driving the MRP plan by the aggregate master
production schedule. The master scheduler manually combines master schedules into a
single master schedule, using the Load/Copy/Merge Master Demand Schedule or Load
Master Production Schedule windows. See: Loading a Master Schedule From an
Internal Source, page 3-9
Demand Classes 7-5
Maintaining the Master Production Schedule

You can allocate your discrete production by sales channel using demand classes. You
can manually or automatically define discrete jobs to build configurations for your
assembletoorder or maketoorder products. You can also associate discrete jobs with
sales orders for standard products to ensure customer satisfaction.
When you create a discrete job, it must consume the master production schedule for the
demand class that satisfies the discrete job. Therefore, a discrete job can have an
associated demand class. Oracle Work in Process automatically specifies the demand
class when you manually define a job or create a configuration order for a specific sales
order.
See Also
Discrete vs. Repetitive Manufacturing, Oracle Work in Process User's Guide
Demand Class ATP Calculation

You can specify that Available to Promise (ATP) be calculated by demand class. In this
case, the available to promise calculation only considers master production schedule
entries associated with the appropriate demand class as available to promise. You can
also segregate and calculate sales order demand by demand class as well.
See Also
Overview of Configure to Order, Oracle Bills of Material User's Guide
Net Inventory by Demand Class

You can net your inventory by demand class so that you do not have the same items
satisfying multiple demand classes. You can net your inventory by demand class in one
of two ways:
You can net items by subinventory. For example, items that are available to satisfy
Wholesale demand class are in a separate subinventory than those items that satisfy
the Retail demand class. You specify the Wholesale subinventory as nettable and
the Retail subinventory is nonnettable when planning the Wholesale demand
class, and vice versa when planning the Retail demand class. This relies upon you
manually overriding the subinventory netting when launching the planning
process.
You can reserve all items in a subinventory for a sales order. You can determine the
items in the subinventory reserved for the demand class by the sales order
associated with the demand class. Note that this method requires the full use of
hard reservations.
See Also
Viewing Item Reservations, Oracle Inventory User's Guide
Demand Classes 7-7
8
Time Fence Control
Overview of Time Fence Planning

Time fences are boundaries between different periods in the planning horizon. They
define short term regions within which planning restrictions minimize costly disruption
to shop floor and supplier schedules.
Time fences also provide guidelines to establish where various restrictions or changes
in operating procedures take place. For example, you can easily accomplish changes to
the MPS beyond the cumulative lead time while changes inside the cumulative lead
time are more difficult to accomplish. Oracle MRP makes use of three time fences: the
planning time fence, demand time fence, and release time fence.
Time Fences for Items

You can define planning, demand, and release time fence days for an item based on the
cumulative manufacturing lead time, cumulative total lead time, total lead time, or a
user-defined value.
You can also use the release time fence to stop the release of Kanban items from Oracle
MRP into Oracle Work in Process and Oracle Purchasing.
Master Schedule Creation Using the Demand Time Fence

When you load forecasts and sales orders into a master schedule you can specify
whether to use demand time fence control. You can specify whether you load forecasts
outside the demand time fence, sales orders within the demand time fence, or ignore
demand time fences. See: Selecting Master Schedule Load Options.
Material Planning with the Demand and Planning Time Fences

When you launch the planning process you can specify whether to consider planning,
or demand time fence control. For an MPS plan, you can also choose to overwrite
Time Fence Control 8-1
master schedule entries outside the planning time fence. For an MRP plan, you can
overwrite all planned orders as well as firm planned orders that fall outside the
Planning Time Fences for Requisitions
Purchase requisitions and internal requisitions are not subject to planning time fence
processes.
Material Planning with the Release Time Fence

When you define a plan or schedule name, you can allow the planning process to
automatically release planned orders as standard discrete jobs in Oracle Work in
Process, or as purchase requisitions in Oracle Purchasing.
You can also use the release time fence to stop the release of Kanban items from Oracle
MRP.
Time Fence Control

Time fence control is a policy or guideline you establish to note where various
restrictions or changes in operating procedures take place. For example, you can easily
change the master production schedule for an item beyond its cumulative lead time,
with little effect on related material and capacity plans. However, changes inside the
cumulative lead time cause increasing difficulty, to a point where you should resist
such changes because of their effect on other operations. You can use time fences to
define these points of policy change. Oracle MRP offers three types of time fences: the
demand time fence, planning time fence, and release time fence.
Defining Time Fences for Items

You define demand, planning, and release time fence days when you define an item.
You can define the demand, planning, and release time fence for the item as either the
cumulative manufacturing lead time, cumulative total lead time, total lead time, or a
user-defined time fence.
Oracle MRP defines one boundary of the time fence for an item as the current date, and
the other boundary as value of the cumulative manufacturing lead time, cumulative
total lead time, total lead time, or a user-defined time.
For example, suppose you define the demand time fence for an item as the cumulative
manufacturing lead time and the planning time fence as a user-defined time. The
planning process considers the demand time fence (in workdays) of the item as the
current date up to the cumulative manufacturing lead time of the item. The planning
process considers the planning time fence (in workdays) of the item as the current date
up to the time fence value you enter. See: Defining Items, Oracle Inventory User's Guide.
Establishing Time Fence Control

You establish demand and planning time fence control when you set up Oracle MRP.
See: Defining Planning Parameters.
You establish release time fence control when you define a plan or schedule name. You
can also override time fence control for individual material plans or master schedules
when you generate a DRP, MRP or MPS. See: Defining a Schedule Name, and Defining
MRP Names.
Demand Time Fence Control

The demand time fence is bordered by the current date and a date within which the
planning process does not consider forecast demand when calculating actual demand.
Within the demand time fence, Oracle MRP only considers actual demand. Outside the
demand time fence, the planning process considers forecast demand. You can specify
whether to use demand time fence control when loading a master schedule and
Planning Time Fence Control

The planning time fence is bordered by the current date and a date within which the
planning process does not alter the current material plan or master schedule. You can
specify whether to use planning time fence control when launching the planning
process.
For discrete items within the planning fence, the planning process does not reschedule
in (create earlier) order due dates or create new planned orders for the item to satisfy
net demand requirements. However, the planning process can reschedule out or cancel
an order when it determines that such orders create excess supply. For discrete items
outside the planning time fence, the planning process can generate suggestions to
create, change, and reduce entries on the master schedule or the material requirements
plan.
For repetitive items, Oracle MRP restricts the planning process to suggest rates of
production within the planning time fence that differ from the current aggregate
repetitive schedule by no more than the acceptable rate increase and acceptable rate
decrease you defined for the item. If either the acceptable rate increase or decrease
value is undefined, the planning process is not restricted from increasing or decreasing
the repetitive schedule respectively.
You can choose whether to display a warning when you define or update MPS entries
that violate the planning time fence, or when you define or update MDS entries that
violate the demand time fence. Set the MRP:Time Fence Warning profile option to Yes.
See: Setting Your Personal User Profile, Oracle Applications User's Guide.
Planning Time Fences for Requisitions

Purchase requisitions and internal requisitions are not subject to planning time fence
processes.
Release Time Fence Control

The release time fence is bordered by the current date and a date within which the
planning process automatically releases planned orders to Oracle Work in Process as
discrete jobs or to Oracle Purchasing as purchase requisitions. You can specify whether
to use release time fence control when defining your plan name.
The planned orders must meet the following auto-release criteria:
the new due date lies within the auto-release time fence
the lead time is not compressed
the orders are for standard items (will not release models, option classes, and
planning items)
the orders are for DRP planned items in a DRP plan, MPS planned items in an MPS
plan, or MRP planned items in an MRP plan See: Auto-release Planned Orders.
Auto-release of suggested repetitive schedules is not applicable to repetitively planned

items. No material availability check is performed before WIP jobs are released.
Time Fences and Firm Orders

A firm order is an order that is frozen in quantity and time (unavailable for
rescheduling). Oracle MRP automatically creates a planning time fence for the firm
order if the firm order exists after the planning time fence date. There are two methods
you can use to firm an order that creates a time fence: you can firm a planned order or
firm a discrete job in the Planner Workbench, or you can firm a discrete job or purchase
order within Oracle Work in Process and Oracle Purchasing directly.
Oracle MRP creates a time fence for a firm order because it implies that resources
committed to meeting the firm order would be unavailable for orders scheduled earlier.
Note: You can use the profile option, MRP: Firm Planned Order Time
Fence to indicate whether to form natural time fences for your MRP
firm planned orders when launching the planning process.
Oracle MRP does not create a time fence for an MRP firm planned order if you set this
profile option to no. See: Setting Your Personal User Profile, Oracle Applications User's
Guide.
Master Schedule Load

You can specify the following demand time fence options when you load forecasts into
a master schedule.
Load Sales Orders within and Forecast Outside Demand Time Fence
Oracle MRP loads only sales orders on and within the demand time fence and only
forecast entries outside the demand time fence
Load Forecast outside Demand Time Fence Only

Oracle MRP loads all forecast entries outside the demand time fence and ignores
forecast entries on and within the demand time fence. Oracle MRP also loads all sales
orders from the start date to the cutoff date if you enter All sales orders in the Include
field.
Ignore Demand Time Fence

Oracle MRP loads all forecast entries between the start date and the cutoff date and
ignores the demand time fence. Oracle MRP also loads all sales orders from the start
date to the cutoff date if you enter All sales orders in the Include field.
Sales Orders Only

When you choose to load sales orders into a master schedule, you can manually enter a
cutoff date, or use the cutoff date based on the demand time fence. If you use the
demand time fence date as the cutoff, Oracle MRP does not consider sales order
demand after the demand time fence for an item. If the item has no demand time fence
or you ignore the demand time fence, Oracle MRP includes all sales orders up to the
cutoff date that you specify. See: Loading a Master Schedule from an Internal Source.
You can specify the following demand time fence options when you load sales orders
into a master schedule.
Load Sales Orders Within Demand Time Fence

Oracle MRP loads all sales orders within the demand time fence. Oracle MRP does not
include sales orders outside the demand time fence.
Ignore Demand Time Fence

Oracle MRP loads all sales orders ignoring the demand time fence.
Planning Process Execution

You can specify whether to consider demand and planning time fence control by
selecting Demand Time Fence Control and Planning Time Fence Control in the Plan
Options window. If demand time fences are active, the planning process ignores entries
on the master schedule that have an origination type of Forecast within the demand
time fence. This is the same as when you load a forecast into a master schedule and
enter Load forecast outside demand time fence only in the Time Fence Option field. You
can choose to use either or both methods to eliminate forecasted demand within the
demand time fence.
Note: The planning process respects The planning process respects firm
orders and the implicit time fences that they create even if you specify
not to use Planning Time Fence control. The planning process does not
apply Planning Time Fence logic to purchase requisitions or internal
requisitions.
Overwriting Entries
When you launch the planning process, you can also choose to overwrite the master
production schedule entries and firm planned orders that fall outside the planning time
fence for an item.
For an MPS plan, the planning process deletes all master production schedule entries
that lie outside the planning time fence, and replaces those entries with a new master
production schedule. The planning process does not modify master schedule entries
that fall within the planning time fence. You can use this option to induce short-term
stability of the master production schedule, while creating the optimal long-term master
production schedule.
When you use this option for an MRP or DRP plan, the planning process overwrites all
planned orders and firm planned orders outside the planning time fence.
See Also
Overwrite Options.
Master Production Schedule Maintenance

On-going maintenance of the MPS is critical to the production plan. Your company
policies and procedures dictate what changes you can make, when you can make them,
and who is authorized to make them.
When you define an item as being MPS planned, you can choose to automatically
reduce master production schedule entries. A periodic process (planning manager)
automatically reduces master production schedule entries for discrete items based on
the option you choose. The planning manager deletes master production entries for
repetitive items.
None
You can use this option to leave master production schedule entries and not
automatically reduce them. Production relief decrements the master production
schedule entries through the creation of discrete jobs or purchase requisitions.
Past Due
You can use this option to automatically reduce master production schedule entries as
they become past due.
Within Demand Time Fence

You can use this option to automatically reduce master production schedule entries for
discrete items within the demand time fence of the item. (Oracle MRP does not reduce
any entries if you do not specify the demand time fence.) Oracle MRP deletes master
production entries for repetitive items. This option may be necessary when MPS relief is
turned off, or if you are not using Oracle Work in Process. If a master production
schedule spans a demand time fence, Oracle MRP truncates it on the time fence date.
Within Planning Time Fence

You can use this option to automatically reduce master production schedule entries for
discrete items within the planning time fence of the item (Oracle MRP does not reduce
any entries if you do not specify the planning time fence). Oracle MRP deletes master
production entries for repetitive items. This option may be necessary when MPS relief is
turned off, or if you are not using Oracle Work in Process. If a master production
schedule spans a planning time fence, Oracle MRP truncates it on the time fence date.
See Also
Production Plan Monitoring

For discretely-planned items, the planning process does not recommend that you
reschedule in existing orders, and it does not create planned orders, within the planning
time fence. However, the planning process can recommend that you reschedule out or
cancel existing orders, even if they fall within the planning time fence.
For repetitively-planned items, Oracle MRP restricts the planning process to suggest
rates of production within the planning time fence that differ from the current
aggregate repetitive schedule by no more than the acceptable rate increase and
acceptable rate decrease you defined for the item. If either the acceptable rate increase
and decrease value is not entered (null), Oracle MRP is not restricted from increasing or
decreasing the repetitive schedule respectively.
Because the planning time fence restricts the actions that Oracle MRP can take, your
plan may have material imbalances that require the attention of the master scheduler or
planner. You can easily identify those elements of the plan that require the attention of
the planner by using the Exceptions window to review action messages. You can view
those items and orders based upon a set of predefined exception messages. You can also
run the Planning Detail Report or the Supply Chain Planning Detail Report for a
specific planner and exception message.
See Also
Reviewing Planning Exceptions Planning Detail Report
Time Fence Planning Example

The following example illustrates one business scenario that utilizes demand, planning,
and release time fences.
Suppose your company builds an item called MODEL. MODEL consists of the
following multiple options:
Your company forecasts its material requirements based on MODEL. The company
places sales orders demand against predefined configurations that have options
OPTION 1, OPTION 2, OPTION 3 as components.
Your company forecasts its material requirements based on MODEL. The company
places sales orders demand against predefined configurations that have options
OPTION 1, OPTION 2, OPTION 3 as components.
Your company uses a demand time fence. Inside the demand time fence, your company
only considers actual sales order demand. Outside the demand time fence, your
company only considers forecasted demand. When you load the master schedule from a
forecast, you can accomplish this by including all sales orders, and by loading sales
orders within and forecast outside demand time fence. See: Loading a Master Schedule
From an Internal Source.
In this example, you have defined the demand time fence for MODEL, CONFIG1, and
CONFIG2 at period 2. You have not defined a demand time fence for the option items 1,
2 and 3.
The material plan for the item MODEL and one of its options, Option 2, and one of the
configurations, CONFIG1, is as follows:
Material Plan for MODEL

Period 1
Period 2
Forecast Demand
Gross Requirements
MPS
Projected QOH
ATP
Period 3
Period 4
100
100
100
100
100
100
100
100
Period 3
Period 4
Material Plan for CONFIG1

Period 1
Period 2
Actual Demand
50
80
Gross Requirements
50
80
Planned orders
50
80
Projected QOH
50
80
Period 1
Period 2
Period 3
Period 4
50
50
Material Plan for OPTION2
Demand from MODEL

Demand from CONFIG1
50
80
Gross requirements
50
80
50
50
Projected QOH
Note the following: there is no demand for MODEL in the first two periods since
MODEL is not an orderable item it is used primarily for forecast and planning
purposes. Demand for MODEL after the demand time fence (period 2) consists entirely
of forecasted demand.
Demand for CONFIG1 in the first two periods consists entirely of actual demand. There
is no other demand for CONFIG1 because it is not forecasted.
Demand for item OPTION 2 in the first two periods consists entirely of demand passed
down from item CONFIG1, which is derived from actual sales order demand for
CONFIG1. After the first two periods, the demand for OPTION 2 consists of demand
generated from MODEL, which is based entirely on forecasted demand.
You have chosen to master schedule both the model and its options. This results in the
production is being driven by sales orders within the demand time fence and by
forecasts outside the demand time fence. Oracle MRP derives the master schedule for
the options entirely from the master schedule for the model. The options are master
scheduled for purposes of order promising. See: Available to Promise.
For this example, you have defined the planning time fence for MODEL as some
number of periods out from today, thereby providing stability for the short-term plan.
You have not defined a planning time fence for the option items 1, 2, and 3. If you
execute the planning process using demand time fence control and you choose to
overwrite the outside planning time fence, Oracle MRP overwrites the entire master
production schedule for the option items, and creates a new schedule based entirely on
actual sales orders for the option items within the demand time fence, and the master
production schedule for the model outside the demand time fence.
For this example, your company does not use Oracle Work in Process. Therefore,
discrete jobs are not created, and thus never consume the master production schedule
for MODEL. To effectively consume the master production schedule for MODEL, you
must set the Auto-reduce MPS attribute to Within Demand Time Fence when you define
the MODEL item. Whenever a master production schedule entry is within the demand
time fence, Oracle MRP automatically reduces it. See: Defining Items, Oracle Inventory
User's Guide.
If your company did use Oracle Work in Process and Oracle Purchasing, you could set a
release time fence for any planned orders generated by the planning process. If you
define OPTION2 with a release time fence of as many days as there are in period 1, then
the 50 planned orders for period 1 generated by the planning process would
automatically be released. They would be released to Oracle Work in Process as discrete
jobs or to Oracle Purchasing as purchase requisition, depending on their item attributes;
their job status, requisition load group, and other values would depend on the defaults
applicable to the item. With this time fence, the 80 planned orders generated for period
2 would not be released, and would require selection and implementation by the master
scheduler or material planner. See: Defining Items, Oracle Inventory User's Guide.
9
Two-Level Master Scheduling
Overview of Two-Level Master Scheduling

This chapter tells you everything you need to know about creating master schedules in
configure-to-order environments
Many companies operate in configure-to-order manufacturing environments
characterized by many different product configurations, each made from combinations
of a few key subassemblies. Competitive pressures often demand that customer
delivery lead times are shorter than manufacturing lead times in these environments.
This forces companies to start building products before customers place sales orders for
specific configurations. One solution to this problem is to master schedule and build
key subassemblies only, based on anticipated demand, and to assemble specific
configurations only after receiving customer orders.
Oracle MRP lets you use this approach, known as two-level master scheduling, to
forecast and master schedule products and key subassemblies in configure-to-order
manufacturing environments.
Multilevel Planning and Model Bills

You can define multilevel planning and model bills to represent product families and
products with options, and to maintain planning percents that represent estimates of
anticipated product and option mixes.
Forecasting
You can forecast any item, anywhere on your bills of material, including planning
items, models, option classes, options, and mandatory components. You can also define
a configuration as a standard item and forecast it as you would any other standard
item.
Two-Level Master Scheduling 9-1
Forecast Explosion
You can explode forecasts for planning items, models, and option classes to selected
components using the components, usages, and planning percents defined on your
planning, model, and option class bills. You can associate alternate bills of material to
multiple forecasts for the same item and explode the same forecast using different
components, usages, and planning percents. You can modify, re-explode, and
re-consume forecasts for planning items, models, and option classes.
Oracle MRP automatically consumes forecasts for configurations, models, option
classes, options, and mandatory components as you place sales order demand for
configurations.
Master Scheduling
You can master schedule any planned item, anywhere on your bills of material,
including models, option classes, options, and mandatory components. You can also
define a configuration as a standard item and master schedule it as you would any
other standard item.
Production Relief
Oracle MRP automatically relieves master production schedules for configurations,
models, and option classes when you create final assembly orders for configurations.
Oracle MRP automatically relieves master production schedules for options and
mandatory components as you create work orders to build them.
Shipment Relief
Oracle MRP automatically relieves master demand schedules for configurations,
models, option classes, options, and selected mandatory components as you ship sales
orders for configurations.
Rough Cut Capacity Planning

You can use rough cut capacity planning to validate your master schedules for
configurations, models, option classes, and options against key resource constraints,
using bills of resources.
See Also
Overview of Configure to Order, Oracle Bills of Material User's Guide
Overview of Master Scheduling
Production Planning
Production Planning is one of the methods of two-level master scheduling used in
managing the supply chain. In creating a production plan, a company looks at the big
picture (the aggregate) rather than the level of the individual product or item,
predicting a level of manufacturing output in accordance with predicted sales and other
company goals and constraints.
Because production planning occurs at an aggregate level, creating a production plan
involves grouping products into product families. These groupings are based on
product's similarities in design, manufacturing process, and resource usage. You can
assign planning percentages to the members of the product family, and use the
relationship between product family items and its members in forecast explosion,
consumption, master scheduling, and capacity and materials planning. Production
Planning enables forecasts for the product family to be exploded down to the product
family members (based on the planning percentages and effectivity dates for the
member items) in a process similar to that of exploding a forecast for a model.
Sales orders for member items consume the forecast for the member items as well as for
the product family. Throughout the application, processing is done at both the
aggregate and the detail level. Thus, you will be able to get detailed and high-level
information about how well your organization is executing its production plans.
Prerequisites to Production Planning
Before you can start production planning, you must:
Define an item as a product family. See: Defining Items, Oracle Inventory User's
Guide.
Assign member items to the product family. See: Assigning Product Family
Members, Oracle Bill of Materials User's Guide.
Set planning percentages and effectivity dates for member items. See: Setting
Planning Percentages for Product Family Members, Oracle Bill of Materials User's
Guide.
See Also
Overview of Forecast Explosion Consumption for a Product Family
Example Bill of Material for Two-Level Master Scheduling

The following table illustrates the multilevel bill of material used to illustrate important
two-level master scheduling concepts. All items are in the bill of material with quantity
of one.
Bill of Material for Training Computer
Level
Item
Description
BOM Item Type
Optional
Plan %
Training
Computer
Planning
No
--
.2
. Laptop
Computer
Model
No
60
..3
. . Carrying Case
Standard
No
100
..3
. . Keyboard
Standard
No
100
..3
. . Processing
Unit
Option Class
No
100
...4
. . . Processor A
Standard
Yes
65
...4
. . . Processor B
Standard
Yes
35
..3
. . Monitor
Option Class
No
100
...4
. . . VGA
Option Class
Yes
70
....5
. . . . VGA
Manual
Standard
No
100
....5
. . . . VGA1
Standard
Yes
50
....5
. . . . VGA2
Standard
Yes
50
...4
. . . EGA
Option Class
Yes
30
....5
. . . . EGA1
Standard
Yes
55
Level
Item
Description
BOM Item Type
Optional
Plan %
....5
. . . . EGA2
Standard
Yes
45
...4
. . . Monitor
Manual
Standard
No
100
..3
. . Operating
System
Option Class
Yes
90
...4
. . . Windows
Standard
Yes
80
....5
. . . . Windows
Manual
Standard
No
100
....5
. . . . Windows
CD
Standard
No
100
...4
. . . Linux
Standard
Yes
20
....5
. . . . Linux
Manual
Standard
No
100
....5
. . . . Linux CD
Standard
No
100
Item and Bill Definition

Oracle Bills of Material provides these item types, identified by the BOM Item Type
item attribute, that you can use to plan and build products with options:
Planning item
Model
Option class
Standard item
Product family item
Define the BOM Item Type for each of your items using the Define Item window in
Oracle Inventory. You can combine each of these item types to define complex bill of
material structures using the Define Bill of Material window in Oracle Bills of Material.
Planning Items
Use planning items to represent groups of related items. In a configure-to-order
environment, you might use planning items to represent groups for your models, and
state your high-level production plans in terms of these groups rather than individual
models. You can also use planning items for forecast explosion.
Models
Use models to represent products that include options chosen by customers during
order entry. For example, you might use a model to represent a computer with many
different CPU, monitor, and operating system options.
Assemble to Order Models vs. Pick-to-Order Models
Models can be assembled-to-order or picked-to-order. Use assemble-to-order models to
represent products whose options and mandatory components are assembled, using a
final assembly order, when customers order configurations. Use pick-to-order models
to represent products whose options and included items are picked and shipped
directly from stock, using a sales order pick slip, when customers order configurations.
Option Classes
Use option classes to group together related options. In a configure-to-order
environment, you might use an option class to group together the different processor
options that are available when customers order a computer.
Standard Items: Options and Mandatory Components

Standard items are the only types of items that are actually built. In a configure-to-order
environment, use standard items to represent your key subassemblies. Standard items
that have the bill of material attribute Optional set to Yes are called options. Standard
items that have the Optional attribute set to No are called mandatory components.
Assemble-to-Order Standard Items vs. Pick-to-Order Standard Items
Standard items are similar to models in that they can be assembled-to-order or
picked-to-order. Use assemble-to-order items, also known as predefined configurations,
to represent standard items that are assembled using a final assembly order. Use
pick-to-order items to represent a collection of items that are picked and shipped from
stock using a picking slip.
Product Family Items

Use product family items to represent groups of items related by similarities in design,
manufacturing, and resource usage. You can use the relationship between product
family items and its members in forecast explosion, consumption, master scheduling,
and capacity and materials planning.

See also Overview of Bills of Material, Oracle Bills of Material User's Guide and Defining
Items, Oracle Inventory User's Guide
Production Forecast Establishment
You can define and maintain forecasts for any item, at any level on your bills of
material. You can forecast demand for products directly, or forecast product families
and explode forecasts to individual products through planning bills. You can forecast
demand for option classes, options, and mandatory components directly. You can also
explode forecasts for models and option classes, through model and option class bills,
to selected option classes, options, and mandatory components.
Forecasting Planning Bills

You can define multilevel planning bills, with multiple levels of planning items, to
represent groups of related products that you want to forecast as a unit in Oracle Bills of
Material.
Typically, you can order components of a planning bill, but not the planning item itself.
The planning item is an artificial grouping of products that helps you to improve the
accuracy of your forecasting since, generally, the higher the level of aggregation, the
more accurate the forecast.
When you load a planning item forecast into another forecast, you can choose to
explode the aggregate forecast for the planning item into detailed forecasts for each of
the components defined on the planning bill. The forecast quantities exploded to the
components are calculated by extending the planning item forecast by the component
usages and planning percents defined on the planning bill. You can also choose to
explode forecasts when you load a planning item forecast into a master schedule.
Planning Bills
The following table illustrates a planning bill for Training Computer, a planning item
that represents a planning bill for three types of computers: laptop, desktop, and server.
The planning percent assigned to each member of the planning bill represents
anticipated future demand for each product. Although, in this example, the planning
percents add up to 100%, it is equally valid for the sum of the planning percents to be
less than or greater than 100%.
Planning Bill of Material for Training Computer
Level
Item Description
BOM Item Type
Planning %
Training Computer
Planning
--
Level
Item Description
BOM Item Type
Planning %
.2
. Laptop Computer
Model
60
.2
. Desktop Computer
Model
20
.2
. Server
Model
20
The following table illustrates forecast explosion, via the planning bill described in the
previous table, for a forecast of 100 Training Computers. The table also illustrates
forecast consumption after you place sales order demand for 20 Laptop Computers.
Original forecast shows forecast quantities before forecast consumption. Current
forecast shows forecast quantities after consumption by sales order demand.
Forecast Explosion and Forecast Consumption
Level
Item Description
Original Forecast
Current Forecast
Training Computer
100
100
.2
. Laptop Computer
60
40
.2
. Desktop Computer
20
20
.2
. Server
20
20
Forecasting Models
You can define model and option class bills, with multiple levels of option classes,
options, and mandatory components, to represent your complex configure-to-order
products in Oracle Bills of Material. You can then use forecast explosion to explode
model and option class forecasts the same way you explode forecasts for planning
items.
The logic for exploding models and option classes is the same as the logic used to
explode planning items.
Model Bills
The following table illustrates a model bill for Laptop Computer, a model that includes
two mandatory components and three option classes. The planning percent assigned to
optional option classes represents anticipated demand for the option class. In this
example, 90% of Laptop Computers are expected to be sold with an operating system,
and the remaining 10% are expected to be sold without.
Model Bill for Laptop Computer
Level
Item
Description
BOM Item Type
Optional
Planning %
.2
. Laptop
Computer
Model
No
60
..3
. . Carrying Case
Standard
No
100
..3
. . Keyboard
Standard
No
100
..3
. . Processing
Unit
Option Class
No
100
..3
. . Monitor
Option Class
No
100
..3
. . Operating
System
Option Class
Yes
90
Option Class Bills

The following example illustrates the option class bills for the Monitor, VGA, and EGA
option classes. The planning percent assigned to each option within each option class
represents anticipated demand for the option. In this example, 70% of all Laptop
Computers are expected to be sold with a VGA monitor, and the remaining 30% are
expected to be sold with an EGA monitor. Notice that the Monitor option class is not
optional. This means that customers must always choose one of the Monitor options
when ordering Laptop Computer. Of the 70% of Laptop Computers sold with a VGA
monitor, 50% are expected to be sold with the VGA1 monitor and 50% are expected to
be sold with the VGA2 monitor. The VGA option class also includes a mandatory
component, VGA Manual, that is always shipped with Laptop Computer if the VGA
monitor option class is chosen, regardless of the VGA option.
Option Class Bills for Monitor, VGA, and EGA
Level
Item
Description
BOM Item Type
Optional
Planning %
..3
. . Monitor
Optiion Class
No
60
Level
Item
Description
BOM Item Type
Optional
Planning %
...4
. . . VGA
Option Class
Yes
100
....5
. . . . VGA
Manual
Standard
No
100
....5
. . . . VGA1
Standard
Yes
100
....5
. . . . VGA2
Standard
Yes
100
...4
. . . EGA
Option Class
Yes
90
Forecasting Predefined Configurations

Predefined configurations are configurations that you have defined as standard items,
with standard bills and standard routings. You might define a predefined configuration
because you often use the configuration in sales promotions, or the configuration is one
of your most commonly ordered configurations, and you want to build it to stock to
reduce delivery lead times and improve customer service levels. Your customers can
order predefined configurations by item number, just as they order any other standard
item.
Forecast consumption, forecast explosion, master scheduling, planning, production
relief, and shipment relief for predefined configurations behave as they do for any other
standard item.
See Also
Overview of Forecast Explosion
Forecast Consumption for Models and Predefined Configurations
Overview of Bills of Material, Oracle Bills of Material User's Guide

Oracle MRP lets you master schedule any planned item on your master schedules,
including models, option classes, and product families.
With the two-level master scheduling approach, you typically master schedule your key
subassemblies, your options and mandatory components, since they are the highest
level buildable items in your model bills.
Although models, option classes, and product families are not buildable items, you may
want to master schedule them so that you can calculate available-to-promise (ATP)
information for promising order ship dates by model, option class, or product family.
You might also want to master schedule your models option classes, and product
families so that you can perform rough-cut capacity checks by model, option class, and
product family. This is particularly valid when different configurations of your models
have very similar capacity requirements.
Note: Oracle MRP does not support planning for pick-to-order models
and option classes.
For product family member items that have forecast control set to None, the planning
process explodes and passes the demand down to the member items based on the
product family allocation percentage. Since forecast control set to None means that the
item is not forecasted, demand for an item whose forecast control is set to None gets
passed down during the planning process. Thus, the resulting explosion is independent
of the quantity of existing sales orders for member items.
10
Repetitive Planning
Overview of Repetitive Planning

You can plan your repetitive assemblies in terms of daily production rates rather than
discrete quantities. Many of the repetitive planning functions are similar to those of
discrete planning.
MPS and MRP Planning for Repetitive Assemblies

You can use repetitive planning to plan supply and demand for repetitive assemblies
using daily production rates rather than discrete quantities.
Repetitive Planning Periods

You can use bucket days and planning horizons to define three repetitive planning
regions. You can define smaller planning periods in the short term, to maintain an
optimal balance between smoothing production and responding to daily demand
fluctuations. You can define larger planning periods for your longterm plan plans, to
monitor supply and demand trends for your repetitive assemblies.
Anchor Date
You can define a repetitive anchor date to stabilize the repetitive planning process
during subsequent planning runs within the same repetitive planning period.
Component Demand
You can pass demand down from repetitive assemblies to repetitive components, from
repetitive assemblies to discrete components and from discrete assemblies to repetitive
components.
Repetitive Planning 10-1
Safety Stock and Order Modifiers

You can use safety stock and order modifiers to implement your inventory and
production policies for your repetitive assemblies.
Repetitive Schedule Allocation

You can allocate suggested aggregate repetitive schedules across individual production
lines according to line priorities and production rates you define in Oracle Work in
Process.
Firm Repetitive Schedules

You can firm part or all of your current repetitive schedules in Oracle Work in Process
to prevent the repetitive planning process from suggesting daily quantities that differ
from your current firm rates.
Repetitive Planning Control

You can use planning time fences, acceptable rate changes, and overrun percents to
control the nervousness of your repetitive plans and to minimize disruption of your
short term shop floor and supplier schedules.
Repetitive Schedule Implementation

You can use the Planner Workbench to implement suggested repetitive schedules as
current repetitive schedules in Oracle Work in Process.
Repetitive Reports and Inquiries

You can use a comprehensive selection of reports and online inquiries to review and
monitor all aspects of your repetitive planning process.
See Also
Overview of Repetitive Manufacturing, Oracle Work in Process User's Guide
Overview of Repetitive Planning Concepts

Repetitive planning allows you to plan your repetitive assemblies using daily
production rates rather than discrete quantities.
The output of the repetitive planning process is a set of suggested repetitive schedules
for each one of your repetitive assemblies.
Each repetitive schedule for repetitive assembly is defined by:
a daily quantity
a start date
an end date
Repetitive Planning versus Discrete Planning

Although there are many similarities between repetitive planning and discrete
planning, there are also a number of important differences.
Repetitive schedules represent planned supply for repetitive assemblies in the same
way that planned orders represent planned supply for discretely planned assemblies.
The difference, however, is that repetitive schedules are defined using daily quantities;
whereas planned orders are defined using discrete quantities. Also, the daily quantities
defined for repetitive schedules represent supply for each workday between the
repetitive schedule start and end dates. The discrete quantities defined for planned
orders represent supply for a single date, the planned order due date, only.
There is another important difference between repetitive planning and discrete
planning. The repetitive planning process always suggests new aggregate repetitive
schedules that replace current aggregated schedules to satisfy net requirements for a
given planning period. This is different from discrete planning where, if net
requirements exist, the planning process suggests planned orders to supplement existing
scheduled receipts.
In repetitive planning, therefore, suggested repetitive schedules alone match net
requirements within a repetitive planning period. With discrete planning, it is the
summation of planned orders and existing orders that always match net requirements
for the same period.
Unlike the reschedule recommendations that the planning process generates for discrete
jobs, the repetitive planning process never recommends that current repetitive
schedules defined in Oracle Work in Process be rescheduled. Instead, it always
recommends a set of new suggested repetitive schedules that satisfy current net
requirements.
The reason for this lies in the way in which repetitive schedules are defined. Since
repetitive schedules are defined by a daily quantity, a start date and an end date, if the
repetitive planning process were to recommend new daily quantities and new start and
end dates, as it would do if it were recommending that a repetitive schedule be
rescheduled, it would essentially be defining a new schedule.
Repetitive Schedule Dates

The repetitive planning process uses four dates to define repetitive schedules:
First unit start date
Last unit start date
First unit completion date
Last unit completion date
The first unit start date (FUSD) represents the date you plan to start production of the
first assembly on a repetitive schedule.
The last unit start date (LUSD) represents the date you plan to start production of the
last assembly on a repetitive schedule.
The first unit completion date (FUCD) represents the date you plan to complete
production of the first assembly on a repetitive schedule.
The last unit completion date (LUCD) represents the date you plan to complete
production of the last assembly on a repetitive schedule.
The difference between the FUSD and the FUCD represents the lead time of a repetitive
assembly, and is the amount of time that it takes to complete a single unit of the
assembly from start to finish. Oracle Work in Process calculates the lead time based on
the routing for lines with a lead time basis of Routing based. Oracle Work in Process
defaults the lead time from the production line for repetitive schedules on production
lines with a lead time basis of Fixed.
The difference between the FUSD and the LUSD represents the repetitive processing
days for your repetitive schedule. These are the number of days you plan to work on
your repetitive schedule.
Repetitive Schedule Types

There are four different types of repetitive schedules:
Current aggregate repetitive schedule
Current repetitive schedule
Suggested aggregate repetitive schedule
Suggested repetitive schedule
Current aggregate repetitive schedules represent the sum of all current work in process
repetitive schedules for repetitive assemblies, across all production lines, for a specified
period. Current aggregate repetitive schedules are defined as an assembly, a daily
quantity, a start date and an end date.
Current repetitive schedules are a portion of current aggregate repetitive schedules.
They represent individual work in process repetitive schedules producing repetitive
assemblies on a single production line. Current repetitive schedules are defined as an
assembly, a daily quantity, a start date, an end date, and a production line.
Suggested aggregate repetitive schedules represent the optimal repetitive schedules
suggested by the repetitive planning process to satisfy the total demand for repetitive
assemblies within a given period. They represent suggested total production across all
production lines.
Suggested repetitive schedules are a portion of suggested aggregate repetitive
schedules. They represent individual suggested repetitive schedules producing
repetitive assemblies on a single production line. The repetitive planning process
generates suggested repetitive schedules during the repetitive schedule allocation
process. See: Repetitive Schedule Allocation.
Repetitive Planning Periods

The repetitive planning process always tries to smooth supply by suggesting daily
quantities that match average daily demand. The time period over which demand is
averaged is a userdefined number of days, or bucket, known as the repetitive planning
period. Since average daily demand and suggested daily quantities are calculated by
dividing total demand by the total number of workdays in your planning periods, the
sizes of your planning periods are very important.
Period Sizes and Horizons
You can use three period sizes, called bucket days, and two horizons to define the
granularity of repetitive plans across your planning horizon. The first bucket days are
used to generate all repetitive planning periods within your first horizon. The second
bucket days are used to generate all planning periods within your second horizon. The
third bucket days are used to generate all other planning periods up to the end of your
workday calendar.
Repetitive planning periods can never overlap. For example, if your first horizon is 20
days and your second horizon is 40 days, your first horizon extends from day 1 to day
19. Your second horizon extends from day 20 to day 59.
You may want to use smaller periods in the short term. Since your daily demand is
averaged over smaller time periods, smaller planning periods result in suggested daily
quantities that more accurately respond to your shortterm fluctuations in demand.
You may want to use larger periods in the long term. Since your daily demand is
averaged over larger time periods, larger planning periods result in fewer and less
precise suggested daily quantities. These are useful for identifying longterm plan
trends in repetitive supply and demand.
There is also a performance advantage to using larger buckets further out along the
planning horizon. It takes the repetitive planning process less time to calculate fewer,
larger schedules than it takes to calculate many smaller schedules.
You can choose to use Calendar dates or Work dates to generate your planning periods.
Calendar dates allow you to fix the length of your planning periods, regardless of the
timing of nonworkdays and holidays. This option always creates weekly start dates on
the same day of the week.

Work dates do not fix the length of your planning periods. Work dates allow your
planning periods to shift out in response to nonworkdays and holidays. This option
does not create weekly start dates on the same day of the week, for example, if there is a
holiday in the middle of the week.
Example Planning Periods

If you want your planning periods to always start on a Monday, regardless of weekends
and holidays, use calendar dates and verify that your bucket days and planning
horizons are all multiples of 7. Also make sure that your anchor date is a Monday.
You can use the Work Dates window to review your workday calendar and identify
which days have been calculated as repetitive planning period start dates.
Repetitive Schedules as Planned Supply

Repetitive planning always acts on completion dates. Notice that repetitive schedules
have two completion dates: first unit completion date and last unit completion date.
These two completion dates are analogous to due dates for planned orders. In both
cases, the dates represent the date when supply is assumed to be available to satisfy
demand. The repetitive planning process always assumes that the supply is available at
the beginning of the day.
The planned supply represented by repetitive schedules becomes available to satisfy
demand after the first assembly on the schedule is completed. Thereafter, there is
supply, for a quantity equal to the daily rate, for each workday between the FUCD and
the LUCD.
To ensure that the supply is available on the first date on which demand needs to be
satisfied, the repetitive planning process offsets the FUCD by the assembly lead time to
determine the FUSD.
The repetitive planning process always assumes that production can only take place on
a workday.
MPS and MRP Planning for Repetitive Assemblies

Optimal Rate Calculation
Without any restrictions, such as firm or partially firm repetitive schedules, the
repetitive planning process always suggests a daily rate that equals the optimal rate.
The basic calculation of optimal rates involves three steps:
Sum net requirements
Calculate average daily demand
Set optimal rate = average daily demand
The repetitive planning process calculates optimal rates by summing net requirements
for each repetitive assembly within each repetitive planning period. An average daily
demand is calculated by dividing the total demand for the period by the total number
of workdays within the same period. The repetitive planning process recommends an
optimal rate that matches the average daily demand.
Component Demand
The repetitive planning process passes down demand, from repetitive assemblies to
repetitive components as daily rates rather than discrete quantities. Component
requirements are offset from using assembly requirements in the same way lead time
offsets are used for discrete assemblies and components in discrete planning.
The following diagram illustrates how component demand is passed down as a rate.
Notice that when component requirements are offset from using assembly requirements
by the assembly lead time, the component demand can sometimes span multiple
planning periods. This can result in multiple suggested daily rates that differ from the
original demand rate.
Safety Stock and Order Modifiers

Safety stock and order modifiers help you translate discrete and repetitive demand into
planned orders and repetitive schedules that match your inventory and production
policies.
Safety Stock
You can specify safety stock days, together with safety stock percent, as item attributes
using the Define Item window in Oracle Inventory. For discretely manufactured items,
the planning process calculates the safety stock quantity by multiplying the safety stock
percent by the average gross requirements for the period of time defined by the safety
stock days.
For repetitively manufactured items, the repetitive planning process multiplies the
safety stock percent by the average daily demand for each repetitive planning period.
The repetitive planning process calculates the safety stock quantity for each repetitive
period across the planning horizon.
Order modifiers for repetitive assemblies work in a similar way to order modifiers for
discrete assemblies.
Minimum and Maximum Daily Rate

Minimum and maximum order quantities are translated into minimum and maximum
daily rates.
Fixed Daily Rate

Fixed order quantities are translated into fixed daily rates. With fixed daily rates, the
repetitive planning process recommends a rate equal to the fixed daily rate or a rate of
zero.
Fixed Daily Rate Multiples

Fixed lot multiples are translated into fixed daily rate multiples.
Rounded Daily Rate

Rounded order quantities are translated into rounded daily rates. Fixed days supply
has no real meaning in repetitive environments.
Safety stock and order modifiers are useful when you have repetitive assemblies that
report to discrete assemblies or discrete assemblies that report to repetitive assemblies.
Discrete Assemblies with Repetitive Components

You can use safety stock to avoid a stock out for repetitive assemblies. Although your
demand should always be satisfied by the end of each planning period, there may be
temporary shortages within the period as the schedules build up supply. If you do not
want to carry excess inventory in the form of safety stock, you may want to reduce the
size and increase the number of your repetitive planning periods. This means that there
is less smoothing of supply, resulting in suggested daily rates that more closely match
fluctuations in your demand. The best way to avoid shortages within planning periods
is to smooth your demand.
Repetitive Assemblies with Discrete Components

If you have a repetitive assembly that has a discretely planned component, then the
repetitive planning process suggests planned orders for each day in the period spanned
by the repetitive schedules for the assembly. Under these circumstances, you might
want to consider using order modifiers, such as fixed days supply, fixed lot multiple or
minimum order quantities for the discrete component. This helps to reduce the number
of planned orders generated for the discrete component.
Anchor Date
The anchor date introduces consistency into your material and distribution plans by
stabilizing your repetitive planning periods. The anchor date represents the start date of
your first repetitive planning period. The anchor date fixes your repetitive planning
periods as time passes so that a plan run on any day during the first planning period
does not see fluctuating average daily demand.
Without the anchor date, the planning periods shift each day and individual demands
can move from one planning period into the next. This can result in different average
daily demands and therefore different suggested daily rates.
Note that the actual demand never changes, it is only the time periods over which they
are averaged that move each day.
The anchor date must lie on or before the current date and is defined both manually
and automatically. You can manually enter a default anchor date as a planning
parameter. You can override the default anchor date when you plan material
requirements or when you plan your master schedules. Since the anchor date is a
system parameter, overriding the anchor date resets the system anchor date. Resetting
the anchor date always triggers a recalculation of the repetitive planning periods.
The anchor date is automatically updated to the beginning of the current planning
period when the current date moves out of a prior planning period. The anchor date is
also automatically updated when you plan material requirements, plan your master
schedules or change your repetitive planning parameters. This allows your planning
periods to be automatically rolled forward as time passes. The anchor date is always
updated to the start date of the current repetitive planning period.
Repetitive Schedule Allocation

Repetitive schedule allocation is the process by which the repetitive planning process
takes suggested aggregate repetitive schedules and allocates them across one or more
work in process production lines. After repetitive schedule allocation, the sum of all
suggested repetitive schedules for an assembly should always equal the suggested
aggregate repetitive schedule for the same assembly.
The repetitive schedule allocation process is driven by suggested aggregate repetitive
schedules, and line priorities and production rates you define in the Oracle Work in
Process window, Define Repetitive Assembly. An example of repetitive schedule
allocation is illustrated in the following diagram. The example illustrates how various
suggested aggregate rates would be divided and allocated across three production lines.
Line Priorities
In the example, lines A and B have the same line priority, 1, while line C has a line
priority of 2. You assign line priorities to help the repetitive planning process decide
which lines it should allocate repetitive schedules to. In the example, you may have
customized lines 1 and 2 to manufacture your assembly with minimum waste and
optimum speed. It may be possible, but more expensive, to also build the assembly on
line C, so you assign it a lower priority.
Production Rates
You define production rates to represent the rate at which an assembly can be
manufactured on specific production lines. Different assemblies may require different
production rates on the same production line. Similarly, the same assembly may require
different production rates on different production lines. The production rate for an
assembly, on a given production line, must fall within the minimum and maximum
hourly rates defined for the production line in the Oracle Work in Process window,
Define Production Line. The example assumes production rates of 400/hour, 200/hour
and 100/hour for lines A, B and C, respectively.
Aggregate Rate Allocation

Notice that until the aggregate rate exceeds 400/hour, the rate is distributed evenly
across lines A and B. This is because lines A and B share the same priority, which also
happens to be the highest priority defined for the assembly, and because lines A and B
have production rates of 400/hour and 200/hour respectively.
Once the rate exceeds 400/hour, line B is fully loaded. Since there is still capacity
available on line A, the repetitive schedule allocation process continues to load line A
until it too is fully loaded. It is only when both lines A and B are fully loaded that the
repetitive schedule allocation process uses the line priorities to decide which lines to use
to allocate any remaining portion of the suggested aggregate rate.
In the example, any aggregate rate between 601 and 700 units/hour is allocated to line
C. Once all lines available for building the assembly have been fully loaded, the
repetitive schedule allocation process loads any additional unallocated rates evenly
across the highest priority lines, in this case lines A and B.
Firm Repetitive Schedules

You can firm part or all of your current repetitive schedules for a repetitive assembly in
If you firm all your current repetitive schedules for an assembly in Oracle Work in
Process, the repetitive planning process considers the current aggregate repetitive
schedule to be firm. The sum of all your firm schedules for an assembly is called the
firm rate. Rather than calculating an optimal rate for assemblies with firm rates, the
repetitive planning process suggests the firm rate for the duration of the firm aggregate
schedule.
The repetitive planning process suggests the firm rate for the duration of the firm
aggregate schedule. After the firm period, the suggested rate is increased to address the
previous depletion in supply caused by the firm rate being less than the optimal rate. If
the optimal rate was less than the firm rate, the repetitive planning process decreases
the suggested rate after the firm period in response to the previous build up of supply.
As an example, the repetitive planning process is 10 units short as a result of the firm
rate. The optimal rate is 12/day. However, for the duration of the firm schedule, the
suggested rate is restricted to 10/day. This creates a shortage of 2/day for 5 days,
resulting in a total shortage of 10 units. This increases the total demand in the next
planning period from 36 to 46 units. The firm schedule breaks up two planning periods
(Periods 2 and 3) into four smaller planning periods (Periods 2, 3, 4, and 5).
Partially Firm Repetitive Schedules

If you have firmed some, but not all, of your current repetitive schedules for an
assembly, the repetitive planning process considers your current aggregate repetitive
schedule to be partially firm. The sum of all firm schedules is called the minimum firm
rate. If the optimal rate calculated by the repetitive planning process is less than the
minimum firm rate, the repetitive planning process suggests the minimum firm rate for
the duration of the partially firm aggregate schedule. If the optimal rate is greater than
the minimum firm rate, the repetitive planning process suggests the optimal rate. The
minimum firm rate acts as the floor for the suggested rates for the duration of your
partially firm aggregate schedule.
The repetitive planning process suggests the minimum firm rate for the duration of the
partially firm schedule. After the partially firm period, the suggested rate is decreased
due to the previous build up in supply caused by the minimum firm rate being greater
than the optimal rate.
As an example, the repetitive planning process has a 25 unit surplus as a result of the
minimum firm rate. The optimal rate is 10/day. However, for the duration of the
partially firm schedule, the suggested rate is restricted to 15/day. This creates a surplus
of 5/day for 5 days, resulting in a total surplus of 25 units. This reduces the total
demand in the next planning period from 30 to 5 units. The partially firm schedule
breaks up two planning periods (Periods 2 and 3) into four smaller planning periods
(Periods 2, 3, 4, and 5).
Implicit Firm Repetitive Schedules

Your repetitive assembly lead times create an implicit firm schedule. Inside the lead
time, the repetitive planning process always suggests the current aggregate rate. This is
true even if your current aggregate rate is zero. The repetitive planning process assumes
an implicit firm schedule inside your assembly lead times on the assumption that any
new suggested rates, even if implemented immediately, can only be realized as supply
outside the assembly's lead time.
The repetitive planning process suggests the current aggregate firm rate for the
duration of the assembly lead time. In the example, the current aggregate rate is 5 per
day.
After the assembly lead time, the suggested rate is increased to address the previous
depletion in supply caused by the current aggregate rate being less than the optimal
rate. The firm schedule formed by the assembly lead time breaks the first planning
period into two smaller planning periods.
Repetitive Planning Control

The repetitive planning process uses the planning time fence to help stabilize your
material plans and minimize disruption to your short term shop floor and supplier
schedules. You can control the nervousness of your repetitive material plans by
specifying minimum and maximum rate changes that are enforced by the repetitive
planning process inside the planning time fence.
Acceptable Rate Changes

There are two repetitive item attributes used by the repetitive planning process to
stabilize production inside the planning time fence. The acceptable rate increase percent
and acceptable rate decrease percent represent the percentage of the current aggregate
rate by which your suggested daily rates can vary from current aggregate rates within a
repetitive planning period inside the planning time fence.
Acceptable rate changes allow you to represent assembly constraints. For example, you
might define acceptable rate changes for a repetitive assembly to simulate the rate at
which you can realistically ramp production of the assembly up or down.
The repetitive planning process calculates acceptable rate increase amounts by
multiplying the current aggregate rate by the acceptable rate increase percent. For
example, if the current aggregate rate is 100/day and the acceptable rate increase
percent is 10%, the acceptable rate increase amount is 10/day. Inside the planning time
fence, the repetitive planning process could not suggest a daily rate greater than
110/day.
Similarly, an acceptable rate decrease amount is calculated by multiplying the current
aggregate rate by the acceptable rate decrease percent. For example, if the current
aggregate rate is 100/day and the acceptable rate decrease percent is 10%, the acceptable
rate decrease amount is 10/day. Inside the planning time fence, the repetitive planning
process could not suggest a daily rate greater than 90/day.
Acceptable Rate Increase

If the optimal rate is greater than the current aggregate rate plus the acceptable rate
increase amount, the repetitive planning process suggests a daily rate that is equal to
the current aggregate rate plus the acceptable rate increase amount. Using the earlier
example, the repetitive planning process would suggest a daily rate of 110/day for any
optimal rate greater than 110/day.
If the optimal rate is less than or equal to the current aggregate rate plus the acceptable
rate increase amount, the repetitive planning process suggests a daily rate that is equal
to the optimal rate. Using the same example, the repetitive planning process suggests a
daily rate equal to the optimal rate for any optimal rate between 100/day and 110/day.
Acceptable Rate Decrease

If the optimal rate is less than the current aggregate rate minus the acceptable rate
decrease amount, the repetitive planning process suggests a daily rate that is equal to
current aggregate rate minus the acceptable rate decrease amount. Using the earlier
example, the repetitive planning process suggests a daily rate of 90/day for any optimal
rate less than 90/day.
If the optimal rate is greater than or equal to the current aggregate rate minus the
acceptable rate decrease amount, the repetitive planning process suggests a daily rate
that is equal to the optimal rate. Using the same example, the repetitive planning
process suggests a daily rate equal to the optimal rate for any optimal rate between
90/day and 100/day.
The repetitive planning process is free to suggest any daily rate outside the planning
time fence.
Undefined acceptable rate changes remove the planning time fence since they do not
restrict the amount by which the repetitive planning process can vary suggested rates.
This is not true for zero acceptable rate changes. Zero acceptable rate changes are used
to restrict the repetitive planning process from suggesting any rate changes at all inside
the planning time fence.
Undefined values allow the repetitive planning process to suggest changes to the
current aggregate rate without restriction. Zero values prevent the repetitive planning
process from suggesting any changes at all. For example, if you choose to make the
acceptable rate increase zero and leave the acceptable rate decrease undefined, the
repetitive planning process suggests a rate between zero and the current aggregate rate,
but no greater than the current aggregate rate.
Overrun Percent
You can also use the overrun percent item attribute to control the nervousness of your
material plans by allowing current repetitive schedules to overbuild by a small amount
without incurring new suggested daily rates. In this way, planning overrun amounts
reduces minor and unnecessary rate change suggestions.
The overrun amount is equal to the optimal rate for the planning period multiplied by
the overrun percent. For example, if your optimal rate is 100/day and your overrun
percent is 10%, the repetitive planning process calculates an overrun amount of 10/day.
The repetitive planning process only recommends a new repetitive schedule if the
current aggregate rate is greater than the optimal rate plus the overrun percent.
According to the previous example, the repetitive planning process only suggests a new
repetitive schedule if the current aggregate rate is greater than 110/day.
The overrun percent for repetitive planning is analogous to acceptable early days
delivery in discrete planning. Both attributes allow you to make the business decision
that you would prefer to carry additional inventory for a short time, rather than disrupt
your shop floor production schedules.
It is important to note that the overrun percent only applies for overproduction. As with
acceptable early days delivery, the repetitive planning process allows you to build
ahead and carry excess inventory, but does not allow you to plan a shortage. Because
the overrun percent often results in overproduction within planning periods, use of this
attribute can sometimes have an impact on subsequent planning periods. Later periods
may need to produce less as a result of the excess supply produced in earlier periods.
Repetitive Schedule Relief

Master production schedules represent build schedules, or statements of planned
production.
Each time you implement a portion of your master production schedule as a discrete job
or a purchase requisition, you are creating actual supply. To avoid overstating supply,
you need to relieve your planned supply by the quantity you have implemented as
actual supply.
For discrete assemblies, total supply is considered by the planning process to be the
sum of your master production schedules plus the scheduled receipts defined in Oracle
Work in Process and Purchasing. With discrete planning, there are two versions of
supply that must be kept in balance to avoid overstatement of supply.
For repetitive assemblies, however, master production schedules are not summed with
current work in process repetitive schedules. With repetitive planning, these two
versions of supply are compared and contrasted, and represent two alternative
statements of supply rather than two components that are summed together.
Therefore, with repetitive planning, there is only one version of supply and therefore no
need to keep two complementing versions in balance. For this reason, there is no
production relief for repetitive master production schedules.
Repetitive Schedule Implementation

You can use the Planner Workbench to implement your suggested repetitive schedules
as repetitive schedules in Oracle Work in Process. The default status for a repetitive
schedule loaded from the Planner Workbench is Pending mass loaded. When
implementing your repetitive schedules, you can choose to implement selected
schedules as firm repetitive schedules. You can additionally modify the first and last
unit completion dates, daily rates and the processing days suggested by the repetitive
planning process. You can also override the production lines that were assigned to your
suggested repetitive schedules during the repetitive schedule allocation process.
11
Reports
Overview of Reports
This section explains how to submit report requests and briefly describes each MRP
report. For additional information on capacity reports and processes, see Reports, Oracle
Capacity User Guide.
Audit Information Report

The Audit Information Report displays the number of incidents retrieved by a
particular audit statement and occurrences of data that are retrieved by an audit
statement.
Report Submission
In the Submit Requests window, enter Audit Information Report in the Name field.
Report Parameters
Show
Choose one of the following options:
Errors only: Report information that can cause your

concurrent program to fail.
Warnings and errors: Report information that can cause

your concurrent program to fail, as well as information
that does not cause your concurrent program to fail,
but is still questionable data.
Warnings only: Report information that does not cause

your concurrent program to fail, but is still
questionable data.
Reports 11-1
Application
Enter the application for which to run the audit.
Audit
Accounting period start dates that do not fall on week start

dates: Identify accounting period start dates that do not
fall on week start dates.
All audits: Identify the nature of all suspected incidents.

If there are any incidents, you can use the other choices
in this form for a more detailed audit that pinpoints the
exact occurrence of the incident.
Duplicate suppliers: Identify duplicate supplier entries.
Bills common to non-existent bills: Identify bills that are

common references to non-existent bills.
Bills common to other bills with different alternate

designator: Identify bills that are common references to
other bills that have a different alternate designator.
Bills in bom_inventory_components but do not exist in

bom_bill_of material: Identify components on bills that
do not have a valid bill of material.
Bills that are buy items: Identify bills that have an item
planning attribute of Buy.
Bills that do not exist in the item master: Identify bills that
do not exist in the item master.
Bills that exist in both manufacturing and engineering:

Identify bills that exist in both manufacturing and
engineering.
Bills with BOM enabled flag set to No: Identify bills that
have their BOM enabled flag set to No.
Bills with no components: Identify bills with no

components.
Capacity modifications that add already existing workdays:

Identify capacity modifications that add workdays that
already exist in the workday calendar.
Components that do not exist in item master: Identify
components that do not exist in the item master.
Components with BOM enable flag set to No: Identify

components that have their BOM enabled flag set to
No.
Components with incorrect number of reference designators:

Identify components on bills of material that have the
incorrect number of reference designators.
Components with revised_item_sequence_ids that do not

exist in eng_revised_items: Identify components with
revised item sequence numbers that do not exist for
engineering revised items.
Components with zero usage quantity: Identify

components that do not have a usage quantity.
Costed items not assigned to the costing category set:

Identify costed items that are not assigned to a costing
category set.
Costed items with no frozen costs: Identify asset items

with no frozen costs.
ECOs with no schedule date: Identify engineering change

orders that do not have a schedule date.
ECOs have future implementation dates: Identify

engineering change orders that have future
implementation dates.
Forecast entries with a zero confidence percent: Identify

forecast entries with a zero confidence percent.
Forecasted items that are not planned and are not planning
items or models: Identify forecasted items that are not
planned and are not planning items or models.
Items that are MRP or MPS planned but with no planning

exception set: Identify items that are MRP or MPS
planned but do not have a planning exception set.
Items that are not planned: Identify items with no

planning type.
Items that are planned as buy but are not purchasable:
Reports 11-3
Identify items that have an item planning attribute of

Buy but are not purchasable.
Items that are planned as make but are not made in WIP:
Identify items that have an item planning attribute of
Make but are not buildable in work in process.
Items that are planned but not in the planning category set:
Identify items that are planned but are not in the
planning category set.
Items that do not have revisions: Identify items that do not

have revisions.
Items that have incorrect summary costs: Identify items

whose summary costs do not agree with the detailed
cost information.
Items with an invalid shrinkage: Identify items with an

invalid shrinkage factor.
Op res with autocharge of PO Move or PO Receipt and no

location: Identify resources assigned to operations with
an autocharge type of PO move or PO receipt that do
not have a location.
Op res with autocharge of PO Move or PO Receipt and

negative usage rates: Identify resources assigned to
operations with an autocharge type of PO move or PO
receipt that have negative usage rates.
Operation sequences that use invalid resources: Identify

operation sequences that use invalid resources.
Operations that have lead time percents or offset percents

exceeding 100%: Identify operations where lead time
and offset percents exceed 100%.
Operations with non-existent routing_sequence_ids:

Identify operations with non-existent routing
sequences.
Planned items with no gross requirements or scheduled

receipts: Identify planned items with no gross
requirements or scheduled receipts.
Planned items with zero full lead time: Identify MPS and
MRP planned items where the sum of their pre, post,

and processing lead times equals zero.
Planned make items with postprocessing lead time: Identify

items with an item planning attribute of Make with
postprocessing lead time.
Planned, purchased bills ignored by MRP: Identify

planned and purchased bills that the planning process
ignores.
Planning organizations with invalid quarterly calendar

types: Identify organizations whose quarterly calendar
has twelve periods per year, based on calendar months.
Repetitive items with pre or postprocessing lead time:

Identify repetitive parts with preprocessing or
postprocessing lead time.
Repetitive master schedule entries with invalid work dates:

Identify repetitive master schedule entries with invalid
workdays.
Repetitive planning flag in mtl_system_items is null:

Identify items that do not have a value for the
repetitive planning item attribute.
Repetitively planned purchased components: Identify

repetitively planned components that are purchased.
Routings common to non-existent routings: Identify

routings that are common to non-existent routings.
Routings common to other routings with different alternate

designator: Identify routings that are common
references to other routings that have a different
alternate designator.
Routings that exist in both manufacturing and engineering:

Identify routings that exist in both manufacturing and
engineering.
Routings with zero processing time: Identify routings

with zero processing time.
Routings without corresponding revisions: Identify

routings without corresponding revisions.
Reports 11-5
Summary
Rows that errored in the table MRP_RELIEF_INTERFACE:

Identify rows that failed in the
MRP_RELIEF_INTERFACE table.
Rows that failed in MRP_LOAD_PARAMETERS:

MRP_LOAD_PARAMETERS table.
Rows that failed in MRP_SALES_ORDER_UPDATES:

MRP_SALES_ORDER_UPDATE table.
Rows that failed in the forecast interface table: Identify

rows that failed in the forecast interface table.
Rows that failed in the schedule interface table: Identify

rows that failed in the schedule interface table.
Schedule date rows with sales order orig that have null
source sales order id: Identify schedule date rows with
sales order origination that do not have a source sales
order identifier.
Schedule entries for discrete items no original quantities:

Identify master schedule entries for discrete items with
no original quantities.
Schedule entries for discrete items end date: Identify master

schedule entries for discrete items with end dates.
Schedule entries for repetitive items with no end date:

Identify master schedule entries for repetitive items
with no end dates.
Scheduled items that are not planned: Identify master

schedule entries that are not planned.
Standard operations which use invalid resources: Identify

standard operations that use invalid resources.
No: Report a list of the items that match your audit. For
example, if you entered All audits in the Audit field,
Oracle MRP prints a list of the items that are discretely
planned, but have a schedule entry with a start date, a
rate, and an end date.
Yes: Report a list of the items that match your audit and
can cause your concurrent program to fail, and a count
of the items that match your audit that does not cause
your concurrent program to fail, but is still
questionable data. For example, if you entered All
audits in the Audit field, Oracle MRP prints a list of the
items that are discretely planned, but have a schedule
entry with a start date, a rate, and an end date. It also
prints a count of the items that are not planned.
Related Topics
Overview of Concurrent Processing, Oracle Applications Developer's Guide
Current Projected On Hand vs. Projected Available Graphical Report for

The Current Projected On Hand vs. Projected Available Graphical Report is a graphical
report of current projected on hand versus projected available inventory for a DRP,
MPS, or MRP plan. This report is printed in line chart format. You can use this report to
gauge trends in projected on-hand quantities over long periods of time.
Note: If your plan was run with the Memory-based Planning Engine,
by-products (negative usage) are included in the calculation of

demand, current projected on hand, and current projected available.
Report Submission
In the Submit Requests window, enter Current Projected On Hand vs. Projected
Available Graphical Report in the Name field. Supply Chain Planning users should
enter Supply Chain Current Projected On Hand vs. Projected Available Graphical
Report in the Name field.
Report Parameters
Plan Name
Select a plan name.
Organization Selection -SUPPLY CHAIN PLANNING
Select the planned organization (all or current) if this is a

supply chain report. You can select All Organizations for a
multi-org plan if you are working in the organization that
owns the plan; otherwise, you can select only the current
organization and report current projected on hand versus
projected available inventory pertaining to the current
Reports 11-7
organization.
First Sort
Second Sort
Select one of the following options. The report sorts items

first in this order, then in the order you specify for Second
Sort and Third Sort.
ABC class: Sort items first by ABC class.
Buyer: Sort first by buyer.
Category: Sort first by material category.
Inventory item: Sort first by inventory item.
Organization: Sort first by organization.
No sort: Do not employ a first sort for the report.
Planner: Sort first by planner.
Select the second sort type for the item. Items are sorted by
the First Sort type and then by this sort type within the first
type.
Note: If you choose No sort here, the
report is soreted using just hte First Sort

type.
Third Sort
Select the third sort type for the item. Items are sorted 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.
For example, if you choose Planner as the First Sort type,
Category as the Second Sort type, and Inventory item as
the Third Sort type, the report is sorted by planner, then by
material category within planner, and finally by inventory
item within material category.
Note: If you choose No sort here, Oracle
MRP sorts the report using just the first

and second sort types.
Exception Type
Choose one of the following exception types:
Item has a shortage: Report all items whose quantity on
hand is less than the sum of the requirements plus

safety stock within the exception time fence.
Item has excess inventory: Report all items whose

quantity on hand exceeds the total requirements
against the item within the exception time fence.
Item has no activity: Report all items that have no

demand or supply in the current plan.
Item has orders to be cancelled: Report all items that the

planning process recommends be cancelled.
Item has orders to be rescheduled in: Report all items that

the planning process recommends be rescheduled in.
Item has orders to be rescheduled out: Report all items that

the planning process recommends be rescheduled out.
Item has orders with compression days: Report all items

that have planned orders, discrete jobs and purchase
orders that have compression days.
Item has a repetitive variance: Report all repetitive items

that have a variance in the amount that you actually
manufacture and the amount that the planning process
suggests you manufacture up to the exception date.
Item has past due orders: Report all items that have past
due orders.
Item is overcommitted: Report all items for which ATP is

negative or below safety stock within the exception
time fence.
Planner
Select a planner to sort the items by.
Buyer
Select a buyer to sort the items by.
Items From/To
To restrict the report to a range of items, enter the

beginning and ending item numbers.
Category Set
Enter a category set. Oracle MRP reports items associated

with this category set.
Categories From/To
To restrict the report to a range of categories, enter the

beginning and ending category names.
Reports 11-9
ABC Assignment Group
Select an ABC assignment group. Items associated with this

ABC assignment group are included in this report.
ABC Class
Select an ABC class associated with the ABC assignment

group.
Related Topics
Demand vs. Replenishment Graphical Report for Supply Chain Planning

The (Supply Chain) Demand vs. Replenishment Graphical Report is a graphical,
summary report of material availability for a DRP, MRP, or MRP plan. This report is
printed in line chart format. Cumulative replenishments plus the quantity on hand and
cumulative demand in buckets of one week are included. You can use this report to
gauge trends in projected on-hand quantities over long periods of time, such as
analyzing repetitively planned items or discrete items that are components of
repetitively planned items.
Note: If your plan was run with the Memory-based Planning Engine,
by-products (negative usage) are included in the calculation of

demand, current projected on hand, and current projected available.
Report Submission
In the Submit Requests window, enter Demand vs. Replenishment Graphical Report in
the Name field. Supply Chain Planning users should enter Supply Chain Demand vs.
Replenishment Graphical Report in the Name field.
Report Parameters
Plan Name
Select a plan name.
Organization Selection

organization and report material availability pertaining to
the current organization.
First Sort

first in this order, then in the order you specify for Second
Sort and Third Sort
Second Sort
Select the second sort type for the item. Oracle MRP sorts
the items by the first sort type and then by this sort type
within the first type.
If you choose No sort, the report is sorted by using just the
First Sort type.
Third Sort
Select the third sort type for the item. Oracle MRP sorts the
items 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.
For example, if you choose Planner as the first sort type,
Category as the second sort type, and Inventory item as the
third sort type, the report is sorted by planner, then by
material category within planner, and finally by Inventory
first and second sort types.
Exception Type
Choose one of the following exception types:
Item has a shortage: Report all items whose quantity on

hand is less than the sum of the requirements plus
safety stock within the exception time fence.
Item has excess inventory: Report all items whose

quantity on hand exceeds the total requirements
against the item within the exception time fence.
Item has no activity: Report all items that have no

demand or supply in the current plan.
Reports 11-11
Item has orders to be cancelled: Report all items that the

planning process recommends be cancelled.
Item has orders to be rescheduled in: Report all items that

the planning process recommends be rescheduled in.
Item has orders to be rescheduled out: Report all items that

the planning process recommends be rescheduled out.
Item has orders with compression days: Report all items

that have planned orders, discrete jobs and purchase
orders that have compression days.
Item has a repetitive variance: Report all repetitive items

that have a variance in the amount that you actually
manufacture and the amount that the planning process
suggests you manufacture up to the exception date.
Item has past due orders: Report all items that have past
due orders.
Item is overcommitted: Report all items for which ATP is

negative or below safety stock within the exception
time fence.
Planner
Select a planner to sort the items by.
Buyer
Select a buyer to sort the items by.
Items From/To

Category Set
Enter a category set. Oracle MRP reports items associated

with this category set.
Categories From/To

Select an ABC assignment group. Oracle MRP reports

items associated with this ABC assignment group.
ABC Class

group.
Related Topics
Financial Analysis Report for Supply Chain Planning

The (Supply Chain) Financial Analysis Report displays a costed picture of the DRP or
MRP plan. Based on the DRP or MRP plan, this report includes the total material value
(in thousands of dollars) of actual and planned purchases, the total labor and overhead
value of actual and planned work in process, the total value of the master demand or
master production schedule, and ending inventory balances.
You can use this report to help plan the corresponding monetary resources necessary to
fulfill the DRP or MRP plan. You can choose how many weeks and months to display in
the report. This report also shows the number of inventory turns for each period and
the cumulative number of turns from the beginning of the report up to the current
period. For the purposes of the report, inventory turnover is defined as the master
schedule value divided by the average inventory value.
Note: This report includes any partially completed work in process
values in inventory, where work in process value represents money to

be spent. Purchasing commitments include: purchase orders, purchase
requisitions, and planned orders for purchased items. Work in process
commitments include: discrete jobs, repetitive schedules, and planned
orders for manufactured items.
This report also shows projected inventory turnover for each period and cumulative,
defined as the average inventory value divided by the master schedule value (which
approximates cost of sales).
Important: All calculations include asset items held in nettable expense
subinventories. This increases the accuracy of cash forecasting.
Report Submission
In the Submit Requests window, enter Financial Analysis Report in the Name field.
Supply Chain Planning users should enter Supply Chain Financial Analysis report in
the Name field.
Report Parameters
Plan Name
Select a plan name.

organization and report costs pertaining to the current
Reports 11-13
organization.
Periods
Weeks
Choose one of the following time periods:
12: Report the MRP financial plan for 12 periods.
Enter the number of weeks. The number of Weeks you

choose, together with the number of Periods you choose,
determines how many weeks and how many months that
display in the horizontal time-phased plan.
For example, if you choose 24 as the time Period and 10 as
the number of Weeks, 10 of these periods display as weeks,
the remaining 14 as months.
Note: The number of weeks that displays
in the List of Values is based on the

workday calendar and corresponds to the
end of the working periods. For example, if
you choose 12 as the time Period and it is
the third week of a four week period
calendar, Oracle MRP calculates the
number of weeks to the end of each period
and displays the valid List of Values
options as 1, 5, and 9 weeks.
Cost Type
Select a cost type to print a costed picture of the DRP or

MRP plan for the items associated with this cost type.
Related Topics
Forecast Comparison Report

The Forecast Comparison Report displays a comparison of forecast quantities and costs
or quantities only. You can choose the number of periods and weeks for which to run
the report. You can report all items or a range of items associated with the forecast
name. You can also compare the costs of the forecast quantities.
Report Submission
In the Submit Requests window, enter Forecast Comparison Report in the Name field.
Report Parameters
Forecast Name
Select a forecast name to compare its forecast to the forecast

quantities of the second forecast name.
First Quantities
Select one of the following options:
Current: Print forecast comparison information using

current forecast quantities.
Original: Print forecast comparison information using

original forecast quantities.
Second Organization
Select the organization of the second forecast to compare to

the forecast from your current organization.
Second Forecast Name
Select a forecast name to compare its forecast to the first

forecast name.
Second Quantities


Report Start Date
Enter a report start date from which to print the forecast

comparison.
Periods
Choose one of the following time periods:
Weeks

Reports 11-15


Include Costs
Include Before Start Date
First Sort
No: Report the comparison information by units rather

than value (standard cost times units).
Yes: Report the comparison information by value

(standard cost times units) in addition to units.
No: Do not display forecast entries, bucketed in the first

bucket, before the start date you enter.
Yes: Display forecast entries, bucketed in the first


first in this order, then in the order you specify for the
second and third sort.

Second Sort
type.
For example, if you choose Planner as the first sort type and
Category as the second sort type. Oracle MRP sorts the
report by planner, and then by material category within
planner.
Note: If you choose No sort here, the reort
is sorted using just the First Sort type.

First Sort type.
Third Sort
second type.
Planner
Select a planner to report items planned by this planner.
Buyer
Select a buyer to report items planned by this buyer.
Items From/To
To restrict the report to a range of items, select the

Category Set
Select a category set. Oracle MRP reports forecast entries

associated with this category set.
Categories From/To


forecast entries associated with this ABC assignment
group.
Reports 11-17
ABC Class

group.
Related Topics
Forecast Detail Report

The Forecast Detail Report displays information for the forecast set or forecast within a
set you specify. You can choose the number of periods and weeks for which to run the
report. You can display the data by horizontal time phased display, by vertical display,
or by both. You can report all items or a range of items associated with the forecast
name.
Note: The Annual Projected Demand is calculated as the demand for
the period multiplied by the periods per year. The demand for the
period is the sum of the demand for up to one year. If there is more
than one year of demand, then it is not included in the calculation. The
period is the length of time between the plan date and the last demand
date. If there is more than one year of demand, then the period is one
year.
Report Submission
In the Submit Requests window, enter Forecast Detail Report in the Name field.
Report Parameters
Forecast Name
Select a forecast name for which you want to report item

forecast information.
Quantities
Display


Both horizontal and vertical: Display the forecast as a

horizontal timephased and vertical listing. The
horizontal timephased listing displays the future

forecast requirements, from today forward to the cutoff
date, bucketed for the periods and number of weeks
you specify. The vertical listing displays the past
(historical) forecast requirements in detail up to the
cutoff date.
Report Start Date
Enter a report start date from which Oracle MRP prints the
forecast. This restricts the information in the vertical
display and the detail sections of the report.
Periods
Weeks
12: Report the forecast for 12 periods.


Include Costs
No: Report the comparison information by units rather

than value (standard cost times units).
Reports 11-19
First Sort
Second Sort
Yes: Report the comparison information by value

(standard cost times units) in addition to units.
No: Do not display forecast entries, bucketed in the first

Yes: Display forecast entries, bucketed in the first


first in this order, then in the order you specify for the
second and third sort.
type.
For example, if you choose Planner as the first sort type and
Category as the second sort type. Oracle MRP sorts the
report by planner, and then by material category within
planner.
Note: If you choose No sort here, the
report is sorted using just the First Sort

type.

First Sort type.
Third Sort
second type.

Planner
Select a planner to report items planned by this planner.
Buyer
Select a buyer to report items planned by this buyer.
Items From/To

Category Set
Select a category set. Oracle MRP reports forecast entries

associated with this category set.
Categories From/To


forecast entries associated with this ABC assignment
group.
ABC Class

group to report only items in that class.
Cutoff Date
Select a cutoff date up to which Oracle MRP prints the

forecast. This restricts the information in the vertical
display and the detail sections of the report.
Related Topics
Late Order Report for Supply Chain Planning

The (Supply Chain) Late Order Report displays purchase orders, purchase requisitions,
intransit shipments, discrete jobs, and planned orders past due for a plan name that you
specify. You can use this report to identify events that will be late.
Report Submission
In the Submit Requests window, enter Late Order Report in the Name field. Supply
Chain Planning users should enter Supply Chain Late Order Reports in the Name field.
Reports 11-21
Report Parameters
Plan Name
Enter a plan name.
Select the planned organization (all or current) if this is a supply chain report. You can
select All Organizations for a multi-org plan if you are working in the organization that
owns the plan; otherwise, you can select only the current organization and report past
due information pertaining to the current organization.
Advance Notice Date
Enter a date to report the events that will be late as suggested by the planning process.
For example, if it is 11-JAN and you enter 15-JAN, the events that will be late within the
next 5 days (before 15-JAN) are reported. When you choose the current date, all events
that will be late as of tomorrow are reported; in other words, those orders that require
some action today.
Sort
ABC class Sort items first by ABC class.
Buyer Sort first by buyer.
Category Sort first by material category.
Inventory item Sort first by inventory item.
No sort Do not employ a first sort for the report.
Organization Sort first by organization.
Planner Sort first by planner.
Planner
Select a planner to report only orders associated with this planner.
Buyer
Select a buyer to report only orders associated with this buyer.
Items From/To
To restrict the report to a range of items, enter the beginning and ending item numbers.
Category Set
Select a category set. Oracle MRP reports forecast entries associated with this category
set.
Categories From/To
To restrict the report to a range of categories, enter the beginning and ending category
names.
Select an ABC assignment group. Oracle MRP reports past due orders associated with
this ABC assignment group.
ABC Class
Select an ABC class associated with the ABC assignment group.
Categories From/To
See Also
Master Schedule Comparison Report

The Master Schedule Comparison Report compares master schedule quantities and
costs. For example, you can compare the master schedule quantities of different
versions of the same master schedule. You can compare the original schedule entries,
the current schedule entries, or the entries that you last submitted.
Report Submission
In the Submit requests window, enter Master Schedule Comparison Report in the Name
field.
Report Parameters
First Schedule: Select a master schedule to compare its schedule quantities to the
schedule quantities of the of the second schedule name.
First schedule version: Select one of the following options:
Current: Report the current version of the master demand or master production
schedule. When you first define a schedule, Oracle MRP creates a current version
and an original version that are identical. As you add new schedule entries, these
entries are added to both versions, keeping them consistent/ However, when you
change existing schedule entries, only the current schedule is updated.
Last submitted to MPS/MRP: Report the version of the schedule you last submitted
to the MRP or MPS. When you run the MRP or MPS, the current version is copied
to this version and is used as input to the planning process. After the MRP or MPS
is run, this version of the schedule is saved so that you can compare it to the
original version or to any changes you make to the new current version.
Reports 11-23
Original: Report the original version of the schedule. As noted, Oracle MRP only
updates this version when you add new entries to the schedule. Updates to existing
scheduling entries do not affect this version.
First Quantities: Select one of the following options:
Current: Print master schedule comparison information using current master

schedule quantitles.
Original: Print master schedule comparison information using original master

schedule quantities.
Second Organization: Select the organization of the second master schedule to compare
to the master schedule from your current organization.
Second Schedule: Select a master schedule to compare its schedule quantities to the first
schedule name. You can only choose a schedule of the same type as the first schedule
name.
Second Schedule Version
Current: Use the current version of the master demand or master production
schedule. When you first define a schedule, Oracle MRP creates a current version
and an original version that are identical. As you add new schedule entries, these
entries are added to both versions, keeping them consistent/ However, when you
change existing schedule entries, only the current schedule is updated.
Last submitted to MPS/MRP: Report the version of the schedule you last submitted
to the MRP or MPS. When you run the MRP or MPS, the current version is copied
to this version and is used as input to the planning process. After the MRP or MPS
is run, this version of the schedule is saved so that you can compare it to the
original version or to any changes you make to the new current version.
Original: Use the original version of the schedule. As noted, Oracle MRP only
updates this version when you add new entries to the schedule. Updates to existing
scheduling entries do not affect this version.
Second Quantities:
Current: Print master schedule comparison information using current master

schedule quantitles.
Original: Print master schedule comparison information using original master

schedule quantities.
Report Start Date: Enter a report start date from which Oracle MRP prints the master
schedule comparison.
Periods: Select one of the following options:
12: Report the forecast for 12 periods
Weeks: Enter the number of weeks. The number of weeks you choose, together with the
number of periods you choose, determines how many weeks and how many months
that display in the horizontal time-phased plan. For example, if you choose 24 as the
time Period and 10 as the number of weeks, 10 of these periods display as weeks, the
remaining 14 as months.
The number of weeks that displays in the List of Values is based on the workday
calendar and corresponds to the end of the working periods. For example, if you choose
12 as the time Period and it is the third week of a four week period calendar, Oracle
MRP calculates the number of weeks to the end of each period and displays the valid
List of Values Options as, 1, 5, and 9 weeks.
Include Costs: Select one of the following options:
No: Report the comparison information by units rather than value (standard cost
times units).
Yes: Report the comparison information by value (standard cost times units) in
addition to units.
Include Before Start Date: Select one of the following options:
No: Do not display forecast entries, bucketed in the first bucket, before the start date
you enter.
Yes: Display forecast entries, bucketed in the first bucket, before the start date you
enter.
First Sort: Select one of the following options. The report sorts items first in this order,
then in the order you specify for the second and third sort:
ABC class: Sort items first by ABC class
Buyer: Sort first by buyer
Category: Sort first by material category
Inventory item: Sort first by inventory item
No sort: Do not employ a first sort for the report
Planner: Sort first by planner
Second Sort: Select the second sort type for the item. Items are sorted by the First Sort
Reports 11-25
type and then by this sort type within the first type. For example, if you choose Planner
as the first sort type and Category as the second sort type. Oracle MRP sorts the report
by planner, and then by material category within planner.
Third Sort: Select the third sort type for the item. Oracle MRP sorts the items 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. For example, if you choose Planner as the first sort type,
Category as the second sort type, and Inventory item as the third sort type, the report is
sorted by planner, then by material category within planner, and finally by Inventory
item within material category. If you choose No sort, the report is sorted by using just
the first and second sort types.
Planner: Select a planner to report master schedule entries associated with this planner.
Buyer: Select a buyer to report master schedule entries associated with this buyer.
Items From/To: To restrict the report to a range of items, enter the beginning and
ending item numbers.
Category Set: Select a category set. Oracle MRP reports forecast entries associated with
this category set.
Categories From/To: To restrict the report to a range of categories, enter the beginning
and ending category names.
ABC Assignment Group: Select an ABC assignment group. Oracle MRP reports master
schedule entries associated with this ABC assignment group.
ABC Class: Select an ABC class associated with the ABC assignment group.
See also Submitting a Request in Oracle Applications User's Guide.
Master Schedule Detail Report

The Master Schedule Detail Report displays master demand or master production
schedule information. You can report the original schedule entries, the current schedule
entries, or the entries you last submitted to the MRP planning process. You can choose
the number of periods and weeks for which to run the report. You can display the data
by horizontal time phased display, by vertical display, or both. You can report all items
or a range of items associated with the plan name.
Note: The Annual Projected Demand is calculated as the demand for
the period multiplied by the periods per year. The demand for the
period is the sum of the demand for up to one year. If there is more
than one year of demand, then it is not included in the calculation. The
period is the length of time between the plan date and the last demand
date. If there is more than one year of demand, then the period is one
year.
Report Submission
In the Submit Requests window, enter Master Schedule Detail Report in the Name field.
Report Parameters
Schedule Name
Schedule Version
CurrentReport the current version of the master demand or master production schedule.
Note: When you first define a schedule, Oracle MRP creates a current
version and an original version that are identical. As you add new
schedule entries, these entries are added to both versions, keeping them
consistent. However, when you change existing schedule entries, only
the current schedule is updated.
Last submitted to MPS/MRP Report the version of the schedule you last submitted to the
MRP or MPS.
Note: When you run the MRP or MPS, the current version is copied to
this version and is used as input to the planning process. After the MRP
or MPS run, this version of the schedule is saved so that you can
compare it to the original version or to any changes you make to the
new current version.
OriginalReport original version of the schedule. As noted, Oracle MRP only updates this
version when you add new entries to the schedule. Updates to existing scheduling
entries do not affect this version.
Quantities
Current: Print master schedule comparison information using current master schedule
quantities.
Original: Print master schedule comparison information using original master schedule
quantities.
Display
Both horizontal and vertical Display the forecast as a horizontal timephased and vertical
listing. The horizontal timephased listing displays the future forecast requirements,
Reports 11-27
from today forward to the cutoff date, bucketed for the periods and number of weeks
you specify. The vertical listing displays the past (historical) forecast requirements in
detail up to the cutoff date.
Horizontal time phased: Display the forecast as a horizontal timephased listing.
Vertical: Display the forecast as a vertical listing.
Report Start Date
Enter a report start date from which Oracle MRP prints the master schedule
comparison.
Periods
Weeks
Enter the number of weeks. The number of Weeks you choose, together with the
number of Periods you choose, determines how many weeks and how many months
that display in the horizontal time-phased plan.
For example, if you choose 24 as the time Period and 10 as the number of Weeks, 10 of
these periods display as weeks, the remaining 14 as months.
Note: The number of weeks that displays in the List of Values is based
on the workday calendar and corresponds to the end of the working

periods. For example, if you choose 12 as the time Period and it is the
third week of a four week period calendar, Oracle MRP calculates the
number of weeks to the end of each period and displays the valid List
of Values options as 1, 5, and 9 weeks.
Include Costs
No: Report the comparison information by units rather than value (standard cost times
units).
Yes: Report the comparison information by value (standard cost times units) in addition
to units.
No: Do not display forecast entries, bucketed in the first bucket, before the start date
you enter.
Yes: Display forecast entries, bucketed in the first bucket, before the start date you enter.
First Sort
Select one of the following options. The report sorts items first in this order, then in the
order you specify for the second and third sort.
ABC Class: Sort items first by ABC class.
Buyer:Sort first by buyer.
Inventory Item: Sort first by inventory item.
No Sort: Do not employ a first sort for the report.
Second Sort
Select the second sort type for the item. Items are sorted by the First Sort type and then
by this sort type within the first type.
For example, if you choose Planner as the first sort type and Category as the second sort
type. Oracle MRP sorts the report by planner, and then by material category within
planner.
Note: If you choose No sort here, the report is sorted using just the First
Sort type.
Third Sort
Select the third sort type for the item. Oracle MRP sorts the items 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.
For example, if you choose Planner as the first sort type, Category as the second sort
type, and Inventory item as the third sort type, the report is sorted by planner, then by
material category within planner, and finally by Inventory item within material category.
If you choose No sort, the report is sorted by using just the first and second sort types.
Planner
Select a planner to report and associate master schedule entries.
Buyer
Select a buyer to report and associate master schedule entries.
Items From/To
Category Set
Reports 11-29
Select a category set to report and associate forecast entries.

Categories From/To
names.
Select an ABC assignment group. Oracle MRP reports master schedule entries
associated with this ABC assignment group.
ABC Class
Cutoff Date
Select a cutoff date up to which Oracle MRP prints the master schedule. This restricts
the information in the vertical display and the detail sections of the report.
See:
Master Schedule Status Report for Supply Chain Planning

The (Supply Chain) Master Schedule Status Report displays shipping activity against a
master demand schedule or multi-org plan, or production activity against a master
production schedule. You can group the items on the report by category set or
inventory item. You can report the original schedule entries, the current schedule
entries, or the entries you last submitted to a DRP, MPS, or MRP plan.
Report Submission
In the Submit Requests window, enter Master Schedule Status Report in the Name field.
Supply Chain Planning users should enter Supply Chain Schedule Status Report in the
Name field.
Report Parameters
Schedule Name
owns the plan; otherwise, you can select only the current organization and report
shipping/production activity pertaining to the current organization.
Schedule Version

Current Report current version of the master demand or master production schedule.
Note: Oracle MRP creates a current version and an original version that
are identical. As you add new schedule entries, these entries are added
to both versions, keeping them consistent. However, when you change
existing schedule entries, only the current schedule is updated.
Last submitted to Report the version of the schedule you last MPS/MRP submitted to the
MRP or MPS.
Note: When you run the MRP or MPS, the current version is copied to
this version, and is used as input to the planning process. After the
MRP or MPS run, this version of the schedule is saved so that you can
compare it to the original version or to any changes you make to the
new current version.
OriginalReport the original version of the schedule. As noted, Oracle MRP only updates
this version when you add new entries to the schedule. Updates to existing scheduling
entries do not affect this version.
Start Date
Enter a past or the current date to report activity for the schedule name, for the day,
week, and month, beginning on this date.
Periods
Weeks

Reports 11-31
Sort
Category: Report activity by category and then by inventory item within the category.
Inventory item: Report activity by inventory item.
Items From/To
Category Set
set.
Categories From/To
names.
See
Planning Manager Worker once-a-day tasks

The Planning Manager Worker (once-a-day tasks) submits planning manager
once-a-day tasks worker. This program performs clean up tasks and auto-reduces the
master production schedule.
Process Submission
In the Submit Requests window, enter Planning Manager Worker (once-a-day tasks) in
the Name field. See: Submitting a Request, Oracle Applications User's Guide.
Planning Parameters Report

The Planning Parameters Report displays your setup parameters.
Report Submission
In the Submit Requests window, enter Planning Parameters Report in the Name field.
See: Submitting a Request, Oracle Applications User's Guide.
Planning Parameters Report

The Planning Parameters Report displays your setup parameters.
Report Submission
In the Submit Requests window, enter Planning Parameters Report in the Name field.
See: Submitting a Request, Oracle Applications User's Guide.
CRP Reports
You can launch the following reports from MRP modules:
CRP Rate Based Report
CRP Routing Based Report
RCCP Rate Based Report
RCCP Routing Based Report
The CRP Rate Based Report shows a breakdown of required rate coming from four
possible sources: planned orders, non-standard jobs, discrete jobs, and repetitive
schedules. The RCCP Rate Based Report does not contain this detail information.
Because RCCP by nature is an estimate of resources required, a detailed breakdown of
required rate is not included in the report.
Order Reschedule Report for Supply Chain Planning

The (Supply Chain) Order Reschedule Report displays discrete jobs, purchase orders,
and purchase requisitions that the DRP, MPS, or MRP planning process recommends
you reschedule, based on a plan name you specify.
Report Submission
In the Submit Requests window, enter Order Reschedule Report in the Name field.
Supply Chain Planning users should enter Supply Chain Order Reschedule Report in
the Name field.
Report Parameters
Plan Name
Select a plan name.
Reports 11-33
Organization Selection - Supply Chain Planning

planning information pertaining to the current organization.
Order Type
All: Report all discrete jobs, purchase orders, and purchase requisitions the MRP or
MPS planning process recommends to reschedule.
Discrete job: Report the discrete jobs the MRP or MPS planning process recommends to
reschedule.
Purchase order: Report the purchase orders the MRP or MPS planning process
recommends to reschedule.
Purchase requisition Report the purchase requisitions the MRP or MPS planning process
recommends to reschedule.
Sort
ABC class Sort the orders by item within an ABC class.
Buyer Sort the orders by item within a buyer.
You can choose this option only if you specified
Purchase order or Purchase requisition as the Order Type.
Category
Sort the orders by item within a category.
Inventory item
Sort the orders by inventory item.
Order number
Sort the orders by order identifier.
Organization
Sort first by organization.
Planner
Sort the orders by item within planner.
Supplier
Sort the orders by supplier.
Note: You can choose this option only if you specified
Purchase order or Purchase requisition as the Order Type.
Out Days Filter

Enter the number of reschedule out days to filter entries that are displayed on the
report. Use 0 days to allow the planning process to report all orders suggested for
rescheduling.
Oracle MRP compares the current purchase or work in process due date with the
suggested due date. It then uses reschedule out days when the current purchase or
work in process due date is earlier than the suggested due date. If the difference
between the purchase or work in process due date and the suggested due date is less
than or equal to the reschedule out days, the reschedule report excludes those orders.
For example, if the suggested due date is 07-JUN, the purchase order date is 04-JUN
and you specify 3 or more, the reschedule report excludes the purchase order. When
you specify 2 or less, the reschedule report includes the purchase order.
In Days Filter
Enter the number of reschedule in days to filter entries that are displayed on the report.
Use 0 days to allow the planning process to report all orders suggested to be
rescheduled.
Oracle MRP compares the current purchase or the work in process due date with the
suggested due date. It uses reschedule in days when the purchase or the work in
process due date is later than the suggested due date. If the difference between the
purchase or the work in process due date and the suggested due date is less than or
equal to the reschedule in days, the reschedule report excludes those orders.
For example, if the suggested due date is 01-JUN, the purchase order date is 04-JUN
and you specify 3 or more, the reschedule report excludes the purchase order. When
you specify 2 or less, the reschedule report includes the purchase order.
Planner
Select a planner to report orders associated with this planner.
Buyer
Select a buyer to report orders associated with this buyer.
Items From/To
Reports 11-35
Category Set
set.
Categories From/To
names.

Select an ABC assignment group. Oracle MRP reports orders associated with this ABC
assignment group.
ABC Class
Cutoff Type
Dock date: Report all orders whose dock date is before the cutoff date.
Note: Use this option if your processing and post-processing lead times
are long and you want to reduce the number of items.
Due date: Report all orders whose due date is before the cutoff date.
Order date: Report all orders whose order date is before the cutoff date.
Start date: Report all orders whose start date is before the cutoff date.
Cutoff Date
Select the cutoff date to report orders with a new dock, due, or order date up to and
including this date.
See Also
Planned Order Report for Supply Chain Planning

The (Supply Chain) Planned Order Report displays new planned orders that the
planning process recommends for a plan name you specify.
Report Submission
In the Submit Requests window, enter Planned Order Report in the Name field. Supply
Chain Planning users should enter Supply Chain Planned Order Reports in the Name
field.
Report Parameters
Plan Name (Required): Select a plan name.
Organization Selection (Required) - Supply Chain Planning

planning recommendations pertaining to the current organization.
Item Selection (Optional, Default)

Select one of the following options. If you do not enter a value in this field, planned
orders for items with an item planning attribute of Make or Buy are reported.
MakeReport planned orders for items with an item planning attribute of Make.
Buy Report planned orders for items with an item planning attribute of Buy.
Note: You assign these attributes to an item when you define an item in
Oracle Inventory.
Include Costs (Required, Default)

No: Report the new planned orders without standard cost.
Yes: Report the new planned orders with standard cost.
Sort (Required, Default)

ABC Class: Sort the orders by item within an ABC class.
Buyer: Sort the orders by item within a buyer.
Category: Sort the orders by item within a category.
Reports 11-37
Due Date: Sort the orders by the item due date.
Inventory Item: Sort the orders by inventory item.
Planner: Sort the orders by item within planner.
Planner (Optional)
Select a planner to report only items associated with this planner.
Buyer (Optional)
Select a buyer to report only items associated with this buyer.
Items From/To (Optional)
Category Set (Optional, Default)
set.
Categories From/To (Optional)
names.
ABC Assignment Group (Optional)
Select an ABC assignment group to reports associated planned orders.
ABC Class (Optional)
Cutoff Type (Required, Default)
Dock Date: Report all planned orders whose dock date is before the cutoff date. Use this
option if your processing and postprocessing lead times are long and you want to
reduce the number of items reported.
Due Date: Report all planned orders whose due date is before the cutoff date.
Order Date: Report all planned orders whose order date is before the cutoff date.
Start Date: Report all planned orders whose start date is before the cutoff date.
Cutoff Date
(Required, Default)
Select the cutoff date to report new planned orders with a suggested dock, due, order,
or start date up to and including this date.
See Also
Planning Detail Report for Supply Chain Planning

The (Supply Chain) Planning Detail Report includes material requirements planning
data for a DRP, MPS, or MRP name that you specify. This is the central planning report
that gives you all the information you need to understand the material plan. The report
may include the following sections: Horizontal Listing, Vertical Listing, and detail
sections showing gross requirements, scheduled receipts, planned orders, bill of
material and engineering changes, repetitive schedules, substitute items, expired lot
and byproduct information.
Note: For MRP Planned safety stock, Oracle MRPprints the safety stock
percentage, if any, that you defined for the item. For non-MRP planned
safety stock, Oracle MRPdoes not print the safety stock percentage,
since the safety stock could be time phased. Information regarding
MRP and non-MRP Planned safety stock appears in the Horizontal
Listing section.
Note: Gross requirements are reduced by the by product supply
quantity.
Note: The calculation for Annual Projected Demand is deamnd for
planning horizon x (365/ length of planning horizon.
The demand for the period is the sum of the demand for up to one year. If there is more
than one year of demand, it is not included in the calculation.
Report Submission
In the Submit Requests window, enter Planning Detail Report in the Name field. Supply
Chain Planning users should enter Supply Chain Planning Detail Reports in the Name
field.
Report Parameters
Plan Name
Select a plan name.
Reports 11-39
planning information pertaining to the current organization.
Vertical Display
Bucketed daily: Report projected available balance information on a daily basis.
Bucketless: Report projected available balance information for dates on which

supply or demand exists.
None: Do not report a vertical display.
Detail Display
No: Display vertical and horizontal listings only.
Yes: Display vertical and horizontal listings and detail sections showing gross
requirements, scheduled receipts, planned orders, bill of material and engineering
changes, repetitive schedules, substitute items, expired lot and by product information.
Periods
12
24
36
48
Weeks

First Sort
Select one of the following options. The report sorts items first in this order, then in the
order you specify for the second and third sort.
Second Sort
Select the second sort type for the item. Items are sorted by the First Sort type and then
by this sort type within the first type.
For example, if you choose Planner as the first sort type and Category as the second sort
type, Oracle MRP sorts the report by planner, and then by material category within
planner.
Note: If you choose No sort here, the report is sorted using just the First
Sort type. If you choose No sort, the report is sorted by using just the
First Sort type.
Third Sort
Select the third sort type for the item. Oracle MRP sorts the items 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.
Reports 11-41
For example, if you choose Planner as the first sort type, Category as the second sort
type, and Inventory item as the third sort type, the report is sorted by planner, then by
material category within planner, and finally by Inventory item within material category.
If you choose No sort, the report is sorted by using just the first and second sort types.
Buyer
Select a buyer to report only items associated with this buyer.
Items From/To
Category Set
set.
Categories From/To
names.

Select an ABC assignment group. Oracle MRP reports items associated with this ABC
assignment group.
ABC Class
Horizontal Display Factor

Enter a space saving factor by which all numbers in the horizontal listing section are
divided by.
Include Items With No Activity

Indicate whether to include items that have no demand or supply information in the
report.
Include Phantoms
Indicate whether to include phantoms in the report.
Include Completed Jobs

Indicate whether to include completed discrete jobs in the report.
Cutoff Date
Select a cutoff date up to which you want to display the DRP, MRP or MPS plan. This
restricts the information in the vertical display and the detail sections of the report.
See Also
Planning Exception Sets Report

The Planning Exception Sets Report displays planning exception sets that you have
defined for items. You use planning exception sets to identify items and orders that
require attention based upon a set of predefined action messages. This facilitates control
over message sensitivity, message priority, and marking those messages where action
has been taken.
Report Submission
In the Submit Requests window, enter Planning Exception Sets Report in the Name
field. See: Submitting a Request, Oracle Applications User's Guide
Reports 11-43
12
Kanban Planning
Overview of Kanban Planning

Kanban is a pull replenishment system whose aims are zero stockouts, shorter lead
times, and reduced inventory with minimal manual supervision. Instead of waiting for
an MRP plan to release materials down the supply chain, with kanban each operation
pulls the materials it needs from its source when it needs them, signaling with a
replenishment signal or a kanban that it needs to do so.
Kanban planning is part of Oracle Flow Manufacturing. You need a Flow
Manufacturing license to use it.
Kanban Terminology
The following terminology describes features or processes in a manufacturing
environment using kanbans.
Actual Production
Actual production refers to the discrete jobs, repetitive schedules, and flow schedules
that are scheduled to be produced on the manufacturing line. Actual production is one
of the demand types used in the Kanban Names window for calculating the kanban size
or number of cards.
Flow Manufacturing
A kanban system is most effective in flow shops manufacturing organizations with
well-defined material flows. Because the demand for customer-order items may be
discontinuous even in a shop where the material demand is steady, you might want to
only designate certain items as kanban items.
Kanban
The term kanban refers to a visual replenishment signal such as a card or an empty bin
for an item. In a kanban system, each work center has several bins, each containing a
certain number of the same item. When a bin becomes empty, the work center starts the
Kanban Planning 12-1
process of replenishing the empty bin by sending the replenishment signal, or a kanban.
Meanwhile, the work center can continue using the other (stocked) bins.
Kanban Cards
Kanban cards are the visual replenishment signals. Each kanban bin has one kanban
card, so the number of kanban cards is the same as the number of kanbans for each
item. Thus, if a work center must have 100 of the same kanban item within the
replenishment lead time, and the kanban size is 20, there must be five kanbans for the
item five kanban cards.
Kanban Items
An item that is pulled through the kanban system, rather than pushed by the planner, is
called a kanban-released item, or simply kanban item. Your planning system can have
kanban items as well as items released by the planner.
Kanban Location
The kanban location for a kanban item is the designated location where that item is
stored (and where replenishment is delivered). You can designate location as a
combination of subinventory and locator. You can use locators on kanbans even if the
locator control is off.
Kanban Plans
The kanban plan indicates the number of kanbans and the size of each kanban required
to satisfy the demand for all items that are either kanban released or have components
that have kanban released items on the bill.
Kanban Size
Kanban size refers to the number of items in each kanban. Because a kanban is only
replenished when it's empty, the kanban size should be a multiple of the lot size. For
example, if you would normally order an item in lots of 20, you should not make the
kanban size less than 20 because the supplier would not be able to fulfill such an order.
You can specify the lot size using the lot multiplier on the pull sequences.
Pull Sequences
For every kanban location, there is a pull sequence ? a grouping of information that
defines a kanban location, source data, and planning parameters.
In defining a pull sequence for a kanban item in Oracle Inventory, you specify the
replenishment source for a kanban item at a specific location. You also specify what you
want the kanban calculation program to calculate, the lead time for obtaining the
kanban item, the allocation percentage, and order modifiers that you want to affect the
calculation program.
See Also
Calculation Formula
Defining Kanban Cards, Oracle Inventory User's Guide
Defining Kanban Pull Sequences, Oracle Inventory User's Guide
Generating Kanban Cards, Oracle Inventory User's Guide
Overview of Kanban Replenishment, Oracle Inventory User's Guide
Printing Kanban Cards, Oracle Inventory User's Guide
Overview of Flow Manufacturing, Oracle Flow Manufacturing User's Guide
Calculation Formula
One of the most important tasks of a kanban planning system is determining the
optimal number of kanban cards. The kanban planning software takes care of this
calculation provided you enter correct values for kanban size, average daily demand for
the kanban item, and the lead time to replenish one kanban.
We provide a package that you can use to customize the calculation. See the Oracle
Manufacturing, Distribution, Sales and Service Open Interfaces Manual.
By default, the standard calculation is:
(C - 1) * S = D * A * (L + SSD) where:
C is the number of kanban cards
S is the kanban size
D is the average daily demand
A is the allocation percent
L is the lead time (in days) to replenish one kanban
SSD is the Safety Stock Days
If you think through the kanban process, you will see why this formula works best
when the demand for the kanban item is steady.
In addition to this basic formula, when the calculation program calculates kanban size,
it takes into account the values for the following order modifiers (specified in the pull
sequence), in the following order:
Minimum Order Quantity
Lot Multiplier
For example, suppose you've specified the Minimum Order Quantity for a particular
item to be 50. You want the formula to calculate the kanban size (S), so you enter values
for C and L. Even though strictly based on the values you enter for C and L?the formula
should yield 40, the actual kanban size will be 50 because of the Minimum Order
Quantity. If a Lot Multiplier of 15 is specified, the kanban size is rounded to 60 in oder
to meeth both the Minimum Order Quantity and Lot Multiplier order modifiers.
Note: The program uses order modifiers only when calculating the
kanban size. If you specify the kanban size and want the program to
calculate the number of kanban cards, the program does not use order
modifiers.
How the Program Determines Average Daily Demand

Before the kanban calculation program can calculate the kanban size or the number of
kanban cards, it needs values for the other variables. It gets the values of L and C or S
from the pull sequence you define in Oracle Inventory. The program calculates the
average daily demand by following these steps:
1.
It identifies all the kanban items that you want to include in your kanban
calculation, using the parameters you enter when you launch a kanban calculation.
2.
It finds location information for each kanban item.
3.
For each kanban item, it identifies every BOM in which the item appears so that it
can explode the demand from the assemblies down to the kanban item.
4.
Using the MDS, MPS, Actual Production, or forecast you specify in the Kanban
Names window - it identifies all the demand entries for each kanban item for which
the demand is independent. For example, suppose that from the forecast you
specified in Kanban Names, the program finds independent demand for 600 of
kanban item A.
5.
It uses the Allocation Percentage specified in the pull sequence for each kanban
item to determine how to distribute demand for the item among its different
locations. For example, if the allocation percentage for item A at location L1 is 20%,
then the program places demand of 120 (that is, 20% of 600) at location L1.
6.
Using the MDS, MPS, Actual Production, or forecast you specify in the Kanban
Names window - it calculates demand for each kanban item for which demand is
dependent on the demand for other items. It does so by using the following
information:
Quantity per Assembly. For example, if there are 2 of kanban item R per one
assembly of item K, and the demand for K is 10, then the demand for R is 20.
Component Yield. The program divides the demand for the child item by that
item's component yield to determine the actual demand for the child item. For
example, if the component yield for item R is 50%, the new demand for R is 40
(because 20 divided by 50% is 40).
7.
Reverse Cumulative Yield. The program further divides the demand for the
child item by the Reverse Cumulative Yield (specified in the operation sequence
of the flow routing for the parent item) to determine the actual demand for the
child item. For example, if the reverse cumulative yield for K is 10%, the new
demand for R is 400 (because 40 divided by 10% is 400).
Net Planning Percentage. The program then multiplies the demand for the
child item by the Net Planning Percentage (specified in the operation sequence
of the flow routing for the parent item) to determine the actual demand for the
child item. For example, if the net planning percentage for K is 80%, the new
demand for R is 320 (because 400 multiplied by 80% is 320).
Finally, the program sums up the demand entries that fall within the kanban
planning horizon for each kanban item at each location and divides the demand for
each item at each location by the number of workdays. For example, if the number
of workdays on the planning horizon is 20, then the average daily demand for item
A at location L1 is 6 (because the total demand for item A at location L1 for the
planning horizon is 120). The program prorates the demand from periodic forecasts
for those days between the Demand window specified for the calculation program.
See Also
Oracle Flow Manufacturing Implementation Manual
Using the Kanban Calculation Program

Calculating the kanban size or the number of kanban cards involves two steps: telling
the application what demand information to use and submitting a request for the
calculation program.
Prerequisites
Before you can run the kanban calculation program, you must:
Identify the kanban items in the system. See: Defining Kanban Items, Oracle
Inventory User's Guide.
Set up a bill of material for kanban items. See: Creating a Bill of Material, Oracle Bills
of Material User's Guide.
Define the pull sequence for the item. See: Defining Kanban Pull Sequences, Oracle
Inventory User's Guide.
Add kanban location information to either the parent assembly or the kanban item
master.
To specify demand information:

1.
Navigate to the Kanban Names window.
2.
Enter a new plan name.

You can enter any name you want for this simulation plan.
Note: An implicit plan named Production is created by the
application to enable kanban comparisons.
3.
Enter a description to help you remember what's unique about this simulation plan.
4.
Select an input type to tell the quantity calculation program whether to use the
demand information from a forecast, an MDS, an MPS, or Actual Production.
A list of choices appears in the Forecast/Schedule field.
5.
Select the name of the specific forecast or schedule you want to use.
Choose the Forecast/Schedule button to see more detail about the selected forecast
or schedule. Then navigate back to the Kanban Names window.
6.
Optionally, enter the date on which this simulation plan is to become inactive.
To calculate the kanban size for a kanban plan:

1.
Navigate to the Kanban Names window.
2.
If the window displays more than one plan, choose which plan you want to do the
calculation.
3.
Choose the Launch button to start the calculation program.
4.
In the Parameters window, enter the following information:

Plan Name: the name of the plan for which you want to run the calculation program.
Items From: the alphabetical beginning of the range of items you're interested in
To: the alphabetical end of the range of items you're interested in Category Set: the
name of the category set for the items
Categories From: the alphabetical beginning of the range of categories you're
interested in
To: the alphabetical end of the range of categories you're interested in
BOM Effectivity: the BOM effectivity date; the program uses BOMs that are effective
as of this date. If you do not enter anything, the program uses today's date
Demand Start Date: the start date on which the demand entries are considered
Cutoff Date: the date up to which ' want demand entries to be considered
5.
Choose OK to set the parameters you've just entered.

In the Launch Kanban window that appears, your parameters appear in the
Parameters field.
6.
In the Launch Kanban window, make optional changes or choose Submit Request
to start the calculation program.
The calculation program uses all the information you entered, including the launch
parameters, the demand information, and the pull sequences, to calculate either the
kanban size or the number of kanban cards. It also takes into account several order
modifiers.
To specify options just before submitting a request for the calculation program:
1.
Navigate to the Launch Kanban window.
2.
Specify the options you want. See: Submitting a Request, Oracle Applications User's
Guide.
Note: The concurrent program will complete with a status of
Warning if the following conditions exist:
Demand start and cutoff dates are outside the range of data in
your demand schedule.
There are pull sequences existing without a matching location

on a bill of material or the item master - and this is the first pull
sequence in a replenishment chain.
Important: Kanban size or quantity is only calculated for pull
sequences that have an exact match with the replenishment

subinventory/locator combination specified on the bill or material
or item master.
See Also
Viewing and Updating Kanban Calculations
Calculation Formula
Kanban Tools Menu
Defining Kanban Cards, Oracle Inventory User's Guide
Generating Kanban Cards, Oracle Inventory User's Guide
Viewing and Updating Kanban Calculations

You can view the recommended kanban size for each item at each location. You can
compare plans and update parts of your production plan with your kanban simulation
plan. You can also re-launch the kanban calculation program to see the effects of
changing one or more variables, including kanban size, number of kanban cards, and
source types.
Prerequisites:
Before you can view or update kanban calculations, you must:
Run the kanban calculation program to generate a kanban plan. See: Using the Kanban
Calculation Program.
To view a kanban calculation, compare two plans, and update parts of

your production plan:
1.
Navigate to the Kanban Workbench window.
2.
Query the simulation plan you're interested in.
3.
Choose Compare. The Find Kanban Comparison window appears.
4.
Choose Find to find all items in the plan or narrow down your search by entering
search criteria. To narrow your search, enter one of the following in the Field field:
Item: if you want to limit your search to only certain kanban items.
Kanban Number: if you want to limit your search to only items within a particular
range of kanban cards (for example, items requiring more than 10 kanban cards).
Kanban Size: if you want to limit your search by kanban size (for example, items
with kanbans that contain between 20 and 100 units).
Locator: if you want to limit your search to only items with a particular locator.
Subinventory: if you want to limit your search to only items with a particular
subinventory location.
Category: if you want to limit your search to only items in a particular category.
Planner: if you want to limit your search to those items planned by a employee
associated to the items.
Variance: if you want to limit your search to only items with a certain variance
percentage from the manually entered plan.
5.
Enter the condition and values for From and To.
6.
Choose Find to find the items that match the criteria you've entered. The Compare
Kanban Plans window appears.
7.
Notice the variances between your simulation plan and your production plan.
Some items may have higher variances than others. You can decide by item which
parts of the simulation plan to merge with the production plan, updating the
production plan with those parts of the kanban calculation that make sense to you.
Choose the check box next to each item for which you want to update the
production plan with the simulation plan. Then choose Update Production.
To change one or more variables and re-launch the plan:

1.
Navigate to the Kanban Workbench window.
2.
Query the simulation plan you're interested in.
3.
Choose the Details button.

The Find window appears.
4.
Choose Find to find all items in the plan or narrow down your search by entering
search criteria and then choosing Find.
5.
In the window that appears, choose the check box next to each item for which you
want to make an adjustment.
6.
In the Calculate column for each item that you checked, choose what you want to
calculate.
7.
For each item that you checked, scroll to the field whose value you want to change
and enter a new value for the field.
You can change these fields: Kanban Size, # of Kanbans, Source Type.
8.
When you've made all the adjustments you want, choose Simulation Replan.
This button sends a request to the kanban calculation program to generate a new
simulation plan based on the new values you've entered. After the request has been
processed, you'll be able to see the results of the kanban calculation from the
Kanban Workbench, just as you would for any simulation plan.
9.
You can update your plan from these results by selecting pull sequences and
choosing Update Production.
To view demand for a particular kanban item at a particular subinventory

and locator (based on the forecast or schedule):
1.
Navigate to the Demand window.

The View Kanban Demand window appears. The demand shown is the total
demand for the period, not the average daily demand the program uses in
calculations.
To check the status of existing kanban cards or to define new kanban

cards:
1.
From the Tools menu, select Kanban Cards. You can print kanban cards by
choosing Print Kanban Cards.
See
Using the Kanban Calculation Program
Kanban Tools Menu
Kanban Tools Menu

You can access the tools menu for kanban when working in the Kanban Workbench
window. Depending upon the currently active window and other conditions, the Tools
menu includes:
Forecast/Schedule
Navigates to the Item Forecast Entries

window where you can review and update
information for items in a forecast set
Kanban Cards
Navigates to the Kanban Cards Summary

window in Oracle Inventory where you can
view, define, and update kanban cards.
Print Kanbans
Navigates to the Print Kanban Cards window

in Oracle Inventory where you can either
batch or manually print kanban cards.
See:
Reviewing Forecast Detail Information Generating Kanban Cards, Oracle Inventory
User's Guide
Printing Kanban Cards, Oracle Inventory User's Guide
13
Project MRP

Project MRP is one of a series of features in Oracle Applications designed to support
companies that manufacture products for projects or contracts. Known as Project
Manufacturing, it is a solution that combines Oracle Projects with Oracle's
manufacturing applications to provide robust project tracking, billing and budgeting,
along with support for hybrid manufacturing methodologies.
Project MRP allows you to plan in a project or contract environment by segmenting all
sources of supply and demand by project. This allows the planning process to identify
components as shared or project specific, track existing inventories by project, and
provide visibility to all supply and demand associated with a project.
Project MRP is completely integrated with Oracle Projects, to offer a comprehensive
project manufacturing solution, but it can also work in isolation to support Seiban
manufacturing methods.
With Project MRP, you can:
include project or Seiban numbers and task references in forecast, MPS, and MDS
entries
load, copy, or merge forecast, MPS, and MDS entries with project or Seiban
numbers and task references recognize and allocate supply according to project or
Seiban numbers and task references combine project and Seiban related supply and
demand with nonproject and nonSeiban related supply and demand in the same
plan or schedule perform netting by planning groups, project or Seiban, and tasks
generate planned orders with project or Seiban number and task references execute
a plan (in the Planner Workbench) by project, Seiban, and task link sales order lines,
production orders, and purchase orders to projects, Seibans, and tasks, allocate
onhand inventory to projects, and issue inventory to projects
perform net change simulation in a project environment
Project MRP 13-1
create a payback transaction as a supply for the lending project, and a demand for
the borrowing project and view these transactions in the Planner Workbench use
model/unit effectivity to create demand and generate planned orders with unit
number specified
See also:
Establishing a Project MRP Environment
Viewing Onhand Quantities in a Project
Model/Unit Effectivity, Oracle Project Manufacturing Implementation Manual
Borrow Payback, Oracle Project Manufacturing User's Guide
Establishing a Project MRP Environment

Project MRP is part of the overall solution offered by Project Manufacturing. If you
want you employ all the features offered by Project Manufacturing, you must define
project parameters in Oracle Projects, Oracle Inventory, and Oracle MRP.
If you are working in a Seiban manufacturing environment, you do not need to include
Oracle Projects in your setup tasks.
Overview of Project MRP Setup Tasks

The setup tasks in Oracle Projects are:
Define projects and tasks in Oracle Projects. This phase is not necessary in a Seiban
environment.
Setup tasks in Oracle Inventory
Define organization level project parameters.
Define subinventories.
Define item attributes.
Setup tasks in Oracle MRP
Define planning group lookups.
Associate a project to a planning group.
Define Seiban numbers (optional).
Setting Up Project MRP in Oracle Projects

These setup steps are not necessary if you are using Seiban numbers only.
To define a project:
1.
Navigate to the Projects, Templates Summary window.
2.
To complete this task, refer to Creating a New Project from a Project Template or an
Existing Project, Oracle Projects User's Guide.
See also:
Setting Up Project MRP in Oracle Inventory
Defining Planning Group Lookups

To define project information in organization parameters :
1.
Navigate to the Project Manufacturing Parameters window.
2.
Choose the General tabbed region.
3.
Check Enable Project Reference.
4.
Select a project control level (the project control level determines the level at which
the organization is allowed to control its project activity):
Project: You will be able to associate demand and supply records with project
references, as well as plan at the project level. Task references will be disabled in all
windows.
Task: You will be able to associate demand and supply records with project and task
references, as well as plan at the project level.
See: Defining Default Inventory Parameters, Oracle Inventory User's Guide for
defining additional organization parameters.
To define project information in subinventories:

1.
Navigate to the Master Item window.
2.
Enter a unique alphanumeric name.
Project MRP 13-3
3.
Select the Item Subinventories window from the Tools menu.
4.
In the Planning tabbed region, place your cursor in the Locator field to display the
Stock Locators parameter window.
5.
Enter a project/Seiban number and, if appropriate, a task reference. See: Defining

Stock Locators, Oracle Inventory User's Guide.
6.
Save your work.
To define project information in item attributes:

1.
Navigate to the Master Item window.
2.
Choose the MPS/MRP Planning tabbed region.
3.
Select a pegging level:
Soft Pegging:The planning process will allocate supply for a projecttask (or
Seiban) to demand for the projecttask (or Seiban), according to the Reservation
Level set in the plan level options.
All reservations of supply to demand records is for a single item. Common,
nonproject supply is used to satisfy project demand. For a soft pegged item,
excess project supply (or common supply) is always available to another
project's demand.
No project references will be attached to planned orders issued to soft pegged
items.
You can also generate a graphical pegging display in a nonproject environment,
for plans with pegging enabled.
End Assembly Pegging:Also known as Where Used, this option traces the Pegging
end assembly the item is pegged to at the top of the bill of material. Even if you
do not select end assembly pegging, you can still calculate and view end
assemblies online.
You can also generate a graphical pegging display in a nonproject environment,
for plans with pegging enabled.
End Assembly/ Soft Pegging :Choose this option for both soft pegging and end
assembly pegging.
You can also generate a pegging display in a nonproject environment, for plans
with full pegging enabled.
Hard Pegging: The planning process will allocate supply for a projecttask (or
Seiban) to demand for the projecttask (or Seiban), according to the Reservation
Level set in the plan level options.
A hard pegged item will not have access to common, nonproject supply. Excess
supply from one project can only be shared among projects in the same
planning group, provided reservation level is set at planning group.
Project references are attached to planned orders for hard pegged items.
You can also generate a graphical pegging display in a project environment, for
plans with full pegging enabled.
End Assembly/ Hard Pegging:Choose this option for both hard pegging and end
assembly pegging.
You can also generate a graphical pegging display in a project environment, for
plans with full pegging enabled.
None: This option disables project material allocation, end assembly pegging,
and graphics in full pegging.
See: Defining Items, Oracle Inventory User's Guide for defining additional item
attributes. See: Viewing Pegged Supply and Demand for information on full
pegging.
See also:
Setting Up Project MRP in MRP

Planning groups allow you to establish a relationship between two or more projects or
Seibans by associating them with a single planning group. Projects and Seibans within
the planning group can share supply, depending upon the reservation level set in the
plan level options.
To define planning group lookups
1.
Navigate to the Planning Group Lookups window.
2.
Place the cursor in the Code field, choose New from the File menu.
3.
Enter a unique alphanumeric code.
4.
Enter a meaning and description.
5.
Enter a start date, and optionally and end date to restrict the effectivity of the
Project MRP 13-5
Lookup.
6.
Check Enabled to activate the Lookup
7.
Save your work.

See also:
Reviewing or Adding Project MRP Plan Options:
Reviewing or Adding Project MRP Plan Options Prerequisite

After establishing a project MRP environment, you must define an DRP, MPS, or MRP
name. See: Defining MRP Names
To review or add Project MRP plan options
1.
2.
Query a plan name.
3.
Check Pegging. This will optionally allow you to set a Reservation Level and a
Hard Pegging Level when in a projects environment. (It will also allow you to
generate a graphical pegging display, if the pegging attribute for your item is not
set to None)
4.
In the Pegging region, set a Reservation Level and (optionally) a Hard Pegging
Level.
Reservation Level: Determine how the planning process will preallocate
project/Seiban supply to project/Seiban demand. This will control only those items
whose item attributes have been set to Soft Pegging, End Assembly/Soft Pegging, Hard
Pegging, or End Assembly/Hard Pegging.
Planning Group: Reserve projectspecific supply and demand at the planning
group level. Supply for one project can be reserved against demand from another
project, if both projects belong to the same planning group. Excess common supply
can be allocated to project demand for hard and soft pegged items.
if reservation level is project supply from due project, it cannot be given a demand
from another project. Only soft pegged items excess project supply can be allocated
to other projects.
Task: Reserve supply for a projecttask against demand for the same projecttask
only.
None: The planning process does not operate in a project manufacturing

environment.
Hard Pegging Level: For hard pegged items, determine if project references will be
added to planned orders. This will control only those items whose item attributes
have been set to Hard Pegging or End Assembly/Hard Pegging. Suggested planned
orders for such items will be assigned at one of the following levels.
Project: Attach the project number to which the planned order is hard pegged.
Project-task: Attach the project and task number to which the planned order is hard
pegged.
None: Do not add project/task references to planned orders.
See: Reviewing or Adding Plan Options for additional plan options.
5.
Save your work.

See also:
Setting Up Project MRP in Oracle Project Manufacturing
Launching a Project MRP Plan
Launching a Project MRP Plan

Prerequisites
Before launching, insure that project demand is loaded into your MDS via forecast
consumption entries and sales orders, or choose MRP/DRP/MPS plans with firm
planned orders.
After establishing a project MRP environment and adding your Project MRP plan
options, perform the following tasks before setting plan level options:
Enter forecast entries with project/Seiban numbers and task references, or
load/copy/merge a forecast with project/Seiban numbers and task references. See:
Defining a Forecast, or Copying/Merging Forecasts
Enter schedule entries with project/Seiban numbers and task references, or
load/copy/merge a schedule with project/Seiban numbers and task references. See:
Defining Schedule Entries Manually, or Loading a Master Schedule from an Internal
Source.
Setting Up Project MRP in Oracle Project Manufacturing

Setting up Project MRP in Oracle Project Manufacturing involves the following steps:
Project MRP 13-7
Defining Seiban Number, Oracle Project Manufacturing User's Guide
Assigning Project Parameters, Oracle Project Manufacturing User's Guide
Project MRP Planning Logic

Project MRP planning logic differs from the regular MRP planning logic primarily in
the way it determines what supply is available to satisfy demand. It also differs in the
way it assigns any suggested planned orders that result from the planning process.
Instead of simply considering existing inventories and scheduled receipts when netting
supply against demand, the project MRP planning logic goes through a process of pre
allocation: Before netting supply against demand, the planning process analyses the
project/Seiban numbers (along with the item attributes, project parameters, and plan
level options you have set), to determine what supply is available for meeting
project/Seiban demand. Supply and demand that is not specific to any project/Seiban is
defined as common supply. The project MRP planning logic treats common supply or
demand as a "null" project/Seiban.
In order for Project MRP planning logic to work, you must set the pegging item
attribute on the items to one of the following values: soft pegging, end assembly/soft
pegging, hard pegging, or end assembly/hard pegging.
The following table compares the logic in regular MRP and project MRP:
Planning logic in regular MRP compared to project MRP
Regular MRP
Project MRP
Explode bill of materials
Explode bill of materials
Snapshot of inventory, supply, and demand
Snapshot of inventory, supply, and demand
--
Pre-allocate supply to projects and seibans
Net supply against demand
Net supply against demand and assign

planned orders to projects and seibans
Project Netting Example for Hard Pegging

In the following diagram, the item is an MRPplanned component used in two projects
and in the common supply.
During the preallocation phase of netting, the planning engine divides the supply for
the item by project. In Period 1, the demand from project 2 (P2) is 100. Since there is an
onhand quantity of 25 for P2 and no scheduled receipts, there is still demand for P2 of
75. The planning engine cannot apply excess from any other source to meet this
demand, the planning engine looks for the available supply for P2 and finds it in Period
2. This supply is rescheduled in to Period 1. This scheduled receipt is also used to
satisfy the P2 demand of 500 in Period 2.
Once again, the planning engine can only apply the excess P2 supply to P2 demand.
The last P2 demand is in Period 3 (for 300), consuming the excess of 25 from Period 2
and leaving a net requirement of 275, which the planning engine converts into planned
orders.
Because the item is hard pegged, and the hard pegging level (from the plan options) is
set to project, the P2 project reference is added to the suggested planned order.
In this diagram:
Item pegging: Hard pegging
Reservation level: Project
Hard pegging level: Project
On hand (common supply): 5
On hand (P1): 10
On hand (P2): 25
Entity
Period 1
Period 2
Period 3
Demand
200 (P1)
150 (P1)
300 (P2)
100 (P2)
500 (P2)
400 (common)
Scheduled receipts
265 (P1)
600 (P2)
600 (common)
Planned orders
--
75 (P1)
275 (P2)
Projected available
75 (P1)
0 (P1)
0 (P1)
-75 (P2)
25 (P2)
0 (P2)
-395 (common)
395 (common)
205 (common)
Project MRP 13-9
Project Netting Example for Soft Pegging

In the following diagram, the item is an MRPplanned component used in two projects
and in the common supply.
During the preallocation phase of netting, the planning engine divides the supply for
the item by project (common is treated as project). Period 1 has a common demand of
400. The net demand after applying the common onhand is 395 in Period 1. The
scheduled receipts in Period 3 are allocated to this demand. There is no more common
demand to be met.
Project P1 has an excess of 75 in Period 1 (scheduled receipts plus the onhand quantity,
minus P1 demand). This is used to partially satisfy the P1 demand of 150 in Period 2.
This leaves an unmet demand of 75 in period 2 for project P1. There is no supply
available. Unlike the hard pegging example, the planning process can use other excess
supply in this period to meet this remaining demand. Therefore, the excess supply of
common in Period 3 is allocated to this demand.
Item 7004 is a soft pegged item, it can use excess supply available in common or other
projects to meet this demand. It allocates the excess supply from 600 common to this
demand.
For project P2 the demand in period 1 is 100. Since there is an onhand quantity of 25 for
P2 and no scheduled receipts in this period, there is still a demand of 75 for P2. To meet
this demand, the planning engine looks for more P2 supply, which it finds in period 2.
This supply of 600 is allocated to the demand of P2 in period 1. This supply also takes
care of the demand for 500 for project P2 in period 2. The available 25 in project P2 at
the end of period 2 are pegged to the P2 demand of 300 in period 3. This leaves a
demand of 275 for project P2 in period 3. As there is no P2 supply, and the item is a soft
pegged item, it uses the excess 130 in common supply. There is still a shortage of 145.
The planning engine then creates a planned order for 145. Since item 7004 is soft
pegged, this planned order will not carry any project references.
Note: Project references on scheduled receipts of soft pegged items
must be entered manually.
See also Project References, Oracle Project Manufacturing User's Guide.

In this diagram:
Item pegging: Soft pegging
Reservation level: Project
Hard pegging level: Project
On hand (common supply): 5
On hand (P1): 10
On hand (P2): 25
Entity
Period 1
Period 2
Period 3
Demand
200 (P1)
150 (P1)
300 (P2)
100 (P2)
500 (P2)
400 (common)
Scheduled receipts
265 (P1)
600 (P2)
600 (common)
Planned orders
--
75 (P1)
145
Projected available
75 (P1)
-75 (P1)
0 (P1)
-75 (P2)
25 (P2)
0 (P2)
-395 (common)
395 (common)
0 (common)
Netting Behavior
By combining the item pegging attribute with the plan options reservation and hard
pegging levels, you can exercise a high degree of control over how the planning process
preallocates supply for an item. The table below summarizes the possible
combinations and types of behavior you can enforce:
Project MRP Netting Behavior
Reservation Level
Hard Pegging Level
Item Pegging
Attribute
Netting Behavior
Planning Group
Project
Hard Pegging
Reserve supply at
planning group level,
excess common
supply used for
project demand, and
create planned orders
at project level
Project MRP 13-11
Reservation Level
Hard Pegging Level
Item Pegging
Attribute
Netting Behavior
Planning Group
Project-Task
Hard Pegging
Reserve supply at
excess common
supply used for
project demand, and
at project-task level
Planning Group
None
Hard Pegging
Reserve supply at
excess common
supply used for
project demand, and
without project
references
Project
Project
Hard Pegging
Reserve supply at
project-task level,
at project level
Project
Project-Task
Hard Pegging
Reserve supply at
project-task level,
at project-task level
Project
None
Hard Pegging
Reserve supply at
project-task level,
without project
references
Project-Task
Project
Hard Pegging
Reserve supply at
project-task level,
at project level
Project-Task
Project-Task
Hard Pegging
Reserve supply at
project-task level,
at project level
Reservation Level
Hard Pegging Level
Item Pegging
Attribute
Netting Behavior
Project-Task
None
Hard Pegging
Reserve supply at
project-task level,
without project
references
Planning Group
<any value>
Soft Pegging
Reserve supply at
project level, create
planned orders
without project
references
Hard Pegging
No reservations, full
pegging
Project
Project-Task
None
Excess Supply
Effects of the pegging item attribute on the netting of excess supply
Item Attribute
Allocation of Excess Supply
Hard Pegging or End Assembly/Hard Pegging
Planning logic ignores excess in common

supplies and project- and seiban-specific
supplies during the netting routine
Soft Pegging or End Assembly/Soft Pegging
Planning logic considers excess in common

supplies and project- and seiban-specific
supplies during the netting routine
Project MRP 13-13
14
Parallel Processing
Overview of Parallel Processing

Oracle MRP distributes processing across multiple concurrent processes to maximize
performance and make optimal use of machine resources. The architecture of Oracle
MRP that enables distributed concurrent processing allows you to:
Maximize your throughput by making optimal use of machine resources. Oracle

MRP is designed to divide tasks across multiple processes running concurrently to
allow you to do more work in less time.
Take advantage of multiprocessor architectures. At the same time, Oracle MRP

should work optimally, without modification, on single processor machines.
Configure Oracle MRP to run optimally on your machine. You can control how
Oracle MRP divides the work across separate processes, and how many processes
should perform the work.
Take advantage of advanced Oracle RDBMS features.
These topics are technical and are not intended for most users. It is not necessary to
read them to be able to use Oracle MRP.
Process Control
Oracle MRP breaks tasks into smaller tasks that can be executed concurrently by
independent processes. Oracle MRP controls the execution of these processes,
independent of the hardware platform.
Concurrent Manager
Oracle MRP uses Oracle Application Object Library's concurrent manager for process
control.
Oracle MRP uses Oracle Application Object Library's Application Programmatic
Parallel Processing 14-1
Interface (API) to launch new concurrent programs via the concurrent manager by
inserting rows to Oracle Application Object Library's concurrent request table.
Oracle MRP also uses the concurrent manager to determine the status of processes that
are executing. One process can determine the status of another process by using an API
to examine the status of the request in the concurrent request table.
Since Oracle MRP uses the concurrent manager to launch new processes and does not
spawn processes directly, Oracle MRP is hardware independent and works on multiple
hardware platforms without modification.
Oracle MRP has no direct control over how the operating system distributes the
processes across processors. Oracle MRP divides the tasks optimally across separate
processes, but depends upon optimization logic on the part of the operating system to
distribute the workload effectively across multiple processors.
See also Managing Concurrent Programs and Requests inOracle Applications User's
Guide .
Inter-process Communication
Oracle MRP breaks tasks into smaller tasks that are executed concurrently by
independent processes (workers). The programs that execute these tasks concurrently
need to communicate to coordinate their actions.
Oracle MRP uses the Oracle Server for inter-process communication. For example, a
Snapshot Delete Worker needs to be able to communicate to the Snapshot Monitor that
it has finished deleting the old plan data from a specific table. The Snapshot Delete
Worker does so by updating the appropriate columns in the database and issuing a
database commit, instead of relying on hardware-dependent techniques such as signals
or sockets. The Snapshot Monitor can then query those columns to receive the message
that the data has been deleted and can launch the Loader Worker.
Oracle MRP also uses an Oracle Server feature, database pipes, as a port independent
mechanism of asynchronous communication. For example, when the Snapshot Monitor
needs to communicate the next task to be executed to the Memory-based Snapshot or
the Memory-based Snapshot Workers, it places the task number on a pipe. The
Memory-based Snapshot and its Workers listen to the pipe to receive the task number.
After the execution of the task, they use the same mechanism to communicate the
completion of task to the Snapshot Monitor.
See also Memory-based Planning Engine.
Single Processor Machine

Distributing the workload across multiple independent processes should give
performance benefits, even when running on a single processor machine. Many Oracle
MRP processes make frequent accesses to the database. Therefore, the processes tend to
be I/O bound. That is, the bulk of the time is spent by the processes waiting for the disks
to access or retrieve the information requested, and not for the processors themselves to
compute.
The total time to execute two I/O bound tasks on a single processor machine is less if
they execute simultaneously rather than one after the other. While one task waits for
information to be brought back from disk, the single processor can execute the second
task.
When there are relatively few processes running, performance of a single processor
machine is similar to that of a multiprocessor machine. In general, performance of a
single processor machine degrades more quickly than a multiprocessor machine, as the
number of simultaneous processes increase.
Therefore, both single processor or multiprocessor machines may benefit from

distributing tasks across multiple processes. However, a multiple processor machine
may be able to distribute the tasks across more processors before realizing performance
degradation.
How Many Processes to Launch?
There is no single answer to how many processes to launch. Performance depends upon
many factors, such as:
What other processes will be running?
How many users are logged on?
How much memory does the machine have?
How many processors does the machine have?
What is the data distribution?
Does data entry occur all at once, or is data at a relatively constant rate throughout
the day?
The best approach is to experiment. For example, first try running the snapshot with
three workers, then increase the number of workers. Assuming other factors are not
skewing the results, determine which option provides the best results.
Snapshot
The Snapshot takes a copy, or "snapshot," of all the information used by the planning
processes so that the planning processes can operate on a picture of the data frozen at a
point in time, and report against that snapshot at any future time.
Snapshot Tasks
The work performed by the Snapshot can be broken down into individual tasks. Some
tasks involve copying information into the MRP tables, such as inventory quantities,
master schedule data, discrete jobs, purchase orders, and repetitive schedules. Other
tasks involve deleting information from tables. For example, the information in the
MRP discrete job table needs to be deleted before MRP can reload the latest
information. Many of the tasks are independent of one another; for example, you can
load inventory information at the same time you load discrete job information. The
Snapshot launches workers to run these tasks concurrently.
When the Snapshot runs, it populates the Snapshot Task table with all the tasks that
need to be executed.
Each task has a start date and a completion date. The values of those columns indicate
the status of the tasks. A task with a null start date and null completion date has not
been executed yet. A task with a value for the start date but no value for the completion
date is currently being processed. A task with values for the start date and for the
completion date has been processed. The Snapshot looks at these columns to determine
which task should be processed next.
Some tasks may be dependent upon other tasks. For example, you must delete from the
MRP discrete job table before you reinsert values for the latest picture of the discrete
jobs; or, you must load information on current repetitive schedules before you can
calculate information on current aggregate repetitive schedules. The Snapshot ensures
that independent tasks are processed before the tasks that depend upon them are
processed.
Read Consistency
Certain tasks require a database lock to guarantee a consistent read. For example,
discrete job information and inventory quantities require a lock on the inventory
transactions table to guarantee a consistent read. Consider the situation where you have
a subinventory with a quantity of 100 units, and a discrete job for 25 units. Between the
time the Snapshot reads the inventory information and the time the Snapshot reads the
discrete job information, 10 units are completed from the job. The Snapshot needs to
guarantee that it populates the MRP tables with inventory of 100 and discrete job
quantity of 25, or inventory for 110 and discrete job quantity of 15. Because each task
may be processed by independent processes, the Snapshot cannot guarantee that both
tasks are executed at the same time. Therefore, by locking the inventory transactions
table, the Snapshot guarantees a consistent read.
Each task has an attribute which indicates whether the Snapshot needs to have acquired
the table lock before the task can be completed. Once the locks have been acquired by
the Snapshot, those tasks that require a lock are given highest priority, so that the time
the tables are locked is minimized. Once all tasks requiring locks have been completed,
the Snapshot releases the locks.
Sometimes it is not necessary to guarantee read consistency. For example, if you are
running the planning processes for simulation purposes to estimate medium-term and
long-term trends in your material requirements, it may not be necessary to guarantee
read consistency. Therefore, you may want to run the planning processes with Snapshot
Lock Tables turned off, so that you do not need to restrict or limit other users from
performing transactions.
One of the advantages of the Memory-based Planning Engine is its ability to get a
consistent image of all planning data without locking users out of the system. The planning
engine accomplishes this with the Oracle Server feature called "set transaction
read-only." With this option, you do not need to lock tables for the duration of the
planning run. To ensure total consistency, you need only synchronize the times when
the Snapshot Workers and the Memory-based Snapshot execute the set transaction
feature.
You can achieve two degrees of read consistency under the Memory-based Planning
Engine. Set the Snapshot Lock Tables field to Yes to force the Snapshot Workers and the
Memory-based Snapshot to execute the set transaction feature simultaneously. Locking
tables gives you the highest degree of data consistency, but you cannot perform any
transactions while this lock is on. If you set the Snapshot Lock Tables field to No, the
Snapshot Workers and the Memory-based Snapshot may execute the set transaction
feature at different times. There is a remote possibility of some inconsistencies with this
method.
Snapshot Configuration
You can configure the Snapshot to determine how many Snapshot Workers to launch
when you define the MRP: Snapshot Workers profile option. See Profile Options.
This provides the capability to perform multiple tasks in parallel. This is a function of
the hardware running your processes and the number of Standard Managers you have
in your Oracle Applications.
This is a detailed explanation of the Snapshot Process logic under the Standard
Planning Engine:
1.
Launch X Snapshot Workers via the Concurrent Manager, where X is the number of
Snapshot Workers to launch, as defined by the profile option MRP: Snapshot
Workers.
2.
Did the user specify to lock tables? If not, go to Step 6.
3.
Try to lock tables to guarantee a consistent read.
4.
Were we able to lock the tables? If No, check to see if we have exceeded the amount
of time specified by the user to wait for the table locks.
5.
The user specified a length of time to wait for the table locks.
6.
Create the lock file. The existence of the lock file signals to the workers that they can
execute tasks requiring a table lock, as well as those that do not.
7.
Keep looping until all tasks that require table locks have been completed.
8.
All tasks requiring a lock have completed. Therefore, there is no need to keep the
locks. Issue a database commit to free the table locks.
9.
Are there any tasks that have not yet been executed and do not have tasks upon
which they are dependent that have not yet completed? If so, execute those tasks.
10. Are there any other tasks to execute? If Yes, those tasks are waiting for the tasks
upon which they are dependent to complete. Loop back and try again.
11. Loop until the workers complete.
12. Check the completion status of the workers. If any of the workers exited with error,
the plan is invalid and the Snapshot exits with an error.
The above diagram illustrates the Snapshot Worker Process logic. Below is a detailed
explanation of the logic.

1.
Check for the existence of the lock file. If the lock file exists, the Snapshot was able
to acquire table locks. Therefore, tasks requiring table locks may be executed.
2.
Are there tasks that have not yet been executed, that require a table lock, and do not
have tasks upon which they are dependent that have not yet completed? If so,
execute those tasks.
3.
Are there any tasks that have not yet been executed, and do not have tasks upon
which they are dependent that have not yet completed? If yes, execute those tasks.
4.
Have all tasks that require table locks been completed? If not, pause and return to
step 1.
See also Launching the Planning Process
Snapshot Parallel Processing

The Memory-based Snapshot takes a copy, or "snapshot," of all information used by the
planning processes so that the planning process can operate on a picture of data frozen
at a point in time and report against that snapshot at any future time.
The work performed by the snapshot can be broken down into individual tasks, such as
copying on-hand, discrete job, purchase order, bill of material, sourcing information,
and so on. These tasks are completely independent of each other and can be performed
in parallel. Each of these tasks consists of the following subtasks: deleting data from the
last plan run, taking a snapshot of the current data and creating a flat file, and loading
the flat file into the MRP tables. While creating the flat file does not require that old data
has been deleted, the flat file can only be loaded into the MRP tables after the data from
the last plan run has been deleted.
Oracle MRP maximizes the degree of multithreading in all these tasks and subtasks by
using multiple processes. For example, the Snapshot Delete Worker deletes the data; the
Snapshot and the Snapshot Workers create the flat files; the Loader Workers load the
data to MRP tables. The Snapshot Monitor coordinates all these tasks to minimize
processing time without violating dependencies among tasks.
See also Memory-based Planning Engine.
Planner Parallel Processing

The Memory-based Planner is the process within the planning engine that performs a
gross-to-net explosion. That is, for each level in the bill of material, it nets available
inventory and scheduled receipts against gross requirements, and recommends a set of
planned orders and order reschedules to meet gross requirements. The Memory-based
Planner passes demand from an assembly down to its components, and then performs
the same netting process on the components.
Thus, the Memory-based Planner first loads all the supply, demand, BOM, and
low-level code information into memory. In order to maximize multithreading Oracle
MRP ensure that the Memory-based Planner loads the data from the Snapshot
generated flat files rather than waiting until the data is loaded into the MRP tables.
After it has performed the gross-to-net explosion, the Memory-based Planner flushes
the output of the plan to MRP tables. Similar to the Memory-based Snapshot, it writes
the data to flat files and launches Loader Workers to load the data to MRP tables.
You can configure the Memory-based Snapshot to control how many Snapshot Workers
and Snapshot Delete Workers should be launched. To do so, define the profile option
MRP: Snapshot Workers. See Profile Options.
See Also:
Defining Managers and Their Work Shifts, in Oracle Applications User's Guide
Snapshot
Locking Tables Within the Snapshot
Planning Manager
The Planning Manager periodically performs many tasks that require processing rows
in an interface table. These are tasks such as forecast consumption, master production
schedule consumption, forecast interface load, schedule interface load, and master
demand schedule relief.
The Planning Manager has been designed to:
Process the work itself, if there are only a few rows to process, rather than incurring
the overhead of launching a new concurrent program.
Divide the work across one or more Planning Manager Worker processes if there
are many rows to process.
Launch more Planning Manager Workers when there are more rows to process, and
fewer workers when there are fewer rows to process.
Avoid delaying the processing of one task due to another task. For example, relief
of the master production schedule should not be delayed because the Planning
Manager is busy processing rows for forecast consumption.
Allow the user to configure the Planning Manager.
You can configure the Planning Manager to control how it divides the rows to be
processed, and across how many processes those rows are divided. You can define the
following profile options:
MRP: Planning Manager Batch Size
MRP: Planning Manager Workers
See Profile Options

The Planning Manager and Planning Manager Workers perform the following tasks:
Consume the master production schedule when work orders or purchase orders are
created
Consume the master demand schedule when sales orders have shipped
Consume the forecast when sales orders are entered
Load forecasts from outside systems when rows are inserted into the interface table
from an outside system
Load master schedules from outside systems when rows are inserted into the
interface table from an outside system
See also Starting the Planning Manager.

This is a detailed explanation of the Planning Manager Worker Process logic:
1.
Update rows in the interface table where the status indicates that they are waiting
to be processed. Update at most X rows, where X is the value of the profile option
MRP: Planning Manager Batch Size.
2.
Check to see if any rows were updated in Step 1. If not, there are no rows waiting to
be processed.
3.
Were the number of rows updated in Step 1 equal to the batch size? If not, all the
remaining rows in the interface table can be processed by this process. If the
number of rows updated equals the batch size, there could be more rows to process.
Go to Step 4 to try to launch a Snapshot Worker.
4.
The number of rows updated never exceeds the batch size, because we have limited
the update in Step 1 to be less than or equal to the batch size number of rows.
5.
It is possible that occasionally Oracle MRP launches a Snapshot Worker

unnecessarily if the number of rows processed exactly matches the batch size. This
is not a serious problem, however, as that extra worker simply wakes up, sees there
is nothing to process, and exits.
6.
Is the number of Planning Manager Workers running or pending less than the
maximum number of workers? If yes, launch a Planning Manager Worker.
Otherwise, do not launch a new Planning Manager Worker.
7.
Process the rows that were updated in Step 1 according to the type of task being
performed. If any errors occur during processing, update the status of the row to "
Error". Otherwise, update the status of the row to "Processed".
8.
Is this process the Planning Manager or a Planning Manager Worker? If this is the
Planning Manager Worker, loop back to Step 1 and try to grab another set of rows
to process. If this is the Planning Manager itself that is running, there should be no
more rows to process. Do not grab more rows, as that may cause a delay in
processing other tasks.
9.
If this is the Planning Manager, move on to the next task to process. If there are no
other tasks to process this cycle, resubmit the Planning Manager to wake up again
after the interval of time set in the profile option. If this is a Planning Manager
Worker, terminate the program.
A
Tools Menu
Tools Menu
This appendix shows you the options available from the Tools menu
Tools Menu
Depending upon the currently active window and other conditions, the Tools menu
includes:
Work Dates
Displays work dates.
Week Start Dates
Displays work dates that are the beginning of the work period.
Period Start Dates
Displays work dates that are the beginning of the week.
Repetitive Period Start

Dates
Displays work dates that are the beginning of the repetitive

planning period.
Preferences
Navigates to the Preferences window where you can define

your display options for the horizontal plan and
supply/demand detail.
Horizontal Plan Current
Navigates to the Horizontal Plan window, where you can view

current supply/demand information for a list of items.
Enterprise View Current
Navigates to the Enterprise View window, where you can view

a summary of current supply/demand information. Supply
Chain Planning users can also include information from
multiple organizations when the current plan is a multiorg
plan and the current organization generated the plan.
Tools Menu A-1
On Hand
Navigates to the View On Hand Quantities window where you

can view quantities for items along with project and task
references, nettable and nonnettable quantities, and
subinventory locations. This gives you a more detailed picture
of nettable and nonnettable quantities than the Items window.
Copy Plan
Navigates to the Launch Copy Plan window. Once you have

generated an MPS, MRP, or DRP plan, you can make a copy
that is identical to the original You can then view, implement,
and replan either version, discarding the altered plan at any
time and preserving the original data.
Plan Status
Navigates to the Plan Status window. Information for the plan

referenced is presented in 3 tabbed regions allowing you to
view current and last options submitted, along with date
information.
SupplierItem Information
Navigates to the SupplierItem Attribute window. Information

in Oracle Purchasing. In this window you can define the
supplier capacity, processing lead times, the Delivery Calendar
pattern, and tolerance fence data.
See Also
Overview of Workday Calendar, Oracle Bills of Material User's Guide
Viewing Onhand Quantities
Making a Copy of a Completed Plan
Defining the Supplier/Item, Oracle Purchasing User's Guide
Defining the Supplier and Commodity/Item Combination, Oracle Purchasing User's

Guide
Kanban Tools Menu
A-2 Oracle MRP User's Guide
B

Windows and paths specific to MRP appear in italic. Windows and paths specific to
Supply Chain Planning appear in bold. Although your system administrator may have
customized your navigator, typical navigational paths include the following:
Note: Text in brackets ([ ]) indicates a button.
For windows described in other manuals:
See...
Refer to this manual for a complete window description
BOM
CST
Oracle Cost Management User's Guide
Flex
Oracle Applications Flexfields Manual
GL
Oracle General Ledger User's Guide
HR
Oracle Human Resources User's Guide
IN
PO
Oracle Purchasing User's Guide
Windows and Navigator Paths B-1
SYS
- Oracle E-Business Suite Setup Guide

- Oracle E-Business Suite Maintenance Guide
- Oracle E-Business Suite Concepts
- Oracle E-Business Suite Security Guide
User
Oracle Applications User's Guide
Material Planner, Supply Chain Planner, and Distribution Planner Responsibility

Window Name
Navigation Path
Available Resources
MRP > Workbench > [Resources] > [Availability]
Sourcing > Bills of Distribution
Change Organization
Other > Change Organization
Compare Kanban Plans
Kanban > Kanban Planning > Kanban Planner Workbench

[Compare]
Components
DRP > Workbench [Items] > [Components]

MPS > Workbench [Items] > [Components]
MRP > Workbench [Items] > [Components]
Other > Request > Open
Other > Request
Consume Forecast Set
Forecast > Consume Set

Forecast > Items [Consume]
Forecast > Sets [Consume]
Copy/Merge Forecast
Forecast > Copy

Forecast > Sets [Copy/Merge Forecast]
B-2 Oracle MRP User's Guide

Window Name
Navigation Path
Forecast > Items [Copy/Merge]
DEMAND_CLASS Lookups 1 29
Setup > Demand Class
Destinations
DRP > Workbench [Items] > [Destinations]

MPS > Workbench [Items] > [Destinations]
MRP > Workbench [Items] > [Destinations]
DRP > Names
DRP Planner Workbench
DRP > Workbench

DRP > View Plan
End Assemblies
DRP > Workbench [Items] > [End Assemblies]

MPS > Workbench [Items] > [End Assemblies]
MRP > Workbench [Items] > [End Assemblies]
Enterprise View
DRP > Workbench [Items] > [Enterprise View]

MPS > Workbench [Items] > [Enterprise View]
MRP > Workbench [Items] > [Enterprise View]
Exceptions
DRP > View Plan [Exceptions]

DRP > Workbench [Exceptions]
Inquiry > MPS > Workbench [Exceptions]
Inquiry > MRP > Workbench [Exceptions]
MPS > View Plan > Status [Exceptions]

Window Name
Navigation Path
MPS > Workbench [Exceptions]
MRP > View Plan > Status [Exceptions]
Exception Details
DRP > View Plan [Exceptions] > [Exception Details]

DRP > Workbench [Exceptions] > [Exception Details]
Inquiry > MPS > Workbench [Exceptions] > [Exception
Details]
Inquiry > MRP > Workbench [Exceptions] > [Exception
Details]
MPS > View Plan > Status [Exceptions] > [Exception
Details]
MPS > Workbench [Exceptions] > [Exception Details]
Exception Summary
DRP > View Plan [Exceptions]

DRP > Workbench [Exceptions]
Inquiry > MPS > Workbench [Exceptions]
Inquiry > MRP > Workbench [Exceptions]
MPS > View Plan > Status [Exceptions]
MPS > Workbench [Exceptions]
MRP > Workbench [Exceptions]
Find Items
DRP > Workbench [Items]

Window Name
Navigation Path
MRP > Workbench [Items]
MPS > Workbench [Items]
Find Supply/Demand
DRP > Workbench [Supply/Demand]

MRP > Workbench [Supply/Demand]
MPS > Workbench [Supply/Demand]
Forecast > Entries [Bucketed]
Forecast > Items [Bucketed]
Forecast > Sets [Forecast Set Items] > [Bucketed]
Forecast > View Entries [Bucketed]
Forecast > View Items [Bucketed]
Forecast > View Sets [Forecast Set Items] >
[Bucketed]
Inquiry > Forecast > View Entries [Bucketed]
Inquiry > Forecast > View Items [Bucketed]
Inquiry > Forecast > View Sets [Forecast Set Items] >
[Bucketed]
Forecast > Entries [Bucketed] [Detail] >
[Consumptions]
Forecast > Entries [Consumptions]
Forecast > Items [Bucketed] > [Detail] >
[Consumptions]

Window Name
Navigation Path
Forecast > Items [Detail] > [Consumptions]
[Detail] > [Consumptions]
Forecast > Sets [Forecast Set Items] > [Detail]
[Consumptions]
Forecast > View Entries [Consumptions]
Forecast > View Items [Bucketed] > [Detail]
[Consumptions]
Forecast > View Items [Detail] > [Consumptions]
[Bucketed] [Detail] > [Consumptions]
Forecast > View Sets [Forecast Set Items] > [Detail]
[Consumptions]
Inquiry > Forecast > View Entries [Consumptions]
Inquiry > Forecast > View Items [Bucketed] > [Detail]
[Consumptions]
Inquiry > Forecast > View Items [Detail] > [Consumptions]
[Bucketed] [Detail] > [Consumptions]
[Detail] [Consumptions]
Forecast > Items [Bucketed] > [Detail]
Forecast > Items [Detail]

Window Name
Navigation Path
[Detail]
Forecast > Sets [Forecast Set Items] > [Detail]
Forecast > View Items [Bucketed] > [Detail]
Forecast > View Items [Detail]
Forecast > View Sets [Detail]
[Bucketed] [Detail]
Forecast > View Sets [Forecast Set Items] > [Detail]
Inquiry > Forecast > View Items [Bucketed] > [Detail]
Inquiry > Forecast > View Items [Detail]
Inquiry > Forecast > View Sets [Bucketed] > [Detail]
Inquiry > Forecast > View Sets [Detail]
Forecast > Items
Forecast > Sets [Forecast Items]
Forecast > Sets [Forecast Set Items]
Forecast > View Items
Forecast > View Sets [Forecast Set Items]
Forecast > View Sets [Forecast Items]
Inquiry > Forecast > View Items

Window Name
Navigation Path
Inquiry > Forecast > View Sets [Forecast Items]
Inquiry > Forecast > View Sets [Forecast Set Items]
Forecast > Sets
Forecast > View Sets
Inquiry > Forecast > View Sets
Forecast > Source List
Generate Forecast
Forecast > Generate
Horizontal Plan
DRP > Workbench [Demand] > [Horizontal Plan]

DRP > Workbench [Exceptions] > [Horizontal Plan]
DRP > Workbench [Items] > [Destinations]
[Horizontal Plan]
DRP > Workbench [Items] > [Horizontal Plan]
MPS > Workbench [Items] > [Sources] [Horizontal
Plan]
DRP > Workbench [Supply/Demand] > [Horizontal
Plan]
DRP > Workbench [Supply] > [Horizontal Plan]
MPS > Workbench [Demand] > [Horizontal Plan]
MPS > Workbench [Exceptions] > [Horizontal Plan]
MPS > Workbench [Items] > [Destinations] [Horizontal
Plan]

Window Name
Navigation Path
MPS > Workbench [Items] > [Horizontal Plan]
MPS > Workbench [Items] > [Sources] [Horizontal
Plan]
MPS > Workbench [Supply/Demand] > [Horizontal
Plan]
MPS > Workbench [Supply] > [Horizontal Plan]
MRP > Workbench [Demand] > [Horizontal Plan]
MRP > Workbench [Exceptions] > [Horizontal Plan]
MRP > Workbench [Items] > [Destinations] [Horizontal
Plan]
MRP > Workbench [Items] > [Horizontal Plan]
MRP > Workbench [Items] > [Sources] [Horizontal
Plan]
MRP > Workbench [Supply/Demand] > [Horizontal
Plan]
MRP> Workbench [Supply] > [Horizontal Plan]
Item Forecast Entries
Forecast > Entries

Forecast > View Entries
Inquiry > Forecast > View Entries
Item Master Demand Schedule

Entries
Inquiry > MDS > View Entries
MDS > Entries

MDS > View Entries

Window Name
Navigation Path
Item Master Production Schedule

Entries
Inquiry > MPS > View Entries
MPS > Entries

MPS > View Entries
Items
DRP > Workbench [Items]

DRP > Workbench [Items] > [Destinations] [Items]
DRP > Workbench [Items] > [Sources] [Items]
MPS > Workbench > [Items]
MPS > Workbench [Items] > [Destinations] [Items]
MPS > Workbench [Items] > [Sources] [Items]
MRP > Workbench [Items]
MRP > Workbench [Items] > [Destinations] [Items]
MRP > Workbench [Items] > [Sources] [Items]
Kanban Details

[Details]
Kanban Names
Kanban > Kanban Planning > Kanban Names
Kanban Workbench
Launch DRP
DRP > Launch

DRP > Names [Launch]
Launch DRP Copy Plan
DRP > Launch Copy Plan

Window Name
Navigation Path
DRP > Workbench > Launch Copy Plan
Launch Kanban
Kanban > Kanban Planning > Launch

Kanban > Kanban Planning > Kanban Names > [Launch]
Launch MPS
MPS > Launch

MPS > Names [Launch]
Launch MPS Copy Plan
MPS > Launch Copy Plan

MPS > Workbench > Launch Copy Plan
Launch Supply Chain MPS Copy

Plan
MPS > Launch Copy Plan
MPS > Workbench > Launch Copy Plan

Launch MRP
MRP > Launch

MRP > Names [Launch]
Launch MRP Copy Plan
MRP > Launch Copy Plan

MRP > Workbench > Launch Copy Plan
Launch Supply Chain MRP Copy

Plan
MRP > Launch Copy Plan
MRP > Workbench > Launch Copy Plan

Load/Copy/Merge Master Demand
Schedule
MDS > Items [Load/Copy/Merge]
MDS > Load/Copy/Merge

Window Name
Navigation Path
Load/Copy/Merge Master Production

Schedule
MPS > Load/Copy/Merge MPS
Master Demand Schedule Bucketed

Entries
Inquiry > MDS > View Items [Bucketed]
Inquiry > MDS > View Entries [Bucketed]

MDS > Entries [Bucketed]
MDS > Items [Bucketed]
MDS > View Entries [Bucketed]
MDS > View Items [Bucketed]
Master Demand Schedule Entries
Inquiry > MDS > View Items [Bucketed] > [Detail]

Inquiry > MDS > View Items [Detail]
MDS > Items [Bucketed] > [Detail]
MDS > Items [Detail]
MDS > View Items [Bucketed] > [Detail]
MDS > View Items [Detail]
Master Demand Schedule Items
Inquiry > MDS > View Items

MDS > Items
MDS > View Items
Master Demand Schedule Reliefs
Inquiry > MDS > View Entries [Reliefs]

Inquiry > MDS > View Items [Bucketed] > [Detail] >
[Reliefs]

Window Name
Navigation Path
Inquiry > MPS > View Items [Detail] > [Reliefs]
MPS > Entries [Reliefs]
MPS > Items [Bucketed] > [Detail] [Reliefs]
MPS > Items [Detail] > [Reliefs]
MPS > View Entries [Reliefs]
MPS > View Items [Bucketed] > [Detail] [Reliefs]
MPS > View Items [Detail] > [Reliefs]
Master Production Schedule Source

List
MPS > Source List
Master Production Schedules
MPS > Names
MPS Planner Workbench
Inquiry > MPS > Workbench

MPS > View Plan
MPS > Workbench
MRP Names
MRP > Names
MRP Planner Workbench
Inquiry > MRP > Workbench

MRP > Workbench
MRP > View Plan
Personal Profile Values
Other > Profile
Plan Options
DRP > Options

DRP > Names [Options]

Window Name
Navigation Path
MPS > Options
MPS > Names [Options]
MRP > Options
MRP > Names [Options]
Plan Organizations
DRP > View Plan Status [Plan Organizations]

DRP > Workbench [Options] > [Plan Organizations]
DRP > Names [Options] > [Plan Organizations]
MPS > View Plan Status [Plan Organizations]
MPS > Workbench [Options] > [Plan Organizations]
MPS > Names [Options] > [Plan Organizations]
MRP > View Plan Status [Plan Organizations]
MRP > Workbench [Options] > [Plan Organizations]
MRP > Names [Options] > [Plan Organizations]
Plan Status
DRP > View Plan Status

DRP > Workbench [Status]
Inquiry > MPS > Status
Inquiry > MRP > Status
MPS > View Plan Status
MPS > Workbench [Status]

Window Name
Navigation Path
MRP > View Plan Status
MRP > Workbench [Status]
Planner Tasks
DRP > Workbench [Status] > [Planner Tasks]

DRP > View Plan Status [Planner Tasks]
Inquiry > MPS > Status [Planner Tasks]
Inquiry > MRP > Status [Planner Tasks]
MPS > View Plan Status [Planner Tasks]
MPS > Workbench [Status] > [Planner Tasks]
MRP > View Plan Status [Planner Tasks]
MRP > Workbench [Status] > [Planner Tasks]
Setup > Exception Set
PLANNING_GROUP Lookups
Setup > Planning Group
Planning Manager
Setup > Planning Manager
Planning Parameters
Setup > Parameters
Request Diagnostics (See User)
Help Menu: View My Requests > Diagnostics
Resource
DRP > Workbench > [Resource]

MRP > Workbench [Resource]
MRP > Workbench [Exceptions] [Resource]
SHIP_METHOD QuickCodes (See IN)
Setup > Ship Method

Window Name
Navigation Path
Snapshot Tasks
DRP > Workbench > Status [Snapshot Tasks]

DRP > View Plan > Status [Snapshot Tasks]
DRP > View Plan Status [Snapshot Tasks]
Inquiry > MPS > Status [Snapshot Tasks]
Inquiry > MPS > Workbench [Snapshot Tasks]
Inquiry > MRP > Status [Snapshot Tasks]
Inquiry > MRP > Workbench [Snapshot Tasks]
MPS > View Plan > Status [Snapshot Tasks]
MPS > View Plan Status [Snapshot Tasks]
MPS > Workbench > Status [Snapshot Tasks]
MRP > View Plan > Status [Snapshot Tasks]
MRP > View Plan Status [Snapshot Tasks]
MRP > Workbench > Status [Snapshot Tasks]
Sources
DRP > Workbench [Items] > [Sources]

MPS > Workbench [Items] > [Sources]
MRP > Workbench [Items] > [Sources]
Sourcing Rule/Bill of Distribution
Sourcing > Bills of Distribution

Sourcing > Sourcing Rules
Sourcing > View Sourcing Rules

Window Name
Navigation Path
Sourcing Rule/Bill of Distribution

Assignments
Sourcing > Assign Sourcing Rule/BOD
Sourcing > View Assignments

Subinventory Netting
DRP > Names [Options] > [Subinventory Netting]

DRP > View Plan Status [Plan Organizations]
[Subinventory Netting]
DRP > Names [Options] > [Plan Organizations]
MPS > Names [Options] > [Subinventory Netting]
MPS > Names [Options] > [Plan Organizations]
MPS > View Plan Status [Plan Organizations]
MRP > Names [Options] > [Subinventory Netting]
MRP > Names [Options] > [Plan Organizations]
MRP > View Plan Status [Plan Organizations]
Submit Requests (See User)
Report
Inquiry > Report
Supply/Demand Detail
DRP > View Plan [Demand]

DRP > View Plan [Exceptions] > [Demand]
DRP > View Plan [Exceptions] > [Supply/Demand]

Window Name
Navigation Path
DRP > View Plan [Exceptions] > [Supply]
DRP > View Plan [Items] > [Demand]
DRP > View Plan [Items] > [Supply/Demand]
DRP > View Plan [Items] > [Supply]
DRP > View Plan [Supply/Demand]
DRP > Workbench [Demand]
DRP > Workbench [Exceptions] > [Demand]
DRP > Workbench [Exceptions] > [Supply/Demand]
DRP > Workbench [Exceptions] > [Supply]
DRP > Workbench [Items] > [Demand]
DRP > Workbench [Items] > [Supply/Demand]
DRP > Workbench [Items] > [Supply]
DRP > Workbench [Supply/Demand]
DRP > Workbench [Supply]
Inquiry: MRP > View Plan [Demand]
Inquiry: MRP > View Plan [Exceptions] > [Demand]
Inquiry: MRP > View Plan [Exceptions] >
[Supply/Demand]
Inquiry: MRP > View Plan [Exceptions] > [Supply]
Inquiry: MRP > View Plan [Items] > [Demand]

Window Name
Navigation Path
Inquiry: MRP > View Plan [Items] > [Supply/Demand]
Inquiry: MRP > View Plan [Items] > [Supply]
Inquiry: MRP > View Plan [Supply/Demand]
Inquiry: MRP > View Plan [Supply]
MRP > View Plan [Demand]
MRP > View Plan [Exceptions] > [Demand]
MRP > View Plan [Exceptions] > [Supply/Demand]
MRP > View Plan [Exceptions] > [Supply/Demand]
MRP > View Plan [Exceptions] > [Supply]
MRP > View Plan [Items] > [Demand]
MRP > View Plan [Items] > [Supply/Demand]
MRP > View Plan [Items] > [Supply]
MRP > View Plan [Supply/Demand]
MRP > View Plan [Supply]
MRP > Workbench [Demand]
MRP > Workbench [Exceptions] > [Demand]
MRP > Workbench [Exceptions] > [Supply/Demand]
MRP > Workbench [Exceptions] > [Supply]
MRP > Workbench [Items] > [Demand]

Window Name
Navigation Path
MRP > Workbench [Items] > [Supply/Demand]
MRP > Workbench [Items] > [Supply]
MRP > Workbench [Supply/Demand]
MRP > Workbench [Supply]
Inquiry: MPS > View Plan [Demand]
Inquiry: MPS > View Plan [Exceptions] > [Demand]
Inquiry: MPS > View Plan [Exceptions] >
[Supply/Demand]
Inquiry: MPS > View Plan [Exceptions] > [Supply]
Inquiry: MPS > View Plan [Items] > [Demand]
Inquiry: MPS > View Plan [Items] > [Supply/Demand]
Inquiry: MPS > View Plan [Items] > [Supply]
Inquiry: MPS > View Plan [Supply/Demand]
Inquiry: MPS > View Plan [Supply]
MPS > View Plan [Demand]
MPS > View Plan [Exceptions] > [Demand]
MPS > View Plan [Exceptions] > [Supply/Demand]
MPS > View Plan [Exceptions] > [Supply]
MPS > View Plan [Items] > [Demand]
MPS > View Plan [Items] > [Supply/Demand]

Window Name
Navigation Path
MPS > View Plan [Items] > [Supply]
MPS > View Plan [Supply/Demand]
MPS > View Plan [Supply]
MPS > Workbench [Demand]
MPS > Workbench [Exceptions] > [Demand]
MPS > Workbench [Exceptions] > [Supply/Demand]
MPS > Workbench [Exceptions] > [Supply]
MPS > Workbench [Items] > [Demand]
MPS > Workbench [Items] > [Supply/Demand]
MPS > Workbench [Items] > [Supply]
MPS > Workbench [Supply/Demand]
MPS > Workbench [Supply]
View Bill of Distribution
Sourcing > View Bills of Distribution
View Kanban Demand

> [Demand]
> [Details] > [Demand]
View My Requests (See User)
Help Menu: View My Requests
View My Requests (See User)
DRP > Workbench [Items]Tools menu >Onhand

MPS > Workbench > [Items]Tools menu >Onhand

Window Name
Navigation Path
MRP > Workbench [Items] Tools menu >Onhand
View Sourcing Assignment

Hierarchy
Sourcing > View Sourcing Hierarchy
View Sourcing Rule
Sourcing > View Sourcing Rules
View Sourcing Rule/Bill of

Distribution Assignments
Sourcing > View Assignments [View Sourcing Rule]
Sourcing > View Sourcing Hierarchy [View

BOD/Sourcing Rule]
Sourcing > View Assignments [View Supply Chain
Bill]
Sourcing > View Supply Chain Bill
Where Used
DRP > Workbench [Items] > [Where Used]

MPS > Workbench [Items] > [Where Used]
MRP > Workbench [Items] > [Where Used]
C
Alerts
Alerts
This appendix shows you the alerts for Oracle MRP.
Oracle MRP includes two precoded alerts you can use with or without customizing.
These alerts help you identify forecast overconsumption:
Forecast Overconsumption Summary
Forecast Overconsumption Detail

This alert notifies you when forecast overconsumption has occurred.
Alert Type Periodic Periodicity Every N calendar days Inputs None
Distribution Departments responsible for preparing forecast

This alert notifies you when forecast overconsumption has occurred. You must enable
this alert and also customize the distribution list.
Alert Type
Periodic
Periodicity
Every N calendar days
Inputs
None
Distribution
Departments responsible for preparing forecast
Alerts C-1
See Also
Overview of Oracle Alert, Oracle Alert User's Guide Using Precoded Alerts, Oracle Alert
User's Guide
C-2 Oracle MRP User's Guide
D

This appendix describes the customized find windows used in Oracle MRP.
Oracle Applications offers two windows to query records in your current block or
window: list windows and find window. The list window shows all the possible records
that you can retrieve for the block, a find window contains fields for entering search
criteria.
You can invoke a list or find window from the Query menu. However, some windows
in OracleMRP, such as Items and Supply/Demand, have their own, customized find
windows. To reach one of these main windows, you must first perform a query/find,
using the customized find window associated with it.
These customized find windows employ Oracle folder technology, allowing you to save
and implement frequently used or complex searches.
See Also:
Navigating through a Find Window:
Items Find Window
Exceptions Find Window:
Using Query Find, Oracle Applications User's Guide Using Query Operators, Oracle
Applications User's Guide Customizing the Presentation of Data in a Folder, Oracle
Applications User's Guide
Navigating through a Customized Find Window

When you navigate to a window which has a customized find window attached to it,
you must respond to the find window before displaying the window you want to work
with. You can either start a search, with manually entered or predefined criteria, or you
Customized Find Windows D-1
can retrieve all available records by leaving all fields blank and choosing Find.
If you decide to narrow your search, you must enter a search string in the first row of
fields in the find window. If you enter more search strings on subsequent lines, a data
record must match both criteria to be retrieved. It will not be retrieved when it matches
only one of the search strings. Multiple search strings assume the logical form (string1)
AND (string2), where string1 and string2 are search strings entered on separate lines in a
find window.
To enter a search string:
1.
Navigate to the Find window
2.
Enter a search criteria in the Field field. This will direct the search to that column in
the relevant table.
3.
Enter an operator in the Condition field. You can choose from a list of valid
operators that determine the conditions you want the data records to satisfy.
Depending on the type of condition you enter, you may be required to enter a
single value (in the From field) or a range of criterion values (in the From and To
fields). Criterion values may be numbers or character strings.
4.
When you have finished entering your search string, choose Find to start the query.
Saving your search in a folder

Use Oracle folder technology to save search strings for later use. This features is
particularly useful when you have complex or frequently used strings, strings whose
entry would be laborious or prone to error.
To define and save your folder criteria in the Material Workbench form, use the Find
window. Do not use personal and public shortcuts.
See Also:
Querying Records in a Folder, Oracle Applications User's Guide. Using Query Find, Oracle
Applications User's Guide Using Query Operators Oracle Applications User's Guide
Customizing the Presentation of Data in a Folder, Oracle Applications User's Guide
Find Exceptions Window

The Find Exceptions window allows you to retrieve exceptions generated by the latest
run of the current plan, and all exception counts saved from prior simulation replans.
Each replan is assigned a version number, and total counts per message are saved for
comparison. After you regenerate the plan, all versions are erased, and only the
"current" version exists.
1.
D-2 Oracle MRP User's Guide
2.
Select a plan name.
3.
Optionally, select a planner.
4.
Choose Exceptions to display the Find Exceptions window

The Find Exceptions window allows you to search for the following information:
Buyer: any valid buyer name
Category: any valid category name (family and class)
Exceptions: any of the unacceptable planning conditions identified during the
planning process
Item: a single item or range of items
Organization: any valid organization name
Note: If you search a mutli-org plan for organizations other than
the one you are logged into, you must be logged into the
organization that generated the plan; otherwise, otherwise you can
search only for your current organization.
Planner: any valid planner name

Planning Group: any valid planning group name
Project: any valid project reference
Task: any valid task ID
Note: Planning Group, Project and Task criteria match only those
exceptions that contain project references. These exceptions are

Items with a shortage in a project, Items with excess inventory in a project
, and Items with supply allocated across projects.)
Version: the number(s) associating exceptions with previous planning runs

5.
To retrieve all records, leave all fields blank and choose Find.
6.
The retrieve a subset of records, enter a search string. You can use just one string in
your search (containing a criterion, an operator, and a value), or you can enter
several strings to refine your search.
7.
Once you have entered at least one string, containing a field name, a condition, and
(optionally) a value, choose Find to start your search.
8.
Optionally, choose a folder to import a previously defined search strings and start
the search.
To sort data on multiple levels

Check Display Message Count opposite the row containing your search string.
The Exceptions window displays all data by exception message and version. That is, for
records found in your search, the data is sorted by exception message, which appears in
the first column. All other data appears in columns to the right.
However, you may want to sort this information further. For instance, you search for
organizations NYC and SAC. The Exceptions window will display all exceptions
generated by all runs of the current plan for items in NYC and SAC. However, while
the window displays the exceptions in the left hand column, it will not display NYC or
SAC in the fields opposite, nor will you be able to determine which exceptions appear
in NYC, SAC, or in both organizations. Moreover, the window will display only the
total number of instances of each message retrieved. You will not see a count of a
particular exception in NYC or SAC.
Checking Display Message Count changes the display so that the data is sorted by
exception, and sorted again by the criterion you chose, for as many criteria as you
choose. For instance, searching for and sorting by organizations NYC and SAC will
show the exception message on two lines, one with a count for NYC and one with a
count for SAC.
You can only sort project-related exceptions by Planning Group, Project and Task
criteria. These exceptions are Items with a shortage in a project, Items with excess inventory
in a project, and Items with supply allocated across projects.
See Also
Items Find Window
Using Query Find, Oracle Applications User's Guide Using Query Operators, Oracle
Applications User's Guide
Find Items Window

The Find Items window allows you to display basic information for the items in the
current plan, plus pegging and supply/demand information.
1.
2.
Select a plan name.
3.
Choose Item to display the Find Items window (mrp_fitems.gif)

The Find Items window allows you to search for the following information:
Item Details
ABC Class
BOM Item Type
MRP Planning Method
Buyer
Exception Set
Make or Buy
Category
Forecast Control
Organization
Item
Nettable Quantity
Nonnettable quantity
Planner
Standard Cost
WIP Supply Type
Repetitive
4.
5.
To retrieve a subset of records, enter a search string. You can use just one string in
6.
7.
the search.
See Also
Using Query Find, Oracle Applications User's Guide
Using Query Operators, Oracle Applications User's Guide
Find Supply/Demand Window

The Find Supply/Demand window allows you to display all supply and/or demand
information for the items in your plan.
Note: These instructions also apply to the Find Supply and Find
Demand windows.
1.
2.
Select a plan name.
3.
Optionally, select a planner. When you open the planner Workbench and navigate
to one of the details windows (such as items or exceptions), you will be asked if you
want select a planner. Doing so may improve workbench performance, however
you will be asked to select a planner once for each session in the workbench.
4.
Choose Supply/Demand to display the Find Supply/Demand window.

(mrp_findsd.gif)
The Find Supply/Demand window allows you to search for the following
information:
Supply/Demand Details
Firm
BOM Item Type
Disposition Status Type
Category
Compression Days
Days from Today
Item
First Unit Start Date
Implemented Quantity
Line
First Unit Completion Date
MRP Planning Method
Planner
Last Unit Start Date
Make or Buy
Organization
Last Unit Completion Date
New Due Date
Repetitive
Project Number
New Quantity
Rescheduled
Quantity in Process
Old Due Date
Source Supplier
Quantity/Rate
Old Order Quantity
Supplier
Selected to Release
Source Organization
WIP Supply Type
Source supplier Site
Using Assembly
5.
6.
The retrieve a subset of records, enter a search string. You can use just one string in
7.

8.
the search.
See Also
Items Find Window
Using Query Operators, Oracle Applications User's Guide
E
Planning Exception Messages Workflow

This appendix provides detailed information about planning exception messages
generated through the workflow process in Oracle MRP.
The Planning Exception Messages workflow allows you to automate the processing of
reviewing exceptions in order to take corrective action quickly when generating
materials and resource plans. This allows you to identify potential conflicts and the
status of resources. You can then take appropriate action to resolve these issues.
Exception messages are routed to key contacts for specific responsibilities. Recipients
can be supplier and customer contacts as well as internal personnel. Suppliers and
customers can use Oracle Supply Management Portal or Oracle Web Customers to see
detailed information related to the exception condition. The process for resolving
exceptions could involve following established procedures, routing information,
obtaining authorization, and updating information concerning materials. This workflow
consists of processes viewable in the Workflow Builder as a diagram, some of whose
objects and properties can be modified. The Planning Exception Messages workflow lets
you do the following tasks:
Initiate appropriate corrective action
View recipients, and have the system route exception messages accordingly
View the actions available to the recipient of the notification
View approval steps and the flow the process will follow
You can view or modify this workflow in the Oracle Workflow Builder. See Oracle
Workflow Guide.
See Also
Customizing the Planning Exception Messages Process: The Planning Exception
Workflow - Planning Exception Messages E-1
Messages Item Type
Summary of Planning Exception Messages Activities
Summary of Exception Process 1
Customizing the Planning Exception Messages Process

Use the Oracle Workflow Builder to customize workflows. You can also use the
Workflow Builder to create unique planning exception messages workflows for
different parts of your organization and associate particular workflows with certain
activities.
To display the process in Oracle Workflow Builder:
1.
Choose Open from the File menu, and connect to the database. See: Opening and
Saving Item Types, Oracle Workflow Guide.
The display name of the exception messages workflow is Planning Exception
Messages. The name of its Workflow definition file is mrpexpwf.wft
2.
Expand the data source, then the Exception Message branch within that data
source.
3.
Expand the Processes branch, then choose the Exception Process activity to display
the diagram.
Creating a New Custom Process

Customize the default (original) workflow that Oracle MRP provides after creating a
backup. This allows you to have your backup while testing customizations.
Required Modifications
There are no required modifications you need to make to this workflow.
Supported and Unsupported Customizations

Although you can use the Planning Exception Messages process as is, you may wish to
customize the process further to accommodate your organization's specific needs.
You could create new functionality in the PL/SQL procedures and add the nodes to the
workflow diagram. Or you could modify the activities and redirect the process in the
workflow, such as sending notification to people other than the planner.
Attributes
You can add new item type attributes to the workflow, but it is not advisable to modify
the existing attributes.
E-2 Oracle MRP User's Guide
Processes
If you modify a process, it is essential that the basic flow remain intact in order to
maintain data integrity in the database. However, you could add additional checks
(processes or function activities) before allowing data to be inserted into the tables.
If you modify any process, either by replacing a portion of its flow or by adding
additional function activities, remember the following:
Attributes that are set by default function activities in the default processes must
also be set if you replace default function activities with ones of your own. That is, if
a function activity in that process uses a SetItemAttr statement, then that function
activity is setting an attribute to be used by another function activity later.
Therefore, your new function activity must do the same. You should also preserve
SetItemUserKey and SetItemOwner statements, if any (You may also want to preserve
GetItemAttrstatements.)
Any database state maintained by the default processes must also be maintained by
processes you customize. That is, if a function activity in that process uses an
Update or Insert.
Into statement, then that function activity is updating or inserting rows in the
database. Therefore, your new function activity must maintain the same database
state.
Notifications
All of the notifications can be modified to meet your individual business needs.
However, if the notification has a reply code, you must make sure that the Result Type
of your customized notification matches the Result Type of the default notification.
Messages
All of the messages can be modified to meet your individual business needs. For a list of
the types of exceptions that may occur when you run your plan. See: Reviewing
Planning Exceptions.
Messages are sent to particular recipients depending on the exception type. For
example, in Process 3 of the Planning Exception Messages workflow, exception types 13
and 15 are sent at Node 5 after a planner is found. See:Summary of Exception Process 3.
To view messages by exception types, select Messages in the navigator tree, and expand
the file. A listing of all the messages in the Planning Exception Messages workflow
displays in order of the exception type. Select the message, you can see the text of the
message in the Description box.
Lookup Types
All of the lookup types can be modified to meet your individual business needs.
Note: If you change a lookup type, you must be sure that all
notifications and processes that use the lookup type allow for the
change. For example, if you change the lookup type from Yes/No to
something else, the activities that use that lookup type should also
change their Result Type from Yes/No to whatever new lookup type
you created.
Planning Exception Messages Item Type

The Exception Messages process is associated with an item type called Planning
Exception Messages, MRPEXPW. This item type identifies all workflow processes
available. All exception types are grouped into four workflow processes:
Exception Process 1
Exception Process 2
Exception Process 3
Exception Process 4
If you examine the property page of Planning Exception Messages, you see that it calls a
selector function named MRP_EXP_WF. This selector function is an example PL/SQL
stored procedure that returns the name of the process to run when more than one
process exists for a given item type.
The Planning Exception Messages workflow item type also has a listing of attributes
associated with it. These attributes reference information in the demonstration
application tables. The attributes are used and maintained by function activities as well
as notification activities throughout the process.
To view descriptions of each item type attribute, select the attribute in the Workflow
Builder and choose Properties from the Edit menu. Look in the Description field.
Workflow Planning Exception Messages Workflow Type Attributes
Display Name
Description
Type
Found/Not Found
Message sent to Username of this person.
Text
Order Type
Type of order for the planning exception - values

include work order, purchase requisition, purchase
order, or other order type.
Number
Proceed/Stop
Indicates it the workflow process should continue or

terminate
Display Name
Description
Type
Reschedule Action
Indicates if the order is rescheduled, or not

rescheduled
Text
Summary of Planning Exception Messages Activities

To view the properties of the Planning Exception Messages processes, select the process
in the navigator tree, then choose Properties from the Edit menu. The Planning
Exception Messages process has no result type, indicating that when the process
completes, it has no defined result corresponding to any lookup type in the navigator
tree.
This process activity is runnable, indicating that it can be initiated as a top-level process
to run by making calls to the Workflow Engine CreateProcess and StartProcess APIs.
The Details property page of the process activity indicates that the Planning Exception
Message Top Process has an error process called DEFAULT_ERROR associated with it,
which gets initiated only when an error is encountered in the process. For example, if
you attempt to initiate the Planning Exception Message Top Process indicating a
planner who is not listed as a valid planner, the Workflow Engine would raise an error
when it tries to execute the Select Planner activity. This error would initiate
DEFAULT_ERROR, which is associated with the System:Error item type. Currently the
process simply executes the standard Default Error Notification activity to provide
information associated with the error. You can customize the process further to suit
your needs.

The process begins at Node 1.
After your MRP, MPS, or DRP plan has completed its run, the function at Node 2
determines if the workflow process should proceed. If the plan is marked as
production, it will proceed. Otherwise, it will continue to Node 3 and terminate.
At Node 4 the process attempts to select a planner based on plan, organization, and
item. If a planner is not found, the process ends at Node 5.
If the planner is selected, at Node 6 the workflow process directs the exception message
to that person.
When the message is sent, the activity is complete and the process ends at Node 7.
Exception Process 1 Activities

The following is a description of each activity in the Planning Exception Messages
Process 1, listed by the activity's display name.
Start (Node 1)
This is a standard function activity that simply marks the start of the subprocess.
Function - WF_STANDARD.NOOP
Result Type - None
Required - Yes
Prerequisite Activities - None
Item Attributes Set by Function - None
Item Attributes Retrieved by Function - None
Workflow Process Forward (Node 2)

This function activity determines if the workflow process should proceed. If the plan
option Production is checked on the MRP, MPS, or DRP Names window; the process
continues. If not, it is terminated.
Function - MRP_EXP_WF.DETERMINPROCEED
Result Type - Yes/No
Required - Yes
Item Attributes Retrieved by Function -
PLAN_NAME_ORGANIZATION_ID
End (Node 3, 5, 7)
This is a standard function activity that marks the end of the process.
Result Type - None
Required - Yes
Prerequisite Activities - Start
Select Planner (Node 4)

This function activity determines the planner who will receives notification based on
plan, organization and item. This activity also selects the appropriate message to be sent
based on exception type.
Function - MRP_EXP_WF.SELECTPLANNER
Result Type - Found/Not Found
Required - Yes
Item Attributes Set by Function - MESSAGE_NAME, FORWARD_TO_USERNAME
Item Attributes Retrieved by Function - PLAN_NAME, ORGANIZATION_ID,

INVENTORY_ITEM_ID, EXCEPTION_TYPE_ID,ORDER_TYPE_CODE
Notify Exception (Node 6)

This function activity calls a standard function which allows dynamic selection of
messages under one notification activity. The required activity attribute MESSAGE is
set to item attribute MESSAGE_NAME which was previously selected in Select Planner
node.
Function - WF_STANDARD.NOTIFY
Result Type - None
Required - Yes
Prerequisite Activities - Select Planner

At Node 4, the order type is determined to see which direction in the process the
workflow will branch. If the order type is a value other than work order, purchase
order, or purchase requisition; the process ends at Node 5.
If the order is a work order, the process continues to Node 6 and attempts to select a
planner. If a planner is not found, the process ends at Node 7.

If the planner is selected, at Node 8 an exception message about the work order is sent.
From this point, the planner can reschedule the order, the workflow proceeds to Node
27 for rescheduling procedures, and completes at Node 28. Otherwise, the workflow
terminates at Node 9 and the process ends.
At Node 4, if the order is a purchase requisition, the process continues to Node 10 and
attempts to select a planner. If a planner is not found, the process attempts to find a
buyer at Node 13. Otherwise, the process ends at Node 14.
If a planner is selected, at Node 11 the workflow process directs the exception message
to that person. The planner can move the information to the buyer at Node 13, or end
the process at Node 12.
If a planner is not found and the buyer is selected at Node 13, the reschedule
information is directed to that person at Node 15. If the buyer reschedules the order, the
workflow proceeds to Node 27 for rescheduling procedures and completes at Node 28.
Otherwise, the process end at Node 16.
At Node 4, if the order is a purchase order, the process continues to Node 17 and
attempts to select a planner. If a planner is not found, the process attempts first to find a
buyer at Node 20. And if that fails, attempts to find a supplier contact at Node 23.
Otherwise, the the process ends at Node 21.
If a planner is selected, at Node 18 the planner can move the exception message to the
buyer at Node 20, or end the process at Node 19.
The buyer receives exception information at Node 21, and moves the information to the
supplier contact at Node 23. Or the supplier contact can receive the information directly
from Node 4. Otherwise, the process ends at Node 24. If the workflow proceeds, at
Node 25, the reschedule information is sent to Node 27 for rescheduling procedures and
completes at Node 28. Otherwise, the process ends at Node 26.

Start (Node 1)
Result Type - None
Required - Yes

Required - Yes
Item Attributes Retrieved by Function - PLAN_NAME_ORGANIZATION_ID
End (Node 3, 5, 7, 9, 12, 14, 16, 19, 21, 24, 26, 28)
Result Type - None
Required - Yes
Determine Order Type (Node 4)

This function determines the order type defined in the current exception, and serves as
a branching point. Valid values for order types are work orders, purchase requisitions,
purchase order, and others.
Function - MRP_EXP_WF.DETERMINEORDERTYPE
Result Type - Order Type
Required - Yes
Item Attributes Retrieved by Function - EXCEPTION_ID, ORDER_TYPE_CODE
Select Planner (Node 6, 10, 17)

Required - Yes

Select Buyer (Node 13, 20)

This function activity determines the buyer who will receives notification, based on
plan, organization, and item. This activity also selects the appropriate message to be
sent based on exception type, thus overriding the message selected in Select Planner
function.
Function - MRP_EXP_WF.SELECTBUYER
Required - Yes
Item Attributes Set by Function - MESSAGE_NAME,
FORWARD_TO_USERNAME

Select Supplier Contact (Node 23)

This function activity determines the supplier contact who will receives notification.
This activity also selects the appropriate message to be sent based on exception type,
thus overriding the message selected in Select Buyer function type.
Function - MRP_EXP_WF.SELECTSUPPLIERCNT
Required - Yes
Prerequisite Activities - Select Buyer
Item Attributes Retrieved by Function -EXCEPTION_TYPE_ID,SUPPLIER_ID,

SUPPLIER_SITE_ID
Notify Exception/Reschedule - Work Order (Node 8)

node. Only the messages which contain information related to work orders are selected
from this activity. When the notification is reviewed, the recipient responds to it by
selecting either Reschedule or Do Not Reschedule.
Result Type - Rescheduling Action
Required - Yes
Notify Exception - Purchase Requisition (Node 11)

node. Only the messages which contain information related to purchase requisitions are
selected from this activity. When the notification is reviewed, the recipient responds to
it by selecting either Proceed or Stop.
Result Type - Proceed/Stop
Required - Yes
Notify Exception/Reschedule - Purchase Requisition (Node 15)

node. Only the messages which contain information related to purchase requisitions are
it by selecting either Reschedule or Do Not Reschedule.
Required - Yes
Notify Exception - Purchase Order (Node 18, 22)

node. Only the messages which contain information related to purchase orders are
it by selecting either Proceed or Stop.
Result Type - Proceed/Stop
Required - Yes
Prerequisite Activities - Select Planner or Select Buyer
Notify Exception/Reschedule - Purchase Order (Node 25)

node. Only the messages which contain information related to purchase orders are
it by selecting either Reschedule or Do Not Reschedule.
Required - Yes
Prerequisite Activities - Select Buyer
Rescheduling Procedure (Node 27)

This function activity performs a rescheduling/cancellation of work order and purchase
entities generated by the planning process. For order types Work order and Purchase
Requisition, both rescheduling and cancellation can be performed. See: Implementing
Planned Orders. For Purchase Orders, only rescheduling is performed by launching an
Oracle Purchasing workflow. See: Oracle Purchase Order Approval Workflow: page
NO TAG.
Function - MRP_EXP_WF.RESCHEDULE
Result Type - None
Required - Yes
Prerequisite Activities - Notify Exception/Rescheduling (Work Order, Requisition,

Purchase Order)
Item Attributes Retrieved by Function - EXCEPTION_ID, PLAN_NAME,

ORGANIZATION_ID, EXCEPTION_TYPE_ID,ORDER_TYPE_CODE

item. If a planner is not found, the workflow proceeds first to Node 7 to select a sales
representative, and if that fails to Node 9 for a customer contact. Otherwise, it will
continue to Node 10 and terminate.

to that person. The planner has the choice of stopping notification and terminating the
process at Node 6. Or proceeding and sending notification to the sales representative at
Node 7.
When the sales representative receives exception information at Node 8, the workflow
moves the information to the customer contact at Node 9. If a customer contact is found,
the message is sent at Node 11 and the activity is complete and the process ends at
Node 12. Otherwise, it will continue to Node 10 and terminate.

Start (Node 1)
Result Type - None
Required - Yes

Required - Yes
End (Node 3, 6, 10, 12)

Result Type - None
Required - Yes

plan, organization, and item. This activity also selects the appropriate message to be
sent based on exception type.
Required - Yes

Notify Exception (Node 5, 8, 11)

node.
Result Type - None
Required - Yes
Select Sales Representative (Node 7)

This function activity determines the sales representative who will receives notification
based on plan, organization and item. This activity also selects the appropriate message
to be sent based on exception type.
Function - MRP_EXP_WF.SELECTSALESREP
Required - Yes
Item Attributes Set by Function - FORWARD_TO_USERNAME
Item Attributes Retrieved by Function - CUSTOMER_ID
Select Customer Contact (Node 9)

This function activity determines the customer contact who receives notification.
Function - MRP_EXP_WF.CUSTOMERCNT
Required - Yes
Prerequisite Activities - Select Sales Representative
Item Attributes Retrieved by Function - CUSTOMER_ID

item. If a planner is not found, the workflow proceeds first to Node 6 to select a
task/project manager, and if that fails to Node 8 for other recipients. Otherwise, it will
continue to Node 9 and terminate.
to either the task or project manager. If both a task and project manager are found, the
notification is only sent to the task manager. At Node 7 the information is passed to
Node 8 to determine if more than one task/project manager should receive notification.
If another recipient is found at Node 10, the workflow proceeds to Node 12. the
message and the activity is complete and the process ends at Node 13. If no other
recipient is found, the workflow proceeds directly to Node 13, the activity is complete
and the process ends.

Start (Node 1)
Result Type - None
Required - Yes

Required - Yes
End (Node 3, 9, 11, 13)

Result Type - None
Required - Yes

Required - Yes

Notify Exception (Node 5, 7, 12)

node.
Result Type - None
Required - Yes
Select Task/Project Manager (Node 6)

This function activity determines the task manager or the project manager who will
receives notification based on plan, organization F - 22 and item. This activity also
selects the appropriate message to be sent based on exception type.
Function - MRP_EXP_WF.SELECTTASKMGR
Required - Yes
Item Attributes Retrieved by Function EXCEPTION_TYPE_ID,PROJECT_NUMBER, TASK_NUMBER,

TO_PROJECT_NUMBER, TO_TASK_NUMBER
Across Projects (Node 6)

This function activity determines if more than one task or project manager should
receive notification This activity also selects the appropriate message to be sent based
on exception type.
Function - MRP_EXP_WF.ISTYPE19
Required - Yes
Prerequisite Activities - Select Task/Project Manager
Item Attributes Retrieved by Function - EXCEPTION_TYPE_ID
See Also
Overview of Oracle Workflow Access Protection, Oracle Workflow Guide
Allowing Access to an Object, Oracle Workflow Guide
Reviewing Planning Exception
F
Forecasting - Statistical and Focus
Forecasts - Statistical and Focus

This appendix describes forecasts created by compiling statistical or focus forecasting
information.
Oracle Inventory provides a mechanism by which future demand may be forecast based
on historical demand. You can then load these forecasts into another forecast or a
master schedule. You can use the Load Forecast form to create a new forecast by
compiling statistical or focus forecasting information.
Focus forecasting is intended to produce only one period forecasts, whereas you can use
statistical forecasting to forecast any number of periods into the future.
Forecast Rules
If you intend to compile a focus or statistical forecast, you must first define a forecast
rule. This forecast rule defines the forecast bucket type, forecast method, and the
sources of demand. If the rule is a statistical forecast, the exponential smoothing factor
(alpha), trend smoothing factor (beta), and seasonality smoothing factor (gamma) are
also part of the rule.
You use a forecast rule in the Load Forecast form to compile a forecast for a particular
item or group of items into a forecast name. A forecast rule consists of the following
information:
Forecast Rule Name
Identify a forecast rule name that you can choose when loading a forecast.
Bucket Type
Specify a daily, weekly or periodic bucket to determine the time periods that forecasts
are compiled in.
Forecast Method
Choose to compile a forecast using either focus forecasting or a statistical forecasting
Forecasting - Statistical and Focus F-1
method.
Demand Sources
A forecast rule may apply to demand from any or all of the following:
inter-organization issues
miscellaneous issues, including account issues, account-alias issues, and

user-defined issues
sales order shipments
work in process issues
Additional Information for Statistical Forecast Rules

If the forecast rule is statistical, some additional information may be required:
alpha smoothing factor
beta smoothing factor, if the forecast is trend-enhanced
gamma smoothing factor, if the forecast is season-enhanced
initial seasonality indices, if the forecast is season-enhanced
number of past periods to use in forecast calculations
Focus Forecasting Methods

There are many ways to forecast future demand based on the past. It is sometimes
difficult to decide which forecasting method to use. Focus forecasting decides the
optimal method for compiling your forecasts.
The focus forecasting technique simulates alternate forecasting methods on prior
periods for which the actual demand is known. It then chooses the forecasting method
that would have produced the most accurate forecast for that period.
The following five simple forecasting models are provided:
The forecast for this period is the actual demand for the same period last year.
The forecast for this period is the actual demand for the previous period.
The forecast for this period is the average of the actual demands for the previous two
periods.
F-2 Oracle MRP User's Guide
The forecast for this period is the actual demand for the same period last year
multiplied by the growth (or decline) since last year as
measured by the ratio of the previous period actual demand to the actual demand for
the same period last year.
The forecast for this period is the actual demand for the previous period multiplied by
the current growth (or decline) as measured by the ratio of the previous period actual
demand to the actual demand for the period before the previous period.
Important: When you use daily time buckets, a week is used instead of
a year in calculating Models 1 and 4. Fifty-two week years are

presumed in yearly calculations with weekly time buckets. This means
that the same week last year is taken to be the week fifty-two weeks
before the current week.
These models are illustrated in the following table. Note that Models 1 and 4 require
over a year of historical data while the other three methods can be executed with only
two historical periods. Focus forecasting is restricted to only those models where
sufficient demand history exists.
To evaluate which forecasting model produced the best forecast last period, the
absolute percentage error (APE) is calculated for the five forecasts and the forecasting
model with the smallest APE is chosen. APE is the ratio of the difference between the
actual demand and forecast to the actual demand.
Forecast Year
January
February
March
April
2000
220
210
250
260
2001
270
255
290
Forecast Model
March 2001
Forecast
March 2001
Actual
Error (APE)
April 2001
Forecast
250
290
14%
260
255
290
12%
290
263
290
9%
273
304
290
5%
302
241
17%
330
Important: Numbers have been rounded.
In this table, the forecast for the previous month is calculated for Model 4 as follows:
Important: For purposes of the previous table, we rounded ? our
numbers off to the nearest integer. However, the forecast compile

process rounds forecasts off to five decimal places.
The error for Model 4 is therefore calculated:
Since 5% is the smallest error of the five models, Model 4 is chosen to calculate the April
2001 forecast:
Although focus forecasting is intended to provide a one-period forecast, if a focus

forecast is requested for multiple periods, the forecast for the first forecast period is
used for all forecast periods.
When actual demand information is available for the current period, the focus forecast
may be rerun to update the forecast.
Statistical Forecasting Methods
Statistical forecasting methods provide an alternate method that is based on a more
mathematical model called exponential smoothing forecast (ESF) or alpha smoothing
forecast. The statistical forecasts available are:
Exponential smoothing forecast (ESF)
Trend-enhanced forecast (TEF)
Season-enhanced forecast (SEF)
Trend and season-enhanced forecast (TSEF)
Exponential Smoothing Forecast (ESF)

In an ESF, demand is forecast by averaging all the past periods of actual demand and
weighs more recent data to give it greater influence over the forecast results than older
data. The weights are adjusted according to the exponential function f(x) = e (- ? x) where
x is the number of periods past and is a chosen value between 0 and 1. shows the alpha
function for three different values of; the larger the-value, the less weight is given to
older data and the more the forecast tends to chase the prior period's demand if demand
is not smooth.
Rather than calculate the exponential function for every period, it can be shown that the
ESF for period t can be easily calculated if we know the ESF for the prior period.
The initial value of ESFt is the actual demand for the prior period, At-1. The table shows
these calculations for three different values of.
Period t
Actual Demand
At
Forecast Eo = 0.9
Demand Eo = 0.5
ESFt Eo = 0.1
200
220
200
200
200
120
218
210
202
230
130
165
194
260
220
198
197
270
256
229
204
290
269
249
210
270
288
270
218
Forecast
272
270
223
Important: Numbers have been rounded.
The forecast for period 9, for = 0.9, is calculated:
Period 3 was an abnormal period, but otherwise the trend is clearly upward. It can be
seen that with the higher alpha, the forecast reacted intensely to the third period, and
produced a very low period 4 forecast, but was also faster to correct itself and adjust for
the trend. By period 9, the period we are forecasting, the abnormal period 3 has only a
negligible effect on the forecast. All three forecasts became more accurate when they
had more historical data upon which to draw.
It should be noted that, even though the higher alpha adjusted to the trend faster, plain
ESF always lags behind the trend by at least one period. Even if the demand in the
example had been smooth, all three scenarios would have lagged behind the trend.
Trend-Enhanced Forecast (TEF)
The statistical forecasting method provides an enhancement to the ESF that allows for
trend. The theory behind the trend-enhanced model is that we can take the ESF and add
a trend index, R, that reflects the current trend.
The ESF is no longer the forecast. We rename that term the base, Bt; since it is the base
value of the forecast to which we add the trend (and, in the case of a season-enhanced
forecast, seasonality indices). The formula becomes:
The base is found in the same way as the ESF, though:
Finally, we need a way to figure out the trend index, Rt. To do this, we need another
smoothing factor to smooth out changes in the trend. Similar to ESF, the higher this
factor, the more responsive it is to changes in trend. However, it increasingly gets
thrown off by abnormal period demand.
The initial value of Rt is the change in demand from two periods ago to the last period,
At-1 - A-2.
Period t
Actual Demand
At
Forecast Base
Bt
Trend Index Rt
Forecast
Demand TEFt
200
220
200
20
230
120
210
15
190
230
175
17
226
260
243
18
261
270
266
19
284
290
287
19
306
270
288
17
305
Forecast
Note: Numbers have been rounded.
The table gives an example of forecasting using the trend-enhanced model. The forecast
for period 9 is found by first calculating the forecast base value:
Then updating the trend index:
And, finally, adding the two for the period 9 trend-enhanced forecast:
Season-Enhanced Forecast (SEF)

In the tables, there was an outlying point in period 3 that threw all the forecasts off.
Suppose that the forecasting periods are manufacturing periods and period 3
corresponds to March, when demand for this item has traditionally been low. The
forecast should take this into account. This is especially important with highly seasonal
goods, such as winter clothing, holiday cards and decorations, and even vaccinations
and antibiotics (more people get sick during the winter than summer).
To take seasonal demand variations into account, you must first enter seasonality
indices for each period indicating how much demand during the period is above or
below average. A seasonality index of 2 indicates that demand during this period is
twice the average demand. Therefore, an index of 0.5 indicates that demand during this
period is half the average demand; 1 means demand is average during this period. If the
average seasonality index entered is not equal to 1, Oracle Inventory normalizes the
indices so that this is the case.
The same kind of logic that is used for adjusting for trend in the TEF is used to adjust
for the seasonal variations. Demand is deseasonalized by dividing by the seasonality
index for that period, and then exponential smoothing is used to produce a new base
value. The base value is then multiplied by the seasonal index for the period being
forecasted to produce the season-enhanced forecast (SEF).
The seasonality index for the prior season is adjusted using yet another user-specified
smoothing factor.
Period t
Actual
Demand At
Old Season
Index St
Forecast
Base Bt
Forecast
Demand
SEFt
New Season
Index S't
200
1.05
220
1.00
190
190
1.05
120
0.65
200
130
0.63
230
0.95
195
185
1.02
260
1.05
210
221
1.11
270
1.10
223
245
1.13
290
1.15
230
265
1.18
270
1.15
238
273
1.15
Forecast
1.10
237
260
This table shows an example of season-enhanced forecasting. Notice how, since a drop
in demand was expected in period 3, the forecast dropped in the same period in
anticipation.
We begin by adjusting last period's seasonality index:
The period 9 forecast can now be found by calculating the forecast base-value:
And then multiplying by the period 9 seasonality index:
When we receive period 9 results we can recalculate period 9's seasonality index and
then forecast for period 10.
Trend and Season-Enhanced Forecast (TSEF)
Despite the seasonal adjustments made in the SEF, there remained a trend element that
can be seen in the gradual increase in the forecast base, B. The TEF and the SEF may be
combined to make a trend and season-enhanced forecast (TSEF).
A combination of the TEF and SEF can be illustrated by showing the formulae and
example provided in the previous table. The TSEF uses all three smoothing factors.
Period
t
Actual
Demand
At
Old
Season
Index St
Forecast
Base Bt
200
1.05
220
1.00
190
120
0.65
200
230
0.95
260
Trend
Index Rt
Forecast
Demand
TSEFt
New Season
Index S't
190
1.05
10
137
0.63
201
199
0.99
1.05
221
10
242
1.07
270
1.10
236
11
272
1.10
290
1.15
247
11
296
1.14
270
1.15
255
10
306
1.11
Forecast
1.10
254
290
As with the SEF, we can calculate the new period 8 seasonality index as soon as period
8 results are in.
To make our period 9 forecast, we first calculate the period 9 basevalue:
And the new trend factor:
Add them together and multiply in the seasonality factor to get the period 9 trend and
season-enhanced forecast:
G

The Memory-based Planning Engine efficiently manages all the processes which
constitute a complete planning run. It utilizes a high degree of concurrency among the
snapshot tasks, eliminates nonvalue-added operations, and combines related tasks into
a single task. It moves long running tasks, such as deleting previous planning data and
loading snapshot data into the MRP snapshot tables out of the critical path. It also
utilizes interprocess communication to manage all the planning tasks. The
Memory-based Planning Engine is the only engine supported in the Oracle MRP
product.
Instead of waiting for all the data to be loaded into files and tables, the Memory-based
Planning Engine begins planning once calculations are loaded in memory. Greater
control over planning activities improves the planner's efficiency. The planning process
passes through fewer phases, greatly reducing planning lead time.
Tip: These topics are technical and are not intended for most users. It is
not necessary to read them to be able to use Oracle MRP.
There are eight main features of the Memory-based Planning Engine:
enhanced method of low-level code calculation: because component changes from

Work in Process and Bill of Material information appear in a single structure, the
planning engine performs loop-checking and low-level code calculation in one step
database loads performed in parallel, not sequentially
enhanced loop-checking: you can detect loops introduced by discrete and

nonstandard job component requirements, and by WIP component changes
flexible configuration: you can specify the number of Workers available to perform
snapshot tasks, taking advantage of hardware resources
Memory-based Planning Engine G-1
locked tables not required: the Memory-based Planning Engine gathers consistent
views of supply and demand data without locking users out of the system
efficient explosion technique, which occurs alongside the snapshot process
reduced number of tasks and simplified process dependencies
preprocessing and setup times: the memory-based engine performs netting

calculations based on snapshot data in memory
The Memory-based Planning Engine plays a significant role in several functions of

Oracle MRP. In some cases, the performance of functions and procedures are enhanced
by the engine. In other cases, you can perform functions and procedures only when the
current plan was generated with the engine. The following list contains all such
functions and procedures:
auto-release planned orders
byproduct planning
comparing current and snapshot data
full pegging
graphical display of planning data
net change replan
phantom assembly planning
See Also
Processing Steps
Processes
Snapshot Tasks
Read Consistency
Interprocess Communication
Configuring the Memory-based Planning Engine
G-2 Oracle MRP User's Guide
Processing Steps
The Memory-based Planning Engine executes the planning run in the following
sequence:
1.
Snapshot preprocessing. This is the first step preformed as a part of the Snapshot. It
consists of tasks that need to be done prior to the Snapshot. These tasks include
calculating repetitive planning periods for all the planned organizations and
auto-reducing the master production schedules.
2.
Item list determination. This step involves determining the items that will be
planned as part of the current planning run. The plan-level option included items
determines the items that will be planned. All other Snapshot activities cannot start
until this step is complete.
3.
Deleting old data. This step consists of cleaning all the snapshot and planner output
data from the previous planning run.
4.
Creating flat files of snapshot data. This step involves selecting the data from the
system tables and writing them to flat files. Since this data is written to flat files, the
deletes are not a prerequisite for this task.
5.
Loading flat files into the database. This step loads the Snapshot flat files into the
MRP Snapshot tables.
6.
Snapshot post-processing. This step consists of cleanup activity and execution of the
user-defined Snapshot tasks (such as updating item categories and ABC classes) in
MRP_SYSTEM_ITEMS.
7.
Netting. This step performs the gross-to-net explosion, during which suggested
supply orders are generated.
See Also
Processes Snapshot Tasks
Read Consistency
Parallel Processing
When executing the planning run, the above steps are carried out by one or more of the
following seven processes:
Memory-based snapshot. This is the main Snapshot process. It is launched by the

Launch Planning Process form. It's primary task is to prepare the list of planned
items and perform the pre- and post-processing steps. Once it performs these steps,
the memory-based snapshot behaves like a Snapshot Worker.
Snapshot monitor. This controls the rest of the planning process. It is launched by
the memory-based snapshot and it in turn launches the snapshot workers, delete
workers, loader workers, and the memory-based planner. The number of delete
worker launched by the snapshot monitor is determined by the MRP:Snapshot
Workers profile option. It launches the Delete Workers after it prepares the list of
delete tasks (see Figure 45). The snapshot monitor also maintains a list of snapshot
tasks and delete tasks and the current status of each task. It uses this list to provide
the next snapshot task to the memory-based snapshot and snapshot workers. It uses
the status of the delete tasks to determine if the flat files created by the
memory-based snapshot and snapshot workers can be loaded into the database by
the loader workers. The snapshot monitor is also responsible for ensuring the read
consistency of the data captured by the memory-based snapshot and the snapshot
workers.
Snapshot workers. The number of these workers launched by the snapshot monitor
is based on the MRP:Snapshot Workers profile; setting the number to one makes the
Snapshot run as a single-threaded process. The snapshot workers collect data on
bills of material, work in process, on-hand quantities, purchasing, firm planned
orders, routings and work in process job resource requirements. The snapshot
monitor controls the snapshot workers and receives instructions on which tasks to
perform next. The snapshot worker places the data into flat files and communicates
the completion of the task and the file name to the snapshot monitor.
Snapshot delete workers. These workers are launched by the snapshot monitor and
delete the planning data from the last planning run. Each worker reads
MRP_SNAPSHOT_TASKS to get the next delete task. After it completes the delete,
it updates the completion date in MRP_SNAPSHOT_TASKS.
Loader workers. The snapshot monitor launches one loader worker for each table
requiring a load. The snapshot monitor launches the loader worker after the flat file
for the snapshot data has been written and the last planning run data has been
deleted. The loader worker uses SQL*Loader to load the data. The profile option
MRP:Use Direct Load Option controls whether SQL*Loader uses direct loading or
conventional loading methods.
Warning: If you use Direct Load, the database grows, potentially
leading to increased storage space. One way to counter this side

effect is to export and reimport the tables affected by the planning
processes.
Memory-based planner. The memory-based planner performs the gross-to-net

explosion. Launched by the Snapshot Monitor or separately by the user, the
memory-based planner loads the snapshot flat files into memory, nets the supply
and demand for planned items and writes the output to flat files. These flat files are
loaded into the database by loader workers.
Planner delete worker. This worker is launched by the memory-based planner. It

runs only when the memory-based planner is run without the snapshot. It is
responsible for deleting data from planner output tables, including
MRP_RECOMMENDATIONS, MRP_GROSS_REQUIREMENTS, and
MRP_FULL_PEGGING.
Figure 7-44 illustrates the Snapshot Monitor Process logic under the Memory-based
Planning Engine. Below is a detailed explanation of the logic.
1.
Launch X Snapshot Workers via the Concurrent Manager, where X is the number of
Snapshot Workers to launch, as defined by the profile option MRP:Snapshot
Workers.
2.
Begin Snapshot Preprocessing. These tasks include calculating repetitive planning

periods for all the planned organizations, and relieving the MPS.
3.
List the items that the planning engine will include in the current run. The
plan-level option Included Items determines this list.
4.
The Snapshot Monitor launches Snapshot Delete Workers to clean old snapshot and
planning output from the tables.
5.
Snapshot Workers select data from system tables, including work in process,
inventory, purchasing, and bill of materials and write the data to flat files. Since the
data is written to flat files, the deletes are not a prerequisite for this step.
6.
Loader Workers load the flat files from step 5 into the MRP snapshot tables.
7.
Once the workers complete the list of items for planning, lock the tables if Snapshot
Lock Tables is set to Yes, then ask the Snapshot and Snapshot Workers to set
transaction to read-only.
8.
Loop until the workers complete.
9.
Snapshot post-processing begins, which consists of cleanup activities and the

execution of user-defined Snapshot Tasks.
After these steps, the Memory-based Planner performs the gross-to-net explosion and
creates new supply orders.
If the user ran the Memory-based Planner without the Snapshot, the Memory-based
Planning Engine launches Planner Delete Workers, which delete data from the planner
output tables.
See Also
Snapshot Tasks
Read Consistency
Parallel Processing
Snapshot Tasks
Once MRP_SYSTEM_ITEMS is loaded, then all other tasks can proceed. Each of the
following tasks is responsible for creating a set of files that correspond to the database
tables:
Capacity information: loads job resource requirements and capacity resource

information
Delete: deletes data from relevant MRP tables which belongs to the previous plan
Demand information: loads independent gross requirements and material

reservations
Inventory information: loads information regarding inventory lots
Item information: loads inventory items, primary suppliers, item categories, item
classifications, quantity on hand and cost information
MPS orders information: loads MPS planned orders
MRP orders information: loads MRP firmed planned orders
Purchasing information: retrieves supply information regarding purchase orders,

purchase requisitions, intransit shipments, intransit receipts and purchase orders in
receiving from the database
Safety stock: loads time-phased safety stock information
Substitute items information: loads substitute items
WIP and BOM component information: loads BOM structures, pending ECOs,
component requirements from discrete jobs, flow schedules, repetitive schedules,
and non-standard jobs; calculates low level codes and checks loops introduced by
both WIP components and BOMs
WIP information: loads discrete jobs, flow schedules, non-standard jobs, repetitive
schedules and calculates aggregate repetitive schedules
When a given file is complete, each tasks submits a request to the Snapshot Monitor.
The Snapshot Monitor then checks the dependency and begins loading the file, for use
by the Memory-based Planner.
See Also
Processing Steps
Processes
Read Consistency
Read Consistency
Certain tasks require a database lock in order to guarantee a consistent read. For
example, discrete job information and inventory quantities require a lock on the
inventory transactions table in order to guarantee a consistent read. Consider the
situation where you have a subinventory with a quantity of 100 units, and a discrete job
for 25 units. Between the time the Snapshot reads the inventory information and the
time the Snapshot reads the discrete job information, 10 units are completed from the
job. The Snapshot needs to guarantee that it populates the MRP tables with inventory of
100 and discrete job quantity of 25, or inventory for 110 and discrete job quantity of 15.
Because each task may be processed by independent processes, the Snapshot cannot
guarantee that both tasks are executed at the same time. Therefore, by locking the
inventory transactions table, the Snapshot guarantees a consistent read.
One of the advantages of the Memory-based Planning Engine is its ability to get a
consistent image of all planning data without locking users out of the system. The planning
engine accomplishes this with the ORACLE RDBMS feature called "set transaction
read-only". With this option, you do not need to lock tables for the duration of the
planning run. The Memory-based Snapshot and Snapshot Workers capture all supply
and demand data as it existed after a snapshot of the item list has been taken. All
changes made to the data after that are not included.
The advantage in using the read-only option is that you do not need exclusive table
locks, which lock users out of the table for the entire duration of the Snapshot. Instead,
you simply co-ordinate the snapshots performed by the Memory-based Snapshot and
Snapshot Workers. Since the collection of data is performed by multiple processes, the
"set transaction read-only" feature has to be executed at the same time by the
Memory-based Snapshot and Snapshot Workers.
You can achieve two degrees of read consistency under the Memory-based Planning
Engine. Set the Snapshot Lock Tables field (Plan Options window) to Yes. This forces
the Snapshot Workers and the Memory-based Snapshot to execute the set transaction
feature simultaneously. It also ensures that no transactions are performed while the
snapshot processes are trying to set the transactions to read-only. To ensure this, the
Snapshot Monitor gains an exclusive lock on the tables and instructions the
Memory-based Snapshot and Snapshot Workers to execute the set transaction feature.
As soon as the Snapshot Monitor receives confirmation from the snapshot processes the
set transaction feature is complete, it releases the lock. In this way, you get a
read-consistent snapshot with little time spent locking users out of the system.
Locking tables gives you the highest degree of data consistency, but you cannot
perform any transactions while this lock is on. If you set the Snapshot Lock Tables field
to No, the Snapshot Workers and the Memory-based Snapshot may execute the set
transaction feature at different times. There is a remote possibility of some
inconsistencies with this method.
See Also
Processing Steps
Processes
Snapshot Tasks
Parallel Processing
Oracle MRP breaks tasks into smaller tasks that are executed concurrently by
independent processes (workers). The programs that execute these tasks concurrently
need to communicate in order to coordinate their actions.
InterProcess Communication
The Memory-based Planning Engine uses a combination of database pipes and database
tables for inter-process communication. The Memory-based Snapshot and Snapshot
Workers communicate with the Snapshot Monitor via database pipes. These pipes carry
messages that include requests for new tasks, task completion, and initiate the set
transaction read-only RDBMS feature. The Snapshot Delete Workers communicate via
the database table MRP_SNAPSHOT_TASKS. See also: Interprocess Communication
See Also
Processing Steps
Processes
Snapshot Tasks
Read Consistency
Configuring the Memory-based Planning
Engine Parallel Processing
Configuring the Memorybased Planning Engine

To configure the memory-based planning engine:
Set profile options
Define a number of target processes
Profile options
In addition to MRP:Snapshot Workers, you can define the following profile options to
improve Memory-based Planning Engine performance:
MRP:Environment variable to set path for MRP files
MRP:Snapshot Pause for Lock (Minutes)
MRP:Snapshot Workers
MRP:Use Direct Load Option
See: Profile Options

Warning: If you use Direct Load, the database grows, potentially
leading to increased storage space. One way to counter this side effect
is to export and reimport the tables affected by the planning processes.
Setting up
To run the Memory-based Planning Engine, you must define a number of target
processes in the concurrent processes in the concurrent manager. Use the following the
formula to determine the number you require:
T=4+2S
where
T = the number of target processes required to run the Memory-based Planning Engine
S = the number of snapshot defined in MRP:Snapshot Workers
See: Managing Concurrent Programs and Requests, Oracle Applications User's Guide
See Also
Processing Steps
Processes
Snapshot Tasks
Read Consistency
H
Character Mode Forms and GUI Windows
Character Mode Forms and Corresponding GUI Windows

This appendix describes character mode forms with their corresponding GUI windows
or processes.
The following table matches character mode forms with their corresponding GUI
windows or processes. This information supplements Windows and Navigator Paths in
the product online documentation. Text in brackets ([ ]) indicates a button.
Character Mode Form and Menu
Path
GUI Window or Process, and Navigation Path
Change Organization
Change Organization
\Navigate Other ChangeOrg
Navigator: Other > Change Organization
\Navigate Forecast Consume
Navigator: Forecast > Consume Set

or
Navigator: Forecast > Items [Consume]
or
Navigator: Forecast > Sets [Consume]
Define Audit SQL Statement

\Navigate Setup Audit
Use the System Administrator responsibility and See:

System Administration Character Mode Forms and
Corresponding GUI Windows.
Character Mode Forms and GUI Windows H-1

Path
Define Demand Classes
DEMAND_CLASS QuickCodes
\Navigate Setup QuickCodes

DemandClasses
Navigator: Setup > Demand Class
Define Forecast Sets
Forecast Sets
\Navigate Forecast Define
Navigator: Forecast > Sets
Define Key Flexfield Security Rule

\Navigate Setup Flexfields Key

Security Define
Define Key Flexfield Segments
Segments
Define Key Segment Values

\Navigate Setup Flexfields Key Values

Define Master Schedule Name
Master Demand Schedules
\Navigate Schedule Define
Navigator: MDS > Names

or
Master Production Schedules
Navigator: MPS > Names
H-2 Oracle MRP User's Guide

Path
Define Planner Workbench Criteria Set
Folder Menu
or
Navigator: Inquiry > MRP > Workbench > Demand >
[Folder Menu]
or
Navigator: Inquiry > MRP > Workbench > Items >
[Folder Menu]
or
Navigator: Inquiry > MRP > Workbench > Supply >
[Folder Menu]
or
Navigator: Inquiry > MRP > Workbench >
Supply/Demand > [Folder Menu]
Define Planning Exception Sets
\Navigate Setup ExceptionSet
Navigator: Setup > Exception Set
Define Planning Parameters
Planning Parameters
\Navigate Setup Parameters
Navigator: Setup > Parameters
Define Rollup Groups


Groups
Define Security Rule
\Navigate Setup Flexfields Validation
Security Define
Define Segment Values
Values
Define Shorthand Aliases
\Navigate Setup Flexfields Key Aliases




Path
Define Value Set


Sets
Enter Employees
\Navigate Setup Employee

Enter Forecast Entries
\Navigate Forecast Enter
Navigator: Forecast > Entries
Define MRP Names
MRP Names
\Navigate Plan Define
Navigator: MRP > Names
Enter Master Schedule Entries
Item Master Demand Schedule Entries
\Navigate Schedule Enter
Navigator: MDS > Entries

or
Item Master Production Schedule Entries
Navigator: MPS > Entries

Path
Launch Planning Process
Launch MPS
\Navigate Plan Plan
Navigator: MPS > Launch

or
Navigator: MPS > Names > [Launch]
or
Launch MRP
Navigator: MRP > Launch
or
Navigator: MRP > Names > [Launch]
or
Plan Options
Navigator: MPS > Names > [Options]
or
Navigator: MPS > Options
or
Navigator: MRP > Names > [Options]
or
Navigator: MRP > Options
or
Plan Status
Navigator: MPS > Workbench > [Status]
or
Navigator: Inquiry > MPS > Status
or
Navigator: MRP > Workbench > [Status]
or
Navigator: Inquiry > MRP > Status
or

Path
Planner Tasks
Navigator: MPS > Workbench > [Status] > [Planner
Tasks]
or
Navigator: Inquiry > MPS > Status > [Planner Tasks]
or
Navigator: MRP > Workbench > [Status] > [Planner
Tasks]
or
Navigator: Inquiry > MRP > Status > [Planner Tasks]
or
Snapshot Tasks
Navigator: MPS > Workbench > Status > [Snapshot
Tasks]
or
Navigator: Inquiry > MPS > View Plan > Status >
[Snapshot Tasks]
or
Navigator: MRP > Workbench > Status > [Snapshot
Tasks]
or
Navigator: Inquiry > MRP > View Plan > Status >
[Snapshot Tasks]

Path
Load Forecast
Copy/Merge Forecast
\Navigate Forecast Load
Navigator: Forecast > Copy

or
Navigator: Forecast > Items > [Copy/Merge Forecast]
Navigator: Forecast > Sets > [Copy/Merge Forecast]
or
Forecast Source List
Navigator: Forecast > Source List
or
Generate Forecast
Navigator: Forecast > Generate

Path
Load Master Schedule
Load/Copy/Merge Master Demand Schedule
\Navigate Schedule Load
Navigator: MDS > Load/Copy/Merge

or
Navigator: MDS > Items > [Load/Copy/Merge]
or
Navigator: MDS > Names > [Load/Copy/Merge]
or
Load/Copy/Merge Master Production Schedule
Navigator: MPS > Load/Copy/Merge MPS
or
Navigator: MPS > Items > [Load/Copy/Merge MPS]
or
Navigator: MPS > Names > [Load/Copy/Merge MPS]
or
Master Demand Schedule Source List
Navigator: MDS > Source List
or
Master Production Schedule Source List
Navigator: MPS > Source List

Path
Planner Workbench
MPS Planner Workbench
\Navigate Plan Workbench
Navigator: MPS > Workbench

or
Navigator: Inquiry > MPS > Workbench
or
MRP Planner Workbench
Navigator: MRP > Workbench
or
Navigator: Inquiry > MRP > Workbench
or
Supply/Demand
Navigator: MPS > Workbench > [Demand]
or
Navigator: MPS > Workbench > [Supply]
or
Navigator: MPS > Workbench > [Supply/Demand]
or
Navigator: MPS > Workbench > [Items] > [Demand]
or
Navigator: MPS > Workbench > [Items] > [Supply]
or
Navigator: MPS > Workbench > [Items] >
[Supply/Demand]

Path
or
Navigator: MRP > Workbench > [Demand]
or
Navigator: MRP > Workbench > [Supply]
or
Navigator: MRP > Workbench > [Supply/Demand]
or
Navigator: MRP > Workbench > [Items] > [Demand]
or
Navigator: MRP > Workbench > [Items] > [Supply]
or
Navigator: MRP > Workbench > [Items] >
[Supply/Demand]
Run Reports
Submit Request window
\Navigate Reports
See: Submit Requests (Oracle Applications User's

Guide)
Navigator: Reports > Run
Start Planning Manager
Planning Manager
\Navigate Setup PlanningManager
Navigator: Setup > Planning Manager
Update Personal Profile Options
Personal Profile Values
\Navigate Other Profile
Navigator: Other > Profile

Path
View Bucketed Request
Forecast Bucketed Entries
\Navigate Inquiry Forecast Bucketed
Navigator: Forecast > Entries > [Bucketed]

or
Navigator: Forecast > Items > [Bucketed]
or
Navigator: Forecast > Sets > [Forecast Items] >
[Bucketed]
or
Navigator: Forecast > Sets > [Forecast Set Items] >
[Bucketed]
or
Navigator: Inquiry > Forecast > View Entries >
[Bucketed]
or
Navigator: Inquiry > Forecast > View Items >
[Bucketed]
or
Navigator: Inquiry > Forecast > View Sets > [Forecast
Items] > [Bucketed]
or
Set Items] > [Bucketed]

Path
View Bucketed Master Schedule
Master Demand Schedule Bucketed Entries
\Navigate Inquiry Schedule Bucketed
Navigator: MDS > Entries > [Bucketed]

or
Navigator: MDS > Items > [Bucketed]
or
Navigator: MDS > View Items > [Bucketed]
or
Navigator: MDS > View Entries > [Bucketed]
or
Master Production Schedule Bucketed Entries
Navigator: MPS > Entries > [Bucketed]
Navigator: MPS > Items > [Bucketed]
or
Navigator: Inquiry > MPS > View Entries > [Bucketed]
or
Navigator: Inquiry > MPS > View Items > [Bucketed]
View Concurrent Requests
Requests window
\ Navigate Other Request
See: Viewing Requests (Oracle Applications User's

Guide)
Navigator: Concurrent > Requests
Choose:
View Output button - to view Request Output View
Log button - to view Request Log
Use the Menu to choose:
Special > Managers - to view Manager Log

Path
View Forecast Entries
Forecast Consumptions
\Navigate Inquiry Forecast Detail
Navigator: Forecast > Entries > [Consumptions]

or
Navigator: Forecast > Items > [Bucketed] > [Detail] >
[Consumptions]
or
Navigator: Forecast > Items > [Detail] >
[Consumptions]
or
[Bucketed] > [Detail] > [Consumptions]
or
or
Navigator: Forecast > Sets > [Forecast Items] > [Detail]
> [Consumptions]
or
or
Navigator: Inquiry > Forecast > View Entries >
[Consumptions]
or
Navigator: Inquiry > Forecast > View Items >
or
Navigator: Inquiry > Forecast > View Items > [Detail]
> [Consumptions]
or

Path
Items] > [Detail] > [Consumptions] or Navigator:

Inquiry > Forecast > View Sets > [Forecast Set Items] >
or
Navigator: Inquiry > View Sets > [Forecast Items] >
or
Navigator: Inquiry > View Sets > [Forecast Set Items]
> [Bucketed] > [Detail] > [Consumptions]
or
Forecast Entries
Navigator: Forecast > Items > [Bucketed] > [Detail]
or
Navigator: Forecast > Items > [Detail]
or
[Bucketed] > [Detail]
or
[Bucketed] > [Detail]
or
Navigator: Forecast > Sets > [Forecast Items] > [Detail]
[Detail]
or
Forecast Items
Navigator: Forecast > Sets > [Forecast Items]
or
Navigator: Forecast > Sets > [Forecast Set Items]
or

Path
Navigator: Inquiry > Forecast > View Items

or
Items]
or
Set Items]
or
Navigator: Forecast > Items
or
Navigator: Inquiry > Forecast > View Entries

Path
View Item Planning Information
Components
\Navigate Inquiry Plan Item

[Components]
or
[Components]
or
End Assemblies
Navigator: MPS > Workbench > [Items] > [End
Assemblies]
or
Navigator: MRP > Workbench > [Items] > [End
Assemblies]
or
Horizontal Plan
Navigator: MPS > Workbench > [Demand] >
[Horizontal Plan]
or
Navigator: MPS > Workbench > [Items] > [Horizontal
Plan]
or
Navigator: MPS > Workbench > [Supply/Demand] >
[Horizontal Plan]
or
Navigator: MPS > Workbench > [Supply] >
[Horizontal Plan]
or
Navigator: MRP > Workbench > [Demand] >
[Horizontal Plan]
or
Navigator: MRP > Workbench > [Items] > [Horizontal

Path
Plan]
or
Navigator: MRP > Workbench > [Supply/Demand] >
[Horizontal Plan]
or
Navigator: MRP > Workbench > [Supply] >
[Horizontal Plan]
or
Items
Navigator: MPS > Workbench > [Items]
or
Navigator: MRP > Workbench > [Items]
or
Where Used
Navigator: MPS > Workbench > [Items] > [Where
Used]
or
Navigator: MRP > Workbench > [Items] > [Where
Used]

Path
View Master Schedule Entries
Master Demand Schedule Entries
\Navigate Inquire Schedule Detail
Navigator: Inquiry > MDS > View Entries

or
Navigator: Inquiry > MDS > View Items > [Detail]
or
Navigator: Inquiry > MDS > View Items > [Bucketed]
> [Detail]
or
Master Demand Schedule Items
Navigator: Inquiry > MDS > View Items
or
Master Demand Schedule Reliefs
Navigator: MDS > Items > [Bucketed] > [Detail] >
[Reliefs]
or
Navigator: MDS > Items > [Detail] > [Reliefs]
or
Master Production Schedule Entries
Navigator: Inquiry> MDS > View Entries > [Reliefs]
or
Navigator: Inquiry> MDS > View Items > [Bucketed] >
[Detail] > [Reliefs]
or
Navigator: Inquiry> MDS > View Items > [Detail] >
[Reliefs]
or
Navigator: MDS > Entries > [Reliefs]
or
Navigator: Inquiry > MPS > View Entries

Path
or
Navigator: Inquiry > MPS > View Items > [Detail]
or
> [Detail]
or
Master Production Schedule Items
Navigator: Inquiry > MPS > View Items
or
Master Production Schedule Reliefs
Navigator: MPS > Entries > [Reliefs]
or
Navigator: MPS > Items > [Bucketed] > [Detail] >
[Reliefs]
or
Navigator: MPS > Items > [Detail] > [Reliefs]
or
Navigator: Inquiry > MPS > View Entries > [Reliefs]
or
> [Detail] > [Reliefs]
or
Navigator: Inquiry > MPS > View Items > [Detail] >
[Reliefs]

Path
View Orders
Supply/Demand
\Navigate Inquiry Plan Orders
Navigator: MPS > Workbench > [Demand]

or
Navigator: MPS > Workbench > [Supply]
or
Navigator: MPS > Workbench > [Supply/Demand]
or
Navigator: MPS > Workbench > [Items] > [Exceptions]
[Supply]
or
Navigator: MPS > Workbench > [Items] > [Demand]
or
Navigator: MPS > Workbench > [Items] > [Supply]
or
[Supply/Demand]
or
Navigator: MRP > Workbench > [Demand]
or
Navigator: MRP > Workbench > [Supply]
or
Navigator: MRP > Workbench > [Supply/Demand]
or
Navigator: MRP > Workbench > [Items] > [Demand]
or
Navigator: MRP > Workbench > [Items] > [Supply]
or
[Supply/Demand]

Path
View Planning Exceptions
Exceptions
\Navigate Inquiry Plan Exceptions
Navigator: MPS > Workbench > [Exceptions]

or
Navigator: MRP > Workbench > [Exceptions]
View Reports
Requests window
\Navigate Report View
See: Viewing Requests (Oracle Applications User's

Guide)
Navigator: Concurrent > Requests
Choose:
View Output button - to view Request Output
View Log button - to view Request Log
View Vendor Schedule

\Navigate Inquiry Plan Vendor
View Workdates
\Navigate Inquiry WorkDates

Glossary
Acceptable Early Days
An item attribute the planning process uses to decide when to suggest rescheduling
orders for the item to an earlier date. The planning process only suggests rescheduling
orders for the item if the order is due to be received into inventory before the acceptable
early date. This attribute is used when it is more economical to build and carry excess
inventory for a short time than it is to reschedule the order. This attribute applies to
discretely planned items only. The attribute for repetitively planned items is Overrun
Percentage
Acceptable Rate Decrease
An item attribute the planning process uses to decide how much to decrease current
daily rates for the item inside the planning time fence. The planning process does not
suggest a new daily rate less than the current daily rate minus the acceptable rate
decrease amount. If you do not define a value for this attribute, the planning process
assumes that there is no lower limit to the new daily rate it can suggest for the item
inside the planning time fence. If you set this attribute to zero, the planning process
assumes it cannot suggest any rate less than the current daily rate inside the planning
time fence. Inventory defaults the value of this attribute to zero. This attribute lets you
minimize short term disruption to shop floor schedules by restricting short term rate
change suggestions. This attribute applies to repetitively planned items only.
Acceptable Rate Increase
An item attribute the planning process uses to decide how much to increase current
daily rates for the item inside the planning time fence. The planning process does not
suggest a new daily rate that is greater than the current daily rate plus the acceptable
rate increase amount. If you do not define a value for this attribute, the planning
process assumes there is no upper limit to the new daily rate that it can suggest for the
item inside the planning time fence. If you set this attribute to zero, the planning
process assumes it cannot suggest any rate greater than the current daily rate inside the
planning time fence. Inventory defaults the value of this attribute to zero. This attribute
lets you minimize short term disruption to shop floor schedules by restricting short
term rate change suggestions and applies to repetitively planned items only.
Glossary-1
accounting period
The fiscal period a company uses to report financial results, such as a calendar month or
fiscal period.
action message
Output of the MRP process that identifies a type of action to be taken to correct a
current or potential material coverage problem.
action result
A possible outcome of an order cycle action. You can assign any number of results to a
cycle action. Combinations of actions/results are used as order cycle action
prerequisites. See also order cycle, cycle action.
actual demand
The demand from actual sales orders, not including forecasted demand.
aggregate repetitive schedule
The sum of detail schedules for an item across all work in process manufacturing lines
in terms of a daily rate, and a start and end date.
aggregate resources
The summation of all requirements of multi-department resources across all
departments that use it.
anchor date
The start date of the first repetitive planning period. It introduces consistency into the
material plan by stabilizing the repetitive periods as time passes so that a plan run on
any of the days during the first planning period does not change daily demand rates.
append option
Option or choice to append planned orders to an MRP plan or an MPS plan during the
planning process. Append either after the last existing planned order, after the planning
time fence, or for the entire plan. The append option is used with the overwrite option.
See overwrite option
application building block
A set of tables and modules (forms, reports, and concurrent programs) that implement
closely-related entities and their processing.
assemble-to-order (ATO)
An environment where you open a final assembly order to assemble items that
customers order. Assemble-to-order is also an item attribute that you can apply to
Glossary-2
standard, model, and option class items.

assignment hierarchy
You can assign sourcing rules and bills of distribution to a single item in an inventory
organization, all items in an inventory organization, categories of items in an inventory
organization, a site, and an organization. These assignments have an order of
precedence relative to one another.
assignment set
A group of sourcing rules and/or bills of distribution and a description of the items
and/or organizations whose replenishment they control.
automatic rescheduling
Rescheduling done by the planning process to automatically change due dates on
scheduled receipts when it detects that due dates and need dates are inconsistent.
available capacity
The amount of capacity available for a resource or production line.
available-to-promise (ATP)
Ability to promise product for customer orders based on uncommitted inventory,
planned production, and material.
backward consumption days
A number of days backwards from the current date used for consuming and loading
forecasts. Consumption of a forecast occurs in the current bucket and as far back as the
backward consumption days. If the backward consumption days enters another bucket,
the forecast also consumes anywhere in that bucket. When loading a forecast, only
forecasts of the current date minus the backward consumption days are loaded.
Therefore, you can use backward consumption days to load forecasts that are past due.
base model
The model item from which a configuration item was created.
bill of distribution
Specifies a multilevel replenishment network of warehouses, distribution centers, and
manufacturing centers (plants).
bill of material
A list of component items associated with a parent item and information about how
each item relates to the parent item. Oracle Manufacturing supports standard, model,
option class, and planning bills. The item information on a bill depends on the item type
and bill type. The most common type of bill is a standard bill of material. A standard
Glossary-3
bill of material lists the components associated with a product or subassembly. It

specifies the required quantity for each component plus other information to control
work in process, material planning, and other Oracle Manufacturing functions. Also
known as product structures.
bill of resource set
A group of bills of resources. A bill of resource set can have one or many bills of
resources within it.
bill of resources
A list of each resource and/or production line required to build an assembly, model, or
option.
bill-to address
The customer's billing address. It is also known as invoice-to address. It is used as a
level of detail when defining a forecast. If a forecast has a bill-to address associated with
it, a sales order only consumes that forecast if the bill-to address is the same.
bucket days
The number of workdays within a repetitive planning period.
by-product
Material produced as a residual of a production process. Represented by negative usage
in the bill of material for an assembly.
Calculate ATP
An item attribute the planning process uses to decide when to calculate and print
available to promise (ATP) for the item on the Planning Detail Report. The planning
process calculates ATP using the following formula: ATP = Planned production committed demand.
capable to deliver
planned production, material, capacity, transportation resources, and transit time.
capable to promise
planned production, material, and the capacity of resources.
capacity modification
Deviation to available resources for a specific department shift.
Glossary-4
capacity requirements planning

A time-phased plan comparing required capacity to available capacity, based on a
material requirements plan and department/resource information.
See routing-based capacity and rate-based capacity
carry forward days
A number of days shifted forward (or backward when using a negative number) when
copying a forecast into another forecast or a master schedule into another master
schedule. The load process shifts any entries on the source forecast (or schedule) onto
the destination forecast (or schedule) forward or backward by this many days.
chase production strategy
A production strategy that varies production levels to match changes in demand. This
production strategy results in minimal inventory carrying costs at the expense of
fluctuating capacity requirements.
component demand
Demand passed down from a parent assembly to a component.
component item
An item associated with a parent item on a bill of material.
component yield
The percent of the amount of a component you want to issue to build an assembly that
actually becomes part of that assembly. Or, the amount of a component you require to
build plus the amount of the component you lose or waste while building an assembly.
For example, a yield factor of 0.90 means that only 90% of the usage quantity of the
component on a bill actually becomes part of the finished assembly.
compression days
The number of days the planning process suggests you compress the order (in other
words, reduce the time between the start date and the due date).
concurrent manager
Components of your applications concurrent processing facility that monitor and run
time-consuming tasks for you without tying up your terminal. Whenever you submit a
request, such as running a report, a concurrent manager does the work for you, letting
you perform many tasks simultaneously.
confidence percent
The degree of confidence in a forecast that the forecasted item becomes actual demand.
Glossary-5
When loading schedules from a forecast, the confidence percent is multiplied by the
forecast quantity to determine the schedule quantity
configuration item
The item that corresponds to a base model and a specific list of options. Bills of Material
creates a configuration item for assemble-to-order models.
CRP planner
A process that may optionally be run as part of the planning process. The CRP planner
calculates capacity requirements for resources and production lines using the material
requirements calculated by the planning process.
current aggregate repetitive schedule
The sum of all current work in process repetitive schedules for an item for all lines for a
given period in terms of a daily rate, and a start and end date. Current aggregate
repetitive schedules can be firm or partially firm. If all current repetitive schedules for
an item are firm, then the current aggregate repetitive schedule for the item is also firm.
If some, but not all the current repetitive schedules for an item are firm, then the current
repetitive schedule is partially firm.
current date
The present system date.
cutoff date
An indication of the last date to be included in a plan or horizon.
daily rate
The number of completed assemblies a repetitive schedule plans to produce per day.
Also known as production rate. See repetitive rate
database diagram
A graphic representation of application tables and the relationships among them.
deliver-to location
A location where you deliver goods previously received from a supplier to individual
requestors.
demand class
A classification of demand to allow the master scheduler to track and consume different
types of demand. A demand class may represent a particular grouping of customers,
such as government and commercial customers. Demand classes may also represent
different sources of demand, such as retail, mail order, and wholesale.
Glossary-6
demand management
The function of recognizing and managing all demands for products, to ensure the
master scheduler is aware of them. This encompasses forecasting, order management,
order promising (available to promise), branch warehouse requirements, and other
sources of demand.
Demand Time Fence
Item attribute used to determine a future time inside which the planning process
ignores forecast demand and only considers sales order demand when calculating gross
requirements for an item. Use this attribute to identify a time fence inside which you
wish to build to sales order demand only to reduce the risk of carrying excess
inventory. A value of Cumulative manufacturing lead time means MRP calculates the
demand time fence for the item as the plan date (or the next workday if the plan is
generated on a non workday) plus the cumulative manufacturing lead time for the item.
A value of Cumulative total lead time means MRP calculates the demand time fence for
the item as the plan date (or the next workday if the plan is generated on a non
workday) plus the total manufacturing lead time for the item. A value of Total lead time
means MRP calculates the demand time fence for the item as the plan date (or the next
workday if the plan is generated on a non workday) plus the total lead time for the
item. A value of User-defined time fence means MRP calculates the demand time fence
for the item as the plan date (or the next workday if the plan is generated on a non
workday) plus the value you enter for Planning Time Fence Days for the item.
Demand Time Fence Days
Item attribute used when you set the Planning Time Fence attribute to User-defined
time fence. MRP calculates the demand time fence for the item as the plan date (or the
next workday if the plan is generated on a non workday) plus the value you enter here.
department
An area within your organization that consists of one or more people, machines, or
suppliers. You can also assign and update resources to a department.
dependent demand
Demand for an item that is directly related to or derived from the demand for other
items.
destination forecast
The forecast you load into when copying a forecast into another forecast.
disable date
A date when an Oracle Manufacturing function is no longer available for use. For
example, this could be the date on which a bill of material component or routing
operation is no longer active, or the date a forecast or master schedule is no longer
Glossary-7
valid.
discrete job
A production order for the manufacture of a specific (discrete) quantity of an assembly,
using specific materials and resources, in a limited time. A discrete job collects the costs
of production and allows you to report those costs including variances by job. Also
known as work order or assembly order.
distribution resource planning (DRP)
Application of replenishment inventory calculations to assist in planning of key
resources contained in a distribution system, such as sourcing and transport. DRP is an
extension of distribution requirements planning, which applies MRP logic to inventory
replenishment at branch warehouses
dock date
The date you expect to receive a purchase order.
DRP
See distribution resource planning
due date
The date when scheduled receipts are currently expected to be received into inventory
and become available for use.
effective date
Date when an Oracle Manufacturing function is available for use. For example, this
could be the date a bill of material component or routing operation becomes effective,
or the date you anticipate revised item changes become part of a bill of material and can
no longer be controlled by an ECO.
end assembly pegging
A Pegging item attribute option the planning process uses to decide when to calculate
and print end assemblies for the item on the Planning Detail Report. Even if you do not
select this option, you can still calculate and view end assemblies for the item on-line.
end date
Signifies the last date a particular quantity should be forecast on a forecast entry. From
the forecast date until the end date, the same quantity is forecast for each day, week or
period that falls between that time frame. An entry without an end date is scheduled for
the forecast date only.
end item
Any item that can be ordered or sold. See finished good and product
Glossary-8
engineering change order (ECO)

A record of revisions to one or more items usually released by engineering.
engineering item
A prototype part, material, subassembly, assembly, or product you have not yet
released to production. You can order, stock, and build engineering items.
entity
A data object that holds information for an application.
exception message
A message received indicating a situation that meets your predefined exception set for
an item, such as Items that are overcommitted, Items with excess inventory, and Orders
to be rescheduled out.
finished good
Any item subject to a customer order or forecast. See also product
firm planned order
An MRP-planned order that is firmed using the Planner Workbench. This allows the
planner to firm portions of the material plan without creating discrete jobs or purchase
requisitions. Unlike a firm order, a MRP firm planned order does not create a natural
time fence for an item.
firm scheduled receipt
A replenishment order that is not modified by any planning process. It may be a
purchase order, discrete job, or repetitive schedule. An order is firm planned so that the
planner can control the material requirements plan.
Fixed Days Supply
An item attribute the planning process uses to modify the size and timing of planned
order quantities for the item. The planning process suggests planned order quantities
that cover net requirements for the period defined by the value you enter here. The
planning process suggests one planned order for each period. Use this attribute, for
example, to reduce the number of planned orders the planning process would
otherwise generate for a discretely planned component of a repetitively planned item.
Fixed Lot Size Multiplier
An item attribute the planning process uses to modify the size of planned order
quantities or repetitive daily rates for the item. For discretely planned items, when net
requirements fall short of the fixed lot size multiplier quantity, the planning process
suggests a single order for the fixed lot size multiplier quantity. When net requirements
Glossary-9
for the item exceed the fixed lot size multiplier quantity, the planning process suggests
a single order with an order quantity that is a multiple of the fixed lot size multiplier
quantity. For repetitively planned items, when average daily demand for a repetitive
planning period falls short of the fixed lot size multiplier quantity, the planning process
suggests a repetitive daily rate equal to the fixed lot size multiplier quantity. When
average daily demand for a repetitive planning period exceeds the fixed lot size
multiplier quantity, the planning process suggests a repetitive daily rate that is a
multiple of the fixed lot size multiplier quantity.
fixed order quantity
quantities or repetitive daily rates for the item. When net requirements fall short of the
fixed order quantity, the planning process suggests the fixed order quantity. When net
requirements for the item exceed the fixed order quantity, the planning process
suggests multiple orders for the fixed order quantity. For discretely planned items, use
this attribute to define a fixed production or purchasing quantity for the item. For
repetitively planned items, use this attribute to define a fixed production rate for the
item. For example, if your suppliers can only supply the item in full truckload
quantities, enter the full truckload quantity as the fixed order quantity for the item.
flow manufacturing
Manufacturing philosophy utilizing production lines and schedules instead of work
orders to drive production. Mixed models are grouped into families and produced on
lines balanced to the TAKT time.
focus forecasting
A simulation-based forecasting process that looks at past inventory activity patterns to
determine the best simulation for predicting future demand.
forecast
An estimate of future demand on inventory items. A forecast contains information on
the original and current forecast quantities (before and after consumption), the
confidence factor, and any specific customer information. You can assign any number of
inventory items to the forecast and use the same item in multiple forecasts. For each
inventory item you specify any number of forecast entries.
forecast consumption
The process of subtracting demand generated by sales orders from forecasted demand
thereby preventing demand being counted twice in the planning period.
Forecast Control
An item attribute used to determine the types of demand you place for the item. MRP
uses the option you choose here to guide the behavior of the key processes involved in
two-level master scheduling: forecast explosion, forecast consumption, planning,
Glossary-10
production relief, and shipment relief. This attribute is only appropriate for items that
are models, option classes, options, or mandatory components of models and option
classes. A value of Consume means you forecast demand for the item directly, rather
than exploding forecast demand to the item using the forecast explosion process. A
value of Consume and derive means you forecast demand for the item directly, or you
explode forecast demand to the item using the forecast explosion process, or you use a
combination of both methods to forecast demand for the item. A value of None means
you place sales order demand but do not forecast demand for the item.
forecast date
The date for a forecast entry for an item. A forecast for an item has a forecast date and
an associated quantity.
forecast demand
A part of your total demand that comes from forecasts, not actual sales orders.
forecast end date
A forecast end date implies that until that date, the same quantity is scheduled for each
day, week, or period that falls between the forecast date and the end date. A forecast
date with no forecast end date is the quantity for that particular day, week, or period,
depending on the bucket size.
forecast end item
The parent item for components that receive exploded forecasts during forecast
explosion. Used to identify the highest level planning or model item from which
forecasts for a component can be exploded.
forecast entry
A forecast for an inventory item stated by a date, an optional rate end date, and
quantity.
forecast explosion
Explosion of the forecast for planning and model bills of material. The forecasted
demand for the planning or model bill is passed down to create forecasted demand for
its components. You can choose to explode the forecast when loading a forecast.
forecast level
The level at which a forecast is defined. Also, the level at which to consume a forecast.
Example forecast levels include items, customers, customer bill-to, and customer ship to
locations.
forecast load
The process of copying one or more source forecasts into a single destination forecast.
Glossary-11
When copying forecasts, you can choose to overwrite all or a subset of existing entries
in the destination forecast, specify whether to explode the source forecast, and specify
whether to consume the source forecast. You can choose to modify the source forecast
by a modification percent, or roll the source forecast forward or backward by a
specified number of carry forward days. You can also load compiled statistical and
focus forecasts from Inventory, and you can use the forecast interface table to load
forecasts into MRP from external sources.
forecast set
A group of complementing forecasts. For each forecast set, you specify a forecast level,
consumption use, update time fence days, outlier update percents, disable date, default
time bucket and demand class. A forecast set can have one or many forecasts within it.
forward consumption days
A number of days forward from the current date used for consuming and loading
forecasts. Consumption of a forecast occurs in the current bucket and as far forward as
the forward consumption days. If the forward consumption days enters another bucket,
the forecast consumes anywhere in that bucket, as well.
gross requirements
The total of independent and dependent demand for an item before the netting of
on-hand inventory and scheduled receipts.
hard reservation
Sales order demand that you firm by reserving selected inventory for the purposes of
material planning, available to promise calculations, and customer service issues.
independent demand
Demand for an item unrelated to the demand for other items.
internal requisition
See internal sales order, purchase requisition.
internal sales order
A request within your company for goods or services. An internal sales order originates
from an employee or from another process as a requisition, such as inventory or
manufacturing, and becomes an internal sales order when the information is transferred
from Purchasing to Order Management. Also known as internal requisition or purchase
requisition.
kanban
A visual signal to drive material replenishment. A Kanban system delivers material into
production as needed to meet demand.
Glossary-12
lead time line

The production line Bills of Material uses to calculate the processing lead time for a
particular repetitive assembly, since lead times may vary on different production lines.
level production strategy
A production strategy that maintains stable production levels despite changes in
demand. The level production strategy results in minimal fluctuations in capacity
requirements at the expense of additional inventory carrying costs.
line balancing
Organizing work on the production line so that resources can be synchronized to daily
demand.
line priority
The line priority indicates which production line to use to build assemblies. You create
repetitive schedules on the highest priority line first, then, if the line capacity is less than
demand, additional repetitive schedules are created on other lines in decreasing order
of their line priority. For example, if demand is for 1000 units per day on two lines with
a daily capacity of 750, the line with the highest priority is loaded with 750 and the
lower priority line with 250. For lines of equal priority, the load is allocated evenly
across lines.
load factor
The maximum hour rate divided by the production rate for a given repetitive assembly
and production line.
load rate
The required rate multiplied by the load factor for a given production line.
load ratio
Required capacity divided by available capacity.
loader worker
An independent concurrent process in planning engine, launched by the snapshot
monitor, that loads data from operating system files into tables.
low level code
A number that identifies the lowest level in any bill of material that a component
appears. Low level codes are used by the MRP planner to ensure that net requirements
for the component are not calculated until all gross requirements from parent items
have first been calculated.
Glossary-13
Make or Buy
An item attribute the Planner Workbench uses to default an appropriate value for
implementation type when implementing planned orders for the item. A value Make
means the item is usually manufactured. The Planner Workbench defaults the
implementation type for planned orders for the item to Discrete job. The planning
process passes demand down from manufactured items to lower level components. A
value of Buy means the item is usually purchased. The Planner Workbench defaults the
implementation type for planned orders for the item to Purchase requisition. The
planning process does not pass demand down from purchased items to lower level
components.
manual rescheduling
The most common method of rescheduling scheduled receipts. The planning process
provides reschedule messages that identify scheduled receipts that have inconsistent
due dates and need dates. The impact on lower level material and capacity
requirements are analyzed by material planners before any change is made to current
due dates.
master demand schedule
The anticipated ship schedule in terms of rates or discrete quantities, and dates.
master production schedule (MPS)
The anticipated build schedule in terms of rates or discrete quantities, and dates.
master schedule
The name referring to either a master production schedule or a master demand
schedule. See master demand schedule and master production schedule
master schedule load
The process of copying one or more source forecasts, master schedules, or sales orders
into a single destination master schedule. When copying forecasts, you can choose to
include all or a subset of sales orders, specify whether to consider demand time fence,
and specify whether to consume the source forecast during the load. You can also
specify update options to control consumption of the source forecast during the load.
When copying master schedules, you can choose to modify the source master schedule
by a specified number of carry forward days. When loading sales orders, you can
choose to load all or a subset of sales orders, and you can specify whether to consider
the demand time fence during the load. You can use the master schedule interface table
to load master schedules from external sources.
material requirements planning (MRP)
A process that utilizes bill of material information, a master schedule, and current
inventory information to calculate net requirements for materials.
Glossary-14
material scheduling method

During the planning process, the method used to determine when to stage material
used in the production of a discrete job. You can schedule material to arrive on the
order start date or the operation start date where a component is required.
Maximum Order Quantity
requirements exceed the maximum order quantity, the planning process suggests the
maximum order quantity. For repetitively planned items, when average daily demand
for a repetitive planning period exceeds the maximum order quantity, the planning
process suggests the maximum order quantity as the repetitive daily rate. Use this
attribute, for example, to define an order quantity above which you do not have
sufficient capacity to build the item.
maximum rate
The maximum number of completed assemblies a production line can produce per
hour.
memory-based planner
The process in the memory-based planning engine that performs a gross-to-net
explosion. Under the standard planning engine, the planner performs memory-based
planner functions.
memory-based planning engine
A planning engine that drives the planning process. It performs the gross-to-net
explosion in memory and offers a short overall planning run time. It employs a high
degree of concurrency among snapshot tasks, eliminates nonvalue-added operations,
and combines related tasks into a single task. This planning engine consists of only one
phase, the snapshot, in which all planning tasks occur.
memory-based snapshot
Part of the snapshot phase, listing the items for planning and performing selected
snapshot tasks.
minimum firm rate
The aggregate schedule that is partially firm since only some of the detail schedules are
firm within a particular time frame
Minimum Order Quantity
requirements fall short of the minimum order quantity, the planning process suggests
Glossary-15
the minimum order quantity. For repetitively planned items, when average daily
demand for a repetitive planning period falls short of the minimum order quantity, the
planning process suggests the minimum order quantity as the repetitive daily rate. Use
this attribute, for example, to define an order quantity below which it is not profitable
to build the item.
minimum rate
The minimum number of completed assemblies a production line can produce per
hour.
mixed model map
Used to design balanced lines. The projected volume and mix of demand for a group of
products is used to calculate weighted average work content times. These averages are
compared to TAKT time in order to regroup events into balanced operations, and
reallocate resources.
model bill of material
A bill of material for a model item. A model bill lists option classes and options
available when you place an order for the model item.
modification percent
Used to modify the destination master schedule entries or forecast entries you are
loading by a percent of the source entries.
module
A program or procedure that implements one or more business functions, or parts of a
business function in an application. Modules include forms, concurrent programs, and
subroutines.
MPS
See master production schedule.
MPS explosion level
An option for a master demand schedule that lets you limit the explosion through
unnecessary levels during the MPS planning process. Set the explosion level to the
lowest level on the bill of material that an MPS-planned item exists so the planning
process does not need to search through all levels for MPS-planned items.
MPS plan
A set of planned orders and suggestions to release or reschedule existing schedule
receipts for material to satisfy a given master schedule for MPS-planned items or
MRP-planned items that have an MPS-planned component. Stated in discrete quantities
and order dates.
Glossary-16
MPS-planned item
An item controlled by the master scheduler and placed on a master production
schedule. The item is critical in terms of its impact on lower-level components and/or
resources, such as skilled labor, key machines, or dollars. The master scheduler
maintains control for these items.
MRP
See material requirements planning.
MRP plan
A set of planned orders and suggestions to release or reschedule existing schedule
receipts for material to satisfy a given master schedule for dependent demand items.
Stated in discrete quantities and order dates.
MRP Planning Method
An item attribute used to decide when to plan the item. A value of MPS planning
means the item is planned by the MPS planning process. It is an item that you master
schedule and for which you require manual control. Choose this option for items with
independent demand, items that are critical to your business, or items that control
critical resources. A value of MRP planning means the item is planned by the MRP
planning process. Choose this option for non-critical items that do not require manual
control. These are typically dependent demand items. A value of DRP planning means
the item is planned by the DRP planning process. A value of DRP & MRP means the
item is planned by either a DRP planning or MRP planning process. A value of DRP &
MPS means the item is planned by either a DRP planning or MPS planning process. A
value of None means the item is neither MPS-planned or MRP-planned. It does not
require long-term plan planning of material requirements. Choose this option for high
volume and/or low cost items that do not warrant the administrative overhead of
material requirements planning. These are typically dependent demand items.
MRP-planned item
An item planned by MRP during the MRP planning process.
multi-department resource
A resource whose capacity can be shared with other departments.
nervousness
Characteristic exhibited by MRP systems where minor changes to plans at higher bill of
material levels, for example at the master production schedule level, cause significant
changes to plans at lower levels.
net change simulation
Process used to make changes to supply and demand and re-plan them.
Glossary-17
net requirements
Derived demand due to applying total supply (on-hand inventory, scheduled receipts,
and safety stock quantities) against total demand (gross requirements and reservations).
Net requirements, lot sized and offset for lead time, become planned orders. Typically
used for rework, prototype, and disassembly.
option
An optional item component in an option class or model bill of material.
option class
A group of related option items. An option class is orderable only within a model. An
option class can also contain included items.
option class bill of material
A bill of material for an option class item that contains a list of related options.
option item
A non-mandatory item component in an option class or model bill of material.
order date
The date an order for goods or services is entered. See also work order date.
order modifier
An item attribute that controls the size of planned orders suggested by the planning
process to mimic your inventory policies.
organization
A business unit such as a plant, warehouse, division, department, and so on. Order
Management refers to organizations as warehouses on all Order Management windows
and reports.
origination
The source of a forecast entry or master schedule entry. When you load a forecast or
master schedule, the origination traces the source used to load it. The source can be a
forecast, master schedule, sales order, or manual entry.
outlier quantity
The amount of sales order left over after the maximum allowable amount (outlier
update percent) was used to consume a forecast.
outlier update percent
The maximum percent of the original quantity forecast that a single sales order
Glossary-18
consumes. It is used to limit forecast consumption by unusually large sales orders

overload
A condition where required capacity for a resource or production is greater than
available capacity.
overrun percentage
An item attribute the planning process uses to decide when to suggest new daily rates
for the item. The planning process only suggests a new daily rate for the item if the
current daily rate exceeds the suggested daily rate by more than the acceptable overrun
amount. This attribute lets you reduce nervousness and eliminate minor rate change
recommendations when it is more economical to carry excess inventory for a short time
than it is to administer the rate change. This attribute applies to repetitively planned
items only. The related attribute for discretely planned items is Acceptable Early Days.
See acceptable early days
overwrite option
Option to overwrite existing orders on an MRP plan or an MPS plan during the
planning process. Without overwriting, you can keep your existing smoothed entries as
well as add new ones. By overwriting, you erase the existing entries and add new one
according to the current demand. The overwrite option in used with the append option.
See append option.
payback demand
Temporary material transfer when one project borrows demand from another project.
payback supply
Temporary material transfer when one project lends supply to another project.
percent of capacity
The required hours divided by the available hours for any given department, resource,
and shift combination.
period
See accounting period.
phantom assembly
An assembly Work in Process explodes through when it creates the bill of material for a
job or schedule. A particular assembly can be a phantom assembly on one bill and a
subassembly on another.
pipe
Allows sessions in the same database instance to communicate with each other. Pipes
Glossary-19
are asynchronous, allo

wing multiple read and write access to the same pipe.
plan horizon
The span of time from the current date to a future date that material plans are
generated. Planning horizon must cover at least the cumulative purchasing and
manufacturing lead times, and is usually quite a bit longer.
planned order
A suggested quantity, release date, and due date that satisfies net item requirements.
MRP owns planned orders, and may change or delete the orders during subsequent
MRP processing if conditions change. MRP explodes planned orders at one level into
gross requirements for components at the next lower level (dependent demand).
Planned orders along with existing discrete jobs also serve as input to capacity
requirements planning, describing the total capacity requirements throughout the
planning horizon.
planned purchase order
A type of purchase order you issue before you order actual delivery of goods and
services for specific dates and locations. You normally enter a planned purchase order
to specify items you want to order and when you want delivery of the items. You later
enter a shipment release against the planned purchase order when you actually want to
order the items.
planner delete worker
An independent concurrent process, launched by the memory-based planner, that
removes previous plan output from the tables. It runs only when the memory-based
planner runs without the snapshot.
Planner Workbench
You can use the Planner Workbench to act on recommendations generated by the
planning process for a plan. You can implement planned orders as discrete jobs or
purchase requisitions, maintain planned orders, reschedule scheduled receipts, and
implement repetitive schedules. You can choose all suggestions from an MRP plan, or
only those that meet a certain criteria.
planning bill of material
A bill of material for a planning item that contains a list of items and planning
percentages. You can use a planning bill to facilitate master scheduling and/or material
planning. The total output of a planning bill of material is not limited to 100% (it can
exceed this number by any amount).
Glossary-20
planning exception set

A set of sensitivity controls used to define exceptions in your plan. You define the
exception set according to your selected criteria and then report on exceptions that meet
those criteria. You can assign an exception set to an item.
Planning Exception Set
An item attribute the planning process uses to decide when to raise planning exceptions
for the item. Enter the name of the planning exception set that groups together the
sensitivity controls and exception time periods for item-level planning exceptions for
the item. The item-level planning exceptions include: overcommitted, shortage, excess,
and repetitive variance.
planning horizon
The amount of time a master schedule extends into the future.
planning manager
A process that performs once-a-day and period maintenance tasks. These tasks include
forecast consumption, master schedule relief, forecast and master schedule loads, and
other miscellaneous data cleanup activities.
planning process
The set of processes that calculates net material and resource requirements for an item
by applying on-hand inventory quantities and scheduled receipts to gross requirements
for the item. The planning process is often referred to as the MPS planning process
when planning MPS-planned items only, and the MRP planning process when planning
both MPS and MRP-planned items at the same time. Maintain repetitive planning
periods is another optional phase in the planning process.
Planning Time Fence
A MRP item attribute used to determine a future point in time inside which there are
certain restrictions on the planning recommendations the planning process can make
for the item. For discretely planned items, the planning process cannot suggest new
planned orders for the item or suggest rescheduling existing orders for the item to an
earlier date. For repetitively planned items, the planning process can only suggest new
daily rates that fall inside the acceptable rate increase and acceptable rate decrease
boundaries defined for the item. A value of Cumulative manufacturing lead time means
MRP calculates the planning time fence for the item as the plan date (or the next
workday if the plan is generated on a non workday) plus the cumulative manufacturing
lead time for the item. A value of Cumulative total lead time means MRP calculates the
planning time fence for the item as the plan date (or the next workday if the plan is
generated on a non workday) plus the total manufacturing lead time for the item. A
value of Total lead time means MRP calculates the planning time fence for the item as
the plan date (or the next workday if the plan is generated on a non workday) plus the
Glossary-21
total lead time for the item. A value of User-defined time fence means MRP calculates
the planning time fence for the item as the plan date (or the next workday if the plan is
generated on a non workday) plus the value you enter for Planning Time Fence Days
for the item.
Planning Time Fence Days
An item attribute MRP uses when you set the Planning Time fence attribute to
User-defined time fence. MRP calculates the planning time fence for the item as the plan
date (or the next workday if the plan is generated on a non workday) plus the value you
enter here.
postprocessing lead time
The time required to receive a purchased item into inventory from the initial supplier
receipt, such as the time required to deliver an order from the receiving dock to its final
destination.
preprocessing lead time
The time required to place a purchase order or create a discrete job or repetitive
schedule that you must add to purchasing or manufacturing lead time to determine
total lead time. If you define this time for a repetitive item, the planning process ignores
it.
primary line
See lead time line.
processing lead time
The time required to procure or manufacture an item. For manufactured assemblies,
processing lead time equals the manufacturing lead time.
product
A finished item that you sell. See also finished good.
production line
The physical location where you manufacture a repetitive assembly, usually associated
with a routing. You can build many different assemblies on the same line at the same
time. Also known as assembly line.
production rate
Hourly rate of assemblies manufactured on a production line.
production relief
The process of relieving the master production schedule when a discrete job is created.
This decrements the build schedule to represent an actual statement of supply.
Glossary-22
project
A unit of work broken down into one or more tasks, for which you specify revenue and
billing methods, invoice formats, a managing organization, and project manager and
bill rates schedules. You can charge costs to a project, as well as generate and maintain
revenue, invoice, unbilled receivable and unearned revenue information for a project.
project job
A standard or non-standard WIP job with a project reference. The valuation accounts
associated with this type of job will be project work in process. Any balance remaining
in such a job when it is closed will be reported as a variance.
project task
A subdivision of Project Work. Each project can have a set of top level tasks and a
hierarchy of subtasks below each top level task. You can charge costs to tasks at the
lowest level only. See also Work Breakdown Structure.
projected available balance
Quantity on hand projected into the future if scheduled receipts are rescheduled or
cancelled, and new planned orders are created as per recommendations made by the
planning process. Calculated by the planning process as current and planned supply
(nettable quantity on hand + scheduled receipts + planned orders) minus demand (gross
requirements). Note that gross requirements for projected available includes derived
demand from planned orders. Note also that the planning process uses suggested due
dates rather than current due dates to pass down demand to lower level items. See
current projected on hand.
projected on hand
Quantity on-hand projected into the future if scheduled receipts are not rescheduled or
cancelled, and new planned orders are not created as per recommendations made by
the planning process. Calculated by the planning process as current supply: (nettable
quantity on hand + scheduled receipts) - gross requirements. Note that gross
requirements for projected on hand does not include derived demand from planned
orders. Note also that the planning process uses current due dates rather than
suggested due dates to pass down demand to lower level items. See projected available
balance
purchase order
A type of purchase order you issue when you request delivery of goods or services for
specific dates and locations. You can order multiple items for each planned or standard
purchase order. Each purchase order line can have multiple shipments and you can
distribute each shipment across multiple accounts. See standard purchase order and
planned purchase order.
Glossary-23
purchase requisition
An internal request for goods or services. A requisition can originate from an employee
or from another process, such as inventory or manufacturing. Each requisition can
include many lines, generally with a distinct item on each requisition line. Each
requisition line includes at least a description of the item, the unit of measure, the
quantity needed, the price per item, and the Accounting Flexfield you are charging for
the item. See also internal sales order.
rate-based capacity
Capacity planning at the production line level. Required capacity, available capacity,
and capacity load ratio are calculated for individual production lines. Required and
available capacity are stated in terms of production rate per line per week.
read consistency
A consistent view of all table data committed by transactions and all changes made by
the user, up to the time of the read.
Reduce MPS
An item attribute the Planning Manager uses to decide when to reduce the quantity on
master production schedule entries for the item to zero. A value of None means the
Planning Manager does not reduce order quantities on master production schedule
entries. A value of Past due means the planning process reduces order quantities on
master production schedule entries to zero when the due date for the entry becomes
past due. A value of Within demand time fence means the planning process reduces
order quantities on master production schedule entries to zero when the due date for
the entry moves inside the demand time fence. A value of Within planning time fence
means the planning process reduces order quantities on master production schedule
entries to zero when the due date for the entry moves inside the planning time fence.
repetitive MRP plan
A set of optimal repetitive schedules which satisfy a given master schedule for
repetitive items.
repetitive planning
The planning of demand or production for an item in terms of daily rates rather than
discrete quantities.
Repetitive Planning (item attribute)
An item attribute the planning process uses to decide whether to plan material
requirements for the item in terms of discrete quantities or repetitive daily rates.
repetitive planning period
A period, defined as a number of days, that smooths the production rate over time.
Glossary-24
With repetitive planning periods, you can prevent your planned repetitive production
rate from fluctuating too frequently.
repetitive processing days
The number of days you plan to work on a repetitive schedule, from the first unit start
date to the last unit start date.
repetitive rate
The daily rate for a repetitive schedule. See daily rate.
repetitive schedule
The process of dividing suggested aggregate repetitive schedules and allocating them
across individual production lines, based on predefined line priorities and production
rates.
repetitive schedule allocation
The process of dividing suggested aggregate repetitive schedules and allocating them
across individual production lines, based on predefined line priorities and production
rates.
required capacity
The amount of capacity required for a resource or production line.
required hours
The number of resource hours required per resource unit to build one unit of the bill of
resources item.
required rate
The production rate allocated to an individual production line by the repetitive
schedule allocation process.
requisition
See purchase requisition and internal sales order.
rescheduling assumption
A fundamental piece of planning process logic that assumes that existing open orders
can be rescheduled into closer time periods far more easily than new orders can be
released and received. As a result, the planning process does not create planed order
receipts until all scheduled receipts have been applied to cover gross requirements.
reservation
A guaranteed allotment of product to a specific sales order. A hold is placed on specific
Glossary-25
terms that assures that a certain quantity of an item is available on a certain date when
transacted against a particular charge entity. Once reserved, the product cannot be
allocated to another sales order or transferred in Inventory. Oracle Order Management
checks ATR (Available to Reserve) to verify an attempted reservation. Also known as
hard reservation.
resource
Anything of value, except material and cash, required to manufacture, cost, and
schedule products. Resources include people, tools, machines, labor purchased from a
supplier, and physical space.
resource group
Resources grouped together according to user-defined criteria to facilitate bill of
resource generation and capacity planning.
resource offset percent
An operation resource field that represents, as a percent of the processing lead time for
an item, the item when a resource is required on a routing. For example, if the
processing lead time for an item is 10 days, and the resource is required on the fourth
day, then the resource offset percent is 30%. Capacity uses resource offset percent to
calculate setback days during the bill of resource load process.
resource roll up
Rolls up all required resources for a end assembly based on the routing and bill of
material structure.
resource set
A grouping of bills of resources.
resource hours
The number of hours required by a repetitive schedule, discrete job or planned order.
resource units
The number of units of a resource available for this resource at this operation.
revision
A particular version of an item, bill of material, or routing.
rough cut capacity planning
The process of converting the master schedule into capacity needs for key resources. See
routing-based capacity and rate-based capacity
Glossary-26
rough cut planner

The routine that automatically calculates required resources for rough cut capacity
planning (done when running a report or inquiry).
Rounding Control
An item attribute the planning process uses to decide whether to use decimal or whole
number values when calculating planned order quantities or repetitive rates for the
item. A value of Do not round order quantities the planning process uses and displays
decimal values when calculating planned order quantities and suggested repetitive
rates for the item. A value of Round order quantities means the planning process
rounds decimal values up to the next whole number when calculating planned order
quantities and suggested daily rates for the item. Planned order quantities and
suggested daily rates are always rounded up, never down. The planning process carries
any excess quantities and rates forward into subsequent periods as additional supply.
routing-based capacity
Capacity planning at the resource level. Required capacity, available capacity, and
capacity load ratio are calculated for individual resources assigned to operations on
routings.. Required and available capacity are stated in terms of hours per resource per
week.
safety stock
Quantity of stock planned to have in inventory to protect against fluctuations in
demand and/or supply.
Safety Stock (item attribute)
An item attribute the planning process uses to decide whether to use fixed or
dynamically calculated safety stock quantities when planning material requirements for
the item. A value of MRP-planned percent means the planning process plans to safety
stock quantities it calculates dynamically as a user-defined percentage of the average
gross requirements for a user-defined number of days. The user-defined percentage is
defined by the value you enter for the Safety Stock Percent attribute for the item. For
discretely planned items, the user-defined number of days is defined by the value you
enter for the Safety Stock Bucket Days attribute for the item. For repetitively planned
items, the planning process uses the repetitive planning period rather than Safety Stock
Bucket Days. These safety stock quantities are dynamic in that they vary as a function of
the average gross requirements calculated by the planning process for the item. A value
of Non-MRP planned means the planning process plans to safety stock quantities
calculated and maintained in Inventory. These safety stock quantities are fixed in that
the Snapshot loads them from Inventory before the planning process and they do not
vary unless they are recalculated in Inventory.
Glossary-27
Safety Stock Bucket Days

An item attribute the planning process uses when you set the Safety Stock attribute for
the item to MRP-planned percent. The planning process dynamically calculates safety
stock quantities for the item by multiplying the average gross requirements for the item,
over the time period defined by the value you enter for Safety Stock Bucket Days, by the
value you enter for Safety Stock Percent.
Safety Stock Percent
An item attribute the planning process uses when you set the Safety Stock attribute for
the item to MRP-planned percent. The planning process dynamically calculates safety
stock quantities for the item by multiplying the average gross requirements for the item,
over the time period defined by the value you enter for Safety Stock Bucket Days, by the
value you enter for Safety Stock Percent.
safety stock quantity
The quantity suggested by MRP as additional supply needed for safety stock. This
quantity can change according to an effective date set in Inventory.
schedule date
The date for a master schedule entry for an item. A schedule for an item has a schedule
date and an associated quantity. For Order Management, it is considered the date the
order line should be ready to ship, the date communicated from Order Management to
Inventory as the required date any time you reserve or place demand for an order line.
schedule end date
For repetitive items, defines the end of the repetitive rate for a master schedule.
schedule entry
A schedule for an inventory item. For discrete items, stated by a date and quantity. For
repetitive items, stated by a date, schedule end date, and quantity.
schedule smoothing
The manual process of entering quantities and dates on the master production schedule
that represent a level production policy.
scheduled receipt
A discrete job, repetitive schedule, non-standard job, purchase requisition, or purchase
order. It is treated as part of available supply during the netting process. Schedule
receipt dates and/or quantities are not altered automatically by the MRP system.
set transaction read-only
An ORACLE RDBMS command that allows you to consider all the transactions
Glossary-28
committed after its execution. No transactions are written after the command is
executed. See read consistency.
setback days
The number of days set back from the assembly due date that a resource is required to
build the assembly.
shift
A scheduled period of work for a department within an organization.
ship-to address
A location where items are to be shipped.
shipment relief
The process of relieving the master demand schedule when a sales order ships. This
decrements the demand schedule to represent an actual statement of demand.
Shrinkage Rate
An item attribute the planning process uses to inflate the demand for the item to
compensate for expected material loss. Enter a factor that represents the average
amount of material you expect to lose during your manufacturing process. For example,
if an average 20% of all units of the item fail final inspection, enter a shrinkage rate for
the item of 0.2. In this example, the planning process always inflates net requirements
for the item by a factor of 1.25 (1 / 1 - shrinkage rate).
simulation schedule
Unofficial schedules for personal use that contain the most current scheduled item
information. You can print Simulation schedules, but you cannot confirm or send them
via EDI.
simulation set
group of capacity modifications for resource shifts to simulate, plan, or schedule
capacity.
snapshot
The only phase under the memory-based planning engine. The snapshot takes a
snapshot or picture of supply and demand information at a particular point in time. The
snapshot gathers all the information about current supply and demand that is required
by the planner to calculate net material requirements, including on-hand inventory
quantities and scheduled receipts. Under the memory-based planning engine, explosion
and planning occur in the snapshot phase.
Glossary-29
snapshot delete worker

An independent concurrent process launched by the snapshot monitor that deletes
planning data from the previous planning run.
snapshot monitor
A process, launched by the memory-based snapshot, that coordinates all the processes
related to the memory-based planning engine.
snapshot task
A task performed by the snapshot or a snapshot worker during the planning process.
snapshot worker
A group of independent concurrent processes controlled by the snapshot monitor that
brings information into flat files. This information comes from Work in Process, Bill of
Materials, on-hand quantities, purchase orders, firm planned orders, routings, and
Work in Process job resource requirements.
soft reservation
The planning process considers sales order demand soft reservation.
source forecast
When loading a forecast into another forecast, the source forecast is the forecast you
load from.
sourcing rule
Specifies how to replenish items in an organization, such as purchased items in plants.
You can also use sourcing rules to override sourcing that is specified in the bill of
distribution assigned to an item.
sourcing rule assignment
See assignment hierarchy
standard purchase order
A type of purchase order you issue when you order delivery of goods or services for
specific dates and locations for your company. Each standard purchase order line can
have multiple shipments and you can distribute the quantity of each shipment across
multiple accounts. See purchase order.
statistical forecasting
A mathematical analysis of past transaction history, last forecast quantities, and/or
information specified by the user to determine expected demand.
Glossary-30
suggested aggregate repetitive schedule

The optimal repetitive schedule suggested by MRP to satisfy a given master schedule.
The optimal schedule represents aggregated production for all lines and considers the
constraints of planning periods, item lead time, firm schedules, time fence control,
acceptable rate changes and overrun amounts.
suggested repetitive schedule
The schedule for an individual production line for a specific item that is derived from
the Suggested aggregate schedule. MRP divides the suggested aggregate schedule for a
specific line and item based on the production line attributes: priority, minimum and
maximum rates.
The development and maintenance of multi-organizational distribution and
manufacturing plans across a
Operational cycle time the rate at which products need to be manufactured on the line.
Aids in establishing the daily rates for the production line. TAKT Time = effective
resource hours available per day / Average daily demand
time bucket
A unit of time used for defining and consuming forecasts. A bucket can be one day, one
week, or one period.
time fence
A policy or guideline established to note where various restrictions or changes in
operating procedures take place. The planning process cannot create or reschedule
orders within the planning time fence. This gives the planner the ability to stabilize the
plan and thereby minimizing the nervousness of the system.
time phased requirements
Requirements for resources where the need dates are offset by the lead time for those
resources.
two-level master scheduling
A technique that facilitates the forecast explosion of product groupings into related
master production schedules. The top-level MPS is usually defined for a product line,
family or end product while the second-level is defined for key options and
components.
underload
A condition where required capacity for a resource or production is less than available
capacity.
Glossary-31
usage quantity
The quantity of a component, including component yield required to produce one
assembly in a discrete job or repetitive schedule as stated on the bill of materials.
utilization
Ratio of direct time charged to the clock time scheduled for the resource.
work order date
The date to begin processing the paperwork for the discrete job. This date is offset from
the start date by the preprocessing lead time.
worker
An independent concurrent process that executes specific tasks. Programs using
workers to break large tasks into smaller ones must coordinate the actions of the
workers.
Glossary-32

Index
A
Alerts
appendix, C-1
forecast overconsumption detail, C-1
forecast overconsumption summary , C-1
assignment sets
assignment hierarchy, 5-8
defining, 5-8
B
bills of distribution
See BODs, 5-8
BODs, 5-8
defining, 5-8
C
crp reports, 11-33
find exceptions window, D-2
find items window, D-4
find supply/demand Window, D-5
Navigating through a customized find
window, D-1
appendix, D-1
Customizing the Planning Exception Messages
Process
appendix, E-2

appendix, E-5
appendix, E-8
F
Find Exceptions Window
appendix, D-2
Find Items Window
appendix, D-4
Find Supply/Demand Window
appendix, D-5
forecast
explosion, 2-36
forecast explosion
logic, 2-36
appendix, C-1
appendix, C-1
Forecasts - Statistical and Focus
appendix, F-1
K
kanban calculations
viewing and updating, 12-8
kanban tools menu, 12-10
L
Late Order Report, 11-21
Index-1
Memory-Based Planning Engine

appendix, G-1
processing steps, G-1
Saving Your Search in a Folder

appendix, D-2
Sorting Data on Multiple Levels
appendix, D-4
sourcing rules
defining, 5-8
supply chain, 5-8
appendix, E-5
appendix, E-7
Summary of Planning Exception Messages
Activities
appendix, E-5
supply chain
assignment sets, 5-8
sourcing rules, 5-8
supply chain modeling
supply chain definition, 5-8
Supported and Unsupported Customizations
appendix, E-2
N
Navigating through a Customized Find Window
appendix, D-1
O
On Hand vs. Available Report, 11-7
Oracle MRP Character Mode Forms and
Corresponding GUI Windows
appendix, H-1
P
parallel processing
inter-process communication, 14-2
overview, 14-1
planner parallel processing, 14-8
planning manager, 14-9
process control, 14-1
single processor machine, 14-2
snapshot, 14-4
snapshot parallel processing, 14-8
Planning Exception Messages Item Type
appendix, E-4
Planning Exception Messages Workflow
appendix, E-1
planning manager worker, 11-32
planning parameters, 11-33
Processing Steps
appendix, G-1
project MRP setup tasks, 13-2
R
Report
late order, 11-21
reports
master schedule comparison report, 11-23
Reports
on hand vs. available, 11-7
Index-2
W
appendix, B-1
customizing the planning exception messages
process, E-2
exception process 1 activities , E-5
exception process 2 activities, E-8
planning exception messages item type, E-4
summary of exception process 1, E-5
summary of exception process 2, E-7
summary of planning exception messages
activities, E-5
supported and unsupported customizations,
E-2
workflow process forward (node 2), E-6, E-9
Workflow Process Forward
appendix, E-9
appendix, E-6

Oracle® MRP: User's Guide Release 12.1

Uploaded by

Copyright:

Available Formats

Oracle® MRP: User's Guide Release 12.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle® MRP: User's Guide Release 12.1

Uploaded by

Copyright:

Available Formats

Oracle MRP

Oracle MRP User's Guide, Release 12.1

Send Us Your Comments

Copying and Merging Forecasts .............................................................................................. 2-9

Material Requirements Planning

Receiving Inspection Inventory ............................................................................................. 4-42

Supply Chain Planning

Viewing On-hand Quantities ...................................................................................................6-5

Time Fence Control

Two-Level Master Scheduling

Repetitive Schedule Relief ................................................................................................... 10-14

Project MRP Planning Logic .................................................................................................. 13-8

Windows and Navigator Paths

Customized Find Windows

Workflow - Planning Exception Messages

Forecasting - Statistical and Focus

Memory-based Planning Engine

Character Mode Forms and GUI Windows

Are the implementation steps correct and complete?

Access to Oracle Support

Related Information Sources

Oracle Electronic Technical Reference Manual - The Oracle Electronic Technical

Oracle E-Business Suite User's Guide

Oracle Alert User Guide

Oracle E-Business Suite Developer's Guide

Oracle E-Business Suite User Interface Standards for Forms-Based Products

Oracle E-Business Suite Flexfields Guide

Oracle Workflow Developer's Guide

User Guides Related to This Product

Oracle Bills of Material User's Guide

Oracle Capacity User's Guide

Oracle Flow Manufacturing User's Guide

Oracle Inventory User's Guide

Oracle Order Management User's Guide

Oracle Project Manufacturing User's Guide

Oracle Purchasing User's Guide

Oracle Supplier Scheduling User's Guide

Oracle Work in Process User's Guide

Installation and System Administration Guides

Oracle E-Business Suite Concepts

Oracle E-Business Suite Installation Guide: Using Rapid Install

The Oracle E-Business Suite Upgrade Guides

Oracle E-Business Suite Setup Guide

Oracle E-Business Suite Maintenance Guide

Oracle E-Business Suite Security Guide

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Set up an Oracle Applications System Administrator responsibility. See: System

Related Product Setup Steps

Performing system-wide setup tasks such as configuring concurrent managers and

Managing data security, which includes setting up responsibilities to allow access

Define your planners.

Define your unit of measure conversions.

Define your item planning information.

If you operate in a project-based environment, add pegging levels for Project

If you operate in a Flow Manufacturing environment, define items for products,

Define financial options

Set up approval information

Oracle Bills of Material

Define your organization calendar