My Oracle Support Banner

Utilizing FSM To Move Configuration Data From One Environment To Another (Doc ID 2617995.1)

Last updated on DECEMBER 30, 2021

Applies to:

Oracle Fusion Financials Common Module Cloud Service - Version 11.13.19.07.0 and later
Information in this document applies to any platform.

Goal

Trying to determine whether or not the FSM can be used to move data from dev environment to prod.

There are three assumptions about the limitations of the FSM:
1. Cannot pin point exactly what to move from one environment to another – so if only part of the configs are ready for migration, cannot separate them out.
2. Not all configs “live within FSM” (like scheduled processes and custom roles) so not all configs get migrated over.
3. FSM Migration doesn’t necessarily replace “bad configs” but just adds to configs that are already there depending on what it is.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.