Applications Cloud Using Functional Setup Manager

Oracle
Applications Cloud
Using Functional Setup Manager
Release 13 (update 17D)

Oracle Applications Cloud
Release 13 (update 17D)

Part Number E89424-01
Copyright © 2011-2017, Oracle and/or its affiliates. All rights reserved.
Authors: Sandesh Posa, Mary Kalway
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by
intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to
us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the
following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/
or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation
and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating
system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions
applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in
any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle
Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of
Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle
Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any
loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement
between you and Oracle.
The business names used in this documentation are fictitious, and are not intended to identify any real companies currently or previously in existence.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/
pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
Preface i
1 Overview 1
Functional Setup Manager: Overview ........................................................................................................................ 1
Who Uses the Functional Setup Manager: Points to Consider .................................................................................. 1
Functional Setup Manager Components: How They Work Together ......................................................................... 1
Functional Setup Manager Work Areas: How They Work Together ........................................................................... 3
Implementation Process: Explained ........................................................................................................................... 3
2 Planning an Implementation 5
Planning Your Implementation: Explained .................................................................................................................. 5
Reviewing Your Subscription: Procedure .................................................................................................................. 5
Entering Promotion Codes: Procedure ...................................................................................................................... 5
Planning Your Implementation: Procedure ................................................................................................................ 5
3 Configuring Offerings 7
Configuring Offerings: Explained ............................................................................................................................... 7
Configuring Offerings: Procedure .............................................................................................................................. 7
Opting into New Features After Upgrade: Explained ................................................................................................. 8
Opting into New Features After Upgrade: Procedure ................................................................................................ 8
Reviewing Opt In History: Explained ......................................................................................................................... 9
Reviewing Opt In History: Procedure ........................................................................................................................ 9
4 Managing Offering Setup 11

Managing Offering Setup: Explained ....................................................................................................................... 11
Managing Offering Setup: Procedure ...................................................................................................................... 12
5 Managing Setup Using Implementation Projects 15

Managing Setup Using Implementation Projects: Explained .................................................................................... 15
Creating Implementation Projects: Procedure ......................................................................................................... 15
Modifying Implementation Projects: Procedure ........................................................................................................ 16
Assigning Setup Tasks: Explained .......................................................................................................................... 17
Assigning Setup Tasks: Procedure ......................................................................................................................... 17
Entering Setup Data Using Assigned Tasks: Explained ........................................................................................... 18
Entering Setup Data Using Assigned Tasks: Procedure .......................................................................................... 19
Monitoring Implementation Progress: Explained ...................................................................................................... 20
Monitoring Implementation Progress: Procedure ..................................................................................................... 21
FAQ's for Managing Setup Using Implementation Projects ..................................................................................... 22
6 Managing Setup Using Alternative Processes 25

Managing Setup Using Alternative Processes: Overview ......................................................................................... 25
Entering Setup Data Using CSV: Explained ............................................................................................................. 25
Exporting Setup Data to CSV: Procedure ............................................................................................................... 25
Copying Setup Configuration: Explained ................................................................................................................. 27
Copying Setup Configuration: Procedure ................................................................................................................ 28
Searching For A Task: Points To Consider ............................................................................................................. 29
Searching For A Task: Procedure ........................................................................................................................... 29
7 Exporting and Importing Setup Data: Overview 31

Exporting and Importing Setup Data: Overview ....................................................................................................... 31
Configuration Packages: Explained ......................................................................................................................... 31
Business Object Import Sequence: Explained ......................................................................................................... 32
Export Scope: Explained ......................................................................................................................................... 33
How Export Works: Explained ................................................................................................................................ 33
How Import Works: Explained ................................................................................................................................ 34
Export and Import: Best Practices .......................................................................................................................... 35
Incremental and Maintenance Data Import: Critical Choices .................................................................................... 37
Additional Access for Exporting and Importing Setup Data: Explained ..................................................................... 37
Concurrent Implementation Maintenance: Critical Choices ...................................................................................... 39
FAQs for Importing and Exporting Setup Data ........................................................................................................ 41
8 Exporting and Importing Offering Setup Data 45

Offering Based Export and Import: Explained ......................................................................................................... 45
Exporting Offering Setup: Procedure ....................................................................................................................... 45
Importing Offering Setup: Procedure ....................................................................................................................... 46
FAQ's for Exporting and Importing Offering Setup Data .......................................................................................... 48
9 Exporting and Importing Setup Data for Implementation Projects 51

Implementation Project Based Export and Import: Explained .................................................................................. 51
Modifying Configuration Packages: Points to Consider ........................................................................................... 52
Business Objects Marked as Scope Parameters: How They are Exported .............................................................. 52
Exporting Setup Data to Configuration Packages: Procedure .................................................................................. 53
Importing Setup Data from Configuration Packages: Procedure .............................................................................. 54
FAQ's for Exporting and Importing Setup Data for Implementation Projects ............................................................ 56
10 Comparing Setup Data 59

Comparing Setup Data: Understanding Setup Data Comparison ............................................................................ 59
Setup Data Comparison: Explained ........................................................................................................................ 59
Identifying Setup Data Changes Made Over Time for an Offering or Functional Area: Explained ............................... 60
Identifying Setup Data Changes Made Over Time for an Offering or Functional Area: Procedure .............................. 60
Comparing Setup Data for Implementation Projects: Explained ............................................................................... 61
Comparing Setup Data Using Configuration Packets: Procedure ............................................................................ 62
11 Reference 65
Reference: Moving Functional Setup Data Using the Command-Line ...................................................................... 65
Oracle Applications Cloud Preface
Preface
This preface introduces information sources that can help you use the application.
Oracle Applications Help

Use the help icon to access Oracle Applications Help in the application. If you don't see any help icons on your page,
click the Show Help icon in the global header. Not all pages have help icons. You can also access Oracle Applications
Help at https://fusionhelp.oracle.com.
Using Applications Help

Watch: This video tutorial shows you how to find help and use help features.

Additional Resources
• Community: Use Oracle Applications Customer Connect to get information from experts at Oracle, the
partner community, and other users.
• Guides and Videos: Go to the Oracle Help Center to find guides and videos.
• Training: Take courses on Oracle Cloud from Oracle University .
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at Oracle
Accessibility Program .
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=trs if you are hearing impaired.
Comments and Suggestions

Please give us feedback about Oracle Applications Help and guides! You can send e-mail to:
oracle_fusion_applications_help_ww_grp@oracle.com.
i
Oracle Applications Cloud Preface
ii
Oracle Applications Cloud Chapter 1
Using Functional Setup Manager Overview
1 Overview
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).
Related Topics
• Oracle Applications Cloud Security Reference for Common Features
1
Functional Setup Manager Components: How They Work

Together
Offerings, functional areas, features, and setup tasks work together in your implementation.
Offerings
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
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.
2
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
Plan
Identify the offerings you want to implement. Evaluate what functional areas and features to opt into and prepare accordingly
for their setup requirements.
3
For more detailed information, refer to the Planning an Implementation chapter in the Using Functional Setup Manager guide.
Configure
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.
Setup
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
Deploy
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.
Maintain
Update setup data or opt into configuration of the functional areas and features as necessary when your business
requirements change over time.
Related Topics
• Using Functional Setup Manager
4
Using Functional Setup Manager Planning an Implementation
2 Planning an Implementation
Planning Your Implementation: Explained

To plan for the implementation of your subscribed Oracle Applications Cloud, identify the offerings you need to implement.
Functional Setup Manager provides documentation to help you to understand the functionality and the setup requirements of
the offerings. Review those documents and then prepare the data you need to implement the relevant offerings.
Reviewing Your Subscription: Procedure

This procedure explains how to review your Oracle Cloud Applications subscription information.
You need the Configure Oracle Fusion Applications Offering privilege to perform this procedure.
To review your Oracle Cloud Applications subscription information, follow these steps:
1. Click Navigator > My Enterprise > Subscriptions work area to go the Review Subscriptions page.
2. Select Subscribed in the Show menu to view your licensed subscriptions or All to view all available subscriptions
for Oracle Cloud Applications.
Entering Promotion Codes: Procedure

This procedure explains how to enter a promotion code to activate a functional area or feature of an offering.
If you are given a promotion code to activate a functional area or feature of an offering, follow these steps to enter the
promotion code:
1. Click Navigator > My Enterprise > Subscriptions work area to go to the Review Subscriptions page.
2. Click the Enter Promotion Code button.
3. Enter the promotion code in the Enter Promotion Code dialog box and click Save and Close to return to the Review
Subscriptions page.
The promotion code you entered is now listed in the table.
5
Using Functional Setup Manager Planning an Implementation
Planning Your Implementation: Procedure

Use the Offerings page to learn about the opt-in configuration and the setup requirements of an offering.
Review Setup Information

To access and review setup information, follow these steps:
1. Select Navigator > My Enterprise > Offerings work area to open the Offerings page. You need the Review
Applications Offering privilege.
2. Explore the list and select the offering you want to implement. You can read the offering descriptions.
3. Click Related Documents to access the following information:
◦ Associated Features Report: This report shows the list of functional areas and features associated with the
offering.
◦ Setup Task Lists and Tasks Report: This report shows the list of task lists and tasks that you should complete
to successfully implement the offering.
◦ Related Business Objects Report: This report shows all setup data needed to implement the offering. It
provides a list of all business objects that are associated with the setup tasks belonging to the offering.
◦ Related Enterprise Applications Report: This report shows the list of enterprise applications used by the
functional pages and web services for the offering.
Related Topics
• Configuring Offerings
6
Using Functional Setup Manager Configuring Offerings
3 Configuring Offerings
Configuring Offerings: Explained

To configure an offering for implementation, you opt into its functional areas and features that are applicable to your business
operations. You start your opt-in configuration by enabling the offering. The offering and its functional areas are shown in a
hierarchy to help you decide, step-by-step, what to opt into. When an offering is enabled, all functional areas and features
representing core functionality of the offering are also automatically enabled. You decide which of the optional functional areas
and features to opt into by specifically enabling them.
After the initial implementation of the offering, if you must change the opt-in configuration to enable additional functional areas
or features at a later time, use the same procedure to enable them as well.
In some cases, opt-in selection of a functional area or a feature may be locked once enabled due to the business operation it
represents and its selection cannot be changed.
Configuring Offerings: Procedure

Video
Watch: This video tutorial shows you how to set up the offerings for initial use. The content of this video is also covered in text
topics.
Step-by-Step Process
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.
7
◦ 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.
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.
Opting into New Features After Upgrade: Procedure

Video
Watch: This video tutorial shows how to review and opt into new functional areas and features after Oracle Applications Cloud is
upgraded to a newer revision. The content of this video is also covered in text topics.
Use the New Features page to review and opt into new functional areas and features.
Opt In
To opt into new functional areas and features, follow these steps.
1. Select Navigator > My Enterprise > New Features to open the New Features page. You need the Review
Applications Offering privilege.
2. Select your enabled offering from the menu to review the new functional areas and features that became available in
the latest revision of the offering.
3. For each new functional area or feature:
◦ Use Learn More to find additional help topics.

◦ Check the Enabled column to view opt-in status. You find a check mark if it is already enabled.
◦ Consult the Requires Setup column to learn whether it requires setup and plan accordingly.
4. If you decide to opt into any functional area or feature, click the Opt In button. For a new functional area, open the
Opt In page. For a new feature, open the Edit Features page.
8
Note: You need the Configure Oracle Fusion Applications Offering privilege to perform this step.
5. Select the Enable check box, or in case of features with multiple choices, select the applicable choices.
6. When you are finished, click Done to return to the New Features page.
Reviewing Opt In History: Explained

Since opt in configuration directly influences behavior of setup and transactional processes, a history of all such changes is
maintained.
If you experience an unexpected change in the behavior of the application, you can review the opt in history to determine:
• Who made the changes
• When the changes were made
• How the opt-in selections changed
Reviewing Opt In History: Procedure

You can review change history of the opt in configuration using the Opt In History page.
Reviewing Opt In Change History

To review change history of the opt in configuration, follow these steps.
1. Click Navigator > My Enterprise > Offerings work area to open the Offerings page.
2. Select the offering whose opt in history you want to review.
3. Click the Opt In Features button to open the Opt In page.
4. In the Opt In page, click the View All History button to open the Opt In History page to view changes made to all
functional areas and features of an offering.
Note: Alternatively, click the View History icon corresponding to a specific functional area or feature
from the Opt In page or the Edit Features page. This displays the change history of that specific
functional area or feature respectively.
Review the Opt In History page for the following information:

• Name of the offering, functional area or feature whose opt in selection changed.
• Type, that is, whether it is an offering, functional area or a feature.
• Old value, that is, what the opt in selection was before the change.
• New value, that is, what the opt in selection changed to.
• User ID who made the change.
• Date and time of the change.
9
The page displays the most recent change first.
10
Using Functional Setup Manager Managing Offering Setup
4 Managing Offering Setup
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
11
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.
Managing Offering Setup: Procedure

Setting Up Offerings: Video
Watch: This video tutorial shows you how to create business data to set up the specific offering components you need for your
enterprise. The content of this video is also covered in text topics.
Setting Up Offerings with Scope: Video

Watch: This video tutorial shows you how to create business data for a specific version of a business object with scope. The
content of this video is also covered in text topics.
Use the Setup and Maintenance work area to directly implement an entire offering or the functional areas within an offering.
Set Up an Offering
To set up an offering using its functional areas, follow these steps.
1. Select Navigator > Setup and Maintenance work area to open the Setup page. You need the Functional Setups
User role.
2. Select the offering you want to implement.
3. Review the list of functional areas. If a functional area is not listed, you did not enable it when configuring the offering
opt-in. If you have access to configure application offerings, you can click Change Feature Opt In to open the Opt
In page. Follow the steps in the Configuring Offerings: Procedure topic to enable the functional area.
4. If you are setting up this offering for the first time, select the functional areas one at a time in the order they are listed.
If you are making changes to existing setup data, select the applicable functional area.
5. If Quick Setup is available for the functional area, then you can use Quick Setup to enter data instead of using the
related setup tasks. Click the icon and proceed.
Note: You need the Perform Quick Setup privilege to perform this step.
6. Select the first task in the list to open the page where setup data for the task is entered. If you are changing existing
setup data, go directly to the relevant task and select it.
12
Note: You need task-specific privileges to perform this step. 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) for more details on task-specific privilege requirements.
7. If the task requires a scope, select a scope value before you proceed. If you previously selected a scope value, then
that value is listed in the Scope column. Make sure it is the correct value and if needed, select a different value. You
can create a new value, select and add an existing value, or select one from the list of previously selected values.
Click Apply and Go to Task when you finished your selection.
Note: Unless you change it, the selected scope value is used for all tasks that use the same scope.
8. Enter setup data. When you finish, close the page, which returns you to the setup task list.
9. Continue to select other tasks from the list as needed and enter setup data for them.
13
14
Using Functional Setup Manager Managing Setup Using Implementation Projects
5 Managing Setup Using Implementation

Projects
Managing Setup Using Implementation Projects: Explained

An implementation project is a list of setup tasks you use to implement your Oracle Applications Cloud. Using this method,
you create an implementation project to generate a list of setup tasks, assign tasks to various users who are responsible for
managing setup data, and monitor progress of the completion of the setup tasks.
This method is best suited when you have a need to modify the default setup best practices, or manage setup as a project by
assigning responsibility of managing setup data to a broad group of users while monitoring their progress.
Generating a Task List

When you create an implementation project, typically you generate its initial list of tasks by selecting one of your enabled
offerings. If you plan to use more than one offering, create a separate implementation project for each one of them. In addition
to selecting an offering, which automatically selects its core functional areas, you may also select none, some, or all of the
optional functional areas of the offering that are also enabled. Using your selection of the offering and the functional areas as
a template, a task list hierarchy is generated for the implementation project. The task list hierarchy includes the tasks that are
associated at the time with your selected offering and functional areas, and their dependent features that are enabled.
Within the task list hierarchy, the tasks are organized according to prerequisite and dependency requirements of the setup
data that they represent. Oracle recommends that you enter setup data in the same sequence as the tasks to avoid errors
due to missing prerequisite data.
Modifying a Task List

Once you create an implementation project, you cannot modify its task list by selecting more functional areas to be included
in it. Similarly, if you change the opt-in configuration of the offering or the list of tasks associated with the selected functional
areas change, implementation project's task list will not reflect any of those changes. You have to create new implementation
projects to experience those changes.
You can, however, modify the task list hierarchy if needed by adding, removing, or reordering its tasks. If you modify the
task list hierarchy, you must consider and maintain prerequisite and dependency requirements. Otherwise your users will
encounter errors when using the implementation project either to enter setup data or to export and import setup data to a
different environment.
Any modification you make to an implementation project's task list is strictly applicable to that implementation project
only and doesn't affect any other projects with similar lists of tasks. Modifications to the task list don't affect setup data
represented by the tasks in the list. Once setup data is entered you cannot identify its source, such as which implementation
project or any other method was used to enter or update the data. Likewise, if you remove a task from an implementation
project, any setup data entered using the task continues to exist in the environment unless you explicitly delete the data using
an appropriate user interface.
15
Creating Implementation Projects: Procedure

Before creating an implementation project, make sure that the offering and the functional areas that you want to use as a
template are enabled.
Create an Implementation Project

To create an implementation project, follow these steps.
1. Select Navigator > Setup and Maintenance work area to open the Setup page. You need the Manage
Implementation Project privilege.
2. From the Setup page, open the panel drawer and select Manage Implementation Projects to open the Manage
Implementation Projects page.
3. Select Create from the actions menu or click the Create icon.
4. Enter a meaningful name and a brief description to describe your project.
5. Optionally, assign the project to a user and specify a start date.
6. Click Next. All offerings and functional areas that you previously enabled are listed.
7. Select the offering and its functional areas you want to use to generate the task list for this project.
8. Click Save and Open Project when you complete your selection.
9. The default task list for the implementation project is generated based on your offering and functional area selection
in the previous step. You can modify the task list if needed, and begin to assign the tasks to the appropriate users.
Modifying Implementation Projects: Procedure

The default task list generated for an implementation project is always organized in the proper sequence to address
prerequisite and dependency requirements of the setup data they represent. Oracle strongly recommends that you don't
modify the task list unless it's unavoidable because of your business requirements. If you add, remove, or reorder tasks within
an implementation project, you must ensure data dependency requirements aren't compromised.
Add Tasks
To add setup tasks to an implementation project, follow these steps.
1. Select Navigator > Setup and Maintenance work area to open the Setup page.
3. Open the implementation project you want to modify to view its task list hierarchy.
4. Select the task or task list you want to add the new task after and click the Add icon.
5. In the Add Task Lists and Tasks dialog window, search for the task or the task list you want to add, select it, and
then click Apply. Your selection will be added after the task or the task list you selected in the previous step.
6. Repeat search, select, and apply to add additional tasks or task lists if needed. Click Done when you have finished
to return to the implementation project.
7. Repeat the entire process if you need to add more tasks or task lists at other positions in the implementation task list
hierarchy.
16
Reorder Tasks
To reorder setup tasks of an implementation project, follow these steps.
4. Select the task you want to move.
5. Drag and drop the selected task on the task that you want it to appear after in the hierarchy.
You can follow the same steps to move a task list as well.
Remove Tasks
To remove setup tasks from an implementation project, follow these steps.
4. Select the task or the task list you want to remove.
5. Click the Remove icon. You are asked to confirm whether you want to remove the selected task or task list. If you
confirm, the task or the task list is removed from the task list hierarchy of the implementation project.
Note: When you remove a task any setup data entered using the task won't be removed.
Assigning Setup Tasks: Explained

You can assign the tasks of an implementation project to the users who are responsible for managing setup data represented
by those tasks. Typically, each setup task is assigned to a single individual. However, you may also assign multiple individuals
to the same task if your implementation project requires such assignment. Each of the individuals has the flexibility to perform
the task and manage setup data independently of the other users assigned to the same task.
If you specify due dates for completing the assigned tasks, it helps you monitor the progress of the task assignments and
monitor the progress of the overall implementation project. If you assign multiple people to a task, you can assign the same
due date to each person or you can assign a different due date to each assigned individual.
You can reassign tasks to a different user or specify a new due date at any time.
Note: If you assign a task list to a person, then they are assigned to all of the tasks included in the task list.
Assigning Setup Tasks: Procedure

This procedure explains how to assign setup task to functional users. After assigning setup tasks to a functional user, you
may reassign the task to another user, if necessary.
17
You need the Manage Implementation Project privilege to perform this procedure.
Initial Assignment
To assign setup tasks to functional users for the first time, follow these steps:
1. Click Navigator > Setup and Maintenance work area to go to the Setup page.
2. Select Manage Implementation Projects from the panel drawer.
3. In the Manage Implementation Projects page, open the implementation projects whose tasks you want to assign to
users.
4. Select one or more tasks or task lists from the task list hierarchy.
5. Click Assign Tasks to go to the Assign Tasks window.
6. Search and select one or more users to whom you want to assign your selected tasks or task lists and click Apply.
Selected users are added to the Assigned Users table in the Assign Tasks window.
7. Repeat search, select and apply to add additional users if needed. Click Done when you finish adding to return to
the Assign Tasks window.
8. To assign the same due date to all the assigned users, select the Assign same date check box.
9. To assign a different due date to each assigned user, click the Due Date column in the Assigned Users table and
select a due date for each assigned user.
10. Add notes for your assigned users, if necessary. Click Save and Close to return to the implementation project.
Reassignment
To reassign setup tasks from one user to another, follow these steps:
2. Select Manage Implementation Projects from the panel drawer.
3. Click Overview to go to the Implementation Projects: Overview page.
4. From the Assigned Users table, search and select the implementation project whose assignment you want to
change.
5. Click the Assignment Details tab in the Implementation Project Details region.
6. Search and select the task whose assignment you want to change and click Reassign Tasks to go to the Reassign
Tasks window.
7. Select the user to whom you want to reassign the task from the New User menu.
8. Select a new due date if necessary.
9. Click Save and Close to return to the Implementation Projects: Overview page.
10. Repeat the steps to reassign more tasks if necessary.
Entering Setup Data Using Assigned Tasks: Explained

If you are a user to whom setup tasks from an implementation project have been assigned, then a consolidated list of all of
your assigned tasks is presented to you. Use each task from the list to enter setup data that the task represents. If you have a
long list of assigned tasks, you can filter the list by due date, task status, or implementation project name to find a task more
easily. In addition, you can search for a specific task in the list by the task name.
Note: You must have the proper security privileges to perform a task.
18
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.
Predecessor Tasks
Some setup tasks may represent setup data that are a prerequisite for other setup data. These setup tasks are known as the
predecessor tasks.
Your assigned task list will indicate if any of the tasks has dependency on a predecessor task and will provide the following
information:
• Which tasks are the predecessors of a given task.

• What are the present statuses of the predecessor tasks.
• What statuses are recommended for each of the predecessor task before entering setup data.
Setting Task Status

By default the status of all assigned tasks are set to Not Started. When you start to enter data for a task, you can change
the task status to In Progress and when you finish entering data you can change it to Completed. Although status of a task
does not determine whether or not you can continue to enter setup data for the task or whether you can export and import
the data, it helps the implementation manager monitor the progress of the assignments.
Adding Notes
You can add a file, URL, or free-format text as notes to your assigned tasks. These notes are accessible not only to you,
but also to the implementation manager and other assignees if multiple users are assigned to the same task. This helps you
communicate and collaborate with others assignees.
Entering Setup Data Using Assigned Tasks: Procedure

Video
Watch: This video tutorial shows you how to enter setup data using Assigned Implementation Tasks. The content of this video is
also covered in text topics.
If you are a user to whom setup tasks from an implementation project have been assigned, then a consolidated list of all your
assigned tasks is presented to you. Use each task from the list to enter setup data that the task represents. If you have a long
19
list of assigned tasks, you can also filter the list by due date, task status or implementation project name to find a task more
easily. In addition you can search for a specific task in the list by the task name.
Note: You cannot perform a task if you do not have the proper security privileges.
To enter setup data using assigned tasks, follow these steps:

2. Select Assigned Implementation Tasks from the panel drawer to go to the Assigned Implementation Tasks page.
3. Find the task for which you want to enter data. Use filters if necessary to help you find the task.
4. Check if the task has dependencies on predecessor tasks. If so, check the statuses and recommended statuses for
the predecessor tasks.
5. Click Go to Task to go to the page for entering setup data for the task.
Note: You need task-specific privileges to perform this step. Refer to the Security Reference Guide for
more details on task-specific privilege requirements.
6. If the task requires a scope, then select a scope value. If you previously selected a scope value then that value is
listed in the Scope column. Verify that the correct scope value is selected and if needed, select a different value by
clicking it. You can Create a new value, Select and Add an existing value, or select one from the list of previously
selected values. Click Apply and Go to Task when you finish your selection.
Note: The selected scope value is used for all tasks that use the same scope unless you change it.
7. Enter the setup data. When you finish, close the page to return to the setup task list.
8. Click the icon in the Status column to change status
9. Click the number in the Notes column to add a note if necessary.
10. Select other tasks from the list and repeat the steps to enter setup data for them.
Monitoring Implementation Progress: Explained

Several graphical reports are available for you to monitor and analyze the progress of the assigned tasks in your
implementation project. You can drill down on the graphs on the Overview page to get all of the information you want to track
the progress of your project.
Assignment by Status
This pie chart shows the statuses of the assigned tasks as percentages of the total number of tasks in the implementation
project. The pie chart also shows the actual number of tasks with the specific status. The task statuses are predefined and
used to indicate the progress. The available statuses are as follows:
• Not Started
• In Progress
• Completed
• Execution Frozen
• Submitted
• Completed with Errors
• Completed with Warnings
20
Assignment by Due Dates

This stacked column graph shows the number of assignments with due dates in various predefined time periods, broken
down by different task statuses. Time periods are represented by columns while task statuses are represented by stacks
within each column. The report compares due dates of the assigned tasks with the current date to determine which time
period a task belongs to. The predefined due date periods are as follows:
• Past Due (one week or more)
• This Week
• Next Week
• In 3 Weeks
• In 4 Weeks
• After 4 Weeks
• None (no due date)
Task Status by Task List

This stacked column graph shows the total number of tasks for each of the task lists in an implementation project as
columns. The total number includes tasks from all subsequent levels of the task list. Each column is further broken down
by task statuses, which are represented by stacks within a column. Since the task lists are organized in a hierarchy in an
implementation project, the graph displays only the top nodes of an implementation project at first. You can drill down on
each graph to view the next level of details.
Top 5 Assigned Users with Incomplete Tasks by Due Dates

This stacked column graph shows the top five users who have the most number of incomplete tasks, such as tasks with
a status anything other than Completed, as columns. Each column is further broken down by due date periods, which are
represented by stacks within a column.
Top 5 Task Allocations

This stacked column graph shows the top five users with the most assignments and is filtered by due date periods. Each
user's allocation is further broken down by task statuses, which are represented by stacks within a column. The default
filtering is set to This Week.
Monitoring Implementation Progress: Procedure

Use the Implementation Projects: Overview page to monitor the progress of an implementation project.
You need the Review Implementation Project Overview privilege to perform this procedure.
To monitor the progress of an implementation project, follow these steps:

2. Select Manage Implementation Projects from the panel drawer. to go to the Manage Implementation Projects
page.
3. Click Overview to go to the Implementation Projects: Overview page.
4. Search and select the implementation project you want to monitor from list of projects.
21
5. In the Implementation Project Details region,
◦ Click the Assignment Status tab to view the Assignment by Status and the Assignment by Due Date reports.
◦ Click the Assignment Status by Task Lists tab to view the Assignment Status by Task List report.
◦ Click the Resource Status tab to view the Top 5 Assigned Users with Incomplete Tasks by Due Dates and the
Top 5 Task Allocations reports.
FAQ's for Managing Setup Using Implementation Projects

Why doesn't my implementation project show the tasks for a
functional area or feature I recently enabled?
If you enabled a functional area or feature after creating the implementation project, then the implementation project won't
show the tasks related to the newly enabled functional area or feature. The task list for an implementation project is created
based on the enabled status of the functional areas and features at the time you created the implementation project. Once
the task list is generated, it does not change if the opt-in configuration changes at a later time.
Why do my implementation projects include some common tasks

regardless of which offering I use to create it?
Every offering is self-contained, for example, its default setup task list contains all tasks, including the prerequisites, to
complete its end-to-end implementation. If there are setup tasks that are needed by multiple offerings, then each of them
include those tasks.
Does a common task duplicate setup data if I use it in multiple

implementation projects?
No, a task used in multiple implementation projects doesn't create duplicate data. Setup data is not segmented by an
implementation project or any other method you use to enter it. Each task points to the same setup data irrespective of the
implementation project from which you perform it. Therefore, when you use a task from a different implementation project,
you can also review the existing data and update it if necessary.
How can I see what types of setup data I enter using an

implementation project?
An implementation project shows the hierarchy of setup tasks by default. You can toggle to view the business object
hierarchy instead. Each business object represents a type of setup data. The sequence of the business objects in the
hierarchy indicates the order in which the setup data is exported and imported when the implementation project is used for
export or import processes.
22
Why didn't the task show as completed when I returned to my

assigned task list after entering data?
After entering setup data, when you return to the assigned task list, it does not necessarily mean that you have completed
entering data. You may need to return to the task to enter additional information. Therefore, a task is never marked as
completed automatically. When you know that you finished entering all data necessary for the task, you can set the task
status to completed.
Why did a common task I already performed and set to completed

not show as completed in every instance of the task across multiple
implementation projects?
You must set the task status individually for each task in each implementation project. The setup data for a task might need
a different set of data for a different implementation. The status of a task doesn't update based on its status in a previous
implementation. For example, you implement Financial Control and Reporting and complete the currency setup. Later, when
you implement Procurement, you want a few additional currencies for paying suppliers but not for financial reporting.
What happens if I change the task list of an implementation project

after I start entering data?
You can modify an implementation project's task list at any time. Your changes become effective immediately. If you add a
new task, it becomes immediately available for assignment, status reporting, and execution. If you remove any task, it does
not remain a part of the task list any longer. However, any data entered using the task is not removed.
How can I view implementation-specific reports?

You can download and print a set of reports at each level of the implementation task list hierarchy. These reports show the
relevant information for the task list and all dependent task lists and tasks. The available reports are the Setup Task Lists and
Tasks report, the Related Business Objects report, and the Related Enterprise Applications report.
23
24
Using Functional Setup Manager Managing Setup Using Alternative Processes
6 Managing Setup Using Alternative

Processes
Managing Setup Using Alternative Processes: Overview

Although you typically use setup task UIs to enter the setup data they represent, you can also use alternative methods to
manage setup data. These alternative methods may be more useful in certain special cases.
Entering Setup Data Using CSV File

Sometimes the setup data you enter is very simple or similar to existing data which you can duplicate. In such cases, you can
use a CSV file.
Copying Setup Configuration

You can copy a set of interdependent setup data configuration to create a new set of interdependent setup data that is
similar to the original with only a few differences. This process helps to create data faster, especially for setup requirements
that are complex but similar.
Entering Setup Data Using CSV: Explained

Sometimes the setup data you enter is very simple or similar to existing data which you can duplicate. In such cases, you can
use a CSV file.
When you enter or update a few attributes of a large volume of setup data for a task, using user interfaces to individually enter
or update them may not be most efficient. In such cases, you can upload setup data using export and import processes at
the task level. This method requires that your setup data is available in a CSV file format.
Exporting Setup Data to CSV: Procedure

Video
Watch: This video tutorial shows you how to export setup data using CSV. The content of this video is also covered in text
topics.
25
Sometimes the setup data you must enter is very simple or similar to existing data which you can duplicate. In such cases,
you can use a CSV file to enter setup data. This procedure explains how to enter setup data using a CSV file.
You need the following privileges to perform this procedure:
• Submit Export Setup Data Process privilege
• Submit Import Setup Data Process privilege
• Task-specific privileges
Refer to the Security Reference Manual for detailed information about task-specific privileges.
Exporting Setup Data To CSV file

To export setup data to CSV file, follow these steps:
1. Select Navigator > Setup and Maintenance to go to a Setup page.
2. Select the offering whose task requires setup data entry using CSV file.
3. Select the appropriate functional area and go to the applicable task.
4. Select Columns > View > Actions to make the applicable task actions visible.
5. Select a task, and from the Actions menu, select Export to CSV file.
Note: The Export to CSV file option is disabled if the task does not support export.
6. Select Create New. You can export all existing setup data represented by the task.
◦ If Scope is supported for the task, you can select appropriate scope values to filter the setup data you want to
export.
◦ You can also download the template without exporting the existing setup data in the environment. To do so,
select the Export only template files check box.
7. Click Submit to start the export process.
8. Select Export to CSV file to see the latest process. Monitor the process until it completes.
9. Select the process once it completes to review the results. Verify that the process completed without any errors
before you download and extract the CSV file.
Note: You may find more than one CSV file if there are more than one business object associated with
the task.
Preparing Setup Data in CSV File

To enter or modify the setup data in the CSV file, follow these steps:
1. Open Microsoft Excel and Click the Data tab.
2. In the Get External Data group, click From Text.
3. Navigate to and select the CSV file you downloaded. Select Delimited as Data Type and click Next.
4. Select Comma as delimiter and click Next.
5. Select Text as column data format for all columns and click Finish.
6. Save it into a .zip file once you complete your modifications.
26
Uploading Setup Data in CSV File

To upload the new or modified setup data, follow these steps:
1. Select the appropriate task from the Tasks region.

2. Select Import from CSV file from the Actions menu.
3. Select Create New.
4. Select the appropriate .zip file. The application validates that the file corresponds to the selected task before you can
submit the process.
5. Click Submit.
6. Select Import from CSV file to see the latest processes. Monitor the process until it completes.
7. Select the process once it completes to review the results. If any errors occur, review the details listed in Status
Details under the Business Objects section. Fix the issues and import again, if necessary.
8. After you import the setup data successfully, you can verify the loaded data by selecting the task from the Setup
page.
Copying Setup Configuration: Explained

You can copy an interdependent setup data configuration to create a new set of interdependent setup data that is similar to
the original with only a few differences. This process helps to create data faster, especially for setup requirements that are
complex but similar.
For example, create a business unit structure and then copy its setup to create a new business unit structure whose setup
data requirements are similar to the original business unit with only a few exceptions.
How Copy Configuration Works

Start the copy process by selecting an existing setup configuration, whose setup data is then copied to a staging area. Next,
modify the setup data in the staging area according to the requirements of the new setup configuration you want to create.
Since the purpose of copying setup is to create a new set of setup data quickly and easily, only those attributes that are
minimally required to be set up are available for edit.
After you complete making modification to the staged setup data, submit an import process which creates the new setup
configuration by copying setup data from the original and changing the data where applicable based on the modifications you
made.
Once the import process completes, Oracle recommends that you review your new setup configuration to ensure it meets
your requirements. You can also make additional changes to the data of the new setup if needed.
27
The following figure illustrates the steps in the copy configuration process.
Create Copy
Edit Staged Import Staged
Configuration
Configuration Configuration
Request
Fix Errors Review Copied

(If applicable) Configuration
Copying Setup Configuration: Procedure

This procedure explains how to copy an existing setup configuration and use it for other setup requirements that are similar.
You need the following privileges to perform this procedure:
• Submit Export Setup Data Process privilege
• Submit Import Setup Data Process privilege
• Task-specific privileges
Refer to the Security Reference Manual for detailed information about task-specific privileges.
To copy a setup configuration, follow these steps:

2. Select Copy Configuration from the panel drawer to go to the Copy Configuration page.
3. To create Copy Configuration Request,
a. In the Copy Configuration Requests region, select Create from the Actions menu to go to the Create
Configuration Request page. Alternatively, you can also click the Create icon.
b. Select the setup configuration you want to copy from Copy Configuration menu.
c. Select the scope of your copy. For example, if you copy setup configuration of business units, then you must
select one of the existing business units to copy its setup.
d. You can change the default request name if necessary.
e. Click Submit to start the copy process and to return to the Copy Configurations page.
4. To edit the staged configuration,
a. Monitor the Status column of the request in the Copy Configuration Requests table. Click Ready to Edit
when the status updates.
b. Enter or update the values for the displayed attributes, which represent the minimum set of setup data
required for the new setup configuration to function.
c. Click Save and Close when you complete making changes to return to the Copy Configuration page.
28
5. To import the staged configuration,
a. Click Ready to import in the Status column in the Copy Configuration Requests table when the status
updates.
b. The same set of attributes shown in the previous step is displayed for your final review. You can compare the
values of the source setup with the values of the new setup. Select Edit to make modifications if necessary.
Note: You cannot edit the values after the new setup is created.
c. Click Import to load the staged setup configuration and to return to the Copy Configurations page.
d. The Status column of Copy Configuration Requests table now shows Import in progress. Click the link
to monitor the import process. To get updated information click the Refresh icon.
6. To fix copy setup configuration errors,
a. Click Ready to fix errors in the Status column in the Copy Configuration Requests table.
b. Review the report and identify where the error occurred. The report lists all business objects in the order they
were processed.
• If the error is due to data conflicts such as attempting to create an object that already exists, use Edit
Staged Configuration to fix the error and resubmit the import process.
• Otherwise, report the issue to your help desk indicating the owning product as indicated in the error.
Download and attach the process status details report when reporting the issue.
7. To review the copied setup configuration,
a. When the import process completes successfully, the Status column is set to Ready to review. Use the link
to review the copied setup configuration. You can select the Go to Task icon for each setup task displayed to
verify accuracy of the setup data.
Searching For A Task: Points To Consider

When you make small changes to existing setup data that typically affects one or two tasks, you may search for the task and
enter or update the data it represents on a one-off basis.
Use this method of managing setup data cautiously, as it does not give you visibility to the setup data dependencies and
recommended sequence of performing tasks. This may cause you to experience errors.
Searching For A Task: Procedure

This procedure explains how to search for a specific task to manage the data it represents.
You cannot perform this procedure unless you have task-specific privileges. Refer to the Security Reference Manual for
detailed information about task-specific privileges.
To search for a specific task, follow these steps:
2. Select Search from the panel drawer to go to the Search page.
29
3. Enter a string that matches the complete or partial name of the task and click Search.
The string is matched with the names of tasks, lists and business objects by default.
4. Click the Tasks, Task Lists, Business Objects link to change the matching criteria. Select the criteria from the
available options and click Done.
5. From the search results,
◦ If you matched with task, click the link in the Name column to go to the page for entering the setup data it
represents.
◦ If you matched with task list or business object name, click the link in the Name column to go to a list of tasks
that are associated with the task list or business object. Follow the actions in the previous step to manage the
setup data of each task in the list.
◦ If you matched with functional area, click the link in the Name column to go to a list of the parent offerings of
the functional area. Select the applicable offering to find the list of tasks in the task region. Follow the actions
in the previous step to manage the setup data of each task in the list.
◦ If you matched with offering name, click the link in the Name column to go to the offering. Follow the actions
in Managing Offering Setup: Procedure to manage the setup data of the offering.
Related Topics
• Setting Up Offerings: Procedure
30
Using Functional Setup Manager Exporting and Importing Setup Data: Overview
7 Exporting and Importing Setup Data:

Overview
Exporting and Importing Setup Data: Overview

Almost all Oracle application implementations require moving functional setup data from one instance to another at various
points in their life cycle. For example, one of the typical cases in any enterprise application implementation is to first
implement in a development or test application instance and then deploy to a production application instance after thorough
testing. You can move functional setup configurations of applications from one application instance into another by exporting
and importing setup data.
You can export and import setup data for your implementation depending on your business needs using any of the methods
described here. You must import the setup data in the same way that you export it.
• Export and import an entire offering or any of its functional areas. This method is recommended when you want to
make sure all the setup data for an offering or functional area is migrated as it currently configured.
• Export and import an implementation project that contains a modified configuration or list of tasks. Use an
implementation project as the source for exporting setup data when you require modifications to the list of tasks or
the list of objects you want to export setup data for.
In the case of an offering or functional area, setup data is exported only for the tasks relevant to the features that are enabled
for implementation in the offering or functional area. Unlike the case of export an offering or functional area, an implementation
project may also include tasks for an entire offering or a functional area but the list of tasks may have been modified to
specific needs by adding or removing some of the tasks.
Task CSV Export

Additionally, in some cases, you may have a substantial number of setup data records with few attributes to enter for a setup
task. Entering this data using the UI may be cumbersome and in some cases prone to error. Functional Setup Manager
provides you the ability to export and import setup data for a specific task that meet these requirements using a CSV file.
Note: Check with the product owner to validate if a task supports CSV export or import that you may require.
Configuration Packages: Explained

A configuration package contains the setup import and export definition. The setup import and export definition is the list of
setup tasks and their associated business objects that identifies the setup data for export as well as the data itself. When you
create a configuration package only the setup export and import definition exists. Once you submit export, a snapshot of the
appropriate setup data is added to the configuration package using the definition. You can continue making modifications to
the setup data in the environment and create a new configuration package any time you need it.
31
You can generate the setup export and import definition implicitly or explicitly:
• A configuration package is created implicitly when you export setup data for an entire offering or any functional area.
• A configuration package is created explicitly when you export setup data based on an implementation project. This
method enables further modification of the configuration packages.
You generate the setup export and import definition by selecting an implementation project and creating a configuration
package. The tasks and their associated business objects in the selected implementation project define the setup export
and import definition for the configuration package. In addition, the sequence of the tasks in the implementation project
determines the export and import sequence.
The tasks and their associated business objects in the selected configuration (offering, functional area or implementation
project) define the setup export and import definition for the configuration package. In addition, the sequence of the tasks in
the implementation project determines the export and import sequence.
Once a configuration package is exported, the setup export and import definition is locked and cannot be changed. You
cannot change the add or remove tasks and their associated business objects, change their export and import sequence, or
change the scope value selection. However, you can create a new configuration package with such modifications at any time.
Business Object Import Sequence: Explained

The setup data for business objects related to tasks are imported according to the import sequence. The default business
object import sequence is derived based on the sequence of the tasks within the configuration selected to export setup data
for. This is because the task sequence should be congruent to the sequence you need to enter the related data to prevent
dependency failures.
Oracle delivered task lists have been designed with the data dependency in mind to avoid errors while running import.
Therefore, the default sequence of the tasks within an offering or functional area takes into consideration such dependencies
and prevents dependency failures.
The application assigns the lowest import sequence number to the business objects associated to the first task and increases
the sequence number for the successive tasks.
Note: When you create an implementation project and modify the list of tasks, you must consider the
dependencies between the setup data. It is strongly recommended that you have no more than one offering in
an implementation project. This ensures that import and export of the setup data is straightforward and that the
export and import sequence is correct.
Note: You can change the default import sequence when creating your configuration package if you are fully
aware that such changes do not result in data dependency failures during import.
The following business objects are exceptions to the default task-based sequence rule and they are always exported and
imported before any other business objects in this sequence:
Business Object Name Business Object ID
Application Taxonomy FND_ APP_TAXONOMY

Application Reference Data Set FND_ APP_ REFERENCE_ DATA_SET

32
Business Object Name Business Object ID
Application Reference Data Set FND_ APP_ REFERENCE_ DATA_ SET_ ASSIGNMENT
Assignment

Application Lookup FND_ APP_ SET_ ENABLED_ LOOKUP

Data Security Policy FND_ APP_ DATA_ SECURITY_ POLICY

Application Tree Structure FND_ APP_ TREE_ STRUCTURE

Application Tree Label FND_ APP_ TREE_LABEL

Application Tree FND_APP_TREE

Application Flex Value Set FND_ APP_ FLEX_ VALUE_SET

Application Descriptive Flexfield FND_ APP_ EXTENSIBLE_ FLEXFIELD

Application Extensible Flexfield FND_ APP_ _FLEXFIELD

Application Key Flexfield (FND_ APP_ KEY_FLEXFIELD

Export Scope: Explained

All setup data from all business objects in the export definition is exported by default. However, exported setup data can
be filtered by specific export scope values if the business object has scope enabled for setup data export. These business
objects are known as scope enabled business objects and are typically qualifiers of other setup data. Some of the examples
of business objects with scope are Business Units, Legal Entities, Ledgers, and Territories. Scope enabled business objects
might potentially be used to filter or segment other setup data during setup export. Example: You can get filter and export
all transaction tax data for a given tax regime. During export, you have the option to select specific scope values for such
business objects and they are used as filter criteria for exporting setup data of the relevant business objects that depend on
them. For any setup data where scope is applicable, only the data that matches the selected values are exported.
How Export Works: Explained

Functional Setup Manager exports the setup data relevant to the configuration you select (offering, functional area or
implementation project). To do that Functional Setup Manager will:
1. First, it takes a snapshot of your configuration at the time of the export by creating a configuration package. This
configuration package includes all the relevant tasks applicable to the selected configuration based on the features
enabled for implementation at the time of the export.
33
Note: The definition of the configuration package is unchanged once you create it. Therefore you
can change the feature selection for your configuration and it will not impact the existing configuration
packages.
2. Then, Functional Setup Manager identifies all business objects associated to the tasks within such configuration and
assign them a sequence for the purpose of export or import their setup data. This sequence is congruent to the task
sequence used to enter the setup data for such configuration.
3. The application assigns the lowest import sequence number to the business objects associated to the first task and
increases the sequence number for the successive tasks.
4. Functional Setup Manager processes the business objects in the list based on the import sequence. Functional
Setup Manager identifies the service associated to the business object, invokes the service to export the setup data
and returns the results. The business object is then marked as processed and Functional Setup Manager continues
with the next business object in the list. If no service is available, then the business object is marked as requiring
manual data loading and continues with the next business object in the list.
5. The setup data of some business objects may be processed by the same service, and hence the service exports
the setup data for all the relevant business objects that shares it. Because the service takes care of all the relevant
setup data at once, it only must be invoked once during the process; therefore, Functional Setup Manager marks as
processed and with the same result, any other business objects sharing the same service.
6. All the scope parameters defined for the configuration being exported are passed to each service in the list when
invoked. Each service handles and uses only the scope parameters relevant to its logic and exports the setup data.
7. Finally, after completing the list, Functional Setup Manager consolidates the setup data returned by each service into
a compressed file known as the configuration package file. Functional Setup Manager also consolidates all the errors
returned by the services while processing the setup data and generates the appropriate summary report.
How Import Works: Explained

Unlike the export setup data process, the import process acknowledges that your attention may be needed for tasks where
setup data cannot be imported through a service.
Functional Setup Manager will first identify and remind you of all such tasks that are recommended to perform either:
• Prior to import
Oracle delivered tasks that cannot be migrated through a service, may be marked as recommended to perform prior
to import when other setup data depend on it. Import setup data process warns and reminds you of performing
such task before proceeding with your import process. Make sure to perform such tasks prior to import to avoid
data dependency issues while running import.
• During import
Oracle delivered business object which setup data is prerequisite of other setup data and that do not have a service
available for setup data are marked as recommended to perform during import. The import setup data process
pauses when it reaches such business object and waits until user confirms such setup data was imported by user.
Functional Setup Manager pauses the import setup data process at the proper time to remind you and wait for
confirmation that such setup data is entered before proceeding. Make sure to perform such task prior or at the time
the process is paused.
• Post import
Oracle delivered tasks handling third-party setup data cannot be migrated through a service, but other setup data
within the configuration do not have any data dependencies. Therefore, you should perform those tasks just to
34
ensure all your configuration setup data is migrated but you do not have to perform prior or during the import
necessarily.
Depending on the method used to import the setup data, you first have to upload the configuration package file created by
the export process prior to initiate the import process. During the import, this file is read to identify all the business objects
which setup data is included in it. Once the import process is initiated, it warns users to perform the task recommended
performing prior to import. Once user decides to continue, Functional Setup Manager starts invoking the business object
services based on the import sequence assigned to the business objects in such configuration and processes the setup data
as follows:
• Setup data records that exist in the configuration package but do not exist in the target environment are inserted.
• For setup data records that exist in both the configuration package and the target environment,
◦ If the attribute values are different, then import updates the record in the target environment with the values
from the configuration package.
◦ If the attribute values are the same, then import leaves the record unchanged.
• Setup data records that exist in the target environment but do not exist in the configuration package, are untouched
in the target environment. Importing data does not delete any existing data.
When required, the import process pauses, giving you the appropriate information and suggested actions. Resume the
import process after taking the appropriate actions.
• If a setup import process paused due to errors encountered, then review the errors and take appropriate actions to
correct the data or fix the issue, and then resume the process. The process resumes processing data for the failed
object. However, you have the option to skip the failed object and continue processing data for the next business
object in the list.
• If a setup import process paused due to a manual task to be performed outside of the application, then you perform
the task and resume the paused process.
The import setup data process continues until all the services for importing the setup data are complete or user has stopped
or canceled the process. Services perform an update and insert operation. That is, existing rows that are identical to the data
being imported are ignored, existing rows that have differences are updated, and new rows are inserted. Each service is
invoked once and imports all the setup data for the relevant business objects that share it. Any dependencies that may exist
between the business objects that share a business object service are taken care and resolved by the service itself.
Export and Import: Best Practices

Use this process to best export setup data from one environment and import it into another.
Use the following procedures for the best approach.
Create and verify setup in the test instance

To create and verify setup in the test instance:
1. Create the new setup in the test instance.

2. Ensure that the setup is fully verified and validated.
3. Once verified, the setup data is ready to be published to the production instance.
35
Publish to the production instance

To prepare to move to production:
1. Ensure that the test and production instances are at the same release level.
2. Use offering reports from the Offerings page to plan your strategy for moving from the test instance to the production
instance.
3. Review setup task list and task reports from the Offerings page to:
◦Identify setup tasks that have setup services and those that do not have services. Tasks without setup
services may require manual actions, plan accordingly.
◦ Understand setup data (business object) dependencies based on Oracle delivered offering task list hierarchy.
Avoid making changes to the default business object sequence.
4. Create a row in one instance and move to another instead of creating the same row manually in both instances.
Note: If a user creates a row in source, then creates the same row in target, and later uses export or import to
move the data, the import may fail due to conflicting alternate keys for the same row.
To export from the test instance:

1. Export verified data from the test instance.
◦ Export only one offering at a time.
2. Use scope filtering functionality to limit the data being exported when performing incremental setup.
3. Download the resulting configuration package file.
4. You may also perform one or more of the following steps with the exported configuration package file:
◦ Back it up or version it in source control.
◦ Keep a history of all your published configuration package files.
◦ Compare it with previous versions to track and analyze setup data changes over time.
To import into the production instance:

1. Upload the verified configuration package file into the production instance.
Note: Only a configuration package file that contains data verified in the test instance should be
imported into the production instance.
2. Use comparison reports to review potential setup changes before submitting the import process.
◦Importing data into a target (production) instance will insert and update rows, but it will not delete any existing
data. Use comparison reports between source (test) and target (production) configuration packages to identify
data that only exists in the target (production) instance, and use the appropriate setup task to delete any data
if and when necessary.
3. Perform tasks marked for pre-import.
4. Submit the import process:
◦ Load the necessary data manually when the import process pauses on a specific business object indicating
manual import pending before resuming the process. Business objects that pause during an import process
have downstream dependencies which may fail if manual actions are not taken at the appropriate time.
◦ Use export and import process status details (looking at the UI, reports, and logs) to review any errors and
either fix the data in source and re-import, or report any unexpected behavior to My Oracle Support.
36
5. Review setup in the production instance once import completes.

6. When a configuration package is imported, the individual business object setup services import the setup data and
commit that data to the database. It is not possible to rollback the data after the import.
Note: To refresh the test instance completely with both the setup and transactional data from the
production instance, always use a reverse production-to-test process to synchronize the test to
production instances before performing incremental setup in the test instance.
Incremental and Maintenance Data Import: Critical Choices

Although it's recommended that you export and import setup data for an offering, you may require an incremental data
migration during your implementation. In such cases, you can export and import setup data for more granular configurations
than an offering such as a functional area or a task list. There are several considerations to keep in mind if you migrate more
granular configurations.
Points to consider for incremental data migration

You should fully consider the following choices before performing any incremental data migration:
• Create the implementation project with the appropriate tasks for the configuration you want to migrate.
• Make sure that all prerequisite data for your configuration is available in the environment where you are planning
to migrate the setup data. For example, If you require a legal entity to exist before you migrate the setup data for a
business unit configuration and the prerequisite setup data does not exist, consider to adding it to the configuration
package you use to import.
• The sequence of the tasks and therefore the business objects in your configuration should align with the business
object dependencies and prerequisites. Oracle delivered task lists have been designed with this in mind to avoid
errors while running import.
• You may also refine the scope of the data you want to export or import while creating your configuration package by
defining the scope selection. Be aware that scope selection is not available to all business objects. Check that the
business object service supports it. Check the application documentation or verify it from the application at the time
you are defining your configuration package. A select and add icon is enabled on the scope table once you select
the corresponding business object.
• During an incremental migration, all the setup data in the configuration package is processed inserting all new data
records and updating existing setup data records according to service logic. No data is removed during the import
process unless otherwise specified by the service. Consult the application release notes to review any exceptions on
handling the setup data by the service.
Additional Access for Exporting and Importing Setup Data:

Explained
You must have access to the Application Implementation Consultant role to export or import setup data. However, access to
additional roles is needed to export and import setup data for certain business objects:
37
Business Object Name Required Role Name
Corporate Card Expense Type Mapping Corporate Card Administrator

Rule

Corporate Card Company Account Corporate Card Administrator

Corporate Card Program Corporate Card Administrator

Corporate Card Transaction Download Corporate Card Administrator

Parameter

Corporate Card Transaction Upload Corporate Card Administrator

Rule

Corporate Card Usage Limit Rule Corporate Card Administrator

Bank Statement Reconciliation Cash Manager

Tolerance

Bank Statement Automatic Cash Manager

Reconciliation Matching Rule Set

Bank Statement Automatic Cash Manager

Reconciliation Matching Rule

Bank Statement Transaction Creation Cash Manager

Rule

Cash Transaction Type Cash Manager

Bank Transaction Code Cash Manager

Bank Statement Parsing Rule Cash Manager

Bank Account Cash Manager

Bank Branch Cash Manager

Bank Cash Manager

Collections Aging Bucket Collections Manager

Collections Dunning Configuration Collections Manager

Collections Preference Collections Manager

Collector Collections Manager
38
Business Object Name Required Role Name

Expense Audit Rule Expense Manager

Expense Audit List Rule Expense Manager

Expense Receipt Management Rule Expense Manager

Incentive Compensation Participant Incentive Compensation Application Administrator

Department Human Capital Management Application Administrator

Legal Employer Human Capital Management Application Administrator

Payroll Statutory Unit Human Capital Management Application Administrator

Division Human Capital Management Application Administrator

Job Human Capital Management Application Administrator

Location Human Capital Management Application Administrator

Enterprise Information Human Capital Management Application Administrator

Legislative Data Group Human Capital Management Application Administrator

Payroll Security Profile IT Security Manager

Payroll Flow Security Profile IT Security Manager

China Ledger Option Enterprise Financial Data Export Options Management for China

China Depreciation Method Formula Enterprise Financial Data Export Options Management for China

China Financial Information Option Enterprise Financial Data Export Options Management for China

China Golden Tax Miscellaneous Option Golden Tax Administration for China

China Value Added Tax Invoice Option Golden Tax Administration for China

39
Concurrent Implementation Maintenance: Critical Choices

If you are concurrently implementing more than one offering at a time, you should adhere to the following sequence when
importing these offerings into another environment to prevent data dependency issues.
Offering Import Sequence

This table shows the offering import sequence.
Sequence Family Offering
1 HCM Workforce Deployment

2 HCM Compensation Management

3 HCM Workforce Development

4 Financials Financials

5 Financials Fusion Accounting Hub

6 HCM Incentive Compensation

7 CRM Customer Data Management

8 CRM Enterprise Contracts

9 CRM Marketing

10 CRM Sales

11 Procurement Procurement

12 Projects Project Financial Management

13 Projects Project Execution Management

14 Projects Grants Management

15 SCM Materials Management and Logistics

16 SCM Manufacturing and Supply Chain Materials

Management

40
Sequence Family Offering
17 SCM Order Management

18 SCM Price Management

19 SCM Product Management

20 SCM Supply Chain Financial Orchestration

21 SCM Supply Chain Managerial Accounting

22 SCM Value Chain Planning

23 GRC Risk and Controls

FAQs for Importing and Exporting Setup Data

What's a setup business object?
A setup business object is a self-contained representation of a business entity supported by a setup task. These are logical
representations of real-world objects. Setup business objects represent the data entered when you perform setup tasks.
Business objects used by setup tasks also require web services to facilitate export and import of corresponding data. Setup
data entered by way of a setup task is stored in the table associated with the corresponding business object. For example,
Primary Ledger is the business object of the setup task called Manage Primary Ledger. When the Manage Primary Ledger
task is performed, data entered is stored in the tables associated with the Primary Ledger business object.
When does export or import show errors at the data level as opposed
to the system level?
An error at the business object level occurs if the setup export and import web services cannot start. For example, if a service
cannot be found in the specified location where it is registered or access is denied to the service then the application raises
an error. In general, errors occur at the system level. However, data level errors may also occur depending on how the web
services are designed.
Why did the export process not raise any errors when it did not
export any data?
Sometimes no data exports for a business object even though the process completes successfully without any errors. This
happens when only Oracle Fusion Applications predefined setup data exists in the business object. Setup export and import
41
exclude Oracle Fusion Applications predefined setup data. A message indicating that no rows were processed and no failures
occurred during export displays when the export process completes.
What's a business object dependency?

If there is data dependency between two business objects then a hierarchical relationship can be defined between them.
Typically this signifies that parent business object is fully qualifies the child business object. For example, Tax Regime is the
parent business object while Tax Rate is a child business object. This means, that to fully identify a tax rate you must know
the tax regime as well.
Task List Scope and Business Object Hierarchy

A hierarchical relationship between business objects is especially important if you want to define hierarchical task list scope
objects. Relationships between the scope objects must be defined through the hierarchical relationships of the respective
business objects.
For example, a Legal Entity object is the scope for a Define Legal Reporting Unit object. If Legal Entity is the scope for Define
Legal Reporting Unit, then if you want to make selection of both Legal Entity and Define Legal Reporting Unit when defining
Legal Reporting Unit, you must define Legal Entity as the parent business object of Define Legal Reporting Unit.
A child or dependent business object can have one and only one parent, while a parent business object may have multiple
children.
What happens if my import process remains in the Paused Due to

Errors status?
An import process is set to Paused due to errors when the process has paused because either an error occurred that you
must correct. Review the process results and resume the process once you have taken appropriate actions to correct the
errors. The process restarts processing the same business object that failed by default. You can instruct the import process
to skip the failed business object and continue with the next object if you manually entered the appropriate data or want to
receive all errors at the end. Notice that additional business object having data dependency downstream may also fail if you
skip the failed object without fixing the corresponding errors.
What happens when I skip the failed object during import?

The skip failed object option during importing setup data is recommended when you have taken care of the issues manually
(outside the configuration package), or when no data dependencies exist for the object and you are planning to address
the issues later. When you resume the import setup data process with the skip failed object option, the import process will
no longer try to process setup data for the business object that generated the error last time and will proceed with the next
business object in the configuration package. However, any setup data for the failed object that was previously processed
by the Import Setup Data will remain. Notice that errors will be raised while processing the setup data of any other business
object that depend on the failed object data that was not fixed.
42
What happens when I resume the import setup data process without
loading the requested data?
Errors may occur later while importing setup data for other objects that depend on the business object you suppose to
manually import data for. However, if the setup data already exists in the environment due to was previously imported, you
can resume the process without any issues.
Can I run the Import Setup Data process without pausing and obtain
a report of all errors at the end?
Yes. To do so, make sure to unmark the option Pause each time an error occurs when submitting or resuming the Import
Setup Data process. After the process finishes, review the process results to get the error details. The import processes all
the business objects but it may still pause with status User Action Required if any business object requires manual import.
You can identify what objects require prior manual data import, if any, and force the process to run without pausing for
manual import. To do so, navigate to the Pause for External Import step when submitting the import setup data process,
then identify all business objects marked for pause and deselect them.
Why was no data exported for my business object?

The export process will always export the setup data rows that are not pre-seeded. If you haven't entered any of this data for
a given business object, the process will report a message indicating no rows were processed. If you are sure you have this
data for the business object, make sure to report this to the product that owns the business object.
Why did I get a message saying Manual Export Status Pending?

During the Export Setup Data process, some business objects may finish with the status Manual Export Pending. This
indicates that a service to export the setup data for this business object is not available, and the application cannot
automatically export the setup data. If any setup data for this business object exists in the environment you are exporting the
data from, you must manually set it up in the environment where you are planning to import the setup data. During the import
setup data process a pause will occurred if the setup data is needed as prerequisite for any other business object.
Do I need to wait for the process to pause in User Action Required to

manually import the setup data?
No. The Import Setup Data process pauses to alert you when such data is required based on the configuration you are
importing. You can manually import it prior to the process pauses.
43
Why did import errors appear when no data to import is found?

If your configuration package contains no data for a given business object, the import process sets the status to Completed
with Errors and indicates that no data is found. The application is trying to ensure that all relevant data for a given
implementation is available during the import. If data does not exist or you do not want to import data for the business object,
you can bypass these errors by resuming the import process without pausing for errors.
44
Using Functional Setup Manager Exporting and Importing Offering Setup Data
8 Exporting and Importing Offering Setup

Data
Offering Based Export and Import: Explained

It's strongly recommended you use this method for data export and import to ensure migration of all relevant setup data to
the offering or functional area. This is especially useful when doing your initial implementation or moving your implementation
or configuration across instances for the first time.
This method is advantageous over others because you do not need to choose the tasks or understand data relationships to
ensure only setup data relevant to the selected offering or functional area is exported. At the same time, it gives you flexibility
to filter the setup data for the offering or functional area, where applicable.
Export and import offering setup data processes are initiated from the Setup and Maintenance work area.
Export
During export, appropriate setup data will be identified as follows:
• When you export setup data for an offering, the export definition will include setup data for all enabled functional
areas and relevant features in the offering.
• When you export setup data for a single functional area within an offering, the export definition will only include setup
data for that functional area and relevant features.
Import
During import, a configuration package created by the export process is uploaded. All setup data contained in the
configuration package is imported into the environment you initiate the setup data import from.
Similarly to the export process, you can import setup data for an entire offering or a specific functional area. The offering
and functional area must already enabled for implementation before you can import setup data for it. However, the feature
selection may or may not be selected. To ensure enabling of that the same functionality that existed in the environment where
the setup data was exported from for the corresponding offering or functional area, use the option to import the feature
selection at the time of importing the setup data. You must use a configuration package file that contains the setup data for
the appropriate offering or functional area. You also have the option to compare the setup data prior to import to identify what
setup data modifications will happen if the setup data is imported. You can also compare the setup data after it has been
imported (rather than prior to import) in order to ensure that no differences exist. One you initiate the import process, you can
monitor its progress and check its status from the Export Offering page. Once the process is complete you can review the
reports. Similarly, use the Import Offering Setup Data page to upload and import previously exported setup data.
Exporting Offering Setup: Procedure
45
Video
Watch: This video tutorial shows you how to export offering setup data from your application instance for future importing into
another environment. The content of this video is also covered in text topics.
You can export setup data for an offering or functional area that you already completed setting up.
Export Offering or Functional Area Setup

To export setup data for an offering or functional area, follow these steps.
1. Select Navigator > Setup and Maintenance work area to open the Setup page. You need the Application
Implementation Consultant role to export setup data.
2. Select the offering whose setup data is already available and you require to export.
3. From the Actions menu for the offering, select Export > Create New.
4. As the default, all existing setup data represented by the tasks of the selected offering is available to export.
5. Optionally, if scope is supported, then you can select the appropriate scope values to filter the exported setup data.
a. Select the business object from the Business Objects table and then click the Add button.
b. Search and select the value you want to filter the data and click Apply.
c. Repeat the step above to add additional values as needed, otherwise, select Done.
6. Click Submit to start the export process.
7. Monitor the process until it completes. Select Export from the Actions menu. The latest process will be shown at the
beginning of the list.
8. Click the process link once it completes to review the results.
9. Review the list of Post-Export Tasks for any task of the selected offering for which setup data is not migrated by the
export process. If applicable, you need to perform those manually in the target environment.
10. Download the Zip file and use it to import the setup data in the target environment where the implementation is
migrated.
11. If the setup data of any of the functional areas change in the future, you can migrate the setup data of the specific
functional area rather than the entire offering. Select the appropriate functional area and then in the Actions menu for
the functional area, select Export > Create New.
12. As the default all existing setup data represented by the tasks of the selected functional area is exported. Follow the
same steps described previously for the offering to export data for the functional area.
Importing Offering Setup: Procedure

Video
Watch: This video tutorial shows you how to import offering setup data into your application instance. The content of this video
is also covered in text topics.
46
Comparing Offering Setup Data During Import

Watch: This video tutorial shows you how to compare offering setup data during import. The content of this video is also
covered in text topics.
You can import setup data for an offering or functional area.
Import Offering or Functional Area Setup

To import setup data for an offering or functional area, follow these steps.
1. Select Navigator > Setup and Maintenance work area to open the Setup page. You need the Application
Implementation Consultant role to import setup data.
2. Select the offering whose setup data you require to import.
3. Open the Actions menu for the offering or the functional area that matches the content of the exported setup data
file. An error message l appears if the selected setup data file wasn't generated for the offering or functional area you
selected to import.
4. Select Import > Create New.
5. Select the file that contains the exported setup data you want to import.
6. Review the configuration package details to verify it's the correct file. If needed, click Update to select a different file.
7. Optionally, select the Import feature selection check box in Import Options to overwrite and match the opted
in selection in the source environment when the setup data was exported. Additionally, select the Compare setup
data before import check box to compare the existing setup data in the environment with the data to import before
the data is actually modified by the import process.
8. If applicable, a list of any required setup data that must be entered manually prior to import appears. These are
the same manual tasks that were listed during the export process. Make sure to enter the appropriate setup data
by performing these tasks and then click Submit to start the import process. A confirmation message appears,
indicating that the import process was submitted.
9. Monitor the process until it completes. Select Import from the Actions menu. The latest process is shown at the
beginning of the list.
10. The process status appears as Waiting for Comparison Review if you selected the Compare setup data before
import option. Click the process link once it completes to review the results.
a. The objects with setup data discrepancies are listed by default.
b. Check the Only in Configuration 1 column to determine which records do not exist in the environment. They
are created in the production if this configuration package is imported. To see the details click on the link for
the corresponding business object to review.
c. Check the In Both with Mismatch column to review the records that exist in both the configuration
package and the environment, but have different attribute values. Click on the link to review the details of the
corresponding business object. The report contains two rows for each matching record: the first row displays
the values from the configuration package and the second row displays the values from the environment.
Values are only presented for the attributes with discrepancies, so they can be easily identified.
d. Check the Only in Configuration 2 column to determine which records exist only in the environment and not
in the configuration package. The import process does not delete any records and therefore these records
remain untouched in the environment. Click on the link to review the details for the corresponding business
objects and determine if you should remove them manually.
47
e. After reviewing all the discrepancies, select Continue to Import to start the import process. Otherwise, select
Cancel Process from the Actions to cancel the process.
11. If any setup data is required during import, the process pauses with the status of Waiting for manual import.
a. Click the status to review the details of what setup data is required.
b. Enter the appropriate setup data by performing the task. Click Go to Tasks.
c. Once you entered the setup data for all of the relevant tasks, return to the Import Offering Data Results page
and resume the process.
d. Confirm you entered the data and the process will resume.
12. Continue monitoring the process until it completes. Click the status once the process completes.
13. Verify that the process completed successfully. If there are any post-import tasks reported, make sure that the
corresponding setup data is entered before making the offering available to the end users.
14. If the process completed with errors, review the status details for each of the failing business objects and take the
appropriate action.
FAQ's for Exporting and Importing Offering Setup Data

How can I view and print any errors generated while importing or
exporting offering setup data?
Open the import or export process results and download the log file. Optionally, you can select a specific business object and
download its log file.
How can I cancel an export or import process that I submitted?

You can cancel any export or import process from the Manage Export and Import Processes page or from the Manage
Configuration Packages page. Select the process you want to cancel, and select Cancel Process from the Actions menu.
Once you confirm to cancel the process, it completes processing of the business object that already started and does not
process the remaining business objects. The process status is changed to Canceled and you are not able to resume the
process.
How can I understand if an export or import offering setup data

process is making progress and know which business object is
currently processing?
For an offering-based export or import process initiated from the Setup page,
1. Select the corresponding offering from the Setup page.
2. Select the export or import process you are interested in.
3. Navigate to the export and import process results page by clicking the Status column.
4. Review the Total of Objects Processed that appears in the Object Details table to identify how many objects
have been processed so far. Refresh the page and review this value again to see any progress.
48
5. Open the Status menu and select In progress to filter the contents of the Object Details table on the Export and
Import process results page.
The name of the business object currently being processed is displayed.
49
50
Using Functional Setup Manager Exporting and Importing Setup Data for Implementation
Projects
9 Exporting and Importing Setup Data for

Implementation Projects
Implementation Project Based Export and Import:

Explained
Use an implementation project as the source for exporting setup data when you are required to modify the list of tasks or of
objects you want to export setup data for.
You must explicitly create a configuration package from the Setup and Maintenance work area to export setup data for an
implementation project. You generate the setup export and import definition by selecting an implementation project and
creating a configuration package. The tasks and their associated business objects in the selected implementation project
define the setup export and import definition for the configuration package. Depending on your needs, when you create a
configuration package based on an implementation project, you can also modify some additional aspects, as explained here.
• Exclude some of the business objects from the configuration you selected to export setup data for.
You should limit to use this option when the corresponding setup data is already available in the target instance and
therefore no data dependency issues appear during import.
• Change the default import sequence of the business objects
It's strongly recommended that you limit using this option when you need to correct a data dependency issue and
you fully understand the data relationships between the business objects of your configuration.
• Filter the setup data to export
Export
During export, appropriate setup data is identified based on the tasks in the implementation project used as source for
the configuration package. The setup data in the configuration package is a snapshot of the data in the source application
instance at the time of export. Once export completes, you can download the configuration package file as a zipped archive
of multiple XML files, move it to the target application instance, and upload and import it. After exporting the setup data
you may continue entering new or modifying existing setup data for your configuration. Since the configuration package
is a snapshot of the setup data taken at the time export is initiated, you may need to take another snapshot of the same
configuration or set of data later. Although you can always create a different configuration package, Functional Setup
Manager provides you the ability to take another snapshot of the setup data using the same modified export and import
definition by exporting the configuration package multiple times and creating multiple versions. While the export definition
remains the same in each version, the setup data can be different if you modified the data in the time period between the
different runs of the export process. Since each version of the configuration package has a snapshot of the data in the source
instance, you can compare and analyze various versions of the configuration package to see how the setup data changed.
Import
During import, you first upload a configuration package created by the export process and then import the setup data. All
setup data contained in the configuration package is imported into the environment you initiate the setup data import from.
In the target application instance, the setup import process inserts all new data from the source configuration package that
51
Projects
does not already exist, and update any existing data with changes from the source. Setup data that exists in the target
instance but not in source will remain unchanged.
Modifying Configuration Packages: Points to Consider

All tasks and associated business objects in the selected implementation project are included in the setup export and import
definition of a configuration package. You can modify the setup export and import definition when you use an implementation
project as source for the configuration package. The following are the modification options available for configuration
packages based on implementation projects.
Excluding Business Objects

If you do not want to export any specific setup data, you can exclude the corresponding business object from the setup data
export and import definition of the configuration package. However, before excluding any business object, make sure that
all prerequisite data for your configuration is available in the environment where you are planning to migrate the setup data.
Therefore, you should limit to use this option to cases where the corresponding setup data is already available in the target
instance and no data dependency issues result during import.
Reordering Business Objects

The default export and import sequence of setup data, or business objects, is the same as the order of the tasks they are
associated with in the configuration. You can change the sequence in which setup data is exported and consequently
imported by changing the sequence of the business objects in the setup export and import definition of your configuration
package. Oracle recommends that you limit using this option when you must correct a data dependency issue and you fully
understand the data relationships between the business objects of your configuration.
Filtering Setup Data

All setup data from all business objects in the setup export and import definition is exported by default. However, you can
filter exported setup data by specific export scope values if the business object has a scope selection for setup data export.
During export, you might have the option to select specific scope values. For any setup data where scope is applicable, only
the data that matches the selected values transfers.
Business Objects Marked as Scope Parameters: How They

are Exported
When creating a configuration package for an implementation project, you may see some business objects listed and used as
scope parameters. These correspond to business objects used as parameters just for the purpose of filtering setup data for
some tasks within the implementation project used as source for the configuration package.
Note: Business objects that are used as scope parameters for data filtering do not appear when creating a
configuration package for an offering or functional area.
52
Projects
How Export Handles Scope Parameters

The data for business objects used as scope parameters is not exported because these business objects are not directly
associated to any tasks in the implementation project used to create the configuration package. During export, all scope
values defined by user are passed to each service to filter the appropriate data. Each service uses the applicable parameters
and return the appropriate setup data. Therefore data of the business objects that depend on the business object scope
parameter is filtered and exported.
Example
Receivable data may be filtered by subledger, (subledger may have been defined as the scope parameter for receivable
data). Even if subledger is not associated with any tasks in the Receivables configuration you selected to export, you have the
option to filter receivables data associated to certain subledgers during export. You find the subledger business object listed
as scope parameter even though subledger data does not exported.
Exporting Setup Data to Configuration Packages:

Procedure
Video
Watch: This video tutorial shows you how to export setup data to configuration packages. The content of this video is also
You can export setup data for an implementation project that you already completed setting up.
Export Setup Data to Configuration Packages

To export setup data to a configuration package, follow these steps.
1. Sign in to the environment where the setup data to export is available and select Navigator > Setup and
Maintenance work area to open the Setup page. You need the Application Implementation Consultant role to
export setup data.
2. From the Setup page, open the panel drawer and select Manage Configuration Packages to open the Manage
Configuration Packages page.
3. From the Actions menu on the Manage Configuration Packages page, select Create New.
4. From the Name list of values under the Source Implementation Project, select the implementation project that
contains the setup data to be exported. The Basic Information section contains information that you can modify as
needed.
5. Click Next. As the default all existing setup data represented by the tasks of the selected implementation project is
exported.
53
Projects
6. Optionally, if scope is supported, then you can select the appropriate scope values to filter the exported setup data.
a. Select the business object from the Business Objects table and then click the Add button on the Scope
table..
b. Search and select the value you want to filter the data and click Apply. Click Done when you finished.
c. Repeat the steps above for additional business objects you want to use as a parameter to filter setup data.
7. Submit the process to export the setup data. However, you can optionally, and only when strictly required, change
the import sequence of the business object or exclude business objects from export.
a. Select the business object and click the Import Sequence attribute until it becomes editable. Enter a unique
value for the import sequence. Move out of the field and dismiss the warning after confirming you are aware of
the impact.
b. Select the business object and click the Export attribute until it becomes editable. Deselect the Export check
box. Move out of the field and dismiss the warning after confirming you are aware of the impact.
c. Repeat the same step for any other object as needed.
8. Click Next to continue. As the default, the process runs as soon as it's submitted, however, you can also schedule it
at a specific time.
9. Click Submit to start the export process. A warning message displays indicating that the configuration package
definition can no longer be modified after submitted. Click Yes to continue. The new configuration package will be
listed at the beginning of the table.
10. Monitor the process until it completes. Click Refresh on the Import and Export Processes table to refresh the
process status.
11. Once it completes successfully, download the setup data file. Select the export process, click Download and then
select Download Configuration Package. Save the file.
12. Review the results details for any required post-export task:
a. Select the export process, and click the status. The Export and Import Process Results page opens.
b. From the Status menu, select Manual Export Pending. The tasks whose setup data is not migrated by the
export process is listed and you need to plan to perform those manually in the target environment.
13. If setup data in the implementation project changes in the future, you can export the setup data using the same
configuration package, rather than creating another, as long as the setup data scope does not change.
a. Select the appropriate configuration package and then select Export Setup Data.
b. Monitor the process following the same steps described previously.
Importing Setup Data from Configuration Packages:

Procedure
Video
Watch: This video tutorial shows you how to import setup data from configuration packages. The content of this video is also
54
Projects
You can import setup data for an implementation project.
Import Setup Data from Configuration Packages

To import setup data from a configuration package, follow these steps.
1. Sign in to the environment where the setup data will be imported. Select Navigator > Setup and Maintenance
work area to open the Setup page. You need the Application Implementation Consultant role to import setup data.
2. From the Setup page, open the panel drawer and select Manage Configuration Packages to open the Manage
Configuration Packages page.
3. From the Actions menu, select Upload or click the Upload icon to first upload the setup data file that was
generated to export the implementation project's setup data.
4. Click Get Details to obtain and verify that the selected setup data file is correct. If needed, click Update to select a
different file.
5. Click Submit to start the process.
6. Once the process is submitted, the configuration package will be listed at the beginning of the table. Select the
configuration package and monitor the process of the upload process that appears in the Export and Import
Processes table.
7. Once the upload process completes successfully, it's ready for import. Select the upload process and click Import
Setup Data. The Import Setup Data page opens.
8. As the default, the process pauses on each business object that fails with errors allowing you to take appropriate
corrective actions before it continues. You can allow the process to run without pausing on errors, but you assume
the risk that additional setup data may not be imported if any errors occur.
9. Click Next. As the default, the import process also pauses for any setup for manual tasks that are required during
import. From the Type list of values, select the Manual data loading option to review the list of all the setup data
you need to prepare for. Review the check mark listed under pause to identify the setup data required during import.
10. Click Next. As the default, the process runs as soon as it's submitted, however, you can also schedule it at a
specific time. Click Submit to start the process.
11. If applicable, a list of required setup data that must be entered manually prior to import appears. Make sure the
appropriate setup data is entered by performing these tasks and then click Yes to start the import process.
12. Monitor the process until it completes. The latest import process will be shown at the beginning of the Export and
Import Processes table for the configuration package.
13. If any setup data is required during import, the process pauses with the status of User Action Required.
a.Click the status of the process to review the details of what setup data is required.
b.In the Object Details table, select User action required from the Status list of values.
c.Enter the appropriate setup data by performing each task. Click Go to Task.
d.Once you entered the setup data for all relevant tasks, return to the Export and Import Process Results page
and resume the process.
e. Click Submit to continue and then confirm that you entered the requested setup data by clicking Yes.
f. The import setup data process resumes.
14. Continue monitoring the process until it completes. Click Refresh in the Import and Export Processes table to
refresh the process status.
15. Once it completes, review the results details. Check for any errors and any required post-import task.
a. Select the export process, and click the status. The Export and Import Process Results page opens.
b. Review the status of the process and verify if it completed successfully.
55
Projects
c. If successful, check for post import tasks, by opening the Status menu and select Data Loading Pending.
The tasks whose setup data is not migrated by the import process are listed and you must plan to perform
those manually in the environment.
d. If completed with errors, open the Status menu and select Completed with Errors. Review the status details
of the corresponding objects and take the appropriate corrective action. Once you fix the errors, you can
resubmit the import process again.
FAQ's for Exporting and Importing Setup Data for

Implementation Projects
When does it make sense to create multiple configuration packages
from the same implementation project?
You can use the same implementation project to create many configuration packages. It's only useful to do so if the
list of tasks in the implementation project has changed, or tasks and their associated business objects in the selected
implementation project define the setup export or import definition for the configuration package. It's also useful if you use an
export or import definition for different configuration packages.
What happens if I modify a configuration package that I recently

created?
You can only modify configuration packages that display a status of definition in progress. The configuration package
definition is locked once you submit it for export or upload it for import. If you want to keep making modifications to a
configuration package you can save it until you are ready to submit it for export.
How can I export or import an implementation project without the

associated setup data?
When you create a configuration package select the option to export the setup task list only. When this configuration package
exports and imports, only the task list from the selected implementation project is transported.
How can I view and print any errors generated by an import or export
process?
Download and then view or print the Export Results Report or the Import Results Report for the relevant process.
56
Projects
How can I view the associated business object hierarchy?

The task list generated for an implementation project not only drives the implementation tasks but also determines what setup
data exports and imports during deployment to another instance. You can see the list of business objects representing the
setup data by selecting the business objects view from the Manage Implementation Projects page. The business object view
shows the business objects associated with the tasks. This gives you an insight into the order of the business objects, and
therefore the setup data that exports and imports when you deploy the implementation to another instance.
How can I exclude any business objects from exporting or change

the import sequences?
By default, all business objects related to the task list of the implementation project used in the configuration package are
exported. You can exclude any business objects from exporting by deselecting the business object from the default list. If you
deselect a business object then the business object data are not exported or available for subsequent import. The default
import sequences of the business objects are based on the order of the related tasks in the implementation project. You can
change the import sequence when creating a configuration package. As a result, the order in which the business objects
export and import changes. Use caution when excluding business objects or changing their import sequences because data
dependencies among the business objects might exist, which could result in failures during import.
How can I cancel an export or import offering setup data process that
I submitted?
Select the process you want to cancel and click Cancel Process. Once you confirm to cancel the process, it completes
processing the business object that already started and does not process the remaining business objects. The process status
is changed to Canceled and you are not able to resume the process.
What happens if I upload a different version of the same configuration

package?
The previously uploaded version is overwritten with the newly uploaded version.
What happens if my import process remains in the User Action

Required status?
An import process is set to User Action Required when the process has paused because certain data must be imported.
This occurs when a standard service to automate the setup data export and import for a business object (marked as required
for other data) is not available. You have to migrate or enter the data manually using another application or process external
to the Setup and Maintenance Work Area. Review the process results to identify the business object and resume the process
once you have taken appropriate actions to externally import the required data.
57
Projects
How can I understand if an export or import setup data process

is making progress and know what business object is currently
processing?
To identify the business object that an export or import setup data is processing at any time while the process is running:
1. Navigate to the Manage Configuration Packages or Manage Export and Import Processes page.
2. Locate the export or import setup data process you are interested.
3. Navigate to the export and import process results page by clicking on the Status column.
4. Look at the Total of Objects Processed that appears in the Object Details table to identify how many objects
have processed. Refresh the page and review this value again to see any progress.
The name of the business object currently being processed displays in the table.
For an offering based export or import process initiated from the Setup page:
1. Select the corresponding offering from the Setup page.

2. Select the export or import process you are interested in.
3. Navigate to the export and import process results page by clicking on the status column.
4. Look at the Total of Objects Processed that appears in the Object Details table in order to identify how many
objects have been processed so far. Refresh the page and review this value again to see any progress.
The name of the business object currently being processed displays in the table.
Why does the configuration package contain some scope values by

default?
If you have selected any scope values when performing an assigned implementation task, then the selected values are
preselected as candidates for filtering setup during export and import. Some application core tasks, such as tasks for defining
profile options, have parameters defined that you can use as setup filters and are preselected as filter candidates for export
and import. You can remove any of these preselected values when you are creating the configuration package. You can also
add more scope values for export and import purposes only.
58
Using Functional Setup Manager Comparing Setup Data
10 Comparing Setup Data
Comparing Setup Data: Understanding Setup Data

Comparison
During the applications lifetime, you must maintain your applications, adopting new functionality and modifying the behavior of
your existing applications to meet your business requirements. To do so, you enter new or update existing setup data. These
modifications are usually made in a test environment where they are certified before they are migrated to the production
environment.
You can use Setup data comparison to learn how data for a given implementation has changed over time. For instance:
• Prior to importing the setup data into the production environment, you would want to identify the setup data changes
that may occur if the new configuration is imported, to prevent undesirable overwrites. To do so, compare the setup
data prior to importing and based on the results, decide whether to import the new configuration or not.
• In other cases, you may also want to compare the setup data to identify the changes made over time, to identify the
potential causes of your application's new behavior or an issue.
• An implementation may have been done in phases and some of the original configuration modified. You can track
the changes over time through different versions of the same configuration package, or different configuration
packages.
Once you identify the setup data differences or discrepancies, you can decide how to resolve them. You can import the setup
data from the configuration package into the environment if the implementation matches what is in the configuration package.
You can also resolve the discrepancies for a given record or business object by editing the setup data through the relevant
task.
The setup data comparison functionality helps you speed up the process of identifying the differences among one or multiple
business objects relevant to a configuration. The comparison identifies which records are common to either configuration
packages' alternate key matching. The report shows any data differences in the records with matching alternate keys. If
alternate keys are not defined for the business object, then the entire data record is compared in the report.
Note: Alternate key definition depends on the specific design of the business objects owning product or
product family, and is not controlled by the application.
You can compare setup data for an offering, functional area or between two different configuration packages or two versions
of the same configuration package generated for an implementation project.
Comparison always requires two sources of the same configuration to compare setup data. However, if you want to compare
setup data before import while submitting an import offering setup data process, you need not explicitly specify the sources.
The comparison takes the configuration package for import as one source and the environment where you are importing the
setup data as the second source.
59
Setup Data Comparison: Explained

Setup data comparison identifies the differences between the setup data of two configuration packages, or two different
versions of the same configuration package.
Setup Data Comparison: How It Works

To compare the setup data, the comparison process
• Identifies the business objects that contain setup data in each source (configuration package or version).
• Identifies the business objects common to both sources. The setup data for business objects that are not common
to both sources is not compared.
• For each of the common business objects, the data records are compared by using the alternate keys and classified
in 3 categories:
◦ A record in which alternate key values match in both sources are classified as a common record.
◦ A record in source 1 without a match in source 2 is marked as a discrepancy and reported to exist Only in
source 1.
◦ A record in source 2 without a match in source 1 is marked as a discrepancy and reported to exist Only in
source 2.
Note: If no alternate keys are defined for the business object or if the alternate key is not unique, then the
entire record is compared.
• Then identifies the discrepancies in the common records by comparing each attribute value of the common data
records:
◦ If one or more of the attribute values differ, a discrepancy is reported and classified as In Both With
Mismatch. This indicates that the setup data that was updated.
◦ If all the attribute values match between both sources, there is no discrepancy and the record is classified as
identical.
Identifying Setup Data Changes Made Over Time for an

Offering or Functional Area: Explained
You can identify the modifications that have occurred over time for an offering or functional area by comparing a previous
exported version of the setup data against the current setup data in the environment. The exported version must exist or first
be uploaded in the environment before initiating the comparison process. To ensure the accuracy of the comparison results,
the comparison process first exports the existing setup data and generates a fresh version of the same configuration before
comparing it. Any setup data filters in the selected previously exported version are applied to the fresh version.
60
Identifying Setup Data Changes Made Over Time for an

Offering or Functional Area: Procedure
You can identify the modifications that have occurred over time for an offering or functional area by comparing a previous
exported version of the setup data against the current setup data in the environment.
You need the Application Implementation Consultant role to export setup data.
Comparing Setup Data for an Offering or Functional Area

To compare setup data for an offering or functional area, follow these steps:
1. Click Navigator > Setup and Maintenance work area to open the Setup page.
2. Select the offering whose setup data you want to compare.
3. Select Compare Setup Data > Create New from the Actions menu for the offering or functional area.
4. Select the configuration package that contains the prior setup data version you want to compare against the setup
data currently available in the environment. If the configuration package is not available in the environment, click
Upload new to upload it.
Note: An error message appears if the selected configuration package does not contain setup data for
the corresponding offering or functional area.
5. Optionally, you can edit the default process name for easy identification.
6. Click Submit to initiate the process. Dismiss the confirmation message.
7. Monitor the process progress until it completes. Select Compare Setup Data from the Actions menu. The latest
process appears first.
8. Once it completes, you can select the process name to view the complete results.
◦ The objects with setup data discrepancies are listed by default.
◦Select the Only in Configuration 1 column to determine which records do not exist in the environment
and therefore, must be created in the production if this configuration package is imported. Select the
corresponding business object to review.
◦ Select the In Both with Mismatch column to review the records that exist in both the configuration package
and the environment, but have different attribute values. Select the corresponding business object to review.
The report contains two rows for each matching record: The first row shows the values from the configuration
package and the second row shows the values from the environment. Values are only presented for the
attributes with discrepancies, so they can be easily identified.
◦ Select the Only in Configuration 2 column to determine which records exist only in the environment and not
in the configuration package. The import process does not delete any records and therefore these records
remain untouched in the environment. Select the corresponding business object to review.
9. Review the discrepancies and decide whether or not to make modifications to the current setup data in the
environment according to your business needs.
61
Comparing Setup Data for Implementation Projects:

Explained
You can identify the modifications that have occurred over time for any configuration managed through implementation
projects by comparing any two configuration packages or two versions of the same configuration package relevant to the
implementation project. To compare setup data of an existing configuration package with data in a current environment,
export the setup data for the current environment into a new configuration package or a new version prior to initiate the
comparison.
Comparing Setup Data Using Configuration Packets:

Procedure
Video
Watch: This video tutorial shows you how to compare setup data using configuration packets. The content of this video is also
To compare setup data of an existing configuration package with data in a current environment, export the setup data for the
current environment into a new configuration package or a new version prior to initiate the comparison.
You need the Application Implementation Consultant role to export setup data.
Comparing Configuration Packages

To compare configuration packages, follow these steps:
1. Click Navigator > Setup and Maintenance work area to open the Setup page.
2. Select Manage Export and Import Processes from the panel drawer in the Setup and Maintenance work area.
3. Verify that both configuration packages are available and then select Compare on the Export and Import Processes
page. You can also compare two available versions of the same configuration package.
4. You can view an existing comparison or create a new one from the Comparison Process page.
5. To create a new comparison, select Create and select the two configuration packages for comparison. Make sure
to select the correct Process Dates.
6. Name the comparison process for easy identification, select Submit, and then refresh the Comparison Process
page to monitor the progress of the comparison until it completes. You can view the process results while it is in
process by selecting the In Process status message.
7. Once the process is complete you can select the process name to view the complete results.
62
8. The comparison results are displayed. The two configuration package names appear in the Compared Configuration
Packages region. The objects with setup data discrepancies are listed by default.
a. Select the Only in Source 1 column to determine which records do not exist in the configuration package
selected as source. Select the corresponding business object to review.
b. Select the In Both with Mismatch column to review the records that exist in both sources but have different
attribute values. Select the corresponding business object to review. The report contains two rows for each
matching record: the first row shows the values from the first source and the second row shows the values
from the second source. Values are only presented for the attributes with discrepancies, so they can be easily
identified.
c. Select the Only in Source 2 column to determine which records only exist in the configuration package
selected as source 2. Select the corresponding business object to review.
9. You can click Download to download the report. Once you finish reviewing the discrepancies, you can decide which
configuration package to use, or what data to modify in the current environment.
63
64
Using Functional Setup Manager Reference
11 Reference
Reference: Moving Functional Setup Data Using the

Command-Line
Functional Setup Manager enables users to implement and configure all Oracle Fusion Applications as well as to move the
setup data across instances. This is generally done using Functional Setup Manager export and import functionality built
into the application. It is strongly recommended that you use and access this functionality from the Manage Configuration
Packages page. As an alternate method, an Application Implementation Consultant user can move the setup data using the
export and import functionality accessed from a command line. Be aware that some capabilities and restrictions may appear
when using command-line functionality.
Moving the data requires the following steps:
1. Set up prerequisites
2. Export data from the source
3. Import data on the target
Moving setup data from the source environment to the target

environment using command-line scripts: Set up Prerequisites
Before you move the Functional Setup Data to the target environment, you must identify the implementation projects used
to enter and define the setup data in the source environment. Ask your Application Implementation Consultant user to
gather the codes of the implementation projects. You can gather the implementation codes using Oracle Fusion Functional
Setup Manager or SQL. To obtain a list of the implementation codes using SQL, use the following query: SQL> SELECT
impl_project_name, short_name from asm_impl_projects_vl;
To gather the implementation codes using Oracle Fusion Functional Setup Manager:
1. Sign in to Oracle Fusion Applications with a user account that is provisioned with the necessary role, such as the
predefined Application Implementation Consultant role. Contact your security administrator for details.
2. From the Administration menu in the work area of Oracle Fusion Applications, select Setup and Maintenance.
3. In the Tasks pane, under the Implementations group, click Manage Implementation Projects.
4. Click an implementation project name in the Search Results. The Implementation Project page is displayed.
5. In the Basic Information section, copy the value for the Code field. Make sure to perform steps 4 and 5 for each
project you want to export.
6. Ensure all the Managed Servers are started in the environment.
65

environment using command-line scripts: Export data from the
source
To export the data from the source:
1. Set the USER_MEM_ARGS variable as follows: export USER_MEM_ARGS="-Xms256m -Xmx1024m -

XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=1024m"
2. For either UNIX or Windows, at an operating system command prompt, navigate to the location of the
fsmConfigurationPackageExport executable:
(UNIX) ATGPF_ORACLE_HOME/fsm/scripts
(Windows) ATGPF_ORACLE_HOME\fsm\scripts
ATGPF_ORACLE_HOME is located under the fusionapps Oracle Fusion Middleware home directory
(FA_MW_HOME).
3. Enter fsmConfigurationPackageExport.sh (for UNIX) or fsmConfigurationPackageExport.cmd (for Windows), using
the following syntax:
fsmConfigurationPackageExport
commonDomainInternalUrl=http://host.domain:port
jdbcUrl=jdbc:oracle:thin:@DB_host_name.domain/sid
fusionRuntimeSchema=fusion_runtime
fusionRuntimeSchemaPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
fsmUsername=user
fsmPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
implementationProjectCode=IMPLEMENTATION_PROJECT_CODE_TO_EXPORT
configurationPackageFile=USER_HOME/cp.zip
logFile=USER_HOME/log_file
jpsConfig=COMMON_DOMAIN_HOME/config/fmwconfig/jps-config-jse.xml
mwHomeLoc=MW_HOME
atgpfHomeLoc=ATGPF_ORACLE_HOME
[pollingInterval=interval]
[pollingLimit=limit]
The description of the options for the fsmConfigurationPackageExport command follows:
66
Option Description Optional or Mandatory?
-commonDomainInternalUrl The CommonDomain domain internal URL Mandatory

on the source registered in Oracle Topology
Manager in the format of Internal_ Server_
Protocol: / / InternalServer Host:Internal_
Server_Port.

-jdbcUrl The JDBC URL in the format of jdbc: oracle: Mandatory

thin:@//DBhost_ name. domain/sid to the
connect to the source database.

-fusionRuntimeSchema The Oracle database schema name (user Mandatory

name) to log in to the source database. This
value should always be fusion_ runtime.

-fusionRuntimeSchemaPasswordFile The absolute path to the password file, Mandatory

which contains the schema password to log
in to the source database.

-fsmUsername User name to log in to Oracle Fusion Mandatory

Functional Setup Manager that has
Application Implementation Consultant job
role.

-fsmPasswordFile The absolute path to the password file, Mandatory

which contains password to log in to

-implementationProjectCode The implementation project code that must Mandatory

be exported from the source instance.

-configurationPackageFile The absolute path to the configuration Mandatory

package ZIP file to save exported data.

-logFile The absolute path to the source log file. Mandatory

-jpsConfig The absolute path to the jps-config. xml file. Mandatory

mwHomeLoc The absolute location of the source Oracle Mandatory

Fusion Applications Middleware Home
(FA_MW_HOME). FA_MW_HOME is located
under the appbase Applications base
directory (APPLICATIONS_ BASE).

-atgpfHomeLoc The absolute location of the source Mandatory

Applications Core Oracle Home (ATGPF_
ORACLE_HOME). ATGPF_ ORACLE_HOME
is located under the fusionapps Oracle
Fusion Middleware home directory
(FA_MW_HOME).

67
-clientPolicy The Web Service Client Policy to be used Optional

to open the Oracle Enterprise Scheduler
Web service to submit the export process.
The default is oracle/wss10_ saml_ token_
client_ policy.

-pollingInterval The polling interval to be used to periodically Optional

check if export process is complete. The
default is 5 seconds.

-pollingLimit The polling limit to be used until reached to Optional

check if the export process is complete. The


environment using command line scripts: Import data on the target
The fsmConfigurationPackageImport script moves the setup data for an implementation to a target instance. To import the
data on the target:
1. For either UNIX or Windows, at an operating system command prompt, navigate to the location of the
fsmConfigurationPackageImport executable:
(UNIX) ATGPF_ORACLE_HOME/fsm/scripts
(Windows) ATGPF_ORACLE_HOME\fsm\scripts
ATGPF_ORACLE_HOME is located under the fusionapps Oracle Fusion Middleware home directory
(FA_MW_HOME).
2. Enter fsmConfigurationPackageImport.sh (for UNIX) or fsmConfigurationPackageImport.cmd (for Windows), using
the following syntax:
fsmConfigurationPackageImport
commonDomainInternalUrl=http://host.domain:port
jdbcUrl=jdbc:oracle:thin:@DB_host_name.domain/sid
fusionRuntimeSchema=fusion_runtime
fusionRuntimeSchemaPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
fsmUsername=FUSION
fsmPasswordFile=USER_HOME/fusionRuntimeSchemaPassword.txt
configurationPackageFile=USER_HOME/cp.zip
logFile=USER_HOME/cpImport.log
68
jpsConfig=COMMON_DOMAIN_HOME/config/fmwconfig/jps-config-jse.xml
mwHomeLoc=MW_HOME
atgpfHomeLoc=ATGPF_ORACLE_HOME
The description of the options for the fsmConfigurationPackageImport command follows:
-commonDomainInternalUrl The CommonDomain domain internal URL Mandatory

on the source registered in Oracle Topology
Manager in the format of Internal_ Server_
Protocol: / / InternalServer Host:Internal_
Server_Port.

-jdbcUrl The JDBC URL in the format of jdbc: oracle: Mandatory

thin:@//DBhost_ name. domain/sid to the
connect to the source database.

-fusionRuntimeSchema The Oracle database schema name (user Mandatory

name) to log in to the source database. This
value should always be fusion_ runtime.

-fusionRuntimeSchemaPasswordFile The absolute path to the password file, Mandatory

which contains the schema password to log
in to the source database.

-fsmUsername User name to log in to Oracle Fusion Mandatory

Functional Setup Manager that has
Application Implementation Consultant job
role.

-fsmPasswordFile The absolute path to the password file, Mandatory

which contains password to log in to

-implementationProjectCode The implementation project code that must Mandatory

be exported from the source instance.

-configurationPackageFile The absolute path to the configuration Mandatory

package ZIP file to save exported data.

-logFile The absolute path to the source log file. Mandatory

-jpsConfig The absolute path to the jps-config. xml file. Mandatory

mwHomeLoc The absolute location of the source Oracle Mandatory

Fusion Applications Middleware Home
(FA_MW_HOME). FA_MW_HOME is located
under the appbase Applications base
directory (APPLICATIONS_ BASE).

69
-atgpfHomeLoc The absolute location of the source Mandatory

Applications Core Oracle Home (ATGPF_
ORACLE_HOME). ATGPF_ ORACLE_HOME
is located under the fusionapps Oracle
Fusion Middleware home directory
(FA_MW_HOME).

-clientPolicy The Web Service Client Policy to be used Optional

to open the Oracle Enterprise Scheduler
Web service to submit the export process.
The default is oracle/wss10_ saml_ token_
client_ policy.

-pollingInterval The polling interval to be used to periodically Optional

check if export process is complete. The

-pollingLimit The polling limit to be used until reached to Optional

check if the export process is complete. The

70

Applications Cloud Using Functional Setup Manager

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Applications Cloud Using Functional Setup Manager

Uploaded by

Copyright:

Available Formats

Oracle

Release 13 (update 17D)

Release 13 (update 17D)

Authors: Sandesh Posa, Mary Kalway

4 Managing Offering Setup 11

5 Managing Setup Using Implementation Projects 15

6 Managing Setup Using Alternative Processes 25

7 Exporting and Importing Setup Data: Overview 31

8 Exporting and Importing Offering Setup Data 45

9 Exporting and Importing Setup Data for Implementation Projects 51

10 Comparing Setup Data 59

Oracle Applications Help

Using Applications Help

• Training: Take courses on Oracle Cloud from Oracle University .

Access to Oracle Support

Comments and Suggestions

Functional Setup Manager: Overview

• Standardized application configuration and setup experience

◦ 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

Who Uses the Functional Setup Manager: Points to

Functional Setup Manager Components: How They Work

Functional Setup Manager Work Areas: How They Work

My Enterprise Work Area Group

Setup and Maintenance Work Area

Implementation Process: Explained

• Managing Offering Setup

Planning Your Implementation: Explained

Reviewing Your Subscription: Procedure

Entering Promotion Codes: Procedure

Planning Your Implementation: Procedure

Review Setup Information

Configuring Offerings: Explained

Configuring Offerings: Procedure

Opting into New Features After Upgrade: Explained

Opting into New Features After Upgrade: Procedure

◦ Use Learn More to find additional help topics.

Reviewing Opt In History: Explained

Reviewing Opt In History: Procedure

Reviewing Opt In Change History

Review the Opt In History page for the following information:

The page displays the most recent change first.

4 Managing Offering Setup

Managing Offering Setup: Explained

Tasks with Scope

Managing Offering Setup: Procedure

Setting Up Offerings with Scope: Video

5 Managing Setup Using Implementation

Managing Setup Using Implementation Projects: Explained

Generating a Task List

Modifying a Task List

Creating Implementation Projects: Procedure

Create an Implementation Project

Modifying Implementation Projects: Procedure

Assigning Setup Tasks: Explained

Assigning Setup Tasks: Procedure

Entering Setup Data Using Assigned Tasks: Explained

Tasks with Scope

• Which tasks are the predecessors of a given task.

Setting Task Status

Entering Setup Data Using Assigned Tasks: Procedure

To enter setup data using assigned tasks, follow these steps: