R12 gop

Oracle® Global Order Promising
Implementation and User's Guide
Release 12
Part No. B31554-01

November 2006

Oracle Global Order Promising Implementation and User's Guide, Release 12

Part No. B31554-01

Copyright © 2004, 2006, Oracle. All rights reserved.

Primary Author:     Sunanda Chatterjee

Contributing Author:     Milind Govind Phadke

Contributor:     Anwesh Roy, James Glasmann, Jiangang (James) Guo, Preetam Dandapani, Michael Hasan,
Yvon Tang

The Programs (which include both the software and documentation) contain proprietary information; they
are provided under a license agreement containing restrictions on use and disclosure and are also protected
by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or
decompilation of the Programs, except to the extent required to obtain interoperability with other
independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in
the documentation, please report them to us in writing. This document is not warranted to be error-free.
Except as may be expressly permitted in your license agreement for these Programs, no part of these
Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on
behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS
Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication,
disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall
be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent
applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted
Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for such
purposes, and we disclaim liability for any damages caused by such use of the Programs.

The Programs may provide links to Web sites and access to content, products, and services from third parties.
Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all
risks associated with the use of such content. If you choose to purchase any products or services from a third
party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality
of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party,
including delivery of products or services and warranty obligations related to purchased products or services.
Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third
party.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.

Contents

Send Us Your Comments

Preface

1 Oracle Global Order Promising
Overview................................................................................................................................... 1-1
Configuration............................................................................................................................ 1-5

2 Setting Up
System Setup............................................................................................................................. 2-1
Functional Setup for ATP Based on Collected Data.................................................................2-8
Functional Setup for ATP Based on Planning Output........................................................... 2-19

3 ATP Based on Collected Data
Basic ATP................................................................................................................................... 3-1
Single-Level Supply Chain ATP .............................................................................................. 3-2
Configuration ATP.................................................................................................................... 3-8
Product Family ATP................................................................................................................ 3-28
Demand Class ATP................................................................................................................. 3-31
Improved ATP Performance ...................................................................................................3-32

4 ATP Based on Planning Output: Part I
Basic ATP................................................................................................................................... 4-1
Multi-Level Supply Chain ATP ............................................................................................... 4-2
Configuration ATP.................................................................................................................. 4-32
Product Family ATP................................................................................................................ 4-73

iii

Combined Item-Product Family ATP..................................................................................... 4-80
Allocated ATP........................................................................................................................ 4-105

5 ATP Based on Planning Output: Part II
End Item Substitution............................................................................................................... 5-1
ATP Result......................................................................................................................... 5-27
Support for Lot Based Components........................................................................................ 5-31
24x7 ATP Support.................................................................................................................... 5-37
Multiple Plans......................................................................................................................... 5-42
Improved ATP Performance Based on Summarized Data..................................................... 5-43
Unplanned Items..................................................................................................................... 5-45
Honoring Plan Recommendations for Sales Order Rescheduling.........................................5-45
ATP Support for Distribution Planning................................................................................. 5-46

6 ATP Inquiry and Order Scheduling
ATP Inquiry............................................................................................................................... 6-1
ATP Criteria......................................................................................................................... 6-2
ATP Details.......................................................................................................................... 6-5
Diagnostic ATP........................................................................................................................ 6-16
Business Application..........................................................................................................6-17
ATP Logic.......................................................................................................................... 6-19
Global Availability............................................................................................................. 6-24
Order Scheduling.................................................................................................................... 6-26
Ship Date and Arrival Date Calculation.............................................................................6-26
Override ATP..................................................................................................................... 6-31
Shipping, Receiving, and Carrier Calendars.......................................................................... 6-34

7 Order Backlog Workbench
Order Backlog Workbench........................................................................................................ 7-1
Selection Criteria for Scheduling with the Order Backlog Workbench.................................. 7-6
Scheduling Order Lines with the Order Backlog Workbench............................................... 7-12

8 Troubleshooting
Troubleshooting........................................................................................................................ 8-1
Debugging............................................................................................................................... 8-12
SQL Queries............................................................................................................................ 8-15

A Profile Options
Oracle Global Order Promising Profile Options..................................................................... A-1

iv

B Application Program Interface
Available-To-Promise Application Program Interface............................................................ B-1

C Windows and Navigator Paths
Windows and Navigation Paths............................................................................................... C-1

Glossary

Index

v

Send Us Your Comments

Oracle Global Order Promising Implementation and User's Guide, Release 12
Part No. B31554-01

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 Applications Release
Online Documentation CD available on Oracle MetaLink 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.

vii

Preface

Intended Audience
Welcome to Release 12 of the Oracle Global Order Promising Implementation and User's
Guide.
This guide assumes you have a working knowledge of the following:
• The principles and customary practices of your business area.

• Oracle Global Order Promising
If you have never used Oracle Global Order Promising, Oracle suggests you attend
one or more of the Oracle Global Order Promising training classes available
through Oracle University.

• The Oracle Applications graphical user interface.
To learn more about the Oracle Applications graphical user interface, read the
Oracle Applications User's Guide.

See Other Information Sources for more information about Oracle Applications product
information.

Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of assistive
technology. This documentation is available in HTML format, and contains markup to
facilitate access by the disabled community. Standards will continue to evolve over
time, and Oracle is actively engaged with other market-leading technology vendors to
address technical obstacles so that our documentation can be accessible to all of our
customers. For additional information, visit the Oracle Accessibility Program Web site
at http://www.oracle.com/accessibility/.

ix

Accessibility of Code Examples in Documentation
JAWS, a Windows screen reader, may not always correctly read the code examples in
this document. The conventions for writing code require that closing braces should
appear on an otherwise empty line; however, JAWS may not always read a line of text
that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations
that Oracle does not own or control. Oracle neither evaluates nor makes any
representations regarding the accessibility of these Web sites.
See Related Information Sources on page xi for more Oracle Applications product
information.

TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services
within the United States of America 24 hours a day, seven days a week. For TTY
support, call 800.446.2398.

Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of assistive
technology. This documentation is available in HTML format, and contains markup to
facilitate access by the disabled community. Accessibility standards will continue to
evolve over time, and Oracle is actively engaged with other market-leading technology
vendors to address technical obstacles so that our documentation can be accessible to all
of our customers. For more information, visit the Oracle Accessibility Program Web site
at http://www.oracle.com/accessibility/ .

Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The
conventions for writing code require that closing braces should appear on an otherwise
empty line; however, some screen readers may not always read a line of text that
consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations
that Oracle does not own or control. Oracle neither evaluates nor makes any
representations regarding the accessibility of these Web sites.

x

Structure
1 Oracle Global Order Promising
2 Setting Up
3 ATP Based on Collected Data
4 ATP Based on Planning Output: Part I
5 ATP Based on Planning Output: Part II
6 ATP Inquiry and Order Scheduling
7 Order Backlog Workbench
8 Troubleshooting
A Profile Options
B Application Program Interface
C Windows and Navigator Paths
Glossary

Related Information Sources
You can choose from many sources of information, including online documentation,
training, and support services, to increase your knowledge and understanding of Oracle
Global Order Promising.
If this guide refers you to other Oracle Applications documentation, use only the
Release 12 versions of those guides.

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.

Online Documentation
All Oracle Applications documentation is available online (HTML or PDF).
• Online Help: The new features section in the HTML help describes new features in
Oracle Applications Release 12. This information is updated for each new release of
Oracle Global Order Promising. The new features section also includes information
about any features that were not yet available when this guide was printed. For
example, if your administrator has installed software from a mini-packs an
upgrade, this document describes the new features. Online help patches are
available on OracleMetaLink.

xi

• Readme File: Refer to the readme file for patches that you have installed to learn
about new documentation or documentation patches that you can download.

Related User's Guides
Oracle Global Order Promising shares business and setup information with other
Oracle Applications products. Therefore, you may want to refer to other user's guides
when you set up and use Oracle Global Order Promising.
You can read the guides online by choosing Library from the expandable menu on your
HTML help window, by reading from the Oracle Applications Document Library CD
included in your media pack, or by using a Web browser with a URL that your system
administrator provides.
If you require printed guides, you can purchase them from the Oracle Store at
http://oraclestore.oracle.com.

Guides Related to All Products
Oracle Applications User's Guide
This guide explains how to enter data, query, run reports, and navigate using the
graphical user interface (GUI) available with this release of Oracle Global Order
Promising (and any other Oracle Applications products). This guide also includes
information on setting user profiles, as well as running and reviewing reports and
concurrent processes.
You can access this user's guide online by choosing Getting Started with Oracle
Applications from any Oracle Applications help file.

User Guides Related to This Product
Oracle Advanced Planning Implementation and User's Guide
This guide describes how to use Oracle's planning solution for supply chain planning
performance. This guide can be used as a reference when you are implementing Oracle
Advanced Supply Chain Planning with Oracle Global Order Promising.
Oracle Inventory User's Guide
This guide describes how to define items and item information, perform receiving and
inventory transactions, maintain cost control, plan items, perform cycle counting and
physical inventories, and set up Oracle Inventory.
Oracle Order Management User's Guide
This guide describes how to enter sales orders and returns, copy existing sales orders,
schedule orders, release orders, create price lists, and discounts for orders, run
processes, and create reports.
Oracle Workflow Guide

xii

This guide explains how to define new workflow business processes as well as
customize existing Oracle Applications-embedded workflow processes. You also use
this guide to complete the setup steps necessary for any Oracle Applications product
that includes workflow-enabled processes.

Installation and System Administration
Oracle Applications Concepts
This guide provides an introduction to the concepts, features, technology stack,
architecture, and terminology for Oracle Applications Release 12. It provides a useful
first book to read before an installation of Oracle Applications. This guide also
introduces the concepts behind Applications-wide features such as Business Intelligence
(BIS), languages and character sets, and Self-Service Web Applications.
Installing Oracle Applications
This guide provides instructions for managing the installation of Oracle Applications
products. In Oracle Applications Release 12, much of the installation process is handled
using Oracle Rapid Install, which minimizes the time to install Oracle Applications, the
Oracle9 technology stack, and the Oracle9i Server technology stack by automating
many of the required steps. This guide contains instructions for using Oracle Rapid
Install and lists the tasks you need to perform to finish your installation. You should use
this guide in conjunction with individual product user's guides and implementation
guides.
Upgrading Oracle Applications
Refer to this guide if you are upgrading your Oracle Applications Release 10.7 or
Release 11i products to Oracle Applications Release 12. This guide describes the
upgrade process and lists database and product-specific upgrade tasks. You must be
either at Oracle Applications Release 10.7 (NCA, SmartClient, or character mode) or
Oracle Applications Release 11i, to upgrade to Oracle Applications Release 12. You
cannot upgrade to Oracle Applications Release 12 directly from releases prior to 10.7.
Maintaining Oracle Applications
Use this guide to help you run the various AD utilities, such as AutoUpgrade,
AutoPatch, AD Administration, AD Controller, AD Relink, License Manager, and
others. It contains how-to steps, screenshots, and other information that you need to run
the AD utilities. This guide also provides information on maintaining the Oracle
applications file system and database.
Oracle Applications System Administrator's Guide
This guide provides planning and reference information for the Oracle Applications
System Administrator. It contains information on how to define security, customize
menus and online help, and manage concurrent processing.
Oracle Alert User's Guide
This guide explains how to define periodic and event alerts to monitor the status of

xiii

your Oracle Applications data.
Oracle Applications Developer's Guide
This guide contains the coding standards followed by the Oracle Applications
development staff. It describes the Oracle Application Object Library components
needed to implement the Oracle Applications user interface described in the Oracle
Applications User Interface Standards for Forms-Based Products. It also provides
information to help you build your custom Oracle Forms Developer 6i forms so that
they integrate with Oracle Applications.
Oracle Applications User Interface Standards for Forms-Based Products
This guide contains the user interface (UI) standards followed by the Oracle
Applications development staff. It describes the UI for the Oracle Applications products
and how to apply this UI to the design of an application built by using Oracle Forms.

Other Implementation Documentation
Oracle Applications Product Update Notes
Use this guide as a reference for upgrading an installation of Oracle Applications. It
provides a history of the changes to individual Oracle Applications products between
Release 11i and Release 12. It includes new features, enhancements, and changes made
to database objects, profile options, and seed data for this interval.
Multiple Reporting Currencies in Oracle Applications
If you use the Multiple Reporting Currencies feature to record transactions in more than
one currency, use this manual before implementing Oracle Global Order Promising.
This manual details additional steps and setup considerations for implementing Oracle
Global Order Promising with this feature.
Multiple Organizations in Oracle Applications
This guide describes how to set up and use Oracle Global Order Promising with Oracle
Applications' Multiple Organization support feature, so you can define and support
different organization structures when running a single installation of Oracle Global
Order Promising.
Oracle Workflow Administrator's Guide
This guide explains how to complete the setup steps necessary for any Oracle
Applications product that includes workflow-enabled processes, as well as how to
monitor the progress of runtime workflow processes.
Oracle Workflow Developer's Guide
This guide explains how to define new workflow business processes and customize
existing Oracle Applications-embedded workflow processes. It also describes how to
define and customize business events and event subscriptions.
Oracle Workflow User's Guide

xiv

This guide describes how Oracle Applications users can view and respond to workflow
notifications and monitor the progress of their workflow processes.
Oracle Workflow API Reference
This guide describes the APIs provided for developers and administrators to access
Oracle Workflow.
Oracle Applications Flexfields Guide
This guide provides flexfields planning, setup and reference information for the Oracle
Global Order Promising implementation team, as well as for users responsible for the
ongoing maintenance of Oracle Applications product data. This manual also provides
information on creating custom reports on flexfields data.
Oracle eTechnical Reference Manuals
Each eTechnical Reference Manual (eTRM) contains database diagrams and a detailed
description of database tables, forms, reports, and programs for a specific Oracle
Applications product. This information helps you convert data from your existing
applications, integrate Oracle Applications data with non-Oracle applications, and write
custom reports for Oracle Applications products. Oracle eTRM is available on Metalink.
Oracle Manufacturing APIs and Open Interfaces Manual
This manual contains up-to-date information about integrating with other Oracle
Manufacturing applications and with your other systems. This documentation includes
API's and open interfaces found in Oracle Manufacturing.
Oracle Order Management Suite APIs and Open Interfaces Manual
This manual contains up-to-date information about integrating with other Oracle
Manufacturing applications and with your other systems. This documentation includes
API's and open interfaces found in Oracle Order Management Suite.
Oracle Applications Message Reference Manual
This manual describes all Oracle Applications messages. This manual is available in
HTML format on the documentation CD-ROM for Oracle Applications Release 12.

Training and Support
Training
Oracle offers a complete set of training courses to help you and your staff master Oracle
Global Order Promising and reach full productivity quickly. These courses are
organized into functional learning paths, so you take only those courses appropriate to
your job or area of responsibility.
You have a choice of educational environments. You can attend courses offered by
Oracle University at any one of our many Education Centers, you can arrange for our
trainers to teach at your facility, or you can use Oracle Learning Network (OLN), Oracle
University's online education utility. In addition, Oracle training professionals can tailor
standard courses or develop custom courses to meet your needs. For example, you may

xv

want to use your organization structure, terminology, and data as examples in a
customized training session delivered at your own facility.
Support
From on-site support to central support, our team of experienced professionals provides
the help and information you need to keep Oracle Global Order Promising working for
you. This team includes your Technical Representative, Account Manager, and Oracle's
large staff of consultants and support specialists with expertise in your business area,
managing an Oracle9i server, and your hardware and software environment.

Do Not Use Database Tools to Modify Oracle Applications Data
Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser,
database triggers, or any other tool to modify Oracle Applications 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 Applications data, you risk destroying the integrity of your
data and you lose the ability to audit changes to your data.
Because Oracle Applications tables are interrelated, any change you make using Oracle
Applications can update many tables at once. But when you modify Oracle
Applications data using anything other than Oracle Applications, 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 Applications.
When you use Oracle Applications to modify your data, Oracle Applications
automatically checks that your changes are valid. Oracle Applications 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.

About Oracle
Oracle develops and markets an integrated line of software products for database
management, applications development, decision support, and office automation, as
well as Oracle Applications, an integrated suite of more than 160 software modules for
financial management, supply chain management, manufacturing, project systems,
human resources and customer relationship management.
Oracle products are available for mainframes, minicomputers, personal computers,
network computers and personal digital assistants, allowing organizations to integrate
different computers, different operating systems, different networks, and even different
database management systems, into a single, unified computing and information
resource.

xvi

Oracle is the world's leading supplier of software for information management, and the
world's second largest software company. Oracle offers its database, tools, and
applications products, along with related consulting, education, and support services,
in over 145 countries around the world.

Your Feedback
Thank you for using Oracle Global Order Promising and this user's guide. Oracle values
your comments and feedback. At the beginning of this guide is a Reader's Comment
Form you can use to explain what you like or dislike about Oracle Global Order
Promising or this user's guide. You can send comments to us at the e-mail address
mfgdoccomments_us@oracle.com.

Do Not Use Database Tools to Modify Oracle Applications Data
Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle Applications 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 Applications data, you risk destroying the integrity of your
data and you lose the ability to audit changes to your data.
Because Oracle Applications tables are interrelated, any change you make using an
Oracle Applications form can update many tables at once. But when you modify Oracle
Applications data using anything other than Oracle Applications, 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 Applications.
When you use Oracle Applications to modify your data, Oracle Applications
automatically checks that your changes are valid. Oracle Applications 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.

xvii

1
Oracle Global Order Promising

Overview
Oracle Global Order Promising (GOP) provides you with an internet based,
sophisticated, and fast order promising tool that provides accurate delivery promises
that your customers can rely on. Oracle Global Order Promising is a comprehensive
order promising solution that determines, based on the current and projected demands
and supplies across a supply chain and on an extended supply chain, when a customer
order can be fulfilled. This includes distributed global order promising and multi-level
supply chain Available-To-Promise (ATP), Capable-To-Promise (CTP), and
Capable-To-Deliver (CTD).
Oracle Global Order Promising allows you to consolidate supply and demand
information from multiple transaction systems to provide a consolidated global picture
of supply and demand. It is accessible from multiple order entry systems or other order
capture systems such as call centers or web stores. It is fully integrated with all of
Oracle's Order Management and customer relationship management applications for
capturing orders.
It can be deployed either as a component of a complete eBusiness suite implementation,
or on a separate server. This flexibility allows you to support any combination of
standalone order promising configurations. This also ensures high availability and
unequaled scalability. You can provide an extremely accurate statement of availability
to all customers in your global supply chain.
Oracle Global Order Promising addresses the following key business issues:
• How can I promise the most accurate dates?

• How quickly can I respond to a customer request?

• How can I get availability information from anywhere?

Oracle Global Order Promising 1-1

Key Capabilities
Supply Chain Available-To-Promise
Large global companies have many different manufacturing and distribution locations
that can ship the same product to customers. In this environment with multiple supply
locations, your customers or sales representatives must be able to easily and quickly
identify which location has the appropriate product and select the best location. Oracle
Global Order Promising determines the best location for you based on the product and
order request date. Sourcing rules determine the acceptable choices, allowing you to
maintain control over which orders get routed to which fulfillment locations.
Multi-Level Supply Chain Available-To-Promise, Capable-To-Promise, and
Capable-To-Deliver
Oracle Global Order Promising calculates promise dates on the basis of both current
on-hand supplies (available-to-promise) and future demand versus supply. It checks for
availability at multiple bills of material levels and at multiple supply chain locations,
drilling down into resource and supplier capacities as necessary (capable-to-promise).
Oracle Global Order Promising also considers intransit lead times in its calculations.
You can perform a multi-level component and resource availability check across your
entire supply chain for the products requested. Using Oracle Global Order Promising,
you control the organizations and suppliers to be included in the availability inquiry,
and you control the number of levels in your supply chain bill to be considered in your
check. At each level in the supply chain, you specify the key components and the
bottleneck resources for which to check availability. Oracle Global Order Promising's
Multi-Level ATP functionality considers transit lead time at each stage of your supply
chain from suppliers, through internal facilities to customers, to provide accurate
delivery promises your customers can rely on.
Allocated ATP
Allocated ATP allows you to allocate supply by sales channels or customers. You can
protect your sales channels or customers from each other by ensuring that each one gets
certain portion of supply. Depending on the situation, the allocation can be equal to the
forecast of the sales channel or customer, or a portion of supply when supply is
constraint.
Available To Promise for Multi-Level Configurations
Oracle Global Order Promising supports Assemble-To-Order (ATO) environments. You
designate any optional items for an ATP check at any level of the configuration. This
provides an accurate availability date for the end configuration. Oracle Global Order
Promising integrates with Oracle Configurator to provide real time availability
information during product configuration.
Graphical Information for your Planners
The result of a multi-level ATP is represented in a detailed pegging tree that shows you
the component and resource availability at all the levels across the supply chain. You

1-2 Oracle Global Order Promising Implementation and User's Guide

can easily identify a material shortage or bottleneck resource. You can further look at
the component or resource cumulative availability, or supply and demand information
for any time in the planning horizon.
Global Access
Oracle Global Order Promising is implemented as a PL/SQL package that is call-able
from web stores, order entry applications such as Oracle Order Management, and from
the menu structure of the Oracle Advanced Planning Suite.
Product Family ATP
In a customer driven manufacturing environment, it may not always be possible to
forecast the exact demand of the end item. However, it may be possible to define
aggregate requirements and forecast at an aggregate level. Product Family ATP allows
you to promise orders for a specific end item based on the supply statement at an
aggregate (product family) level.
The member items within a product family usually require similar raw material and
manufacturing process. Therefore, the end items can be interchanged within a product
family. In such a scenario, if a demand is in the future and beyond the manufacturing
lead time, you can use Combined Item-Product Family ATP to take advantage of
aggregate supplies beyond a well-defined time period in the planning horizon.
Single Statement of Availability
You can consolidate data from multiple instances and different versions of Oracle
Applications. Existing Oracle Application (Releases 10.7 and 11) customers need not
upgrade other applications. Thus, multiple order entry systems can access a global
statement of availability.
Scalability
Oracle Global Order Promising leverages the multi-threading capabilities of the Oracle
database to provide support for multiple concurrent order promising requests.
Backward Compatibility
Using Oracle Global Order Promising, you consolidate availability information from
multiple instances and different versions of Oracle Applications. Oracle Global Order
Promising is compatible with any supported version of Oracle Applications. Current
Oracle customers implement Oracle Global Order Promising without upgrading their
other Oracle Applications.
Interface to Non-Oracle Applications
You can also include data from non-Oracle systems in your global statement of supply,
demand, and availability. Interface tables allow you to collect data from non-Oracle
applications. Non-Oracle application order entry or web store systems communicate
with Oracle Global Order Promising through application program interfaces (APIs).
Flexible Configuration
Oracle's Global Order Promising solution is flexible and configurable. You control the
complexity of the availability inquiry. You specify the list of potential sources to be


considered in the availability check. Sourcing rules are used to specify the approved
sources. These sourcing rules are assigned to products or customers. Sourcing rules
allow you to control which products can be quoted to a customer from specific
locations.
A flexible, hierarchical, approach is used to assign sources. This hierarchical assignment
allows you to employ sophisticated sourcing strategies with minimal data entry. Rules
can be applied at several levels. For example, you can apply rules globally to entire
organizations, to categories of products, or to individual stock keeping units. More
specific rules override more general rules, allowing you to apply default rules and
maintain them on an exception basis. This reduces the overhead necessary to maintain
your global model.
24x7 ATP Support
Oracle Global Order Promising provides 24x7 ATP support that enables you to refer a
plan for immediate delivery quotes for new orders even when the underlying supply
chain plan is being refreshed. Automatic exceptions are generated for orders that are
promised using the original plan but cannot be synchronized against the refreshed plan.
You can also turn off ATP for a time period to speed up the switching process to the
refreshed plan.
Oracle Global Order Promising also provides these additional flexibilities:
• Check availability for an item or a set of items across bills and across organizations.

• Control single level or multi-level availability check.

• Availability checks at a product family level allowing more rapid response in mixed
mode production environments.

• Specify ship set or arrival set as constraints in the availability inquiry.

• Specify infinite time fence to limit the time the availability is constrained.

• Allow forward and backward consumption.

Integration with Other Oracle Applications
Oracle Global Order Promising is integrated with, but not limited to the following:
• Oracle Order Management

• Oracle Configurator

• Oracle iStore

• Oracle Spares Management


Configuration
Oracle Global Order Promising supports the following configurations for
implementation:
• Standalone Planning Server Configuration: Oracle Global Order Promising sits on a
different instance from other enterprise resource planning (ERP) applications.

• Integrated Planning Server Configuration: Oracle Global Order Promising sits on
the same instance as other enterprise resource planning applications.

Standalone Planning Server Configuration
In the Standalone Planning Server Configuration, supply and demand are pulled from
the source instances to the Oracle Global Order Promising instance through database
links.
The following figure shows the centralized order promising configuration:

Standalone Planning Server Configuration

Integrated Planning Server Configuration
With the Integrated Planning Server Configuration, Oracle Global Order Promising and
its source data reside in the same database. No database link is required in this case.
The two components can communicate through the planning object application
program interfaces (APIs) and the interface tables defined in Oracle Applications.
The following figure shows the decentralized order promising configuration:


Integrated Planning Server Configuration

Deployment
Oracle Global Order Promising can be deployed in the following two ways:
• Deployed without Oracle Advanced Supply Chain Planning (ASCP). Availability
calculation is based on the collected supply and demand data from transactional
systems. It is often referred to as ATP Based on Collected Data.

• Deployed with Oracle Advanced Supply Chain Planning. Availability calculation is
based on an ASCP plan output. It is often referred to as ATP Based on Planning
Output. The advantage of this deployment is the ability to do CTP and CTD checks,
as well as an ability to use advanced order promising capabilities, such as Allocated
ATP and End Item Substitution.

Note: When you deploy Oracle Advanced Supply Chain Planning,
there is no restriction on how you can deploy ATP. You can choose
ATP Based on Collected Data or ATP Based on Planning Output.
However, if you choose ATP Based on Collected Data, you can only
use the capabilities that are enabled for that mode.

ATP Based on Collected Data
This deployment offers backwards compatibility to existing application users. Most of
the 10.7 and R11 ATP capabilities are available in this deployment.
The major difference is the introduction of data collection. It is a process to pull
transactional data into a repository for Oracle Global Order Promising.
The section called ATP Based on Collected Data Setup Flow, page 2-9 provides
detailed setup instructions for this deployment method.
Chapter 3, ATP Based on Collected Data, provides an explanation of the capabilities
supported with this deployment method. The main capabilities are:


• Basic ATP

• Single-Level Supply Chain ATP

• Product Family ATP

• Configuration ATP

• Demand Class ATP

ATP Based on Planning Output
With the deployment of Oracle Advanced Supply Chain Planning, you have a more
realistic supply picture that considers various constraints. Oracle Global Order
Promising takes advantage of the output from an ASCP plan and promises delivery
dates based on that. Additionally, there are a set of enhanced capabilities that provide
you with a better and more flexible order promising solution.
The ATP Based on Planning Output Setup Flow, page 2-20 provides detailed setup
instructions for this deployment method.
Chapters 4 and 5, ATP Based on Planning Output, provide an explanation of the
capabilities supported in this deployment method. The main capabilities are:
• Basic ATP

• Multi-Level Supply Chain ATP



• Allocated ATP


• End Item Substitution


2
Setting Up

This chapter covers the following topics:
• System Setup
• Functional Setup for ATP Based on Collected Data
• Functional Setup for ATP Based on Planning Output

System Setup
The following section explains the system and database preparation for Oracle Global
Order Promising.
The Source instance refers to the database where other enterprise resource planning
(ERP) applications, including Oracle Order Management, reside. The Destination
instance refers to the database where Oracle Global Order Promising and Oracle
Advanced Supply Chain Planning reside.

One Instance Setup
When Oracle Global Order Promising resides on the same instance as the other
enterprise resource planning applications, you need to perform the following system
setup steps:

Setting Up 2-1

One Instance Setup

1. Install Patches:
Context: You need to perform this step only once.
Required: Yes
You need to install the Oracle Global Order Promising (or ATP) source and
destination patches on the same instance. The Data Collection patches also need to
be applied. The patch numbers can be release specific. You can find the patch
numbers on Oracle Support Metalink under Top Tech Docs in Advanced Planning
and Scheduling, or by contacting Oracle Support.

Note: Before beginning the installation of the source patch, count
all, if any, invalid database objects. If after the patch is installed,
there are more invalid objects than before, there was a problem
with the patch application.

2. Run Create APS Partitions Concurrent Program:
Required: Yes
You need to run Create APS Partitions concurrent program. This step is also part of
Oracle Advanced Supply Chain Planning system setup. If you have already
performed this step as part of Oracle Advanced Supply Chain Planning setup, you
do not need to repeat this step.

Note: This step is not needed unless the profile MSC: Share Plan
Partitions is set to No.

3. Run Create Global ATP Flexfields Concurrent Program:
Context: Run this program on the source instance only if you are on Release 10.7 or
Release 11.


Required: Yes
The Create Global ATP Flexfields concurrent program creates new flexfield
segments to hold ATP data at the item, bills of material, routing, and resource
levels.

4. Define Instance:
Context: Set up for each source instance.
Required: Yes
Under the Order Management User responsibility, go to Scheduling, and ATP and
Scheduling Setup. Then select Instances.

Application Instances Window

• Instance Code: This field contains a user-defined, three character short form for
the instance to be planned.

• Instance Type: This field contains the valid values are Discrete, Process, and
Discrete and Process. This field controls whether discrete manufacturing data,
process manufacturing data, or both are collected from the transaction instance
to the destination instance for order promising.

• Version: This field contains the Oracle Application version of the transaction
instance.

• From Source to APS: Leave this field blank.

• From APS to Source: Leave this field blank too.

Setting Up 2-3

• Enable Flag: Select this option to enable the collection process.

• GMT Difference: Leave it blank. This field is for future use.

• Assignment Set: Enter the default assignment set for this instance. The
assignment is used to resolve sourcing for order promising inquiries.

Important: Category-level assignments are supported only if
the category set indicated by MRP: Sourcing Rule Category Set
and MSC: Sourcing Rule Category Set is controlled at the
Master level and not at the Organization level.

Note: This step is also part of the Oracle Advanced Supply
Chain Planning system setup. If you have already performed
this step as part of the Oracle Advanced Supply Chain
Planning setup, you do not need to repeat this step.

5. Run Create ATP Partitions Concurrent Program:
Context: Run this concurrent program if you are if upgrading from prior 11i release.
Required: Yes.

Two Instances Setup

Two Instances Setup

1. Install Patches:
Required: Yes
Step 1 Install Patches
You need to install the Oracle Global Order Promising source patches on the source


instance and the Oracle Global Order Promising destination patches on the
destination instance. The Data Collection patches also need to be applied. The patch
numbers can be release specific. You can find the patch numbers from Oracle
Support Metalink under Top Tech Docs in Advanced Planning and Scheduling, or
by contacting Oracle Support.

Note: Before beginning the installation of the source patch, count
all, if any, invalid database objects. If after the patch is installed,
there are more invalid objects than before, there was a problem
with the patch application.

2. Create Database Links:
Required: Yes
The database administrator needs to create two database links: one that points from
source database to destination database, and the other that points from the
destination database to the source database.
If you want the source instance to be in Real Application Clusters (RAC)
environment, you need to manually create the table
MSC_APPS_INSTANCE_NODES with individual database links using sql. This
table holds individual database links between the APS instance and each individual
Real Application Clusters (RAC) node at the source instance. Load balancing is
supported on the source only.
The table structure for MSC_APPS_INSTANCE_NODES is:

Field Name Null? Type

INSTANCE_ID NOT NULL NUMBER

NODE_ID NOT NULL NUMBER

M2A_DBLINK - VARCHAR2(128)

LAST_UPDATE_DATE - DATE

LATS_UPDATED_BY - NUMBER

CREATION_DATE - DATE

CREATED_BY - NUMBER

Setting Up 2-5

Field Name Null? Type

LAST_UPDATE_LOGIN - NUMBER

3. Run Create APS Partition Concurrent Program:
Context: You need to perform this step on the instance where Oracle Global Order
Promising resides.
Required: Yes
You need to run the Create APS Partitions concurrent program. This step is also
part of the Oracle Advanced Supply Chain Planning system setup. If you have
already performed this step as part of the Oracle Advanced Supply Chain Planning
setup, you do not need to repeat this step.

Note: This step is not needed unless the profile MSC: Share Plan
Partitions is set to No.

4. Run Create Global ATP Flexfields Concurrent Program:
Context: Run this program on the source instance only if you are on Release 10.7 or
Release 11.
Required: Yes
The Create Global ATP Flexfields concurrent program creates new flexfield
segments to hold ATP data at the item, bills of material, routing, and resource
levels.

5. Define Instance:
Context: Set up for each source instance. The setup is performed on the destination
instance.
Required: Yes
Under the Oracle Advanced Supply Chain Planner responsibility, set up the
Instances window.

Note: This Instances windows resides on the destination instance.


Application Instances Window

• Instance Code: This is a user-defined, three character short form for the
instance to be planned.

• Instance Type: The valid values here are Discrete, Process, and Discrete and
Process. This field controls whether discrete manufacturing data or process
manufacturing data or both are collected from the transaction instance to the
destination instance for order promising.

• Version: The Oracle Application version of the transaction instance.

• From Source to APS: This is the database link name that points from the source
instance to the destination instance. Use the database link from the source
instance to the destination instance, defined by the DBA in Step 2.

• From APS to Source: This is the database link name that points from the
destination instance to the source instance. Use the database link from the
destination instance to the source instance defined by the DBA in Step 2.

• Enable Flag: Select this option to enable the collection process.

• GMT Difference: Leave it blank. This field is for future use.

• Assignment Set: Enter the default assignment set for this instance. The
assignment is used to resolve sourcing for order promising inquiries. This is not
mandatory and can also be set in the profile options MRP: ATP Assignment Set
or MSC: ATP Assignment Set. See Appendix A for details. The value in this
field will be used if none of the profiles are defined.

Setting Up 2-7

Note: This step is also part of the Oracle Advanced Supply
Chain Planning system setup. If you have already performed
this step as part of the Oracle Advanced Supply Chain
Planning setup, you do not need to repeat this step.

6. Run Create ATP Partitions Concurrent Program
Context: Run this concurrent program if you are if upgrading from prior 11i release.
Required: Yes.

Functional Setup for ATP Based on Collected Data
The following section explains the functional setup steps for ATP Based on Collected
Data.


ATP Based on Collected Data Setup Flow

ATP Based on Collected Data Setup Flowchart

1. Check ATP item attribute:
Context: You need to perform this step for every item.
Required: Yes
Oracle Global Order Promising uses this flag to determine whether to use the
supply of this item to promise demand. You need to set the Check ATP Flag item
attribute to either:
• Material only: check material availability for this item at this level.

• None: no need to check ATP at this level.

• Material and Resource: not currently supported.

• Resource only: not currently supported.

For details on defining item attributes, see Defining Item Attributes in Oracle
Inventory User's Guide.

2. ATP Rules

Setting Up 2-9

Context: Every ATP-able item must have an ATP Rule assigned. An ATP Rule can
be used for multiple items.
Required: Yes
You need to define an ATP Rule. An ATP Rule indicates the ATP options. Each ATP
Rule is a combination of time fence options, supply sources, and demand sources to
use during the ATP Inquiry.

To define an ATP Rule:
1. Navigate to the Rules section in Inventory setup, and find
Available-To-Promise.

ATP Rules Window

2. Enter a unique name and a description for the ATP Rule.
• Oracle Global Order Promising always performs Backward Consumption,
regardless of the setting.

• Oracle Global Order Promising always performs Forward Consumption,

• Oracle Global Order Promising always performs Accumulation, regardless
of the setting.

3. Past Due Supply and Demand Days fields can be used to limit supply and


demand with past due dates. Enter the number of days to limit the past-due
demand and supply. Or leave blank for the inclusion of all the past due supply
and demand. When calculating the ATP quantity of an item, Oracle Global
Order Promising does not consider any demand or supply source before these
dates.

4. The Infinite Supply Time Fence specifies the end of your ATP horizon. ATP
considers any demand that falls beyond this time fence as available. This is
displayed in the ATP Details window as 10,000,000 available on the horizon
date. There are four options:
• Cumulative total lead time: the total lead time of an assembly plus the
largest adjusted cumulative total lead time of its components.

• Cumulative manufacturing lead time: the manufacturing lead time of an
assembly. It may also include and add to the previous lead time, the largest
adjusted cumulative manufacturing lead time of its components. This only
occurs for ATO items.

• Total lead time: the sum of the pre-processing, processing, and
post-processing lead times of the item.

• User-defined time fence: the lead time that you specify in the Days field.

5. The ATP by Demand Class indicates whether to calculate ATP based on
defined demand classes. Demand classes allow you to segregate scheduled
demand into user-defined groups. If you choose to calculate ATP based on
defined demand classes, then the following Supply Source options are not
available:
• On-hand available

• Inter-org transfers

• Purchase orders

• Internal and supplier requisitions
This is to enable Demand Class ATP.
For details, see: Demand Class ATP, page 3-31.

6. Select the Demand and Supply Sources to use in ATP calculations. When you
use ATP based on the collected data, then supply and demand are specified in
the ATP rules.
The possible supply sources are:

Setting Up 2-11

• Discrete Master Production Schedule (MPS)

• Repetitive MPS

• Discrete Work-In-Process (WIP)

• Repetitive WIP

• Non-standard WIP

• Available QOH

• Internal requisitions

• Vendor requisitions

• Purchase orders

• Intransit shipments

• User-defined supply
You control which sources are selected for consideration for the availability
requests. You use the on-hand available checkbox to choose whether to
include the available on-hand quantity as a source of supply. Typically,
make-to-order and assemble-to-order manufacturing environments do not
use the available on-hand quantity as a source of supply. Oracle Global
Order Promising designates a supply period as beginning on a scheduled
supply date and ending the day before the next scheduled supply date. A
supply period covers several days or be a minimum of one day in duration.
If supply occurs on a non-work day, the ATP calculation considers that
supply as belonging to the next working day. If multiple supply events
occur on the same day, the ATP process sums the supplies.
The possible demand sources are:

• Sales orders

• Internal orders

• Discrete WIP demand

• Repetitive WIP demand

7. Save your work.


Example
The following example explains how Oracle Global Order Promising performs
Backward Consumption, Forward Consumption, and Accumulation when
calculating what is available-to-promise.
Assume supply and existing demand as follows:

Day 1 Day 2 Day 3 Day 4

Supply 20 10 20 20

Demand 0 -35 0 -25

1. Step 1: Calculate net availability for each bucket. Net = Supply - Demand.


Supply 20 10 20 20

Demand 0 -35 0 -25

Net 20 -25 20 -5

2. Step 2: For each negative Net, perform backward consumption and forward
consumption until there is no more negative.

3. Step 2.1: On Day 2, Net = -25. Consume backward. There are 20 available on
Day 1 to cover partial shortage. Availability on Day 1 becomes 0.


Supply 20 10 20 20

Demand 0 -35 0 -25

Net 20 -25 20 -5

Backward 0 -5 20 -5

Setting Up 2-13

4. Step 2.2: After consuming the 20 units backward, there are still 5 short on Day
2. Consume forward. There are 20 units on Day 3 to cover the shortage of 5.
Availability on Day 3 becomes 15.


Supply 20 10 20 20

Demand 0 -35 0 -25

Net 20 -25 20 -5

Forward 0 0 15 -5

5. Step 2.3: There is no more shortage on Day 2. On Day 4, there is a shortage of 5.
Consume backward. There are 15 available on Day 3 to cover the shortage.


Supply 20 10 20 20

Demand 0 -35 0 -25

Net 20 -25 20 -5

Backward 0 0 10 0

6. Step 3: Accumulate the above result starting from Day 1.


Supply 20 10 20 20

Demand 0 -35 0 -25

Net 20 -25 20 -5

Cum 0 0 10 10


The cumulative quantity on each day is the quantity available to promise for
that day.

3. Profile INV: Capable to Promise
Required: Yes
When Oracle Global Order Promising is deployed without Oracle Advanced
Supply Chain Planning, ATP is based on collected, transactional data. You set this
profile to ATP Based on Collected Data.

4. MSC: Enable ATP Summary Mode Profile
Required: Optional
Oracle Global Order Promising response times can be improved by means of a
summary approach that stores summary supply and demand information.
Set this profile to Yes to use summary approach. You may only set this profile to
Yes when Oracle Global Order Promising is on the same instance as other ERP
application.
The summary process is accomplished through a concurrent program that is
automatically launched through Data Collection. For a detailed explanation on ATP
summary approach, see: Improved ATP Performance, page 5-43.

5. Transit Lead Time
Context: Ongoing maintenance.
Required: Optional
If there is transit lead time between your shipping warehouse and customer, you
need to define the lead time for each shipping method using the Transit Times form
in Oracle Shipping. You define shipping network from most specific to least specific
at the following levels:
• Warehouse location to an internal location associated with a customer site.

• Warehouse location to a region.

• Warehouse location to a user-defined geographic area called zone.

Setting Up 2-15

Transit Times Window

Per a given shipping method on an ATP request, Oracle Global Order Promising
searches for the shipping method in the above three levels from the most specific to
the least specific. If it finds the shipping method in a particular level, it use the lead
time associated with the shipping method to calculate the scheduled arrival date for
an order. If the shipping method is not specified at any level, Oracle Global Order
Promising uses the default shipping method and its lead time in any level you
define from the most specific to the least specific.
For example, you define shipping lane from your shipping organization to a
specific customer location with shipping method of GROUND that has a lead time
of 3 days. You also define a shipping lane from your shipping organization to a
region, where the previous customer resides. This lane has GROUND as a valid
shipping method, and a lead time of 2 days. On a sales order to this customer using
the GROUND shipping method, Oracle Global Order Promising uses 3 days for the
transit lead time.
Before you set up transit times between the locations, you need to have set up
shipping methods and a default shipping location as the shipping organization.
Optionally, you can set up an internal location and its association with the
customers ship-to address, regions and zones.

Note: In the Transit Time window, you can setup region-to-region
lead time for a ship method. However, Global Order Promising
would only consider location-to-region transit lead time for a ship
method to account for the transit lead time between shipping
organization and the customer's location.


For detailed setup instructions on Regions, Zones, and Transit Times, see: Regions
and Zones in Oracle Shipping Execution User's Guide.

6. Single-Level Supply Chain ATP
Context: Perform this step when you want to use Single-Level Supply Chain ATP.
Required: Function specific for Single-Level Supply Chain ATP.
When there are multiple shipping organizations to fulfill customer orders, Oracle
Global Order Promising recommends the desired shipping organization based on
sourcing rules you define.
For detailed instructions, see: Single-Level Supply Chain ATP, page 3-2.

7. Configuration ATP
Context: You perform this step when you want to use Configuration ATP.
Required: Function specific for Configuration ATP.
Oracle Global Order Promising enables you to promise orders for those items used
in Configure-To-Order environments.
For detailed instructions, see: Configuration ATP, page 3-8.

8. Product Family ATP
Context: You perform this step when you want to use Product Family ATP.
Required: Function specific for Product Family ATP.
Oracle Global Order Promising enables you to promise orders at the aggregate level
based on product family item supply.
For detailed instructions, see: Product Family ATP, page 3-28.

9. Demand Class ATP
Context: You perform this step when you want to use Demand Class ATP.
Required: Function specific for Demand Class ATP.
Oracle Global Order Promising lets you promise orders for a specific demand class
based on a predetermined supply statement for the same demand class.
For detailed instructions, see: Demand Class ATP, page 3-31.

10. Audit Statement Report

Context: You perform this step when you want to check for errors.
Required: Optional, but strongly recommended.
The Audit Statement Report concurrent program checks for common data setup
errors that can lead to collection or plan failures, or incorrect ATP Results. You
should run this program to validate the ATP setup before you initiate an ATP

Setting Up 2-17

Inquiry.
You may run the report for any of the following report areas:
• Collections Setup: typically you choose this option when there are problems in
Collections that you want to diagnose.

• ATP Data Setup: choose this option to report on ATP data setup.

You can control the level of detail of the resulting audit report. The supported levels
of detail are:
• Summary.

• Detailed - Errors Only.

• Detailed - Errors and Warnings.

• Detailed - Complete: provides a complete listing of errors and warnings along
with properly executed data setup.

11. Data Collection

Context: Ongoing.
Required: Yes
Data Collection is a process that pulls data from source instances into an area called
the Operational Data Store (ODS) in Oracle Global Order Promising. Oracle Global
Order Promising uses the data in ODS for order promising. When there is a change
with the source data, you need to run collections to bring the changes into the ODS
so that the ATP result reflects the changes. Source data includes items, ATP Rules,
on-hand, WIP jobs, and purchase orders.
To run data collection without Oracle Advanced Supply Chain Planning, sign on
using the Oracle Order Management responsibility, and select ATP Data Collection.
Currently, the ATP Data Collection concurrent program only contains the following
parameters:
• Instance: the source instance for data collection.

• Number of Workers: number of processes that simultaneously pull transaction
data.

• Timeout: number of minutes before the collection errors out if it has not
finished.

• Collection Type: complete Refresh or Net Change Refresh. Note that Net
Change Refresh is faster.


• Sales Orders: complete Refresh or Net Change Refresh.

The following table describes the data that ATP Data Collection collects. It also
indicates which data entity is supported by the Net Change Refresh mode. When
you create a new data entity or update an existing data entity that is not supported
by Net Change Refresh, you need to run Compete Refresh to obtain the new
information.

Data Entity Supported by Net Change Refresh

ATP Rules No

Calendars No

Demand Class No

Items Yes

Master Production Schedule Yes*

On Hand Yes

Purchase Requisitions / Orders Yes

Sales Orders Yes

Sourcing Rules No

Subinventories No

Trading Partners (Customers) No

Units of Measure No

Work-In-Process Yes

Functional Setup for ATP Based on Planning Output
The following section explains the functional setup steps for using Oracle Global Order
Promising with Oracle Advanced Supply Chain Planning. It is also referred to as ATP
Based on Planning Output.

Setting Up 2-19

ATP Based on Planning Output Setup Flow

ATP Based on Planning Output Setup Flowchart

1. Check ATP and Component ATP item attributes
Context: You need to perform this step for every item.
Required: Yes
You can set the Check ATP item attribute to:
• Material only: check material availability for this item at this level. For a
standard item for which you want to check availability, select this value.


• Resource only: not currently supported.

• Material and Resource: not currently supported.


You can set the Component ATP item attribute to:
• Material only: check availability of the components in the bill for this item. If
the item is sourced from a supplier, then check supplier capacity.

• Resource only: check availability of the resources required to assemble this
item.

• Material and Resource: check availability of both materials and resources
required to assembly this item.

• None: no need to check ATP for this item at the component level.

See: Multi-Level Supply Chain ATP, page 4-2 for an example of the item attribute
setting.

2. ATP Rule
Context: Every ATP-able item must have an ATP Rule assigned. An ATP Rule can
be used for multiple items.
Required: Optional
When Oracle Global Order Promising is based on Oracle Advanced Supply Chain
Planning output, you only need to define the infinite supply time fence option in an
ATP Rule.
If you do not associate an ATP Rule to an ATP-able item, Oracle Global Order
Promising assumes that the infinite time fence is equal to the planning horizon.
You need to setup the ATP Rule for an ATPable resource either at resource or org
level.

To define an ATP Rule:
Navigate to the Inventory Setup, and find Available-To-Promise Rules.

Setting Up 2-21

ATP Rules Window

1. Enter a unique name and a description for the ATP Rule.
• Oracle Global Order Promising always performs Backward Consumption,
• Oracle Global Order Promising always performs Forward
Consumption, regardless of the setting.

• Oracle Global Order Promising always performs Accumulation,

2. Oracle Global Order Promising honors all the past due supply and demand that
are honored by the Oracle Advanced Supply Chain Planning plan. You do not
need to specify any value here.

3. Infinite Supply Time Fence: this time fence specifies the end of your ATP
horizon. ATP considers any demand that falls beyond this time fence as
available. This is displayed in the ATP Details window as 10,000,000 available
on the horizon date. If you do not specify a value, Oracle Global Order
Promising uses the plan horizon as the infinite time fence. There are four
options:
• Cumulative total lead time: the total lead time of an assembly plus the
largest adjusted cumulative total lead time of its components.


• Cumulative manufacturing lead time: the manufacturing lead time of an
assembly. It may also include and add to the previous lead time, the largest
adjusted cumulative manufacturing lead time of its components. This only
occurs for ATO items.

• Total lead time: the sum of the pre-processing, processing, and
post-processing lead times of the item.

• User-defined time fence: the lead time that you specify in the Days field.

4. ATP by Demand Class: Indicate whether to calculate ATP based on defined
demand classes. Demand classes allow you to segregate scheduled demand into
user-defined groups. If you choose to calculate ATP based on defined demand
classes, then the following Supply Source options are not available:
• On-hand available

• Inter-org transfers

• Purchase orders

• Internal and supplier requisitions

This is to enable Demand Class ATP.
For Demand and Supply Sources: when you use ATP based on the planning
output, Oracle Global Order Promising honors all the supply and demand in
the Oracle Advanced Supply Chain Planning plan. You do not need to make
any selection here.

5. Save your work.

Example
The following example explains how Oracle Global Order Promising performs
Backward Consumption, Forward Consumption, and Accumulation when
calculating what is available-to-promise.
Assume supply and demand as follows:


Supply 20 10 20 20

Demand 0 -35 0 -25

Setting Up 2-23

Step 1: Calculate net availability for each bucket. Net = Supply - Demand.


Supply 20 10 20 20

Demand 0 -35 0 -25

Net 20 -25 20 -5

Step 2: For each negative Net, perform backward consumption and forward
consumption until there is no more negative.
Step 2.1: On Day 2, Net = -25. Consume backward. There are 20 available on Day 1
to cover partial shortage. Availability on Day 1 becomes 0.


Supply 20 10 20 20

Demand 0 -35 0 -25

Net 20 -25 20 -5

Backward 0 -5 20 -5

Step 2.2: After consuming the 20 units backward, there are still 5 short on Day 2.
Consume forward. There are 20 units on Day 3 to cover the shortage of 5.


Supply 20 10 20 20

Demand 0 -35 0 -25

Net 20 -25 20 -5

Forward 0 0 15 -5

Step 2.3: There is no more shortage on Day 2. On Day 4, there is a shortage of 5.


Consume backward. There are 15 available on Day 3 to cover the shortage.


Supply 20 10 20 20

Demand 0 -35 0 -25

Net 20 -25 20 -5

Backward 0 0 10 0

Step 3: Accumulate the above result starting from Day 1.


Supply 20 10 20 20

Demand 0 -35 0 -25

Net 20 -25 20 -5

Cum 0 0 10 10

The cumulative quantity on each day is the quantity available to promise for that
day.

3. Profile INV: Capable to Promise
Context: You need to perform this step on the source and destination instances.
Required: Yes
Set this profile to ATP/CTP Based on Planning Data on both the source and
destination instances.

4. Profile MSC: Enable ATP Summary Mode
Context: You need to perform this step only once on the destination instance.
Required: Optional
Oracle Global Order Promising response times improve with a summary approach
that stores summary supply and demand information. Set this profile to Yes to use
the summary approach.

Setting Up 2-25

For a detailed explanation on ATP Summary approach, see: Improved ATP
Performance Based on Summarized Data, page 5-43.

5. Transit Lead Time
Context: Ongoing maintenance.
Required: Optional
If there is transit lead time between your shipping warehouse and customer, you
need to define the lead time for each shipping method using the Transit Times form
in Oracle Shipping. You define shipping lead times from the most specific to the
least specific at the following levels:
• Warehouse location to an internal location associated with a customer site

• Warehouse location to a region

• Warehouse location to a geographic area called zone

If there is a transit lead time between the supplier and the receiving warehouse, you
need to define the lead time for each shipping method at the following levels:
• Region to warehouse location

• Zone to warehouse location


Transit Times Window

Given a shipping method on an ATP request, Oracle Global Order Promising will
search for the shipping method in the above 3 levels from most specific to least
specific. If it finds the shipping method in a particular level, it will use the lead time
associated with the shipping method to calculate the scheduled arrival date for an
order. If the specified shipping method is not specified at any level, Oracle Global
Order Promising will use the default shipping method and its lead time in any level
you define from most specific to least specific.
For example, you define shipping lane from your shipping organization to a
specific customer location with shipping method of GROUND that has a lead time
of 3 days. You also define a shipping lane from your shipping organization to a
region where the previous customer resides. This lane has GROUND as a valid
shipping method, and a lead time of 2 days. On a sales order to this customer using
GROUND shipping method, Oracle Global Order Promising uses 3 days for the
transit lead time.
Before you set up transit times between the locations, you need to have set up
shipping methods and a default shipping location as the shipping organization.
Optionally, you can set up an internal location and its association with the
customers ship-to address, regions and zones.
For detailed instructions, see Transit Times in Oracle Shipping Execution User's Guide.

6. Multi-Level Supply Chain ATP
Context: You need to perform this step for Multi-Level Supply Chain ATP.
Required: Optional
With Oracle Global Order Promising, you can promise demand based on the

Setting Up 2-27

sourcing rule you define for any number of shipping organizations. If there is not
sufficient supply, Oracle Global Order Promising explodes the supply chain bills of
material to find additional component and resource supplies to promise.
For detailed instructions, see: Multi-Level Supply Chain ATP, page 4-2.

7. Configuration ATP
Required: Function specific for Configuration ATP.
Oracle Global Order Promising enables you to promise orders for those items used
in Configure-To-Order environments.
For detailed instructions, see: Configuration ATP, page 3-8.

8. Product Family ATP
Required: Function specific for Product Family ATP.
Oracle Global Order Promising enables you to promise orders at aggregate level
based on product family item supply.
For detailed instructions, see: Product Family ATP, page 3-28.

9. Allocated ATP
Required: Function specific for Allocated ATP.
Oracle Global Order Promising lets you allocate scarce supply to different sales
channels or customers, and promise orders based on allocated supply.
For detailed instructions, see: Allocated ATP, page 4-105.

Note: The Allocated ATP functionality includes allocation by
demand priority. This functionality is a preferred alternative to
using the Demand Class ATP functionality, which is also available
for ATP Based on Planning Output.

10. Audit Statement Report

Required: Optional, but strongly recommended
The Audit Statement Report concurrent program checks for common data setup
errors that may lead to collection or plan failures, or incorrect ATP results. You run
this program to validate the ATP setup before you initiate an ATP inquiry.
You can run the report for any of the following report areas:
• Collections Setup: typically you choose this option when there are problems in
Collections you want to diagnose.

• ATP Data Setup: choose this option to report on ATP data setup.


You control the level of detail of the resulting audit report. The supported levels of
detail are:
• Summary.

• Detailed - Errors Only.

• Detailed - Errors and Warnings.

• Detailed - Complete: provides a complete listing of errors and warnings along
with properly executed data setups.

11. Run Collections

Context: Ongoing.
Required: Yes
Data Collection is a process that pulls data from source instances into an area called
the Operational Data Store (ODS) in Oracle Global Order Promising and Oracle
Advanced Supply Chain Planning. An ASCP plan is run based on the collected
data. The output of an ASCP plan is used for order promising. It is typical that you
run Collections before you rerun your ASCP plan.
Also, you need to be logged on using the Advanced Supply Chain Planner
responsibility.
For more information on data collection, see Running Collections in Oracle Advanced
Planning and Scheduling Implementation and User's Guide.

12. ASCP Plan

Context: Perform this step as needed.
Required: Yes
You need to identify a particular plan for ATP by checking the Check ATP flag in
the plan definition window in Oracle Advanced Supply Chain Planning.
For detailed instructions, see, Setting Plan Options in Oracle Advanced Planning and
Scheduling Implementation and User's Guide.

13. Run Plan

Context: Ongoing.
Required: Yes

Setting Up 2-29

3
ATP Based on Collected Data

• Basic ATP
• Single-Level Supply Chain ATP
• Improved ATP Performance

Basic ATP
Basic ATP allows you to perform an availability check based on a statement of current
and planned material supply against a given organization. You perform ATP checks by
specifying the item, the need by date, and the ship-from. Results describing the need by
date quantity and the fulfillment date are returned to you.

Business Application
Basic ATP allows you to receive detailed information on whether your availability
check request can be met and on what date the request can be fulfilled. Based on
statements of current and planned material supply, Basic ATP determines the
availability of items.
You perform a Basic ATP check when you only have one ship-from location in your
company, or when you want to check availability in one inventory location.

Setup
After you perform the mandatory and optional setup steps explained in the Setting Up,
page 2-1 chapter, then you may perform Basic ATP.

ATP Based on Collected Data 3-1

When you initiate ATP from another application such as Oracle Order Management,
you need to specify a shipping organization. The calling application may have its own
way to default a shipping organization. When Oracle Global Order Promising is called
with a specific organization, it performs Basic ATP. Otherwise, it attempts to perform
Single-Level Supply Chain ATP, which requires additional setup.
Refer to the calling application's user guide for further details on shipping organization
specifications.

ATP Logic

ATP Logic in a Single Organization
1. If Check ATP is set to None, then there is no ATP check.
If ATP item attribute is Material Only, then the system checks ATP for the item on
the request date. If there is availability, then you are done. Otherwise, go to step 2.

2. ATP fails to satisfy this request. From the sysdate, ATP performs forward
scheduling for this request. ATP finds the earliest date that you can meet the
shortage based on the supply in the ATP Rule. This is the ATP date.

3. If the ATP Date is less than or equal to the Latest Acceptable Date, Oracle Global
Order Promising returns a success. Otherwise, it returns a failure.

Note: The Latest Acceptable Date is a date beyond the request date
that the customer will accept the order. This date is determined by
any calling application, and is passed to Oracle Global Order
Promising.

ATP Result
Oracle Global Order Promising returns very detailed information and presents the data
in the ATP Details window. However, the calling application may decide to only show
a subset of the information. For example, Oracle Order Management shows some of the
ATP results such as Warehouse, Request Date Quantity, Available Date, and Error
Message in its Availability window. It provides an ATP Details selection for you to drill
down to the ATP Details window, if you want detailed information.
For details on the ATP Details window, see: ATP Inquiry, page 6-1.

Single-Level Supply Chain ATP
Single-Level Supply Chain ATP enables you to perform availability checks based on
current and planned supply across multiple supply organizations. You rank the supply
organizations so that ATP checks for availability in the order you want. Single-Level


Supply Chain ATP automatically finds the best supply organization for your request.
Oracle Global Order Promising also drills down to look at the availability at every
supply organization.


ATP for Multiple Supply Locations
If you have multiple distribution centers in your enterprise, Oracle Global Order
Promising determines the best location to fulfill a customer request. Alternatively, you
can check ATP for any of the possible supply locations, drill down to ATP details, and
select the desired location.
Any environment where multiple supply locations are used to fulfill order demand can
benefit from this feature. As you utilize available inventory from other locations, you
can successfully meet customers requirement and thus increase your company's overall
order fill rate by utilizing inventories that might otherwise be in excess.
For example, a company has three stores throughout the United States. When a
customer inquires about the availability of a particular product A, the company wants
to first check the preferred store (Org1). The product may not be available at the
preferred store. The company then wants to check the other stores (Org2 and Org3) to
find the store that can meet the customer's requirement. Single-Level Supply Chain ATP
helps the company to accomplish this goal. This is shown in the following diagram:

Single-Level Supply Chain ATP

Setup
Perform the mandatory and optional setup steps explained in the Setting Up, page 2-1
chapter. The following are the additional setup steps.

Sourcing Rule
Sourcing Rules are used to describe all of the possible shipping warehouses. The
sourcing rule priority determines the order that Oracle Global Order Promising uses to
search for supply. The receiving party can be a customer or an internal organization.
You must use a Sourcing Rule that is non-organization specific to define the movement
of goods from shipping organizations to customers. The type of the sourcing rule must


be Transfer From.

Note: Oracle Global Order Promising currently does not support
sourcing a customer sales order from a supplier, directly, in a Drop
Ship scenario.

For detailed setup instructions, see Sourcing Rules and Bills of Distribution in Oracle
Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide.

Assignment Set
Once you define your sourcing rules, you assign them to particular items, and / or
organizations and customers. These assignments are grouped together in assignment
sets.
In an assignment set, you assign your sourcing rules at different levels, as follows:
• A single item in an organization / for a customer site

• A category of items in an organization / for a customer site

• An item across all organizations / customer sites

• A category of items across all organizations / customer sites

• All items in an organization / for a customer site

• All organizations (global) / customer sites

You create an assignment set at different levels based on your needs. If the receiving
party is a customer, then assign the sourcing rule to this customer and its site. If you
want a sourcing rule to be applicable to any customer or any items, then you assign the
sourcing rule to global.

Important: Category-level assignments are supported only if the
category set indicated by MRP: Sourcing Rule Category Set and MSC:
Sourcing Rule Category Set is controlled at the Master level and not at
the Organization level.

For detailed setup instructions, see Sourcing Rules and Bills of Distribution in Oracle
Master Scheduling/MRP and Oracle Supply Chain Planning User Guide.

Profile MRP: ATP Assignment Set
When you perform Single-Level Supply Chain ATP from the source instance, this
profile determines the assignment set ATP uses to determine the shipping organization
for the receiving organization or customer. This profile should point to the assignment
set discussed above and be set up at the source instance.


Profile MSC: ATP Assignment Set
This profile points to an assignment set that contains the Sourcing Rule, which defines
the movement of goods from shipping organizations to customers. This profile is set up
at the destination instance. The profile MRP: ATP Assignment Set, defined at the source
instance, takes precedence over the profile MSC: ATP Assignment Set.

ATP Logic
An ATP request is processed by the system in the following order:
1. If the ranks are different, the organization with the highest rank is selected first. If
the ranks are the same, the source that has the higher allocation percentage is
selected first. If the allocation percentages are the same, the source is selected
arbitrarily.

2. Check the availability of the item in the organization.
1. If there is enough supply, then the ATP Date equals request date and the ATP
status equals success.

2. If there is not enough supply, forward schedule to find the earliest date that the
shortage can be met. The ATP Date equals the earliest available date. If the date
is less than or equal to the Latest Acceptable Date, then the ATP status equals
success. Otherwise, the ATP status equals failure.

3. If the ATP status equals success, then return the ATP Date with a success status.
Otherwise, go to step 1 for the next ranked organization.

4. If there is no more organizations, then return the ATP Date and ATP status from the
highest ranked organization.

• The Latest Acceptable Date is determined by the calling
application.

• A request is only promised against one source.

ATP Result
When the ATP check is performed without a shipping organization, Oracle Global
Order Promising automatically performs Single-Level Supply Chain ATP based on the
sourcing rules defined in the assignment set pointed to by the profile MRP: ATP
Assignment Set. It returns a shipping warehouse based on the logic described in ATP
Logic, quantity available on request date, the available date, and other information. The
detail information can be obtained from the ATP Details window.


From Oracle Order Management or Oracle Global Order Promising ATP Inquiry, users
can select Global Availability to view availability information in each of the shipping
organization.
For details about viewing availability information, see: ATP Inquiry, page 6-1.

Example
The following example guides you through some of the setup steps and shows you the
Single-Level Supply Chain ATP result.
You have two supply organizations: M1 and M2. M1 is the preferred warehouse. For
end item A, it is Make at M1, but it is a Buy From supplier S1 at M2. This sourcing
strategy is applicable to all customers.
You ship the product to customers using either the standard 3 day delivery or 1 day
express.
For any demand, you want ATP to look at the two supply warehouses based on the
current and planned supply.

Sourcing Rule
You set up a sourcing rule as shown in the following table:
• Note that you must check the All Org field in the Define Sourcing Rule form. For
this example, the sourcing rule name is SR-A:

Type Org/Supp Percent Rank

Transfer M1 100% 1

Transfer M2 100% 2

This is a non-organization specific sourcing rule.

Assignment Set
In the assignment set, you make an item level assignment by assigning sourcing rule
SR-A to item A, as shown in the following table:

Assigned To (Type) Item / Sourcing Rule

Item A


Assigned To (Type) Item / Sourcing Rule

SR SR-A

Transit Times
You can set up different shipping methods and transit lead times from the shipping
organization to a customer.
The following table shows the transit lead times from the shipping location to the
region of the United States:

From To Shipping Method Lead Time

M1-ShipLoc USA (region) Express 1 day

M1-ShipLoc USA (region) Standard 3 days

M2-ShipLoc USA (region) Express 1 day

M2-ShipLoc USA (region) Standard 3 days

This profile points to the assignment set defined above.
The cumulative ATP quantity for each of the warehouses is as shown in the following
table:

Org Day 10 Day 11 Day 12 Day 13

M1 80 85 90 100

M2 90 95 100 105

The following list shows the ATP request information:
• Order Quantity = 100

• Request Arrival Date = Day 11

• Customer = ABC


• Address = 1234 Evergreen Lane, California, CA 96666, USA

• Shipping Method = Express

• Latest Schedule Limit = 2 days

Oracle Global Order Promising performs the following:
1. Single-Level Supply Chain ATP first looks at M1. Since the shipping lead time is 1
day, the quantity must be available on Day 10. However, it is not available.

2. Because the latest schedule limit for this customer is 2 days, Single-Level Supply
Chain ATP looks forward to Day 11 and Day 12. M1 is still not available.

3. Single-Level Supply Chain ATP now looks at M2. It is available on Date 12.

4. Based on this search, Single-Level Supply Chain ATP returns M2 as the warehouse
for the request with the availability date of Day 12.

Note: You must provide a shipping warehouse for the ATO Model,
PTO Model, and ATO Item. Currently, Oracle Global Order
Promising does not recommend sourcing for these items.

Configuration ATP
A Configure-To-Order (CTO) environment is one where the product or service is
assembled or kitted on receipt of the sales order. This section provides a detailed
explanation of order promising on items used in a configure-to-order environment.
Oracle Global Order Promising supports a Configure-To-Order environment. You
designate the optional and included items for the ATP Check. This provides an accurate
availability date for the end configuration.

In a configure-to-order environment, it is not possible or practical to project and plan
for every possible configuration. Inventory is planned and held at component level. To
accurately promise a customer order, you need to check availability based on the actual
options selected. Oracle Global Order Promising lets you promise a sales order for
configuration based on the selected options.

Items Used in Configure-To-Order Environment
The following items may be used in a configure-to-order environment:
• ATO Model


• PTO Model

• ATO Item

• Kit (PTO Item)

For detailed feature descriptions, see Oracle Configure-To-Order Implementation Guide.

Examples
ATO Model

Level Item BOM Item Mutually Optional Assemble-To
Type Exclusive -Order

0 Laptop X11 ATO Model - - Yes

1 - Base System Standard No No No

2 - - Board Standard No No No

2 - - Network Card Standard No No No

2 - - Graphics Card Standard No No No

1 - Processor Class Option Class Yes No Yes

2 - - Mobile Standard No Yes No
Pentium®4 2.2
GHz

Pentium®4 2.0
GHz

Pentium®4 1.8
GHz

Pentium®4 1.7
GHz

1 - Memory Class Option Class Yes No Yes



2 - - 256 MB Standard No Yes No



1 - Monitor Class Option Class Yes No Yes

2 - - 17in Flat Screen Standard No Yes No


1 - Modular Drive Option Class No No Yes
Class

2 - - 24X CD-Rom Standard N/A Yes No

2 - - 8X Max DVD Standard N/A Yes No
Rom

2 - - 24X CD-RW Standard N/A Yes No

2 - - 24X Standard N/A Yes No
CD-RW/DVD
Combo

PTO Model

Level Item BOM Item Mutually Optional Pick
Type Exclusive Components

0 Laptop X11 PTO Model - - Yes
Deluxe

1 - Laptop X11 ATO Model No No No

1 - External Option Class No Yes No
Mouse



2 - - Logitech Standard No Yes No
Optical Mouse

2 - - COMPAQ Standard No Yes No
Mouse

1 - Wireless Option Class No Yes Yes
Networking
Card

2 - - External Standard No Yes No
TrueMobile
1150 PC Card

2 - - Internal Standard No Yes No
TrueMobile
1150 miniPCI
Card

1 - Laptop Case Standard No No No

1 - External Option Class No Yes Yes
Speaker

2 - - Premium Standard No No No
Speaker

2 - - Speaker Standard No No No
Manual

ATO Item

Level Item BOM Item Mutually Optional Assemble-To-
Type Exclusive Order

0 Laptop X11-1 Standard - - Yes

1 - Base System Standard N/A No No


Level Item BOM Item Mutually Optional Assemble-To-
Type Exclusive Order

1 - Mobile Standard N/A No No
Pentium®4 2.2
GHz

1 - 512 MB Standard N/A No No

1 - 17in Flat Screen Standard N/A No No

1 - 24X Standard N/A No No
CD-RW/DVD
Combo

Kit


0 External Standard No - Yes
Speaker

1 - Premium Standard No No No
Speaker

1 - Speaker Standard No No No
Manual

Configuration ATP Based on Collected Data
Oracle Global Order Promising lets you check availability for an ATO Model, PTO
Model, ATO Item, and Kit. The following section explains the setup needed to perform
availability checks for such items, as well as the data that is passed from front-end
applications to Oracle Global Order Promising.

ATO Model
Front-end applications such as Oracle Order Management and Oracle Configurator are
used to configure an ATO Model. The ATO Model, selected option classes and selected
option items are passed to Oracle Global Order Promising for ATP check.


Setup

ATP Item Attributes and Component ATP Flag
To perform availability and lead time check for an ATO Model and its components:
When the availability for the ATO Model depends on the availability of the included
items and optional items, you should set up the Check ATP item attribute according to
the following table:

Item Type Check ATP Component ATP

ATO Model None Material

Option Class None Material

Mandatory Component Material or None None

Optional Item Material or None None

Oracle Global Order Promising checks the availability of the included and selected
optional items on a date that is offset from the ATO Model request date by:
Fixed Lead Time + Request Quantity * Variable Lead Time
of the ATO Model. Oracle Global Order Promising returns a Ship Date that is either the
request date or a later date, if any ATP-able items are not available.
To perform lead time check for an ATO Model:
Setup the ATP Flag and the ATP Component Flag as following:

Item Type ATP Flag ATP Component Flag

ATO Model None None

Set the profile MSC: ATP Enforces Lead Time for ATO Models to Yes.

Note: If you set both the ATP Flag and ATP Component Flag to None,
and the profile MSC: ATP Enforces Lead Time for ATO Models to No,
Oracle Global Order Promising does not perform the availability and
lead time checks for the ATO Model.


• If you have Multi-Level or Multi-Org ATO Models, you need to
deploy Oracle Advance Supply Chain Planning to accurately
promise such orders through the use of the Multi-Level ATP or
Multi-Level CTP functionalities and sourcing capabilities. For
configuration details for ATP based on planning output, see:
Configuration ATP, page 3-8.

• An ATO Model is like a product family. Therefore, it is
recommended to not define an ATO Model under a product family.

ATP Logic

Match to Existing Configuration
Oracle Global Order Promising does not attempt to match a new sales order to an
existing configuration. Oracle Global Order Promising is based on the availability of the
options and mandatory items. Once the order is scheduled and booked, you use the
Match and Reserve capability from Oracle Order Management to match to an existing
configuration with supply.

Note: If you implement Oracle Advanced Supply Chain Planning and
perform ATP based on planning out, Oracle Global Order Promising
will match to existing configuration for a new sales order and net
supply and demand based on the configuration item supply and
demand. For details, see Match to Existing Configuration, page 4-40.

Reschedule Order
When a sales order line is rescheduled, Oracle Global Order Promising first
unschedules the original order lines, and then reschedules the order based on the
availability of the ATPable optional item and standard mandatory item availability. If
there is a supply of the configuration item and is available earlier, Oracle Global Order
Promising will not use it.

Option Specific Sourcing
A model-option combination may not always be produced at a specific source. There
can be restrictions associated with specific options like equipment limitations, and
engineering qualifications. If a model requires a specific option, you can predefine that
it will be sourced from a reduced set of sources. Oracle Configure-To-Order enables you
to specify a sub-set of the model sources as valid sources for a model-option
combination. Oracle Global Order Promising honors this setup and schedules a date for
a configuration, based upon the sub-set of the model sourcing that is valid for the
specific configuration. The configuration bill of material (BOM) is created in the


reduced set of sources only.

Note: Oracle Configure to Order may create configuration item in an
org that is not on the list of valid orgs based on the Option Specific
Sourcing rule. When you perform an ATP inquiry for such item using
applications such as Oracle Order Management, Oracle Configure to
Order validates the item-org combination and flags such error.
However, this validation is not available on the destination instance.
You need to provide a valid organization while performing ATP
inquiry for such item.
For more details on configuration item creation, see Oracle Configure to
Order Implementation Guide.

For details on how option specific sourcing is used, see Example, page 3-17.

To define option specific sourcing:
1. In the Navigator, select Advanced Planning > Source Instance Setups > Sourcing >
CTO Option Specific Sourcing List.
The Option Specific Sourcing List window appears.

Option Specific Sourcing List Window

2. Define valid sources for each model-option configuration.

Oracle Global Order Promising uses the option specific sources list to restrict available
sources when promising the ATO Model.
• Option specific sources on a child model restrict its parent model's available


sources.

• Oracle Configure-to-Order performs the following:

• The configured item's bill of material (BOM) and routing are created only at the
subset of organizations required by the option specific sources setup.

• New sourcing rules and assignments are created for the option specific sources
model and its parent models.

For details on how to setup configuration creation based on option specific sourcing, see
Oracle Configure To Order User Guide.

To set the item attribute to Based to Model:
1. In the Navigator, select Items > Organizations > Master Item.
The Master Items window appears.

2. Set Create Configured Item, BOM to Based on Model.

For details on setting item attributes, see Oracle Configure-To-Order User Guide.

Global Availability
If an ATO Model can be sourced from multiple shipping warehouses, Oracle Global
Order Promising recommends a shipping warehouse based on the availability in each
of the warehouses.
For details about setting up sourcing rules for shipping warehouses, see: Single-Level
Supply Chain ATP, page 3-2 or, Multi-Level Supply Chain ATP, page 4-2.

Infinite Time Fence
Oracle Global Order Promising honors the infinite time fence for an ATO Model. The
Model must have either the Check ATP attribute or Component ATP attribute enabled
or both the attributes enabled.

Consistent Interface to All Calling Applications
Any application that attempts to interface with Oracle Global Order Promising for
Models (ATO or PTO) needs to send the Model and selected options to Oracle Global
Order Promising. Oracle Global Order Promising does the following:
• For ATO Model, it will derive the standard mandatory components

• For PTO Model, the calling application has the choice of either having Oracle
Global Order Promising derive the included items or pass the included items to


Oracle Global Order Promising.

Examples
ATO Model
Consider the ATO Model from Example 1. Let us say for a particular order, some
options are selected. The ATP item attributes for these items are shown below:

Level Item Check ATP Component ATP

0 Laptop X11 - Material Only

1 - Base System Material Material Only

1 - Processor Class - Material Only

2 - - Mobile Pentium®4 Material None
2.2 GHz

1 - Memory Class - Material Only

2 - - 256 MB - None

1 - Monitor Class - Material Only

2 - - 19in Flat Screen - None

1 - Modular Drive - Material Only
Class

2 - - 24X CD-RW/ DVD Material None
Combo

The cumulative availability picture for the items that have the Check ATP attribute set
is described as follows:

Item Day 1 Day 2 Day 3

Base System 0 10 10

Mobile Pentium®4 2.2 GHz 10 20 30



24X CD-RW/DVD Combo 0 10 10

Lead time setup for Laptop X11:
• Fixed lead time = 0

• Variable lead time = 0.05 day

A sales order for the above configuration for quantity of 10 on Day 2 can be promised
on Day 3.
An ATP inquiry for the above order will show the following result in the ATP Detail
window:

Item Matched Org Request Ship Date Days Late
Configuration Date Qty

Laptop X11 - SG 0 Day 3 1

Base System - SG 0 Day 3 1

Processor - SG 0 Day 3 0
Class

Mobile - SG 0 Day 3 0
Pentium®4 2.2
GHz

Memory Class - SG 0 Day 3 0

256 MB - SG 0 Day 3 0

Monitor Class - SG 0 Day 3 0

19in Flat - SG 0 Day 3 0
Screen

Modular - SG 0 Day 3 0
CD/DVD
Drive


Item Matched Org Request Ship Date Days Late
Configuration Date Qty

24X - SG 0 Day 3 1
CD-RW/DVD
Combo

The Org field only shows the shipping organization for the top ATO Model.
ATP Pegging for the item Base System shows the following result:
(D) Laptop X11- Org qty 10 on Day 2
(S) Laptop X11- Make Org Qty 10 on Day 3
(D) Base System- Org Qty 10 on Day 1
(S) Base System- ATP Org Qty 0 on Day 1
(S) Base System- ATP Org Qty 10 on Day 2
(D) Mobile Pentium 4.22 GHZ - Org Qty 10 on Day 1
(S) Mobile Pentium 4.22 GHZ - ATP Org Qty 10 on Day 1
(D) 24X CD-RW/DVD Combo - Org Qty 10 on Day 1
(S) 24X CD-RW/DVD Combo - ATP Org Qty 0 on Day 1
(S) 24X CD-RW/DVD Combo - ATP Org Qty 10 on Day 2
Explanation:
• In pegging, different graphical icons are used for supply and demand. In the above
representation, the icons are represented by (S) and (D) respectively.

• Option classes appear on the same level as its components. They are treated as
phantom items.

• The demand pegging line for the components of an ATO Model reflects the lead
time offset of the Model. The lead time for 10 units of the Model = round (0 + 0.05 *
10) = 1 day.

• The Base System and 24X CD-RW/DVD Combo are not available on Day 1.

• All components are available on Day 2. It takes 1 day to produce the configuration.
Therefore, the configuration is only available on Day 3.

Model 1 has three options: Option 1, Option 2 and Option 3.


Option Specific Sourcing Structure

M1, M2, M3 denote the manufacturing organization. S1 denotes a supplier.
• If an order for Model 1 only has option 1, the valid sources would be M1 and M2.


• If an order for Model 1 only has option 3, the valid sources would be M1 and S1.

• If an order for Model 1 has option 1 and option 2, the only valid source would be
M1.

• If the new item creation attribute is set to Based on Model, the item is created in M1
and the Order Management validation organization.

• The bill of material and routing is created in M1 only.

• New sourcing is created and assigned to the configuration item.

• If no valid source is found based on the options selected and option specific
sourcing setup, Global Order Promising will give an order and will not be able to
schedule the sales order.

PTO Model
A front-end application, such as Oracle Order Management and Oracle Configurator, is
used to configure a Pick-To-Order (PTO) Model. When the PTO Model has Ship Model
Complete checked, Oracle Order Management groups the PTO Model and the selected
option classes with items and optional items into a set for the ATP check. Otherwise,
Oracle Order Management treats each PTO line, including items and selected options,
independently for the availability check.


Setup

ATP Item Attributes
Set the Check ATP item attribute as following:


PTO Model None Material Only

Option Class None Material Only

Included Item Material or None None

Optional Item Material or None None

Examples
PTO Model with Ship Model Complete set to Yes
Let us say for a particular order with a PTO Model, some options are selected. The ATP
item attributes for these items are shown below:

Level Item Check ATP Component ATP Ship Model
Complete

0 Laptop X11 Deluxe - Material Only Yes

1 - Laptop X11 - Material Only -

1 - External Mouse - Material Only -

2 - - Logitech Optical Material None -
Mouse

1 - Laptop Case Material Material Only -

The cumulative availability picture for the items that have the Check ATP item attribute
set is described as follows:



Logitech Optical Mouse 0 0 20

Laptop Case 10 20 30

For the availability of Laptop X11 and its components, see: Example, page 3-21.
A sales order demand of the above configuration for a quantity of 10 with a request
date of Day 2 can be promised on Day 3.
window:

Item Matched Request Date Ship Date Days Late
Configuration Qty

Laptop X11 Deluxe - 10 Day 3 1

Laptop X11 - 0 Day 3 0

External Mouse - 10 Day 3 0

Logitech Optical - 0 Day 3 1
Mouse

Laptop Case - 20 Day 3 0

Explanation:
• Oracle Global Order Promising checks the availability of optional items as well as
included items that are ATPable.

• The Logitech Optical Mouse is not available when the request date = Day 2.

• The PTO Model can be shipped on Day 3.

• The optional items of the ATO model Laptop X11 will show up in the ATP Details
window. They are not illustrated here.

PTO Model with ShIp Model Complete set to No
Same scenario as the previous example, except the PTO Model has Ship Model
Complete set to No. In this case, each individual lines can be shipped on the Ship Date.


window:

Configuration Qty




Mouse


ATO Item
When an order is created in Oracle Order Management for an ATO Item, Oracle Order
Management constructs a set of items to be passed to Oracle Global Order Promising
for availability check based on the ATP item attributes setting.

Setup

ATP Item Attributes
Oracle Global Order Promising supports the following ATP item attributes setting for
an ATO Item:
1. The ATO Item is forecasted and planned. There is a statement of supply for the
ATO Item. Order promising for the ATO Item is based the supply for the ATO Item.
In this case from the order promising perspective, the ATO Item is similar to a
standard item. The significance of the ATO is on the transactional side. You should
only enable Check ATP for the ATO Item.


ATO Item (Standard) Yes None

Components (Standard) None None

Oracle Global Order Promising returns a Ship Date that is either the request date or


a later date if the ATO Item is not available.

2. The ATO Item is created for a commonly ordered configuration. It is not
individually forecasted and planned. Oracle Global Order Promising for the ATO
Item is based on the availability of its immediate components.
You should enable the Component ATP flag for the ATO Item and enable the Check
ATP flag for its key components.

Item Check ATP Component ATP

ATO Item (Standard) No Material

Next level components Material No
(Standard)

Oracle Order Management passes the ATO Item to Oracle Global Order Promising
for the availability check.
Oracle Global Order Promising checks the availability of the components on a date
that is offset from the ATO Item request date by:
Fixed Lead Time + Request Quantity * Variable Lead Time
of the ATO Item. Oracle Global Order Promising returns a Ship Date that is either
the request date or a later date, if any ATP-able items are not available. Under such
setting, Oracle Global Order Promising will not check the availability of the ATO
item.

Examples
ATO Item
Only the ATO Item has ATP Check set to Material.


0 Laptop X11-1 Material None

1 - Base System - -

1 - Mobile Pentium®4 2.2 - -
GHz

1 - 512 MB - -



1 - 17in Flat Screen - -

1 - 24X CD-RW/DVD Combo - -

The cumulative availability picture for the items that have Check ATP item attribute set


Laptop X11-1 0 0 10

An ATP Inquiry for a sales order demand of the ATO Item for a quantity of 10 with a
request date of Day 2 can only be promised on Day 3.
The ATP Details window shows the following result:

Item Request Date Request Date Qty Ship Date

Laptop X11-1 Day 2 0 Day 3

ATO Item
Using the ATO example above, here is another example. The ATP item attribute for the
items are shown below:


Laptop X11-1 - Material

- Base System Material -

- Mobile Pentium®4 2.2 GHz Material -

- 512 MB - -

- 17in Flat Screen - -

- 24X CD-RW/DVD Combo Material -




- Base System 10 20 30

- Mobile Pentium®4 2.2 GHz 10 20 30

- 24X CD-RW/DVD Combo 10 10 10

Laptop X11-1 lead time:


An ATP Inquiry for a sales order demand of the ATO Item for a quantity of 10 with a
request date of Day 2 can be promised on Day 2.


Laptop X11-1 Day 2 10 Day 2

Explanation:
• The availability information on the ATO item line tells you the availability on the
request date in the Request Date Quantity field. If the entire quantity is not
available on the request date, the Ship Date tells you the earliest date that the order
quantity is available.

• Ship Date equals the date the component items are available plus the ATO Item's
lead time. For example, the Base System is available on Day 1. Thus, the Ship Date
equals Day 1 + 1 = Day 2.

Reschedule Order
• When a sales order line of an ATO Item is rescheduled: Oracle Global Order
Promising first unschedules the original order demand. Then it reschedules for the
new demand.

• When the ATO Item has Check ATP enabled and the components do not have
Check ATP enabled: during rescheduling, the original demand is unscheduled first


for the ATO Item. New demand is placed based on the ATO item's availability.

• When the ATO Item has Check ATP set to None and components have Check ATP
set to Material: during rescheduling, the original demand is unscheduled first for
the components. New demand is placed based on the availability of the
components regardless of the availability of the ATO item.

Kit
A Kit, also known as a PTO Item, is a standard item with Pick Component item
attribute checked. When an order is created in Oracle Order Management for a Kit,
Oracle Order Management explodes the next level components of the Kit, groups the
items into a set, and passes the set to Oracle Global Order Promising for availability
check.

Setup

ATP Item Attributes
Set the Check ATP item attribute.
Oracle Global Order Promising supports two types of settings:
1. Check availability for the Kit:

Item Check ATP

PTO Item (Standard) Material

- Next level components (Standard) None

2. Check availability for the components of the Kit:

Item Check ATP

PTO Item (Standard) None

- Next level components (Standard) Material

Oracle Global Order Promising checks the availability for the components on the
request date of the Kit. Oracle Global Order Promising returns a Ship Date that is either
the request date or a later date, if any ATP-able items are not available.


Examples
PTO Item
Using a PTO Item, the ATP item attributes for the items are shown below:

Level Item Check ATP

0 External Speaker -

1 - Premium Speaker Material

1 - Speaker Manual Material



Premium Speaker 0 0 10

Speaker Manual 10 10 10

An ATP Inquiry for a sales order demand of the PTO Item for a quantity of 10 with a


External Speaker Day 2 10 Day 2

Premium Speaker Day 2 0 Day 3

Speaker Manual Day 2 10 Day 2

Product Family ATP
Oracle Manufacturing lets you define product family item as a percentage composition
of member items. If the product family item is set up to perform ATP based on product
family, then when an ATP Inquiry is launched for a member item, the ATP is actually


performed against the product family item.
When you set ATP to be based on collected data, and define setups to perform ATP
based on product family, the product family supply should be present in the source as a
Master Production Schedule (MPS) schedule.

It may not always be possible to forecast the exact demand of the end item. However, it
may be possible to define aggregate requirements and forecast at an aggregate level,
instead of at the item level. This is shown in the following diagram:

Aggregate Product Family Level Forecast

Setup
Once you define product family item and product family item / member item
relationship, you need to perform the following setup to enable ATP based on Product
Family:
1. Check ATP item attribute: needs to be set to Material for product family item in
order to perform Product Family ATP.
You must set the Check ATP flag for all the member items to be Material. Otherwise
incorrect result can occur. This is because the demand and supply for product
family is an aggregation of the demand and supply of the member items.

2. ATP Rule: designate an ATP Rule for a product family item.

ATP Logic
When an item is set to Check ATP at product family level, Oracle Global Order
Promising uses the cumulative availability at the product family level to promise an
order.


To calculate availability at product family level:
1. Obtain a supply picture of product family item per day up to the infinite time fence
of the product family item.

2. Sum the demand from its member items per day up to the infinite time fence of the
product family item.

3. Calculate the net availability for each day.
Net Availability = Supply (step 1) - Demand (step 2).

4. If any buckets have negative quantities, then perform backward and forward
consumption.

5. Cumulate the supply from step 4.

ATP Result
ATP Result is expressed in terms of the requested member item. You see the requested
item in ATP Details window as well as in ATP Pegging.

Example
Product family item, PF1, has two members A and B. The supply demand picture for
these items is described in the following table:

Item Row Type Today (Day Day 2 Day 3 Day 4
1)

PF1 Supply 10 50 50 50

A Demand 2 10 5 10

B Demand 3 10 10 20

PF1 Net 5 30 35 20

PF1 Cum 5 35 70 90

A request for item A of quantity 30 on Day 3 can be promised on Day 3, because there is
cumulative supply of 70 on Day 3.


Demand Class ATP
Demand Class ATP enables you to perform availability checks by demand class. The
availability calculation only considers the supply in a master schedule with the same
demand class as that on the ATP request.

This feature is useful when you want to use a known statement of supply of
independent items for a specific sales channel for order promising. For example, your
sales channels may be countries. You know how much supply you give to each country.
The aggregate demand from the customers in a country cannot exceed supply allocated
to that country. You use demand class to represent the country, and declare the supply
for each country by using a specific MPS. Oracle Global Order Promising honors the
MPS, and only promises demand based on the demand class MPS.

Setup
Additional setup steps and details, beyond the mandatory and optional steps explained
in Functional Setup for ATP Based on Collected Data, page 2-8 section, are described
below for the Demand Class ATP functionality:

ATP Rule
You need to check the Demand Class field in the ATP Rule.
Demand Class ATP restricts the supply and demand to sources with a specified
demand class. A demand class ATP Rule cannot include on-hand quantity, purchase
orders, supplier requisitions, internal requisitions, or intransit shipments as sources of
supply.

Demand Class MPS
You need to define an MPS for each demand class for which you perform Demand
Class ATP. You need to create entries for each demand class MPS.

Demand Class ATP Compared To Allocated ATP
In Demand Class ATP, you promise orders by sales channels through the use of
demand class. You use a specific MPS for each demand class, and populate the master
production schedules with a statement of supply for that demand class. Oracle Global
Order Promising uses the demand class MPS to calculate the available supply against
the demand with the same demand class. The mechanism is simple, and can work well
in an environment where demand does not fluctuate much and supply is relatively
fixed.
Allocated ATP, page 4-105 lets you obtain the same result as the Demand Class ATP by


ensuring some level of supply for your designated sales channels. However, this feature
is much more powerful and the implementation is more flexible. It differs from
Demand Class ATP in the following ways:
• Allocated ATP allows you to designate sales channel by demand class, customer
class, customer site, or ship-to site hierarchy. Demand Class ATP lets you designate
sales channel by demand class only.

• Allocated ATP allows you to define time phased allocation rules that designate a
percentage of your total supply to each sales channel. The allocation rule is applied
to your designated production MPS or MRP plan during order promising. Demand
Class ATP requires that you to maintain a specific MPS for each demand class, and
uses that as the statement of supply during order promising. You need to
synchronize the demand class MPS's and the production MPS.

• Allocated ATP performs a capable-to-promise check when demand exceeds
allocation. Demand Class ATP cannot.

• Allocated ATP provides automatic stealing from lower ranked sales channels.
Demand Class ATP requires that you to resolve the shortage by manually adjusting
the demand class MPS.

Oracle Advanced Supply Chain Planning is required to deploy Allocated ATP
capability in Oracle Global Order Promising.

ATP Logic
An ATP request is processed by the system as follows:
1. The ATP Rule, either item level or org level, is checked to see if Demand Class ATP
needs to be done.

2. If Demand Class ATP is enabled on the ATP Rule, the system checks for a plan
having the same demand class as the demand class on the ATP request.

3. If no demand class specific plan is found, then the generic plan with no demand
class is used.

Improved ATP Performance
Oracle Global Order Promising response times can be improved by a summary
approach that stores summarized supply and demand information into a separate table.
This allows each ATP request to quickly retrieve summarized availability information
without computing availability from detailed supply and demand information. The
result is the same as using detailed data. It is highly recommended that you use
summarized data.


The summary process is accomplished through the concurrent program: Load ATP
Summary Based on Collected Data. This summary concurrent program is automatically
run after each data collection.
This feature is currently only supported for non-distributed environments only:
environments where the transaction data source and the Oracle Global Order Promising
are on the same database instance.

Setup

To enable ATP based on summary data:
Set the system profile MSC: Enable ATP Summary Mode to Yes.

Manually Generating Summary Tables
While the summary tables required to support summary data based order promising
are automatically triggered by collections, you can also load the summary data by
manually invoking summary concurrent program. You may want to do this if you do
not want to rerun collections before enabling summary data based order promising.
To manually generate the Oracle Global Order Promising summary tables from the
Order Management Super User responsibility:
1. Log in using the Order Management Super User responsibility.

2. From the Navigator, go to Scheduling, and ATP and Scheduling Setup. Now Run
Requests.

3. From the list of values in the Names field, select the following concurrent request:
Load ATP Summary Based on Collected Data.

4. Select the following ATP Summary Based on Collected Data parameters:
• Instance

• Load Method:
• Complete Refresh: completely resummarizes sales orders and
supplies/demands. Demands mean other demand such as WIP Job demand.

• Net Change Refresh: summarizes the new sale orders and
supplies/demands change after last collection run.

• Targeted Refresh: performs a Complete Refresh on either sales orders or
supplies/demands.

• Refresh Sales Orders: yes or no. You can only set to Yes if Load Method = Net


Change Refresh.

• Refresh Supplies/Demands: yes or no. You can only set to Yes if Load Method =
Net Change Refresh or Complete Refresh.

5. Select Submit.


4
ATP Based on Planning Output: Part I

• Basic ATP
• Multi-Level Supply Chain ATP
• Combined Item-Product Family ATP
• Allocated ATP

Basic ATP
Basic ATP allows you to perform an availability check based on statement of current
and planned material supply against a given organization. You can perform ATP checks
by specifying the item, need-by date, and organization. Results describing the need-by
date quantity and the fulfillment date of their request are returned to you.

Basic ATP allows customers to perform availability checks and receive detailed
information on whether their request can be met or on what date the order can be
fulfilled. Based on statements of current and planned material supply, Basic ATP
determines the availability of items.
You perform a Basic ATP check when you only have one inventory location in your
company or you simply want to check availability in one inventory location.

Setup
After you perform the mandatory and optional setup steps explained in the Setup
chapter, you should be able to perform Basic ATP.

ATP Based on Planning Output: Part I 4-1

ATP Logic

ATP Logic in a Single Organization
1. If Check ATP and Component ATP item attributes are set to None, there is no ATP
check.
If the ATP item attribute is Material Only, the system checks ATP for the item on
the request date. If there is availability, you are done. Otherwise go to step 2.

2. ATP fails to satisfy the request on the request date. From the request date, Oracle
Global Order Promising looks forward for future supply. It returns an ATP Date
that is the earliest date that the request quantity is available.

3. If the ATP Date is less than or equal to the Latest Acceptable Date, Oracle Global
Order Promising returns success. Otherwise, it returns failure.

Note: The Latest Acceptable Date is a date beyond the request date
that the customer will accept the order. This date is determined by
any calling application, and is passed to Oracle Global Order
Promising.

ATP Result
Oracle Global Order Promising returns very detailed information and presents the data
in ATP Details window. However, the calling application may decide to only show a
subset of that information. For example, Oracle Order Management shows some of the
ATP results such as warehouse, Request Date Quantity, Available Date, and Error
Message in the Availability window. It provides an ATP Detail selection for users to
drill down to in the ATP Details window, if user desires detailed information. The
information provided in the ATP Details window is typically not needed for end users.
For details on ATP Details window, see: ATP Details, page 6-5.

Multi-Level Supply Chain ATP
Oracle Global Order Promising lets you perform a multi-level component and resource
availability check across your supply chain for the end items you specify. You can
control the organizations and suppliers to be included in the availability inquiry, and
you can control the number of levels in your supply chain bill to be considered in your
check. At each level in the supply chain, you can check the availability of key
components and bottleneck resources.
The diagram depicts a supply chain scenario where item A can be shipped from
organization Org1 and Org2 to a customer. Both organizations manufacture the item.


Item A has a key component B and a bottleneck resource (R1 is a bottle neck resource in
Org1, R2 is a bottle neck resource in Org2). Component B comes from different
suppliers for different organizations with different lead times.

Simplified Supply Chain Scenario

Multi-Level ATP can help you decide the following:
• Which shipping organization can meet the demand on request date?

• If there is not enough supply (on-hand plus scheduled receipts) in a shipping
organization, then can I make it or source it from another organization?

• If there is not enough supply for a component, does my supplier have additional
capacity?

Multi-Level Supply Chain ATP helps companies to increase order fill rate by promising
orders using extra manufacturing and supplier capacity. Because of demand
fluctuation, your planned production level can change and thus result in under
utilization of manufacturing resources or supplier capacity at times. However, if
demand increases beyond forecast, you want to be able to book those orders using the
extra capacity. A Multi-Level Supply Chain ATP check will ensure whether you have
enough capacity to book the unanticipated demand.
As companies today out source more and more of their assemblies or subassemblies,
order promising can only become accurate if the supply chain is being considered. A
factory must be capable of not only making the product on time, but also delivering the
product to the parent factory on time. Transit lead time between the facilities and from
the suppliers become critical elements in the availability calculation. Only Multi-Level


Supply Chain ATP is capable of providing you with an accurate promise date based on
the entire supply chain.

Setup
Besides the mandatory and optional steps discussed in the Setting Up, page 2-1, the
following are the additional setup steps for using Single-Level or Multi-Level Supply
Chain ATP.

ATP Plan
You need to establish an Advanced Supply Chain Planning plan to be used for
ATP/CTP for Multi-Level Supply Chain ATP.
For detailed setup instructions, see: Setup, page 2-1.

Supply Chain
You can Model your supply chain through sourcing rules or bills of distribution, and
assign the sourcing rules or bills of distributions to your items, organizations, suppliers,
and customers in assignment sets. Oracle Global Order Promising shares the same
supply chain setup as Oracle Advanced Supply Chain Planning.
The following is an example of a supply chain. Order for item A from customers can be
shipped from either Org1 or Org2. Shipping from Org 1 is preferred (rank 1). A is made
of component B and uses resource R1 in Org1. Item B is sourced from Supplier1. A in
Org2 can be transferred from Org3 or made in Org2. Transferring is more preferred
than making.


Multi-Level Supply Chain Scenario

You can use either Sourcing Rules or Bills of Distribution to define the supply chain
below the shipping organizations. This is illustrated in the above diagram.
MRP: ATP Assignment Set or MSC: ATP Assignment Set should be set to point to the
assignment set that contains the Sourcing Rules that define the movement of goods
from shipping organizations to customers.
For more information about how to set up sourcing rules, bills of distribution, and
assignment sets, see Sourcing Rules and Bills of Distribution in Oracle Master
Scheduling/MRP and Oracle Advanced Planning and Scheduling User's Guide.

Regional Level Sourcing
Geographic Regions and Zones
Oracle Shipping supports country, state/province, county, city, and zip code geographic
region levels. A zone is a user-defined collection of regions. You can group the regions
into user-defined zones. For example, you can group all the west coast states into a zone
called West Coast.

Note: Oracle Global Order Promising does not support county as a
region.

For detailed description and setup instruction, see Regions and Zones in Oracle Shipping
Execution User's Guide.
Sourcing Rules at Region or Zone Level
You can assign a sourcing rule at various levels including region and zone. Oracle
Global Order Promising selects the most specific assignment based on the priority
provided in table below. Then it uses the sourcing rule in the assignment to determine
the shipping organization.


Oracle Global Order Promising uses the customer ship-to to determine the region or
zone that the ship-to address belongs to. Then it automatically uses the correct regional
or zonal sourcing rule. If more than one sourcing rule applies, Oracle Global Order
Promising chooses the sourcing rule that is assigned to the most specific, smallest
geographic area. If there is a more specific sourcing assignment exists, for example:
Instance-Item-Organization type, then the specific sourcing rule is used.
This capability allows you to easily manage regional distribution centers that serve
designated sales in the region.
The following table shows the assignment level. The higher the priority, the more
specific the assignment level.

Assignment Level Priority

Item-Instance-Organization 1

Item-Instance-Region 2

Category-Organization 3

Item-Instance 4

Category-Region 5

Category 6

Instance-Organization 7

Instance-Region 8

Instance 9

• When you choose an assignment level that has an organization, you
can make the assignment either an organization or
customer/ship-to site.

• Region level sourcing only applies to customers as receiving
parties.

For detailed setup instructions, see Sourcing Rules in Oracle Master Scheduling/MRP and
Oracle Supply Chain Planning User's Guide.


To enable Oracle Global Order Promising to use region level sourcing:
1. On the source instance, setup region level and zone.

2. Log on with the Advanced Supply Chain Planner responsibility.

3. Run collections.

4. Create the appropriate sourcing rules on the source or destination instance.

5. Create an assignment set on the source or destination instance.

6. If you have created the assignment set on the source instance, then run collections.

7. On the destination instance, assign the sourcing rules at the region or zone level.

Sourcing Rule/Bill of Distribution Assignments Window

8. Enter the assignment set name and description.

9. In the Assigned To drop-down menu, choose Item-Instance-Region or
Category-Instance-Region or Instance-Region to create a region-level sourcing rule
assignment.


10. Select an item from the LOV in the Item/Category column.

11. Select either Sourcing Rule or Bill of Distribution from the LOV in the Type column.

12. Select a sourcing rule or bill of distribution from the LOV in the Sourcing Rule/BOD
column.

13. Scrolling to the right, select a region or zone from the LOV in the Region/Zone
column. You can search for a region or zone in the Regions search window.

14. Save the assignment set.

15. On the planning server, set the profile option MSC: ATP Assignment Set to the
assignment set that was saved.

• Region level sourcing assignments can only be defined on the
destination instance under Sourcing menu in Oracle Advanced
Supply Chain Planner responsibility. They cannot be defined in
the source in the Sourcing Rule and the Bill of Distribution
Assignments windows of Oracle MRP and Oracle Supply
Chain Planning.

• Since MRP: ATP Assignment Set defined at the source instance
takes precedence over the MSC: ATP Assignment Set defined
on the planning server, you need to make sure it is set to
NULL. Thus, Oracle Global Order Promising uses MSC: ATP
Assignment Set.

Transit Lead Times
Oracle Global Order Promising considers the transit lead time associated with a
shipping method from shipping warehouse to customers as well as transit lead time
between source-from and source-to organizations.
You set up transit lead times using Transit Times form available in Oracle Shipping.
For detailed setup instruction, see Transit Times in Oracle Shipping Execution User's
Guide.
The following diagram describes the transit lead times between various parties and
shows how Oracle Global Order Promising honors the lead times:


Transit Lead Times

From shipping warehouse to customers:
You can define shipping methods and their related lead time from your shipping
organization to a location. A location can be from most specific to least specific: an
internal location associated with a customer ship-to location, a region, or a zone. When
more than one applicable transit lead time exists in the shipping lane, the most specific
lead time specification is used. For example, you have defined shipping lane from your
shipping organization to a specific customer location with shipping method of
GROUND that has lead time of 3 days. You must have also defined a shipping lane
from your shipping organization to a region where the customer resides. It also has
GROUND as a valid shipping method that has lead time of 2 days. For a sales order to
this customer using GROUND shipping method, Oracle Global Order Promising will
use 3 days for the transit lead time.
Between organizations:
You can define shipping methods and their related lead time between a source-from
and source-to organizations. Oracle Global Order Promising will honor the lead time
during its capable-to-promise calculation.
From supplier to organization:
Oracle Global Order Promising does not currently consider shipping methods used
between a supplier and a receiving organization. A typical implementation approach to
Model the lead time is by using the item post processing lead time or by using the item /
Approved Suppliers List (ASL) lead time.
For detailed setup instruction, see Inter-Location Transit Times in Oracle Shipping
Execution User's Guide.

Resource Capacity
Oracle Global Order Promising shares the same resources and routing information as
Oracle Advanced Supply Chain Planning.


To designate a specific resource for Capable-To-Promise check:
1. Sign on using the Manufacturing and Distribution Manager responsibility.

2. From the Navigator, select Bills of Materials. Then select Routings, and finally
Departments.

3. Select the department to which the resource belongs.

4. Click Resources button. The Resources window appears.
This window shows the resources that have the Enable the Check CTP flag enabled.

Resources Window

Note: Oracle Global Order Promising:

• Uses only primary resource capacity during capable-to-promise
calculation, not alternate resource capacity.

• Supports network routing only with planning method =
Planning %.

For details on how to setup up routing, see: Setting up Routings under Supply Chain
Modeling in Oracle Advanced Planning and Scheduling User's Guide.


Supplier Capacity
Oracle Global Order Promising checks supplier capacity when performing
capable-to-promise calculation. It uses the same supplier capacity information used in
Oracle Advanced Supply Chain Planning. You can define multiple supplier sources.
Oracle Global Order Promising checks the supplier capacity in the order of the source
rank defined on the sourcing rule.
During the capable-to-promise process, Oracle Global Order Promising uses supplier
capacity calendars that indicate the working/non working days of the supplier. Supplier
capacity is only accumulated on the working days according to the supplier capacity
calendar.
For more information about setting supplier capacity constraints, see Supply Chain
Modeling in Oracle Advanced Supply Chain Planning Implementation and User's Guide.

This profile points to an assignment set that contains the Sourcing Rule that defines the
movement of goods from shipping organizations to customers. This profile is set up at
the source instance. If you plan to use Region/Zone level sourcing, you must set this
profile to NULL.

Profile MSC: ATP Assignment Set
This profile points to an assignment set that contains the Sourcing Rule that defines the
movement of goods from shipping organizations to customers. This profile is set up at
the destination instance. MRP: ATP Assignment Set defined at the source instance takes
precedence over the MSC: ATP Assignment Set. If you plan to use region or zone level
sourcing, you need to set the latter instead of MRP: ATP Assignment Set.

Data Collection and Run Plan
Once you finish setup at source instance, you need to run Collection.
For details, see: Setting Up, page 2-1.
Once you finish setup on the destination side, you need to launch the ASCP plan that is
used for ATP. Please review plan output for correctness because Oracle Global Order
Promising uses the result.

ATP Logic

For Request With Specified Shipping Organization
If a request has shipping organization specified, then only search for availability from
the specified organization and its sources.
1. Check availability for the item at that organization based on the Check ATP flag. If
the organization is the shipping organization, check for the entire requested


quantity. If the organization is a source-from organization for the shipping
organization or supply organization for a lower level component, check for the
remaining shortage. If both the Check ATP flag and the Component ATP flag are
set to None, no ATP check is performed. If the Check ATP flag is set to Materials, an
ATP check for the item on the request date is performed. If there is enough supply
on the request date, the system goes to step 5.

2. If the Component ATP flag is set to None, the request is not satisfied. The system
goes to step 4, otherwise, go to step 5.

3. If the Component ATP flag of the item in step 1 is not set to None, determine the
sourcing of the item:
1. If source is Make At, the bills of material is exploded to get to the next level
component (if Component ATP Flag contains the Material check) and resource
(if Component ATP Flag contains the Resource check) to check availability.
• If there is not enough resource availability, go to step 4.

• If there is enough resource availability, go to next step.

• Repeat step 1 for the components of the item in step 1.

2. If source is Buy From, supplier capacity is checked. If there is not enough
capacity, go to step 4. If there is enough supply, go to step 5.

3. If source is Transfer From, go to the source-from organization to check
availability. Repeat step 1 for the item in the source-from organization.

4. ATP has failed to satisfy this request. From request date, forward scheduling for
this request is performed. The system searches for the earliest date that it can get
the remaining quantity. The earliest date is the ATP date. If the ATP date is <=
Latest Acceptable Date (LAD), then the ATP status is success. Otherwise, the ATP
status is failure. Also note that the LAD is determined by the calling application.

Note: In case of a set, Oracle Global Order Promising honors the
earliest of the given Latest Acceptable Dates.

5. ATP has successfully found supply on the request date. ATP returns the request
date as the ATP date, and success as the ATP status.

For Request Without Specified Shipping Organization
If a request does not specify a shipping organization, start with the shipping
organization with the highest rank from sourcing rule. If the ranks are the same, then
choose the one that has highest percentage. If the percentages are the same, then choose


any one. In the following example, the shipping organization Org1 will be picked first.
Using the above logic for the following supply chain, a request from a customer for item
A without a specific shipping warehouse triggers Oracle Global Order Promising do the
following:
For each of the shipping warehouses starting from the highest ranked one, obtain the
ATP Date, ATP status:
• If ATP status = success, return shipping warehouse, ATP Date, status and other
information.

• If ATP status = failure, go to next shipping organization.

• If ATP status = failure for all the shipping organizations, return shipping
warehouse, ATP Date, status and other information from the highest ranked
organization.

Supply Chain for Item A

Forward Scheduling
Forward scheduling refers to looking beyond the request date to find a future supply
that can meet the shortage. In forward scheduling, Oracle Global Order Promising looks
for supply to cover the shortage from each individual source. A source can be found:
• Using scheduled receipts

• Using other sources such as make, transfer, or buy (each source is evaluated
individually)

Oracle Global Order promising uses the source that returns the earliest available date.


Note: Oracle Global Order Promising does not combine supply from
multiple (or more than one) sources in forward scheduling.

An order will be scheduled if the ATP date is on or before the Latest Acceptable Date.
Otherwise, Oracle Global Order Promising will return the ATP date without scheduling
the order.

Transit Lead Time
There can be transit lead time from your shipping warehouse to customers and between
organizations. The transit lead time days are considered as calendar days.
For more details on calendar days calculation, see: Shipping, Receiving, and Carrier
Calendars, page 6-34.

Detailed Logic for Make Item

Work Order Start Date
In the following example, A can be made using component B and requires resource R1.
Oracle Global Order Promising calculates the start date of the job by offsetting
manufacturing lead time from A's request date. For example, A's fixed lead time = 1
day, variable lead time = 0.5 day. A request for A of quantity of 10 on Day 10 means the
job start date would be Day 4 (Day 10 - 1 - 10 * 0.5 = Day 4).

Supply Chain for Make Item A

If the job start date falls before today's date or within Planning Time Fence of the item,
Oracle Global Order Promising fails to meet the demand on request date.
The start date calculation is based on the manufacturing calendar of the organization. In
this example, if Day 5 and Day 6 are non-working days, then the start date should be
Day 2.

Note: Planning Time Fence (PTF) is calculated at the time of each plan
run. The PTF Date = the date the plan runs + PTF days. If the Planning
Time Fence control is off at the plan level, then PTF = the date the plan
runs.
ATP considers the value that is greater between the system date and
the calculated date, as the PTF date.


Resource Requirement Calculation
Oracle Global Order Promising calculates resource requirement as the following:
For resources with basis of Item:
Demand quantity * Resource usage / (Reverse cumulative yield * Resource efficiency %*
Resource utilization %)
For resources with basis of Lot:
Resource usage / (Reverse cumulative yield * Resource efficiency %* Resource
utilization %)
Oracle Global Order Promising uses resource offset % to determine when to check
resource availability. The logic is the following:
• Compute resource start date: Resource start date = Demand request date - (1- offset
%) * manufacturing lead time.

• Sort resources by the start date from earliest to latest.

• Check availability of a resource on the start date of the next resource in the above
sort.

Example: Item A has the following resources that have CTP flag checked on its routing.

R1 Op 10 Offset=0% Usage=1hr

R2 Op 20 Offset=60% Usage=2hr

A's Fixed lead time = 0 day and Variable lead time = 0.4 day
Assume 100% resource utilization and efficiency. Reverse cumulative yield = 1.
Request for A for quantity 10 on Day 5. There is no availability of A on Day 5. Oracle
Global Order Promising performs capable-to-promise.
1. R1 start date = Day 5 - (1 - 0%) * (0 + 10 * 0.4) = Day 1.

2. R2 start date = Day 5 - (1 - 60%) * (0 + 10 * 0.4) = Day 3.

3. Sort R1 and R2.

4. Check R1's availability on Day 3.

5. Check R2's availability on Day 5.

Resources Availability Calculation
Oracle Global Order Promising cumulates resource availability from the planning time


fence date of the assembly item that the resource belongs. The planning time fence date
is calculated by Oracle Advanced Supply Chain Planning. If the Planning Time Fence
checkbox is not checked in the plan option, Oracle Advanced Supply Chain Planning
uses the plan start date as the planning time fence date.
In the above example, let's say A's planning time fence date is D2. There is net
availability of resource on each day. But cumulative availability only starts on Day 3.

Resource 1 D1 D2 D3 D4 D5 D6 D7

R1 Net 3 5 5 10 10 10 10

Cum 0 0 5 15 25 35 45

Shared Resources
Shared resource is a resource owned by a department but can be used by other
departments. Oracle Global Order Promising looks for the availability in the owning
department and sums the requirement from all departments that uses the resource.

Batch Resources
Oracle Global Order Promising supports the ability to accurately consider the capacity
of batch resources.
For details, see: Batch Resource Considerations, page 4-29.

Component Requirement Calculation
Oracle Global Order Promising checks component availability on the work order start
date. The required quantity is calculated as follows:
Demand quantity * Component usage / Reverse cumulative yield

Component Availability Calculation
Oracle Global Order Promising uses cumulative supply up to the component
requirement date. The cumulative quantity starts from plan start date.

Component Substitution
ATP supports the use of substitute components if the primary component is not
available.
For details, see:Component Substitution, page 4-27.

Detail Logic for Buy Item
The following example is used to explain the detail logic for a buy item:


Supply Chain for Buy Item B

Item B in Org 1 can be sourced from Supplier 1. Check ATP attribute for B is set to
Material. Component ATP attribute for B is set to Material. A request comes for B for
quantity of 10 on Day 9 in Org 1.
Lead time information:
• Post processing lead time for B = 1 day.

• Processing lead time for B = 2 days.

• Preprocessing lead time for B = 1 day.

• Processing lead time for Supplier1 = 3 days.

• Item B planning time fence date = Day 4.

Net and cumulative availability picture is the following:

Item Row Type Day Day Day Day Day Day Day Day Day 9
1 2 3 4 5 6 7 8

B/Org1 Net 1 0 0 0 0 1 0 0 0

B/Org1 Cum 1 1 1 1 1 2 2 2 2

B/Supplier1 Net 10 10 15 15 20 10 10 10 10

B/Supplier1 Cum 10 20 35 50 70 80 90 100 110

Oracle Global Order Promising performs the following:
1. There is quantity of 2 on Day 9. Shortage is 8.

2. Component ATP flag is set to Material. There is a sourcing rule to purchase the item
from Supplier1. Go to next step. Otherwise ATP fails to meet request date.

3. Item B has 1 day post processing lead time. This means we must receive the item


from Supplier1 on Day 8 (dock date = Day 8). If the item's post processing lead time
puts the receipt date before today's date or on or before planning time fence date,
then ATP fails to meet request date.

4. Check to see if supplier has sufficient time to process. The time needed = item's
preprocessing lead time + approved supplier list's processing lead time = 4 days. If
the approved supplier list's processing lead time is not defined, item's processing
lead time will be used and is calculated as (fixed lead time + variable lead time *
quantity). The request to Supplier 1 is Day 8. Day 8 - 4 days = Day 4. Since it is
greater than today's date, the supplier has sufficient time. If it is < today, ATP fails
to meet request date.

5. Check supplier capacity on the dock date at the supplier. In this example, it is Day
8. There is a cumulative quantity of 100 on Day 8. This is enough to cover the
shortage of 8. ATP succeeds.

Detail Logic for Transferred Item
Oracle Global Order Promising first ensures that the receiving organization has
sufficient time to process the receipt. It offsets the demand date of the item in the
receiving organization by item's post processing lead time. If the result is before today's
date or on or before planning time fence date, ATP fails to meet the demand on request
date.
The demand date in the source-from organization is calculated by offsetting transit lead
time. Oracle Global Order Promising will honor the shipping method and its lead time
from the sourcing rule. If shipping method and lead time are not present on the
sourcing rule, Oracle Global Order Promising uses the default shipping method and its
lead time defined in the shipping network for the two organizations. If there is no
default shipping method, then 0 lead time is assumed.
After offsetting the transit lead time, if the demand date in the source-from organization
is before today's date, Oracle Global Order Promising fails to meet the request.
Otherwise it proceeds with checking availability in the source-from organization based
on the item's ATP attributes in that organization.

Planned Order
Oracle Global Order Promising creates planned order supply when it determines that
there is enough capacity to make, buy or transfer an item. These planned orders will be
visible from Planner Workbench in Oracle Advanced Supply Chain Planning. The
planned order created by Oracle Global Order Promising does not have pegging
information.
When a sales order is cancelled, Oracle Global Order Promising removes the sales order
demand from the plan, but it does not remove any planned order created previously to
satisfy the sales order. The supply is available for new sales order demand.


Examples
The supply and demand figures in the following examples are expressed in the primary
unit of measure of the referenced item or resource.
Multi-Level ATP in a Single Organization
Assume assembly A has the following bill in Org1.

Multi-Level ATP

Lead time information for A and B is as shown in the following table:

Item Fixed Lead Time Variable Lead Time

A 0 0.1

B 1 0.01

The routing information for Item A and Item B is as shown in the following table:

Item Operational Resource Usage Lead Time
Sequence Offset

A 1 R1 1 0

B 1 R2 2 20%

Planning information for Item A and Item B from an MRP run on Date1 is as shown in
the following table. Assume every day is a working day.


Supply / Item A Item B Item C Item D
Demand Type

Sales Orders 10 5 50 40

Forecasts 100 10 75 60

Dependent 0 145 270 135
Demand

Scheduled 5 25 50 50
Receipts

Planned Order 105 135 345 185

ATP 100 10 75 60

Suppose we have the cumulative ATP quantities from the planning run as shown in the
following two tables:

Item Date1 Date2 Date3 Date4 Date5 Date6 Date7

A 100 100 110 110 150 160 170

B 10 10 10 200 255 260 270

C 10 75 85 85 85 90 100

D 50 60 60 60 60 65 70

Resource Date1 Date2 Date3 Date4 Date5 Date6 Date7

R1 16 16 16 16 20 22 24

R2 16 16 16 16 22 24 26

The values of the Check ATP flag and Component ATP flag of the request item
determine the level of the ATP check, which may cause different results for the same
request. Assume that the Check ATP flag at bill level is Yes for all items.


Example 1-1: Request 100 of Item A on Date4 in Org1

Item Check ATP Flag Component ATP Flag

A Materials None

We do have ATP quantity 100 on Date4. ATP date is Date4.
Case 2.1


A Materials None

1. We do not have ATP quantity 120 on Date4.

2. Component ATP flag is None. We cannot go to next level. ATP fails for this request.
For Item A, we can have 110 on Date4 and 120 on Date5. ATP date is Date5.

Case 2.2


A Materials Materials

B Materials None

1. We do not have 120 of Item A on Date4.

2. The Component ATP flag is Materials. The shortage is 10 for Item A. The lead time
to build 10 of Item A is one day. Therefore, we need 10 of Item B on Date3 to build
this simulated supply of 10.

3. We do have 10 of Item B on Date3, so the ATP date is Date4; use 110 of Item A on
Date4 and 10 of Item B on Date3.

Case 2.3



A Materials Materials and Resources

B Materials None

1. We do not have 120 of Item A on Date4. The shortage is 10.

2. The Component ATP flag of Item A is Materials and Resources. Simulate a supply
of Item A for quantity 10. Explode the bill to the next level. The lead time to build 10
of Item A is one day. We need 10 of Item B on Date3 and 10 R1 on Date3 to build 10
of Item A
We do have 10 R1 on Date3.
We do have 10 of Item B on Date3. So ATP date is Date4; use 110 of Item A on
Date4, 10 of Item B on Date3, and 10 of R1 on Date3.



A Material Only Material and Resource

B Material Only Material and Resource

C Material Only None

D Material Only None

1. We do not have 165 of Item A on Date5. The shortage is 15.

of Item A for quantity 15. Explode the bill to the next level. The lead time to build
15of Item A is two days. We need 15 of Item B on Date3 and 15 R1 on Date3 to build
15 of Item A.

3. We do have 15 R1 on Date3.

4. However, we only have 10 of Item B on Date3, and the shortage is 5.

5. The Component ATP flag of Item B is Materials and Resources. Simulate a supply
of Item B for quantity 5. Explode the bill to the next level. The lead time to build 5 of
Item B is two days. We need 10 of Item C and 5 of Item D on Date1, and 10 R2 on


Date2 (Date3-CEIL((1+0.01*5)*80%)).

6. We do have 10 R2 on Date2.

7. We do have 10 of Item C and 5 of Item D on Date1, so the ATP date is Date5; use
150 of Item A on Date5, 10 of Item B on Date3, 15 of R1 on Date3, 10 of Item C on
Date1, 5 of Item D on Date1, and 10 of R2 on Date2.

Case 4


A Material Only Material and Resource

B Material Only None

1. We do not have 130 of Item A on Date3.

of Item A for quantity 20. Explode the bill to the next level. The lead time to build
20of Item A is two days. We need 20 of Item B on Date1 and 20 R1 on Date1 to build
20 of Item A.

3. We do not have enough R1 on Date1. ATP fails for this request on request date.

4. We can only make 16 of Item A since we only have 16 R1 available on Date1.

5. We can only make 10 of Item A since we only have 10 of Item B available on Date1
although we have 16 R1 available on Date1. The request date ATP quantity is 120.

6. Do forward scheduling from sysdate (Date1) for Item A with quantity 10.

7. The earliest date we can have another 10 R1 is Date5 (the supply picture of R1 has
been changed since we have used 10 R1 in Date1 to build 10 of Item A).

8. The earliest date we can have 10 of Item B is Date4 (the supply picture of Item B has
been changed since we have used 10 of Item B in Date1 to build 10 of Item A).

9. Considering lead time, the earliest date we can have 10 of Item A built is Date6 (=
max (Date4 + 1, Date5 +1)

10. If we do not build 10 of Item A, we can have 130 of Item A on Date5. Date5 < Date6.
The ATP date is Date5. We can provide 130 on Date5.


Multi-Level ATP for a Supply Chain BOM
The supply chain bill looks like the following figure:

Supply Chain Bill Example

For an item with no associated sourcing information, the item is assumed to be make or
buy based on item's make / buy code. If the item is buy, Oracle Global Order Promising
assumes infinite capacity.
Assume that Customer1 has the following sourcing rule, shown in the next table, with
assembly A.

Source Type Org Rank Shipping Lead Time

Transfer from Org1 1 1 day

Transfer from Org2 2 2 days

Org1
The bill and routing for item A in Org1 is the same as the information provided in the
previous example. No sourcing information is defined for item A in Org1 and the make
/ buy code is make for item A. It is assumed that item A in Org1 has an implicit supply
chain bill which is shown in the following table:


Source Type Org Rank

Make at Org1 1

The cumulative ATP quantities in Org1 are shown in the following table:

Item Date1 Date2 Date3 Date4 Date5 Date6 Date7

A 100 100 110 110 150 160 170

B 10 10 10 200 255 260 270

R1 16 16 16 16 20 24 26

Org2
The supply chain bill for item A in Org2 is shown in the following table:

Source Type Org Rank Shipping Lead Time

Transfer from Org3 1 1 day

Make at Org2 2 0 days

Item A in Org2 uses the common bill from item A in Org1. The fixed lead time of Item
A is 0 and the variable lead time is 0.1 day.
Item B is a buy item and it sources from Supplier1with lead time of 0 days. Assume
Supplier1 can provide 100 of Item B for Org2 from Date1 to Date10.

Item/Resource Date1 Date2 Date3 Date4

A 100 120 120 150

B 10 40 50 60

R1 16 16 16 16

Org3



Item Date1 Date2 Date3 Date4 Date5

A 20 20 20 20 30

Note: Assume that the Check ATP flag at bill level for all items in every
organization is set to Yes.

Assume that the Latest Acceptable Date is the same as the request date for all the
following cases:
Example 2-1: Customer1 requests 100 of item A with Date5 delivery date

Item Org Check ATP Flag Component ATP
Flag

A Org1 Material Only None


1. The system checks the availability of 100 of Item A on Date4 at Org1. The item is
available. Therefore, ATP date is Date4 from Org1 and Customer1 will receive it on
Date5 because shipping lead time is 1 day. This request is satisfied by using 100 of
Item A on Date4 in Org1.

Example 2-2: Customer1 requests 120 of item A with Date5 delivery date

Flag


A Org2 Material Only Material and
Resource

1. The system checks the availability of 120 of Item A on Date4 at Org1. Item A has
enough supply on Date5. The ATP date in Org1 is Date5 and Customer1 receives it
on Date6. From Org1, we will not be able to satisfy the request.

2. The system checks the availability of 120 of Item A on Date3 at Org2. The item is
available. ATP date is Date3 from Org2 and Customer1 will receive it on Date5. The
request is satisfied by using 120 of Item A in Org2 on Date3.


Example 2-3: Customer1 requests 145 of Item A with Date5 delivery date

Flag


A Org2 Material Only Material and
Resource


1. The system checks the availability of 145 of Item A on Date4 at Org1. The request
cannot be satisfied in Org1. Item A has enough availability on Date5. The ATP date
in Org1 is Date5 and Customer1 will receive it on Date6.

2. The system checks the availability of 145 of Item A on Date3 at Org2. There is not
enough of Item A and the shortage is 25.

3. The Component ATP flag is Material and Resources. There are two sources to
obtain item A:
1. Transfer from Org3

2. Make at Org2.
Oracle Global Order Promising starts with the higher ranked source.

4. Oracle Global Order Promising checks the availability at Org3 and tries to transfer
25 of Item A from Org3 on Date2 to cover the shortage. There is only 20, and so the
shortage is 5.

5. Oracle Global Order Promising checks the availability at Org2 and tries to make 5 of
Item A to cover the shortage. Five of Item B and 5 R1 on Date2 is needed. There is
16 of R1 on Date2. There is 10 of Item B on Date2. ATP date is Date3 from Org2 and
the customer receives it on Date5. The request is satisfied on the requested date by
using 120 of Item A in Org2 on Date3, 20 of Item A in Org3 on Date2, 5 of R1 in
Org2 on Date2, and 5 of Item B in Org2 on Date2.

Component Substitution
ATP supports the use of substitute components if the primary component is not
available. If sufficient quantity of primary component is not available, the ATP searches
for substitute components.
Many substitutes are possible for a primary item. In this case, the sequence of search for
substitutes is determined by substitute priority, which is a flex field in the Bills of


Material.
ATP splits demand among the primary and substitute components. For example:
• Demand for 10 comes for item A.

• Item A has Item B as a component.

• Item B has two substitutes: B1 and B2.

• Item B has 2 available, B1 has 4 available, and B2 has 20 available.

Then, the ATP results will return, 2 for Item B, 4 for B1, and 4 for B2. It will not just
return 10 for B2.
Consider the Bills of Material, shown below, where A is made up of component B. B can
be substituted by B(1) whenever B does not exist.

Bills of Material Example

Oracle Global Order Promising searches for substitute components before doing a
multi-level search. If there is not sufficient quantity of A to meet the requirement at a
given date, the quantity for B is checked. If that is also not enough, the substitute B(1) is
considered. If that is also not sufficient, then C that is the component of B is considered.
Oracle Global Order Promising does not search for the components of B(1), which is the
substitute for B.
Even after the inclusion of B(1) and C, the demand is not satisfied. Then Oracle Global
Order Promising searches forward to find a date when the shortage can be met. In
forward scheduling, substitute components are not considered.


MRP: Include Substitute Components
This site level profile must be enabled in order to consider substitute components in the
ATP inquiry.

Batch Resource Considerations
Oracle Global Order Promising supports the ability to accurately consider the capacity
of batch resources when performing Capable-To-Promise based on planning data. Batch
resources are resources that can process multiple units of the same item or multiple
units of different items simultaneously.
Batch resource capacity is expressed along two dimensions:
• Time dimension: how long each load takes to process.

• An additional size dimension that expresses the maximum size of each load: the
number of units in each load, maximum weight of each load, or maximum volume
of each load.

Oracle Global Order Promising considers the capacity of batch resources by converting
multiple dimensions into a single dimension, such as unit-hours. Oracle Global Order
Promising uses the cumulative available capacity for the Capable-To-Promise
calculations. For example:
Batch Resource Heat_Treat_1 is for heat-treating pistons. The capacity information:
• Volume of 100 cubic feet

• Availability 8 hours / day

• Capacity / day = 100 cubic feet * 8 hours = 800 cubic feet hours

The capacity requirement:
• Piston1 requires 2 hours of processing and occupies 1 cubic foot

• Capable-To-Promise inquiry for a quantity of 100 Piston1 on Day 2. Capacity
needed = 1 cu. ft. * 2 hours * 100 units = 200 cubic feet-hours.

The following table shows the capacity picture of Heat_Treat_1 at the time of the
Capable-To-Promise inquiry:

Capacity Day 1 Day 2

Total capacity 800 cubic feet-hours 800 cubic feet-hours



Consumed capacity 700 cubic feet-hours 600 cubic feet-hours

Net capacity 100 cubic feet-hours 200 cubic feet-hours

The next table shows the capacity picture of Heat_Treat_1 after the Capable-To-Promise
inquiry and after the order is scheduled:


Total capacity 800 cubic feet-hours 800 cubic feet-hours

Consumed capacity 700 cubic feet-hours 800 cubic feet-hours

Available capacity 100 cubic feet-hours 0 cubic feet-hours

The Capable-To-Promise inquiry returns a result of Day 2.
Resource batching is honored only for constrained MRP / DRP plans and when routings
(not bills-of-resources) are used and when items are planned at the individual item as
opposed to product family level.

Note: Oracle Global Order Promising does not support the Batching
window functionality.

To invoke Capable-To-Promise for batch resources:
Set the profile option MSO: Global Batchable Flag to Yes to setup the resource as a batch
resource.
For details, see: Setting Up Batch Resources, Oracle Advanced Planning and Scheduling
Implementation and User's Guide.

Enforcing Purchasing Lead Time Constraint
Oracle Global Order Promising honors the Enforce Purchasing Lead Time Constraints
plan option for constrained plans. When this option is not selected, Oracle Global Order
Promising will not enforce purchasing lead time as a hard constraint when performing
a capable-to-promise check. It only ensures that the demand due date is greater than the
planning time fence date.
If your supplier provides frequent supplier capacity updates, then you may want to


refer to the supplier capacity updates as the availability information for checking the
supplier's ability to deliver material to your dock, instead of referring to a global lead
time constraint.

To enforce the purchasing lead time constraint:
1. Log into Oracle Global Order Promising with the Advanced Supply Chain Planner
responsibility.

2. Select an instance: organization.

3. Select Plan Options.
The Plan Options window appears.

Plan Options window

4. In the Constraints tab, select Enforce Purchasing Lead Time Constraints.

You can enable or disable this option for constrained plans. For unconstrained plans,
Oracle Global Order Promising always enforces the purchasing lead time during
Capable-To-Promise process.


Configuration ATP
A Configure-To-Order environment is one where the product or service is assembled or
kitted on receipt of the sales order. This chapter provides a detailed explanation of
order promising for items used in a configure-to-order environment.
Oracle Global Order Promising supports Configure-To-Order (CTO) environment. You
can designate any optional items as well as included items for ATP check. This provides
an accurate availability date for the end configuration.

In a configure-to-order environment, it is not always possible or practical to project and
plan for every possible configuration. Inventory is planned and held at component
level. To accurately promise a customer order, you need to check availability based on
the actual options selected. Oracle Global Order Promising lets you promise sales order
for configuration based on the selected options.

Items Used in Configure-to-Order Environment
The following items may be used in a configure-to-order environment.
• ATO Model

• PTO Model

• ATO Item

• Kit (PTO Item)

Examples of the above items are below. In all the examples, the component usage is
assumed to be 1.

Examples
ATO Model


0 Laptop X11 ATO Model - - Yes

1 - Base System Standard No No No

2 - - Board Standard No No No



2 - - Network Card Standard No No No

2 - - Graphics Card Standard No No No

1 - Processor Class Option Yes No Yes
Class

Pentium®4 2.2 GHz

Pentium®4 2.0 GHz

Pentium®4 1.8 GHz

Pentium®4 1.7 GHz

1 - Memory Class Option Yes No Yes
Class




1 - Monitor Class Option Yes No Yes
Class



1 - Modular Drive Option No No Yes
Class Class

2 - - 24X CD-ROM Standard N/A Yes No



2 - - 8X Max DVD Standard N/A Yes No
ROM

2 - - 24X CD-RW Standard N/A Yes No

2 - - 24X Standard N/A Yes No
CD-RW/DVD
Combo

PTO Model


0 Laptop X11 Deluxe PTO Model - - Yes

1 - Laptop X11 ATO Model No No No

1 - External Mouse Option Class No Yes No

2 - - Logitech Optical Standard No Yes No
Mouse

2 - - COMPAQ Standard No Yes No
mouse

1 - Wireless Option Class No Yes Yes
Networking Card

2 - - External Standard No Yes No
TrueMobile 1150
PC Card

2 - - Internal Standard No Yes No
TrueMobile 1150
miniPCI card

1 - Laptop case Standard No No No



1 - External Speaker Optional No Yes Yes
Class

2 - - Premium Standard No No No
Speaker

2 - - Speaker Manual Standard No No No

ATO Item


0 Laptop X11-1 Standard - - Yes

1 - Base System Standard N/A No No

1 - Mobile Standard N/A No No
Pentium®4 2.2
GHz

1 - 512 MB Standard N/A No No

1 - 17in Flat Screen Standard N/A No No

1 - 24X CD-RW/DVD Standard N/A No No
Combo

Kit


0 External Speaker Standard No - Yes

1 - Premium Standard No No No
Speaker

1 - Speaker Manual Standard No No No


ATO Model
If you implement Oracle Advanced Supply Chain Planning and promise orders based
on the output from the ASCP plan, you can promise configuration orders based on the
availability of optional items and resource in the entire supply chain bill. You may use
two types of ATO models:
• Single-Level, Single-Org ATO Model

• Multi-Level, Multi-Org ATO Model

A Single-Level, Single-Org ATO Model refers to an ATO Model that does not have
another ATO Model as its component. In addition, it is neither sourced from a different
organization nor procured from a supplier, in the shipping org.
A Multi-Level, Multi-Org ATO Model refers to a supply chain bill that has an ATO
Model as a non-phantom component of another ATO Model or the Model at any level
can be sourced from an organization other than the shipping organization.

Note: An ATO Model is like a product family. Therefore, it is
recommended to not define an ATO Model under a product family.

For details on demand planning and planning process description, see Oracle Advanced
Supply Chain Planning Implementation and User's Guide and Oracle Demand Planning

Setup
Refer to the Setting Up, page 2-1 chapter for the mandatory and optional setup steps.

ATP Item Attributes and Component ATP
You need to set the Check ATP item attributes.
Here are the setup scenarios:
1. ATO Model is manufactured.
The availability of the ATO Model depends on the availability of its components
and resources. You can set the ATP item attributes as following:



ATO Model • None • Material

• Material and Resource

• Resource

Option Class • None • Material


• Resource

Mandatory Item • Material • Material

• None • Material and Resource

• Resource

• None

• None

Optional Item • Material • Material


• Resource

• None

• None

2. ATO Model is procured.
The availability of the Model depends on the supplier capacity or beyond the
procurement lead time. You can setup ATP attributes as following:



ATO Model • None • Material

Option Class • None • None

Mandatory Item • None • None

Optional Item • None • None

3. The Model is manufactured.
The availability of the Model comes from a supply schedule, which typically
represents an aggregate capacity constraint of the Model. The availability may or
may not depend on the options selected. You can setup the ATP attributes as
following:


ATO Model • Material • None

• Material

Option Class • None • Material

• None

Mandatory Item • Material • Material

• None


4. The Model is procured.
The availability of the Model comes from a supply schedule which is used to
represent supplier capacity. You can setup the ATP attributes as following:



ATO Model • Material • None

Option Class • None • None

Mandatory Item • None • None

Optional Item • None • None

Note: When the Check ATP flag is set to None for an optional item
or a mandatory item, the Component ATP flag should also be set to
None.

Create Config Item for ATO Model item attribute
Set this attribute to Based on Model to perform match to existing configuration check.

Supply Chain: Sourcing Rule, Bills of Distribution, & Assignment Set
You will be able to define sourcing rules or bills of distribution for an ATO Model.
For detail instruction on how to setup sourcing rules or bills of distribution, and
assignment set, see: Setting up the Supply Chain, Oracle Advanced Planning and
Scheduling User's Guide.

Source Model from Supplier
When you source an ATO Model from a supplier, you can define supplier capacity for
the ATO Model. If you set Component ATP to Material for the ATO Model, Oracle
Global Order Promising checks the supplier capacity for the Model.

MRP: Default Sourcing Assignment Set/ MRP: ATP Assignment Set
Set these profiles to the assignment set that defines the supply chain for your Model.
The plan for ATP uses the plan level assignment set that defines the supply chain for
your Model. The sourcing definition for the Model in this assignment set must be the
same as the sourcing definition in the following profiles:
• MRP: ATP Assignment Set. - ATP checks the setting for this profile during order
promising.


• MRP: Default Sourcing Assignment Set - Oracle Configure To Order checks the
setting for this profile to create the bill of material (BOM) and sourcing for a
configuration.

To define supplier capacity for a procured Model:
1. In the Navigator, select Purchasing > Supply Base > Approved Supplier List.

2. Query for the ATO Model item, select Global, then click the Attributes button to
enter the planning attributes.

3. Define the Supplier Capacity for the ATO Model.

This is the total capacity for all configurations of the base Model that the supplier can
produce.

ATP Logic

Match to Existing Configuration
Oracle Global Order Promising determines whether a new sales order matches to an
existing configuration if the profile BOM: Match To Existing Configuration is set to Yes.
• If a matching configuration is found in an ATP enabled plan, then Oracle Global
Order Promising will check the availability using the matched configuration item.
Existing supply for the configuration item will be used. Additional supply may be
created based on the Component ATP flag setting for the configuration item as well
as the supply available for the lower level component and resources. After the order
is scheduled, demand is placed on the configuration item. Oracle Global Order
Promising uses the matched item for available-to-promise checks both before and
after it is linked to a sales order.

• For a Multi-Level Multi-Org ATO Model, Oracle Global Order
Promising supports matching at any level where there is an
ATO Model.

• The matched configuration will not be present on an order line
until you explicitly progress the order to create the
configuration item. That process step should find and match to
the same configuration item that Oracle Global Order
Promising uses.

• If the new sales order does not match with any existing configured item, Oracle
Global Order Promising creates a temporary bill of material (BOM) and routing
structure for the new configuration request and promises the delivery date based


on when the configuration will be available. This bill of material (BOM) includes the
Standard Mandatory Components (SMC) applicable to each organization. The
demand will be placed for the Model, atpable options and standard mandatory
components.

For details on how option specific sourcing is used, see: Example, page 4-46.

To perform a match to configuration check:
1. In the Navigator, select Order Management > Orders, Returns > Sales Orders.
The Sales Orders window appears.

2. Enter a sales order and click Availability.
The Availability window appears with the ATP results. Oracle Global Order
Promising performs a match to configuration check and returns the earliest possible
date.

3. Click ATP Details.
The ATP Details window displays the matched configuration details.

Change Management
In some industry, configuration change can be at a higher rate. Customers may change
their requirement and choose different options.
When a configuration is changed and the order gets rescheduled, Oracle Global Order
Promising returns the supply back to the option that is de-selected and schedules the
new options selected. This ensures the correct availability picture for all the options.
Oracle Global Order Promising performs the following during order rescheduling:
1. It removes the sales order demand for the configuration item.

2. If any of the supply that pegs to the configuration sales order demand is a planned
order supply, Oracle Global Order Promising creates a negative Order
Rescheduling Adjustment to net out that portion of the supply.

3. Oracle Global Order Promising frees up any optional item, standard mandatory
item or resource supplies by creating a positive Order Rescheduling Adjustments to
net out the planned order demand that comes from the planned order of the
configuration item for these items and resources.

4. If the sales order that is unscheduled consumes forecast for a specific configuration
item, then Oracle Global Order Promising will not place adjustments for the
configuration item supply. Therefore, there will be no adjustment for the optional
items and standard mandatory items.


Detail explanation on adjustment with respect to forecast:
Forecasts can be specified for both Configuration Items and corresponding base Models
at any level in the bills of material (BOM). Forecasts can be Global (applicable to all
Organizations) or Local (specific to individual organization). Corresponding to this, the
following consumption scenarios arise:
1. Configuration Item forecast is consumed to fulfill the sales order or lower level
demands.

2. Only Model is forecast and this is consumed to fulfill the sales order or lower level
demands.

3. Both Configuration Item and Model's forecasts are consumed to fulfill the sales
Order or lower level demands.

ATP offsets the consumption and creates adjustments in the following manner.
• Demand Relief: The sales order demand is set to 0. Adjustments are applied to
Planned Order Demands to the extent of the consumption of the forecast of the
Model. If only the Model's forecast is consumed, the entire Planned Order Demand
will be offset. If only the configuration item's forecast is consumed then the
behavior is the same as that of a standard item where Planned Order Demands are
not relieved.

• Supply Relief: The supply adjustments mirror the Demand offsets. The Planned
Order pegged to the Sales Order is offset completely. If more than one supply is
pegged to a demand, the relief will happen only on the allocated quantity for the
demand. Adjustments are applied to Planned Orders Allocated Quantities to the
extent of the consumption of the Forecast of the Model. If only the Model's forecast
is consumed, the entire Planned Order allocated quantity will be offset. If only the
configuration item's forecast is consumed then the behavior is the same as that of a
standard item where Planned Orders are not relieved.

• Resource Requirement Relief: The Resource Requirement adjustments match those
of the Supply that they are tied to. In case of Lot Based Resources, these will be
adjusted only when allocated and supply quantities are the same, for example,
when supplies are not distributed between multiple lines/orders.

For details on Forecast Consumption and Explosion by Planning, see Oracle Advanced
Supply Chain Planning Implementation and User's Guide.

Note: If no new orders are scheduled, Oracle Advanced Supply Chain
Planning recommends cancellation of the real supplies in the next plan
run.

The Order Rescheduling Adjustment is visible in the Planner Workbench. You may
optionally choose to display the rescheduling adjustments in the Planners Workbench


by setting the profile MSC: Display Order Rescheduling Supplies to Yes.
For details on how change management is used, see: Example, page 4-46.

A model-option combination may not always be produced at a specific source. There
can be restrictions associated with specific options like equipment limitations, and
engineering qualifications. If a model requires a specific option, you can predefine that
it will be sourced from a reduced set of sources. Oracle Configure-To-Order enables you
to specify a sub-set of the model sources as valid sources for a model-option
combination. Oracle Global Order Promising honors this setup and schedules a date for
a configuration, based upon the sub-set of the model sourcing that is valid for the
specific configuration. The configuration bill of material (BOM) is created in the
reduced set of sources only.

Note: Oracle Configure to Order may create configuration item in an
org that is not on the list of valid orgs based on the Option Specific
Sourcing rule. When you perform an ATP inquiry for such item in
applications such as Oracle Order Management, Oracle Configure to
Order validates the item-org combination and flags such error.
However, this validation is not available on the destination instance.
You need to provide a valid organization while performing ATP
inquiry for such item.
For more details on configuration item creation, see Oracle Configure to
Order Implementation Guide.

For details on how option specific sourcing is used, see Example, page 4-46.

To define option specific sourcing:
1. In the Navigator, select Advanced Planning > Source Instance Setups > Sourcing >
CTO Option Specific Sourcing List.
The Option Specific Sourcing List window appears.


Option Specific Sourcing List window

2. Define valid sources for each model-option configuration.

Oracle Global Order Promising uses the option specific sources list to restrict available
sources when promising the ATO Model.
• Option specific sources on a child model restrict its parent model's available
sources.

• Oracle Configure-to-Order performs the following:
• The configured item's bill of material (BOM) and routing are created only at the
subset of organizations required by the option specific sources setup.

• New sourcing rules and assignments are created for the option specific sources
model and its parent models.

For details on how to setup configuration creation based on option specific sourcing, see
Oracle Configure To Order User Guide.

To set the item attribute to Based to Model:
1. In the Navigator, select Items > Organizations > Master Item.
The Master Items window appears.

2. Set Create Configured Item, BOM to Based on Model.

For details on setting item attributes, see Oracle Configure-To-Order User Guide.


Option Dependent Resource Support
Option dependent resource means that certain resources are only needed when certain
options are selected. Oracle Global Order Promising considers non-option dependent
resources and option dependent resources for those options selected during its
availability calculation.

To define option dependent resources:
1. In the Navigator, select BOM > Routing.

2. Define the routing for the ATO Model. For each operation, select the Option
Dependent checkbox as required.

3. In the Navigator, select BOM >BOM.

4. Define the BOM for the ATO Model. Assign the optional component to the
operation as required.

5. In the Operation Resources window, enter the time (in hours) that a resource is
required for that operation.
You can view the calculated resource hours in the Resource Requirements window.
The Auto-create configuration process creates the configured item's bill of material
with only the specified options. In the same way, it creates the configured item's
routing with only those operations that are mandatory and the option specific
operations linked to the options that you select. Oracle Global Order Promising
creates a temporary bill of material and routing in the same way as Auto-create
configuration process.

Note: Oracle Global Order Promising uses pre-calculated lead time
for a model and does not roll-up the lead time based on selected
options.

For details on Auto-create Configuration process, see Oracle Configure to Order User
Guide.

Global Availability
If an ATO Model can be sourced from multiple shipping warehouses, Oracle Global
Order Promising recommends a shipping warehouse based on the availability in each
of the warehouses.
For details about setting up sourcing rules for shipping warehouses, see:
Single-Level Supply Chain ATP, page 3-2 or, Multi-Level Supply Chain ATP, page 4-2.


Infinite Time Fence
Oracle Global Order Promising honors the infinite time fence for an ATO Model. The
Model must have either the Check ATP attribute or Component ATP attribute enabled
or both the attributes enabled.

Supplier Capacity for Procured Model
You can constrain procured configurations based on the aggregate capacity available
for the base Model of the configuration. This means that you can state the capacity for
the supplier-supplier site in terms of how many of the base ATO Model can be built.
Oracle Advanced Supply Chain Planning constrains all planned orders, requisitions,
and purchase orders of all configurations of a base Model to its aggregate capacity
value. Planned orders for the ATO item will also consume this aggregate capacity.
Oracle Global Order Promising checks the supplier capacity defined for the base Model
when scheduling a sales order for the Model.

Consistent Interface to All Calling Applications
Any application that attempts to interface with Oracle Global Order Promising for
models (ATO or PTO) needs to send the Model and selected options to Oracle Global
Order Promising. Oracle Global Order Promising does the following:
• For ATO Model, it will derive the standard mandatory components

• For PTO Model, the calling application has the choice of either having Oracle
Global Order Promising derive the included items or pass the included items to
Oracle Global Order Promising.

Examples
Matching to Existing Configuration
The ATO Model is as follows:

Level Item Check ATP Component ATP Item Type Op
Seq

0 Laptop X11 - Material & Model
Resouce

1 - Base System Material Material Standard 10
mandatory
component


Seq

2 -- Board - - Component of 10
standard
mandatory
component

2 -- Network card Material - Component of 10
standard
mandatory
component

2 -- Graphics card - - Component of 10
standard
mandatory
component

1 - Processor Class - Material Option class 10

2 -- Mobile Material - Optional item 10
Pentium® 4 2.2
GHz

Pentium® 4 2.8
GHz

Pentium® 4 3.4
GHz

1 - Memory Class - - Optional item 10

2 -- 256 MB - - Optional item 10

2 --512 MB - - Optional item 10

1 - Monitor Class - - Option class 10

2 --15.4'' Display - - Optional item 10



Seq


1 - Modular Drive - Material Option class 20
Class

2 -- 24X Material - Optional item 20
CD-RW/DVD
Combo

The routing is as follows:

Item Operation Seq Option Res urce Usage Basis Offset
Dep

Laptop X1 10 No Assembler 3hr Item 0%

Laptop X1 20 Yes Tester 1hr Item 80%

Process Class Common - - - - -
routing to
Laptop

Memory Common - - - - -
Class routing to
Laptop

Monitor Common - - - - -
Class routing to
Laptop

Modular Common - - - - -
Drive Class routing to
Laptop

Both the resources, Assembler and Tester, have the Capable-to-Promise flag enabled.
Lead Time


Item Fixed Lead Time Variable Lead Time

Laptop X1 0 0.11 day

Base System 0 0.01 day

Existing Configuration Item
There is an existing configuration item Laptop X11*23694 for base Model Laptop X11. It
has the following bill of material:
Laptop X11*23694
Base System
Board
Network card
Graphics car
Mobile Pentium 4 2.2 GHz
256 MB
14.1'' Display
Laptop X11
Process Class
Memory Class
Monitor Class
It has the following routing:

Item Operation Option Dep Resource Usage Basis
Seq

Laptop X11*23694 10 No Assembler 3hr Item

is as follows:

Item/Resource Day 1 Day 2 Day 3

Base System 10 5 10


Item/Resource Day 1 Day 2 Day 3

Network Card 8 10 15


Mobile Pentium® 4 2.8 GHz 10 20 30

Mobile Pentium® 4 3.4 GHz 10 20 30


Laptop X11*23694 5 0 0

Assembler 10 20 30

Tester 10 20 30

A sales order comes with a request date of Day 1 for a quantity of 10 units, with the
following selected options:
• Mobile Pentium 4 2.2 GHz

• 256 MB

• 14.1'' Display

Oracle Global Order Promising processes the order as follows:
1. A matched configuration Laptop X11*23694 is found for the order. (Assuming the
matching profile is turned on.)

2. The matched configuration item is used for checking availability.

3. On Day 1, there is availability of 5.

4. In order to make 5 unit of the configuration, it will take 1 day = CEIL(0 + 5 *0.11).
The components must be available on Day 0 in order to make the end assembly
item. Since, Day 0 is past due, the remaining quantity cannot be manufactured on
Day 1. ATP now tries to project the date when the remaining quantity could be
manufactured.

5. There is enough availability of the Base System, Mobile Pentium 4 2.2 GHz on Day
1.


6. The sales order can be promised on Day 2.

An ATP Inquiry for the above order shows you the following in the ATP Details
window, summary region:

Item Matched Configuration Request Date Ship Date Days Late
Qty

Laptop X11 Laptop X11*23694 5 Day 2 1

Mobile - - Day 2 0
Pentium 4 2.2
GHz

256 MB - - Day 2 0

14.1'' Display - - Day 2 0

Explanation:
• The Days Late field shows the difference between the date the item is required and
date the item is available. It is applicable for every line.

• There are many fields in the summary region. Some fields such as Request Date
Qty, Schedule Ship Date, Schedule Arrival Date, and Org are only meaningful for
the ATO Model line.

• The pegging region shows the pegging for the matched configuration item. For
further information on how Oracle Global Order Promising displays the pegging,
see ATP Inquiry.

No matched configuration is found
The ATO Model for this example is the same as used in Example, page 4-46.
A sales order comes with request date of Day 1 and the following selected options:
-Mobile Pentium 4 2.2 GHz
-256 MB
-14.1'' Display
- 24X CD-RW/DVD Combo
Oracle Global Order Promising processes the order as follows:
1. No match is found. (Assume that the profile BOM: Match to Existing Configuration
is set to Yes.)

2. Temporary bill of material and routing are created for the configuration. These are


used during capable-to-promise calculation.

The temporary bill of material is as follows:
Temporary configuration item
Base System
Board
Network card
Graphics car
Mobile Pentium 4 2.2 GHz
256 MB
14.1'' Display
Laptop X11
Process Class
Memory Class
Modular Drive Class
The temporary routing is as follows:

Item Operation Option Dep Resource Usage Basis
Seq

Temp 10 No Assembler 3hr Item

- 20 Yes Tester 1hr Item

1. In order to make 10 units of the configuration, it will take 2 day = CEIL(0 + 10 *0.11).
The earliest possible promise date would be Day 3.

2. The availability picture is:
• The Base System, Mobile Pentium 4 2.2 GHz is available on Day 1.

• 24X CD-RW/DVD Combo is available only on Day 2.

• The resource Assembler is required on Day 1 and is available on Day 1.

• The resource Tester is required on Day 2 and is available on Day 2.

3. A job can only start on Day 2 due to 24X CD-RW/DVD Combo availability, and
takes 2 days to finish. Therefore, the sales order can be promised on Day 4.


4. After scheduling the above sales order, a sales order demand is placed for the ATO
Model. A planned order demand is placed for the atpable standard mandatory
components and optional items. Resource requirement are placed for ctpable
resources.

Unscheduling or canceling a sales order
Note that the data used in this example are independent from the data used in the
previous examples.
The supply demand detail from the ATP plan is as follows:

Item Order Type Qty Order Num

Laptop X11*23694 Sales Orders -10 12345

- Planned Order 10 0

Base System Planned Order Demand -10 0


Mobile Pentium 4 2.2 GHz Planned Order Demand -10 0


There is a resource requirement of 30 hours on day 3 due to the planned order of
Laptop X11*23694.
Pegging for the above supply demand from the ATP plan:
Laptop X11*23694 Qty 10 on Day 3 (Sales Order 12345)
Laptop X11*23694 Qty 10 on Day 3 (Planned order)
Op 10 Assembler Qty 30 on Day 2
Base System Qty 10 on Day 2 (Planned order demand)
Base System Qty 10 on Day 2 (Planned order)
Mobile Pentium 4 2.2 GHz Qty 10 on Day 2 (Planned order demand)
Mobile Pentium 4 2.2 GHz Qty 10 on Day 2 (Planned order)

Note: The pegging is illustrated conceptually. Not all the details or lines
are shown.

Based on the plan output, ATP picture is as follows:


Item/Resource Supply/Demand Day 1 Day 2 Day 3

Laptop X11*23694 Supply 0 0 10

- Demand 0 0 -10

- Net ATP 0 0 0

Base System Supply 0 10 0

- Demand 0 -10 0

- Net ATP 0 0 0

Mobile Pentium 4 2.2 GHz Supply 0 10 0

- Demand 0 -10 0

- Net ATP 0 0 0

Assembler Supply 0 50 0

- Demand 0 -30 0

- Net ATP 0 20 0

If the above sales order is unscheduled or cancelled, Oracle Global Order Promising
make the following supply demand adjustments to the plan based on pegging
information in the plan:


Laptop X11*23694 Sales Orders 0 12345

- Planned Order 10 -

- Order Scheduling -10 -
Adjustment

Base System Planned Order Demand -10 -




- Order Scheduling 10 -
Adjustment

Mobile Pentium 4 2.2 GHz Planned Order Demand -10 -


Adjustment

Assembler Planned Order -30 -

Adjustment

ATP picture will be:


Laptop X11*23694 Supply 0 0 0

- Demand 0 0 0

- Net ATP 0 0 0

Base System Supply 0 10 0

- Demand 0 0 0

- Net ATP 0 10 0

Mobile Pentium 4 2.2 Supply 0 10 0
GHz

- Demand 0 0 0

- Net ATP 0 10 0



Assembler Supply 0 50 0

- Demand 0 0 0

- Net ATP 0 50 0


Multi-Level Multi-Org ATO

Supply Chain Bill

Sourcing relationships are shown in dotted lines and the BOM relationships are shown
in continuous lines. The BOM and the sourcing is defined using Oracle Bills of Material
and Oracle Supply Chain Planning or Oracle Advanced Planning Solution. You can find
the item names within each of the nodes. The item name is followed by a two-letter
code to identify the organizations.


CMP MainFrame has four configurable ATO Model assemblies: PCI module, Dual Pod
Enclosure, Sub Prod 32, and Sub Prod 64. The company sells CMP MainFrames from its
shipping organizations at Boston and Singapore. It has three manufacturing sites: Hong
Kong, Mexico, and Boston. CMP MainFrames are assembled in Boston and Hong Kong.
The PCI module is manufactured and sourced at the Mexico facility. Dual Pod
Enclosures are manufactured and sourced at Hong Kong along with the components
Sub Prod32 and Sub Prod64. Optional items CD ROMs, DAT Drives, and Tape Drives
can be sold as spares from either Boston or Hong Kong.
An order is accepted at the Singapore organization with the following selected options:
1. CMP MainFrame

2. CD-ROM

3. PTN32-2MB

4. 32TLC Add-On

5. 5V Card

The following table shows the ATP item attributes setting:

Item Org Check ATP Component ATP

CMP MainFrame SG - Material

CMP MainFrame HK - Material

Console HK Material -

P Devices HK - -

CD ROM HK Material -

PCI Module HK - -

PCI Module MEX - -

Cables MEX - -

PCI Cards MEX - -

5V Card MEX - -


Item Org Check ATP Component ATP

Compatibility Bridge MEX - -

Dual Pod Enclosure HK - -

Sub Prod OC HK - -

Power Supply HK - -

Sub Prod 32 HK - Material

PTN-32 OC HK - Material

PTN32-2MB HK Material -

TLC1032 HK - -

32TLC Add-On HK Material -


Item Org Day 1 Day 2 Day 3 Day 4 Day 5

Console HK 10 20 30 30 30

CD ROM HK 10 15 30 30 30

PTN32-2MB HK 20 30 30 40 40

32TLC Add-On HK 12 12 30 30 30

Lead time setup:
• There is transit lead time of 1 day between all the organizations.

• CMP MainFrame (HK) lead time: fixed lead time = 0 and variable lead time = 0.05
day.

• Dual Pod Enclosure lead time: fixed lead time = 0 and variable lead time = 0.05 day.


• Routing is not shown in this example. Assume that resource capacity check is not
needed.

A sales order for the above configuration for quantity of 10 on Day 5 can be promised
on Day 5.
An ATP inquiry for the above order will show the following result in the ATP Details
window:

Item Matched Org Request Date Ship Date Days Late
Configuration Qty

CMP - SG 10 Day 5 0
MainFrame

CD-ROM - SG 0 Day 5 0

PTN32-2MB - SG 0 Day 5 0

32TLC - SG 0 Day 5 0
Add-On

5V Card - SG 0 Day 5 0

The Org field only shows the shipping organization for the top ATO Model.
ATP Pegging shows the following result:
1 (D) CMP MainFrame - Org SG Qty 10 On Day 5
2 (S) CMP MainFrame - Transfer From Org HK Qty 10 On Day 5
3 (D) CMP MainFrame - Org HK Qty 10 on Day 4
4 (S) CMP MainFrame - Make At Org HK Qty 10 on Day 4
5 (D) Console - Org HK Qty 10 on Day 3
6 (S) Console - Org HK Qty 30 on Day 3
7 (D) P devices - Org HK Qty 10 on Day 3
8 (D) CD ROM - Org HK Qty 10 on Day 3
9 (S) CD ROM - ATP Org HK Qty 30 on Day 3
10 (D) Dual Pod Enclosure - Org HK Qty 10 on Day 3
11 (S) Dual Pod Enclosure - Make At Org HK Qty 10 on Day 3
12 (D) Sub Prod - Org HK Qty 10 on Day 2
13 (D) Sub Prod 32 - Org HK Qty 10 on Day 2


14 (S) Sub Prod 32 - Make At Org HK Qty 10 on Day 2
15 (D) PTN 32 OC - Org HK Qty 10 on Day 1
16 (D) PTN32-2MB - Org HK Qty 10 on Day 1
17 (S) PTN32-2MB - ATP Org HK Qty 20 on Day 1
18 (D) 32 TLC Add-On - Org HK Qty 10 on Day 1
19 (S) 32 TLC Add-On - ATP Org HK Qty 12 on Day 1
Explanation:

• Option classes appear on the same level as its components. They are treated as
phantom items.

• Since there is 1 day transfer lead time, the demand line below the Transfer From
supply lines reflect the 1 day lead time offset.

• The demand pegging line for the components of an ATO Model reflect the lead time
offset of the Model. For example, the lead time for 10 units of CMP MainFrame =
round (0 + 0.05 * 10) = 1 day. In order to make 10 units of CMP MainFrame on Day
4, Console is needed on Day 3. Line 5 reflects that.

Demand Flow
Upon scheduling a sales order, Oracle Global Order Promising inserts demand for
items that have Check ATP and Component ATP enabled into the ASCP plan used for
ATP purpose. The demand picture of the above example is after scheduling:

Item Org Check ATP Component ATP Demand

CMP MainFrame SG - Material Sales Order

CMP MainFrame SG - - Planned Order

CMP MainFrame HK - Material Planned Order
Demand

CMP MainFrame HK - - Planned Order

Console HK Material - Planned Order
Demand


Item Org Check ATP Component ATP Demand

P Devices HK - - None

CD ROM HK Material - Planned Order
Demand

PCI Module HK - - None

PCI Module MEX - - None

Cables MEX - - None

PCI Cards MEX - - None

5V Card MEX - - None

Compatibility Bridge MEX - - None

Dual Pod Enclosure HK - - Planned Order
Demand

Dual Pod Enclosure HK - - Planned Order

Sub Prod OC HK - - None

Power Supply HK - - None

Sub Prod 32 HK - Material Planned Order
Demand

Sub Prod 32 HK - Material Planned Order

PTN-32 OC HK - Material None

PTN32-2MB HK Material - Planned Order
Demand

TLC1032 HK - - None

32TLC Add-On HK Material - Planned Order
Demand


Model 1 has three options: Option 1, Option 2 and Option 3.

Option Specific Sourcing Structure

M1, M2, M3 denote the manufacturing organization. S1 denotes a supplier.


• If an order for Model 1 only has option 3, the valid sources would be M1 and S1.

• If an order for Model 1 has option 1 and option 2, the only valid source would be
M1.

• If the new item creation attribute is set to Based on Model, the item is created in M1
and the Order Management validation organization.

• The bill of material and routing is created in M1 only.

• New sourcing is created and assigned to the configuration item.

• If no valid source is found based on the options selected and option specific
sourcing setup, Oracle Global Order Promising will show an error and will not
schedule the sales order.

PTO Model
Front-end applications such as Oracle Order Management and Oracle Configurator are
used to configure a PTO Model. When the PTO Model has Ship Model Complete
checked, Oracle Order Management groups the PTO Model, selected option class,
included items, and selected optional items into a set for ATP check. Otherwise, Oracle
Order Management treats each PTO line with included items and selected options
independently for availability check.

Setup
Refer to the Setting Up, page 2-1 chapter for the mandatory and optional setup steps.


ATP Item Attributes
• Set the Check ATP item attribute.

• The Component ATP is not relevant for PTO Model and option classes.


PTO Model • None Material Only

Option Class • None Materail Only

Included Item • Material • Material


• Resource

• None

• None



Resource • None

• None

Examples
PTO Model has Ship Model Complete set to Yes
A sales order has items with options. The ATP item attributes for these items are shown
below:


0 Laptop X11 Deluxe - Material



1 - Laptop X11 - Material

2 - - Base System Material -

3 - - - Board - -

3 - - - Network Card Material -

3 - - - Graphics Card - -

2 - - Processor Class - -

3 - - - Mobile Pentium®4 Material Yes
2.2 GHz

2 - - Memory Class - -

3 - - - 256 MB - -

2 - - Monitor Class - -

3 - - - 19in Flat Screen - -

2 - - Modular Drive Class - -

3 - - - 24X CD - RW/DVD Material Yes
Combo

1 - External Mouse - -

2 - - Logitech Optical Material Yes
Mouse

1 - Laptop Case Material Yes

The cumulative availability picture for the items that have Check ATP attribute set is
described as follows:



Base System 0 5 10

Network Card 8 10 15



Logitech Optical Mouse 0 0 20

Laptop Case 10 20 30

Aa sales order demand in the above configuration for a quantity of 10 with a request
date of Day 3 can be promised on Day 3.
window:

Configuration Qty

PTO Model line - 0 - 0



Base System - 0 Day 3 0

Processor Class - 0 Day 3 0

Mobile Pentium®4 - 0 Day 3 0
2.2 GHz

Memory Class - 0 Day 3 0

256 MB - 0 Day 3 0

Monitor Class - 0 Day 3 0


Configuration Qty

19in Flat Screen - 0 Day 3 0

Modular CD/DVD - 0 Day 3 0
Drive

24X CD-RW/DVD - 0 Day 3 0
Combo


Mouse


Explanation:
• Request Date Qty reflects the supply available on the date the items are needed.

• Since, all the items are available on Day 3, the sales order can be promised on Day 3.

PTO Model has Ship Model Complete set to No
In this case, each individual line can be shipped on the Ship Date.
window:

Configuration Qty

PTO Model line - 0 - 0



Base System - 0 Day 3 0

Processor Class - 0 Day 3 0


Configuration Qty

Mobile Pentium®4 - 0 Day 3 0
2.2 GHz

Memory Class - 0 Day 3 0

256 MB - 0 Day 3 0

Monitor Class - 0 Day 3 0

19in Flat Screen - 0 Day 3 0

Modular CD/DVD - 0 Day 3 0
Drive

24X CD-RW/DVD - 0 Day 3 0
Combo


Mouse


ATO Item

Setup
Verify that you have performed the mandatory and optional setup steps explained in
the Setup chapter.

ATP Item Attributes
Oracle Global Order Promising treats an ATO Item like a standard item. The following
setting is supported:
• The ATO Item is forecasted and planned. There is statement of supply for the ATO
item. Oracle Global Order Promising for the ATO Item is based the supply for the
ATO Item. In this case, the ATO Item is similar to a standard item from order
promising point of view. The ATO aspect significance is on the transactional side.


You should enable Check ATP Flag for the components of the ATO Item.


ATO Item (Standard) • Material Only • Material


• Resource

• None

- Components (Standard) • Material Only • Material


• Resource

• None

Oracle Global Order Promising first checks the availability of the ATO Item. If there is
not enough supply, it goes to its components to perform capable-to-promise check
based on the Component ATP for the ATO Item.

Examples
Using an ATO Item
The ATP Item attributes for the items are shown below:


Laptop X11-1 Material Material

- Base System Material -

- Mobile Pentium®4 2.2 GHz Material -

- 512 MB - -

- 17in Flat Screen - -



- 24X CD-RW/DVD Combo - -
Material



Laptop X11-1 1 1 1

Base System 10 20 30



Laptop X11-1 lead time:


An ATP inquiry for a sales order demand of the ATO item for quantity of 10 with

Configuration Qty

Laptop X11-1 - 10 Day 2 0

ATP Pegging shows the following:
(D) Laptop X11-1 - Org Qty 10 On Day 2
(S) Laptop X11-1 - ATP Org Qty 1 On Day 2
(S) Laptop X11-1 - Make At Org Qty 9 on Day 2
(D) Base System - Org Qty 9 on Day 1
(S) Base System - Org Qty 10 on Day 1


(D) Mobile Pentium®4 2.2 GHz - Org Qty 9 on Day 1
(S) Mobile Pentium®4 2.2 GHz - Org Qty 10 on Day 1

Kit
A kit, also known as a PTO Item, is a standard item with Pick Component item attribute
checked. When an order is created in Oracle Order Management for a PTO item, Oracle
Order Management explodes the next level components of the PTO item and groups the
items into a set and passes the set to Oracle Global Order Promising for availability
check.

Setup
Refer to the Setting Up, page 2-1 Chapter for the mandatory and optional setup steps.

ATP Item Attributes
Oracle Global Order Promising supports the following ATP item attribute setting for
Kit:
1. Check availability for the Kit.


PTO Item (Standard) Material None

- Next Level Components None None
(Standard)

2. Check availability for the components of the Kit.


PTO Item (Standard) None • None

- Next Level Components Material • Material
(Standard)

• Resource

• None


Oracle Global Order Promising checks the availability for the components on the
request date of the PTO item. Oracle Global Order Promising returns a Ship Date that is
either the request date or a later date if any ATP-able items are not available.

Examples
Using a PTO Item
The ATP item attributes for the items are shown below:


0 External Speaker - -

1 - Premium Speaker Material -

1 - Speaker Manual Material -



Premium Speaker 0 0 10

Speaker Manual 10 10 10

An ATP inquiry for a sales order demand of the PTO item for quantity of 10 with
window:

Configuration Qty

External Speaker - 10 Day 2 0

Premium Speaker - 0 Day 3 1

Speaker Manual - 10 Day 2 0


Product Family ATP
Oracle Manufacturing lets you define product family item as a percentage composition
of member items. If the product family item is setup to perform ATP based on product
family, then once an ATP Inquiry is launched for a member item the ATP is actually
performed against the product family item. Since Oracle Advanced Supply Chain
Planning lets you plan for such items, you can define Bills of Resources to check and
verify the available capacity for capable-to-promise for your critical resources.

Note: With the current setup for Product Family ATP, for a given item
you can either perform ATP:
• Based on product family item

• Or based on the individual member items

If ATP is based on planning output, Oracle Global Order Promising views the entire
planning horizon and does not differentiate between the various buckets and
aggregation you have defined for the ATP enabled plan.

In a customer driven manufacturing environment, it may not always be possible to
forecast exact demand of the end item. However, it may be possible to define aggregate
requirements and forecast at an aggregate level, instead of at the item level. This is
shown in the following diagram:

Product Family Item Aggregation

When an order is scheduled for ATP based on planning data, the sales order is
scheduled against the product family item. After data collection and plan rerun, the
sales order demand for the member item is present in the plan where the member items
are planned.


Setup
Once you defined product family item and the product family item / member item
relationship, you need to perform the following setup to enable ATP based on Product
Family.

Check ATP Item Attribute
It needs to be set to Material for product family item in order to perform Product
Family ATP.
You must set the Check ATP flag for all the member items to be Material when using
Product Family ATP. Otherwise, an incorrect result can occur. This is because the
demand and supply for product family is an aggregation of the demand and supply of
the member items.

Component ATP Item Attribute
The product family item can be set to:
• Resource only: check material availability for item at this level. System performs
CTP if ATP is based on planning data.

Note: Material and Material & Resource options are not
supported for product family items.

When ATP is based on the product family level, the Component ATP flag for the
member items is not a factor in the setup.

ATP Logic
1. If the requested item is not a member of a product family item, go to step 2.
Otherwise go to step 3.

2. ATP is performed on requested item. For details, see: ATP Logic, page 6-19. End.

3. If Check ATP item attribute for the product family item is set to None, go to step 2.
Otherwise go to step 4.

4. If product family item is found in multiple plans, then use the plan that serves as
feeder plan to the other. For example, if an MPS plan feeds into an MRP plan and
product family item exists in both the plans, Oracle Global Order Promising uses
the MPS plan.

5. If there is enough cumulative supply for the product family item, then ATP


succeeds. The request date is the ATP date. End. Otherwise go to next step.

6. If Component ATP flag is set to Resource, then go to next step. Otherwise, perform
forward scheduling. Go to step 8.

7. If MPS plan is used, then use Bills of Resource for capacity check. If MRP plan is
used, then use routing for capacity check. If there is sufficient capacity to build the
shortage, then ATP succeeds, otherwise perform forward scheduling. Go to step 8.

8. Perform Forward Scheduling. For details, see: Forward Scheduling, page 4-13.

Capable-To-Promise for Product Family Item
When product family is in an MPS plan, you define Bills of Resource (BOR) for product
family item. If you set Component ATP item attribute for the product family item to
Resource, Oracle Global Order Promising uses Bills of Resource for capable-to-promise
check.
When product family is in MRP plan, you define routing for product family item.
However if member items also exist in MRP plan and have routing defined, you should
not define routing for product family item because that will load resource twice if same
resources are used in both routing. Thus, you should set Component ATP item attribute
for the product family to None.

Examples
Member Items and the Product Family Item in the Same Plan
Planning uses the ATP enabled plan for ATP Inquiry and sales order scheduling, as
long as the plan contains the product family demand and supply. When the product
family item and members are part of the same plan and the plan is ATP enabled then
ATP uses this plan for the inquiry and order scheduling.
Assume the plan you use is an MRP plan. Product family item is PF1 with member
items A at 50% and B at 50%. The Item Aggregation bucket in the plan is set to Item for
all buckets.
Supply / Demand picture in the plan is the following:

Category Item Order Type Date Quantity

Demand PF1 Forecast Day X 100

Supply PF1 Planned Order Day X 100


Category Item Order Type Date Quantity

Demand A Product Day X 50
Family/Model/O
C Dependent
Demand

Supply A Planned Order Day X 50

Demand B Product Day X 50
Family/Model/O
C Dependent
Demand

Supply B Planned Order Day X 50

Availability picture for PF1 is as follows:

Category Item Day X

Supply PF1 100

Demand PF1 0

Net PF1 100

Cum PF1 100

A sales order (1001) for member item B for 60 units on Day X. Oracle Global Order
Promising promises the order based on product family item (PF1) availability picture.
After scheduling, Supply / Demand picture is the following:

Category Item Order Date Quantity


Demand PF1 Sales Order Day X 60
Number 1001




Family/Model/
OC Dependent
Demand


Family/Model/
OC Dependent
Demand


After you rerun the plan, the Supply / Demand picture shows:


Demand PF1 Sales Order Number Day X 60
1001



Demand B Sales Order Number Day X 60
1001


Family/Model/OC
Dependent Demand


Family/Model/OC
Dependent Demand




Member Item and the Product Family Item in Separate Plans
This is the scenario where product family item is planned in an MPS plan while
members are planned in an MRP plan. MPS plan feeds into MRP plan. The product
family item exists in both plans. Oracle Global Order Promising uses the MPS plan for
promising.
For example, item A is a MRP planned item and item PF1 is a MPS planned item. You
generate a production plan and feed the production plan as a demand schedule to a
manufacturing plan. Suppose both the plans are ATP enabled. If you choose to perform
ATP using Product family item then the production plan will be used for ATP inquiry
and sales order scheduling.
Assume product family item is PF1 with member items A (50%) and B (50%).
The Supply / Demand picture in the MPS plan is the following:




The Supply / Demand picture in the MRP plan is the following:




Family/Model/OC
Dependent Demand




Family/Model/OC
Dependent Demand


A sales order (1001) for member item B for 60 units on Day 1. Oracle Global Order
Promising is able to promise the order based on product family item (PF1) availability
in the MPS plan. After scheduling, Supply / Demand picture is the following:
The Supply / Demand picture in the MPS plan is the following:




Demand PF1 Sales Order 1001 Day X 60

The Supply / Demand picture in the MRP plan is the following:




Demand A Product Family/Model/OC Day X 50
Dependent Demand


Demand B Product Family/Model/OC Day X 50
Dependent Demand


After you rerun the plan, the Supply/ Demand picture in the MPS plan is:





Demand PF1 Sales Order 1001 Day X 60

The Supply / Demand picture in the MRP plan is:


Demand PF1 Sales Order Day X 60
Number 1001



Demand B Sales Order Day X 60
Number 1001


Family/Model/OC
Dependent Demand


Family/Model/OC
Dependent Demand


For detailed explanation on planning logic, see: Planning Logic, Oracle Advanced
Planning and Scheduling User's Guide.

Combined Item-Product Family ATP
Oracle Global Order Promising supports time-phased order promising where you can


promise orders by checking the availability of a requested item within an aggregate
time fence and beyond that, you can use the product family to which the requested item
belongs.
Aggregate time fence is a time period beyond which Oracle Global Order Promising
switches between end items and product family items using the ATP rule.

Oracle Global Order Promising allows you to perform order promising using the
requested item's availability in the short term and aggregate availability (sum of all
members' availability) in the long term.
This provides you flexibility to accommodate high demand variations in order
promising. It also allows sufficient lead time for preparing the actual product
combination. You can take advantage of aggregate supplies beyond a well-defined time
period in the planning horizon, where end items are interchangeable within the product
families.

Setup
You need to perform the following setup steps:
1. In Inventory > Setup > Rules > Available To Promise > ATP Rules window, set the
Aggregate Order Promising Time Fence to one of the following:
• None - Oracle Global Order Promising uses the product family for order
promising across the planning horizon.

• Demand Time Fence - Within the demand time fence, Oracle Global Order
Promising uses the end-item for order promising, and beyond the time fence, it
uses the product family item.

• Planning Time Fence - Within the planning time fence, Oracle Global Order

• User Defined - Within the user defined time fence, Oracle Global Order
You need to assign this ATP rule to a product family item.

2. Run an ATP plan with forecast either at item level or product family level.
After the plan run, the ATP post plan processing is automatically launched.

Note: If you run the plan with the ATP flag unchecked and then


check the ATP flag, you need to manually run the ATP Post Plan
Processing concurrent program.

Using Combined Item-Product Family ATP with Allocated ATP
If you wish to use Combined Item-Product Family ATP with Allocated ATP, you need
to perform the following setup steps:
1. The allocation rules have to be valid throughout the planning horizon/infinite time
fence.
Oracle Global Order Promising does not support invalid rules. For example, the
allocation rule for a member item is valid from day 1 to day 5 but the allocation rule
for the product family item is valid from day 5 to day 10, and then the allocation
rule for the member item is valid again from day 10 to end of planning horizon.
Oracle Global Order Promising will consider this as an invalid rule.

2. Define the allocation rule at the product family level.
If you define the allocation rule only at member item level, you may receive
unpredictable results.

3. For percentage based allocation, you can choose to define the allocation rule at the
member item level or not.

The following section explains various scenarios and valid allocation rule setup if you
intend to use combined item-product family ATP and allocated ATP.

Percentage based allocation
• Allocation rule defined only at the member item level (No allocation rule for the
product family item)
This setup is not recommended due to unpredictable results. (ATP will not error
out but generate erroneous results)

• Allocation rule defined only at the product family item level
For example, the product family item has a rule valid through the planning horizon.

• Allocation rules defined for both the member and product family item
For example, member1 has rule AllocM1 and member2 has rule AllocM2 and the
product family has rule AllocPF valid through the planning horizon.

Oracle Global Order Promising uses the allocation rule for the demanded member item
till the aggregate time fence (AllocM1 or AllocM2) beyond which it uses the product
family allocation rule (AllocPF).


Note: Under this allocation method, the allocation hierarchy and
priority must be the same in member item's rule and product family
item's rule.

Demand Priority based allocation
• Allocation rule defined only at the member item level (No allocation rule for the
Allocation rule defined only at the member item level (No allocation rule for the
product family item)
This setup is not recommended due to unpredictable results. ATP will not error out
but generate erroneous results.

• Allocation rule defined only at the product family item level
For example, the product family item has rule ALLOCPF valid through the
planning horizon.

• Allocation rules defined for both for the member and product family item

• Oracle Global Order Promising disregards the allocation rule for the demanded
member item and uses the product family allocation rule for the entire planning
horizon.

ATP Logic
With this feature, Oracle Global Order Promising divides time horizon into two regions:
item region and product family region. In the item region, supply and demand is at
item level. In the product family region, supply and demand are the sum of all the
member items for the product family item.

Demand Spread Calculation
In order to keep track of the proper supply consumption inside and outside the
aggregate time fence, Oracle Global Order Promising uses a pseudo demand called the
product family demand spread. The product family demand spread is used to divide
the actual demand into a maximum of two portions representing the region where the
supplies satisfying the actual demand lie - one inside the aggregate time fence and one
outside the aggregate time fence.
• If the actual demand is outside the aggregate time fence date (ATF Date), then the
portion inside the time fence shows up on the ATF Date. The portion outside the
aggregate time fence shows up on the same date as the actual demand date.

• If the actual demand is inside the ATF Date then the portion inside the time fence
shows up on the actual demand date. The portion outside the aggregate time fence


shows up on the ATF Date.

The quantities of these portions equal the amount of supplies consumed by this
demand from the respective time regions. This enables the rest of availability
calculation (net availability, backward consumption) to be computed correctly.
You can view the product family demand spread and the aggregate time fence date in
the Horizontal Plan and View Allocation Workbench windows.
Between plan runs, when scheduling a new sales order demand, ATP calculates the
product family demand spread as follows - when a demand exceeds the cumulative
supply on the request ship date, Oracle Global Order Promising consumes the item
supply upto the request ship date. For the shortage, it consumes supplies as close to the
demand due date as possible.
For further illustration on how the Product Family Demand Spread is calculated, see the
example.

Net Availability Calculation
Oracle Global Order Promising first calculates the net for each bucket for both the
member items and the product family. The net is based on the demand spread values
and not on the actual demand.

Backward Consumption and Forward Consumption Calculation
Backward consumption and forward consumption takes place independently inside the
two regions based on the net availability.

Cumulative Supply
Cumulative supply is calculated daily. After the aggregate time fence (ATF) date, the
item's cumulative supply is added onto the product family numbers to yield the
product family cumulative supply.

Demand Spread Calculation After Plan Runs
After plan runs, Oracle Global Order Promising refreshes the supply and demand
picture as well as re-calculates the product family demand spread based on the plan
pegging.
• If a portion of the demand is satisfied using (pegged to) the supply inside the
aggregate time fence (ATF) date, that portion of the demand will contribute to the
product family demand spread quantity inside the aggregate time fence (ATF) date.

• If a portion of the demand is satisfied using (pegged to) the supply outside the
aggregate time fence (ATF) date, that portion of the demand will contribute to the
product family demand spread quantity outside the aggregate time fence (ATF)
date.


Capable-To-Promise
Oracle Global Order Promising performs a capable-to-promise check based on the
requested item's bill of material (BOM) and routing. If the supply is created outside the
aggregate time fence (ATF), the supply rolls up to the product family level so that it is
available for the consumption at the product family level.

Allocated ATP
• Allocated ATP based on user-defined allocation percentage: Oracle Global Order
Promising applies the allocation percentage to an item's supply inside the aggregate
time fence (ATF) and allocation percentage to aggregate supply outside the
aggregate time fence (ATF). For details on the logic used for the allocation based
percentage, see: Percentage based allocation, page 4-82.

• Allocated ATP based on demand priority: The supply and demand are allocated to
the corresponding demand class based on the end demand's demand class. Beyond
the aggregate time fence (ATF), the supply and demand are aggregated by the
demand class.

ATP Override
Oracle Global Order Promising calculates the demand spread during ATP override as
follows:

Scenario 1
When the request ship date and the demand satisfied date are both within the aggregate
time fence, there will be a single spread demand with the complete quantity on the
request ship date.

Scenario 2
When the request ship date is inside the aggregate time fence but the demand satisfied
date is outside the aggregate time fence, there are two demand spreads:
• On the request ship date with the quantity equal to the cumulative quantity on the
aggregate time fence date

• The balance quantity is spread to the day after the aggregate time fence date

If the cumulative quantity on the aggregate time fence date is 0, Oracle Global Order
Promising places a single demand spread on the day after the aggregate time fence date

Scenario 3
When the request ship date and demand satisfied date are both outside the aggregate
time fence, there are two demand spreads:


• On the aggregate time fence date with quantity equal to the cumulative quantity on
the aggregate time fence date

• The balance quantity is spread to the request ship date.

If the cumulative quantity on the aggregate time fence date is 0, Oracle Global Order
Promising places a single demand spread on the request ship date.

Examples
Here are a few examples to illustrate how the combined item-product family ATP
feature works.
Demand Spread Calculation
This example illustrates how Oracle Global Order Promising performs demand spread
calculation in various scenarios. For all the scenarios described below, the aggregate
time fence (ATF) date is Day 5.
Scenario 1
A sales order has the request ship date inside the aggregate time fence (ATF) date and is
scheduled to ship inside the aggregate time fence (ATF) date.
The initial ATP picture is:
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Supply
10
10
10
10
10
50
50


50
50
Demand
0
0
0
0
0
0
0
0
0
Product Family Demand Spread
0
0
0
0
0
0
0
0
0
Net
10
10
10
10
10
50
50
50
50


Cum
10
20
30
40
50
100
150
200
250
Oracle Global Order Promising schedules a sales order with the request ship date of
Day 2 for quantity 110, on Day 7.
The ATP picture after the sale order is scheduled:
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Supply
10
10
10
10
10
50
50
50
50


Demand
0
0
0
0
0
0
-110
0
0
0
0
0
0
-20
0
-90
0
0
Net
10
10
10
10
-10
50
-40
50
50
Cum
10


20
30
30
30
40
40
90
140
Explanation:
• On the request ship date (Day 2), there is cumulative item availability of 20. There is
a shortage of 90.

• The product family demand spread inside the aggregate time fence date will be -20
at this point.

• Oracle Global Order Promising performs forward scheduling to look for the date
where the shortage can be covered.

• The shortage can be covered on Day 7.

• Oracle Global Order Promising schedules the sales order on Day 7.

• On Day 7, there is enough product family supply to cover the shortage. Therefore,
the product family demand spread outside the aggregate time fence is -90.

• Since the order is scheduled outside the aggregate time fence, the product family
demand spread inside the aggregate time fence will be place on the aggregate time
fence date.

Scenario 2
A sales order has the request ship date inside the aggregate time fence (ATF) date and is
scheduled to ship inside the aggregate time fence (ATF) date.
Scenario 2 considers the end of scenario 1 as the initial ATP picture.
Day 2 for quantity of 15, on Day 2.
Day 1
Day 2
Day 3


Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Supply
10
10
10
10
10
50
50
50
50
Demand
0
-15
0
0
0
0
-110
0
0
0
-15
0
0
-20


0
-90
0
0
Net
10
-5
10
10
-10
50
-40
50
50
Cum
5
5
15
15
15
25
25
75
125
Explanation:
There is only one product family demand spread because the sales order only needs to
consume the item supply.
Scenario 3
A sales order has the request ship date outside the aggregate time fence and is
scheduled outside the aggregate time fence.


Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Supply
10
10
10
10
10
50
50
50
50
Demand
0
-15
0
0
0
0
-110
-30
0
0


-15
0
0
-20
0
-90
-30
0
Net
10
-5
10
10
-10
50
-40
20
50
Cum
5
5
15
15
15
25
25
45
95
Explanation:
There is only one product family demand spread because the sales order only needs to
consume the aggregate supply outside the aggregate time fence.
Scenario 4


A sales order has the request ship date inside the aggregate time fence and is scheduled
to ship after the aggregate time fence.
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Supply
10
10
10
10
10
50
50
50
50
Demand
0
-15
0
0
0
-22
-110


-30
0
0
-15
0
0
-32
-10
-90
-30
0
Net
10
-5
10
10
-22
40
-40
20
50
Cum
3
3
3
3
3
3
3
23
73


Explanation:
a shortage of 17.

• The product family demand spread inside the aggregate time fence (ATF) date will
be -5 at this point.


• The shortage can be covered on Day 6.

• The sales order will be scheduled on Day 6.

• On Day 6, there is product family supply of 10. So product family demand spread
outside the aggregate time fence (ATF) is -10.

• The remaining shortage (7) will be covered using item supply inside aggregate time
fence (ATF). Therefore, the additional product family demand spread of -7 is added
inside the aggregate time fence (ATF).

• Total product family demand spread equals (-5) + (-7) = -12 and is placed on Day 5.

Scenario 5
A sales order has the request ship date inside the aggregate time fence (ATF) and is
scheduled after the aggregate time fence (ATF). A new planned order (through the
capable-to-promise process) is created on the schedule date.
The initial ATP picture is:
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Supply
5
5


5
5
5
10
10
10
10
Demand
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Net
5
5
5
5


5
10
10
10
10
Cum
5
10
15
20
25
35
45
55
65
Day 4 for quantity of 60, on Day 7. It creates a new planned order of 40 based on the
capacity availability.
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Supply
5
5
5
5


5
10
50
10
10
Demand
0
0
0
0
0
0
-60
0
0
0
0
0
0
-20
0
-40
0
0
Net
5
5
5
5
-15
10


10
10
10
Cum
5
5
5
5
5
15
25
35
45
Explanation:
a shortage of 40.

• The product family demand spread inside the aggregate time fence (ATF) date will
be -20 at this point.

• If using planned supply, the earliest available date is Day 9.

• If creating new supply based on capacity available, the earliest available date is
Day 7 (assume capable-to-promise gives Day 7).

• Since, the capable-to-promise (CTP) result gives a better date than using scheduled
receipts, Oracle Global Order Promising schedules the order on Day 7 and creates a
new supply of 40 on Day 7.

Note: Oracle Global Order Promising does not support combining
scheduled receipt and additional supply when forward scheduling.

• Oracle Global Order Promising creates a product family demand spread of -40 on
Day 7.

• Oracle Global Order Promising also creates a product family demand spread of -20


on Day 5.

ATP override when the aggregate time fence is defined
Assume that:
• The Aggregate Order Promising Time Fence is set to Demand Time Fence and is for
5 days

• The forecast for product family item PF-1 is for 20 units per day.

• The product family item is PF-1 with member items M-A at 50% and M-B at 50%.

• There is a demand of 90 units of member item on Day 7 for M-A.

The initial demand and supply picture is as follows:
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Supply M-B
10
10
10
10
10
20
20
20
Demand M-B (SO)
0
0
0
0


0
0
-90
0
Product Family Demand Spread M-B (SO)
0
0
0
0
0
0
-40
0
Net M-B
10
10
10
10
10
0
0
20
Cum M-B
10
20
30
40
50
50
50
70
A new sales order of 58 units of member item M-B comes on Day 7 with an ATP


override. Oracle Global Order Promising places the sales order on Day 7 based on the
ATP Override logic described in ATP Override, page 6-36. The product family demand
spread is calculated as shown below.
The new demand and supply picture is as follows:
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Supply M-B
10
10
10
10
10
20
20
20
Demand M-B (SO)
0
0
0
0
0
0
-148
0
Product Family Demand Spread M-B (SO)
0
0


0
0
-50
0
-48
0
Net M-B
10
10
10
10
40
20
28
20
Cum M-B
0
0
0
0
0
0
0
12
The demand spread is as follows:
• 50 units on day 5

• 8 units on day 7

Allocated ATP
Allocated ATP allows you to allocate scarce material among multiple sales channels.
Based on your business strategy, you can establish an Allocation Rule which ranks the
sales channels. You can time phase the allocation to reflect changes in your monthly or


quarterly objectives. During order promising, Oracle Global Order Promising honors
the allocation rule and calculates order due dates based on allocated supply.
Oracle Global Order Promising supports two allocation methods for different business
needs:
• Allocated ATP based on User-Defined Allocation Percentage

• Allocated ATP based on Demand Priority

In user-defined allocation percentage method, you specify a time phased allocation
percentage for your sales channel or customers. The percentage is applied to total
supply to yield allocated supply. Oracle Global Order Promising promises orders based
on allocated supply. You can designate priorities to the sales channel or customers on
the allocation rule. When there is not enough allocated supply from a higher priority
sales channel or customer, Oracle Global Order Promising automatically use available
supply from lower priority sales channel or customers to promise orders from higher
priority sales channels or customers.
In demand priority based allocation method, you prioritize demand such as, forecast
and Master Demand Schedule (MDS). Supply is allocated based on the prioritized
demand. The resultant supply is used for order promising. In this method you can also
designate priority for the sales channels. When there is not enough allocated supply
from a higher priority sales channel, Oracle Global Order Promising automatically uses
available supply from lower priority sales channel to promise orders from higher
priority sales channels.
The following section describes the two allocation methods in detail.

Allocated ATP based on User-Defined Allocation Percentage
In this allocation method, you define specific allocation percentages for your sales
channel or customers. The allocation percentage is applied to total supply and resultant
allocated supply is used for order promising.
You can define two types of hierarchies to represent your various sales channels. You
use demand classes that are single-level and user-defined or, you use the three levels of
customer classes:
• Customer Class

• Customer

• Site

You can designate any items you want to allocate.

When supply is scarce, a supplier may decide to ration the supply based on some ratio.


An example is using the forecast demand ratio. This way you can give every customer
some of the supply. You may fine tune the allocation percentage such that for high
priority customers you may want to give more and less to lower priority customers.
Allocated ATP lets you input the allocation percentage based on your business rules.
Different businesses may group demand differently. Some businesses group demand
into different sales channels and allocate supply to each sales channel. Others may first
group demand into regions and then to customers in each region. Allocated ATP
provides two allocation hierarchies to meet different needs.

Setup
After you perform the mandatory and option setup steps described in the Setup
chapter, you need to perform the following additional steps to use Allocated ATP.
To enable allocation, the following setup steps must be performed:
1. Set profile options.

2. Define demand class or customer class.

3. Define allocation rule.

4. Assign allocation rule.

5. View the allocation, after the plan runs.

Profile MSC: Enable Allocated ATP
To enable allocation, set the profile option MSC: Enable Allocated ATP to Yes.

Profile MSC: ATP Allocation Method
To set the allocation method you want to use. This profile has two values. For Allocated
ATP based on Allocation Percentage, select: User Defined Allocation Percentage.

Profile MSC: Class Hierarchy
This profile determines the type of hierarchy that will be used. There are two values for
this profile:
• Demand Class: single level.

• Customer Class: this hierarchy has 3 levels: customer class, customer, and site.

Profile MSC: Enable ATP Workflow
Workflow notifications are automatically triggered and sent to the item planner and
sales representative or customer contact when the following happens:


• ATP fails on request date during scheduling, or

• ATP is successful only by stealing allocation from a lower priority demand class.

Profile MSC: Allocated ATP Forward Consumption Method
You can set the MSC: Allocated ATP Forward Consumption Method profile option to
one of the following:
• Reduce future supply from lowest priority - to use the available future supply from
the lowest priority demand class. If every demand class is at the same priority, the
demand class that has a shortage, consumes its own future supply.

• Reduce available supply from any priority - to use the available supply from any
demand class. In this method, Oracle Global Order Promising first accounts for a
committed demand before allowing more promises.

Define Demand Classes
If you are using demand class hierarchy, setup demand classes to represent the various
sales channels. For details, see Setting up demand classes inOracle Master
Scheduling/MRP and Oracle Supply Chain Planning User's Guide.

Define Customer Class Hierarchy
If using customer class hierarchy, setup customer classes and assign a customer class to
a customer. For details, see Setting up customer classes in Oracle Receivables User's Guide
.

Define Allocation Rules
Allocation rules must be defined on the destination server. These rules determine how
the supply is allocated.
Allocation rules have the following features: effective dates, percentages, and priorities.
• Allocation Effective Dates: you define time-phased allocation percentages. The ATP
engine determines which allocation percentage to use based on the dates of the
supplies and demands. For on-hand supply, the allocation that is effective today is
used. The allocation hierarchy needs to be the same across the entire planning
horizon. Consistent hierarchy must be ensured for all items that have a supply
chain or BOM relationship.

• Allocation Percentages: you define allocation percentages for each node in the
hierarchy. Your supply is allocated to those nodes based on the allocation
percentages. If the total percentages do not add up to 100% on each level, the
remaining percentages are assigned to a system generated node called Other.


• Allocation Priorities: you define priorities against your allocation rules to be used to
steal supply from other nodes if supply is not available. Priorities are assigned to
each node on each level, and you only steal from those with lower priority.

• Service Level: not used.

To define Allocation Rules:
1. From the Navigator, choose Advanced Supply Chain Planning.

2. Choose ATP. Then Allocation. Finally, select Define Allocation Rule.
The Allocation Rules window appears.


Allocation Rules Window

3. Enter name, description, and the effective dates for the rule. For each demand class
or node in a customer class hierarchy, assign an allocation percentage and priority.

Assign Allocation Rules
Once the rules have been defined, the allocation rules must be assigned so that Oracle
Global Order Promising knows which rule to use for each item. You only assign
allocation rule to the end items. This refers to the items that have independent demand.
You should not assign allocation rule to components or resources. This is because
allocation rule is honored after plan run, and thus is only applicable to end items.
Allocation rules can be assigned at the following levels from least specific to most
specific:
• Global


• Item Category (those categories that are part of the planning category set)

• Item

• Organization

• Item/Organization

A more specific level can override a more general level assignment. For example, if
there is a rule for a particular item and a different rule for the category of that item, then
the effective rule will be the item rule.

Note: Global Order Promising does not support percentage-based
allocation for components of ATO Model or ATO item. Components of
an ATO Model can be options and standard mandatory components.

To assign Allocation Rules:

2. Choose ATP. Then Allocation. Finally, choose Assign Allocation Rules.
The Assign Allocation Rule window appears.


Assign Allocation Rule Window

3. Choose level in the Assign To column.

4. Choose the correct level. Depending on the level you have chosen, you must fill in
the respective column.

5. In the Allocation Rule column, either enter the name of the Allocation Rule or select
the rule from the full list.

Refreshing Allocations
Oracle Global Order Promising stores information of which item having which
allocation rule for fast access during order promising. To do this, a concurrent program
Refresh Allocation Hierarchy is launched automatically every time you make or change
an allocation assignment. However if you update an existing allocation rule which has
assignment, you need to manually launch this concurrent program. You do this by click
the Refresh Hierarchy button on the Allocation Rule window.
The refresh allocation hierarchy process must be finished before the changes take effect
in ATP result.

View Allocation
Once you define an allocation rule and assign the rule to your item(s), if you already
have an ATP plan that contains the item(s), you can view the allocation result. In this
workbench, the left-hand side is the tree structure representing your hierarchy. You can
choose a node and view the horizontal plan. For instance, a particular site within a
customer for customer class hierarchy or a demand class for demand class hierarchy.


The horizontal plan gives a picture over time of the total demand, total supply, net ATP,
and cumulative ATP for the total and for the particular node that you chose.
In addition, you can change the allocation percentages and priorities for any node
directly from the workbench and immediately view the effects. You can do this by
selecting any of the nodes and filling in the Define Allocation Rules form.

To view allocations:
1. Choose the Advanced Supply Chain Planner responsibility.

2. Choose ATP. Then Allocation. Finally, View Allocation.

3. Enter Organization. Then enter either the item.

4. Choose an allocation node from the allocation hierarchy.

Data in the View Allocation Workbench
You can view the following for each allocation node:
• Supply: the total supply for this item in the ATP plan * actual allocation percentage.

• Demand: Oracle Global Order Promising regards the following as demand: sales
order, planned order demand, work in process job demand, sales order MDS,
reservation, safety stock demand, and manual MDS.

• Net: Supply - Demand.

• Cum: The cumulative quantity after net, backward and forward consumption for
any negative net.

• Backward: the quantity after backward consumption

• Demand Adjustment: the quantity after forward consumption

• Adjusted Supply: the supply quantity adjusted to meet the demand

• Allocation %: the allocation percentage

• Actual Allocation %: the actual allocation percentage

• Unallocated Data: the unallocated quantity available. In unallocated data, you can
view the following:
• Supply: the total unallocated supply for the item.

• Demand: the total demand.



• Cum: the cumulative quantity after netting, backward and forward
consumption.

Total: the total allocation for a demand class/customer class. In Total, you can view the
following:
• Supply: the total supply for the item.

Note: The value displayed by a parent allocation node is the sum of
its child nodes.



• Cum: the cumulative quantity after netting, backward and forward consumption.

Use the following options to refresh the allocation data:
• Recalculate: To retrieve the current allocation data from all the nodes and
recompute the allocation for the parent nodes.

• Refresh Screen: To refresh the display in the View Allocation Workbench window
with the recomputed allocation data.

You can also view the following additional information in the View Allocation
Workbench window:

Supply/Demand Data
Double-click on a value displayed in the horizontal plan.
The Supply/Demand window appears. This window displays the supply and demand
details for the value that you have selected.
For more details on the Supply/Demand window, see Supply/Demand, page 6-12.

Hide/Show Row_name
Right-click and select Hide >Row_name or Show >Row_name to hide or show a row in
the View Allocation Workbench window.

Copy horizontal plan
Right-click and select Copy horizontal plan to copy the horizontal plan.

Save Settings
You can adjust the row height and column widths of the fields displayed in the


horizontal plan and save these settings.
1. Highlight a row or a column and drag (using the mouse) to adjust the size.

2. Right-click and select Save Settings to save the settings that you have made for
future display.

Hide/Show graph
Right-click and select Hide/Show graph to hide or show the graph in the View
Allocation Workbench window.

Hide/Show Set
Right-click and select Hide Set or Show Set to hide or show the associated rows for the
following:
• Total: displays the total supply, demand, net and cumulative quantity

• Unallocated availability: displays the unallocated supply, demand, net and
cumulative quantity

To set the preferences for View Allocation Workbench:
1. Log onto Oracle Global Order Promising with the Advanced Supply Chain Planner
responsibility.


3. Select Supply Chain > Plan > Workbench.

4. Select a plan.

5. Select Tools > Preferences.
The Preferences window appears.

6. Click the Allocated ATP tab.


Preferences window, Allocated ATP tab

7. In the User-Defined Percentage Based Allocation section, select the checkboxes
corresponding to the fields that you want to show in the View Allocation
Workbench window.
The following fields are checked by default:
• Allocated Supply

• Demand

• Net

• Cum

Note: Depending on the option that you have selected for the
MSC: Allocated ATP Forward Consumption Method profile
option, the related set of fields are enabled in this tab.

The Allocated ATP tab also contains the following fields:


Field Description

Display Factor Specify a number that you want to multiply to the numbers in
the horizontal plan. For example, if you specify 0.001 in this
field, then a number like 1000000 will be displayed as 1000 in the
horizontal plan.

Decimal Places Specify a number to set the number of decimal places that you
want to display for values in the View Allocation Workbench
window.

Show Graph Select the checkbox to show a graph in the View Allocation
Workbench.

Day = Specify a number to set the time bucket type to days.

Week = Specify a number to set the time bucket type to weeks

ATP Logic

Applying Allocation Rule
For each supply, Oracle Global Order Promising applies the allocation rule that is
effective for the date of that supply.
For any past due supply or demand except sales order demand, Oracle Global Order
Promising allocates the supply or demand using the allocation rule effective on the past
due date. If the allocation rule on the past due date is not available, Oracle Global Order
Promising uses the rule effective on today's date.

Allocation Stealing and Forward Scheduling
For a demand from a demand class, Oracle Global Order Promising first uses its own
allocated supply. If there is shortage, it steals supply from lower priority demand
classes starting from the next lower priority as defined on the allocation rule. This is
often referred to as Backward Stealing. If there is still shortage after stealing, Oracle
Global Order Promising performs capable-to-promise to see if more supply can be
generated. If there is still shortage after capable-to-promise, then the order is late.
Next, Oracle Global Order Promising determines when the shortage can be satisfied by
finding the availability date based on scheduled receipt. During this check, the system
only uses the availability from the demand class itself. There is no stealing. It then
performs a forward capable-to-promise to find a date when the shortage can be made.
The answer is the better date of the two methods.


Forward Consumption
In Allocated ATP based on User-Defined Allocation percentage method, when the
committed cumulative demand exceeds the cumulative allocated supply for a demand
class, Oracle Global Order Promising performs forward consumption of the supply to
accommodate the shortage. Therefore, when a demand class has a shortage after
consuming its own allocated supply and available supply from a lower priority, the
forward consumption method lets you decide how to adjust the allocated availability
based on the MSC: Allocated ATP Forward Consumption Method profile option. Oracle
Global Order Promising provides you with two methods for performing a forward
consumption:
• Reduce future supply from lowest priority

• Reduce available supply from any priority

Reduce future supply from lowest priority
In this method, Oracle Global Order Promising calculates the availability for each
demand class using the following steps:
1. Start from the highest priority demand class.

2. For each demand class:
1. Calculate the net and backward consumption

2. If there is a shortage for a higher priority demand class, adjust from what is
available from the demand class in step 2a.

3. If there is still a shortage and there is a lower priority demand class, then stop.
Otherwise, reduce the future supply to account for the shortage.

Note: If all demand classes are at the same priority, the demand
that has a shortage, consumes its own future supply.

For details, see the following examples:
• Forward consumption: scenario 1, page 4-126





Reduce available supply from any priority
In this method, Oracle Global Order Promising calculates the availability for each
demand class using the following steps:
1. Start from the highest priority demand class.

2. For each demand class:
1. Calculate the net and backward consumption.

2. If there is shortage for a higher priority demand class, adjust from what is
available (step 2a)

3. If the demand class is of the lowest priority, then stop.

3. Calculate the unallocated availability by reducing the total supply to cover the
existing committed demand. This includes backward and forward consumption.

4. The adjusted cumulative for each demand class is the minimum of the supply the
demand class could have (step 2b) compared to the available supply available or
the unallocated availability (step 3). The adjustment starts from the highest priority
demand class first. This means the availability of a lower priority demand class is
reduced to account for shortages from prior period. This reduces the available
supply to account for the shortage from a lower priority demand class.

For details, see the following examples:





Examples
Here are a few examples to illustrate how allocated ATP can be used. The first example
is simple, and shows allocated ATP based on percentages. The second and third
examples incorporate the priorities, and thus show the stealing functionality. The first
two examples use the demand-class hierarchy. The final example shows how ATP
works with a customer-class hierarchy.
Simple example to illustrate how allocation is calculated
In this case, the supplier is using two demand classes to represent various sales


channels. Demand Class b (DCb) contains customers that are more important to this
supplier, and thus the supplies wants to guarantee that 60% of the total supply is
allocated to this group of demands. The following table shows the allocation rule:

Demand Class Percentage

DCa 40%

DCb 60%

The supply and demand picture for this example is shown in the table below. There is
one sales order coming from Demand Class a (DCa) for 20. There are two sources of
supply: a work order for 25 and a purchase order for 35.

Demands and Supplies Demand Class Quantities

Demand Sales Order DCa 20

Supply Work Order - 25

Supply Purchase Order - 35

The overall availability picture is 25 + 35 - 20 = 40. This is calculated by adding the total
supplies and subtracting the already committed demand of 20. If there is no allocation,
the availability for any ATP requests from any demand class is 40.
With the allocation rules in place, this supply is rationed to the demand classes based
on the predefined percentages.
For Demand Class a (DCa):

Demands and Supplies Quantities

Demand Sales Order 20

Supply Work Order 10 = (25 * 40%)

Supply Purchase Order 14 = (35 * 40%)

Thus, the ATP quantity for this demand class is 4 = 10 + 14 - 20.
For Demand Class b (DCb):


Demands and Supplies Quantities

Supply Work Order 15 = (25 * 60%)

Supply Purchase Order 21 = (35 * 60%)

Thus, the ATP quantity for this demand class is 36 = 15 + 21 - 0.
Therefore, with the allocation rules, demand class DCb is guaranteed to be allocated
60% of the supply which is 36. Without these rules in places, customers from demand
class DCa could keep submitting orders, and when a demand came from DCb, no
supply would be available.
Allocation stealing example
This example illustrates how allocated ATP works with both percentages and priorities.
The supply is allocated to the demand classes based on the percentages that are defined
within the allocation rules. Yet, if a higher priority demand class still needs more
supply, they can steal the necessary supply from the lower priority demand classes.
The Allocation rule is as follows:

Demand Class Priority Percentage

DC1 1 30%

DC2 2 20%

DC3 3 50%

In this example, the supplier has defined three demand classes. He has assigned certain
percentages to these demand classes, but in addition he has ranked the priorities of
these demands. In this scenario, Demand Class c (DCc) has the largest number of
customers and thus has been allocated the largest percentage of the available supply.
However, Demand Class a (DCa) has more important customers. Thus, they should be
allowed to steal the supply from the other demand classes if they want to submit an
order.
The Allocation picture is as follows:

Demand Class Row Type Day 1 Day 2 Day 3

DC1 Supply 30 30 30



- Demand 20 10 10

- Net 10 20 20

- Cum 10 30 50

DC2 Supply 20 20 20

- Demand 10 0 0

- Net 10 20 20

- Cum 10 30 50

DC3 Supply 50 50 50

- Demand 30 30 30

- Net 20 20 20

- Cum 20 40 60

Assume that the total supply is 100 per day.
A sales order demand comes in DC2 on Day 2 for quantity 60. Oracle Global Order
Promising does the following:
• On Day 2, cumulative availability for DC2 = 30. There is a shortage of 30.

• There is a lower priority demand class DC3 that has cumulative availability of 40 on
Day 2. Steal 30 from DC2.

• Return success.

The allocation picture after scheduling the above sales order is:


DC1 Supply 30 30 30

- Demand 20 10 10



- Net 10 20 20

- Cum 10 30 50

DC2 Supply 20 20 20

- Demand 10 60 0

- Net 10 -40 20

- Cum 0 -30 20

DC3 Supply 50 50 50

- Demand 30 30 30

- Net 20 20 20

- Cum 20 40 60

The above is what you see in View Allocation Workbench. Even though the cumulative
availability of DC3 is internally adjusted, it is currently not showing in the user
interface.
In other words, the availability for DC3 is the actually the following:


DC3 Supply 50 50 50

- Demand 30 30 + 30 30

- Net 20 -10 20

- Cum 10 10 30

DC3 can only promise sales order demand for 10 either on Day 1 or Day 2.
Allocation using Customer Class Hierarchy
This example illustrates how allocated ATP works with customer class hierarchy. The
supply is allocated to the customer classes, customers, and sites based on the


percentages that were defined within the allocation rules.
The following diagram illustrates a customer class hierarchy:

Customer Class Hierarchy Example

The following percentages and priorities have been defined in the allocation rule. The
actual percentage is calculated by multiplying the entered percentage by the parent's
allocation percentage. For example, in the computer industry there are 3 customers,
Dell, IBM, and other. The percentages for those 3 must add up to 100. The entered
percentage for Dell is 40%, and thus the actual percentage of the total that Dell receives
is 40% of what the Computer Industry is allocated, and thus 28%.
Allocation Rule
The following tables show the allocation rule:
Customer Class Level

Customer Class Priority Percentage Actual
Percentage

Computer Industry 1 70% 70%

Other 2 30% 30%

Customer Level


Customer Class Customer Priority Percentage Actual
Percentage

Computer Industry Dell 1 40% 28%

Computer Industry IBM 2 40% 28%

Computer Industry Other 3 20% 14%

Site Level

Customer Class Customer Site Priority Percenta Actual
ge Percenta
ge

Computer Industry Dell Europe 1 50% 14%

Computer Industry Dell Asia 2 25% 7%

Computer Industry Dell Other 3 25% 7%

Computer Industry IBM Russia 1 50% 14%

Computer Industry IBM China 1 25% 7%

Computer Industry IBM Other 1 25% 7%

Assume 1000 units total supply every day. Allocation picture is:

Note: In this example, only a few nodes are selected to show the row
types.

Customer Customer Site Priority Row Day 1 Day 2 Day 3
Classes Type

Computer Dell Europe 1 -1 -1 Supply 140 140 140
Industry

- - - - Demand 100 100 200


Customer Customer Site Priority Row Day 1 Day 2 Day 3
Classes Type

- - - - Net 40 40 -60

- - - - Cum 20 20 20

Computer Dell Asia 1-1-2 - 0 0 0
Industry

Computer Dell Other 1-1-3 - 0 0 0
Industry

Computer IBM Russia 1-2-1 - 0 0 0
Industry

Computer IBM China 1-2-1 Supply 70 70 70
Industry

- - - - Demand 30 100 10

- - - - Net 40 -30 60

- - - - Cum 10 10 70

Computer IBM Other 1-2-1 - 0 0 0
Industry

Computer Other - 1-3 - 0 0 0
Industry

Other - - 2 - 0 0 0

Explanation of allocation stealing:
• A demand for Computer Industry-Dell-Europe can steal available supply from all
the other nodes.

• A demand for Computer Industry-IBM-Russia can steal available supply only from
Computer-Industry-Other or Other.

• A demand for Other cannot steal.

Forward consumption: scenario 1
In this example, the total cumulative supply is greater than the total cumulative


demand and the MSC: Allocated ATP Forward Consumption Method profile option is
set to Reduce future supply from lowest priority.
The top priority demand class has more demand than supply due to stealing. This
example illustrates that in the course of normal stealing, the net availability picture
remains correct.

Demand Class Row Type D1 D2 D3

DC1 (P1) Allocated Supply 10 10 10

- Demand 0 -55 0

- Net 10 -45 10

- Backward 0 -35 10

- Demand Adjustment 0 0 0

- Adjusted Availability 0 0 10

- Cumulative quantity 0 0 10


- Demand 0 -2 0

- Net 10 8 10

- Backward 10 8 10

- Demand Adjustment 0 -18 0




- Demand 0 -2 0

- Net 10 8 10



- Backward 10 8 10




Sum of DC Cumulative - 1 1 11
quantity

Explanation:
• DC1 has a shortage of -35 on D2.

• DC2's supply is reduced by -18 to meet the demand of DC1.


In this example, the total cumulative supply is less than the total cumulative demand
and the MSC: Allocated ATP Forward Consumption Method profile option is set to
Reduce future supply from lowest priority.
This example illustrates that if overall supply changes, Oracle Global Order Promising
allocates the available supply from the lowest demand class (or the last one from the
lowest priority demand classes) to the demand class that has a shortage. You may have
to do manual adjustment to re-distribute future supply (in this example, may be D4)
more to the lowest priority demand class.

Demand Class Row Type D1 D2 D3 D4

DC1 (P1) Supply 10 10 10 30

- Demand 0 -15 0 0

- Net 10 -5 10 30

- Backward 5 0 10 30

- Demand Adjustment 0 0 0 0



- Adjusted 5 0 10 30
Availability

- Cumulative quantity 5 5 15 45

DC2 (P2) Supply 10 10 10 30

- Demand 0 -45 0 0

- Net 10 -35 10 30

- Backward 0 -25 10 30


- Adjusted 0 0 10 30
Availability


DC3 (P3) Supply 10 10 10 30

- Demand 0 -24 0 -5

- Net 10 -14 10 25

- Backward 0 -4 10 25

- Demand Adjustment 0 -25 0 0

- Adjusted 0 0 0 6
Availability


Sum of DC - 5 5 25 91
Cumulative quantity

Explanation:



In this example, the demand classes are with same and different priorities and the MSC:
Allocated ATP Forward Consumption Method profile option is set to Reduce future
supply from lowest priority.
This example illustrates a scenario where one higher priority demand class has stealing
and the other does not.


DC1 (P1) Supply 10 10 10

- Demand -5 -12 0

- Net 5 -2 10

- Backward 3 0 10




DC2 (P1) Supply 10 10 10

- Demand -4 -34 0

- Net 6 -24 10

- Backward 0 -18 10




DC3 (P2) Supply 10 10 10

- Demand -3 -16 0



- Net 7 -6 10

- Backward 1 0 0




DC4 (P2) Supply 10 10 10

- Demand -4 -4 0

- Net 6 6 10

- Backward 6 6 10




quantity

Explanation:

• DC3 can supply only -1 to meet the demand of DC2.

• DC4 accounts for the remaining shortage on, before and beyond D2 because DC4 is
the last demand class among the lowest priority demand classes.

In this example, the demand classes are at the same priority and the MSC: Allocated
ATP Forward Consumption Method profile option is set to Reduce future supply from
lowest priority.



DC1 (P1) Supply 10 10 10

- Demand 0 -25 0

- Net 10 -15 10

- Backward 0 -5 10




DC2 (P2) Supply 10 10 10

- Demand 0 -15 0

- Net 10 -5 10

- Backward 5 0 10




quantity

Explanation:

• DC1 and DC2 are at the same priority level. Therefore, DC1 consumes its own
future supply to meet the shortage.

In this example, the total cumulative supply is greater than the total cumulative
demand and the MSC: Allocated ATP Forward Consumption Method profile option is
set to Reduce available supply from any priority.


This example illustrates a scenario where a top priority demand class has more demand
than supply due to stealing.


Unallocated Supply 30 30 30

- Demand 0 -59 0

- Net 30 -29 30



- Demand 0 -55 0

- Net 10 -45 10

- Backward 10 -35 10




- Adjusted Cumulative 0 0 10
quantity


- Demand 0 -2 0

- Net 10 8 10

- Backward 10 8 10

-- Demand Adjustment 0 -18 0





quantity


- Demand 0 -2 0

- Net 10 8 10

- Backward 10 8 10




quantity

Sum of DC Adjusted - 1 1 31
Cumulative quantity

Explanation:
• On D2, DC1 has a shortage of -35.
• DC1 consumes the supply of -18 from DC2 and -17 from DC3.

In this example, the total cumulative supply is less than the total cumulative demand
and the MSC: Allocated ATP Forward Consumption Method profile option is set to
Reduce available supply from any priority.
This example illustrates that if overall supply changes, Oracle Global Order Promising
allocates the available supply from the lowest demand class (or the last one from the
lowest priority demand classes) to the demand class that has a shortage. You may have
to perform manual adjustment to the allocation percentage to re-distribute the future
supply (in this example, may be D4) more to lowest priority demand class.



Unallocated Supply 30 30 30 90

- Demand 0 -84 0 -5

- Net 30 -54 30 85


DC1 (P1) Supply 10 10 10 30

- Demand 0 -15 0 0

- Net 10 -5 10 30

- Backward 5 0 10 30


- Adjusted Availability 5 0 10 30


- Adjusted Cumulative 0 0 6 45
quantity

DC2 (P2) Supply 10 10 10 30

- Demand 0 -45 0 0

- Net 10 -35 10 30

- Backward 0 -25 10 30






quantity

DC3 (P3) Supply 10 10 10 30

- Demand 0 -24 0 -5

- Net 10 -14 10 25

- Backward 0 -4 10 25

- Demand Adjustment 0 -25 0 0



quantity

Sum of DC Adjusted - 0 0 6 91
Cumulative quantity

Explanation:
• On D1, total availability is 0. DC1 can have only 0 instead of 5.

• On D4, total availability is 91. DC1 should have 45. Therefore, the adjusted
cumulative is 45.

In this example, the demand classes are with same and different priorities and the MSC:
Allocated ATP Forward Consumption Method profile option is set to Reduce available
supply from any priority.
This example illustrates a scenario where one higher priority demand class has stealing
and the other does not.





- Demand -16 -69 0

- Net 24 -29 40


DC1 (P1) Supply 10 10 10

- Demand -5 -12 0

- Net 5 -2 10

- Backward 3 0 10




- Adjusted Cumulative quantity 0 0 13

DC2 (P1) Supply 10 10 10

- Demand -4 -34 0

- Net 6 -24 10

- Backward 0 -18 10





DC3 (P2) Supply 10 10 10



- Demand -3 -19 0

- Net 7 -9 10

- Backward 0 -2 10





DC4 (P2) Supply 10 10 10

- Demand -4 -4 0

- Net 6 6 10

- Backward 6 6 10





Cumulative quantity

Explanation:
• DC2 has a shortage of 18 on D2 that needs to be adjusted from lower priority
demand classes. Since, DC3 does not have any availability after backward
consumption, the entire shortage is placed on DC4 because this is the only lower
priority demand class.

• DC3 has a shortage of 2 on D2. Since there is no lower priority demand class, it is


left in DC3.

• The adjusted availability is calculated on each day. A negative number is treated as
0.

• The cumulative quantity is calculated based on the adjusted availability.

• The adjusted cumulative is calculated for each demand class starting from the
highest priority. The demand class's cumulative is compared to the unallocated
cumulative quantity on each day from the date before the ATP infinite time fence to
the first date. For DC1, on D3, the cumulative is 13, which is less than the
unallocated cumulative quantity. Therefore, the adjusted cumulative for DC1 is 13.
After allocating 10 to DC2 and 10 to DC3, 2 of the item are left. Even though DC4
could have 10, due to covering a shortage from a higher priority demand class, it is
only left with 2.

In this example, the demand classes are at the same priority and the MSC: Allocated
ATP Forward Consumption Method profile option is set to Reduce available supply
from any priority.
This example illustrates a scenario where all the demand classes are at the same
priority.



- Demand 0 -40 0

- Net 30 -10 30


DC1 (P1) Supply 10 10 10

- Demand 0 -25 0

- Net 10 -15 10

- Backward 0 -5 10






quantity

DC2 (P1) Supply 10 10 10

- Demand 0 -15 0

- Net 10 -5 10

- Backward 5 0 10




quantity

Cumulative quantity

Explanation:
• There is no demand adjustment among the demand classes because of the same
priority.

• The cumulative quantity is compared to the unallocated cumulative to obtain the
adjusted cumulative amount. On D2, the unallocated cumulative is 0. Therefore,
both DC1 and DC2 have 0 as the adjusted cumulative quantity.

In this example, the unallocated cumulative is greater than the adjusted cumulative and
the MSC: Allocated ATP Forward Consumption Method profile option is set to Reduce
available supply from any priority
This example illustrates a scenario where the unallocated cumulative can be more than
sum of adjusted cumulative from demand class.




- Demand 0 -15 0

- Net 20 5 20



- Demand 0 -15 0

- Net 10 -5 10

- Backward 5 0 10




quantity


- Demand 0 0 0

- Net 10 10 10

- Backward 10 10 10






quantity

Cumulative quantity

Explanation:
• On D1, the unallocated cumulative is 20. The cumulative for DC1 and DC2 is 5 and
10 respectively. The sum of the demand classes' cumulative quantity is less than the
unallocated cumulative. In this scenario, Oracle Global Order Promising will
allocate up to the demand classes' cumulative quantity.

• The reason this scenario can happen is that in unallocated calculation, the demand
of 15 consumes supply on D2. However, in allocated calculation, the demand of 15
consumes both D1's and D2's supply. Therefore, the unallocated cumulative shows
more availability on D1 than the sum of cumulative from allocation.

Alocated ATP Based on Demand Priority
In this allocation method, supply is allocated based on prioritized demand. Oracle
Advanced Supply Chain Planning supports this method of allocation by pegging
supply based on prioritized demand. Oracle Global Order Promising uses the result.
In this method, Oracle Global Order Promising allows high priority sales channel to
steal supply from lower priority sales channel. You define priorities against your
allocation rules. These priorities can be used to steal supplies from lower priority nodes
if supplies are not available. The allocation rules are assigned globally, to the item
category, or to the item. Notifications are sent to you if scheduling fails or if scheduling
is only successful by stealing allocation from other nodes.

If you want to protect your high priority customers or sales channels by securing
supply based on the forecast demand for those customers, you use this allocation
method. In this method, supply is allocated based on prioritized demand. Forecast or
Master Demand Schedule for high priority customers or sales channels would have a
higher priority (lower priority number) number associated. Thus supply is allocated to
those demand first. When orders from these customers or sales channels comes, they
are promised based on allocated supply.


Setup
After you have performed the mandatory and optional setup steps described in the
Setup chapter, you need to perform the following additional setup steps:
1. Run the concurrent program Create ATP Partitions. You only need to perform this
step once.

2. Set profiles options that are described in the following pages.

3. Define a demand class.

4. Define an allocation rule.

5. Assign an allocation rule.

6. Enter demand by demand class.

7. Run an ATP plan.

8. Optionally, run the concurrent program ATP Post Plan Processing.

9. View the allocation.

Create ATP Partitions
Oracle Global Order Promising uses partitions to segregate data by plan. This improves
performance. Run this concurrent program once, before you start using Allocated ATP.

Profile MSC: Enable Allocated ATP
To enable allocation, set the profile option MSC: Enable Allocated ATP to Yes.

Profile MSC: ATP Allocation Method
To set the allocation method you want to use. This profile has two values. For Allocated
ATP based on demand priority, select Demand Priority.

Profile MSC: Class Hierarchy
This profile determines the type of hierarchy that will be used. Only Demand Class is
supported in this allocation method. Choose Demand Class.

Profile MSC: Enable Allocated ATP Workflow
To enable workflow notifications that are specifically for Allocated ATP, set the profile
option MSC: Enable Allocated Workflow to Yes.
Workflow notifications are automatically triggered and sent to the item planner, sales


representative, and customer contact when the following happens:
• ATP fails on request date during scheduling, or

• ATP is successful only by stealing allocation from a lower priority demand class.

Define Demand Classes
You need to setup demand classes to represent the various sales channels. For more
information, see: Setting up demand classes, Oracle Master Scheduling/MRP and Oracle
Supply Chain Planning User's Guide.

Define Allocation Rules
Allocation rules must be defined on the destination server. These rules tells Oracle
Global Order Promising the demand classes you are allocating and their relative
priority.
• Effective Dates: you only need to create one date range starting from today.
Currently Global Order Promising does not support different allocation hierarchy
for different date range.

• Demand Class: specify the demand class that will be allocated.

• Maximum Allocation %, Actual Allocation %: these fields are used by allocation
based on user-defined allocation percentage.

• Priority: priority is used for stealing. When a higher priority demand class does not
have enough supply to promise an order, it can steal availability supply from lower
priority demand classes.

• Service Level: this field is currently not used by Oracle Global Order Promising.

Upon saving a new allocation rule, the system inserts a row with OTHER as the
demand class. It is used as a generic bucket for excess supply or supply that is pegging
to a demand class that is not on the rule.

To define Allocation Rules:

2. Choose ATP. Then Allocation. Finally, Define Allocation Rule.
The Allocation Rules window appears.


Allocation Rules Window

3. Enter name, description, and the effective dates for the rule. Enter customer class
and its priority.

Assigning Allocation Rules
Once the rules have been defined, the allocation rules must be assigned so that the
Oracle Global Order Promising knows which rule to use for each item. This allocation
method is only meaningful for end items. You should only assign allocation rule to
those items that have independent demand.
Allocation rules can be defined at the following levels from least specific to most
specific:
• Global

• Item Category (those categories that are part of the planning category set)


• Item

• Organization

• Item / Organization

To assign Allocation Rules:

2. Choose ATP. Then Allocation. Finally, select Assign Allocation Rules.
The Assign Allocation Rules window appears:

Assign Allocation Rules Window

3. Choose level in the Assign To column.

4. Choose the correct level. Depending on the level you have chosen, you must fill in
the respective column.

5. In the Allocation Rule column, either enter the name of the Allocation Rule or select
the rule from the full list.

Enter Demand by Demand Class
The premise of using this allocation method is to have prioritize demand by demand
class. Whether you are using forecast or Master Demand Schedule, you need to create
the demand by demand class and indicate the priority on the demand entries. You enter
the priority number in the demand entry flexfield called Priority.


Run ATP Plan
You need to identify a particular plan, such as MPS, MRP, or DRP for ATP by checking
the Check ATP flag in the Plan Definition window in Oracle Advanced Supply Chain
Planning.
It is very important for you to carefully decide the Priority Rule and pegging options.
Oracle Global Order Promising uses the output.
For details on priority pegging, see Pegging in Oracle Advanced Planning and Scheduling
User's Guide.

ATP Post Plan Processing
When you launch a plan that has ATP flag checked, the plan run process automatically
launch ATP Post Plan Processing at the end of the plan run. This concurrent program
analyzes the plan output and summarizes the supply according to item's allocation rule.
Only when this program finishes successfully, you will have a valid availability picture
for order promising.
If the plan does not have ATP flag checked, you can manually launch this concurrent
program for the plan.

View Allocation
Once the ATP Post Plan Processing concurrent program successfully finishes, you can
view the allocation result in View Allocation Workbench. In this workbench, the
left-hand side is the tree structure representing your demand classes. You can choose a
node and view the horizontal plan. The horizontal plan gives a picture over time of the
total demand, total supply, net ATP, and cumulative ATP for the total and for the
particular node that you chose.

To view Allocations:

2. Choose ATP. Then Allocation. Finally, View Allocation.
The View Allocation window appears.

3. Enter Organization. Then enter either the item.

4. Choose an allocation node from the allocation hierarchy.

Data in the View Allocation Workbench
You can view the following for each allocation node:
• Supply: the total supply that pegs to independent demand for the demand class you


are looking at.

• Demand: Oracle Global Order Promising regards the following as demand: sales
order, planned order demand, WIP job demand, sales order MDS, reservation,
safety stock demand, and manual MDS.


• Cum: The cumulative quantity after net, backward and forward consumption for
any negative net.

• Supply Adjustment - the supply quantity adjusted to meet the demand

• Total Supply - the total supply available

• Backward and Forward - the quantity after backward and forward consumption

• Total: the total allocation for a demand class/customer class. In Total, you can view
the following:
• Supply: the total supply for the item.



• Cum: the cumulative quantity after netting, backward and forward
consumption.

To set the preferences for View Allocation Workbench:
responsibility.


3. Select Supply Chain > Plan > Workbench.

4. Select a plan.

5. Select Tools > Preferences.
The Preferences window appears.

6. Click the Allocated ATP tab.

7. In the User-Defined Percentage Based Allocation section, select the checkboxes
corresponding to the fields that you want to show in the View Allocation


Workbench window.
The following fields are checked by default:
• Allocated Supply

• Supply Adjustment

• Demand

• Net

• Cum

ATP Logic

ATP Post Plan Processing
The concurrent program uses pegging to identify the supply for a particular demand
class.
The logic is as follows, for any item that has allocation rule assigned:
• If the supply pegs to independent demand that has a demand class on the allocation
rule, then the supply goes to that demand class.

• If the supply pegs to independent demand that has a demand class not present on
the allocation rule, then the supply goes to OTHER bucket.

• If the supply pegs to independent demand that does not have a demand class, then
the supply goes to OTHER.

• Excess supply, which includes supply pegged to safety stock demand goes to
OTHER.

• The due date on the supply order is used to indicate the supply date for order
promising.

• The following supply is ignored: supply pegged to negative on-hand, supply
pegged to shrinkage demand, and supply that Oracle Advanced Supply Chain
Planning recommends to cancel.

Independent demand includes external and internal sales orders, forecast, and Master
Demand Schedule.

Stealing and Forward Scheduling Logic
For a demand from a demand class, Oracle Global Order Promising first uses its own
allocated supply. If there is shortage, it steals supply from lower priority demand


classes starting from the next lower priority as defined on the allocation rule. This is
often referred to as Backward Stealing. If there is still shortage after stealing, Oracle
Global Order Promising performs capable-to-promise to see if more supply can be
generated. If there is still shortage after capable-to-promise, then the order is late.
Next, Oracle Global Order Promising determines when the shortage can be satisfied by
first finding the availability date based on scheduled receipt. During this check, a high
priority demand class steals from a lower priority demand class on a daily basis. This is
often referred to as Forward Stealing. It then performs a forward capable-to-promise to
find a date when the shortage can be made. The answer is the better date of the two
methods.

Examples
The following examples illustrate Allocated ATP based on demand priority.

Note: The pegging shown below is just an example, and may vary
based on factors such as planning priority specified for a sales order or
forecast.

Demonstrates the allocation and stealing logic
Oracle Advanced Supply Chain Planning Output is the following:

Demand Class Date 1 Date 2 Date 3 Date 4 Date 5

Demand DC1 (1) fc11 = 20 fc12 = 20 fc13 = 20 fc14 = 20 fc15 = 20

DC2 (2) fc21 = 80 fc22 = 80 fc23 = 80 fc24 = 80 fc25 = 80

DC3 (3) fc31 = fc32 = fc33 = 100 fc34 = 100 fc35 = 100
100 100

Supply - 200 200 200 200 200

ASCP Pegging - 20-fc11 20-fc12 20-fc13 20-fc14 20-fc15

80-fc21 80-fc22 80-fc23 80-fc24 80-fc25

100-fc31 100-fc32 100-fc33 100-fc34 100-fc35

Note: fc11 and others represent the forecast identifier.

Allocation Rule is:
• DC1, Priority 1


• DC2, Priority 2

• OTHER, Priority 3

The ATP Allocation is the following:


DC1 (1) Supply 20 20 20 20 20

- Demand 0 0 0 0 0

- Net 20 20 20 20 20

DC2 (2) Supply 80 80 80 80 80

- Demand 0 0 0 0 0

- Net 80 80 80 80 80

DC3 (3) Supply 100 100 100 100 100

- Demand 0 0 0 0 0

- Net 100 100 100 100 100

The sales order demand has:
• Demand Class = DC1

• Quantity = 430

• Request Date = Date 2

Assuming no CTP, the ATP Result is Request Date Quantity = 400 and Schedule Date =
Date 3.
The Allocation is the following:


DC1 (1) Supply 20 20 20+10 20 20
+160+200



- Demand 0 0 -430 0 0

- Net 20 380 -400 20 20

- Cum 0 0 0 20 40

DC2 (2) Supply 80 80+(-160) 80+(-10) 80 80

- Demand 0 0 0 0 0

- Net 80 -80 70 80 80

- Cum 0 0 70 150 230

DC3 (3) Supply 100 100 100 100 100
+(-200)

- Demand 0 0 0 0 0

- Net 100 -100 100 100 100

- Cum 0 0 100 200 300

Explanation:
• On request date, there are 40 units available from DC1, 160 from DC2, 200 from
DC3.

• After stealing, there are 30 units short.

• On Date 3, there are 20 units from DC1. Now the shortage is 10. Oracle Global
Order Promising can steal 10 from DC2. Thus schedule date equals Date 3.

• After the order is scheduled for Date3, the demand appears on Date 3 under DC1.
On Date 2 (request date), supply for DC2 and DC3 are adjusted to reflect backward
stealing. On Date 3, supply is adjusted for DC2 to reflect forward stealing.

Demonstrates the Allocation Derivation
This example further illustrates how allocation is derived based on Oracle Advanced
Supply Chain Planning pegging and allocation rule. Same input to Oracle Advanced
Supply Chain Planning and output from Oracle Advanced Supply Chain Planning as in
Example 1.


Allocation Rule is:
• DC1, Priority 1


The ATP Allocation is the following:

Date 1 Date 2 Date 3 Date 4 Date 5

ATP DC1 (1) 20 20 20 20 20
Allocation

OTHER (2) 180 180 180 180 180

Explanation:
• Since DC2 and DC3 do not appear on the allocation rule, the supplies that peg to
DC2's demand and DC3's demand go to the OTHER bucket.

Prioritized Demands
The prioritized demands for two demand classes are fed into Oracle Advanced Supply
Chain Planning. However, due to the order modifier, there is excess supply.
The Order Modifier is a Fixed Order Quantity of 250.
The Oracle Advanced Supply Chain Planning Output is:

Demand Date 1 Date 2 Date 3 Date 4
Class

Demand DC1 (1) fc11 = 20 fc12 = 20 fc13 = 20 0

- DC2 (2) fc21 = 80 fc22 = 80 fc23 = 80 0

Supply - 250 - 250 0

ASCP Pegging - 20-fc11 - 50-fc23 0

80-fc21 20-fc14

20-fc12 80-fc24

80-fc22 100-excess

20-fc13

30-fc23


The Allocation Rules are:
• DC1, Priority 1

• DC2, Priority 2


The ATP Allocation is:

Demand Class Date 1 Date 2 Date 3 Date 4

ATP Allocation DC1 (1) 60 0 20 20

- DC2 (2) 190 0 130 80

- OTHER (3) - 0 100 -


5
ATP Based on Planning Output: Part II

• End Item Substitution
• Support for Lot Based Components
• 24x7 ATP Support
• Multiple Plans
• Improved ATP Performance Based on Summarized Data
• Unplanned Items
• Honoring Plan Recommendations for Sales Order Rescheduling
• ATP Support for Distribution Planning

End Item Substitution
Oracle Global Order Promising supports end item substitution. End item substitution is
where an item is substituted when the requested product is not available. Whether
substitution occurs and how items are substituted depends on the customer or customer
site ordering the item.

Setup
After you complete the mandatory and optional setup steps described in the Setup
chapter, you need to perform the following setup steps in order to use End Item
Substitution capability:
1. Define item substitution relationship.

2. Set item attribute to establish a window for substitution.

3. Set profile to control the generation of supplies for capable-to-promise.

ATP Based on Planning Output: Part II 5-1

4. Set profile to control workflow notification when substitution occurs during sales
order scheduling.

5. Have an ATP plan that has end item substitution enabled.

Each of these steps are explained in detail in the section that follows.

1. Define Item Substitution Relationship
You use the Item Relationship window in Oracle Inventory to define item substitution
relationship.
For detailed instructions, see: Define a Substitution Relationship, Oracle Advanced
Planning and Scheduling Implementation and User's Guide.

Note: Oracle Global Order Promising currently only supports No
Substitution or Full Substitution. Partial substitution is not supported.
This means a request is not fulfilled by using a partial quantity from the
requested item and a partial quantity from substituted item.

2. Set Item Attribute to establish a Window for Substitution
While substitutions are part of regular business process, substitutions done too far
ahead of demand might not be appropriate. For example, if you find a substitute supply
four weeks ahead of the demand, you may not want to substitute as you may have a
good chance of producing supply for the demanded item in the next three weeks.
A substitution window allows you to limit the time frame for the substitution. You can
define the substitution window for an item using item attribute form in Oracle
Inventory. The substitution window is effective in the forward direction from every
demand. All substitute supplies prior to demand are eligible for substitution. Please
note that the substitution window is applicable only for substitution; if you are netting
supply and demand from the same item, the substitution window does not apply.
The Item Substitution window is under Item window in the MPS/MRP Planning tab.


Item Window

You have the following choices:
• Cumulative Manufacturing Lead Time

• Cumulative Total Lead Time

• Total Lead Time

• User-Defined

3. Set Profile to Control the Generation of Supplies
When Oracle Global Order Promising tries to create new supply during its
capable-to-promise process, you can control which item Oracle Global Order Promising
uses to create new supply. This is helpful when you may not want to create new supply
for phased out items.
Profile MSC: Choice of Item for Which to Create Supplies in Substitute Relationship has
following values:
• Demanded Item: planned orders are created for the demanded item.

• Highest Level Item: planned orders are created for the highest level item in a
substitution chain for the demanded item.


• By Item Attribute: if Create Supply item attribute is Yes, demand is created for the
demanded item with the item attribute. If Create Supply is no, demand is created
for the nearest item in a substitution chain that has the item attribute.

Note: Create Supply is a checkbox under MPS/MRP Planning tab of
the Item window.

Suppose there are three items: A, B and C, where Item B can be substituted for A and
Item C can be substituted for B. These two relationships are entered in the Item
Relationships form as follows:

From Item To Item Type Reciprocal

A B Substitute Not Checked

B C Substitute Not Checked

Using typographical notation, we show this as:
• A --> B

• B --> C

We are showing which way the demand is passed from one item to its substitute.
An inferred relationship is that C, which can be substituted for B, can also be
substituted for A. We can show this as:
• A --> C

Now, we have a substitution chain that we can show as:
• A --> B --> C

In this chain, we say that C is the highest level item. Companies might define a chain
such as this in the case of product phase outs. Items A and B are no longer
manufactured and are phased out. If a customer orders A or B, the current item C is
shipped when there are no more supplies of A and B. New planned orders are created
for C only. For this scenario, you may set the profile MSC: Choice of Item for Which to
Create Supplies in Substitute Relationship = Highest Level Item.

4. Set Profile to Control Workflow Notification When Substitution Occurs During Sales Order Scheduling
You need to set profile MSC: Enable ATP Workflow to Yes if you want notification to be
sent to the appropriate people when item substitution occurs during sales order
scheduling.


5. Have an ATP Plan that has End Item Substitution Enabled
Oracle Global Order Promising enables substitution if the underlying ASCP plan has
end item substitution enabled.
For details on how to enable end item substitution in an ASCP plan, see: End-Item Level
Substitution, Oracle Advanced Planning and Scheduling Implementation and Users's Guide.
Note that you can optionally specify a Substitution Set in an ASCP Plan. If you specify
one, Oracle Advanced Supply Chain Planning and Oracle Global Order Promising will
only honor those substitution relationships that are associated with the named
substitution set.

ATP Logic

Substitution Logic in a Single Organization
Oracle Global Order Promising uses up the on-hand and scheduled receipts for the
requested item and its substitutes prior to the request date. Once ATP logic exhausts all
the possible supplies from demanded and substitute items prior to the request date, it
will start looking for scheduled receipts and fresh supplies in the forward direction.
While evaluating the existing scheduled receipts, Oracle Global Order Promising
develops a consolidated supply picture across requested item and its substitutes. If it is
not successful in satisfying the request, then Oracle Global Order Promising tries first to
project the availability date, and then to present the earliest date.
Oracle Global Order Promising first evaluates the existing supply by request date for
the requested item in the shipping organization. If there is not enough supply for the
requested item, then it evaluates existing supply comprising on-hand and scheduled
receipts for substitute items one by one. Global Order Promising stops evaluating when
it finds enough supply for any substitute item.
If none of the substitute items can meet the requested quantity, Oracle Global Order
Promising attempts to create supply based on the profile MSC: Choice of Item for
Which to Create Supplies in Substitute Relationship. For example, if the item can be
made using additional capacity and components supply. If Oracle Global Order
Promising cannot create enough supply for the requested item on the request date, it
attempts to create supply for the substitute items one by one for shortage of the
substituted items. It stops evaluating when it finds enough supply.
If none of the items can meet the request, Oracle Global Order Promising performs
forward scheduling for the requested item, then substitute items. Oracle Global Order
Promising recommends the item that can meet the demand the earliest.

Searching Supply Chain for Substitutes
Oracle Global Order Promising first evaluates the existing supply by request date for
the requested item across the supply chain using breadth-first logic. If there is not
enough supply for the requested item, Oracle Global Order Promising evaluates


existing supply for substitute items one by one across the supply chain using
breadth-first logic. It stops when it finds supply for any substitute item.
If Oracle Global Order Promising needs to suggest supply, it creates supply using
existing capable-to-promise logic.
Oracle Global Order Promising uses a plan-level option selection to determine if
breadth-first logic needs to be applied. The plan level option is the End Item
Substitution checkbox in the Decision Rules tab on the Plan Options window. If you
select this checkbox, you get the breadth-first logic for items that have end item
substitutions defined.
The diagram below illustrates the breadth-first search concept. Items A and B are two
substitute items and they are enabled in different organizations. The search for existing
supply of a substitute proceeds breadth first, i.e., Oracle Global Order Promising
searches for items A and B in Org 1, Org 2, Org 3, Org 4, and Org 5. If you have setup
your substitution, ATP searches for each item individually. If Org 3 is set to Rank 1 and
Org 2 to Rank 2, then ATP follows this path: Org 1, Org 3, Org 2, Org 4, and Org 5 while
evaluating existing on-hand and scheduled receipts for both native and substitute
supplies across the supply chain.


Breadth-First Search Concept

It is assumed that both items A and B have the same sourcing rule. If substitution needs
to happen in all organizations and all organizations can swap materials freely, you can
expect that substitute items are enabled in all relevant organizations and sourcing rules
exist for all substitute items to ship materials to all relevant organizations. If you do not
establish sourcing rules, the substitution logic does not make any assumptions about
sourcing rules.

Note: When end item substitution is not enabled, Oracle Global Order
Promising performs depth-first search. In the above example, the order
of search will be:
Org 2 -> Org 5 -> Org 3 -> Org 4

Resolving Ties in the Substitution Chain
Oracle Global Order Promising provides only one item as an outcome of your supply
query. There may be a case where you have a tie between the requested item and a
substitute item. If both the requested item and a substitute item are available on the


same day, Oracle Global Order Promising promises the order with the requested item.
For example, items A, B, and C are three substitute items. You get demand for 10 units
of item A. You find 10 units of supply of both item A and item B on Day 3. The result is
that Oracle Global Order Promising suggests item A as the requested item.
If there are multiple ties and the requested item is not in the tie, Oracle Global Order
Promising suggests the nearest item in the substitution chain. For example, if you do
not have any supply for A but you can find supply for both item B and C on the same
day, Oracle Global Order Promising suggests item B.

Substitution in Allocated ATP
Oracle Global Order Promising supports allocation of materials to various segments of
your demand. When demand cannot be satisfied using allocated supply, Oracle Global
Order Promising first steals any available supply from lower priority sales channels.
Then, if there is a shortage after stealing, Oracle Global Order Promising performs an
availability check on the substitute item.

Note: Currently, Oracle Global Order Promising only supports All or
None substitution.

Examples
The following examples provide illustrations of the ATP logic.
Substitution Using Supplies by Request Date
In this example you have three items: A, A1, and A2. A2 is the highest level item in the
substitution chain. A can use the A1 or A2 supply, and A1 can use the A2 supply. The
following tables show you the supply and demand picture for items in the substitution
chain. There are two inquiries for Item A:
1. Day 12 for 50 units

2. Day 35 for 80 units (after you schedule the first demand)

The substitution window width is 5 days for all items.
Item A

Record Item Day 2 Day Day Day Day 15 Day Day Day
Type 5 10 12 35 40 45

Demand A 0 0 0 0 0 0 0 0

Supply A 0 10 0 0 0 70 0 0


Item A1

Record Item Day 2 Day 5 Day Day Day Day 35 Day 40 Day
Type 10 12 15 45

Demand A1 0 0 0 2 0 0 0 0

Supply A1 0 0 0 7 0 0 0 100

Item A2

Record Item Day 2 Day 5 Day Day Day Day Day Day 45
Type 10 12 15 35 40

Demand A2 0 2 0 0 0 0 0 0

Supply A2 0 35 0 17 0 30 0 0

Demand on Day 12 for item A is satisfied by consuming 50 units of A2. Because Oracle
Global Order Promising currently does not support Partial Fulfillment, the demand is
fulfilled by using supply from only one item.
The promise date for the first demand is Day 12 with item A2 and an ATP quantity of
50. Oracle Global Order Promising collects substitute supplies only if the supplies are in
excess and after satisfying the existing committed native demand. In this example,
although there are 35 units of supply on Day 5 for item A2, only 33 units can be used for
substitution because it needs to satisfy its own demand for 2 units.
Demand for item A on Day 35 first consumes its own supply of 80 units. Supply from
item A1 is not considered because of the substitution window. The promise date for the
demand is Day 35 with an ATP quantity of 80. No substitution occurs.
Production Prior to Request Date
Now, the supply picture changes so that the substitution window is set to 10 days for all
items. There are two inquiries for item A: one on Day 12 for 50 units and the other on
for 80 units on Day 35 after you schedule the first demand. The profile MSC: Choice of
Item for Which to Create Supplies in Substitute Relationship is set to Demanded Item.
Item A

Record Item Day 2 Day 5 Day 10 Day Day 15 Day 35 Day 40 Day
Type 12 45

Demand A 0 0 0 0 0 0 0 0


Record Item Day 2 Day 5 Day 10 Day Day 15 Day 35 Day 40 Day
Type 12 45

Supply A 0 10 0 0 0 0 5 0

Item A1

Record Item Day 2 Day 5 Day Day Day Day 35 Day 40 Day 45
Type 10 12 15

Demand A1 0 0 0 2 0 0 0 0

Supply A1 0 0 0 7 0 10 65 0

Item A2

Record Item Day 2 Day 5 Day Day 12 Day 15 Day Day Day
Type 10 35 40 45

Demand A2 0 2 0 0 0 0 0 0

Supply A2 0 35 0 17 0 0 5 0

The first demand of 50 units will be satisfied as item A2 ATP quantity is 50 on Day 12.
The next demand of 80 units can be met in two ways:
• Use substitute supplies from item A1 on Day 12 through Day 40, so the promise
date is Day 40, or

• Use existing supply of 10 units on Day 5 and try to produce 70 units prior to the
request date of Day 35, assuming you have the capacity to produce by Day 35.

Considering these two options, Oracle Global Order Promising recommends an ATP
date of Day 35 based on the following supply:
• Planned order for 70 units of item A on Day 35.

• Supply of 10 units of item A on Day 5.

Oracle Global Order Promising suggests new supplies based on the profile MSC: Choice
of Item for Which to Create Supplies in Substitute Relationship setting, if the existing
supplies for a demanded item or the substitute items cannot meet the request on the
request date.


Substitution using Supplies Past Request Date
There is an ATP query for item A for 20 units on Day 10.
The setup details are:
• The substitution window width is 10 days for all items.

• Substitution between item A and A2 becomes effective starting on Day 15. All of the
other substitution definitions are applicable for the entire horizon.

• Infinite Time Fence Date is Day 35.

The profile MSC: Choice of Item for Which To Create Supplies in Substitute
Relationship is set to Demanded Item. The following tables show you the supply and
demand picture for items in the substitution chain:
Item A

Record Item Day 2 Day 5 Day Day Day Day Day Day
Type 10 12 15 21 30 45

Demand A 0 0 0 0 0 0 0 0

Supply A 0 2 0 2 0 1 2 0

Item A1

Record Item Day 2 Day 5 Day Day 12 Day Day Day Day
Type 10 15 21 30 45

Demand A1 0 0 0 0 0 0 0 0

Supply A1 0 2 0 2 18 1 2 0

Item A2

Type 10 12 15 21 30 45

Demand A2 0 0 0 0 0 0 0 0

Supply A2 0 2 0 20 0 0 0 0

Oracle Global Order Promising evaluates the substitution relationship effectivity on the


ATP request date. Only substitution relationships valid as of the request date are valid
for the whole query. Oracle Global Order Promising does not evaluate the substitution
effectivity on every day. Thus, A2 is not a valid substitute for A.
By the request date, neither A or A1 has sufficient supply. Since the profile MSC: Choice
of Item for Which to Create Supplies in Substitute Relationship is set to Demanded
Item, Oracle Global Order Promising only evaluates the possibility of creating new
supply for A to meet the shortage of 18 units by the request date.
If you are able to produce 4 units of item A by the request date Day 10, then you can
satisfy 6 units out of 20 units by the request date.
So by the request date, you have 6 of A available and 2 of A1 available. Since Oracle
Global Order Promising does not support Partial Fulfillment, it looks forward for the
earliest date that the remaining shortage of 14 of A is available and the earliest date that
the remaining 18 of A1 is available.
For item A
• Using Scheduled Receipts: the earliest date that the shortage can be fulfilled using
scheduled receipts will be Day 35 (the infinite time date).
Creating Fresh Supplies: assume you can create fresh supplies for 14 units of item
A on Day 25.
So the earliest date that the 14 units of A is available is Day 25.

For item A1
• Using Scheduled Receipts: the earliest date that the shortage can be fulfilled using
scheduled receipts will be Day 15.
Creating Fresh Supplies: since the profile MSC: Choice of Item for Which To Create
Supplies in Substitute Relationship is set to Demanded Item, Oracle Global Order
Promising will not attempt to create fresh supplies for A1.
So the earliest date that the 18 units of A1 is available is Day 15.
A1 is available earlier than A. Thus, Oracle Global Order Promising recommends
A1 with available date of Day 15.

Creation of Planned Supplies
There are four items in the substitution chain, items: A1, A2, A3, and A4. The highest
level item in this pool is A4. You get a demand for A2, and the profile MSC: Choice of
Item for Which to Create Supplies in Substitute Relationship is set to Requested Item.
You can evaluate supply availability for A2, A3, and A4 assuming chaining and
direction is A1 to A2 to A3 to A4. If you do not find any supply for the requested item,
you can generate supply for requested item, which is A2.
If the item you try to produce happens to be a co-product, Oracle Global Order
Promising creates supplies for all items in co-product relationships. If your item is not
an item in coproduct relationship, it may be possible to produce a substitute item
instead of the demanded item, but please note that Oracle Global Order Promising will


create supplies for only one item. The exception to this rule is when a requested item is
involved in a coproduct relationship. If the profile MSC:Choice of Item for Which to
Create Supplies in Substitute Relationship is set to Follow Item Attribute, and the
requested item's Create Supply flag is set to No in the Master Item form, Oracle Global
Order Promising generates supplies for the next higher item in the substitution chain.
The following table summarizes this example:

Chaining Highe Reque Profile Creat Co- Action Generate
and st sted Option: e Prod Supply
Directio Level Item Choice Suppl uct?
n Item of Item... y
Flag

A1 to A2 A4 A2 Demand Yes No Evaluate Generate supply
to A3 to ed Item supply for requested
A4 availability for item.
A2, A3, and A4.

A1 to A2 A4 A2 Demand Yes Yes Evaluate Generate
to A3 to ed Item supply planned order
A4 availability for for requested
A2, A3, and A4. item and
co-product
supplies for the
rest of the items
in the
co-product
relationship.

A1 to A2 A4 A2 Follow Yes No Evaluate Create supply
to A3 to Item supply for A2. If
A4 Attribute availability for capacity is not
A2, A3, and A4. found, evaluate
generation of
supplies for
items A3 and
A4. Then the
supplies are
created for one
item.

A1 to A2 A4 A2 Highest Yes No Evaluate Create supply
to A3 to Level supply for A4.
A4 Item availability for
A2, A3, and A4.

Example
Evaluating Supplies After Request Date


One of the purposes behind substituting is to use up all the possible supplies before
creating fresh supplies. This applies to both native supplies and substitute supplies.
In this example, cases 1 to 4 are for a single organization. Case 5 is for a supply chain.
Case 1
A can be substituted by B. The substitute window for both items across the supply
chain is set to 15 days.
The supply situation is shown in the following table:

Type 10 12 15 20 25 45

Supply A 5 0 0 2 0 0 0 10

Supply B 0 2 0 8 5 3 10 0

There is an inquiry for 10 units of item A on Day 12, and the infinite time fence date is
set to Day 45.
The first step is to determine the availability by the request date either by requested
item or the substitute item. By the request date, you will have 7 units of item A and 10
units of item B.
Therefore, item B is suggested as a substitute because it can fulfill the entire quantity
using only the supply from one item. You are not able to look at the ATP details and
pegging for item A, but you have access to summary level information for item A. You
have also full access to the ATP details and pegging for item B.
Case 2

Type 10 12 15 20 25 45

Supply A 1 0 0 2 0 0 0 10

Supply B 0 0 0 8 5 3 10 0

In this example, there is also an inquiry for 10 units of item A on Day 12. The first step is
to evaluate the supplies prior to request date. You have 3 units of item A and 8 units of
item B. You have to evaluate the possible production prior to the request date.
If you produce 7 units of item A by Day 12 and 2 units of item B by Day 12, both items
A and B have a total supply of 10 units by Day 12. Given this scenario, Oracle Global


Order Promising promises the order on Day 12 using item A. If you have a choice
between the original item and a substitute item, Oracle Global Order Promising
promises with the original item.
Case 3
You have 10 units of existing supply for item B, 5 units of supply for item A and you
can produce 5 units of item A by the request date. Oracle Global Order Promising
recommends item B because it uses up the existing supplies rather than producing item
A.
Case 4
For this case, the profile MSC: Choice of Item for which to Create Supplies in Substitute
Relationship is set to Follow Item Attributes. The assumption is that supplies can be
created for both items.

Record Type Item Day 2 Day 5 Day Day Day Day Day Day
10 12 15 20 25 45

Supply A 5 0 0 2 0 1 10 0

Supply B 0 2 0 0 5 3 10 0

You have 7 units of item A by request date and 2 units of item B by the request date.
Assume you do not have the capacity to produce either item A or B by request date. The
availability and production of both A and B is evaluated in the forward direction.
Evaluating scheduled receipts, you can satisfy the requested quantity by using item B
by Day 20. If you use the production route, then assume you do not get the deficit
produced until Day 40. The request is satisfied by item B by Day 20.
Case 5
The following diagram shows the supply chain for item A and B:


Supply Chain for Item A and B

For this example, the profile MSC: Choice of Item for which to Create Supplies in
Substitute Relationship is set to Follow Item Attributes. The assumption is that supplies
can be created for both items.
Consider the following supply picture as shown in the following tables. The
substitution window is set to 15 days for both items A and B. Assume that the lead time
to transfer items across all organizations is zero. The request date is Day 10 and the
request quantity is 100 units. The infinite time fence date set to Day 26.
Org 1


Record Item Day 2 Day 5 Day Day 12 Day Day 20 Day 25 Day 45
Type 10 15

Supply A 5 0 0 2 0 0 10 0

Supply B 0 2 0 0 5 0 10 0

Org 2

Type 10 12 15 20 25 45

Supply A 10 0 0 0 2 0 16 0

Supply B 0 0 0 0 0 15 0 20

Org 3

Type 10 12 15 20 25 45

Supply A 0 5 0 0 0 48 5 0

Supply B 0 0 0 0 38 0 10 10

Org 5

Record Item Day 2 Day 5 Day Day Day 15 Day 20 Day 25 Day
Type 10 12 45

Supply A 0 10 5 0 0 2 63 5

Supply B 0 55 0 0 0 23 5 0

Oracle Global Order Promising evaluates the supplies for items A and B individually by
using up all the on-hand and scheduled receipts prior to the request date. Later, it tries
to produce the deficit by the request date.
If Oracle Global Order Promising is not successful in satisfying the request, it tries to
project the availability date for the requested item as well as its substitutes by choosing
the better date of:


1. Using scheduled receipts

2. Creating fresh supplies

Oracle Global Order Promising returns the item that gives the best available date.
Evaluating Item A Supply
On-hand + scheduled receipts available on request date:

Total Org 1 Org 2 Org 3 Org 5

35 5 10 5 15

Note: The order of the organization columns in the above table shows
the order in which Oracle Global Order Promising looks for supplies.

Creating new supplies on request date:
Assume there is no capacity to create new supplies on request date.

Total Org 5 Org 3 Org 1

0 0 0 0

the order that Oracle Global Order Promising is trying to create new
supplies.

There is a shortage of 65 of item A on request date. Oracle Global Order Promising
looks forward to project a date where the shortage is available. The earliest date that 65
units are available is Day 15. Remember that in the forward scenario: if there are
multiple sources for the supply, then Oracle Global Order Promising uses the source
that gives the best available date.
The following explains how Oracle Global Order Promising computes the availability
date.
• Org 1: scheduled receipts (Day 26 = infinite time fence)

• Org 1: transfer from Org 2 (Day 21 = the better date of the two sources in Org 2)


• Org 5: scheduled receipts (Day 25)

• Org 5: make (Day 21 = assume there is capacity to make 65 on Day 21)




Out of the four sources in Org 1, the transfer from Org 3 gives the best available date.
Thus for item A, Day 15 is the date the requested quantity is available.
Evaluating Item B Supply
On-hand + scheduled receipts available on request date:

Total Org 1 Org 2 Org 3 Org 5

57 2 0 0 55

the order in which Oracle Global Order Promising looks for supplies.

Creating new supplies on request date:
Assume there is no capacity to create new supplies on request date.

Total Org 5 Org 3 Org 1

0 0 0 0

the order that Oracle Global Order Promising is trying to create new
supplies.

There is a shortage of 43 of item B on request date. Oracle Global Order Promising looks
forward to project a date where the shortage is available. The earliest date that 43 units
are available is Day 17. Remember that in the forward scenario: if there are multiple


sources for the supply, Oracle Global Order Promising uses the source that gives the
best available date.
date:







Thus for item B, Day 17 is the date the requested quantity is available.
Based on the above calculations, you can meet the requirement either by using item A
on Day 15, or item B on Day 17. Oracle Global Order Promising suggests Item A on Day
15 with the following details:
• 35 units of scheduled receipts of item A by the request date.

• 65 units of production of item A in Org 3.

Allocated ATP With Substitution
This section explains how allocated ATP works if stealing is done ahead of substitution.
The allocation method used here is demand priority allocation. In this example, you
have two items: A and A1 that are substitutable. You have three demand segments
called tiers: T1, T2, and T3. The substitution window is 2 days. The profile MSC: Choice
of Item for Which to Create Supplies in Substitute Relationship is set to Follow Item
Attributes, and the assumption is that supplies can be created for both items.

Tier Day 1 Day 2 Day 3 Day 4 Day 5

T1-A 0 0 0 7 0



T1-A1 8 0 5 0 10

T2-A 5 0 1 4 0

T2-A1 0 0 0 0 0

T3-A 3 0 2 6 0

T3-A1 0 0 0 0 0

Assume that you have demand for 8 units of item A at tier T1 in Day 1. Oracle Global
Order Promising steals 5 units from tier T2 and 3 units from tier T3 to satisfy the order.
Note that it does not use the substitute available at tier T1. Then you have demand for
20 units at tier T1 on Day 3 for item A1 after satisfying the first request for 8 units.
For item A:
1. There are 3 units of supply across all tiers.

2. Assume that you do not have any capacity to produce item A prior to request date.

3. The deficit is 17 units.

4. As shown in the table above, you have 17 units of supply across all tiers by Day 4.
Please note that forward stealing is only available when demand priority allocation
is used.

5. Assume that you have the capacity to product 17 units by Day 7.

6. You can promise the order for Item A by Day 4.

For item A1:
1. There are 13 units of supply by request date.

2. Assume that you do not have any capacity to produce item A1 by the request date.

3. The deficit is 7 units.

4. As shown in the table above, you have no eligible existing supplies for A1 after the
request date.

5. Assume you can produce 7 units by Day 7.

Given the analysis above, Oracle Global Order Promising promises the order by Day 4


using item A.
Allocated ATP In a Supply Chain
Consider a five organization supply chain setup:


Five-Organization Supply Chain

The substitution window is 2 days for items A and B. In the following table, you get a
request for 50 units of item A in tier T1 at Day 3 in the supply and demand picture in
each organization. The infinite time fence date is set to Day 26. Assume there is no
intransit lead time. The profile MSC: Choice of Item for Which to Create Supplies in
Substitute Relationship is set to Follow Item Attributes, and the assumption is that
supplies can be created for both items. The profile MSC: Allocation Method is set to
Demand Priority.
Org 1



T1-A 0 0 0 2 10

T1-B 2 0 0 5 10

T2-A 2 0 1 4 0

T2-B 0 2 0 2 0

T3-A 1 0 2 6 0

T3-B 0 0 0 0 5

Org 2


T1-A 0 0 0 2 24

T1-B 0 4 0 15 3

T2-A 0 1 1 4 0

T2-B 2 0 0 2 0

T3-A 0 2 2 6 0

T3-B 5 0 0 0 5

Org 3


T1-A 0 0 2 0 40

T1-B 0 0 0 0 0

T2-A 0 2 0 14 0



T2-B 0 0 0 2 0

T3-A 2 0 0 6 0

T3-B 0 0 0 0 5

Org 5


T1-A 0 0 0 2 10

T1-B 0 0 5 5 10

T2-A 0 0 1 4 0

T2-B 2 2 0 2 0

T3-A 3 5 2 6 0

T3-B 6 0 0 0 5

Evaluating Item A Supply
• By the request date, there are 29 units of Item A available across all tiers in the
supply chain.

• Assume that you do not have the capacity to produce Item A by the request date.

There is a shortage of 21 of item A on the request date. Oracle Global Order Promising
looks forward to project a date where the shortage is available. The earliest date that 21
units are available is Day 5. Remember that in the forward scenario: if there are multiple
sources for the supply, Oracle Global Order Promising uses the source that gives the
best available date.
date:



• Org 2: scheduled receipts (Day 5 = 36 are available across all tiers in Org 2)






Thus for item A, Day 5 is the date the requested quantity is available.
Evaluating Item B Supply
• By the request date, there are 30 units of Item B available across all tiers in the
supply chain.

• Assume that you do not have enough capacity to produce Item B by the request
date.

There is a shortage of 20 of item B on request date. Oracle Global Order Promising looks
forward to project a date where the shortage is available. Remember that in the forward
scenario: if there are multiple sources for the supply, Oracle Global Order Promising
uses the source that gives the best available date.
date:
• Org 1: scheduled receipts (Day 5, 22 are available across all tiers in Org 1)








Out of the four sources in Org 1, using scheduled receipts in Org 1 gives the best
available date. Thus for item B, Day 5 is the date the requested quantity is available.
Based on the above calculations, you can meet the requirement either by using item A
on Day 5, or item B on Day 5. Therefore, Oracle Global Order Promise suggests item A
on Day 5, with the following details:
• 29 units of scheduled receipts of item A by the request date across all tiers.

• 21 units of scheduled receipts of item A by Day 5.

ATP Result

Integration with Order Management
Oracle Global Order Promising allows the calling application to decide when end item
substitution can occur. This is done through a parameter in the ATP application
program interface.
When an ATP inquiry or ATP scheduling occurs before an order is booked, Oracle
Order Management calls Oracle Global Order Promising with end item substitution
enabled. After an order is booked, the order is no longer eligible for automatic
substitution in subsequent rescheduling activities.
When substitution is enabled and Oracle Global Order Promising recommends a
substitute item during scheduling, the requested item is replaced by the substituted
item.
For details on how Oracle Order Management displays substitute item, see Automatic
Item Substitution within Order Management in Oracle Order Management User's Guide.

Display of the Substituted Item in the ATP Details Window
You can access the ATP Details window either by selecting Availability within the
Oracle Order Management Sales Order Pad or by selecting ATP Details within the
Oracle Global Order Promising ATP Criteria window.
When substitution happens, the ATP Details window shows the following information:


ATP Details Window

When you request 100 units of item A, you see the following details in the ATP Details
window provided that Item B is substituted for Item A.

Item Org UO Qt Shi Availab Origin Availa Origin Origin Origin
M y p le Qty al Item ble al Item al Item al Item
Dat by Qty Reque ATP ATP
e Reques by st Date Date Date
t Date ATP Qty Qty
Date

B M1 Ea. 100 Da 20 A 100 50 Day 20 75
y 10

Table field descriptions:
• All of the fields except Original Item, Original Item Request Date Qty, Original Item
ATP Date, and Original Item ATP Date Qty will be for item B.

• The Original Item column is the requested item.

• The Original Item Request Date Quantity refers to the quantity of the original item
available by request date.

• The Original Item ATP Date provides you the date by which the entire requested
quantity can be provided using original item.


• The Original Item ATP Date Quantity provides you the quantity that is found on
the Original Item ATP Date. The available quantity can be more than the requested
quantity.

ATP Pegging Details
ATP Pegging shows the supply and demand pegging for the substitute item.

End Item Substitution Workflow
When the profile MSC: Enable ATP Workflow is set to Yes, a workflow notification is
sent once the substitution occurs at the time of sales order scheduling. The following is
a diagram depicting this workflow. The title for the workflow that is generated is
Demand Satisfied Using End Item Substitution. This workflow is initiated upon
scheduling of sales orders in Oracle Order Management.


Demand Satisfied Using End Item Substitution Workflow

The following details are shown in the workflow:
• From Item: the item for which you received the demand; the exception is for this
item.

• Order Number: sales order number.

• Line Number: sales order line number.

• Original Quantity: requested quantity.

• Substitute Item: the item to which the demand was transferred.


• Organization: shipping organization.

• Substituted Quantity: demand transferred quantity.

Support for Lot Based Components
Material requirements typically scale proportionally in many manufacturing
environments. For example, the number of hard disks required to build computers
would scale proportionally to the requirements quantity. However, in certain scenarios
you may want to include a certain component in fixed amount irrespective of the job
quantity or yield. The support for lot based material usage allows you to calculate
material requirements based on materials used for a specific "lot" of end items or
products.

Business Application:
Support for lot based components allows the planner to calculate material requirements
based on materials used per lot of the assembly. In a business environment, this is also
referred to as requirement calculated on the basis of lot or batch. The following
scenarios will explain the concept in detail:
When assembly component is lot based:
In this scenario you can include a fixed amount of material that will be used for the
entire lot of the assembled products irrespective of the size of the lot or batch. For
example, you manufacture door panel assemblies, each of which consists of an injection
molded panel and a lock. As part of the job start process, you will produce a fixed
number of plastic door panels to cycle in the process so that you get the parameters set
correctly. In such a scenario, you may want to include a certain weight of plastic resin
that will be used in the job in the Bill of Material irrespective of the job quantity.
When non-assembly component is lot based:
In this scenario you can include a fixed amount of material will not be a part of the
yield, but will be used to initialize or activate the entire lot of end products irrespective
of the size of the lot or batch. For example, during the manufacture of DVDs, a test kit is
issued to each job. The test kit contains a CD and instructions that are used to initialize
the process. A single test kit is used for the whole job.
When all components in the assembly are lot based:
In this scenario you can include a fixed amount or number of material that can be used
to test the effectiveness of the assembled lot or batch irrespective of the size of the lot or
batch. For example, during the manufacture of gas cylinders, your quality assurance
procedures may require you to perform a destructive test on the first cylinder
produced, regardless of the job quantity.
For discrete manufacturing environment, the enhancement allows the planner to
calculate the requirements for fixed amount of material used for a lot or batch of


assembled products. For process manufacturing environment, this enhancement allows
the planner to calculate material requirements in fixed amount or amount expressed in
integer for a lot or batch of assembled products. The following examples discuss lot
based material usage in discrete and process manufacturing environments:
In discrete manufacturing environment:
Let us take a scenario, where window locks are assembled using housing, screws, and
cleaning solutions. The requirements of housing and screws will be directly
proportionate to the requirement of window locks and hence will be calculated on "Item
Basis" (Where material requirement is measured in proportion to per unit of end item).
The requirement of cleaning solution is, however, independent of the requirement for
window locks and will thus be fixed irrespective of the size of the "lot" of end items
assembled.
The material requirement picture for the above scenario is as follows:

Component UOM Basis Quantity per Required
Assembly for 500
units of
Assembly

Main Carriage Each Item 1 500

Screw Each Item 2 1000picture

Cleaning Solution Gallon Lot 1 1

In process manufacturing environment:
Let us take a scenario, where food supplements are produced using base dough, mixed
berries, and lemon juice. The material requirements for mixed berry and base dough
scale proportionally to the finished good requirement, whereas the lemon juice directly
contributes to the yield of the finished product. Thus, the material requirement for
lemon juice remains constant at 100 oz, irrespective of the quantity of food supplement
to be produced. Note that in Global Order Promising, the requirements of the
proportional scaled items increase proportionally, without considering whether the
fixed scaling item contributes to yield or not.
The material requirement picture for the above scenario is as follows:

Component UOM Basis Formula Quantity after
Quantity Scaling

Food Supplement Proportional Lbs 400 800
(Finished Good)


Component UOM Basis Formula Quantity after
Quantity Scaling

Mixed berry Proportional Lbs 200 400

Base dough Proportional Lbs 100 200

Lemon Juice Fixed Oz 100 100

Scaling Types Used for the Support for Lot Based Components
The following scaling types are used while calculating material requirements for a
component in Oracle Process Manufacturing:
• Fixed scaling: In this case the material requirements for a component in an
assembly do not change based on formula quantity or quantity requested. The
component quantity used in the assembly remains same irrespective of the size of
the lot or batch of finished products. For both discrete and process manufacturing
environment, this scaling type enables lot-based material requirements.

• Proportional scaling: In this case the material requirements for a component in an
assembly are measured in proportion to the formula quantity, requested quantity,
or based on the list of components required in the assembly. For both discrete and
process manufacturing environment, this scaling type enables item-based material
requirements.

• Integer scaling: In this case the material requirements for a component in an
assembly are measured in integers and in multiple of integers. The user should
specify the rounding direction and the rounding variance for integer scaling. Note
that Oracle Global Order Promising does not support this scaling type.

Setup
Perform the following steps to enable the support for lot based components:
In the Bills of Material window, define the following:
1. Basis for calculating material requirement:In the Main tab of the Bills of Material,
• Select Item for item based calculation

• Select Lot for lot based calculation


Bills of Material Window

2. Scaling type: In the Formula window for the Ingredient Lines, select the scaling
type in the Scaling Type drop-down list.


Formula for Ingredient Lines Window

Business Process:
After you define lot based material requirements in the Bills of Materials window, this
data is then collected into the planning server. The following steps explain the business
process for the support for lot based components:
1. The user defines lot based material requirements and scaling type for a component
in the end item's Bill of Material (BOM).

2. The system checks whether the organization is discrete manufacturing or process
manufacturing.

3. The ATP process checks whether the scaling type is selected as Fixed Scaling or
Proportional Scaling. The ATP process uses the bill of materials used by the
manufacturing organization to decide on the scaling type and usage quantity.
1. For both discrete and process manufacturing process, if the scaling type is
selected as Fixed Scaling, the material requirement is calculated based on lot
based components.


2. For process manufacturing process, if the scaling type is selected as
Proportional Scaling, the material requirement is calculated based on item
based components. Discrete manufacturing does not support Proportional
Scaling. By default the material requirement is calculated based on item based
components.

3. For Integer scaling the following factors are considered:
• Scale Multiple: A factor used to convert component requirements to an
integer

• Rounding Direction: A factor that indicates whether the integer quantity of
the component must be rounded up or down.

• Rounding Variance: The allowed variance (deviation) of the integer
quantity from the non-integer quantity, in percentage terms, with the
non-integer quantity as the basis ensures ingredient requirements scale in
integers and in multiple of integers.

4. The Order Promising process is not impacted by the lot based material usage
enhancement and is executed as usual.

5. The results of the lot based material usage functionality can be reviewed in the ATP
details screen.

Note: The Order Promising process is not impacted by the lot based
material usage enhancement and is executed as usual.

• A lot based component can be a phantom item.

• In case of lot based and fixed scaled components, if the quantity of
component present is less than the lot-size requirement, we will
consider it zero.

• In case of Configure-To-Order (CTO) items, the optional and
included items cannot be lot-based. Only Standard Mandatory
Components (SMC) may be specified as lot based.

• Lot-based component is used to calculate material requirement
once per planned order created by a Capable To Promise (CTP)
process. Thus, in case of backward and forward CTP, lot based
component may be used twice.


24x7 ATP Support
Oracle Global Order Promising provides 24x7 support for processing ATP requests.
When you run a plan with the 24x7 support option enabled, Oracle Global Order
Promising creates a copy of the original plan. When the supply chain is being refreshed,
the plan is run on the plan copy and the original plan is available for processing ATP
requests.

When you have worldwide customer services or a 24x7 web store, you need around the
clock order promising capability so that your customers can get immediate delivery
quotes for their orders. This means that ATP must be up even when the underlying
supply chain plan is being refreshed. The 24x7 ATP support option provides you with a
plan to process ATP inquiries even when the plan is being refreshed.

Setup
1. Set the MSC: ATP 24x7 Synchronization Downtime profile option to specify an
acceptable downtime duration (in minutes).
If the order volume is high, the synchronization process can take some time to
complete as it not only synchronizes the orders during plan run, but also the orders
entered during the synchronization process. This profile enables you to shut ATP
down for the desired period of time to allow the synchronization process to
complete. Oracle Global Order Promising translates the downtime to a total number
of orders based on the current synchronization speed. When the number of orders
that are left to synchronize are at a threshold that may be sequentially processed in
the time specified in the MSC: ATP 24x7 Synchronization Downtime profile option,
ATP will be shut down. The default value is 10 minutes.

2. Set the MSC: Action Allowed on ATP 24x7 Plan While Running profile option to
control whether the manual updates are allowed to the original plan while the plan
copy is running.
Any action taken during this time will not be migrated to the latest plan copy.
Manual steps may be required to apply these changes to the latest copy of plan.

To run a plan in 24x7 mode:
1. Log on with the Advanced Supply Chain Planner responsibility.

2. In the Navigator, select Supply Chain Planner > Supply Chain Plan > Names.



4. In the Supply Chain Plan Names window, select a plan.

5. Mark the ATP checkbox.

6. Click Launch Plan.
The Parameters window appears.

Parameters Window

7. Set Enable 24x7 ATP to Yes.

8. Click OK.

9. In the Launch SCP Plan window, click Submit.

To view the status of the ATP plan:
In the Navigator, select Supply Chain Planner > Workbench.
The Navigator window appears.


Navigator Window

The ATP plan is visible in the Planner Workbench only if the MSC: Action Allowed on
ATP 24x7 Plan While Running profile option is set to Yes. If this profile option is set to
No, the ATP plan is displayed in the View Plan window.

Note: When a 24x7 ATP plan is running, the Plan > Online Replan
menu option remains disabled.


ATP Logic
Consider the following example:
• Original ATP plan = Plan A

• Copy of the original ATP plan = Plan B

Note: Note: Plan B is created by the system and is not visible to
users.

When the plan run is in process on Plan B and you enter new orders, Oracle Global
Order Promising provides you with schedule dates that can be promised against Plan
A.
At the end of the plan run, the synchronization process takes place. In this process,
orders scheduled against Plan A (during the plan run on Plan B) are checked against the
new plan data in Plan B. If it is not possible to meet the original schedule date in Plan A,
an exception will be raised. The original schedule date of the sales order will not
change. You can view the following results in the Planner Workbench:
• Orders that are synchronized appear in the Planner Workbench.

• Orders with schedule dates that cannot be met by Plan B are listed under the Over
Commitment of Sales Order exception of Plan B.

The orders are synchronized until there are no more to synchronize or to a point
specified in the MSC: ATP 24x7 Synchronization Downtime profile option. At this
point, ATP is shut down temporarily. All the remaining sales orders, if any, are
synchronized. Plan B now becomes Plan A. All new sales orders from this point
onwards are promised against the new ATP plan.

Technical Notes
1. Some scheduling transactions, such as orders with many lines, may run longer than
the downtime. The synchronization process will continue to run for an extended
period of time even after the new plan is in place to ensure that these transactions
are processed. The extended time is the maximum of 10 minutes or the time set in
the MSC: ATP 24x7 Synchronization Downtime profile option.

2. If you terminate the synchronization concurrent request for some reason, make sure
that the underlying process is terminated at database level before you kick off
another synchronization process. Consult your DBA to check whether the database
processes are complete.


Impact of failures during a 24x7 plan run
This section discusses the impact of failures during various stages of a 24X7 plan run. A
plan run can fail during:
• The refresh snapshot process

• Memory based planning

• ATP post plan processing

• 24x7 ATP synchronization

The impact of a failure and the action that you need to take are discussed in the
following sections.

Scenario 1: Failure during the refresh snapshot process
When the refresh snapshot process for the 24x7 plan run fails, the original plan will be
available for ATP inquiry. However, the refreshed plan will not be available.
You need to re-launch the plan to complete the plan run process. You can run
collections as an optional step as this process has an impact on the synchronization time
based on the number of records that need to be synced between the original plan and
the plan copy and might help in minimizing the time taken for the synchronization
process.

Scenario 2: Failure during memory based planning
When the memory based planning fails, the original plan will be available for ATP
inquiry. However, the refreshed plan will not be available. All new scheduling requests
continue to be scheduled against the original plan.
You need to re-launch the 24x7ATP plan run along with the memory based planning to
complete the plan run process. You can run collections as an optional step as this
process has an impact on the synchronization time based on the number of records that
need to be synced between the original plan and the plan copy and might help in
minimizing the time taken for the synchronization process.

Scenario 3: Failure during ATP post plan processing
When the ATP post plan processing fails before synchronization can begin, the original
plan will be available for ATP inquiry. The refreshed plan will be ready from the
planning perspective (visible in the Planners Workbench). However, the ATP post plan
processing will not be complete.
You need to re-launch the ATP post plan processing after analyzing/resolving the issue
reported in log file. The ATP 24x7 synchronization process will automatically continue
after the post plan processing steps are complete.


Scenario 4: Failure during 24x7 synchronization
The failure during ATP 24x7 synchronization can occur at the following three instances:
• Before the downtime

• During the downtime, and before the plans are switched

• After the plans are switched

The impact of failure in case of all the three instances are discussed in the following
sections.

Failure before downtime:
In this scenario, the original plan is still available for ATP inquiry. The refreshed plan is
ready from the planning perspective (visible in the Planners Workbench). However, the
ATP post plan processing is not complete.
You need to re-launch the 24x7ATP synchronization process. The synchronization will
continue from where the process stopped during failure and continue till completion.

Failure during downtime, and before the switch plan process:
In this scenario, the original plan is still available for ATP inquiry. The refreshed plan is
ready from the planning perspective (visible in the Planners Workbench). However, the
ATP post plan processing is not complete.
When the 24x7 synchronization process fails and it is not possible to identify the error
type like in rare cases when the Advanced Supply Chain Planning concurrent manager
is down, the 24x7 synchronization process might not be able to restore the original plan
for ATP inquiry. Therefore, ATP will remain in downtime.
You need to re-launch the 24x7 ATP synchronization process to immediately enable the
original plan for ATP inquiry. The plan run will then go through the downtime, the
switch plan process, and then complete the process.

Failure after the switch plan process:
Any failures after the switch plan process is complete, will have minimal impact on the
system. The refreshed plan will be available for ATP inquiry.
It is possible that some of the schedule requests, which are lined up for processing
during the extended synchronization process might not be processed and may not be
available in refreshed copy. Manual steps may be required to resolve such issues.

Multiple Plans
If you use planning output for ATP, then Oracle Global Order Promising supports the
inclusion of multiple plans. To include multiple plans, check the Inventory ATP
checkbox for all the plans that ATP needs to use in the plan options form.


As Oracle Global Order Promising moves in its search, it chooses a plan for each item.
Each move in a search could be down one level in the Bills of Material in a multi-level
search or across the supply chain as per the assignment set. The plan that is picked must
be a successfully run plan, and should have a unique combination among item,
organization, instance and demand class. If there are multiple occurrences of this set,
the plan which has the lowest plan identification number is picked. There should be
only one plan checked for ATP for a combination of item/org.
Thus, if two ATP-able plans contains same item/organization combination, ATP uses
the most recently completed plan. This makes the plan selection more accurate and
deterministic, specifically, as the plan ID may change in case of 24x7 ATP.
There may be situations where one plan is used as the source for another plan. For
example, an MPS plan is the source for an MRP run. If the feeder plan serves as a
supply schedule for a component of an end item, you should check the plan that
contains the end item for ATP. Otherwise, you can enable either the feeder plan or the
destination plan for ATP.

Improved ATP Performance Based on Summarized Data
Oracle Global Order Promising response times can be improved by means of a
summary approach that stores summary supply and demand information in a separate
table. It allows each ATP request to quickly retrieve summarized availability
information without computing availability from detailed supply and demand.
The summary process is accomplished through the concurrent program ATP Post Plan
Processing. The concurrent program is automatically launched at the end of an ATP
plan run. You manually run this concurrent program for a non-ATP plan and then
enable ATP flag of this plan.

ATP based on summarized data allows you to quickly retrieve summarized availability
information without computing availability from detailed supply and demand data.
This means you can provide quick response to customers whenever an order is placed.
The end result is the same as using detailed data to an end user. It is highly
recommended that you use summarized data.

Setup

To enable ATP based on summarized data:
1. Set the system profile MSC: Enable ATP Summary Mode to Yes.

2. Run the ATP Partitions concurrent program. You only need to run this program
once before you enable summary mode.


Oracle Global Order Promising supports two types of summarization processes:
• Full summarization

• Incremental summarization

To launch full summarization:
Run ATP Post Plan Processing.
• This program is automatically launched after the plan run if the plan is ATP
enabled.

• If you run the plan without enabling ATP and then you enable ATP, this program
will not be launched. You need to manually launch this concurrent program.

If you need to re-run the full summarization process, you need to run ATP Post Plan
Processing again.

To launch incremental summarization:
Run Load ATP Summary Based on Planning Output.
Incremental summarization adds the new supply and demand data since the last
summarization onto the existing summarized data. You need to schedule to run the
Load ATP Summary Based on Planning Output at regular intervals.

ATP Logic
Summarization means to add up the supply and demand data on a regular basis and
store the net availability picture. It improves performance because of less supply
demand data to process for each ATP request.
The full summarization process takes place after the plan run.
Incremental summarization processes only those data that are new or changed since the
last summarization. You can continue with your ATP transactions during both the full
summarization and incremental summarization processes.

• If you are using Allocated ATP based on User Defined Allocation
Percentage, summarization is not supported.

• If the profile MRP: Calculate SupplyDemand is set to Yes, Oracle
Global Order Promising always uses detailed data for processing.

Manually Generating Summary Tables
While the summary tables required to support summary data based order promising


are automatically triggered by the planning processes, you can also load the summary
data by manually invoking the ATP Post Plan Processing concurrent program. You may
want to do this if you do not want to rerun a plan before enabling summary data based
order promising.
You can manually generate the Oracle Global Order Promising summary tables from
either the Oracle Advanced Supply Chain Planner responsibility or the Oracle Order
Management Super User responsibility.

To manually generate the Summary Tables from the Advanced Supply Chain Planner responsibility:
1. Log in using the Advanced Supply Chain Planner responsibility.

2. From the Navigator, select Other and Request.

3. Select the Submit a New Request button.

4. Select Single Request to submit a single concurrent request.

5. Select OK.
The Submit Request window appears.

6. From the list of values in the Names field, select ATP Post Plan Processing.

7. Select a plan name in the Plan parameter.

8. Select Submit.

Unplanned Items
Once an ATP inquiry is initiated for an item that is not planned, then Oracle Global
Order Promising cannot find the item in any plan. It automatically reverts to an ATP
inquiry on the basis of collected data. If enough supply is not available, Oracle Global
Order Promising performs forward scheduling. It cannot perform the next level bills of
material explosion. For example, Oracle Global Order Promising cannot perform a
capable-to-promise check since it does not know which plan to use.

Note: Unplanned items refer to items not appearing in the ATP plan.
They do not refer to items with the Planning Method item attribute of
Not Planned.

Honoring Plan Recommendations for Sales Order Rescheduling
If you promise orders based on first-come-first-serve basis and need to process an
expedite order, the planning engine has the capability of planning by priority. The


planning engine recommends rescheduling of the sales order based on the supply
condition. It also recommends alternative shipping warehouses if the original shipping
warehouse cannot meet the sales order demand due date. Therefore, the planning
engine suggests an earlier fulfillment date for the expedite order and Oracle Global
Order Promising honors the date suggested by planning.
Oracle Global Order Promising nets the sales order demand on the planned ship dates
or organizations suggested by planning. After the sales orders rescheduling
recommendations are implemented, Oracle Global Order Promising uses the implement
date to net the sales order demand. A planner may implement a ship date different
from the planned ship date.

To use the plan recommended date for netting orders:
Set the profile MSC: Horizontal Plan Demand Bucketing Preference to Plan
Recommended Date.
• If you wish to net the demand on the schedule ship date of the sales orders, set the
profile to Demand Due Date.

• Oracle Advanced Supply Chain Planning may recommend a
different ship dates for sales order lines in a ship set or arrival
set. Oracle Global Order Promising may net demand of the
different order lines on the different plan ship dates.

• If Oracle Advanced Supply Chain Planning recommends an
alternative warehouse for shipping, Oracle Global Order
Promising does not use the original warehouse for netting
irrespective of the profile setting.

ATP Support for Distribution Planning
The distribution planning process enables you to establish an effective distribution
network for movement of materials by generating detailed material distribution plans.
The plans you create can be short-term executable plans that outputs a movement plan
on each of the lanes of the distribution network or a longer term plan that provides a
higher level material distribution plan.

Distribution planning provides global visibility to inventory positions in both external
and internal locations. For the short term plans, this process involves continuous
decision making to maintain target inventory levels at each of the destination locations
and safety stock levels at each of the source locations to be able to react to uncertainties
in the demand picture. Oracle Global Order Promising supports the customers to place


orders against the distribution network through ATP.
The ATP support for Distribution Planning process enables the user to be benefited in
the following ways:
• React to tight supply situations (Delay in supply arrival from supplier, production
shortfalls in manufacturing plants, etc.) with allocation strategies.

• Replenish inventories on time according to the consumption patterns.

• Minimize inventory write off (wastage/spoilage).

• Reduce overall cost of inventory and material movement.

Setup
In the MPSMRP Planning tab of the Master Item window, select the Distribution
Planned checkbox to enable Distribution Plans for your organization. For more
information on setting up the distribution network for your organization, see Oracle
Advanced Supply Chain Planning Implementation and User's Guide.

Note: To work with distribution plans, you require the "Distribution
Planner" responsibility.

ATP Logic
ATP adheres to the following logic to create the supply/demand records for distribution
plans. Note that the sourcing rules and their impact on ATP are same for distribution
plans as for the ASCP plans.
1. ATP identifies the supplies and demands to be included in netting. Note that the
basic algorithm for supply/demand netting is similar to the ATP process on ASCP
plans.

2. ATP provides Supply/Demand netting and ATP capability for the distribution
plans. Note that the changes in supply/demand netting honor the DRP
order/origination types.

3. If there is no supply in the distribution organization, ATP will create a demand
record of type Planned Inbound Shipment for the ordered quantity.
For a DRP Kit, Constrained Kit Demands will be created for the items included in
the kit for the ordered quantities on the planned arrival date.

4. ATP carries out Supply/Demand Netting in the transfer from the manufacturing
organization. If there is an excess supply, the demand is satisfied from the
manufacturing organization and ATP will then create a planned order in the


manufacturing (source) organization.

5. In the distribution organization, ATP will update the supply record of type Planned
Inbound Shipment with the source organization.

Important: Global Order Promising does not support the following for
distribution plans:
• Allocated ATP: Global Order Promising does not support
Allocated ATP for distribution plans. A warning message in Plan
Names window would be displayed if the Allocated ATP profile is
enabled and a distribution plan is enabled for ATP. This rule holds
true for all flavors of Allocated ATP..

• Circular sourcing: Circular sourcing is not enabled in ATP, though
it is enabled in Distribution Planning. For more information on
circular sourcing, see, Advanced Supply Chain Planning

• Product family based ATP: Global Order Promising does not
support product family based ATP on distribution plans.

For detailed instructions on distribution plans, see Oracle Advanced Supply Chain
Planning Implementation and User's Guide.


6
ATP Inquiry and Order Scheduling

• ATP Inquiry
• Diagnostic ATP
• Order Scheduling
• Shipping, Receiving, and Carrier Calendars

ATP Inquiry
ATP Inquiry is typically performed through an application that can place orders or
quotes. This type of application makes a call to Oracle Global Order Promising with
information such as item, request date, quantity, or shipping warehouse. Oracle Global
Order Promising returns availability information such as quantity available on request
date or earliest available date (if the request cannot be met on the request date). Then
the application decides what specific information to display to the end user.
Oracle Global Order Promising has its own user interface to allow users to perform
availability checks. Using this interface, you can obtain the detailed information
returned by Oracle Global Order Promising. This section explains this user interface.
The following diagram describes the information flow through the Oracle Global Order
Promising windows:

ATP Inquiry and Order Scheduling 6-1

The Selection of Windows

Each window is explained in detailed in the sections that follow.

ATP Criteria
ATP Criteria lets you enter parameters for the desired ATP check.
To enter ATP Criteria:
1. Choose ATP. Then select ATP Inquiry.
The ATP Criteria window opens.


ATP Criteria Window

The following table contains the fields and options in the ATP Criteria window:

Note: Not all of these fields are required.

Field Description

Pick Sources This field controls whether Oracle Global Order Promising should
use all the possible shipping organizations or only use the
organization you specify.

• Choose No to have Oracle Global Order Promising perform an
availability check in the warehouse you specify.

• Choose Yes to have Oracle Global Order Promising return all
the shipping warehouses, so that you can select the specific
organizations on which you want Oracle Global Order
Promising to perform an availability check. Thus, you can view
availability from multiple supply organizations.

If you choose No, the ATP Details button appears on the lower
right corner of the screen. If you choose Yes, the Pick Source button
appears on the lower right corner.


Field Description

Line Set Choose from Ship Set, Arrival Set, or [Blank].

• Ship Set indicates that the lines you enter need to be shipped
together.

• Arrival Set indicates that the lines you enter will arrive
together at the receiving party.

Customer Enter the customer name. If you leave this field blank, the default
receiving party is your login organization. Only collected
customers appear in this list.

Site Enter the customer site.

Request Date Type Choose between Ship Date or Arrival Date. This tells Oracle Global
Order Promising whether the request date you enter in the Request
Date field is meant to be request ship date or request arrival date.

Assignment Set This is a view only field. If the ATP Inquiry window is launched at
the source or destination instance, this field shows what is in the
profile MRP: ATP Assignment Set. If you perform Pick Source,
Oracle Global Order Promising uses the sourcing assignment set to
search for all possible shipping organizations.

Demand Class Choose the demand class from a list of values.

Org Specify the shipping organization. If you selected Pick Source as
Yes, you do not need to enter a value in this field.

Item Specify the item.

ATP Rule This is a view only field. It shows the ATP Rule defined for the item
or organization.

UOM Enter the unit of measure (UOM) for the item. If this UOM is not
item's primary UOM, Oracle Global Order Promising coverts it to
the primary UOM for calculations.

Qty Enter the request quantity.

Req Date Enter the request date. If you leave it blank, Oracle Global Order
Promising uses today's date for the request date.


Field Description

Item Description This is a view only field. It shows the item description.

2. Select ATP Details.
The ATP Details window appears with the ATP details and the pegging tree. The
pegging tree shows how the demand is being met.

ATP Details

ATP Details Window

The ATP Details window has two regions:
• Summary region

• Pegging region

Summary Region
The summary region is a folder form.


Note: Not all fields are shown by default.

The following table describes each field in this window:

Field Description

Item Shows the requested item.

Quantity Shows the requested quantity.

Org Shows the shipping organization.

Request Date Qty Shows the quantity available on the request date.

Ship Date Qty Shows the quantity available on the date that the request quantity
can be met. The quantity can exceed the requested quantity.

Arrival Date Shows the arrival date. Arrival date equals ship date plus transit
lead time.

Request Date Shows the request date.

Request Date Type Shows either Ship Date or Arrival Date, based on the selection.

UOM Shows the primary unit of measure of the requested item.

Group Ship Date Shows the group ship date for a set, if the request is for a set.

Group Arrival Date Shows the group arrival date for a set, if the request is for a set.

Ship Method Shows the ship method that is passed from any calling application
or default ship method defined for the shipping organization and
receiver.

Shipment Method Shows the description of the ship method.
Description

Transit Lead Time Shows the lead time associated with the above ship method.

Demand Class Shows the demand class associated with the request.

Message Shows any error or warning message.


Field Description

Customer Shows the customer on the request.

Ship To Show the ship-to site of the customer.

Latest Acceptable Date Shows the date beyond the request date that the ATP request
should be considered successful, if the requested quantity can be
met.

Arrival Set Shows the set identifier passed by any calling application for
grouping items in an arrival set.

Ship Set Shows the set identifier passed by any calling application for
grouping items in an ship set.

Line Shows the order line number passed by any calling application for
indication of demand line number.

Plan Name Shows the ASCP plan name used for Oracle Global Order
Promising, if ATP is based on planning output.

Original Item Shows the requested item. The item field shows the substituted
item.

Original Item Request Shows the availability of the requested item on the request date.
Date Qty The Request Date Qty field shows the availability of the substituted
item on the request date.

Original Item ATP Date Shows the earliest date the requested quantity for the requested
item is available.

Original Item ATP Date Shows the quantity available on the Original Item ATP Date. The
Qty available quantity may exceed the requested quantity.

Status Not used.

Days Late Shows the days between the request date and date the supply is
available for the item.

Matched Configuration This field is only applicable for an ATO model request. When
Oracle Global Order Promising finds a matched configuration, the
configuration item is displayed in this field.


Pegging Region
ATP Pegging region further explains how Oracle Global Order Promising obtains the
ATP results. Pegging is shown for each line in ATP Details: Summary Region.

For ATP Based on Collected Data
Oracle Global Order Promising first checks the availability on the request date. If there
is a shortage, then Oracle Global Order Promising finds a date beyond request date
when the shortage can be met. The pegging depicts this logic.
For example, a request for item A on Day 10 for quantity of 20 for Org 1. Only a
quantity of 5 is available on request date, but the shortage can be met on Day 12.
Pegging shows the following:
• Line 1: A - Org 1 Qty 20 On Day 10
Line 2: A - ATP Org 1 Qty 5 On Day 10
Line 3: A - ATP Org 1 Qty 30 on Day 12

Explanation:
• The first line represents the demand.

• The second line represents the supply available on request date.

• The third line represents the earliest date that the remaining demand can be
satisfied. The availability on that date is 30.

For ATP Based on Planning Output
When Multi-Level Supply Chain ATP is enabled, the pegging shows how Oracle Global
Order Promising searches for supply throughout the supply chain.
Pegging Example: Supply Chain Bills of Materials (BOM): Item A can either be made in
Org1 or transferred from Org2. Making item A is priority 1, as seen with Make(1). Also,
Component X can be supplied from either S1 or S2.


Supply Chain BOM

Other setup:
• Item A has a 1 day fixed lead time, and no variable lead time.

• Item A has no post-processing lead time.

• Component X has a 1 day post-processing lead time, but no pre-processing lead
time.

• S1 does not have processing lead time.

• S2 has a 2 day processing lead time.

• Transfer(2) shows the transfer of item A from Org2 to Org1, which takes a 1 day
transfer lead time.

Cumulative Availability based on on-hand plus scheduled receipts is depicted in the
following:
Note that D1 = today.

Org D1 D2 D3 D4 D5

A - Org1 0 0 40 80 120

X - Org1 0 10 10 10 10

Y - Org1 0 30 90 0 0

Z - Org1 10 50 50 0 0

S1 10 10 10 10 0


Org D1 D2 D3 D4 D5

S2 10 10 10 10 0

A - Org2 10 50 100 100 0

An order for item A with a quantity of 100 on D4 gives the following pegging:
1 (D) A - Org1 Qty 100 on D3
2 (S) A - ATP Org1 Qty 40 on D3
3 (S) A - Make At Org1 Qty 20 on D3
4 (D) X - Org1 Qty 20 on D2
5 (S) X - ATP Org1 Qty 10 on D2
6 (S) X - Buy S1 Qty 0 on D2
7 (D) X - Qty 10 on D1
8 (S) X - ATP Qty 10 on D1
9 (D) Y - Org1 Qty 20 on D2
10 (S) Y - Org1 Qty 30 on D2
11 (D) Z - Org1 Qty 20 on D2
12 (S) Z - Org1 Qty 50 on D2
13 (S) A - Transfer From Org2 Qty 40 on D3
14 (D) A - Org2 Qty 40 on D2
Explanation:

• (D) represents the demand line. Demand lines, except the first demand line, indicate
the actual demand that can be placed. They do not indicate what is required.

• (S) represents the supply line. Supply lines have the following types:
• ATP: supply from on-hand and scheduled receipts.

• Make At: supply can be obtained from a Make At source.

• Transfer From: supply can be obtained from a Transfer From source.


• Buy From: supply can be obtained from a Buy From source.

• Line 2: on request date (D3), there are 40 available for A. There is a shortage of 60.

• Line 3: Oracle Global Order Promising finds components available to make 20 of A.
Lines 4 to 12 explain why.

• Line 4: to make A on D3, X is needed on D2 because of the lead time offset.
However, only 20 of X can be demanded on D2. Lines 5 and 8 explain why.

• Line 5: there are 10 of X available in Org1on D2.

• Line 6: 10 units of X can be obtained from supplier S1 on D2. Lines 7and 8 explain
why.

• Line 7: X is needed from S1 on D1 due to a 1 day postprocessing lead time of X.
Only 10 units of X can be demanded from S1. Line 8 explains why.

• Line 8: on D1, there are only 10 of X available from S1. S2 has a Buy From source
and a 2 day processing lead time. There is not enough time to meet demand on D1.
Since Oracle Global Order Promising does not use S2, there is no pegging shown for
S2.

• Line 9: only 20 of X is available. Oracle Global Order Promising looks for 20 of Y.
More does not help. On D2, 20 of Y can be demanded. Line 10 explains why.

• Line 10: there are 30 of Y available on D2. If there are less Y, Oracle Global Order
Promising would readjust X to demand less quantity.

• Line 13: since there is still shortage of 40, Oracle Global Order Promising looks for
supply at the Transfer From source. 40 of A can be transferred from Org2 on D3.
Lines 14 and 15 explain why.

• Line 14: demand for A is placed in Org2 on D2 due to a 1 day transfer lead time.

• Line 15: there are 50 of A available on D2.

For details on ATP Logic, see: ATP Logic, page 6-19.
To view further details:
1. Select a supply line of the pegging tree.

2. Right-click to drill down to ATP details.
The available options are:
• Expand


• Show Late Supply Only

• Show Constraints

• Horizontal Plan

• Supply/Demand

• Supply

• Demand

• Properties

Note: To be able to drill down to ATP detail, you must set the
profile MRP: Calculate Supply Demand to Yes before you
initiate the ATP Inquiry
However, when the profile MRP: Calculate Supply Demand is
set to Yes, Oracle Global Order Promising performs extra work
to retrieve and retain the detail. This makes ATP performance
slower. You should only set this profile to Yes for analysis
purpose.

Expand
Right-click and select Expand.
When you select this option, all the lower nodes under the pegging line that you have
selected are expanded.
For example, if you highlight a pegging line for a sub-assembly and right-click to select
Expand, the pegging tree displays all the detail pegging lines for that sub-assembly.

Show Late Supply Only

2. Right-click and select Show Late Supply Only.
When you select this option, the pegging region displays only those sales order
lines that are receiving late supplies.

Supply/Demand
Right-click and select Supply/Demand.
This window shows supply and demand for the selected line of the pegging tree.


Supply/Demand Window

For an item, all of the supply and demand up to the item's infinite time fence appears in
the Supply/Demand window. For a resource, all the supply and demand over the entire
ASCP plan horizon appears.
The following table describes each field in this window:

Field Description

Group Availability Date This field is currently not populated.

Organization Code This field is currently not populated.

Demand Class This field is currently not populated.

Item/Resource Indicates the item or resource of the pegging line.

Type Indicates if it is an item or resource.

UOM Shows the primary unit of measure of the item or resource.

Date Shows the due date of supply or demand.


Field Description

Supply/Demand Type Shows the supply or demand type.

Identifier Shows the identifier of the supply or demand.

Quantity Shows the quantity of the supply or demand.

Horizontal ATP
Right-click and select Horizontal Plan.
The Horizontal ATP window shows material or resource availability in a horizontal
time scale. It shows total demand, total supply, net available-to-promise, and
cumulative available-to-promise.
• For ATP based on collected data: the time horizon equals the item's infinite time
fence defined in the ATP rule, or the date of last supply or demand.

• For ATP based on planning data: the time horizon equals the item's infinite time
fence or the end of the plan horizon (if the infinite time fence is not defined).

Properties
Right-click and select Properties.
The Properties window appears.


Properties Window

Depending on whether you are viewing the properties of an item or a resource, the
Properties window displays different fields. The Properties window for an item
contains two tabs: Main and Other.
The display of values in the various lead time fields depends on the type of item
(make/buy) and whether Oracle Global Order Promising uses a specific lead time for
computing the order promising dates for the item.
For lot based components, the Other tab of the Properties window for a selected pegged
item in the ATP Details window displays the following fields:
• Component Yield: Displays the percent of the amount of the selected item present
in the assembly.

• Usage: The value displayed in this field defines the physical amount of the


component used (1 unit, 2 units, etc.)

• Scaling Type: Displays either Lot or Item based on the calculation basis of material
requirements.

• Rounding Direction: Displays the factor that indicates whether the integer quantity
of the component must be rounded up or down.

• Scale Rounding Variance: Displays the allowed variance (deviation) of the integer
quantity from the non-integer quantity, in percentage terms, with the non-integer
quantity as the basis. If no rounding variance is specified, it is assumed to be 0%.
This means that no deviation is allowed from the proportionally scaled quantity. In
such a case, the scale multiple would not impact the requirement of that
component.

• Scale Multiple: A factor used to convert component requirements to an integer.
The value displayed in this field also ensures that components are consumed in
multiples of the scaling factor.

In addition, the item quantity displayed in the pegging tree will also be based on the
selected basis for material requirements.

Note: The Pegging region of the ATP Details screen also displays both
forward ATP and forward CTP pegging information.

Example
For a make item, Oracle Global Order Promising calculates the processing lead time
using the following equation:
• Processing lead time = fixed lead time + quantity * variable lead time

For a buy item, Oracle Global Order Promising uses the following values:
• Preprocessing lead time

• Processing lead time

• Postprocessing lead time

Therefore, depending on the lead time data required for an item, the lead time fields
display data in the Properties window.

Diagnostic ATP
When you perform an ATP inquiry, the ATP Details window provides you with the
explanation on how the demand is satisfied. When a particular source (make, buy, or
transfer) does not have any supply, the pegging region in the ATP Details window will


not show the source. If you need to analyze the result and find out the constraint, you
can perform an ATP inquiry in the diagnostic mode. In addition to all the detail views
mentioned above, you can:
• View all the supply sources on the pegging tree

• Filter the pegging tree to show only the constraint nodes

• View additional details about the pegging line like property, supply/demand, and
horizontal plan.

When a source of supply does not have any availability during a capable-to-promise
check, a planner might want to diagnose the underlying constraint that leads to a
promise date being later than the request date. ATP Detail/Pegging displays the
constraints and lets you quickly determine the reasons for not being able to return a
promise date that meets the request date.

To view supply constraints in the Diagnostic ATP mode:
responsibility.


3. Select ATP > ATP Inquiry.
The ATP Criteria window appears.

4. Select Tools > Enable Diagnostic ATP.

Tools Menu Options

5. Enter your ATP criteria in and click ATP Details.
The ATP Details window appears.


ATP Details Window: Diagnostic ATP Mode

6. View the constraint(s) in the pegging region.

Show Constraints

2. Right-click and select Show Constraints.

Note: Note: The Show Constraint option is enabled only in the
diagnostic ATP mode.

When you select this option, it only expands the paths that contain constraints under
the pegging line that you have highlighted. The rest of the nodes in the pegging tree
will be abbreviated, represented by (+).
For example:
An order for item A with a quantity of 100 on D4 gives the following pegging:
1 - (D) A - Org1 Qty 100 on D3
3 - (S) A - Make At Org1 Qty 10 on D3
4 - (D) X - Org1 Qty 20 on D2


6 - (S) X - Buy S1 Qty 0 on D2
7 - (D) X - Qty 10 on D1
8 - (S*) X - ATP Qty 0 on D1 (Material Constraint)
9 - (D) Y - Org1 Qty 20 on D2
10 (S) Y - Org1 Qty 30 on D2
11 - (D) Z - Org1 Qty 20 on D2
12 (S) Z - Org1 Qty 50 on D2
13 - (S) A - Transfer From Org2 Qty 50 on D3
14 - (D) A - Org2 Qty 50 on D2
If X is the only constraint, the pegging tree with the Show Constraint option displays
the following:
1 - (D) A - Org1 Qty 100 on D3
3 - (S) A - Make At Org1 Qty 10 on D3
4 - (D) X - Org1 Qty 20 on D2
6 - (S) X - Buy S1 Qty 0 on D2
7 - (D) X - Qty 10 on D1
8 - (S*) X - ATP Qty 0 on D1 (Material Constraint)
9 + (D) Y - Org1 Qty 20 on D2
10 + (D) Z - Org1 Qty 20 on D2
11 + (S) A - Transfer From Org2 Qty 50 on D3

ATP Logic
In diagnostic mode:
• ATP checks across the supply chain to perform backward scheduling and shows all
the constraints encountered during scheduling of the requested quantity.

• If demand is not met by the request date, then ATP does not perform a forward
scheduling to project a date on which the demand could be met.

• ATP does not project the partial amount that could be available by the request date.


• ATP does not provide information about the substitute item that is used in place of
the requested item in regular ATP inquiry.

• The full requested quantity is placed as demand at each node. However, if that
node has additional sources, then the last source for that node opens a planned
order supply equal to the demand placed at that node, minus the planned order
supplies acquired from other sources.

Note: When you perform Diagnostic ATP, the response is slower
than non Diagnostic ATP because Oracle Global Order Promising
needs to store all the pegging data during diagnostic ATP.

When you enable the diagnostic mode, each constrained pegging line in the pegging
tree is appended with the type of constraint and the earliest due date of the planned
order. The types of constraints that you can see on the pegging line are:

Manufacturing lead time constraint
For a make item, when Assembly Requirement Date - (preprocessing lead time + fixed
lead time + quantity * variable lead time) < Today, no supply can be obtained and the
supply pegging line will show 0 as the supply quantity. ATP categories this as a
manufacturing lead time constraint.
For example:
Assembly A has component B
Fixed lead time = 0
Variable lead time = 0.1 day
The pegging tree for 100 of A on D5 in Org 1 will look like:
(D) - DEMAND A Org 1 Date 5 Qty 100
(S) - ATP A Org 1 Date 5 Qty 0
(S*) - Make A Org 1 Date -1 Qty 0 (Manufacturing Lead time Constraint: Due Date D6)
Explanation:

• (D) represents the demand line. Demand lines indicate the actual demand that can
be placed. They do not indicate what is required.

• (S) represents the supply line. Supply lines have the following types:
• ATP: supply from on-hand and scheduled receipts.


• Make At: supply can be obtained from a Make At source.

• Transfer From: supply can be obtained from a Transfer From source.

• Buy From: supply can be obtained from a Buy From source.

• (S*) represents the supply line with a constraint.

• On the requested date D5, A is not available. Therefore, there is a shortage of 100.

• Oracle Global Order Promising finds components available to make 100 of A only
on D6, which is one day after the requested date. This is a manufacturing lead time
constraint.

Purchasing lead time constraint
For a buy item, when Requirement Date - [postprocessing lead time - preprocessing
leave time - (the approved supplier list's processing lead time or item's processing lead
time)] < Today, no purchase supply can be obtained and the supply pegging line will
show 0 supply quantity. ATP categories this as a purchasing lead time constraint.
For example:
Item A is purchased from supplier S1.
A's postprocessing lead time = 2 days
Preprocessing lead time = 1 day
S1's processing lead time = 3 days
(D) - Demand A D5 Qty 100
(S) - ATP A D5 Qty 0
(S*) - Buy A S1 D -1 Qty 0 (Purchasing Lead time Constraint. Due Date: D6)
Explanation:
Org 1 cannot buy any quantity of B from S1 due to the processing lead time of 3 days
required for S1, and the preprocessing lead time of 1 day as well as postprocessing lead
time of 2 days for Org 1. This is a purchasing lead time constraint.

Transfer lead time constraint
For a transfer item, when Requirement Date - (postprocessing lead time + transit lead
time) < Today, no supply can be transferred and the Transfer From supply pegging line
shows 0 as the supply quantity. ATP categorizes this as a transfer lead time constraint.
For example:
Item A is transferred from Org1 to Org2.


A's postprocessing lead time=2 days
(D) - Demand A Org 2 D1 Qty 100
(S) - ATP A Org 2 D1 Qty 0
(S*) - Buy A Org 2 D1 Qty 0 (Transfer lead time constraint. Due Date: D2)
Explanation:
Item A has a postprocessing lead time of 2 days and cannot be transferred on D1 from
Org 2. This is a transfer lead time constraint.

Planning time fence constraint
When no supply can be created due to a planning time fence constraint, the supply
pegging line shows 0 as the supply quantity.
For example:
Assembly A has component B.
Fixed lead time = 0
Variable lead time = 0.1 day
Planning time fence date = D5
(D) - DEMAND A D5 Qty 100
(S) - ATP A D5 Qty 0
(S*) - Make A D5 Qty 0 (PTF Constraint. PTF Due Date: D5)
In this example, the planning time fence due date is more constrained than the
manufacturing lead time date. When two constraints are met for a supply line, Oracle
Global Order Promising follows two rules to decide the constraint to be displayed on
the pegging line:
1. When the lead time constraint and planning time fence constraint both exist, the
pegging line displays the constraint that causes a later due date. If the due date in
both the cases are equal, then the planning time fence constraint is displayed.

2. When a pegging line encounters a lead time or a planning time fence constraint, no
further pegging will be available.

Material/resource constraint
ATP marks all the lowest level supply nodes that do not satisfy the demands as material
or resource constraints. A lowest level node is a node that does not have any sources to
fulfill the residual demand left after consuming the ATP quantity. The nodes that
qualify for this category are:


• ATP node for supplier

• ATP node for resource

• ATP node for an item for which ATP Components flag is set to N in a organization

ATP categorizes a supply line as a material or resource constraint depending on the
type of constraint met while scheduling for the requested quantity.
Resource constraint:
When there is not enough availability for a resource, ATP categorizes this as a resource
constraint.
For example:
Item A needs to be made and transferred from Org 2 to Org 1.
Intransit lead time = 1 day
(D) - Make A Org 2 D4 Qty 5
(D) - Demand R Org 2 D4 Qty 30
(S*) - ATP R Org 2 D4 Qty 20 (Resource Constraint)
Explanation:
• On D4, 5 of A needs to be made in Org 2 due to a 1 day intransit lead time.

• To make A on D5, R is needed on D4 because of the lead time offset. Demand for 30
of R is placed in Org 2 on D4 due to a 1 day intransit lead time.

• On D4, there are only 20 of R available in Org 2. This is a resource constraint.

Material constraint:
When Oracle Global Order Promising looks for supply for an item, it first checks to see
if there is existing on-hand supply or scheduled receipts. This is called ATP quantity. If
there is not enough supply, it then performs a capable-to-promise check to see if the
item is available through a make, transfer or buy sources option. When the ATP
quantity is less than the required quantity and there is no other source to obtain the
supply, ATP categorizes this as a material constraint.
For example:
Item A needs to be bought by Org 1 from supplier S1.
The pegging tree for 30 of A on D2 in S1 will look like:
(D) - Demand A S1 D2 Qty 30
(S*) - ATP A S1 D2 Qty 5 (Material Constraint)
Explanation:


• On D2, demand for 30 of A is placed in S2.

• On D2, there are only 5 of A available in S2. This is a material constraint.

Calendar constraint:
If the schedule ship or arrival date falls on a non working day, Oracle Global Order
Promising categorizes this as a a calendar constraint.
For example:
Org 1 needs item A from supplier S1 on D2. The transit lead time is 1 day and D1 is a
non working day for S1.
The pegging tree for 30 of A on D2 in S1 will look like:
(D) - Demand A S1 D2 Qty 30
(S*) - ATP A S1 D2 Qty 5 (Calendar Constraint)
Explanation:
• On D2, demand for 30 of A is placed in S2.

• D1 is a non working day for S1 and the transit lead time is 1 day. Therefore, Item A
cannot arrive at Org 1 on D2. This is a calendar constraint.

Global Availability
When you have Pick Source set to Yes and you have selected Pick Source, the ATP
Sources and Global Availability window, as seen below, opens. Selecting Pick Source
with the Yes setting triggers Oracle Global Order Promising to use sourcing rules to
find all the possible shipping organizations.


ATP Sources and Global Availability Window

The following table describes the fields in this window:

Field Description

Pick Indicates whether or not the item will be picked.

Org Organization short code.

Supplier Not currently used.

Site Not currently used.

Ship Method Shows the default shipping method defined for the shipping
organization to the receiving party. Oracle Global Order
Promising accepts Ship Method as a parameter in its Calling API.

If any calling application calls ATP with a specific Ship Method,
Oracle Global Order Promising checks to see if the ship method
is defined in Transit Lead Time as a valid ship method between
the shipping organization and receiving party. If it is a valid ship
method, Oracle Global Order Promising honors it. Otherwise, it
uses the default ship method. If there is no default ship method,
a 0 lead time if assumed.

Lead Time Shows the lead time associated with the ship method.

Once you select or deselect the shipping organizations, then you can retrieve the ATP
Details to obtain ATP results for each selected shipping organization.


Order Scheduling
This section discusses the features that help you schedule requests in Oracle Global
Order Promising.

Ship Date and Arrival Date Calculation
Scheduling sales orders for ATP as well as non-ATP items is carried out through Oracle
Global Order Promising. Oracle Global Order Promising calculates supply at day level
and returns Schedule Ship Date and Schedule Arrival Date with a timestamp of
23:59:00.
Note that ATP does not support time zones. There could be discrepancies in the time
stamps of the scheduled ship date when compared to request dates. You can see
discrepancies in the scheduled ship date even if you have existing inventory.
The timestamp display of 23:59:00 is applicable to all of the following:
• ATP and non-ATP items

• Override and non-override mode scheduling

• ATP based on planning or ATP based on collection

• Single line request and Set request

• Requests with or without the latest acceptable date

If ATP is based on planning output, Oracle Global Order Promising creates supply and
demand orders with the timestamp of 23:59:00 in the plan. The orders include:
• Demand date of sales order

• Demand date of planned order demand in the Planners Workbench

• Supply date of planned order in the Planners Workbench

• Resource requirement date

Note: Oracle Global Order Promising performs the return date
calculation by checking the Scheduled Arrival Date against
shipping, receiving, and carrier calendars. For details, see:
Shipping, Receiving, and Carrier Calendars, page 6-34.

Examples
A few examples to illustrate how Oracle Global Order Promising calculates the


Schedule Ship Date and Schedule Arrival Date in different scenarios are given in the
following sections.
In all the 3 examples, assume that:
• The transit lead time is 0.

• The receiving calendar is setup as 24x7.

Non-ATP items with past due and non-past due request dates

Scenario Description ATP Return Date

A single line request for a non-ATP • Schedule Ship Date = 20-DEC-2003 23:59:00
item with a non-past due request date.
• Schedule Arrival Date = 20-DEC-2003 23:59:00
• Requested ship date = 20-DEC-2003
10:23:57

• System date = 12-DEC-2003
13:20:26

Two lines request for non-ATP items in For line 1:
a ship set with non-past due request
• Schedule Ship Date = 20-DEC-2003 23:59:00
dates.

• Requested ship date for line 1 = • Schedule Arrival Date = 20-DEC-2003 23:59:00
20-DEC-2003 10:34:27
For line 2:
• Requested ship date for line 2 =
25-DEC-2003 11:34:17

• • Schedule Arrival Date = 25-DEC-2003 23:59:00
System date = 12-DEC-2003
13:20:26
For the group:

• Group Ship Date = 25-DEC-2003 23:59:00

• Group Arrival Date = 25-DEC-2003 23:59:00



an arrival set with non-past due request
• Schedule Ship Date (1) = 20-DEC-2003 23:59:00
dates.

• Requested arrival date for line 1 = • Schedule Arrival Date (1) = 20-DEC-2003
20-DEC-2003 10:34:27 23:59:00

• Requested arrival date for line 2 = For line 2:
25-DEC-2003 11:34:17
• Schedule Ship Date (2) = 25-DEC-2003 23:59:00
• Schedule Arrival Date (2) = 25-DEC-2003
13:20:26
23:59:00

For the group:



A single line request for a non-ATP • Schedule Ship Date = 12-DEC-2003 23:59:00
item with a past due request date
• Requested ship date = 5-DEC-2003
10:23:57

13:20:26



a ship set with past due request dates
10-DEC-2003 10:34:27 • Schedule Arrival Date = 12-DEC-2003 23:59:00

• Requested ship date for line 2 = For line 2:
5-DEC-2003 11:34:17
13:20:26

For the group:



an arrival set with past due request
dates

• Requested ship date for line 1 = • Schedule Arrival Date = 12-DEC-2003 23:59:00
10-DEC-2003 10:34:27
For line 2:
5-DEC-2003 11:34:17

• • Schedule Arrival Date = 12-DEC-2003 23:59:00
System date = 12-DEC-2003
13:20:26
For the group:



Note: The Group Ship Date and Group Arrival Date is displayed as the
Schedule Ship Date and Schedule Arrival Date for the set on the sales
order.

ATP and non-ATP items in the same request but not in a set



Two lines where: For line 1:

Line 1 = Non-ATP item • Schedule Ship Date =
20-DEC-2003 23:59:00
Line 2 = ATP item

The ATP item is available in sufficient quantity on the • Schedule Arrival Date =
requested date. 20-DEC-2003 23:59:00

• Requested ship date for line 1 = 20-DEC-2003 For line 2:
10:34:27
• Schedule Ship Date =
• Requested ship date for line 2 = 25-DEC-2003 25-DEC-2003 23:59:00
11:34:17
• Schedule Arrival Date =
• System date = 12-DEC-2003 13:20:26 25-DEC-2003 23:59:00

ATP and non-ATP items in the same request and in a set


Two lines in a ship set where: For line 1:

Line 1 = Non-ATP item • Schedule Ship Date = 20-DEC-2003 23:59:00

Line 2 = ATP item • Schedule Arrival Date = 20-DEC-2003
The ATP item is available in sufficient 23:59:00
quantity on the requested date.
For line 2:
20-DEC-2003 10:34:27 • Schedule Ship Date = 25-DEC-2003 23:59:00

• Requested ship date for line 2 = • Schedule Arrival Date = 25-DEC-2003
25-DEC-2003 11:34:17 23:59:00

• System date = 12-DEC-2003 13:20:26 For the group:





Two lines in an arrival set where: For line 1:

Line 1: Non-ATP item • Schedule Ship Date = 20-DEC-2003 23:59:00

Line 2: ATP able item • Schedule Arrival Date = 20-DEC-2003
The ATP item is available in sufficient 23:59:00
quantity on the requested date.
For line 2:
20-DEC-2003 10:34:27 • Schedule Ship Date = 25-DEC-2003 23:59:00

• Requested ship date for line 2 = • Schedule Arrival Date = 25-DEC-2003
25-DEC-2003 11:34:17 23:59:00

• System date = 12-DEC-2003 13:20:26 For the group:



Override ATP
The override ATP feature enables you to schedule a sales order on a date earlier than
the product available date. You can schedule an order on a date where there is not
enough supply or on a non-working day.
A Sales order overcommitment exception will be generated when you override ATP
and you can view the exception in the Planner Workbench. In addition to this, you can
send workflow notification to concerned users such as planners.

During business transactions, due to exceptional circumstances, you might have to
schedule and ship orders for which your supply chain plan does not show availability.
For instance, there could be occasions when:
• You receive a fresh demand and it is possible to bring the supply in early to meet
the demand

• You can use the capacity that is allocated to another product's forecast for the
requested product

• You decide to push out an existing low priority order to accommodate the higher
priority order


• You need to ship an order on a non-working date.

In such scenarios, you might want to override ATP and make a commitment to your
customer. Global Order Promising provides you with the option of allowing authorized
users to override ATP.

Setup
1. Set the profile option OM: Authorize to Override ATP to Yes.

2. Set the profile option MSC: Enable ATP Workflow. This is optional and can be set if
you want to send a notification to any responsibility like Advanced Supply Chain
Planner or Distribution Manager.

To Override ATP:
You can override the ATP on a sales order using the Sales Order window in Oracle
Order Management.
For details on how Oracle Order Management performs an ATP override, see
Overriding ATP in Oracle Order Management User's Guide.

ATP Logic
Using Oracle Order Management, you can override the Schedule Ship Date or Schedule
Arrival Date depending on the request date type.
• When the Schedule Ship Date is overridden, Oracle Global Order Promising
calculates the arrival date by adding the transit lead time to the Schedule Ship Date.

• When the Schedule Arrival Date is overridden, Oracle Global Order Promising
calculates the ship date by offsetting the transit lead time. If the ship date falls on a
non-working day according to the manufacturing calendar of the shipping
organization, the ship date is moved to the previous working day.

Once the Schedule Ship Date is determined, Oracle Global Order Promising will
perform the same supply consumption calculation assuming the request date is the
Scheduled Ship Date. Any shortage beyond the request date may trigger creation of
new supply through capable-to-promise process with due date beyond the request date.

Note: You can only override a date and not time. Oracle Global Order
Promising will use the end of day timestamp (23:59:00) for any
scheduling actions.

Example
Supplies and Demands for A and B are as follows. B is a component of A. A's


manufacturing lead time is 1 day.
For item A

Record Type Item D1 D2 D3 D4

Supply A 0 0 0 0

Demand A 0 0 0 0

For item B


Supply A 0 10 10 10

Demand A 0 0 0 0

You have a sales order for 10 of A on D2, which cannot be met. Therefore, you perform
an override ATP. The supply/demand picture after override ATP is:
For item A


Supply A 0 0 10 0

Demand A 0 10 0 0

For item B

Record Item D1 D2 D3 D4
Type

Supply A 0 10 10 10

Demand A 0 10 0 0

Explanation: The ATP date when 10 of A can be promised is D3. However, an override
ATP has been performed to meet the demand on D2.


Shipping, Receiving, and Carrier Calendars
Oracle Global Order Promising checks the shipping and receiving calendars that have
been assigned to specific organizations, carriers, and customers for scheduling sales
orders. Oracle Global Order Promising ensures that the scheduled ship and arrival
dates on sales orders as well as the ship dates, dock dates on planned orders during the
Capable-To -Promise process fall on valid working days according to the various
shipping and receiving calendars.
Shipping calendars indicate when a shipment can start from a source organization or a
supplier. Use of the shipping calendar ensures that the shipment is shipped on a valid
day according to the shipping calendar of the shipping organization or the supplier.
Receiving calendars indicate when an organization or a customer can receive a
shipment into the facility. Use of the receiving calendar ensures that the shipment
arrives at the receiving site on a valid day according to the organization or customer's
receiving calendar.
Carrier intransit calendars indicate the days when a certain carrier operates for
transporting the shipment. Use of the carrier intransit calendar ensures that the
shipment is planned for transportation on a valid day according to the carrier calendar.
The duration of any shipment that uses the carrier accounts for the transit calendar.

In a supply chain, each entity like the supplier, manufacturer, and distribution center
can have its constraints or preferences for shipping or receiving goods in or out of their
facilities on specific days. For example, a manufacturing facility may be able to ship out
goods only on certain days of the week.
The support of shipping, receiving, and carrier calendars facilitates the process of
scheduling sales orders by checking the days on which each entity can perform the
required activity. Therefore, you can provide accurate dates during order promising.
This also helps in reducing the manual intervention required to adjust
shipping/receiving dates.

Setup
Perform the following steps to use calendars for scheduling ship and arrival dates:
1. Select Order Management > Shipping > Setup > Calendars > Assign.
The Assign Calendars window appears.


Assign Calendars window

2. Define the calendar that you need to use.

3. Run Collection.

4. Run an ATP enabled plan if the profile INV: Capable to Promise is set to ATP/CTP
Based on Planning Output.

For more details on setting up the calendars, see Oracle Shipping User Guide and Oracle
Advanced Supply Chain Planning Implementation and User's Guide.
If you do not want to use any calendar for scheduling ship and arrival dates, set the
profile MSC: Use Shipping/Receiving Calendars to No. When you set this profile to No,
Oracle Global Order Promising performs order promising without checking the
schedule dates against any calendar. This means that the response time of Oracle Global
Order Promising will be faster and therefore, improves the ATP performance.

ATP Logic
Oracle Global Order Promising verifies the schedule ship date against the shipping
org's calendar. It verifies the schedule arrival date against the carrier transit calendar as
well as the customer/site receiving calendar.
If the requested date does not fall on a shipping date, Oracle Global Order Promising
will move the request date to a prior shipping date. If there is availability on this date,


this becomes the schedule ship date. If availability is beyond this date but falls on a non
shipping date, Oracle Global Order Promising will use the next valid shipping date as
the Schedule Ship Date beyond the availability date.
For details on calendar constraint, see: Diagnostic ATP, page 6-16.

ATP Override
For a sales order with an ATP override, Oracle Global Order Promising leaves the
overridden date as it is and checks the other dates against the calendars. For example, if
you override the schedule ship date, Oracle Global Order Promising leaves the schedule
ship date and checks the transit lead time against the carrier calendar and the schedule
arrival date against the customer's receiving calendar.

Example
This example illustrates how Oracle Global Order Promising uses the shipping,
receiving, and carrier calendars.
Assume that the carrier transit time is 4 days.
The working and non-working days for the shipping, receiving, and carrier
organizations are as follows:

Calendar D1 D2 D3 D4 D5 D6 D7 D8 D9 D10
Type

Organization w w w - w w w - w w
shipping
calendar

Carrier w w w w - w w - w w
calendar

Customer w w - w w w w w - w
receiving
calendar

Note that w represents working days in the above table. The non-working days are left
blank.
If you have a sales order with the request ship date on D4, Oracle Global Order
Promising calculates the schedule ship date and schedule arrival date as follows:
• D4 is a non-working day for the shipping organization. Therefore, the schedule ship
date is D3.

• The carrier needs 4 days for transporting the items to the customers site. The carrier


organization has D5 and D8 as non-working days. Therefore, the carrier reaches the
customer's site on D9.

• The receiving organization has D9 as a non-working day. Therefore, the schedule
arrival date is D10.


7
Order Backlog Workbench

• Order Backlog Workbench
• Selection Criteria for Scheduling with the Order Backlog Workbench
• Scheduling Order Lines with the Order Backlog Workbench

Order Backlog Workbench
The Order Backlog Workbench is a powerful graphic tool that enables you to easily
manage the existing order lines you wish to reschedule. This workbench is especially
useful when a significant issue such as item shortage occurs within your supply chain,
manufacturing line, or distribution chain, and you need to react rapidly to reschedule
groups of order lines affected by the item shortage.
• Once you have selected orders for scheduling using system processing constraints
and user-defined controls, order lines are processed in a simulated scheduling
mode and presented for your review.

Note: You must first select and schedule order lines before you can
navigate to the Order Backlog Workbench.

During the review process, you can:
• Take actions based on system exceptions or errors resulting from simulated
scheduling.

• Update or modify the simulated scheduled dates or source organizations for order
lines presented.

• Choose to accept or cancel all simulated order line scheduling information.

• Choose to firm selected order lines for simulated rescheduling.

Order Backlog Workbench 7-1

• Choose to pick and accept a selected order line simulation results.

• View the Oracle Global Order Promising Pegging Detail information.

• Reschedule the order line information presented in the simulated schedule mode
again.

Once you are satisfied with your scheduling simulation results, save your changes, and
then your new order line scheduling information is updated for selected order lines.

Note: The Order Backlog Workbench does not support rescheduling of
the ATO model. It excludes any order lines that are part of an ATO
model or in a set with an ATO model during rescheduling.

Order Backlog Scheduling Process
1. Define Priority Rules: determine the processing order used when scheduling orders
through the scheduler.

2. Define Filter Criteria: enables you to determine order line selection criteria for
scheduling within the Order Backlog Workbench.

3. Schedule Orders using the Order Backlog Workbench.
1. Simulate Order Scheduling: shows the scheduling simulation results by:
• Exceptions

• Order Number

• Organization / Item

2. You can choose to:
• Firm all or selected simulated order lines scheduling results.

• Pick all or selected simulated order lines scheduling results.

• Save all scheduling simulation results.

• Cancel all scheduling simulation results.

• Modify the simulated order line schedule dates or source organization's
fields, and resimulate scheduling based upon modifications made,
performing any of the functions previously listed, until satisfied.

4. Save your work. Once your simulation work is saved, simulated order line schedule


dates and sources become the scheduled date and source organization for all order
lines selected.

Order Backlog Workbench User Interface
The Order Backlog Workbench consists of three panes within a window:
• Navigator Tree

• Reschedule Lines Results

• Order Line Pegging Information

Navigator Tree
The Navigator Tree controls the display of information for the Reschedule Lines Results
and Order Line Pegging panes within the Workbench. Drill down to the different levels
within the Exceptions, Orders, or Items tabs to view the order line and pegging
information.

Exceptions Tab
The Exceptions tab is the default tab displayed within the Navigation Tree pane upon
system display of the Order Backlog Workbench. This tab displays a tree containing the
order line exceptions that occurred during simulated scheduling.
Exceptions are grouped and displayed by exception type, and a corresponding number
is displayed to the right of each exception tree node to denote the number of
occurrences for each of the exception types that occurred during simulated scheduling.
Exception Tree Drill Down Details
• + Exceptions
+ Exception Folder Name
+ Order Number

Orders Tab
The Orders tab displays a folder tree of all orders selected for simulated scheduling.
Orders within this folder tree are displayed in the ascending order.
Order Tree Folder Drill Down Details
• + Sales Orders
+ Order Number
+ Independent (Order) Lines


Items Tab
The Items tab displays a folder tree of all items contained within order lines that were
selected for simulated scheduling. Items are displayed by an alpha numeric sort of the
organization to which they were scheduled against.
Item Tree Folder Drill Down Details
• + Organizations
+ Organization Name
+ Product Families
+ Product Family
+ Categories
+ Item Category Sets
+ Item Category Set code combinations

Reschedule Lines Results
The Reschedule Lines Results pane is used to display order line information based upon
cursor placement within the Navigator pane.
If the Item field is highlighted in yellow, simulated scheduling encountered an error
during processing, and the order line was not modified in any way. Specific scheduling
error messages can be seen in the Error column.
The Reschedule Lines Results pane displays the following order line information:
• Firm Checkbox

• Item

• Order Line Number

• Quantity Ordered

• Order Line UOM

• Ship from Org

• Ship Date (Scheduled Date)

• Scheduled Arrival Date

• Available Quantity

• Group Ship Date


• Group Arrival Date

• Request Date Quantity

• Requested Ship Date

• Requested Arrival Date

• Firm Source Org

• Firm Ship Date

• Firm Arrival Date

• Latest Acceptable Date

• Ship Method

• Lead Time

• Demand Class

• Ship Set

• Arrival Set

• Customer

• Location (Customer Site)

• Status (Order Line Status)

• Error

Order Line Pegging Information
The Order Line Pegging Information pane displays pegging information based upon
the cursor location within the Navigator tree.

Note: If there is no information contained within the Pegging
Information window based upon the cursor location within Order
Backlog Workbench:
• Entity referenced within the Navigator tree is not related to
pegging, such as Organization.

• The item or order line that is referenced is not ATP enabled.


• The item or order line does not currently reside in Oracle Global
Order Promising collection tables.

If you select a node element within the Order Line Pegging pane and select Details, the
Oracle Global Order Promising ATP Details window is displayed.
For more information on the ATP Details window, see ATP Details, page 6-16.

Selection Criteria for Scheduling with the Order Backlog Workbench
As a prerequisite, you must define at least one Sequencing (Priority) Rule prior to
utilizing the Order Backlog Workbench.

Priority Rules
The Oracle Advanced Planning Solution utilizes Priority Rules to determine the
processing order used when scheduling orders through the scheduler.
• You can choose to define a default scheduling order processing Priority Rule.

• You can choose to disable a Priority Rule.

• Or you can choose to define single or multiple criteria within a priority rule to
further define the processing order the scheduler utilizes during line scheduling.

Priority Rules are not instance specific and are defined by selecting specific criteria that
determine the order input to the scheduler.

Note: At least one priority rule must be defined prior to utilizing the
Order Backlog Workbench for scheduling.

To define Priority Rules:
1. Navigate to the Define Priority Rules window.


Define Priority Rules Window

2. Enter the Name for the Priority Rule.

3. Enter a Description for the Priority Rule.

4. Select the Enabled checkbox to enable the priority rule to be utilized by the
scheduler.

5. Choose to establish whether the priority rule will be used as the default priority
rule used during scheduling execution.
Select the Default checkbox to use the priority rule as the default rule.

Note: If another priority rule has been defined as the Default
Priority Rule and you select the Default checkbox, you are
presented with a decision box asking if you wish to update the
current default priority rule to the rule you are currently
modifying. Select Yes to update your default Priority Rule.

6. Select the Priority Rule criteria name in the Criteria Name field. Valid values are:
• Gross Margin

• Promise Date


• Request Date

• Sales Order and MDS Entities priority

• Scheduled Date

7. Select the criteria processing order the scheduler will use when scheduling order
lines. Enter a numeric value in the Criteria Priority field.

8. Save your work.

Note: Once a Priority Rule has been successfully saved, you can
only update the following information:
• Enabled checkbox

• Default checkbox

You may choose to add additional criteria to the Priority Rule.

To schedule orders using the Order Backlog Workbench:
1. Navigate to the Order Backlog Workbench.
The Schedule Orders window appears.

2. Determine your order selection with filter criteria for scheduling:
• Select the Filter Criteria Name and proceed to Step 3, or

• Select the Filter Criteria Name you wish to modify and select the Create/Edit
button, or

• Select Create/Edit if you wish to enter new filter criteria information.

Note: Select the Exclude Picked Lines checkbox to avoid
rescheduling of order lines that are pick released.

The Criteria folder window appears. The window title is Criteria.


Criteria Window

Create your order selection criteria for scheduling. Order selection is determined by
current order line status and the Filter Criteria you define.

• Order lines that have a current status of Shipped or Cancelled
are not selected for simulated scheduling.

• Order lines whose source is External, for example drop ship
order lines, are also not selected for simulated scheduling.

The Schedule Orders window utilizes Oracle Applications Folder technology to save
Filter Criteria for reuse. Users can choose to create filter criteria and save it to a folder,
or query an existing folder and modify the Filter Criteria. However, you are not allowed
to enter Filter Criteria for scheduling without first saving the criteria to a folder.
1. Either edit the Filter Criteria for the folder selected, or enter new filter criteria.
Select the Field name. Valid values are:
• Task
• Customer

• Item Name

• Order Number

• Project Number

• Promise Date

• Requested Arrival Date


• Requested Ship Date

• Scheduled Arrival Date

• Scheduled Shipped Date

• Ship from org

2. Select an operator for your criteria. Valid values are:
• Equals

• Is Not (Equal)

• Less Than

• At Most

• At Least

• Greater Than

• Between

• Outside

• Is Empty

• Is Entered

• Among

3. Choose to further define your query criteria values by entering limiting values in
the From and To fields. Enter values appropriate to the Field Name selected.
For example, if you are interested in displaying order lines that have a scheduled
order date two weeks from today, enter the present date in the From field, and a
date two weeks from the present date in the To field.

4. Save your work to a folder. From the File menu, select Save As to save your folder.
When you save your folder, there are several options available. Once you have
saved your folder, close the Criteria window
For more information on using folders within Oracle Order Management, see
Private Folders in Oracle Order Management User's Guide.

5. Select the scheduling Priority Rule.


6. Choose whether to overwrite or preserve all existing source organizations for
current order line sources during scheduling.
• Select No to use current order line source information. Use existing sourcing
rules and priority rules to determine order line schedule date.

• Select Yes to overwrite current order line source information. Use any source
for your order, based upon sourcing and priority rules for scheduling, and use
the modified sourcing information during scheduling to determine order line
scheduled date.

Note: If there is no order source specified on the order line, the
order source is determined by your Sourcing Rule ranking.
Ensure that your profile MRP: ATP Assignment Set is properly
defined.

7. Choose to manually sequence the processing order during scheduling for your
order lines or allow the system to schedule your order lines based upon the
sequencing rule chosen by selecting Manual Sequence.

Note: If you choose to allow the system to process order lines by
the Sequencing Rule chosen, proceed to Step e.

Manual Sequence enables a user, based upon query criteria, to schedule, sequence,
Firm, or delete order lines selected for rescheduling.
1. Once you select Manual Sequence, the system queries open sales orders based
upon filter criteria that contain order lines. Then the system displays the orders
based upon the Sequencing Rule selected in the Order Sequencing window.

2. Choose to Firm current order line information: Select the Firm checkbox if you
do not want a particular order line processing sequence to be modified when
selecting

3. Apply.
For example, suppose you update sequence 1 to sequence 5, sequence 6 to
sequence 8, and select the Firm checkbox for sequence 2. Once Apply is
selected, the order line associated with sequence 2 remains sequence 2.
If the Firm checkbox for sequence 2 had not been selected, then, based upon
your user changes, the order line originally associated with sequence 2 could
possibly be changed because of your re-sequencing.

4. Choose to update order processing sequence during reschedule. Select the line
you wish to modify, then update the sequence number assigned to the order


line.

5. Select Apply. This saves your new order line sequence to be used during
rescheduling.

6. Select Schedule to initiate simulated order line scheduling.
While scheduler is running, the user is presented with a Progress window to
track the reschedule process.
The Progress window continually updates the progress of rescheduling
concurrent program. The following information is displayed:
• Total Lines #: total order lines selected for scheduling.

• Remaining: total order lines remaining to be scheduled.

• Time Remaining: total time remaining to process order lines currently not
scheduled.

• Complete: total order lines current completed scheduling.

• Progress Indicator Bar: an indicator bar that graphically displays the
current order lines scheduled as a percentage of the total order lines
selected for scheduling.
Once the indicator bar reaches 100% and the Remaining field displays 0,
select OK to display scheduling results.
Results are presented within the Order Backlog Workbench.

Scheduling Order Lines with the Order Backlog Workbench
Once the order lines have been scheduled and processed, users are presented with the
Order Backlog Workbench, a graphical user interface that enables a user to review,
manage, and process simulated order line scheduling results.

To manage Simulated order line scheduling results:
1. Review the following reschedule exceptions generated during rescheduling process:

Note: Select Create/Edit in the Schedule Orders window and define
the criteria to search for the order lines to be re-scheduled.


Exception Name Message Received When...

Item Shortage ATP date is greater than the latest
acceptable date.

Modified Source The new shipping warehouse is different
from the original shipping warehouse.

Later Than Old Schedule Date The new schedule ship date is greater than
the old schedule ship date.

Later than Promise Date The new schedule ship date is greater than
the promise date.

Later than Request Date The new schedule ship date is greater than
the original request date.

Errors Unexpected error is encountered.

2. Choose to modify the schedule date and source organization's fields for order lines.

3. Choose to accept current order line scheduling information.

4. Choose to Firm current order line information.
Select the Firm checkbox if you:
• Want to accept current simulation scheduling information for an order line.

• Do not want a particular order line to be modified during any additional
simulated rescheduling that may occur within the workbench for the current
workbench simulation session.
For details, see Reschedule Lines Results, page 7-4

5. Choose to view Oracle Global Order Promising Details. If Oracle Global Order
Promising information is available for an item or order line, Details is enabled.
Select Details to be presented with the Oracle Global Order Promising ATP Details
window to review supply and demand, and horizontal planning details.
For more information on the ATP Details window, see: ATP Details, page 6-5.

6. Modify simulated scheduling information.
• You may modify only the Schedule Date and Source Organization fields for an


order line.

• You may choose to Firm an order line or group of order lines, and then process
new a new scheduling simulation using the current order line information by
selecting Reschedule.
For details, see Reschedule Lines Results, page 7-4.

Accept simulated scheduling recommendations. Select Save.
Once you select Save, all simulated scheduling results for order lines are committed
to the database. The Order Backlog Workbench closes, and the user is presented
with the Schedule Orders window.

7. Reject simulated scheduling recommendations. Select Cancel.
Simulated scheduling information is discarded, order line information is not
updated within the database, the Order Backlog Workbench closes, and the user is
presented with the Schedule Orders window.

Note: ATP in the Order Backlog Workbench is based on the detail
supply demand tables, regardless of the profile setting for MSC:
Enable ATP Summary Mode.


8
Troubleshooting

• Troubleshooting
• Debugging
• SQL Queries

Troubleshooting
This section provides a detailed explanation on Oracle Global Order Promising:
• Troubleshooting

• Debugging

• SQL Queries

Troubleshooting
The following are error messages Oracle Global Order Promising users may receive,
and how to troubleshoot these messages.

Note: The lookup codes are passed from the Oracle Global Order
Promising API to the calling module, which displays the error
messages to the users.

ATP Based on Collected Data Errors

Troubleshooting 8-1

Error Msg Code Message Received When... To Resolve this Message...

Try ATP again 130 The complete / target Wait until so_tbl_status in
later. collection or sales order msc_apps_instances is set to
collection is running. Null or 0.

Summary 160 The Load Summary Based on Wait until the Load Summary
Concurrent Collected Data concurrent Based on Collected Data
program is program is running in concurrent program is
running.Try ATP complete refresh mode, and completed successfully.
later. ATP is offline.

Invalid ATP rule or 57 A valid ATP rule is not Assign a valid ATP Rule to the
No ATP rule assigned to the item or the item or at the organization
defined. organization. level. Run collections to collect
the new item definition and
organization setup.

Unable to meet the 52 The infinite time fence is not Define the infinite time fence in
request quantity. defined in the ATP Rule, and the ATP Rule, or ensure that
Oracle Global Order there is sufficient supply for
Promising cannot find the the item within the calendar
entire requested quantity limits.
within the Manufacturing
calendar of the organization.

Unable to find a 47 • The calendar is not • Assign the calendar to the
calendar date. assigned to that organization.
organization.
or
or
• Extend the length of time
• The order request date is on the calendar.
outside of the calendar.
or
or
• Build the calendar.
• The calendar is either not
built and/or collected.

No APS instance 140 The instance for Oracle Global Define the instance to collect
defined. Set APS Order Promising has not been the data over to the APS server.
instance and run defined in the Advanced For details, see: System Setup,
collections. Planning and Scheduling page 2-1.
server.



Wrong Check ATP 180 Member items for a product Set the Check ATP attribute to
setup for product family item have Check ATP Material for the member item
family item and set to Material, if the product that failed with that product
member item. family item has Check ATP family.
set to Material. However,
when the requested member
item has Check ATP set to
None, this error occurs.

One of the group 19 Lines in a ship or arrival set Correct the error for the line
elements or receive this error when any item that has an error message
mandatory line in the set has an error. For other than this error message.
components failed. example, in a three line ship Then the entire ship or arrival
set where one line has the set will not fail.
error Plan not Found, then the
other two lines get this error
message.

ATP has detected 220 Some ATP packages are Contact your database
invalid objects. invalid. administrator. This is typically
Contact your related to applying the correct
system admin. patch.

ATP processing 23 - Contact your system
error. administrator to investigate the
problem.

INV: Capable to 230 The profile INV: Capable to Set the profile INV: Capable to
Promise must be Promise is set differently at Promise to the same value on
same at source and the source from at the both the source and destination
destination. destination. instances.

Cannot meet 53 The scheduling fails because Excess supply is required for
request date or the demand cannot be this item.
latest acceptable satisfied for the latest
date acceptable date, but the
demand can be satisfied at a
later date.

ATP not 61 Item is not ATP-able. No action is needed, unless
applicable. item is supposed to be
ATP-able.

Troubleshooting 8-3


No Sources. 80 Sourcing is not defined for Define globally, all
that customer. Thus, Oracle organization sourcing rules
Global Order Promising and assign them to the
cannot select the shipping appropriate levels for that
organization in the ATP customer in the ATP
Assignment Set. Assignment Set. Note that Bills
of Distribution and local
sourcing rules are not
applicable.

This item is not 85 An ATP-able item has not Run collections to collect the
collected. Please been collected. item.
run Data
Collection.

No Assignment 90 Both the MRP: ATP Define at least one assignment
Set. Assignment Set at source and set. You must does this when
destination are null. you need Oracle Global Order
Promising to recommend a
shipping warehouse.

ATP Based on Planning Data Errors


Error Msg Code Message Received To Resolve this Message...
When...

Plan not found. 120 For Standard Items: For Standard Items:

• This error is generated • The plan that contains
only when the plan is the item is running or
running or has errored has errored out. Try ATP
out. after the plan run has
completed successfully.
For Multi-Level, Multi-Org
ATO Model: For Multi-Level, Multi-Org
ATO Model:
• The plan that contains
the model is not • Make the plan ATP-able
ATP-able. and run the Analyze
Plan Partitions
• The model is not concurrent program.
included in any
ATP-able plan. • Define and run the plan
to successful completion.
• The plan is running or
has errored out. • Try ATP after plan has
been run successfully.

Plan not found. 150 If standard items are not No action is needed. If you
ATP is calculated found in any ATP-able expect there should be a plan
using collected data. plan, use collected data to for the item, make sure that
find availability. plan is ATP-able and has
been run successfully.

Run ATP Post Plan 200 The ATP Post Plan Run the ATP Post Plan
Processing Processing concurrent Processing concurrent
concurrent program has not been run program. If you are not using
program. for the ATP-able plan. demand priority based
Allocated ATP or Summary
Based ATP, make sure the
related profile is set correctly.

Summary 160 The ATP Post Plan Wait until the ATP Post Plan
Concurrent Processing concurrent Processing concurrent
program is running. program is still running. program is finished running.
Try ATP later.

Troubleshooting 8-5

When...

MRP: Default 240 Only applicable for Only applicable for
Assignment Set multi-level, multi-org ATO multi-level, multi-org ATO
sourcing not in sync models: the sourcing models: ensure that the ATO
with ATP Plan. defined for the model in model has the same sourcing
the assignment set assigned and is the same in the two
to the profile MRP: Default assignment sets is used in
Assignment Set is not the profile and plan.
same as the sourcing
defined in the assignment
set used in the ATP plan.

Unable to find a 47 • The calendar is not -
calendar date. assigned to that
organization.

or

• The order request date
is outside of the
calendar.

or

• The calendar is either
not built and/or
collected.

• Assign the calendar to
the organization.

or

Extend the length of
time on the calendar.

or

Build the calendar.

No APS instance 140 The instance for Oracle Define the instance to collect
defined. Set APS Global Order Promising the data over to the APS
instance and run has not been defined in the server. For details, see:
collections. Advanced Planning and System Setup, page 2-1.
Scheduling server.


When...

Wrong Check ATP 180 Member items for a Set the Check ATP attribute
setup for product product family item have to Material for the member
family item and Check ATP set to Material, item that failed with that
member item. if the product family item product family.
has Check ATP set to
Material. However, when
the requested member item
has Check ATP set to None,
this error occurs.

One of the group 19 Lines in a ship or arrival set Correct the error for the line
elements or receive this error when any item that has an error
mandatory line in the set has an error. message other than this error
components failed. For example, in a three line message. Then the entire ship
ship set where one line has or arrival set will not fail.
the error Plan not Found,
then the other two lines get
this error message.

ATP has detected 220 Some ATP packages are Contact your database
invalid objects. invalid. administrator. This is
Contact your typically related to applying
system admin. the correct patch.

ATP processing 23 - Contact your system
error. administrator to investigate
the problem.

INV: Capable to 230 The profile INV: Capable to Set the profile INV: Capable
Promise must be Promise is set differently at to Promise to the same value
same at source and the source from at the on both the source and
destination. destination. destination instances.

Unable to meet the 53 The scheduling fails Excess supply is required for
latest acceptable because the demand cannot this item.
date. be satisfied for the latest
acceptable date, but the
demand can be satisfied at
a later date.

ATP not applicable. 61 Item is not ATP-able. No action is needed, unless
item is supposed to be
ATP-able.

Troubleshooting 8-7

When...

No Sources. 80 Sourcing is not defined for Define globally, all
that customer. Thus, Oracle organization sourcing rules
Global Order Promising and assign them to the
cannot select the shipping appropriate levels for that
organization in the ATP customer in the ATP
Assignment Set. Assignment Set. Note that
Bills of Distribution and local
sourcing rules are not
applicable.

This item is not 85 An ATP-able item has not Run collections to collect the
collected. Please run been collected. item.
Data Collection.

No Assignment Set. 90 Both the MRP: ATP Define at least one
Assignment Set at source assignment set. You must
and destination are null. does this when you need
Oracle Global Order
Promising to recommend a
shipping warehouse.

Options selected 350 Two or more options Review option specific
have exclusive needed to build a sourcing rules defined for
sources. configuration can only be your options to ensure that
sourced from different the configuration can be
organizations. manufactured in at least one
source.

No valid source for 310 There are option specific Review the sources rules for
this configuration. sourcing rules that do not the model and the option
match the sourcing rules specific sourcing rules to
for the model. ensure that there is at least
one model sourcing rule that
can build this configuration.

Failure during ATP 320 A failure occurred when -
Match process. attempting to match your
order to existing
configurations.

Note: For both ATP Based on Collected Data and Planning Data tables,
each customer has only one table to use.


Other Data Errors

Error Error Occurs When... To Resolve this Message...

Collection Process The collections process fails due to Set the following event in the
Fails. invalid state of msc_atp_plan_sn init.ora file to:
snapshot.
EVENT = 32333 trace name context
forever, level 8

ATP performance is - • Set the profile MRP: Calculate
slow. Supply Demand to No on
both the source and
destination.

• Set the profile MSC: ATP
Debug Mode to None on both
the source and destination.

• Apply the latest ATP patch.

• Run the "Purge ATP Temp
Table" concurrent program to
delete the temporary data
(supply, demand, horizontal
plan, pegging) for each ATP
transaction. This concurrent
program purges the
temporary data according to
the 'age of the data' you
specify for deletion. It ois
recommended to run this
program daily or even hourly
if your ATP transaction
volume is high.

Parameter of the concurrent
program:

Age of Entry (in hours): You
can specify the age of the data
you want to delete. For
example, if you enter '1', this
program will delete any data
that is more than 1 hour old.

Troubleshooting 8-9


Some past due sales - For ATP based on collected data,
orders, supplies, or check the ATP Rule assigned to
demands are not the item:
included in the ATP.
• From the collection
workbench. This is to verify
that the sales orders, supplies,
and demands in question are
collected over to the
destination.

• To verify that an ATP Rule
exists for the item.

• To verify the values for Past
Due Days supply and
demand attributes in the ATP
Rule. If there are any values,
ATP only considers the past
dues demand and supply for
that many days.

For example: for a 5 day Past Due
Demand, ATP only considers the
past due demand that fall under
the last 5 working days before the
sysdate. To consider all past due
demand, these field should be left
blank.

For ATP based on planned data,
check the ATP Rule assigned to
the item:

• From the collection
that the sales orders, supplies,
and demands in question are
collected over to the
destination.

• From the planners
that the sales orders are
included in the plan. If they
are not, investigate why the



sales orders are not included
in the plan.

Some supplies and When a sales order is not present Check if this supply and demand
demands are in ATP supply and demand is visible in the Collections
missing. details, and the supply is not Workbench:
present in ATP supply and
• If ATP is based on planning
demand details.
output, check if this supply
and demand is in the plan.

• If certain purchase orders or
work orders are missing,
make sure Planning Manager
is up and running if the
profile MRP: Consume MPS is
set to Yes.

• If the on-hand quantity from a
certain subinventory is
missing, check if that
subinventory is ATP-able
when ATP is based on
collected data.

If supply or demand records are
missing, run the SQL query (for
Error 11: some supplies and
demands are missing) to
determine if collection was
successful in bringing the supply
and demand from the source to
destination.

Subscript Beyond Internal error. Contact your system administrator
Count. to investigate the problem or
contact Oracle Support.

Troubleshooting 8-11


Delivery Lead Time For Lead Time set between the For Lead Time set between the
Not Calculated. customer location and the source customer location and the source
organization's location: organization's location:

• The internal location is not • Create an internal location in
created for the customer site. the Organization and
associate the Customer's Ship
• Intransit Lead times are not to location with it.
specified for the Ship method
between Orgs Ship From and • Define the Intransit Lead
the above internal location. times between the
Organization's Ship From and
For lead time set between this internal location. Also
customer ship-to site location, make sure that one of the
customer region, or customer available ship methods is
zone: selected as the default ship
method.
• The intransit lead time is not
defined between the region or For lead time set between
zone to which customer ship customer ship-to site location,
to location belongs and the customer region, or customer
source organization's location. zone:
There is no lead time at the
region or zone level where the • Define the intransit lead time
customer's ship to site falls between the region or zone to
under a specific region or which the customer ship to
zone. site belongs and the source
organization's location. Also
make sure that one of the
available ship methods is
selected as the default ship
method.

Debugging

ATP Debug File
The ATP debug file contains process information that helps facilitate ATP debugging
whenever logging a tar or bug. In a Standalone Planning Server Configuration, ATP
produces one ATP debug file. In an Integrated Planning Server Configuration, ATP
produces one ATP debug file at the source and one ATP debug file at the destination.


To Produce an ATP Debug File for a Standalone Planning Server Configuration:
1. Set the profile MSC: ATP Debug Mode to Debug Only at the user level of the source
instance.

2. Run the following query to find the location where the ATP debug file is created:
select ltrim(rtrim(value))
from
(select value from v$parameter2
where name='utl_file_dir'
order by rownum desc)
where rownum <2;
Ensure that there no * values at the end of utl_file_dir value returned by the query.
Also ensure that this directory is writable.

3. Run the ATP Inquiry for the item.

4. When the test case is complete, pick latest session file from the location determined
in the first step.

5. Upload the debug.

• Complete steps 1 to 4 on both the source and destination
instance.

• Set profile MSC: ATP Debug Mode back to None at the
appropriate site level after generating the debug file. If the
profile option is not set back to None, then the ATP
performance degrades.

To Produce an ATP Debug File for an Integrated Planning Server Configuration:
1. At the instance where the query is performed, set the profile MSC: ATP Debug
Mode to Debug Only at the user level.

2. Run the following query to find the location where the ATP debug file is created:
select ltrim(rtrim(value))
from
(select value from v$parameter2
where name='utl_file_dir'


order by rownum desc)
where rownum <2;
Ensure that there are no * values at the end of utl_file_dir value returned by the
query. Also, ensure that this directory is writable.

3. Run the ATP Inquiry for the item.

4. Pick the latest session file from the location determined in the first step, when the
test case is complete.

Debugging Areas
The following are areas that people commonly debug to ensure that the basic setup and
ATP calculations are correct.
Oracle Global Order Promising Architecture
• The source view, mrp_ap_apps_instances, must contain one row. Verify that the
Enable ATP checkbox is enabled for a correct instance in the instance setup UI. The
instance_id column must contain the instance id assigned to this source instance on
the APS instance.

• The destination table, msc_apps_instances, may contain as many rows as the
collected source instances.

• The complete / target collections must be completed at least once before using ATP.

• For ATP based on collected data to work correctly, the collections process must be
completed successfully. A value of zero or null in the st_status column of the
msc_apps_instance table for the source instance indicates that collections for this
source has been run successfully, and ATP can be performed against this instance.
If this column contains any other value, then collections is running or collections
has errored out.
For details for ATP based on collected data, see Data Collection, page 2-9.

• For ATP based on planning data to work correctly, collections and the plan run
must be completed successfully. Plan_completion_date and data_completion_date
columns in msc_plans table for the plan are populated if the plan has completed
successfully. If any of these columns contains a null value, then the plan has errored
out. The plan must be relaunched and completed successfully before performing
the ATP check against this plan.

Oracle Global Order Promising Database Links
• Run the following query to verify the database link at the source:
Select substr(a2m_dblink, 1, 35), substr(m2a_dblink, 1, 35) from


mrp_ap_apps_instances;
a2m_dblink must contain the database link that points from the source to the
destination.
m2a_dblink must contain the database link that points from the destination to the
source.

• Run the following query to verify the database link at the destination:
Select substr(a2m_dblink, 1, 35), substr(m2a_dblink, 1, 35) from msc_apps_instances
where instance_code = l_instance_code;
where l_instance_id = instance_id of the source instance;
a2m_dblink must contain the database link that points from the source to the
destination.
m2a_dblink must contain the database link that points from the destination to the
source.

SQL Queries
Note: Your organization's database administrator should be the person
designated to run these SQL Scripts.

A basic understanding of the architecture of Oracle Global Order Promising is helpful.
The following are some notes:
• Data Collection is responsible for gathering all the relevant data in the Source
Instance from the INV, BOM, PO, OE, MRP, and WIP schemas, and duplicating the
data in the MSC schema for ATP and Oracle Advanced Supply Chain Planning
purposes.

• Since you can collect data from more than one instance, MSC has it's own item
numbering system that is seen in MSC_SYSTEM_ITEMS. This means that each item
is assigned a new INVENTORY_ITEM_ID in MSC_SYSTEM_ITEMS when it is
collected. The Source Inventory Item ID is stored under
SR_INVENTORY_ITEM_ID.

• SR_% is used in many common column names to denote a value on the Source
Instance.

• Many tables contain the first column PLAN_ID.
• The PLAN_ID "-1" is reserved for the Collected Data.

• Positive PLAN_ID numbers are for the ASCP planning data generated when a


plan is executed in Oracle Advanced Supply Chain Planning.

• Some collected data is used regardless of ATP type being executed, and do not
need a PLAN_ID. Sourcing rules is an example.

• MSC_PLANS and MSC_PLAN_PARTITIONS contain the setup data for your plans.
For example, Collections is PLAN_ID = -1 in MSC_PLANS.

• If you collect data from more than one instance, then the SR_INSTANCE_ID
column in the MSC_% tables becomes very important since the data from the two
different instances can be exactly the same with the exception of this value.

• The ORGANIZATION_ID does not change in the MSC tables. It is differentiated by
the SR_INTANCE_ID when collecting from more than one instance.

Basic Queries
The basic queries below retrieve item and plan information to start diagnosis of an item
problem:
From the Source instance, the following gives you:
• The organization_id for your organization_code

• The inventory_item_id which is the sr_inventory_item_id is MSC_SYSTEM_ITEMS
Select
i.concatenated_segments,
i.inventory_item_id,
i.organization_id
from
mtl_system_items_kfv i,
mtl_parameters p
where
i.concatenated_segments like '&Item_name'
and i.organization_id = p.organization_id
and p.organization_code = '&Organization_code'
and i.organization_id = p.organization_id;
Use
&Organization_Code = Enter your Org Code when prompted
&Item_name = Enter your Item Name when prompted


The following query gives you:
• The instance_id of your source instance

• The instance_code of your source instance
Select
instance_id, instance_code
from
mrp_ap_apps_instances;

From the destination, the two following queries should produce results to allow for
most the various variables:
• Select
substr(item_name,1.30) Item_name,
sr_inventory_item_id,
inventory_item_id,
organization_id
from
msc_system_items
where
sr_inventory_item_id = &Source_Inventory_item_id
and organization_id = &Organization_id
and sr_instance_id = &Instance_ID
and plan_id = -1;
USE
&Source_Inventory_item_id = from first query on the source
&Organization_id = organization_id from the first quest on the source
&Instance_ID = from the second query of on the source

Data Error SQL Queries
These SQL queries address the ATP Based on Collected Data Errors, page 8-1 and the
Other Data Errors, page 8-9 from the Troubleshooting section.

Error 47: Unable to find a calendar date.
Two possible issues:


• The calendar is not assigned to the organization.
Select
calendar_code,
calendar_exception_set_id
from
msc_trading_partners
where
sr_instance_id = &Instance_id
and sr_tp_id = &Organization_id
and partner_type = 3;
Use
&Instance_id = instance id of the source instance
&Organization_id = organization id of the item
If the above two columns are not populated, then a calendar has not been assigned
to the organization. Assign a calendar to the organization and run Data Collections
with a Complete Refresh.

• The request date is outside the date range of the calendar assigned to the
organization.
Select
Min(calendar_date),
Max(calendar_date)
from
msc_calendar_dates
where
sr_instance_id = &Instance_id
and calendar_code = '&Calendar_code'
and exception_set_id = &Calendar_exception_set_id;
Use
&Calendar_code = calendar code from query in section a
&Calendar_exception_set_id = calendar exception set id from query in section a


Error 57: Invalid ATP Rule or No ATP Rule defined.
Select
nvl(msi.atp_rule_id, tp.default_atp_rule_id) atp_rule_id
from
msc_system_items msi,
msc_trading_partners tp
where
msi.sr_inventory_item_id = &Source_Inventory_item_id
and msi.sr_instance_id = &Instance_id
and msi.organization_id = &Organization_id
and plan_id = -1
and tp.sr_instance_id = msi.sr_instance_id
and tp.sr_tp_id = msi.organization_id
and tp.partner_type = 3;
Use
&Source_Inventory_item_id = source inventory item id
&Organization_id = organization id of the sourcing organization

Error Code 85: This item is not collected. Please run Data Collection.
Select
item_name,
atp_flag,
atp_components_flag
from
msc_system_items
where
and sr_instance_id = &Instance_id
and plan_id = -1;
• Use



Note: If the above query does not return a row for the organization
that you are expecting, then the item has not been collected. Check
the item's setup on the source instance. Run Data Collections with a
Complete Refresh or Target Refresh. Then check for the item again.

Error 120: Plan not found.
Execute the following query:
• Select
distinct(plan_id) Plan_id
from
msc_atp_plan_sn;

Then:
• Select
plan_id,
from
msc_atp_plan_sn
where
and organization-id = &Organization_id;
Use

Note: If the above query does not return any data, then:

• The Plan has not been made ATP-able. Check that the Inventory
ATP Flag is the plan options is checked.

• The Plan has not run successfully. Then:


Select
plan_completion_date,
data_completion_date,
plan_id
from
msc_plans
where
compile_designator = '&Plan_name';
Use
&Plan_name.
The name of the plan.
If plan is run successfully, then above two date columns should be
populated.

• The Plan does not contain the item. Then:
Select
item_name
from
msc_system_items
where
plan_id = &Plan_id
and sr_inventory_item_id = &Source_Inventory_item_id
and organization-id = &Organization_id;
Use
&Plan_id = The Plan_id from above

Error 140: No APS instance defined. Set APS instance and run collections.
Run the following queries on the source instance:


• Select
a2m_dblink from mrp_ap_apps_instances;

Note: The above query should return the name of only one valid
database link.

Error 220: ATP has detected invalid objects. Contact your system admin.
The following query provides some of the possible invalid objects in the database:
• Select
owner,
object_name,
object_type,
status
from
all_objects
where
status = 'INVALID'
and object_name like 'MSC%'
and object_type != 'UNDEFINED';

Then:
• Select
owner,
object_name,
object_type,
status
from
all_objects
where
status = 'INVALID'
and object_name like 'MRP%'
and object_type != 'UNDEFINED';


Note: If any objects are owned by APPS_MRC, ignore them.
Recompile the rest of invalid objects returned, and report the errors
for each object that cannot be recompiled.

Error 230: INV: Capable To Promise must be same at source and destination.
Run the following queries on both source and destination:
• Select
FND_PROFILE.value('INV_CTP') from dual;

Note: This profile must be the same in both instances and should
only be set at the site level.

Other Data Error: Some past due sales orders, supplies, or demands are not included in the ATP.
Select
rule_name,
past_due_demand_cutoff_fence,
past_due_supply_cutoff_fence,
include_sales_orders,
include_purchase_orders,
include_discrete_wip_receipts,
include_nonstd_wip_receipts,
include_discrete_mps,
include_rep_mps,
include_rep_wip_receipts
from
msc_atp_rules
where
rule_id = &ATP_Rule_id
and sr_instance_id = &Instance_id;
Use
&ATP_Rule_id = rule id determined using query in the section above


Note: For any supply and demand types that have values returned as 1,
ATP only considers the past due demand and supply for that many
days.
For example: for Past Due Demand Days of 5 days, ATP only considers
past due demands that fall under the sysdate of 5 days. To consider all
past due demands, these fields should be left blank.


A
Profile Options

This appendix covers the following topics:
• Oracle Global Order Promising Profile Options

Oracle Global Order Promising Profile Options
There are several types of profile options used by Oracle Global Order Promising. These
types include:
• MRP Profile Options

• MSC Profile Options

• INV Profile Options

• BOM Profile Options

The following sections contain tables that list the profile option names, values, and
descriptions.

MRP Profile Options
The following table lists and defines the MRP profile options used by Oracle Global
Order Promising:

Profile Options A-1

Profile Option Valid Default Description
Name Values Value

MRP: ATP Text Null Indicates the assignment set name for use with
Assignment Set Oracle Global Order Promising.When set to
Null, Oracle Global Order Promising uses the
assignment set from profile MSC: ATP
Assignment Set from Oracle Advanced
Planning Solution instance.Update this profile
at site level on the source instance.

MRP: ATP Text Null Determines whether distributed Oracle Global
Database Link Order Promising is used. Set this profile at the
source instance. The value should equal the
value you entered in the 'From Source to APS'
of the source instance you defined in the
Instance form.This is a site level profile.

MRP: Calculate • Yes Yes When set to Yes, this profile controls whether
Supply Demand detailed supply / demand data is retrieved and
• No retained for viewing during an ATP
Inquiry.This is viewed by selecting ATP Details
in the Inquiry form.There are performance
implications when profile is set to Yes. It can be
set to Yes, then an ATP Inquiry can be run to
see the details. Then set it back to No for better
performance.

Set this profile to Yes only when you need to
view the detailed supply demand and
horizontal plan information for an ATP
inquiry.

You can set the profile at user level.

MRP: Include • Yes No Indicates whether to include substitute
Substitute components in the Oracle Global Order
Components • No Promising calculation. Users can update at the
site level. It is only applicable when ATP is
based on Oracle Advanced Supply Chain
Planning output.

A-2 Oracle Global Order Promising Implementation and User's Guide

Name Values Value

MRP: Set Text (varies) Use this profile option to indicate which items
Category for belonging to this category set are displayed in
Backlog Form the Backlog Scheduling Workbench tree
navigator. If no value is entered, no items are
displayed in the Backlog Scheduling
Workbench tree navigator.You can update this
profile at the site level.

MSC Profile Options
The following table lists and defines the MSC profile options used by Oracle Global
Order Promising:

Profile Valid Values Default Description
Option Name Value

MSC: Action • Yes No Determines whether manual updates are
Allowed on allowed to the original plan when the plan
ATP 24x7 • No copy is running.
Plan While
Running Values are:

• Yes - The ATP plan appears in the
Workbench window while it is running.
You can make changes to the plan.
However, the changes will not appear in
the refreshed plan.

• No - The ATP plan appears only in the
View Plan window.

Profile Options A-3

Option Name Value

MSC: • Reduce Null Determines the type of forward consumption
Allocated future that Oracle Global Order Promising can
ATP Forward supply from perform to accommodate the shortage faced
Consumption lowest by a demand class.
priority
Values are:
• Reduce • Reduce future supply from lowest
available priority: Use the available supply from
supply from the lowest priority demand to account for
any priority the shortage of a demand class. If every
demand class is at same priority, reduce
the future supply to cover the shortage
for a demand class.

• Reduce available supply from any
priority: A promised demand is the most
important demand that you need to meet.
Oracle Global Order Promising starts the
adjustments from the higher priority
demand class. This means Oracle Global
Order Promising reduces the availability
of a lower priority demand class before a
higher priority demand class to account
for shortages from prior period. This
reduces the available supply to account
for the shortage from lower priority
demand classes.

MSC: ATP Any number Null Determines the approximate ATP downtime
24x7 between 0-999 (in minutes) to cover the time required to
Synchronizati synchronize as well as to switch over to the
on Downtime refreshed plan during the plan
synchronization process. Oracle Global Order
Promising internally translates this value into
the number of orders to process.

Oracle recommends that you set the value for
this profile depending on the sales order
volume during the ATP 24x7 plan run.

This profile option also determines the
duration of the extended synchronization
process. This process is executed for the
duration of the ATP downtime or 10 minutes,
whichever is larger.


Option Name Value

MSC: ATP • User-Define Null Determines the allocation method used by
Allocation d Allocation ATP. This is a site level profile. Valid values
Method Percentage are:

• User-Defined Allocation Percentage
• Demand
Priority
• Demand Priority

MSC: ATP Text Null Indicates name of the assignment set for
Assignment Oracle Global Order Promising to use to
Set identify all the possible shipping
organizations. Oracle Global Order Promising
uses this assignment set if the profile MRP:
ATP Assignment Set is Null on the ERP
instance. Users can update it at the site level in
the Planning instance.

MSC: ATP • Yes No Set it to No. You should only set it to Yes
Capacity under specific instruction from Oracle
Allocation • No Applications development.

MSC: ATP • Debug Only Null Determines whether to enable debug
Debug Mode messages within Oracle Global Order
• Debug and Promising. You can update it at the user level.
Database Valid values are:
Trace • Debug Only: ATP generates a log file for
an ATP request.
• Database
Trace Only • Debug and Database Trace: ATP
generates a log file and a database trace
• None file.

• Database Trace Only: ATP generates a
database trace file.

• None: ATP does not generate log file or
database trace file.

Profile Options A-5

Option Name Value

MSC: ATP • Yes Yes Indicates whether ATP enforces lead time for
Enforces Lead ATO models or not.
Time for ATO • No • Yes - Enforces lead time for ATO models.
Models

• No - Does not enforce lead time for ATO
models.

MSC: Class • Demand Demand Indicates which allocation hierarchy to use.
Hierarchy Class Users can update it at the site level. Valid
values are:
• Customer • Demand Class: User-defined, single-level
Class
hierarchy.

• Customer Class: Has three levels:
customer class, customer, and site.

MSC: Integer >= 0 Null Used when collections for the trading partners
Collection entity is run in complete mode.
Window for
Trading Specifies the number of days backwards for
Partner collecting changes in customer names,
Changes customer sites, vendors, and vendor sites. A
(Days) Null value means all changes are collected.

MSC: Display • Yes No Determines whether the rescheduling supplies
Order are displayed in the Planner Workbench or
Rescheduling • No not.
Supplies
Values are:

• Yes - displays the rescheduling supplies
details in the Planner Workbench.

• No - the rescheduling supplies details are
hidden from the Planner Workbench

This profile is provided for debugging and
analysis only.Therefore, it is recommended
that you set this profile to No in a production
environment.


Option Name Value

MSC: Enable • Yes No Use this profile options to indicate whether
Allocated allocated order promising is used. Users can
ATP • No update this profile at the site level.

MSC: Enable • Yes No Enables the summarization of supply /
ATP demand data for performance improvement.
Summary • No This is a site level profile. Valid values are:
Mode
• Yes: Enable ATP Summary Mode.

• No: Disable ATP Summary Mode.

MSC: Enable • Yes No Controls the generation of workflow
ATP notifications to send to the planner. This is a
Workflow • No site level profile. Valid values are:

• Yes: Generate ATP Workflow
Notifications.

• No: Do not generate ATP Workflow
Notifications.

MSC: Excess • Yes No Controls the allocation of supply or demand
and Safety that pegs to excess or safety stock in the case
Stock by • No of allocated ATP using the demand-priority
Demand based method.
Class
The valid values are:

• Yes: If such supply or demand has a
demand class, and if the demand class
exists on the allocation rule, allocate the
supply or demand to the demand class.
However, if the supply or demand does
not have a demand class or if the demand
class does not exist on the allocation rule,
allocate the supply or demand to OTHER.

• No: Allocate such supply or demand to
OTHER.

Profile Options A-7

Option Name Value

MSC: • Plan Demand Determines which date is used for bucketing
Horizontal Recommend Due Date demands.
Plan Demand ed Date
Bucketing Values are:
Preference • Demand • Plan Recommended Date - the demands
Due Date are bucketed based on the dates
recommended by the planning engine

• Demand Due Date - the demands are
bucketed based on the schedule ship date
on the sales order

MSC: Sales Integer >= 0 Null Collects completed sales orders within the
Orders Offset offset duration. For example, if Sales Orders
Days Offset Days is set to 90, all the sales orders
completed in the past 90 days are collected.
Can be defined at the site level. A Null value
means all closed sales orders are collected.

MSC: Integer >= 0 Null Offsets the starting date of sourcing history
Sourcing calculations and is used in conjunction with
History Start the following collections parameters:
Date Offset
• Purge Sourcing History = Yes
(in months)

• Recalculate Sourcing History = Yes

These settings delete, then calculate Sourcing
History from the Start date determined by the
profile option value (in months). System
performance might degrade when you set a
high value for this profile option and there is a
high volume of source transaction data.


Option Name Value

MSC: Use • Yes Yes Determines whether
Shipping/Rec shipping/receiving/carrier calendars are being
eiving • No used for order promising.
Calendars
Values are:

• Yes - Uses the shipping, receiving, and
carrier calendars to schedule ship and
arrival dates.

• No - Uses only the organization's
manufacturing calendar to schedule ship
dates at each level.

INV Profile Options
The following table lists and defines the INV profile options used by Oracle Global
Order Promising:

Profile Option Valid Values Default Value Description
Name

INV: Capable to • ATP/CTP ATP Based on This is a site level profile. Valid values
Promise Based on Collected Data are:
Planning
• ATP/CTP Based on Planning
Output
Output: set the profile to this value
• if you want to use the Oracle
ATP Based
Advanced Supply Chain Planning
on
output for order promising.
Collected
Data
• ATP Based on Collected Data: set
the profile to this value if you
want to use collected data for
order promising.

Profile Options A-9

Profile Option Valid Values Default Value Description
Name

INV: External • Global - Only applicable for Oracle Global
ATP ATP Order Promising for non-Oracle
Server Applications on Release 11i source.
Only to be set up only on source
• None instance. Do not set this up for an
Oracle Applications Release 11i
instance. Set this profile to Global ATP
Server if Oracle Global Order
Promising is deployed. This is a site
level profile.

BOM Profile Options
The following table lists and defines the BOM profile option used by Oracle Global
Order Promising:

Name Values Value

BOM: Match To • Yes No Determines whether Oracle Global Order
Existing Promising matches a sales order to an existing
Configuration • No configuration or not.

Values are:

• Yes - attempts to match a sales order to an
existing configuration

• No - schedules a sales order without a
match to existing configuration check


B
Application Program Interface

• Available-To-Promise Application Program Interface

Available-To-Promise Application Program Interface

Description
The Available to Promise (ATP) API is a public API which could be used to calculate
the material and resource availability across the supply chain. The API accepts
information about an item or group of items, checks availability for the item(s) and
returns the availability picture for the items. Shown below is the specification of ATP
API:
The specification of the ATP API are below:
PROCEDURE Call_ATP (

p_session_id IN OUT NUMBER,

p_atp_rec IN MRP_ATP_PUB.ATP_Rec_Typ,

xx_atp_rec OUT NOCOPY MRP_ATP_PUB.ATP_Rec_Typ,

x_atp_supply_demand OUT NOCOPY MRP_ATP_PUB.ATP_Supply_Demand_
Typ,

x_atp_period OUT NOCOPY MRP_ATP_PUB.ATP_Period_Typ,

x_atp_details OUT NOCOPY MRP_ATP_PUB.ATP_Details_Typ,

Application Program Interface B-1

x_return_status OUT VARCHAR2,

x_msg_data OUT VARCHAR2,

x_msg_count OUT NUMBER

);
Where:
1. p_session_id: This is the session identifier of the user transaction. The session id is
passed to ATP API from the calling module.

2. p_atp_rec: This record of tables contains information about items for which
resource and material availability check needs to be done. This record is explained
in detail later in the document.

3. x_atp_rec: This record of table contains resource and material availability
information generated by ATP for items passed to ATP API in p_atp_rec. This
record is explained in detail later in the document.

4. x_atp_supply_demand: This record of tables contains information about supplies
and demands ATP considered to check the availability. This record is explained in
detail later in the document.

5. x_atp_period: This record of tables contains net supply and demand picture for the
items for the whole time horizon during which availability is checked. This record
is explained in detail later in the document.

6. x_atp_details: This record of tables is not used by ATP at present.

7. x_return_status: This variable contains the overall status of ATP check. There are
three possible value for this variable:
1. FND_API.G_RET_STS_SUCCESS: The return value is 'S'. It means ATP request
was successful.

2. FND_API.G_RET_STS_ERROR: The return value is 'E'. It means that some error
occurred during ATP check.

3. FND_API.G_RET_STS_UNEXP_ERROR; The return value is 'U'. It means that
an unexpected error occurred during ATP check.

8. x_msg_data: This variable is not used by ATP at present

9. x_msg_count: This variable is not used by ATP at present.

B-2 Oracle Global Order Promising Implementation and User's Guide

Nested Tables
The following nested tables are used for defining data types of members in a record:

Col. 1 Col. 2 Col. 3 Col. 4 Col. 5 Col. 6

TYPE number_arr IS TABLE of number

TYPE char1_arr IS TABLE of varchar2(1)

TYPE char3_arr IS TABLE of varchar2(3);








TYPE char2000_arr IS TABLE of varchar2(2000
);

TYPE date_arr IS TABLE of date;

Description of MRP_ATP_PUB.ATP_Rec_Typ
The specification of the ATP_REC_Typ is shown below:
TYPE ATP_Rec_Typ is RECORD (

Col. 1 Col. 2

Row_Id char30_arr,


Col. 1 Col. 2

Instance_Id number_arr,

Inventory_Item_Id number_arr,

Inventory_Item_Name char40_arr,

Source_Organization_Id number_arr,

Source_Organization_Code char7_arr,

Organization_Id number_arr,

Identifier number_arr,

Demand_Source_Header_Id number_arr,

Demand_Source_Delivery char30_arr,

Demand_Source_Type number_arr,

Scenario_Id number_arr,

Calling_Module number_arr,

Customer_Id number_arr,

Customer_Site_Id number_arr,

Destination_Time_Zone char30_arr,

Quantity_Ordered number_arr,

Quantity_UOM char3_arr,

Requested_Ship_Date date_arr,

Requested_Arrival_Date date_arr,

Earliest_Acceptable_Date date_arr,


Col. 1 Col. 2

Latest_Acceptable_Date date_arr,

Delivery_Lead_Time number_arr,

Freight_Carrier char30_arr,

Ship_Method char30_arr,

Demand_Class char30_arr,

Ship_Set_Name char30_arr,

Arrival_Set_Name char30_arr,

Override_Flag char1_arr,

Action number_arr,

Ship_Date date_arr,

Arrival_Date date_arr,

Available_Quantity number_arr,

Requested_Date_Quantity number_arr,

Group_Ship_Date date_arr,

Group_Arrival_Date date_arr,

Vendor_Id number_arr,

Vendor_Name char80_arr,

Vendor_Site_Id number_arr,

Vendor_Site_Name char80_arr,

Insert_Flag number_arr,


Col. 1 Col. 2

OE_Flag char1_arr,

Atp_Lead_Time number_arr,

Error_Code number_arr,

Message char2000_arr,

End_Pegging_Id number_arr,

Order_Number number_arr,

Old_Source_Organization_Id number_arr,

Old_Demand_Class char30_arr

Ato_delete_flag char1_arr,

Attribute_01 number_arr,




Attribute_05 char30_arr,




Attribute_09 date_arr,


Customer_name char80_arr,


Col. 1 Col. 2

Customer_class char30_arr,

Customer_location char40_arr,

Customer_country char60_arr,

Customer_state char60_arr,

Customer_city char60_arr,

Customer_postal_code char60_arr,

Substitution_typ_code number_arr,

Req_item_detail_flag number_arr,

Request_item_id number_arr,

Req_item_req_date_qty number_arr,

Req_item_available_date date_arr,

Req_item_available_date_qty number_arr,

Request_item_name char40_arr,

Old_inventory_item_id number_arr,

Sales_rep char255_arr,

Customer_contact char255_arr,

Subst_flag number_arr,

Top_Model_line_id number_arr,

ATO_Parent_Model_Line_Id number_arr,

ATO_Model_Line_Id number_arr,


Col. 1 Col. 2

Parent_line_id number_arr,

Match_item_id number_arr,

Config_item_line_id number_arr,

Validation_Org number_arr,

Component_Sequence_ID number_arr,

Component_Code char255_arr,

Line_number char80_arr,

Included_item_flag number_arr,

Atp_flag char1_arr,

Atp_components_flag char1_arr,

Wip_supply_type number_arr,

Bom_item_type number_arr,

Mandatory_item_flag number_arr,

Pick_components_flag char1_arr,

Base_model_id number_arr,

Oss_error_code number_arr,

Matched_item_name char255_arr,

Cascade_model_info_to_comp number_arr,

Sequence_number number_arr,

Firm_flag number_arr,


Col. 1 Col. 2

Order_line_number number_arr,

Option_number number_arr,

Shipment_number number_arr,

Item_desc char255_arr,

Old_line_schedule_date date_arr,

Old_source_organization_code char7_arr,

Firm_source_org_id number_arr,

Firm_source_org_code char7_arr,

Firm_ship_date date_arr,

Firm_arrival_date date_arr,

Ship_method_text char255_arr,

Ship_set_id number_arr,

Arrival_set_id number_arr,

Project_id number_arr,

Task_id number_arr,

Project_number char30_arr,

Task_Number char30_arr,





Col. 1 Col. 2


















Atf_date date_arr,

Plan_id number_arr,

Original_request_date date_arr,


Col. 1 Col. 2

Receiving_cal_code char14_arr,

Intransit_cal_code char14_arr,

Shipping_cal_code char14_arr,

Manufacturing_cal_code char14_arr,

Internal_org_id number_arr,

First_valid_ship_arrival_date date_arr

);
1. Row_Id: The row_id in database for an order. This field is used only in 10.7 and 11.0
versions of application. This field is optional for later versions.

2. Instance_Id: Instance identifiers of the requesting module. This is mandatory if
calling_module is 724. For other calling modules, instance_id is obtained from
MRP_AP_APPS_INSTANCES.

3. Inventory_Item_Id: Inventory Item ID for which the ATP check needs to be done.
This field is mandatory.

4. Inventory_Item_Name: Name of the items. If not provided, then ATP may populate
this field.

5. Source_Organization_Id: Shipping Organization ID. If not provided, ATP calculates
the shipping organization ID using sourcing rules based on provided
customer_site_id/organization_id.

6. Source_Organization_Code: Shipping Organization Code. ATP populates this field
based on Source_Organization_Id.

7. Organization_Id: Receiving organization ID. Either organization_id or customer_id
must be provided but both should not be provided.

8. Identifier: Order line ID. This field is mandatory for scheduling, unscheduling, and
rescheduling.

9. Demand_Source_Header_Id: Header ID for Order. This field is not mandatory.

10. Demand_Source_Delivery: This field is used along with demand_source_header_id


and demand_source_type to uniquely identify an order in Order Management. This
field is not mandatory.

11. Demand_Source_Type: This field is used along with demand_source_header_id
and demand_source_delivery to uniquely identify an order in Order Management.
This field is not mandatory.

12. Scenario_Id: This field is for ATP internal use.

13. Calling_Module: Module that called ATP.

1. 724 indicates planning server

2. 660 indicates OM

3. 708 indicates configurator

4. -1 indicates backlog scheduling workbench

14. Customer_Id: ID of the customer for whom ATP check needs to be done. Either
organization_id or customer_id must be provided but both should not be provided.

15. Customer_Site_Id: Ship to Site ID of the receiving Customer Site. If this field is not
provided then ATP cannot do global sourcing and ship method/delivery lead time
calculation.

16. Destination_Time_Zone: Time zone of the requesting organization. ATP does not
support this field at present.

17. Quantity_Ordered: Quantity ordered for the items expressed in Quantity_UOM.
This field is mandatory. For unscheduling, this field must be 0.

18. Quantity_UOM: Unit of measurement of items ordered. This field is mandatory.

19. Requested_Ship_Date: Requested ship date for the items. Either
requested_ship_date or requested_arrival_date must be provided but both should
not be provided.

20. Requested_Arrival_Date: Requested arrival date for the items. Either
requested_ship_date or requested_arrival_date must be provided but both should
not be provided.

21. Earliest_Acceptable_Date: Earliest acceptable date by which the requester is ready
to accept the order in case ATP check fails on requested ship or arrival date. This
feature is not used by ATP at present.

22. Latest_Acceptable_Date: Latest acceptable date by which the requester is ready to
accept the order in case ATP check fails on requested ship or arrival date.


23. Delivery_Lead_Time: Delivery lead time between shipping and receiving
organization. If not provided, then ATP calculates it based on ship method
provided to ATP or else default ship method setup between ship-from Org and
ship-to site. Customer_Site_ID must be provided for ATP to make this calculation.

24. Freight_Carrier: Freight Carrier used for the shipment. This feature is not used by
ATP at present.

25. Ship_Method: Ship method to be used for shipping. If delivery_lead_time is
provided then this is not required. Otherwise, ATP tries to calculate
delivery_lead_time based on provided ship method. If the ship_method provided is
not a valid one between the source organization and receiving
organization/customer, then ATP uses the default shipping method. If the default
shipping method is set between the source organization and receiving
organization/customer, then ATP will assign the default ship method to this field
else this field will be left empty. Customer_Site_ID must be provided for ATP to
make this calculation.

26. Demand_Class: Demand class under which customer or requesting organization
falls. This field is not mandatory.

27. Ship_Set_Name: Name of the ship-set. For line items, this field remains empty.
Either Ship_set_name or Arrival_Set_Name should be passed, and not both.

28. Arrival_Set_Name: Name of the arrival-set. For line items, this field remains empty.
Either Ship_set_name or Arrival_Set_Name should be passed, and not both.

29. Override_Flag: Indicates ATP to honor the requested date irrespective of
availability of the requested items. Possible values:
• Y

• N

30. Action: Type of Inquiry. Possible Values:

• 100 - ATP Inquiry

• 110 - Scheduling

• 120 - Rescheduling

31. Ship_Date: Date on which requested item will be shipped. This field is populated
by ATP.

32. Arrival_Date: Date on which requested item will arrive. This field is populated by
ATP.


33. Available_Quantity: Quantity available on ship date. This field is populated by
ATP.

34. Requested_Date_Quantity: Quantity available on requested ship/arrival date. This
field is populated by ATP.

35. Group_Ship_Date: Ship date for whole ship set. This field is populated by ATP in
case of ship set.

36. Group_Arrival_Date: Arrival date for arrival set. This field is populated by ATP in
case of arrival set.

37. Vendor_Id: Vendor ID from where item needs to be requested. This field is not used
by ATP.

38. Vendor_Name: Vendor Name. This field is not used by ATP.

39. Vendor_Site_Id: ID of vendor site from where item needs to be requested. This field
is not used by ATP.

40. Vendor_Site_Name: Vendor site name. This field is not used by ATP.

41. Insert_Flag: Flag to indicate if supply/demand and period details are calculated or
not. Usually, this should be left NULL or, set to zero due to performance reasons,
unless the user needs to see supply demand details.

42. OE_Flag: Indicates if it is an internal sales order or not. Possible values:

• Y

• N

43. Atp_Lead_Time: ATP Lead Time for Configure-to-Order Models/ Option Classes/
Option Items etc. This field is obsolete in 11.5.10.

44. Error_Code: Error code of the error occurred during ATP check. Check
MTL_DEMAND_INTERFACE _ERRORS lookup for a complete list of error codes
and corresponding error messages.

45. Message: Error message for the error occurred during ATP check. This field is not
used by ATP.

46. End_Pegging_Id: Pegging ID for the ultimate parent. This field is populated by
ATP.

47. Order_Number: Order number in Order management.

48. Old_Source_Organization_Id: This field is used for rescheduling and indicates ID of


Organization where item was scheduled initially.

49. Old_Demand_Class: Used for rescheduling and indicates the demand class under
which item was scheduled initially.

50. Ato_delete_flag: Indicates if the item requested for Unscheduling is part of an ATO
Model. Possible values are Y or N. This field is obsolete in 11.5.10.

51. Attribute_01: Used for passing source document line id for internal sales orders.

52. Attribute_02: Used for diagnostic ATP.

• 1 for on

• 2 for off

53. Attribute_03: Reserved for future ATP functionalities.

54. Attribute_04: ATP uses this flag internally to pass refresh number in 24x7
processing.

55. Attribute_05: ATP uses this flag internally to pass visible demand flag for ATO
items.

56. Attribute_06: ATP uses this flag internally to pass ATP_FLAG for an item from
source to destination.

57. Attribute_07: ATP uses this flag internally to pass back the name of the plan used
by ATP for inquiry.




61. Customer_name: Name of ship-to customer entered on the sales order pad.
Currently, this field is not used by ATP.

62. Customer_class: Reserved for future ATP functionalities.

63. Customer_location: Customer location of ship-to customer entered on the sales
order pad. Currently, this field is not used by ATP.

64. Customer_country: Country of ship-to customer entered on the sales order pad.
Currently, this field is not used by ATP.

65. Customer_state: State of ship-to customer entered on the sales order pad. Currently,


this field is not used by ATP.

66. Customer_city: City of ship-to customer entered on the sales order pad. Currently,
this field is not used by ATP.

67. Customer_postal_code: Postal code of ship-to customer entered on the sales order
pad. Currently, this field is not used by ATP.

68. Substitution_typ_code: Type of substitution that should be performed on the line.
Possible values:
• 1 - All or Nothing

• 2 - Mixed

• 3 - Refer to item attribute

• 4 - No Substitution

69. Req_item_detail_flag: Indicates whether ATP details of original items should be
provided or not in case a substitute is used to satisfy the demand.
• 1 - Provide requested item's details

• 2 - Do not provide requested item's details.

70. Request_item_id: Source inventory item id of the requested item in case substitute
is used to satisfy the demand.

71. Req_item_req_date_qty: Request date quantity for requested item. This field is
populated by ATP only if the Req_item_detail_flag field is set to 1 and susbtitution
occurs.

72. Req_item_available_date: Date on which requested item is available. This field is
populated by ATP only if the Req_item_detail_flag field is set to 1 and substitution
occurs.

73. Req_item_available_date_qty: Quantity of requested item on ATP date. This field is
populated by ATP only if the Req_item_detail_flag field is set to 1. This field is
populated only if substitution occurs.

74. Request_item_name: Name of the requested item. This field is populated only if
substitution occurs.

75. Old_inventory_item_id: Source inventory item ID for the item used during last
scheduling session for the line.

76. Sales_rep: Name of the sales representatives listed on the order line. If this is not


provided, then workflow notification is not sent in case of substitution.

77. Customer_contact: Name of the customer contact listed on the order line. If this is
not provided, then workflow notification is not sent in case of substitution.

78. Subst_flag: Contains 1 if substitution occurs for the line.

79. Top_Model_line_id: Line ID of the top model for an ATO/PTO configuration.

80. ATO_Parent_Model_Line_Id: Line ID of parent ATO configuration.

81. ATO_Model_Line_Id: Line ID of the top ATO model configuration.

82. Parent_line_id: Line ID of the parent item in case of ATO/PTO models.

83. Match_item_id: Source inventory item ID for the matched configuration.

84. Config_item_line_id: Line ID of the configuration item linked to a sales order.

85. Validation_Org: Validation organization ID for the calling instance.

86. Component_Sequence_ID: Sequence ID of an option item/class in the BOM of an
ATO model.

87. Component_Code: Component code of an option item/class in the BOM of an ATO
model.

88. Line_number: Line number of an item on sales order.

89. Included_item_flag: Indicates whether calling module has already exploded
included items for a PTO model/Kit or not.
• Null or 1 - Calling module has exploded included items

• 2 - Calling module has not exploded included items

90. Atp_flag: ATP flag for an item

91. Atp_components_flag: ATP Components flag for an item

92. Wip_supply_type: WIP Supply type for an item.

93. Bom_item_type: BOM item type for an item.

94. Mandatory_item_flag: Indicates whether the item is mandatory for PTO model or
not. This field is applicable only when the Included_item_flag field is set to 2.

95. Pick_components_flag: Pick components flag for an item.


96. Base_model_id: Inventory item id for the base model for a matched configuration.

97. Oss_error_code: Code of the error encountered while evaluating option specific
sourcing.

98. Matched_item_name: Name of the matched configuration. This field is populated
by ATP in case matched ATO configuration is found.

99. Cascade_model_info_to_comp: Indicates whether availability result information for
top ATO model should be cascaded to its components or not. Possible values:
• 1 or null - Model information is cascaded to its components

• 2 - Model information is not cascaded to its components

10 Sequence_number: Sequence in which items are passed to ATP for availability
0. check.

10 Firm_flag: Indicates whether line has been firmed or not. This field is specifically
1. used for Order Backlog Workbench.

10 Order_line_number: Line number for an item on Order backlog workbench. This
2. field is specifically used for Order Backlog Workbench.

10 Option_number: Number for on option on Order backlog workbench. This field is
3. specifically used for order backlog workbench.

10 Shipment_number: Shipment number for on option on Order backlog workbench.
4. This field is specifically used for Order Backlog Workbench.

10 Item_desc: Description of an item on Order backlog workbench. This field is
5. specifically used for Order Backlog Workbench.

10 Old_line_schedule_date: Old schedule date for a give line on Order Backlog
6. Workbench. This field is specifically used for Order Backlog Workbench.

10 Old_source_organization_code: Code of an organization in which order was last
7. scheduled. This field is specifically used for Order Backlog Workbench.

10 Firm_source_org_id: Code of an organization in which order was last scheduled.
8. This field is specifically used for Order Backlog Workbench.

10 Firm_source_org_code: Code of the source organization. This field is specifically

11 Firm_ship_date: Firm ship date. This field is specifically used for Order Backlog
0. Workbench.


11 Firm_arrival_date: Firm arrival date. This field is specifically used for Order
1. Backlog Workbench.

11 Ship_method_text: Ship method description. This field is specifically used for Order
2. Backlog Workbench.

11 Ship_set_id: ID for the ship set. This field is specifically used for Order Backlog
3. Workbench.

11 Arrival_set_id: ID for arrival set. This field is specifically used for Order Backlog
4. Workbench.

11 Project_ID: ID of the project with which line is associated. This field is specifically

11 Task_ID: ID of the task with which line is associated. This field is specifically used
6. for Order Backlog Workbench.

11 Project_number: Project number. This field is specifically used for Order Backlog
7. Workbench.

11 Task_number: Task number. This field is specifically used for Order Backlog
8. Workbench.

11 Attribute_11: Reserved for future ATP functionalities.
9.
0.
1.
2.
3.
4.
5.
6.
7.
8.
9.
0.


1.
2.
3.
4.
5.
6.
7.
13 Atf_date: ATF date associated with the combined item-product family item. This
8. field is used for internal ATP processing.

13 Plan_id: ID of the plan used to satisfy the demand.
9.
14 Original_request_date: Original request date for the order. This field is used for
0. internal ATP processing.

14 Receiving_cal_code: Code for the receiving calendar of the customer associated
1. with the line. This field is used for internal ATP processing.

14 Intransit_cal_code: Code for the In-transit calendar for the customer associated with
2. the line and the source organization. This field is used for internal ATP processing.

14 Shipping_cal_code: Code for the shipping calendar of the source organization. This
3. field is used for internal ATP processing.

14 Manufacturing_cal_code: Code for the manufacturing calendar of the
4. manufacturing organization. This field is used for internal ATP processing.

14 Internal_org_id: ID of the receiving organization in case of internal sales order
5.
14 First_valid_ship_arrival_date: If the request date type is Ship, this field contains the
6. first valid ship date after the system date as per the shipping calendar for the source
organization. If the request date type is Arrival, then this field contains the first
valid arrival date after the system date as per the receiving calendar of the
customer.

Data Validation for ATP_REC_TYPE
• Either requested_ship_date or requested_arrival_date should be provided. Error
will be generated if none or both of these dates are provided


• If delivery lead time and source organization id are specified then organization_id
and customer_site_id could be null. If either delivery lead time or source
organization are not specified, then at least one of these fields should be populated
to enable ATP to do global sourcing and delivery lead time calculation.

• Instance_ID must be provided if calling_module is 724.

• Inventory_Item_ID field should contain a valid inventory item ID.

• Quantity_ordered field should contain a valid quantity.

• Quantity_UOM should contain a valid unit of measurement value.

• Action field should contain a valid Action type. See the description of action field
for valid values.

• Old_Source_Organization_id and Old_Demand_class should be provided in case of
order rescheduling.

• Substitution_typ_code should always be populated if substitution needs to be done
for the item.

• Old_inventory_item_id should always be populated for a substituted line in case of
order rescheduling.

• Top_Model_line_id, ATO_Model_Line_Id, Parent_line_id, Config_item_line_id,
Component_Sequence_ID and Component_Code fields should always be
populated for Inquiry on ATO models.

Description of MRP_ATP_PUB.ATP_Supply_Demand_Typ
TYPE ATP_Supply_Demand_Typ is RECORD (

Col. 1 Col. 2

Level number_arr,



Request_Item_Id number_arr,



Col. 1 Col. 2

Department_Id number_arr,

Resource_Id number_arr,

Supplier_Id number_arr,

Supplier_Site_Id number_arr,

From_Organization_Id number_arr,

From_Location_Id number_arr,

To_Organization_Id number_arr,

To_Location_Id number_arr,


Uom char3_arr,

Disposition_Type number_arr,

Disposition_Name char80_arr,

Identifier1 number_arr,




Supply_Demand_Type number_arr,

Supply_Demand_Source_Type number_arr,

Supply_Demand_Source_Type_Name char80_arr,

Supply_Demand_Date date_arr,


Col. 1 Col. 2

Supply_Demand_Quantity number_arr,


Pegging_Id number_arr,


Original_Item_Id number_arr,

Original_Supply_Demand_Type number_arr,

Original_Demand_Date date_arr,

Original_Demand_Quantity number_arr,

Allocated_Quantity number_arr,

Pf_Display_Flag number_arr,

);
1. Level: Indicates the level of supply/demand in pegging.

2. Identifier: A unique identifier to identify a line (Order line number in case of OM).

3. Inventory_Item_Id: Inventory item ID (Product Family ID in case of product
family).

4. Request_Item_Id: Inventory Item ID.

5. Organization_Id: Organization ID of Organization where supply/demand is placed.

6. Department_Id: Department ID of the department to which resource belongs.

7. Resource_Id: Resource ID.

8. Supplier_Id: Supplier ID.

9. Supplier_Site_Id: Supplying Site ID.

10. From_Organization_Id: Shipping Organization ID. This field is not used by ATP at


present.

11. From_Location_Id: Shipping Location ID. This field is not used by ATP at present.

12. To_Organization_Id: Receiving Organization ID. This field is not used by ATP at
present.

13. To_Location_Id: Receiving Location ID. This field is not used by ATP at present.

14. Ship_Method: Ship Method Used. This field is not used by ATP at present.

15. Uom: Unit of Measurement.

16. Disposition_Type: This field is not used by ATP.

17. Disposition_Name: This field contains Order Number.

18. Identifier1: This field contains instance ID.

19. Identifier2: This field is not used by ATP.

20. Identifier3: This field contains demand ID in case of demand, and transaction ID in
case of supplies for resource or components.


22. Supply_Demand_Type: Type of supply demand. Possible values:

• 1 - Demand

• 2 - Supply

23. Supply_Demand_Source_Type: Type of Supply/Demand.

24. Supply_Demand_Source_Type_Name: This field is not used by ATP at present.

25. Supply_Demand_Date: Date of Supply/Demand.

26. Supply_Demand_Quantity: Supply/Demand Quantity.

27. Scenario_Id: This field is not used by ATP at present.

28. Pegging_Id: Pegging ID for the current record.

29. End_Pegging_Id: Top Parent's pegging ID.

30. Original_Item_Id: ID of the Original Item


31. Original_Supply_Demand_Type: Type of the original supply/demand. This is
applicable only for supplies and demands of items that are members of time-phased
enabled product families.

32. Original_Demand_Date: Date of the original demand. This is applicable only for
demands of items that are members of time-phased enabled product families.

33. Original_Demand_Quantity: Quantity of the original demand. This is applicable
only for demands of items that are members of time-phased enabled product
families.

34. Allocated_Quantity: Allocated quantity of the supply/demand - This field is used
for internal ATP processing.

35. Pf_Display_Flag: Indicates whether to display in ATP supply demand window.

Description of MRP_ATP_PUB.ATP_Period_Typ
TYPE ATP_Period_Typ is Record (

Col. 1 Col. 2

Level number_arr,












Col. 1 Col. 2




UOM char3_arr,

Total_Supply_Quantity number_arr,

Total_Demand_Quantity number_arr,

Period_Start_Date date_arr,

Period_End_Date date_arr,

Period_Quantity number_arr,

Cumulative_Quantity number_arr,




Pegging_Id number_arr,



Demand_Class char80_arr,

Class char80_arr,

Customer_Id number_arr,

Customer_Site_Id number_arr,


Col. 1 Col. 2

Allocated_Supply_Quantity number_arr,

Supply_Adjustment_Quantity number_arr,

Backward_Forward_Quantity number_arr,

Backward_Quantity number_arr,

Demand_Adjustment_Quantity number_arr,

Adjusted_Availability_Quantity number_arr,

Adjusted_Cum_Quantity number_arr,

Unallocated_Supply_Quantity number_arr,

Unallocated_Demand_Quantity number_arr,

Unallocated_Net_Quantity number_arr,

Total_Bucketed_Demand_Quantity number_arr,

Unalloc_Bucketed_Demand_Qty number_arr

);
1. Level: Indicates the level of supply/demand in pegging.

2. Identifier: A unique identifier to identify a line (Order line ID in case of OM).

3. Inventory_Item_Id: Inventory Item ID (Product family ID in case of product
family).

4. Request_Item_Id: Inventory Item ID.

5. Organization_Id: Organization ID of the organization where supply/demand is
placed.

6. Department_Id: Department ID of the department to which resource belongs.

7. Resource_Id: Resource ID.


8. Supplier_Id: Supplier ID.

9. Supplier_Site_Id: Supplying site ID.

10. From_Organization_Id: Shipping Organization ID. This field is not used by ATP at
present.

11. From_Location_Id: Shipping Location ID. This field is not used by ATP at present.

12. To_Organization_Id: Receiving Organization ID. This field is not used by ATP at
present.

13. To_Location_Id: Shipping Organization ID. This field is not used by ATP at present.

14. Ship_Method: Ship Method used. This field is not used by ATP at present.

15. Uom: Unit of Measurement.

16. Total_Supply_Quantity: Total supplies for a period.

17. Total_Demand_Quantity: Total demands for a period.

18. Period_Start_Date: Start date for a period.

19. Period_End_Date: End date for a period.

20. Period_Quantity: Net Supply-Demand quantity for that period.

21. Cumulative_Quantity: Cumulative quantity for a period after doing backward
consumption, forward consumption and accumulation.

22. Identifier1: Instance ID.


24. Scenario_Id: This field is for ATP internal use.

25. Pegging_Id: Pegging ID for the current record.

26. End_Pegging_Id: Pegging ID of the top parent.

27. Identifier4: Sysdate allocation percentage. Used by allocation workbench during
allocated ATP based on user defined allocation percentage.

28. Demand_Class: Demand class. Used by allocation workbench.

29. Class: Customer class. Used by allocation workbench.


30. Customer_Id: Customer ID. Used by allocation workbench.

31. Customer_Site_Id: Customer site ID. Used by allocation workbench.

32. Allocated_Supply_Quantity: Supply allocated to a demand class on a date. Used by
allocation workbench.

33. Supply_Adjustment_Quantity: Supply adjustment. Used by allocation workbench.

34. Backward_Forward_Quantity: Figures after backward and forward consumption.
Used by allocation workbench.

35. Backward_Quantity: Figures after backward consumption. Used by allocation
workbench.

36. Demand_Adjustment_Quantity: Demand adjustment. Used by allocation
workbench.

37. Adjusted_Availability_Quantity: Figures after demand class consumption. Used by
allocation workbench.

38. Adjusted_Cum_Quantity: Adjusted cumulative quantity. Used by allocation
workbench.

39. Unallocated_Supply_Quantity: Unallocated supply. Used by allocation workbench.

40. Unallocated_Demand_Quantity: Unallocated demand. Used by allocation
workbench.

41. Unallocated_Net_Quantity: Unallocated net. Used by allocation workbench.

42. Total_Bucketed_Demand_Quantity: Bucketed Demand. Used only in PF time
phased ATP.

43. Unalloc_Bucketed_Demand: Unallocated bucketed demand. Used in rule based and
time phased ATP.

Description of MRP_ATP_PUB.ATP_Details_Typ
TYPE ATP_Details_Typ is RECORD (

Col. 1 Col. 2

Level number_arr,


Col. 1 Col. 2



Request_Item_Name char40_arr,


Inventory_Item_Name char40_arr,


Organization_Code char3_arr,


Department_Code char10_arr,


Resource_Code char10_arr,


Supplier_Name char80_arr,



From_Organization_Code char3_arr,


From_Location_Code char20_arr,


To_Organization_Code char3_arr,


Col. 1 Col. 2


To_Location_Code char20_arr,


Uom char3_arr,

Supply_Demand_Type number_arr,

Supply_Demand_Quantity number_arr,

Source_Type number_arr,





Scenario_Id number_arr

);

Note: ATP_Details_Typ is not used by ATP at present.


C
Windows and Navigator Paths

• Windows and Navigation Paths

Windows and Navigation Paths
Refer to the following sources for other window and application information:
• Oracle Advanced Planning and Scheduling Implementation and User's Guide

• Oracle Application User's Guide

The following table lists the navigation path for each window.

• Brackets surrounding a path indicate a button selection.

• Logon responsibilities other than Advanced Supply Chain Planner
are indicated just before the navigation path.

Window Names and Navigation Paths

Window Name Navigation Path

Allocation Rules ATP > Allocation > Define Allocation Rule

Assign Allocation Rules ATP > Allocation > Assign Allocation Rules

Assignment Set Sourcing > Bills of Distribution > [Assignment Set]

ATP Criteria ATP > ATP Inquiry

Windows and Navigator Paths C-1


ATP Details ATP > ATP Inquiry > [ATP Details]

ATP Rules Inventory: Setup > Rules > Available-To-Promise

ATP Sources and Group Pick Sources
Availability

Bills of Distribution Sourcing > Bills of Distribution

Bills of Material Manufacturing and Distribution: Bills of Materials > Bills

Collection Workbench Collections > View Collected Data

Define Priority Rules Setup > Priority Rules

Find Requests Other > Request

Horizontal ATP ATP > ATP Inquiry > [ATP Details] > [Right-click] >
Horizontal ATP

Instances Order Management: Scheduling > ATP > Scheduling Setup >
Instances

Item Inventory: Items > Organization Items

Launch Purge Program for Collections > Legacy Systems > Purge Collected Data
Collected data [Parameters]

Launch SCP Plan Supply Chain Plan > Launch > [Parameters]

MRPFIND Order Management > Order, Returns > Schedule Order >
[Create/Edit]

Order Backlog Workbench Order Management > Scheduling > [Schedule]

Order Sequencing Order Management > Order, Returns > Schedule Order >
[Create/Edit] > [Manual Sequence]

Organizations Other > Change Instance/Organization

Personal Profile Values Other > Profile

C-2 Oracle Global Order Promising Implementation and User's Guide


Planning Data Collection Collections > Oracle Systems > Data Collection

- Collections > Legacy Systems > Collect Flat File Data

Planning Parameters Setup > Parameters

Preferences Tools > Preferences

Progress Order Management > Order, Returns > Schedule Order >
[Create/Edit] > [Manual Sequence] > [Apply] > [Schedule]

Properties ATP > ATP Inquiry > [ATP Details] > [Right-click] > Properties

Regions Sourcing > Assign Sourcing Rule > [Region/Zone column
LOV]

Requests Other > Request > [Find]

Resources Manufacturing and Distribution Manager: Bills of Materials >
Routings > Departments > [Resources]

Sales Order Pad Order Management > Orders, Returns > Sales Order

Schedule Orders Order Management > Order, Returns > Schedule Order

Sourcing Rules Sourcing > Sourcing Rules

Sourcing Rule/Bill of Sourcing > View Assignments
Distribution Assignments

- Sourcing > Assign Sourcing Rules

Submit Request Other > Request > Submit a New Request] > Single Request

Supply Chain Planner Supply Chain Plan > Workbench
Workbench

- Supply Chain Plan > View Plan

Supply/Demand ATP > ATP Inquiry > [ATP Details] > [Right-click] >
Supply/Demand

Windows and Navigator Paths C-3


Transit Times Manufacturing and Distribution: Order Management >
Shipping > Setup > Regions and Zones > Transit Times

View Allocations ATP > Allocation > View Allocation

View Assignment Sourcing > View Assignments

View Bill of Distribution Sourcing > View Bills of Distribution

View Sourcing Assignment Sourcing > View Sourcing Hierarchy
Hierarchy

View Sourcing Rule Sourcing > View Sourcing Rules

Work Dates View Work Dates

C-4 Oracle Global Order Promising Implementation and User's Guide

Glossary

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.

aggregate resources
The summation of all requirements of multi-department resources across all
departments that use it.

allocated ATP
This term is used to describe the ability to allocate scarce supply, whether it's finished
goods, or a key components or resources, to various demand channels. Whether you are
performing ATP or CTP, the allocation is being considered for order promising. See
Feature Highlight: Allocation.

alternate bill of material
An alternate list of component items you can use to produce an assembly.

alternate resources
Different resource or a group of different resources that can be used instead of primary
resource or group of resources in the job operation. Each resource, or group of
resources, can form an alternate group. Alternative scheduling is when the primary
group can be replaced by an alternate group in the job operation.

alternate routing
An alternate manufacturing process you can use to produce an assembly.

alternate unit of measure
All other units of measure defined for an item, excluding the primary unit of measure.

API
An application programming interface (API) is a published interface to accomplish a
business or scientific function. An API defines a contract to its users by guaranteeing a

Glossary-1

published interface but hides it's implementation details.

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
standard, model, and option class items.

assembly
An item that has a bill of material. You can purchase or manufacture an assembly item.
seeassemble-to-order, bill of material.

assignment hierarchy
You can assign sourcing rules and bills of distribution to a single item n 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.

ATO
Seeassemble-to-order.

ATO item
See assemble-to-order item.

ATO model
Seeassemble-to-order model.

ATP (Available to Promise)
ATP (Available to Promise) typically refers to the ability to promise finished goods
availability based on a statement of current and planned material supply.

ATP
Seeavailable to promise.

available capacity
The amount of capacity available for a resource or production line.

available to promise (ATP)
The quantity of current on-hand stock, outstanding receipts and planned production

Glossary-2

which has not been committed through a reservation or placing demand. In Oracle
Inventory, you define the types of supply and demand that should be included in your
ATP calculation.

available-to-promise rule
A set of Yes/No options for various entities that the user enters in Oracle Inventory. The
combination of the various entities are used to define what is considered supply and
demand when calculating available to promise quantity.

basic ATP
This term is used to describe the task of performing an ATP check against a given
organization.

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
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 resources
A list of each resource and/or production line required to build an assembly, model, or
option.

bottleneck resource
A resource whose capacity is less than the demand placed upon it. For example, a
bottleneck machine or work center exists where jobs are processed at a slower rate than
they are demanded.

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.

Glossary-3

calendar type
The period pattern used to define a manufacturing calendar.

capable to deliver
CTD (Capable to Deliver) refers to considering the transportation resources and
transportation lead time to meet your customers delivery needs. In this release, only
transportation lead time is being considered. Transportation resources will be added in
a future release.

capable to promise
CTP (Capable to Promise) refers to the additional ability to determine the availability of
component materials and resources to meet unplanned demands.

capacity requirements planning
A time-phased plan comparing required capacity to available capacity, based on a
material requirements plan and department/resource information. Seerouting-based
capacity and rate-based capacity.

component
A serviceable item that is a part or feature in another serviceable item. Your customers
cannot report service requests against this type of serviceable item directly. You can
reference components when you enter service requests against actual end item-type
serviceable items, or products. For example, if you define three inventory items, A, B,
and C, where A and B are products (end item-type serviceable items) but C is a
component (non-end item-type serviceable item) of A, you can enter service requests
against A and B directly, but not against C. When you enter a service request against
product A, you can reference C because it is a component of A. see standard
component.

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.

Glossary-4

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

discrete job
Discrete jobs are used to manufacture assemblies using specific materials and resources
within a start and end date. (Also known as work order or assembly order).

end item
Any item that can be ordered or sold. Seefinished good and product.

engineering change order (ECO)
A record of revisions to one or more items usually released by engineering.

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.

forward consumption
A mechanism used in planning during which the available future supply is consumed
to meet a 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.

independent demand
Demand for an item unrelated to the demand for other items.

item routing
A sequence of manufacturing operations that you perform to manufacture an assembly.
A routing consists of an item, a series of operations, an operation sequence, and
operation effective dates. Edits to an Item Routing do not automatically update a job
routing.

job routing
A snapshot of an item routing that has been assigned to a job. The routing is current on

Glossary-5

the day the job was created. Edits to a job routing do not automatically revert to the
item routing.

master demand schedule
The anticipated ship schedule in terms of rates or discrete quantities, and dates. In
ASCP, MDS is used as an input to the enterprise plan.

material constrained plan
In this plan, all material constraints that can be specified in the form of a supply
schedule from manufacturing plants or by statements of vendor capacity from vendors
are considered. When material availability is not a concern, resource availability
constraints are used only to generate exceptions arising due to over utilization or
under-utilization of resources.

material and resource constrained plan
In this plan, you can generate a plan that respects material, resource, and transportation
constraints. However, no plan objectives are considered.

multilevel supply chain ATP/CTP/CTD
This term is used to describe the task of performing a multilevel BOM availability check
including finished goods, components, resource, supplier capacityand transportation
lead time. See Feature Highlight: Multilevel Supply Chain ATP/CTP/CTD
For the rest of the document, we will use Multilevel ATP as a short form for this feature.

need-by date
The need-by date for the end item is the demand date. The need-by dates for the
dependent demands are calculated based on the lead-time offsets that are associated to
the Items and routings used.
• If a constrained plan is run, the planning process will use the planned orders and
actual routings for scheduling to derive the suggested due date.

• If an unconstrained plan is run, the suggested due date will simply be the same as
the need by date.

Therefore, any differences between the lead time offsets (need by date) and actual
manufacturing time (suggested due date) created by the planning process, will show up
in the form of multiple exception messages.

operation data store (ODS)
It represents all the tables that acts as destination for the collected data from each of the
data sources (both Oracle Applications or legacy systems). This acts as the input for the
snapshot portion of the planning process.
When we refer to ODS based ATP, we mean ATP based on collected data.

Glossary-6

optimized plan
In this plan, you can generate an optimized and executable plan based on plan
objectives as well as material, resource, and transportation constraints.

overload
A condition where required capacity for a resource or production is greater than
available capacity.

pegging
The capability to identify for a given item the sources of its gross requirements and/or
allocations. Pegging can be thought of as active where-used information.

planned order
A suggested quantity, release date, and due date that satisfies net item requirements.

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 data store (PDS)
It represents all the tables within Oracle ASCP which encompass those in the ODS and
other output tables from planning. When we refer to PDS based ATP, we mean ATP
based on planning output.

planning exception set
An item attribute that the planning process uses to decide when to raise planning
exceptions for the item.

planning horizon
The amount of time a master schedule extends into the future.

planning time fence
A Master Scheduling/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.

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

Glossary-7

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.

processing lead time
The time required to procure or manufacture an item. For manufactured assemblies,
processing lead time equals the manufacturing lead time.

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
The total quantity on hand plus the total scheduled receipts plus the total planned
orders.

refresh snapshot process
A database process during which the data stored in the database snapshots are updated
with the new/changed data.

resource constrained plan
In this option, all resource constraints such as available machine hours, transportation
capacity, as well as alternate resources are considered. Alternate bill of materials are
considered only when optimized option is selected. Material constraints are used only
to generate exceptions arising due to lack of material availability.

routing
A sequence of manufacturing operations that you perform to manufacture an assembly.
A routing consists of an item, a series of operations, an operation sequence, and
operation effective dates.

safety stock
Quantity of stock planned to have in inventory to protect against fluctuations in

Glossary-8

demand and/or supply.

schedule arrival date
The date when scheduled receipts are expected to arrive as suggested by the planning
process. Also the date on which sales orders are expected to arrive at customer's
location.

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.

schedule ship date
The date when you expect the supplier to ship scheduled receipts as suggested by the
planning process. Also the date on which the sales order is planned for shipping to the
customer.

Seiban manufacturing
A type of manufacturing environment where demand and supply are identified by
Seiban numbers to peg supply to demand. This numbering system is widely used in
Japan and Korea.

simultaneous resources
Two or more resources are scheduled to be working concurrently within a job
operation. Each operation contains a scheduled sequence of activities and resources
used in the operation. Simultaneity is implemented by having more than one resource
used in an operation.

sourcing rule
Specifies how to replenish items in an organization, such as purchased items in plants.

suggested dock date
The date you expect to receive an order (to arrive on the receiving dock) as suggested
by the planning process.

suggested due date
The date when scheduled receipts are expected to be received into inventory and
become available for use as suggested by the planning process.
The need-by date for the end item is the demand date. The need by dates for the
dependent demands are calculated based on the lead-time offsets that are associated to
the Items and routings used.
• If a constrained plan is run, the planning process will use the planned orders and

Glossary-9

actual routings for scheduling to derive the suggested due date.

• If an unconstrained plan is run, the suggested due date will simply be the same as
the need by date.

Therefore, any differences between the lead time offsets (need-by date) and actual
manufacturing time (suggested due date) created by the planning process, will show up
in the form of multiple exception messages.

suggested order date
The date that the planning process suggests an order for goods or services is entered.
The earliest order date allowed is today and no compression days are allowed.

suggested start date
The date you or your suppliers expect to start to manufacture the order as suggested by
the planning process.

supply chain ATP
This term is used to describe the task of performing an ATP check against multiple
sourcing organizations for a given customer request. See Feature Highlight: ATP for
Multiple Supply Locations.

supplier flex-fences
Specifies capacity tolerance percentages that vary over time for each source. This allows
you to represent the ability of your supplier to flex capacity upwards based on the
amount of advanced notice you provide.

time bucket
A unit of time used for defining and consuming forecasts. A bucket can be one day, one
week, or one period.

unconstrained plan
In this plan, the system performs traditional MRP type planning and assumes infinite
material availability and resource capacity. Statements of material availability and
resource capacity are used to generate exceptions. Demand priorities are included
during the planning run to determine the appropriate pegging relationships between
supply and demand.

underload
A condition where required capacity for a resource or production is less than available
capacity.

Glossary-10

Index

setup, 3-33
A product family ATP, 3-28
ATP logic, 3-29
aggregate time fence, 4-81
ATP result, 3-30
API
business application, 3-29
data validation
examples, 3-30
ATP_REC_TYPE, B-20
setup, 3-29
description, B-1
SLSC ATP
MRP_ATP_PUB.ATP_Details_Typ, B-29
assignment set, 3-4
MRP_ATP_PUB.ATP_Period_Typ, B-25
ATP for multiple supply locations, 3-3
MRP_ATP_PUB.ATP_Supply_Demand_
ATP logic, 3-5
Typ, B-21
ATP result, 3-5
nested tables, B-3
example, 3-6
PROCEDURE Call_ATP, B-1
setup, 3-3
specification, B-1
SLSC ATP setup
ATP_Rec_Typ, B-3
sourcing rule, 3-3
architecture, 8-15
ATP based on collected data setup flow, 2-9
Assemble-To-Order, 1-2
ATP based on planning output
ATP based on collected data
24x7 ATP support, 5-37
basic ATP, 3-1
configuration ATP, 3-8
impact of failures, 5-41
ATO item, 3-23
setup, 5-37
ATO model, 3-12
allocated ATP, 4-105
based on collected data, 3-12
allocated ATP based on user-defined
allocation percentage, 4-106
kit, 3-27
allocation effective dates, 4-108
PTO model, 3-20
allocation percentages, 4-108
demand class ATP, 3-31
allocation priorities, 4-109
ATP logic, 3-32
ATP logic, 4-117
setup, 3-31
examples, 4-119
versus allocated ATP, 3-31
setup, 4-107
improved ATP performance, 3-32
allocated ATP based on demand priority, 4-

Index-1

142 product family ATP, 4-73
assigning allocation rules, 4-145 ATP logic, 4-74
ATP logic, 4-149 business application, 4-73
ATP post plan processing, 4-147 Capable-To-Promise for product family
business application, 4-142 item, 4-75
create ATP partitions, 4-143 examples, 4-75
define allocation rules, 4-144 setup, 4-74
define demand classes, 4-144 Support of Lot Based Components, 5-31
run ATP plan, 4-147 unplanned items, 5-45
setup, 4-143 ATP based on planning output setup flow, 2-20
View Allocation, 4-147 ATP inquiry, 6-1
basic ATP, 4-1 ATP Criteria, 6-2
ATP logic, 4-2 ATP Criteria window, 6-2
ATP result, 4-2 Assignment Set, 6-4
business application, 4-1 Line Set, 6-4
setup, 4-1 Pick Sources, 6-3
configuration ATP, 4-32 Req Date, 6-4
ATO item, 4-68 Request Date Type, 6-4
business application, 4-32 ATP Details, 6-5
examples, 4-32 Expand, 6-12
kit, 4-71 Horizontal ATP, 6-14
PTO model, 4-44, 4-53, 4-64 pegging region, 6-8
single-level, single-org ATO model, 4-36 Properties, 6-14
end item substitution, 5-1 summary region, 6-5
ATP logic, 5-5 Supply/Demand, 6-12
ATP result, 5-27 view the ATP results, 6-11
examples, 5-8 ATP Details window, 6-5
setup, 5-1 ATP Sources and Group Availability, 6-25
improved ATP performance, 5-43 enter ATP criteria, 6-2
ATP based on summary data, 5-43 Global Availability, 6-24
manually generating summary tables, 5- Org, 6-25
44 Pick, 6-25
multi-level ATP Ship Method, 6-25
ATP logic, 4-11 Site, 6-25
business application, 4-3 Supplier, 6-25
data collection and run plan, 4-11 ATP Support for Distribution Planning, 5-46
designate a specific resource for Available-To-Promise, 1-1
Capable-To-Promise check, 4-10
regional level sourcing, 4-5 B
Regions window, 4-8
basic ATP
resource capacity, 4-9
ATP logic, 4-2
Resources window, 4-10
basic queries, 8-16
setup, 4-4
simplified supply chain scenario, 4-3
C
supplier capacity, 4-11
transit lead times, 4-8 Capable-To-Deliver, 1-1
multiple plans, 5-42 Capable-To-Promise, 1-1

Index-2

carrier calendars, 6-34 230, 8-3, 8-7
change management, 4-41 240, 8-6
combined item-product family atp, 4-80 47, 8-2, 8-6
configuration, 1-5 52, 8-2
integrated planning serverconfiguration, 1-5 53, 8-3, 8-7
standalone planning server configuration, 1-5 57, 8-2
configuration ATP, 1-2 61, 8-3, 8-7
80, 8-4, 8-8
D 85, 8-4, 8-8
90, 8-4, 8-8
debugging
architecture, 8-14
ATP debug file, 8-12 F
centralized implementation, 8-13 forecast, 4-42
decentralized implementation, 8-13 full summarization, 5-44
database links, 8-14 functional setup for ATP based on collected data,
debugging areas, 8-14 2-8
demand relief, 4-42 functional setup for ATP based on planning
demand spread calculation, 4-83 output, 2-19
deployment, 1-6
ATP based on collected data, 1-6, 1-6 G
capabilities, 1-6
global availability, 3-16, 4-45
ATP based on planning output, 1-6, 1-7
capabilities, 1-7
H
diagnostic ATP, 6-16
ATP logic, 6-19 honoring plan recommendations, 5-45
manufacturing lead time constraint, 6-20
material/resource constraint, 6-22 I
planning time fence constraint, 6-22 incremental summarization, 5-44
purchasing lead time constraint, 6-21 infinite time fence, 3-16, 4-46
transfer lead time constraint, 6-21 integration with other Oracle applications, 1-4
show constraints, 6-18 M
match to existing configuration, 3-14, 4-40
E
multi-level supply chain ATP, 1-2
enforcing purchasing lead time constraint, 4-30 multi-level supply chain CTD, 1-2
error code multi-level supply chain CTP, 1-2
120, 8-5
130, 8-2 N
140, 8-2, 8-6
navigator paths and windows, C-1
150, 8-5
net availability calculation, 4-84
160, 8-2, 8-5
180, 8-3, 8-7
19, 8-3, 8-7
O
200, 8-5 option dependent resource, 4-45
220, 8-3, 8-7 option specific sourcing, 3-14, 4-43
23, 8-3, 8-7 Oracle Configurator, 1-4

Index-3

Oracle Global Order Promising, 1-1
Oracle iStore, 1-4 P
Oracle Order Management, 1-4
profile options, A-1
Oracle Spares Management, 1-4
BOM: Match To Existing Configuration, 4-40,
Order Backlog
A-10
scheduling process, 7-2
INV: Capable to Promise, 2-15, 2-25, 6-35, A-9
Order Backlog Workbench, 7-1
INV: External ATP, A-10
capabilities, 7-1
MRP: ATP Assignment Set, 2-7, 3-4, 3-5, 3-5, 3-
Filter Criteria, 7-2
7, 4-11, 6-4, 7-11, A-2
navigator tree, 7-3, 7-3
MRP: ATP Database Link, A-2
Exceptions tab, 7-3
MRP: Calculate Supply Demand, 5-44, 6-12, 6-
Items tab, 7-4
12, A-2
Orders tab, 7-3
MRP: Include Substitute Components, A-2
order line pegging, 7-5
MRP: Set Category for Backlog Form, A-3
order line pegging information, 7-3
MSC: Action Allowed on ATP 24x7 Plan
Priority Rules, 7-2
While Running, 5-37, 5-39
reschedule line results, 7-4
MSC: Allocated ATP Forward Consumption
reschedule lines results, 7-3
Method, 4-108, 4-108
Schedule Orders, 7-2
MSC: Allocation Method, 5-23
scheduling order lines, 7-12
MSC: ATP 24x7 Synchronization Downtime,
Accept simulated scheduling
5-37, 5-40, 5-40, A-4
recommendations, 7-14
MSC: ATP Allocation Method, 4-107, 4-143, A-
Firm, 7-13
5
Reject simulated scheduling
MSC: ATP Assignment Set, 2-7, 3-5, 3-5, 4-8, 4-
recommendations, 7-14
11, A-5
simulated order line, 7-12
MSC: ATP Capacity Allocation, A-5
selection criteria for scheduling, 7-6
MSC: ATP Debug Mode, A-5
Criteria folder window, 7-8
MSC: ATP Enforces Lead Time for ATO
define priority rules, 7-6
Models, 3-13, 3-13, A-6
Manual Sequence, 7-11
MSC: Choice of Item for Which to Create
Priority Rule, 7-10
Supplies in Substitute Relationship, 5-3, 5-4, 5-
Priority Rules, 7-6
5, 5-9, 5-10, 5-12, 5-12, 5-13, 5-15, 5-16, 5-20, 5-
Priority Rules window, 7-7
23
Progress window, 7-12
MSC: Class Hierarchy, 4-107, 4-143, A-6
rescheduling concurrent program, 7-12
MSC: Collection Window for Trading Partner
schedule orders, 7-8
Changes, A-6
Schedule Orders window, 7-9
MSC: Display Order Rescheduling Supplies, 4-
user interface, 7-3
43, A-6
order scheduling, 6-26
MSC: Enable Allocated ATP, 4-107, 4-143, A-6
examples, 6-26
MSC: Enable Allocated ATP Workflow, 4-143
Schedule Arrival Date, 6-26
MSC: Enable ATP Summary Mode, 2-15, 2-25,
Schedule Ship Date, 6-26
3-33, 5-43, A-7
timestamp, 6-26
MSC: Enable ATP Workflow, 4-107, 5-4, 5-29,
override ATP, 6-31
6-32, A-7
MSC: Excess and Safety Stock by Demand
example, 6-32
Class, A-7
setup, 6-32

Index-4

MSC: Horizontal Plan Demand Bucketing two instances setup, 2-4
Preference, A-8 create database links, 2-5
MSC: Sales Orders Offset Days, A-8 define instance, 2-6
MSC: Share Plan Partitions, 2-2, 2-6 run Create APS Partition Concurrent
MSC: Sourcing History Start Date Offset, A-8 program, 2-6
MSC: Use Shipping/Receiving Calendars, A-9 run Create Global ATP Flexfields
MSO: Global Batchable Flag, 4-30 Concurrent program, 2-6
OM: Authorize to Override ATP, 6-32
T
R troubleshooting, 8-1
RAC, 2-5 data errors, 8-1, 8-4
Real Application Clusters, 2-5 debugging, 8-12
receiving calendars, 6-34 other troubleshooting errors, 8-9
reschedule order, 3-14, 3-26 SQL queries, 8-15
resource requirement relief, 4-42 troubleshooting, 8-1

S W
shipping calendars, 6-34 windows
single statement of availability, 1-3 Allocation Rule, 4-109, 4-112
SQL queries Allocation Rules, 4-144
ATP has detected invalid objects. Contact your Assign Allocation Rule, 4-111
system admin, 8-22 Assign Allocation Rules, 4-146
data error code queries, 8-17 ATP Criteria, 6-2
Invalid ATP Rule or No ATP Rule defined, 8- ATP Details, 2-11, 3-2, 3-5, 4-2, 4-70, 5-27, 5-28,
19 6-5
INV Capable To Promise must be same at ATP Inquiry, 5-27
source and destination, 8-23 ATP Rules, 2-10, 2-21
Plan not found, 8-20 Availability, 3-2, 4-2
Some past due sales orders, supplies, or Batching, 4-30
demands are not included in the ATP, 8-23 Bill of Distribution Assignments, 4-8
This item is not collected. Please run Data Criteria, 7-8
Collection, 8-19 Define Priority Rules, 7-6
Unable to find a calendar date, 8-17 Global Availability, 6-24
supplier capacity calendars, 4-11 Horizontal ATP window, 6-14
supplier capacity for procured model, 4-46 Instances, 2-3, 2-6
supply relief, 4-42 Item, 5-2, 5-4
system setup, 2-1 Item Substitution, 5-2
destination instance, 2-1 MPS/MRP Planning tab, 5-2
one instance setup, 2-1 Item Relationship, 5-2
define instance, 2-3 Order Backlog Workbench, 7-3
install patches, 2-2 Exceptions tab, 7-3
run Create APS Partitions Concurrent Orders tab, 7-3
program, 2-2 Order Sequencing, 7-11
run Create Global ATP Flexfields Parameters, 5-38
Concurrent program, 2-2 Plan Definition, 4-147
source instance, 2-1 Planner Workbench, 5-38

Index-5

Plan Options, 5-6
Decision Rules tab, 5-6
Progress, 7-12
Properties, 6-15
Regions, 4-8
Resources, 4-10
Schedule Orders, 7-8
Submit Request, 5-45
Supply/Demand, 6-13
Transit Times, 2-15, 2-26
View Allocation, 4-113, 4-147
windows and navigator paths, C-1

Index-6

R12 gop

Recommended

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to R12 gop (20)

Recently uploaded (20)

R12 gop