This chapter contains the following:

Common Implementation: Overview

Common implementation involves performing setup tasks that are common and available within multiple offerings. The Application Extensions, Transactional Business Intelligence, and other functional areas comprise these common setup and implementation tasks.

Application Extensions

Use the Application Extensions functional area to configure common business objects. For example, this functional area comprises tasks that help you to:

  • Set options for the help features available at the site, which might include access to external web sites, and settings for creating and editing help content.

  • Review and manage objects, for example currencies and reference data sets that are shared across applications.

  • Configure common reference objects such as flexfields, document sequences, and profile options that affect the functionality and look of Oracle Applications Cloud.

Transactional Business Intelligence

Use the Transactional Business Intelligence functional area to configure business intelligence and gain real-time insight into transactional data. You can also secure the transactional data and manage the users accessing that data.

Other Functional Areas

Other functional areas contain several tasks to manage common functions that apply to the entire implementation. Examples of such functional areas include Legal Structures, Users and Security, and Enterprise Profile. Use these functional areas to, for example:

  • Set up security, enterprise structures, geographies, and business units.

  • Create and maintain user accounts and synchronize the list of users and roles stored in Lightweight Directory Access Protocol (LDAP).

Understanding Implementation Structures

Functional Setup Manager: Overview

Oracle Functional Setup Manager provides an integrated, end-to-end process for functional administrators to manage the implementation and maintenance of Oracle Applications Cloud.

Functional Setup Manager offers the following:

  • Standardized application configuration and setup experience

  • Feature opt-in for a best fit configuration

  • Flexible processes for managing setup:

    • Setup by functional areas for an adopt-as-you-go approach

    • Implementation projects to manage setup

    • Upload file to enter setup data in bulk

  • Guided task list for end-to-end setup requirements

  • Export and import services for setup data migration between environments

  • Comprehensive reporting on setup data

Who Uses the Functional Setup Manager: Points to Consider

Business users who are responsible for configuring feature opt-in and managing setup data are the primary users of Functional Setup Manager.

Security Access

The Application Implementation Consultant job role has full access to perform all Functional Setup Manager-related activities. Other user must include the Functional Setups User role in addition to other roles or privileges needed to perform specific setup activities.

For more detailed information about security requirements for Functional Setup Manager, refer to the Oracle Applications Cloud Security Reference for Common Features guide in the All Books for Oracle Cloud page of the Oracle Help Center (docs.oracle.com).

Functional Setup Manager Components: How They Work Together

Offerings, functional areas, features, and setup tasks work together in your implementation.


An offering represents a collection of business processes that are supported by Oracle Applications Cloud. Each subscription of Oracle Cloud provides license to use one or more offerings and they are the starting point of all implementations. An offering consists of multiple functional areas and features.

Functional Areas

A functional area represents one or more business subprocesses and activities within its parent offering. It may represent a core operation of the offering or may represent an optional activity which may or may not be applicable to your business. When you start to implement an offering by enabling it, core functional areas are enabled automatically. You have a choice to opt into and enable an optional functional area or to opt out of it. A functional area may be divided into smaller functional areas creating a hierarchy to help you to decide what to opt into one step at a time. Some of the functional areas may be applicable to more than one offering. Once you set up a shared functional area, you do not have to set it up again when implementing another parent offering. However, Oracle recommends that during successive implementation of the other parents you verify if there are any offering-specific tasks that may still require your attention.


Features are optional business practices or methods applicable to the functional areas. Like functional areas, you can decide to opt into or opt out of features depending on the requirements of your business processes. Features can be one of three different types:

  • Yes or No: These features allow you either to opt into or to opt out of them and are represented by a single check box. You select them to opt into or deselect them to opt out.

  • Single Choice: These features offer multiple choices but allow you to select only one option. Select the option applicable to your business processes.

  • Multi-Choice: These features offer multiple choices but allow you to select more than one of the choices. Each choice is presented with a check box. Select all that apply to your business processes by checking the appropriate choices.

Setup Tasks

Setup tasks represent the work necessary to set up an offering and the business processes and activities that the offering represents to make them ready for transaction processing. Perform these tasks to enter setup data when you implement an offering.

Tasks representing setup requirements of the offerings and the functional areas are grouped into task lists and are organized in a hierarchy. For example, all setup tasks of an offering are grouped into a task list which includes subtask lists that represent setup of functional areas within the offering. This helps you gain visibility into setup data that are related to each other, helping you to manage setup.

Functional Setup Manager Work Areas: How They Work Together

Use the My Enterprise and Setup and Maintenance work areas to manage feature opt-in and setup of your subscribed offerings.

My Enterprise Work Area Group

The following work areas are part of My Enterprise:

  • Offerings: This work area shows all available offerings. Review and opt into your subscribed offerings when you are ready to implement. Oracle Applications Cloud are available for use only after the relevant offerings and their related features are opted into by enabling them. This helps you to configure Oracle Applications Cloud according to what your enterprise needs to use and exclude any irrelevant features. Get started by reviewing the description of the offerings and the related documents, which helps you to determine what features to opt into and how to plan for implementation.

  • New Features: This work area highlights the new features that have been introduced in the latest release version to give more visibility to what is new in Oracle Applications Cloud. After upgrade, review this page to get a quick view of the newly introduced features and to decide whether to opt into any of them.

  • Enterprise: This work area allows you to enter your enterprise-specific information related to your Oracle Applications Cloud.

  • Subscriptions: This work area shows your subscriptions for Oracle Applications Cloud.

Setup and Maintenance Work Area

The Setup and Maintenance work area is for managing setup data required by Oracle Applications Cloud. After you opt into and enable one or more offerings in the Offerings work area, use this work area to manage setup.

Implementation Process: Explained

A functional implementation of Oracle Applications Cloud typically includes the following steps.

  • Plan

  • Configure

  • Setup

  • Deploy

  • Maintain


Identify the offerings you want to implement. Evaluate what functional areas and features to opt into and prepare accordingly for their setup requirements.

For more detailed information, refer to the Planning an Implementation chapter in the Using Functional Setup Manager guide.


Opt into the offerings, functional areas, and features that best fit your business requirements by enabling them.

For more detailed information, refer to the Configuring Offerings chapter in the Using Functional Setup Manager guide.


Use setup tasks to enter setup data necessary for your enabled offerings and functional areas. Typically, you set up and verify your transaction processes in a test environment before starting to transact in a production environment.

For more detailed information, refer to the following chapters in the Using Functional Setup Manager guide:

  • Managing Offering Setup

  • Managing Setup Using Implementation Projects

  • Managing Setup Using Alternative Processes


Move your verified setup data from the test environment to a production environment and deploy to all users to start transaction processing.

For more detailed information, refer to the Exporting and Importing Setup Data chapter in the Using Functional Setup Manager guide.


Update setup data or opt into configuration of the functional areas and features as necessary when your business requirements change over time.

Managing an Implementation

Enabling Offerings: Explained

Offerings and their functional areas are presented in an expandable and collapsible hierarchy to facilitate progressive decision making regarding whether or not you want to implement them. An offering or its functional areas can either be opted into or not opted into for implementation. Implementation managers decide which offerings to enable for implementation. Although all of the functional areas that represent core functionality of an offering are automatically enabled for implementation when a parent offering is enabled for implementation, you can select which of the optional functional areas are enabled. You can identify which functionality is already opted into by looking at the check box in the Enable column.

Configuring Offerings: Procedure

Enable offerings to modify functionality so that it matches the services you plan to implement.

Enable Offerings

To enable offerings, follow these steps:

  1. Select Navigator > My Enterprise > Offerings work area to open the Offerings page. You need the Configure Oracle Fusion Applications Offering privilege.

  2. Select the offering you want to implement.

  3. Click Opt In Features button to go to the Opt In page.

  4. In the Opt In page, select the Enable check box for the offering.

  5. Review functional area hierarchy. Select the Enable check box to opt into functional areas as applicable to your business operations.

  6. Click the Edit icon in the Features column for the functional area you enabled to opt into and enable applicable features.

    • Depending on the feature type, a check box for Yes or No features or an Edit icon for single and multiple choice features is displayed in the Enable column.

    • To enable a feature, select the check box for Yes or No types or click Edit and select the appropriate choices for single and multiple choice features.

  7. Click Done when you're finished to return to the Opt In page.

  8. Click Done to return to the Offerings page.

Repeat the same steps for each offering you want to implement or if you must change the opt-in configuration of any functional areas or features of an enabled offering.

Adopting New Functionality: Explained

As your business needs change or expand, you may need to adopt new functionality not included in your initial implementation. You can adopt any new functionality for your subscribed offerings to satisfy your business needs. All functionality available for an offering is listed in the Opt In page whether or not you have opted into it. In order to opt into new functionality, make sure that its parent in the hierarchy is already selected. Additionally, Functional Setup Manager provides you easy access to learn more about any feature by clicking the feature's Help icon.

Opting into New Features After Upgrade: Explained

New functional areas and features for an offering you implemented are often introduced in the later revisions of Oracle Applications Cloud. You can use the New Features work area to explore and learn about what has been introduced in the last upgrade of your applications and decide whether to opt into them.

You can review the new functional areas and features of all your enabled offerings or focus on only one of them. For each functional area or feature, you can view its opt-in status, check whether it requires setup, and access additional help topics to learn more details.

Managing Offering Setup: Explained

After you enable an offering and configure the opt-in selection of its functional areas and features, you can set up the offering by using its functional areas as a guide. This adopt-as-you-go approach to functional setup gives you the flexibility to set up different functional areas of the offering at different times. For example, you can begin with setup of the functional areas you require immediately to start transactions. You can then set up other functional areas as you adopt additional offering functionality over time. This setup process is ideal for an enterprise looking for a simpler implementation approach that follows setup best-practices.

For example, you can begin with setup of the functional areas you require immediately to start transactions. You can then set up other functional areas as you adopt additional offering functionality over time. This setup process is ideal for an enterprise looking for a simpler implementation approach that follows setup best practices.

Functional Areas

When using this method, you start by selecting one of the offerings you enabled. Based on your opt-in configuration, all its enabled functional areas, which include core and optional functional areas, are automatically displayed in a list to guide you through the setup tasks. The display order reflects the sequence in which the functional areas should be set up because setup data of the functional areas listed higher up in the list are usually prerequisite for those shown lower in the list. Any functional area for which setup is mandatory is marked with an asterisk.

Functional areas that are applicable to more than one of your enabled offerings is marked as shared to allow you to evaluate whether they were previously set up during the implementation of another offering. Even if a shared functional area was set up previously, you may still need to evaluate if it requires additional setup data for the offering you are presently implementing.

For some functional areas, Quick Setup may be available to implement its basic functionality quickly. A Quick Setup icon next to a functional area indicates if Quick Setup is available. You can use this task instead of the setup task list to set up those functional areas.

Setup Tasks

For each functional area, a sequenced list of tasks representing the setup best practices according to your opt-in configuration of the features is shown to guide you through optimal implementation requirements. Use the tasks to enter the setup data they represent. Like functional areas, the display order of the tasks always reflects the sequence in which they should be performed to address setup data dependencies.

Required Tasks

Only the required setup tasks are shown by default to minimize your setup effort and to make the offering ready for transactions sooner. However, you can also review the rest of the tasks in the list, which are typically optional or have predefined default values based on common use cases, and decide whether your implementation must change their default setup data.

Tasks with Scope

If any setup data is segmented by a specific attribute or scope, you may need to perform the task iteratively. If so, you must select a qualifying scope value prior to performing the task. You can pick a scope value that was previously selected, select a new scope value, or create a new scope value and then select it. The selected value is a qualifying attribute of the setup data and therefore, different setup data can be entered for the different scope values.

Note: You cannot perform a task if you do not have the proper security privileges.