Skip Headers

Contents

1 Overview

This chapter contains the following:

Order Orchestration Offering: Overview

Getting Started with an Implementation: Overview

Manage Application Implementation

Order Orchestration Offering: Overview

By implementing the Order Orchestration offering, your enterprise can set up order fulfillment to reflect operating practices, improve effectiveness and consistency of business processes, and enforce corporate compliance.

Before you begin, use the Getting Started page in the Setup and Maintenance work area to access reports for each offering, including full lists of setup tasks, descriptions of the options and features that you can select when you configure the offering, and lists of business objects and enterprise applications that are associated with the offering.

The first implementation step is to configure the offerings in the Setup and Maintenance work area by selecting the offerings and options that you want to make available to implement. For the Order Orchestration offering, you can select the following options:

Order Orchestration (this option also has associated features that you can select to configure)
Supply Chain and Order Management Business Intelligence Analytics
Order Management Business Intelligence Analytics
Logistics Business Intelligence Analytics

Next, create one or more implementation projects for the offerings and options that you want to implement first, which generates task lists for each project. The application implementation manager can customize the task list and assign and track each task.

If you select all of the options, then the generated task list for this offering contains the following groups of tasks:

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
Define Transactional Business Intelligence Configuration
Define Extensions for Order Orchestration

Define Common Applications Configuration for Order Orchestration

Use this task list to manage definitions that are used across offerings, which typically apply to multiple products and product families. These definitions include enterprise structures, workforce profiles, security, and approval rules, among others.

You can find other information that supports the common implementation tasks in the Oracle Fusion Applications Concepts Guide.

Define Common Order Orchestration Configuration

Use this task list to define the configuration for common setup, such as units of measure and catalogs for Oracle Fusion Distributed Order Orchestration.

Define Order Promising

Use this task list to enable order promising by defining specific supply sources and the data that needs to be collected from each source, and assigning sourcing rules or rule sets to items in order to select the correct source organization from one of the fulfillment source systems in your supply chain.

Collect Order Promising Reference and Transaction Data

Use this task list to define collection of supply data from multiple sources, including inventory and planning systems, and to define supply update frequency across supply sources.

Manage Order Promising Rules

Use this task list to define order promising rules for items by customer and location, the method used to allocate supply across classes of demand, and the priority and sequence of supply sources to check for supply when there are multiple sources for an item.

Define Sales Order Fulfillment

Use this task list to configure decomposition rules, orchestration processes, planning and jeopardy conditions, and change order logic. You can also define holds, constraints, and status, and register new services and integration targets.

Define Transactional Business Intelligence Configuration

Use this task list to configure Oracle Transactional Business Intelligence for ad hoc reporting, including managing the repository, connections, presentation catalog, and currency type display.

Define Extensions for Order Orchestration

Use this task list to define extensions, such as custom Oracle Enterprise Scheduler jobs.

You can also customize and extend applications using other tools. For more information, see the Oracle Fusion Applications Extensibility Guide.

Getting Started with an Implementation: Overview

To start an Oracle Fusion Applications implementation, you must setup one or more initial users using the super user that was created during installation and provisioning of the Oracle Fusion Applications environment. Because Oracle Fusion Applications is secure as delivered, the process of enabling the necessary setup access for initial users requires several specialized steps when getting started with an implementation.

The following high level steps are required for starting an implementation.

As the Oracle Identity Management Administration user, provision the IT Security Manager job role with roles for user and role management.
This step enables the super user account, which is provisioned with the IT Security Manager job role, to create implementation users.
As the Oracle Fusion Applications installation super user, perform the following tasks once you have selected an offering to implement and generated the setup tasks needed to implement the offering.
1. Synchronize users and roles in the Lightweight Directory Access Protocol (LDAP) store with HCM user management by using the Run User and Roles Synchronization Process task.
2. Create an IT security manager user by using the Create Implementation Users task.
3. Provision the IT security manager with the IT Security Manager role by using the Provision Roles to Implementation Users task.
As the newly created IT security manager user, sign in to Oracle Fusion Applications and set up at least one implementation user for setting up enterprise structures.
1. Create an implementation user by using the Create Implementation Users task.
2. Provision the implementation user with the Application Implementation Manager job role or the Application Implementation Consultant job role by using the Provision Roles to Implementation Users task. The Application Implementation Consultant job role inherits from all product-specific application administrators and entitles the necessary View All access to all secured object.
3. Optionally, create a data role for an implementation user who needs only the limited access of a product-specific Application Administrator by using the Create Data Role for Implementation Users. Then assign the resulting data role to the implementation user by using the Provision Roles to Implementation Users task.

The figure shows the task flow from provisioning the IT Security Manager job role with the user and role management entitlement to creating and provisioning implementation users for enterprise setup.

Three swim lanes for the OIM Administrator
user, the installation super user, and the IT Security Manager or
Security Administrator user, if available, show the tasks each type
of user performs to create and provision one or more implementation
users for setting up enterprise structures.

Manage Application Implementation

Manage Application Implementation: Overview

The Manage Applications Implementation business process enables rapid and efficient planning, configuration, implementation, deployment, and ongoing maintenance of Oracle Fusion applications through self-service administration.

The Setup and Maintenance work area offers you the following benefits:

Prepackaged lists of implementation tasks
Task lists can be easily configured and extended to better fit with business requirements. Auto-generated, sequential task lists include prerequisites and address dependencies to give full visibility to end-to-end setup requirements of Oracle Fusion applications.
Rapid start
Specific implementations can become templates to facilitate reuse and rapid-start of consistent Oracle Fusion applications setup across many instances.
Comprehensive reporting
A set of built-in reports helps to analyze, validate and audit configurations, implementations, and setup data of Oracle Fusion applications.

With Oracle Fusion Functional Setup Manager you can:

Learn about and analyze implementation requirements.
Configure Oracle Fusion applications to match your business needs.
Get complete visibility to setup requirements through guided, sequential task lists downloadable into Excel for project planning.
Enter setup data through easy-to-use user interfaces available directly from the task lists.
Export and import data from one instance to another for rapid setup.
Validate setup by reviewing setup data reports.
Implement all Oracle Fusion applications through a standard and consistent process.

There are several documentation resources available for learning how to configure Oracle Fusion Applications.

Information Technology Management, Implement Applications Developer Guide
Common Implementation Guide
Customer Data Management Implementation Guide
Enterprise Contracts Implementation Guide
Marketing Implementation Guide
Sales Implementation Guide
Fusion Accounting Hub Implementation Guide
Financials Implementation Guide
Compensation Management Implementation Guide
Workforce Deployment Implementation Guide
Workforce Development Implementation Guide
Incentive Compensation Implementation Guide
Procurement Implementation Guide
P6 EPPM Administrator's Guide for an Oracle Database
P6 EPPM Administrator's Guide for MicroSoft SQL Server Database

Implementation Projects: Explained

An implementation project is the list of setup tasks you need to complete to implement selected offerings and options. You create a project by selecting the offerings and options you want to implement together. You manage the project as a unit throughout the implementation lifecycle. You can assign these tasks to users and track their completion using the included project management tools.

Maintaining Setup Data

You can also create an implementation project to maintain the setup of specific business processes and activities. In this case, you select specific setup task lists and tasks

Exporting and Importing

Implementation projects are also the foundation for setup export and import. You use them to identify which business objects, and consequently setup data, you will export or import and in which order.

Selecting Offerings

When creating an implementation project you see the list of offerings and options that are configured for implementation. Implementation managers specify which of those offerings and options to include in an implementation project. There are no hard and fast rules for how many offerings you should include in one implementation project. The implementation manager should decide based on how they plan to manage their implementations. For example, if you will implement and deploy different offerings at different times, then having separate implementation projects will make it easier to manage the implementation life cycles. Furthermore, the more offerings you included in an implementation project, the bigger the generated task list will be. This is because the implementation task list includes all setup tasks needed to implement all included offerings. Alternatively, segmenting into multiple implementation projects makes the process easier to manage.

Offerings: Explained

Offerings are application solution sets representing one or more business processes and activities that you typically provision and implement as a unit. They are, therefore, the primary drivers of functional setup of Oracle Fusion applications. Some of the examples of offerings are Financials, Procurement, Sales, Marketing, Order Orchestration, and Workforce Deployment. An offering may have one or more options or feature choices.

Implementation Task Lists

The configuration of the offerings will determine how the list of setup tasks is generated during the implementation phase. Only the setup tasks needed to implement the selected offerings, options and features will be included in the task list, giving you a targeted, clutter-free task list necessary to meet your implementation requirements.

Enabling Offerings

Offerings and their options are presented in an expandable and collapsible hierarchy to facilitate progressive decision making when specifying whether or not an enterprise plans to implement them. An offering or its options can either be selected or not be selected for implementation. Implementation managers decide which offerings to enable.

Provisioning Offerings

The Provisioned column on the Configure Offerings page shows whether or not an offering is provisioned. While you are not prevented from configuring offerings that have not been provisioned, ultimately the users are not able to perform the tasks needed to enter setup data for those offerings until appropriate enterprise applications (Java EE applications) are provisioned and their location (end point URLs) is registered.

Options: Explained

Each offering in general includes a set of standard functionality and a set of optional modules, which are called options. For example, in addition to standard Opportunity Management, the Sales offering includes optional functionality such as Sales Catalog, Sales Forecasting, Sales Prediction Engine, and Outlook Integration. These optional functions may not be relevant to all application implementations. Because these are subprocesses within an offering, you do not always implement options that are not core to the standard transactions of the offering.

Feature Choices: Explained

Offerings include optional or alternative business rules or processes called feature choices. You make feature selections according to your business requirements to get the best fit with the offering. If the selected offerings and options have dependent features then those features are applicable when you implement the corresponding offering or option. In general, the features are set with a default configuration based on their typical usage in most implementations. However, you should always review the available feature choices for their selected offerings and options and configure them as appropriate for the implementation.

You can configure feature choices in three different ways:

Yes or No

If a feature can either be applicable or not be applicable to an implementation, a single checkbox is presented for selection. Check or uncheck to specify yes or no respectively.

Single Select

If a feature has multiple choices but only one can be applicable to an implementation, multiple choices are presented as radio buttons. You can turn on only one of those choices.

Multi-Select

If the feature has multiple choices but one or more can be applicable to an implementation then all choices are presented with a checkbox. Select all that apply by checking the appropriate choices.