1. Using Functional Setup Manager
  2. Key Information About Setup Data Export and Import Processes

Key Information About Setup Data Export and Import Processes

Use the information in this topic to effectively manage the setup data export and import processes.

Here are the key components of the setup data export and import process.

  • Setup Business Objects

  • Configuration Packages

  • Scope to Filter Exported Setup Data

  • Importing Feature Opt-In

  • Setup Data Update Rules During Import

  • Import Sequence of Setup Data

  • Export and Import Process Results

Setup Business Objects

Setup business objects are the logical representations of setup data. The export and import processes use these business objects and their associated web services to read and write the appropriate set of setup data from source to the target environments respectively.

Configuration Packages

A configuration package is the medium used to move setup data from one environment to another. When you export setup, a configuration package is created which includes the following:

  • A list of setup tasks based on the offering, functional area or implementation project you used for the export process.

  • The business objects associated with those tasks.

  • Exported setup data of those business objects

After an export process runs successfully, you can download the configuration package as a .zip file. You can then move this configuration package to the environment where you plan to import the same setup, upload the file, and run the import.

This graphic describes the process of moving setup data from one environment to another using configuration packages, which is explained in the topic.

Scope to Filter Exported Setup Data

When a business object is exported, all its setup data (except the ready to use data that's not yet modified) is exported by default. You may optionally select one or more Scope values to filter setup data of the business objects and limit the exported data. The resulting configuration package from that export process contains only the setup data that matches the Scope criteria you specified. However, if you include the ready to use setup data in scope, it doesn't get exported unless it was previously modified. This condition applies to the following ready to use setup data:

  • Application Taxonomy

  • Application Reference Data Set

  • Application Reference Data Set Assignment

  • Application Lookup

  • Data Security Policy

  • Application Tree Structure

  • Application Tree Label

  • Application Tree

  • Application Flex Value Set

  • Application Descriptive Flexfield

  • Application Extensible Flexfield

  • Application Key Flexfield

Additionally, make sure that you deploy the ready to use setup data for the following business objects:

  • Application Descriptive Flexfield

  • Application Extensible Flexfield

  • Application Key Flexfield

Note:

  • You can't migrate the translation data for these business objects using the Export to CSV File or Import from CSV File functionality. Instead, use the standard export or import functionality that uses XML files. For details, see Export Setup Data Using Offering or Functional Area.

  • You can never export user level profile values.

Importing Feature Opt-In

When you export an offering or a functional area, the configuration package includes the opt-in configuration of all their dependent functional areas and features as they were set in the source environment at the time of export. However, the import of the same configuration package doesn't automatically import the opt-in configurations to the target environment.

You may choose to import the opt-in configuration from the source to the target when you import the configuration package. The import process enables the dependent functional areas and features that were enabled in the source but aren't enabled in the target. The opt-in configuration of any other dependents in the target remains unchanged.

Note: This option isn't available when you use an implementation project to export and import setup data.

Setup Data Update Rules During Import

When you import a configuration package to the target environment, setup data in the target is modified as follows:

  • If a record exists in the configuration package but doesn't exist in the target, then import creates the record.

  • If a record doesn't exist in the configuration package but exists in the target, then import doesn't modify the record in the target.

    Note: Import doesn't delete the records in the target that don't exist in the configuration package. You must delete these records or make them obsolete manually, if necessary.

  • If a record exists both in the configuration package and in the target, then:

    • If all attribute values are the same, import doesn't modify the record in the target.

    • If values of any attributes of the record are different, then import updates the record in the target with the values in the configuration package.

Import Sequence of Setup Data

Some setups are prerequisites for other setups and thus, have data dependencies. Therefore, the sequence in which setup data is imported from a configuration package is important to prevent any failure due to data dependency.

The sequence of the tasks within the offering, functional area or implementation project, which you used during export to create the configuration package, determines the sequence in which their related business objects, and consequently, the setup data are imported. The following business objects, on the other hand, are exceptions to the default task-based sequence rule. They're always exported and imported before any other business objects in the sequence specified in this table:

Business Object Name

Business Object ID

Application Taxonomy

FND_APP_TAXONOMY

Application Reference Data Set

FND_APP_REFERENCE_DATA_SET

Application Reference Data Set Assignment

FND_APP_REFERENCE_DATA_SET_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 and Import Process Results

You can review and analyze results of setup export and import processes. The results show what setup data was exported or imported, and are listed in the order in which the business objects were processed. The results also include information about any errors encountered during the export or import process to help you analyze and resolve those errors. You can download the information about the process results in a file to review them offline.