Considerations When Migrating Cross-Subscription Connections

Oracle recognizes that it's common practice for administrators to try out new features, such as connecting subscriptions, on test environments and then migrate to production environments. However, in doing so, it could cause some issues after migration. We'll describe some use case scenarios that you need to be aware of.

In the following scenarios, assume you have subscriptions for Financial Consolidation and Close and Planning.

Use Case Scenario 1: Test to Production

In this scenario, the administrator has defined a connection between the Planning test instance and the Financial Consolidation and Close test instance. The administrator then uses this connection to build a navigation flow in the Planning test environment that refers to a card in the Financial Consolidation and Close test environment. If the administrator chooses to export all artifacts in the test environment, the export will include connections and navigation flows, including the connection to the Financial Consolidation and Close test instance.

When the administrator imports this snapshot into the Planning production environment, they will have an undesirable connection to the Financial Consolidation and Close test instance from the Planning production environment.

When migrating connections from test environments to production environments, it's important to ensure that any connections that were defined in the test environment are changed to point to the corresponding production instances.

Use Case Scenario 2: Production to Production or Test to Test

This scenario doesn't have any caveats.

Use Case Scenario 3: Production to Test

In this scenario, the administrator might be trying to replicate an issue on a test instance. In this case it's important that the administrator remember to change any connections that point to a production instance to a test instance. Connections that point to a production instance from a test environment could inadvertently tamper with production.