Connect to Oracle Fusion Cloud Applications Suite

You can connect to Oracle Fusion Cloud Applications Suite and create datasets that help you visualize, explore, and understand your applications data.

Topics:

• About the Oracle Applications Connector

• Connect to an Application in Oracle Fusion Cloud Applications Suite

• Configure Impersonate User for the Use Active User's Credentials Option

About the Oracle Applications Connector

The "Oracle Applications" connection type () enables you to use Oracle Analytics to visualize data from applications in Oracle Fusion Cloud Applications Suite. For example, Oracle Fusion Cloud Financials.You can also use the "Oracle Applications" connection type to connect to your on-premises Oracle BI Enterprise Edition deployments (if patched to an appropriate level) or connect to another Oracle Analytics service.

You can connect to these applications in Fusion Applications Suite:

• Oracle Fusion Cloud Financials

• Oracle Fusion Cloud Human Capital Management

• Oracle Fusion Cloud Loyalty

• Oracle Fusion Cloud Procurement

• Oracle Fusion Cloud Project

• Oracle Fusion Cloud Supply Chain Planning

• Oracle Sales Automation

Note:

When you connect to applications in Fusion Applications Suite, you access the data from an Oracle Transactional Business Intelligence report. These reports are subject to caching in Oracle Transactional Business Intelligence, and the data available in Oracle Analytics is based on the cached data. You can't control the cache behavior in Oracle Transactional Business Intelligence from Oracle Analytics.

Connect to an Application in Oracle Fusion Cloud Applications Suite

Create a connection to an application in Oracle Fusion Cloud Applications Suite to visualize data from that application. For example, you can connect to Oracle Fusion Cloud Financials with Oracle Transactional Business Intelligence. You can also connect to Oracle BI Enterprise Edition.

1. On the Data page or Home page, click Create, then click Connection.
2. Click Oracle Applications.
3. Enter the connection details.
   • For Connection Name, specify a user-friendly name to identify the connection details in Oracle Analytics.
   • For Host, enter the URL for Fusion Applications Suite with Oracle Transactional Business Intelligence or Oracle Analytics Server.

     Note:

     Don't enter the URL of the Oracle Analytics application you're currently logged in to. If you want to visualize the data used in a local analysis, create a dataset based on the analysis (local subject area). See Create a Dataset from a Subject Area in Your Instance.
   • For Username and Password, specify the Oracle Applications user credentials.
4. Under Authentication, specify how you'd like to authenticate the connection:
   • Always use these credentials - Oracle Analytics always uses the login name and password you provide for the connection. Users aren’t prompted to log in.
   • Require users to enter their own credentials - Oracle Analytics prompts users to enter their own user name and password for the data source. Users can only access the data for which they have the permissions, privileges, and role assignments.
   • Use the active user’s credentials - Oracle Analytics doesn't prompt users to sign in to access the data. The same credentials they used to sign in to Oracle Analytics are also used to access this data source. Make sure that the Oracle Analytics user exists in Oracle Transactional Business Intelligence .
5. Click Save.

   You can now create datasets from the connection.

The connection is visible only to you (the creator), but you can create and share datasets for it.

Configure Impersonate User for the Use Active User's Credentials Option

You can configure "impersonate user" to enable the active user's credentials option when you use the Oracle Applications connection type.

You can implement "impersonate user" for connections to Oracle Fusion Cloud Applications Suite with Oracle Transactional Business Intelligence, and Oracle BI EE. When you use "impersonate user", users can access data allowed for the active user's permissions, privileges, and role assignments. Users aren’t prompted to enter their user name and password.

Tips on setting up impersonation

• Provision one administrator user in the Oracle Fusion Cloud Enterprise Performance Management (EPM) identity domain with the necessary roles and permissions to impersonate other users.
• Specify the credentials for this EPM administrator user when you import the metadata using the Model Administration Tool. The credentials are stored in the connection pool of the RPD data model created by the Model Administration Tool.
• In addition, the SSO checkbox must be checked on the Planning server connection pool in the RPD.
• With this setup, only one native user needs to be provisioned in the EPM identity domain. Other end users log into Oracle Analytics using their SSO credentials, and Oracle Analytics passes the SSO username to Planning and Budgeting Cloud Service when connecting, along with the credentials of the native EPM administrator user that has impersonation permissions.
• Note: Logging into EPM using SSO credentials isn't supported by the REST API or the Planning ADM driver.

Provision Impersonate User for Connection to Oracle Fusion Cloud Applications Suite

You can provision the impersonate user functionality in Oracle Fusion Cloud Applications Suite when your connection target is an application in Oracle Fusion Cloud Applications Suite with Oracle Transactional Business Intelligence.

1. Log in to Oracle Fusion Applications as an administrator with privileges to create or modify a role.
2. Display the Security Console dialog, and display the Users tab.
3. Click Add User Account to create a user. For example, create a user called DV Admin.
4. Display the Roles tab, and click Create Role.
5. Enter a role name in the Role Name field. For example, enter DV Access.
6. Enter a code for the role name in the Role Code field. For example, enter DV_ACCESS.
7. Select BI - Abstract Roles in the Role Category field.
8. Skip the steps Function Security Policies and Data Security Policies.
9. In the Role Hierarchy step, click (+) Add Role and select the existing BIImpersonator role in the Add Role Membership dialog.
10. Select the user that you created (for example, DV Admin).
11. Click Add User to Role in the Add User dialog.
12. Click Save and Close.

    The DV Admin user is added to the BI Impersonator role, and you can use the DV Admin user in Oracle Analytics in conjunction with the Use Active User's Credentials option in the Create Oracle Application Connection dialog.

    You can now test the impersonate functionality.

Provision Impersonate User for Connections to Oracle BI EE On-Premises

You can provision the impersonate user functionality in Oracle Fusion Middleware when your Oracle Application connection target is an on-premises installation of Oracle BI EE.

1. Log in to Oracle Fusion Middleware Control for your Oracle BI EE instance using an administrator account.
2. Click the Weblogic Domain option, and select Security and Application Policies.
3. Click Create to display the Create Application Grant dialog.
4. Click (+) Add in the Permissions area.
5. Select Resource Types.
6. Select oracle.bi.user from the drop-down list.
7. Click Continue.
8. Enter an asterisk (*) in the Resource Name field.
9. Select "impersonate" in Permission Actions.
10. Click Select.
11. Click (+) Add in the Grantee section.
12. Select User from the Type drop-down list.

    You grant the newly created permission to either an application role or user.

13. Select Includes from the Principal Name drop-down list and enter an asterisk (*) into the field.
14. Click the > arrow to display a list of users.
15. Select the user that you want to give the permission to and click OK.

    You can now test the impersonate functionality.

Create a Dataset from a Subject Area in Oracle Fusion Cloud Applications Suite

You can create a dataset from subject areas stored in an applications in Oracle Fusion Cloud Applications Suite. For example, Oracle Fusion Cloud Financials with Oracle Transactional Business Intelligence.

When you drag and drop a subject area to the Join Diagram, by default Oracle Analytics doesn't include any columns in the dataset table. You must specify which columns to include in the table.

Oracle Analytics doesn't automatically join tables created from subject areas. You need to manually join these tables. See Understand Dataset Table Joins.

Don't create or use an Oracle Applications connection to connect to your local Oracle Analytics instance. Using a connection to your instance to create datasets from local subject areas or analyses results in data caching issues and errors in visualizations. Instead, use the Local Subject Area connection type to create a dataset from a subject areas stored in your Oracle Analytics instance. See Create a Dataset from a Local Subject Area.

1. On the Home page, click Create and then click Dataset.
2. In the Create Dataset dialog, select a connection to the application you want to analyze. Oracle Applications connections have this icon:
3. In the Dataset editor, go to the Connections pane and browse or search for a subject area.
4. Drag and drop one or more subject areas to the Join Diagram.
5. To add columns to a table, go to the Table Page Tabs, click a subject area table, and use the Transform Editor to specify which columns to include in the table. Click OK.
6. In the Join Diagram, locate the table that you want to join, hover over it to select it, and then click and drag and drop it on to the table that you want to join it to. Open the Join editor to inspect or update the join type and conditions.
7. Click Save Dataset.
8. Change the default name "New Dataset" displayed top left.

Create a Dataset from an Analysis in Oracle Fusion Cloud Applications Suite

You can create a dataset based on analyses from applications in Oracle Fusion Cloud Applications Suite. For example, Oracle Fusion Cloud Financials with Oracle Transactional Business Intelligence.

Oracle Analytics doesn't automatically join tables created from analyses. You need to manually join these tables. See Understand Dataset Table Joins.

Don't create or use an Oracle Applications connection to connect to your local Oracle Analytics instance. Using a connection to your instance to create datasets from local subject areas or analyses results in data caching issues and errors in visualizations. Instead, use the Local Subject Area connection type to create a dataset from a analyses stored in your Oracle Analytics instance. See Create a Dataset from a Local Analysis.

1. On the Home page, click Create and then click Dataset.
2. In the Dataset editor, go to the Connections pane and browse or search for an analysis.
3. Drag and drop one or more analysis to the Join Diagram.
4. In the Join Diagram, locate the table that you want to join, hover over it to select it, and then click and drag and drop it on to the table that you want to join it to. Open the Join editor to inspect or update the join type and conditions.
5. Click Save Dataset.
6. Optional: Change the default name "New Dataset" displayed top left.

Edit an Oracle Applications Connection

You can edit an Oracle Applications connection. For example, you must edit a connection if your system administrator changed the Oracle Applications login credentials.

1. In the Data page, click Connections.
2. In the Edit Connection dialog, edit the connection details. Note that you can’t see or edit the password that you entered when you created the connection. If you need to change the connection’s password, then you must create a new connection.
3. Click Save.

Delete an Oracle Applications Connection

You can delete an Oracle Applications connection.

1. Delete any datasets that use the connection you need to delete.
2. In the Data page, click Connections.
3. Click Yes.