Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

Functional Setup Manager (FSM): Export and Import Best Practices (Doc ID 1905704.1)

In this Document

Purpose
Scope
Details
References

APPLIES TO:

Oracle Fusion Application Toolkit - Version 11.1.8.0.0 and later

Oracle Fusion General Ledger Cloud Service - Version 11.1.11.1.0 to 11.1.11.1.0 [Release 1.0]
Information in this document applies to any platform.

PURPOSE

The purpose of this document is to share Functional Setup Manager (FSM): Export and Import Best Practices

SCOPE

Support and Customer

DETAILS

Create and verify setup in test instance

Create the new setup in the test instance.

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

Publish to production

Prepare to move to production

Ensure that the test and production instances are at the same release level.
Use offering reports from the Getting Started page to plan your strategy for moving from the test instance to the
production instance.
Review setup task list and task reports from the Getting Started 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 (i.e., business object) dependencies based on Oracle delivered offering task list
hierarchy. Avoid making changes to the default business object sequence.
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.

Export from Test

Export verified data from the test instance.

Export only one offering at a time.

Use Scope filtering functionality to limit the data being exported when performing incremental setup.

Download the resulting configuration package file.

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. See Exporting and
Importing Setup Data: Explained in the FSM User’s Guide for more information on comparison reporting.

Import into Production

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.

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.
Perform tasks marked for pre-import.
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.
Review setup in the production instance once import completes.

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.

REFERENCES

NOTE:1992613.1 - Concurrent Implementation Maintenance in Functional Setup Manager: Points to Consider

Didn't find what you are looking for?