March 2013

Oracle Fusion Applications

Setting Up Order Orchestration: Quick Start
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Disclaimer
The following is intended to outline our general product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or
functionality, and should not be relied upon in making purchasing decisions. The development, release, and
timing of any features or functionality described for Oracle’s products remains at the sole discretion of
Oracle.

Warning
The tasks presented in this guide are intended for a quick introduction or pilot implementation. The guide
does not include all the setup and security tasks that are appropriate for a complete implementation.
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Table of Contents
Table of Contents ................................................................................ 1
Introduction ......................................................................................... 2
Access Requirements ......................................................................... 2
Pilot Implementation Overview ............................................................ 3
Table 1: Performing Common Applications Configuration Tasks ........ 4
Table 2: Setting Up Product Model and Importing Items .................... 5
Table 3: Defining Source Systems and Importing Customers............. 6
Table 4: Collecting Data ...................................................................... 7
Table 5: Enabling Global Order Promising .......................................... 9
Table 6: Performing Order Orchestration Setup Tasks ..................... 10
Table 7: Preparing to Run Test Orders ............................................. 12
Appendix ........................................................................................... 14
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Introduction
This document provides a high-level overview of the key tasks that implementors perform to implement
the Oracle Fusion Distributed Order Orchestration and Oracle Fusion Global Order Promising applications
in a pilot project after installation and provisioning of Oracle Fusion Applications.

Warning: This document does not include all the steps and security tasks required for a full
implementation of the Order Orchestration offering. This document presents the minimum implementation
steps that must be performed to receive and fulfill test orders using an infinite availability ATP rule.

Before you begin your pilot implementation, determine the following for your test orders:
- Which items will be ordered and which customers will order the items?
- What item organizations will your items be associated to?
- Which units of measure (UOMs) and currencies you will use in your orders?

References to related help accompany the steps. The help is available from Oracle Fusion Applications
Help or the Oracle Fusion Applications Order Orchestration Implementation Guide unless specified
otherwise.

You can find this document (ID: 1536529.1) on My Oracle Support, at [Link]

Access Requirements
To get started with Oracle Fusion Applications implementation, you need access to Oracle Identity
Manager (OIM), Oracle Authorization Policy Manager (APM), and Oracle Fusion Applications.

Before you begin, make sure you have the following information. You will need some familiarity with
running UNIX commands.

• URLs for Oracle Fusion Applications and OIM

For example, the URL for Oracle Fusion Applications is
[Link] where host is the name of the
host location such as [Link].
If you do not know the URLs, contact the person who installed the systems at your company.
When the Oracle Fusion Applications provisioning process ends, these URLs are shown on the
summary page. They are also recorded in a file whose default name is Provisioning Summary.
The person installing the software, however, has the option to choose a different file name. The
file is created in the same location as the provisioning plan.

• The user name and password of the Oracle Fusion Applications super user and the OIM
system administrator user

The default user name of the Oracle Fusion Applications super user is FAADMIN. The default
OIM system administrator user name is XELSYSADM. Contact the person who installed the
systems for the actual user names and passwords specified during installation and provisioning.

• Location of the Oracle home directory in the Oracle Identity Management (IDM) environment
(IDM_ORACLE_HOME)

Note: If you are already set up with access to the Functional Setup Manager (FSM), you can
invoke tasks from FSM to access OIM and APM instead of using the additional URLs.

2
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Pilot Implementation Overview

To complete your pilot implementation you must perform a subset of the tasks within these task lists:

• Define Common Applications Configuration for Order Orchestration

• Define Common Order Orchestration Configuration
• Define Order Promising
• Collect Order Promising Reference and Transaction Data
• Manage Order Promising Rules
• Define Sales Order Fulfillment
A list of the task lists and tasks you must perform for a pilot implementation is provided in the appendix of
this document.

Within this document, the following tables provide documentation references for each of the tasks that
must be performed. The purpose of this guide is to specify which tasks must be performed for a pilot
implementation. For details on how to perform the tasks, refer to the referenced documentation. Where
applicable, these tables also provide suggestions for providing the minimal amount of data required to
implement the task for a pilot implementation. Before you start performing tasks, review the
documentation references and data requirements provided within these tables.

• Table 1: Performing Common Applications Configuration Tasks

This table includes user, security, enterprise structure, and common reference object tasks that
are applicable to all Oracle Fusion implementations. This table also includes the Manage Item
Organizations task.
• Table 2: Set Up Product Model and Importing Items
This table includes the Common Order Orchestration tasks that you must perform to set up
Oracle Fusion Product Model and to import items. You must set up Product Model before you
can import items.
• Table 3: Defining Source Systems and Importing Customers
This table includes the Common Order Orchestration tasks that you must perform to define the
source systems that your test orders will specify as the source of the order and the tasks that
you must perform to be able to import customers.
• Table 4: Collecting Data
This table includes the Define Order Promising task and Collect Order Promising Reference and
Transaction Data task. You must perform these tasks to collect the reference data required by
order orchestration when decomposing an order.
• Table 5: Enabling Global Order Promising
This table includes the Manage Order Promising Rules tasks that you must perform.
• Table 6: Performing Order Orchestration Setup Tasks
This table includes the three tasks that you must perform within the Define Sales Order
Fulfillment task list. Predefined data, sufficient for a pilot implementation, are provided for the
other tasks within this task list.
• Table 7: Preparing to Run Test Orders
This table includes the final tasks that you must perform to run test orders.

3
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Table 1: Performing Common Applications Configuration Tasks

Tasks Description Documentation

Task 1: For each step in task 1, table 1 of this

Perform initial document, refer to the corresponding
The following implementation steps are common to all
implementation table in the Getting Started with
Oracle Fusion Applications. You must complete these
steps common Oracle Fusion Applications: Common
steps before continuing with task 2 in this table and in
to all Oracle Implementation document (ID:
the remaining tables in this document.
Fusion 1387777.1) on My Oracle Support,
Applications [Link] for
additional documentation references.
1. Prepare Oracle Fusion Applications Super User for
User Management and Configuration. Tables 1 - 3 in the Getting Started
with Oracle Fusion Applications:
2. Prepare IT Security Manager Role for User and Role Common Implementation document
Management. (ID: 1387777.1)
3. Generate Functional Setup Task List.
Notes:
• Select the Order Orchestration offering as
the offering you want to implement.
• The Order Orchestration offering specifies the
tasks for a full implementation. Refer to the
appendix of this guide for a list of the subset
of tasks specified in this document or in the
sections of the other getting started
documents referenced by this document.
Table 4 in the Getting Started with
4. Define Implementation Users. Oracle Fusion Applications: Common
Implementation document (ID:
5. Define Basic Enterprise Structures.
1387777.1)
Notes:
Table 5 in the Getting Started with
- For your pilot implementation, you can use the Oracle Fusion Applications: Common
default enterprise structure. Implementation document (ID:
1387777.1)
- The Order Orchestration work area displays
orders for the business units to which the
current user has access. For each business
unit in the enterprise that will receive orders,
you must create a business unit in the
application.
A set is a collection of business units.
Distributed Order Orchestration uses sets to
restrict access to holds and orchestration
processes. When you create a business unit,
you must specify a default set. For the pilot,
use the predefined Common Set for the
default set.
Table 6 in the Getting Started with
6. Define Users for Functional Testing. Oracle Fusion Applications: Common
The implementation users created earlier have Implementation document (ID:
extensive privileges. If you want to test having different 1387777.1)
users with fewer privileges, define users with the

4
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Tasks Description Documentation

following roles specific to order orchestration:
• Job role: Order Manager
• Job Role: Order Administrator
• Job Role: Supply Chain Application
Administrator
• Abstract role: Error Recovery
To see how these roles implement role-based security,
you should create these users:
- At least one user with just the Order Manager
role
- A user with the Order Manager role and the
Error Recovery role.
- A user with the Order Administrator role and
the Supply Chain Application Administrator role
Note: The Order Administrator role is inherited
through the Supply Chain Application
Administrator role.

Task 2: Manage Configure your item organizations to be used by the

The Oracle Fusion Product Information
Item Oracle Fusion Product Model. You will also need at least
Management Implementation Guide is
Organizations one organization that represents a warehouse from
available in the Oracle Fusion
which you will collect supply data to fulfill orders.
Applications Technology Library
Warehouses from fulfillment systems must be
configured as item organizations in Oracle Fusion. Do Chapter 7: Define Enterprise Structures
not associate item organizations with a business unit.
Section: Define Facilities:
Go to the Manage Item Organizations task. Manage Item Organizations

Table 2: Setting Up Product Model and Importing Items

The items referred to in orders must be contained in the Oracle Fusion Product Model. To set up Product
Model and import the items that you will order in your test orders, you must perform the implementation
tasks in this table. Note that the items you import must be associated with the item organizations you
created in table 1.

Tasks Description Documentation

Task 1: Create
Use the Setup and Maintenance page to The Oracle Fusion Product Information Management
Units of Measure
go to the Manage Units of Measure Implementation Guide which is available in the Oracle
task. Fusion Applications Technology Library

Chapter 3: Manage Units of Measure

5
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Tasks Description Documentation

Task 2: Set up
Before you can import items, you must The Oracle Fusion Product Information Management
Oracle Fusion
perform the following steps to set up Implementation Guide is available in the Oracle Fusion
Product Model
Oracle Fusion Product Model. Go to these Applications Technology Library
tasks by searching for the task name in
the All Tasks tab of the Overview region Chapter 16: Define Product Information Management
of the Setup and Maintenance page.

1. Create Item Lifecycle Phases

2. Associate Item Lifecycle Phase
with Root Item Class
3. Create Key Flexfield Structures
for Catalogs (Release 5 and
prior)
4. Create Functional Catalogs
(Release 5 and prior)
5. Assign Catalogs to Functional
Areas (Release 5 and prior)
6. Deploy Flexfields

Task 3: Import
Use the import items process to import
items Oracle Fusion Applications Order Orchestration
the items that your test orders will
reference. Implementation Guide, Define Common Order

Go to the Import Items task. Orchestration Configuration chapter

The Import Items task creates a • Importing Items: Explained

background process that takes the data
that is loaded in the interface tables and
uses the import process to move the data The Oracle Fusion Applications Product Management,
to the production tables. The import Product Information Management Guide available in the
processes will perform all of the Oracle Fusion Applications Concept and User Guides Library
validations necessary to ensure the • Manage Imports: Overview in Chapter 17
imported data is correct prior to moving
the data into the production tables. • Creating Item Batches: Explained in Chapter 18

Table 3: Defining Source Systems and Importing Customers

To define the source systems and customers referred to by your test orders, perform the implementation
tasks in this table.

The documentation in this table is found in the Oracle Fusion Applications Order Orchestration
Implementation Guide.

6
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Tasks Description Documentation

Task 1: Define The Oracle Fusion system is predefined

Define Common Order Orchestration Configuration chapter
source systems with code = OPS. Define the source
systems for your order capture and
• Manage Customers: Define Source Systems
fulfillment systems.
section
Go to the Manage Trading Community
Source Systems task. o Source Systems: Explained

Create each source system and enable

each system for order orchestration and
planning. This step registers the source
systems. In a later step you must allow
collections for each of these systems. If a
system will be a source for customer
information, you must also enable the
system for customers.

Task 2: Import
Use the import process to import a batch
customers Define Common Order Orchestration Configuration chapter
from the interface tables into the Trading
Community Model registry. The batch you • Define Common SCM Configuration: Manage SCM
import must include the customers that Common Customers section
your test orders will reference.
o Defining the Import Process for
Go to the Import Person and Customers and Consumers: Points to
Organization task. On the Data Consider
Import Batches Overview page, click o Defining the Import Process for
on the Create Data Import Batch task Customers and Consumers: Worked
located in the task pane. Example

After creating the import batch, load your

data into the interface tables using a
standard Extract, Transform, and Load
(ETL) tool.

Table 4: Collecting Data

Oracle Fusion Distributed Order Orchestration references units of measure, currency, and currency
conversions directly from the order orchestration and planning data repository. Before you can receive
orders, you must perform the tasks in this table to collect data for these entities. Global Order Promising
sourcing rules reference the Organization Parameter entity. Before you can define sourcing rules, you
must collect Organization Parameters.

The documentation in this table is found in the Oracle Fusion Applications Order Orchestration
Implementation Guide.

7
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Tasks Description Documentation

Task 1: Manage Specify details for your Oracle Fusion system,

Define Order Promising chapter
Planning Source for the order capture source systems that
Systems your test orders will reference, and for your
• Manage Planning Source Systems section
fulfillment systems.
Go to the Manage Planning Source o Managing Data Collection Source
Systems task. Systems: Explained
First, select your Oracle Fusion system and
carefully set the version equal to Fusion,
select collections allowed, and enable data
cross-referencing. Before saving, verify that
the version equals Fusion and type equals
Order Orchestration.
For the order capture source systems and
your fulfillment systems, set the version
equal to Others, specify collections allowed,
and enable data cross-referencing.

Task 2: Manage Enable the Currencies and Units of Measure

Collect Order Promising Reference and Transaction
Planning Data entities for cross-referencing.
Data chapter
Collection processes
Go to the Manage Planning Data • Manage Planning Data Collection
Collection Processes task. Processes
Collect Order Promising Reference and Transaction
Task 3: Collect You must collect the Organization Parameters
Data chapter
Organization entity for item organizations from your
Parameters external source systems. In your collected
• Data Collection Methods for External
data, your organizations will be identified
Source Systems: Explained
with the source system concatenated to the
organization ID. Other entities, such as
Sourcing Rules, will use this combined ID.
You may collect this data by using web
services uploads or by loading the data into
staging tables and launching the scheduled
process named Perform Data Load from
Staging Tables.
Verify the collected data in the Review
Planning Collected Data page.

8
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Tasks Description Documentation

Task 4: Collect You must collect UOMs, currencies, and

Collect Order Promising Reference and Transaction
UOM, Calendar, currency conversions from your order capture
Data chapter
Currency, and systems. When submitting orders from your
Currency Conversion order capture system, Order Orchestration
• Data Collections, Order Orchestration,
Data validates UOM and currencies against data
and Order Promising: How They Fit
previously collected from your order capture
Together
system.
You must collect calendars from your fulfillment • Collecting Data for the Order
systems. Calendars specify when a facility, such Orchestration and Planning Data
as a warehouse, is open. This is also known as Repository: Explained
on/off days, which is used for scheduling.
• Data Collection Methods for External
You may collect data from an external source Source Systems: Explained
system by using web services uploads or by
loading the data into staging tables and
launching the scheduled process named
Note: While reference data can be collected from
Perform Data Load from Staging Tables.
multiple systems, because reference data entities
Verify the collected data in the Review are global objects, the last data collected is the
Orchestration Collected Data or in the Review data used by Order Orchestration and Global
Planning Collected Data pages. Order Promising. Decide which source system
contains the master data list and collect from it
Note: The pilot implementation expects your last. For example, if the Oracle Fusion source
test orders to use the same values for UOM, system contains the master list of currencies,
currency, and currency conversion that you collect currencies from the order capture system
collect into the data repository. When first to enable cross-referencing of currencies for
performing a full implementation, if your that system, and then collect currencies from the
different order capture systems use different Oracle Fusion source system last.
values for these entities, then you must
perform additional implementation steps. For Note: Collecting shipping methods is required if
example, if one order capture system uses Ea order promising needs to consider the transit lead
for each, whereas another order capture time between ship-from warehouses to
system uses Each for each, then you must destinations. If shipping methods are not
perform additional steps to fully enable data specified, a lead time of zero days is assumed.
cross-referencing.

Table 5: Enabling Global Order Promising

Oracle Fusion Global Order Promising uses sourcing rules, assignment sets, and ATP Rules when
determining availability.

The documentation in this table is found in the Oracle Fusion Applications Order Orchestration
Implementation Guide.

9
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Tasks Description Documentation

Sourcing Rules determine possible supply Define Order Promising chapter
Task 1: Manage Sourcing
sources.
Rules • Manage Sourcing Rules and Bills of
Go to the Manage Sourcing Rules Distribution section
task.

Create a global sourcing rule that

transfers from an organization you
created to represent a warehouse.
Assignment Sets determine which Define Order Promising chapter
Task 2: Manage
sourcing rules are used for which items.
Assignment Sets • Manage Assignment Sets section
Go to the Manage Assignment Sets
task.
Create an assignment set that assigns
the sourcing rule you created to the
Global assignment level.
The assignment set profile option
Task 3: Manage
determines which assignment set is used
Administrator Profile
when Global Order Promising determines
Values
availability.
Go to the Manage Administrator
Profile Values task
In the Application field, select Global
Order Promising from the choice list, and
then search. Set the profile value of the
MSP_DEFAULT_ASSIGNMENT_SET to the
sourcing rule you created.
Available-to-Promise rules determine the Manage Order Promising Rules chapter
Task 4: Manage ATP
mode used for determining order
Rules • Manage ATP Rules section
promising.
Go to the Manage ATP Rules task.

Create an ATP rule that uses the Infinite-

Availability-Based promising mode.
Assign the ATP rule to each of the
organizations you created for your
fulfillment warehouses.

Table 6: Performing Order Orchestration Setup Tasks

The Oracle Fusion Distributed Order Orchestration architecture is situated between one or more order
capture systems and one or more fulfillment systems. You must perform tasks in the Define Sales Order
Fulfillment task list to set up the connections to these systems and to deploy the predefined data that
define default processing of an order by Distributed Order Orchestration.

The documentation in this table is found in the Oracle Fusion Applications Order Orchestration
Implementation Guide unless otherwise noted.

10
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Tasks Description Documentation

Go to the Manage Orchestration Define Sales Order Fulfillment chapter
Task 1: Manage
Profiles task.
Orchestration Profiles • Orchestration Profile Management:
Define values for the two profile options Points to Consider
with these profile display names:
• Display Currency
• Currency Conversion Type

Go to the Manage Orchestration Define Sales Order Fulfillment chapter

Task 2: Generate and
Process Definitions task.
Deploy Orchestration • Define Orchestration section
Process Download the Orchestration Process
o Orchestration Process
Definition:
Definition Deployment:
• On the Manage Orchestration Explained
Process Definitions page, search for
An example SOA Configuration Plan is
process name
presented in the implementation guide.
ShipOrderGenericProcess.
For more information about deploying SOA
• In the Search Results region, click
composite applications, see Oracle Fusion
the Edit icon.
Middleware Administrator's Guide for Oracle
• From the Actions menu on the Edit SOA Suite and Oracle Business Process
Orchestration Process Definitions Management Suite.
page, select Regenerate
Orchestration Process.
• In the Download Generated Process
window, click Download and save
the archive file that appears to a
local directory.
• Open the archive file in a local
directory. Note: The JAR file is
located in a Deploy folder within a
folder bearing the name of the
orchestration process that you
downloaded.
Modify the SOA Configuration Plan:
• Replace the host names and ports
with your organization's distributed
order orchestration ADF server and
port and SOA server and port. Use
the external-facing URLs of the
servers.
• The configuration plan enables you
to define the URL and property
values to use in different
environments. During process
deployment, the configuration plan
is used to search the SOA project
for values that must be replaced to
adapt the project to the next target
environment.
Deploy the JAR File:
• Use any of the following: Oracle
Enterprise Manager Fusion

11
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Tasks Description Documentation

Middleware Control, any command
line tool, or Oracle WebLogic
Scripting Tool.
Constraints contain business logic that Define Sales Order Fulfillment chapter
Task 3: Generate
affects what transactions are allowed
Constraint Package • Define Processing Constraints
under specified circumstances. You may
section
optionally create your own constraints.
Required constraints are provided, but o Define Processing
must be applied as part of initial setup. Constraints: Overview
This is called generating the constraint
package. o Using Processing
Constraints: Examples
Go to the Generate Constraint
Package task. o Creating Processing
Constraints: Worked
• On the Manage Processing Example
Constraints page, select the
Validation Rule Set tab.
• Click the Generate Constraints
Package action at the top of the
page.
• A message will be displayed that
the job has been submitted.
• Click OK.

Table 7: Preparing to Run Test Orders

You have performed the minimum implementation steps required to receive and fulfill test orders using an
infinite-availability ATP rule. You are now ready to perform the final steps needed to run a test order.

The documentation in this table is found in the Oracle Fusion Applications Order Orchestration
Implementation Guide.

Tasks Description Documentation

Contact Oracle Support to receive access
Task 1: Configure XForm
to the XForm for Order Simulation and
for Order Simulation
instructions on how to use it.
To refresh the Global Order Promising Define Sales Order Fulfillment chapter
Task 2: Refresh the
data store, complete these steps:
Order Promising Data • Collect Orchestration Reference
Store • Navigate to the Schedule New and Transaction Data section
Process page by following this
o Refreshing the Global
navigation path: Navigator>>
Order Promising Engine:
Tools>> Scheduled Processes>>
Explained
Actions>> Schedule New Process.
• In the popup window, select Job for
the type, then search for and select
the process named
RefreshOpDatastore. Click OK.

12
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Tasks Description Documentation

• Select all of the entities and submit
the job. You must select all of the
entities the first time you refresh
the order promising data store even
though you have not collected data
for all of the entities.
Use Oracle Enterprise Manager to start Define Sales Order Fulfillment chapter
Task 3: Start the Order
the Global Order Promising server.
Promising Server • Collect Orchestration Reference
and Transaction Data section
o Refreshing the Global
Order Promising Engine:
Explained
Submit a test order using the XForm.
Task 4: Submit Orders
From the Order Orchestration work area,
search for the submitted order by its
source order number. Confirm that the
order has been received and that
processing is under way.

13
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Appendix
The following task lists and tasks are specified in this quick start guide or in other guides that this quick
start guide references. The task lists and tasks included in an offering can vary from one release to the
next. If any of the tasks in the following table do not appear in your implementation project, then you can
navigate to the Setup and Maintenance work area and search for the task.

Level Type Name

1 Task List Order Orchestration Top Task List

2 Task List Define Common Applications Configuration for Order Orchestration

3 Task List Define Synchronization of Users and Roles from LDAP

4 Task Run User and Roles Synchronization Process

3 Task List Define Implementation Users

4 Task Create Implementation Users

4 Task Create Data Role for Implementation Users

4 Task Provision Roles to Implementation Users

3 Task List Define Enterprise Structures for Order Orchestration

4 Task List Define Initial Configuration

5 Task Establish Enterprise Structures

4 Task List Define Reference Data Sharing

5 Task Provision Roles to Implementation Users

4 Task List Define Geographies

5 Task Manage Geographies

4 Task List Define Enterprise for Order Orchestration

5 Task Manage Locations

4 Task List Define Business Units for Order Orchestration

5 Task Manage Business Unit

4 Task List Define Facilities for Order Orchestration

5 Task Manage Item Organizations

3 Task List Define Security for Supply Chain Management

14
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Level Type Name

4 Task List Define Users for Supply Chain Management

5 Task Manage Users

2 Task List Define Common Order Orchestration Configuration

3 Task Manage Units of Measure

3 Task Manage Lifecycle Phases

3 Task Manage Default Item Classes

3 Task Manage Product Value Sets

3 Task Manage Key Flexfield for Catalogs (release 5 and prior)

3 Task Create Catalog (release 5 and prior)

3 Task Manage Default Catalogs (release 5 and prior)

3 Task Import Items

3 Task Monitor Item Imports

3 Task List Manage Customers

4 Task List Define Source Systems

5 Task Manage Trading Community Source Systems

4 Task Import Person and Organization

2 Task List Define Order Promising

3 Task Manage Planning Source Systems

3 Task Manage Sourcing Rules

3 Task Manage Assignment Sets

Manage Administrator Profile Values

3 Task
(Instead of Manage Global Order Promising Profile Options)

2 Task List Collect Order Promising Reference and Transaction Data

3 Task Manage Planning Data Collection Processes

3 Task Review Planning Collected Data

2 Task List Manage Order Promising Rules

3 Task Manage ATP Rules

2 Task List Define Sales Order Fulfillment

15
 Oracle Fusion Applications Setting Up Order Orchestration: Quick Start

Level Type Name

3 Task Manage Orchestration Profiles

3 Task List Define Orchestration

4 Task Manage Orchestration Process Definitions

3 Task List Define Processing Constraints

4 Task Generate Constraint Package

16
Oracle Fusion Applications
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the
Setting Up Order Orcehstration: Quick Start
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
March 2013
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are
Oracle Corporation
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
World Headquarters
means, electronic or mechanical, for any purpose, without our prior written permission.
500 Oracle Parkway
Redwood Shores, CA 94065
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
U.S.A.
owners.

Worldwide Inquiries:
AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel
Phone: +1.650.506.7000
and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are
Fax: +1.650.506.7200
trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open
[Link]
Company, Ltd. 0410