About Connecting EPM Cloud Environments

Overview

Service Administrators can connect multiple EPM Cloud environments of the following types:

Planning
Financial Consolidation and Close
Tax Reporting
Account Reconciliation
Profitability and Cost Management
Narrative Reporting
Strategic Workforce Planning

Once Service Administrators set up the connections, users who have access across EPM Cloud environments can navigate across them from a single access point with one login. Also artifacts such as forms and dashboards, from across environments can be co-mingled within a cluster or within tabs on a card in navigation flows. Artifacts in the target environment are accessible based on the user's role.

Note:

You can also connect directly Oracle Analytics Cloud Enterprise Edition or Professional Edition 5.6 to EPM Cloud Platform, provided you have both services. When you've configured the connection, you can visualize data from EPM Cloud business processes in Oracle Analytics Cloud. You no longer have to model EPM data in a metadata repository (RPD) file to create visualizations and dashboards in Oracle Analytics Cloud.

For more information, see the Oracle Analytics Cloud documentation.

Which EPM Cloud Environments can I Connect?

The source environment is the environment from which you're creating the connection. The target environment is the environment to which you're connecting from the source environment.

You can connect these source environments (these environments can also be target environments):

Planning
Financial Consolidation and Close
Tax Reporting

Source environments can also connect to these target environments (these environments can't be source environments):

Account Reconciliation
Profitability and Cost Management
Narrative Reporting
Strategic Workforce Planning

What are the Ways I can Connect to Other EPM Cloud Environments?

Toggle between the source environment and the target environment on the Navigator menu. See your source environment documentation for details.
Customize navigation flows in the source environment to access clusters, cards, and artifacts in other target environments from the Home page. See your source environment documentation for more details.
Use direct URLs to seamlessly integrate connected environments. See Using Direct URLs to Integrate Connected Environments.

Considerations

Only Service Administrators create cross-environment connections.

Users click a navigation link to open the linked environment. Access within the linked environment is determined by the predefined role and access permissions, if any, assigned to the user.
For cross-environment navigation to be seamless, all environment instances to which cross-environment navigation flows are setup must belong to the same identity domain.

Note:

If the target and source environment instances are not on the same identity domain, then you'll not be able to establish a connection between them.
Service administrators cannot configure cross-environment connections using corporate SSO (identity provider) credentials.

If your environments are configured for SSO, ensure that identity domain credentials are maintained for the Service Administrators who configure cross-environment connections.
Migrating cross-environment connections between test and production environments can cause issues in certain use case scenarios. For more information, see your source environment documentation.
Vanity URLs are not supported in cross-environment connections.