Functional Setup Manager

Functional Setup Manager is a key integration option with export and import processes that help in migrating setup data from one instance to another.

Applications also provide comma-separated values (CSV) file export and import, which helps to enter or update a large volume of setup data but is insufficient for managing setup task UIs individually.

For more information, see Using Functional Setup Manager.

Key Features

• Used only for setup data.
• Supports exporting and importing an entire offering, functional area, or implementation project.
• Supports the filtering of setup data to limit the export that matches the criteria.
• Provides review of setup data before or after the export or import process using the Setup Data Reports and Comparison Reports.
• Supported by all Oracle Fusion Cloud Supply Chain (SCM) & Manufacturing applications.
• Supports both automated and manual data-export processes, giving flexibility to users based on their specific requirements and IT infrastructure.
• Supports only XML and CSV formats.

Best Practices

• Create and verify the setup data in a test instance.
• Ensure that the test and production instances are at the same release level.
• Use scope-filtering functionality to limit the data being exported when performing an incremental setup.
• Use comparison reports to review potential setup changes before submitting the import process.
• Review setup in the production instance once import completes.
• Implement only the offering required for the business need to prevent unnecessary data export.
• Export only one offering at a time.
• If you make any configuration changes in the production environment, ensure you make the same changes in the test environment so that the changes will be carried over during the next migration.
• Make sure the functional security associated with the roles exists in both source and target instance.

Constraints

• Not suitable for real-time data extraction.
• Import doesn't delete the records in the target instance if they don't exist in the configuration package. You must delete these records or make deprecate them manually, if necessary.
• Some setups are prerequisites for other setups and 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.
• You can't combine the export and import processes of different methods. When an offering or functional area is exported, that setup data can only be imported using the same offering or functional area.

Note: Functional Setup Manager isn't a typical integration option but is a way to move your setup data from a test instance to a production instance after your integration has completed end-to-end testing. It enables you to use export and import to quick-start functional setup at different instances and to validate a setup by reviewing setup data reports.