Handling Issues with Navigation Flows

This section details information on fixing common errors while working with Navigation Flows (cross-environment connections).

Navigation Flows enable Service Administrators to establish cross-environment connections so that users of multiple Oracle Enterprise Performance Management Cloud environments can sign in to one environment and then seamlessly navigate to others without going through additional authentication processes. Service Administrators can create mashups of artifacts from various environments into a single unified business process flow of clusters, cards, and tabs.

Common Errors and Steps to Resolve Them

The following errors are commonly reported:
  • The target connection does not belong to the same identity domain as the source.

    Ensure that the target connection is in the same domain as the source.

  • The product version of the target is different from that of the source.

    Before creating a connection, ensure that both the source and target product versions are the same. For example, you cannot set up connections between 20.04 Planning and a 20.03 Financial Consolidation and Close.

  • You are not able to create a connection.

    Ensure that you are assigned to the Service Administrator predefined role. Only a Service Administrator can create connections.

  • The target connection does not have a business process or application.

    Create a business process in the target environment and try again.

  • The user name or password is invalid.

    • If you are designing a connection, ensure that you are signed in as a Service Administrator.

    • Ensure that the password used in the connection definition has not expired.

    • Do not edit the Domain field. The domain is automatically populated from the URL. If there is no domain in the URL, then the Domain field is left blank.

  • The URL provided is not for a business process of type <selected provider type name>.

    The URL is not for a business process supported by the selected provider. For example, the user has selected a provider type of Oracle Sales Planning Cloud but the URL is for a Financial Consolidation and Close business process, which uses the EPM Cloud provider.

  • The target you are trying to reach could not be found.

    • Ensure that the URL is valid.

    • Ensure that the URL is not a Workspace URL (for example, http://<hostname>/workspace). See Sample EPM Cloud URLs in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators .

  • Unable to establish a connection due to an unexpected error.

    For additional information, see "Connecting Subscriptions in EPM Cloud" in your Administering guide at Cloud Documentation.

    • The target environment is down.

    • The target environment is in maintenance mode.

    • The target environment is performing daily maintenance and will not be available until the maintenance process is complete.

    • The target environment URL is not a trusted website and is denied access.

Other Errors and Resolution

You do not see a card, tab or cluster.

To check if you have access to the card, tab or cluster, complete these operations in the remote environment.

  • Click the Data card and verify that you can access and launch the associated form.
  • Click the Dashboard card and verify that you can access and launch the dashboard.
  • Click the Report card and verify that you can access and launch the report.

When customizing navigation flows to connect EPM Cloud environments, at times the connected artifacts may not be visible. Here are some common reasons why:

  • The target environment is down; for example, to perform routine daily maintenance.

  • The password provided in the connection definition has expired.

  • The user name provided in the connection no longer is assigned to the Service Administrator predefined role.

  • The product version of one of the environments has changed; for example, 20.03.xxx and 20.04.xxx versions of EPM Cloud environments don't communicate; both environments must be at the same version.

    Note the following:

    • This version restriction only applies to the first four digits of the version number.

    • This version restriction impacts customers who have multiple EPM Cloud environments and who might have stopped taking monthly updates for a given environment.

  • The referenced navigation flow was deleted on the target environment, or one of the following occurred:

    • The referenced navigation flow artifact (card, tab, or cluster) was deleted.

    • The referenced artifact from the target flow was deleted or renamed.

    • The currently logged in user's access to the given artifact was revoked.

How to Get Help

If the information in the preceding sections fails to resolve you issue, contact Oracle for help.
  1. Create Provide Feedback submissions from both the source and the target environments defined in the cross-environment connection.

    Be sure to authorize Oracle to access the maintenance snapshot of both environments by consenting to the application snapshot submission. See Creating a Provide Feedback Submission.

  2. Create a technical service request that identifies the reference numbers of both Provide Feedback submissions. See Submitting a Technical Service Request. Ensure to attach additional screenshots, if needed, to explain the issue in the service request, and specify the following:

    • Whether you are in the production phase (as opposed to implementation or testing) on these environments.
    • Whether this issue is stopping you from performing critical business operations; for example, preventing you from closing the current financial cycle or creating urgent reports for management.