Professional Documents
Culture Documents
OBIEE Integration With EBS PDF
OBIEE Integration With EBS PDF
Saurabh Gautam
6/9/2011
Applies to:
Purpose
This document details the steps required to integrate Oracle BI Applications with Oracle E-Business Suite Applications
in the following ways:
Single Sign-On first into Oracle E-Business Suite and have that authentication passed through to Oracle BI EE
Embed links to Oracle BI EE dashboard/catalog in Oracle E-Business Suite pages
Create Action Links within Oracle BI EE reports and dashboards that take you back into Oracle E-Business Suite in
context
Setup is required both on the E-Business Suite Application and Oracle BI EE sides to perform this integration. These
steps are detailed in this bulletin with an example of how to achieve this in the Oracle BI Applications. This document
does not describe the mechanism to embed Oracle BI EE charts, dashboards, or reports in the E-Business Suite
application.
This section describes the necessary steps to achieve SSO integration and to embed links to the Oracle BI Interactive
Dashboards and to Oracle BI Answers within Oracle E-Business Suite Applications.
The following patch is a pre-requisite on the Oracle E-Business Suite Applications 11i instance for this
functionality to work:
11i.ATG_PF.H.delta.5 - 5473858 contains all required patches for integration. If you are on later RUP
patchsets, they will also contain all required patches for integration.
For Oracle EBS R12, there are no pre-requisite patches required since base R12 has all the functionality
that OBIEE leverages, namely the OBIEE profile is defined in b5869360.ldt, OracleOasis.jsp and APP_SESSION
package which are in base R12.
1.2. Embedding Links to Oracle Business Intelligence in Oracle E-Business Suite
To embed a link in Oracle E-Business Suite that opens Oracle Business Intelligence dashboards, you need to
create a form function and then assign menus and responsibilities.
Before you begin, log in to Oracle E-Business Suite as the system administrator (for example, sysadmin).
Then, select the System Administrator responsibility from the responsibility navigator pane on the left.
The available menus appear on the right.
Follow the steps in this section to create the following objects, in sequence:
Function
Menu
Responsibility
User
Profile
1. From the Application menu, select Function. The Form Functions dialog appears.
2. Enter the name of the function in the Function Field
3. Enter the User Function Name
4. Enter a description
5. Save your changes using the Save button on the toolbar
6. Select the Properties tab
7. Specify the Type as SSWA jsp function
1. From the Application menu, select Menu. The Menus dialog appears.
2. Enter the name of the Menu
3. Enter a User Menu Name
4. For Function, enter the name of the function(s) created in the previous section
5. Save you changes using the Save button on the toolbar, and then close the Menus dialog.
You can create a new responsibility or an existing responsibility can be used. Below steps shows how
to create a new responsibility:
8. Save you changes using the Save button on the toolbar, and then close the responsibilities dialog.
You can create a new user or an existing responsibility can be used. Below steps shows how to create a
new user:
1. From the Security Menu, Click on User and then Select Define
2. Enter the name of the user
3. Specify the responsibilities that this user will have access to.
4. Save you changes using the Save button on the toolbar, and then close the Users dialog.
1. From the Applications menu, Click on Profile and then select System Profile
2. Select Responsibility and then enter the name of the responsibility which you created earlier
3. Enter %Business Intelligence% in the Profile field
4. Click Find
5. On the resulting screen, specify the Oracle Business Intelligence URL. For example:
http://my_server.domain.com:port
For port, enter the Web server port where Oracle Business Intelligence is running (for example,
9704).
Note: The BI Url should be the fully qualified hostname including the domain name. It shouldnt be an
IP Address
2. RPD Changes
1. Open the file authenticationschemas.xml for editing. This file can be found at:
ORACLE_HOME/bifoundation/web/display
2. Find the following element in the file:
<AuthenticationSchema name="EBS-ICX"
3. Locate the sub-element RequestVariable source="cookie" and change the value of the nameInSource
attribute from ICX_SESSION to the name of the EBS ICX authentication cookie prefix. For example:
<RequestVariable source="cookie" type="auth" nameInSource="VIS"
biVariableName="NQ_SESSION.ICX_SESSION_COOKIE" />
Note: Ask your Oracle E-Business Suite administrator for the name of the EBS ICX authentication cookie
if you do not know it. Alternatively, follow these steps to find the cookie name:
Log in to Oracle E-Business Suite.
Enter the following text in the address bar of your browser: javascript:alert(document.cookie)
The value you need to provide in authenticationschemas.xml is the prefix of the EBS ICX authentication
cookie. In the previous example, the EBS ICX authentication cookie is VIS=ZcEJeoLNVqcHGiGYvCpzTx3N:S;,
and the prefix is VIS.
4. In the same entry (RequestVariable source="cookie"), ensure that the value of the biVariableName
attribute is the same as the value you entered as part of the connection script when you created the
connection pool for the Oracle E-Business Suite database.
5. Find the following element:
<SchemaKeyVariable source="cookie"
Change the value of the nameInSource attribute from ICX_SESSION to the name of the EBS ICX
authentication cookie prefix (often VIS). For example:
1. Open the file instanceconfig.xml for editing. You can find this file at:
ORACLE_INSTANCE/config/OracleBIPresentationServicesComponent/coreapplication_obipsn
2. Locate the Authentication element.
3. Include EBS-ICX in the list of enabled schemas. For example:
<EnabledSchemas>UidPwd,Impersonate,UidPwd-soap,Impersonate-soap,EBS-ICX</EnabledSchemas>
4. Ignore the comment in instanceconfig.xml that says this setting is centrally managed. EBS-ICX must be
manually added to the EnabledSchemas element.
5. Save and close the file.
6. Restart Oracle Business Intelligence.
1. Identify the e-Business Suite Form that is to be linked to. Identify the parameters required by
the Form/Page. Please refer to e-Business Suite Documentation for details.
2. Create a new Action which will enable OBIEE to call the e-Business Suite Target form.
d. In the resultant screen, two mandatory parameters, FunctionCode and Connection pool need to
be specified. For FunctionCode, Specify the function code of the target form which need to
be launched. Also, Specify the connection pool (mentioned under section rpd changes ). In
addition to these two mandatory parameters, create new parameters which has the same name as
the identified parameter (Identified in Step 1) and specify a value.
For better user experience, Mark the FunctionCode and ConnectionPool parameters as Hidden.
f. Navigate to location where the Action is saved and Click on Execute to test the Action
Clicking on Execute should launch e-Business Suite Form.
f. The Action Link created above can be used in Analysis/Dashboards. For details, how to use
Action Links in Analysis/Dashboard, Refer to Oracle Business Intelligence Enterprise Edition
documentation. Steps below provides a simple example on how to use Action Link in Analysis:
2. Navigate to New->Analysis
3. Select a Subject Area and then select a column on which the Action Link is to be
set as an Interaction
7. Click on + icon and Specify the Action Link (which was created in earlier step).
8. Specify parameters if a dialog box for parameters is prompted. Set the value to
be based on Column. Check the Hidden Checkbox. Click on ok.
10. Login to e-Business Suite. Click on the OBIEE Answers link to navigate to
OBIEE