| Oracle® Business Intelligence Applications Release Notes 11g Release 1 (11.1.1.8.0) E49135-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Business Intelligence Applications Release Notes 11g Release 1 (11.1.1.8.0) E49135-03 |
|
|
PDF · Mobi · ePub |
These release notes describe known issues and workarounds for Oracle Business Intelligence Applications Release 11.1.1.8.0, and contain the following sections:
These release notes are updated periodically as new information becomes available. To ensure that you are reading the latest version of the release notes, check the Oracle Business Intelligence Applications Documentation set. The most current version of the Oracle Business Intelligence Applications Release Notes is available:
On the Oracle Technology Network at http://www.oracle.com/technetwork/middleware/bi-foundation/documentation/bi-apps-098545.html (to register for a free account on the Oracle Technology Network, go to http://www.oracle.com/technetwork/index.html).
The issues and workarounds related to Oracle Business Intelligence that have been identified since the previous revision of the Release Notes include:
Section 1.2.2.1, "SIL_ExchangeRateGeneral.W_EXCH_RATE_G Map Creating Duplicates"
Section 1.3.10, "Product Information Management Incorrectly Listed For E-Business Suite" (Updated)
Section 1.3.11, "Ignore FSM Task How to Integrate Project Analytics with Financial Analytics"
Section 1.3.12, "W_INDUSTRY_DH.INTEGRATION_ID Formatted Incorrectly"
This section describes issues and workarounds for specific areas, such as installation, upgrade, security, and documentation.
This section provides release notes on installing Oracle Business Intelligence Applications. It contains the following topics:
Oracle BI Applications release 11.1.1.8.0 requires the following critical patches.
Oracle BI Applications RCU
The Oracle BI Applications RCU (also referred to as the Business Analytics Applications RCU).zip file for this release is provided as Patch 18185465. Download this patch from My Oracle Support > Patches & Updates.
ODI Patch
ODI Patch 18204886 is required. This patch is delivered in Patch 18438401: P4FA SYSTEM PATCH 11.1.8.0.140311. Download this patch from My Oracle Support > Patches & Updates.
Before you run the domains load plan, you must complete the mapping of externally conformed domains to point to a particular source (even if you have only one source), using the Manage Externally Conformed Domains dialog in Oracle BI Applications Configuration Manager. You must perform the mapping configuration for each domain listed in the Manage Externally Conformed Domains dialog.
For instructions on mapping the externally conformed domains, see "How to Configure Externally Conformed Domains," in Oracle Business Intelligence Applications Configuration Guide.
This section provides release notes on upgrading Oracle Business Intelligence Applications.
When you upgrade from 11.1.1.7.1 to 11.1.1.8.1, the 'SIL_ExchangeRateGeneral.W_EXCH_RATE_G' map will cause duplicates to be loaded. Apply the workaround below before running the first Load Plan on the 11.1.1.8.1 environment. As part of the standard customization process, you will copy the existing mapping folder to a custom folder, make changes in the custom folder, delete the default installed scenario from the original mapping folder, and then generate the new scenarios in the custom folder using the original installed scenario name. Detailed instructions are provided in the workaround below. For general customization guidelines, refer to section 'Customizing the Oracle Business Analytics Warehouse' in Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Applications.
Login to ODI repository from studio and navigate to the BI Apps Project.
Under the Mappings folder, create a new custom SILOS adaptor folder based on the default installed SILOS folder in your environment.
Right-click the Mappings folder and select New Sub-Folder.
Specify the Name as CUSTOM_<Original Folder Name>.
For example, if this is for SILOS, create custom folder CUSTOM_SILOS.
Click the Connect Navigator button in the Designer tab.
Select Edit Release Tags.
Select the release tag that corresponds to your source. For example, BIA_11 for SILOS.
Select the custom SILOS folder you created and add it to the release tag.
Click Next.
Click Finish.
Enable versioning for the preconfigured Task Folder, SIL_ExchangeRateGeneral, to be customized.
The version comment should indicate this is the base version of the task. Subsequent patches applied to this task in the future would require increasing the version in the comment so that it can be compared to the original task to identify any changes.
Go to SILOS folder, right-click the Task folder SIL_ExchangeRateGeneral and select Version > Create Version.
Accept the default version number, 1.0.0.0.
Add a description indicating that this is the original version of this task.
Duplicate the Task folder to be customized (i.e. SIL_ExchangeRateGeneral) by copying it.
Cut and paste the copied task folder to the Custom adaptor folder you have created (e.g. CUSTOM_SILOS), and rename it to remove the 'Copy of…' prefix.
Using the same method as in step 3, enable versioning of copied Task folder.
The version comment should indicate this is the original version. This versioning enables comparison of the customized task to a copy of the original version to determine all changes that have been introduced.
Create another version of the copied task SIL_ExchangeRateGeneral.
The version comment should indicate this is the customized version. Use the same steps as above.
Expand the below map and find one Interface inside this folder in the custom adaptor folder.
Open the interface SIL_ExchangeRateGeneral.W_EXCH_RATE_G and make the following changes.
Go to QuickEdit tab and make the select the UK checkbox for the columns shown below.
Clear the checkbox for any other columns.
Save the Interface after making the changes.
Update the scenario, as follows:
Delete the scenario associated with the original, out-of-the-box task and generate a new scenario for the custom task using the same scenario name as the original. ODI enforces unique scenario names and we want to use the same scenario name for the custom task so that the load plan executes this ETL task rather than the installed default ETL task.
Delete the installed default scenario:
* Navigate to the out-of-the-box Task folder - Packages - <Package Name> - Scenarios - <Scenario Name>.
* Make a note of the Scenario Name (you can double click and use CTRL-C to copy the scenario name).
* Right click the scenario and select 'Delete'.
i) Before regenerating the scenario, go to the original task folder SIL_ExchangeRateGeneral in the installed default mapping folder (e.g. SILOS), delete the existing installed default scenario (e.g. SILOS_SIL_EXCHANGERATEGENERAL).
Generate a scenario for the custom task:
* Navigate to the custom Task folder - Packages - <Package Name>.
* Right click the package and select 'Generate Scenario'.
* Use the original, installed default scenario name (CTRL-V to paste the name if you copied it previously).
* Check the 'Generate scenario as if all underlying objects are materialized' box.
* Click 'OK'.
* Select 'Use All' from the 'Startup Parameters' drop down box.
* Click 'OK'.
When you execute the load plan, it will now execute the custom task rather than the original task.
ii) Go back to the modified SIL_ExchangeRateGeneral in the custom folder, go to Packages and generate the scenario using the option to generate the scenario as if all underlying objects are materialized. Rename the scenario name to use the original out of box scenario name. For example SILOS_SIL_EXCHANGERATEGENERAL.
If you make further changes to any of the interfaces or to the package, you can either regenerate the existing scenario or generate a new scenario. Unless you need separate scenarios, it is recommended that you regenerate the existing scenario. To do this, right-click the scenario and select Regenerate.
Generate a new Load Plan and continue with the ETL.
This section provides corrections and additions for documentation and Help for Oracle Business Intelligence Applications.
In the section Related Documentation in the Preface, some of the guides provide an incorrect link for the location of the Oracle BI Applications Release 11.1.1.8.0 documentation library. The correct link is:
Note the following errors:
This issue applies to the following dialogs:
- Register Source in Oracle Data Integrator Topology\Provide Connection Details area.
- Edit Source dialog\Edit Connection Details area.
The help topic for these dialogs does not include the following Element Descriptions for the Technology: Oracle BI tab:
Technology: Oracle BI (Fusion Applications-only)
Use this tab to set the Oracle BI EE connection details for the model selected in the Oracle Data Integrator Connection Information window.
| Element | Description |
|---|---|
|
Oracle Data Integrator Data Server Name |
A short meaningful name incorporating 'FUSION' or similar that identifies the data server as being for Fusion Applications. For example, FUSION_CMDS. This name must be unique across all ODI data servers in the ODI Repository. |
|
JDBC Driver |
The name of the JDBC driver for Oracle BI EE. For example: It is recommended that you leave the default value. |
|
JDBC URL |
The JDBC URL for Oracle BI EE. The format for the URL is the following:
For example, |
|
Database Username |
The database username for Oracle BI EE. For example, |
|
Database Password |
The password for the OBIA_ETL_USER user. |
|
Test |
Use this button to test the connection to Oracle BI EE. |
Note the following errors:
- Section B.2.107 'How to Integrate Project Analytics with Financial Analytics' is a duplicate topic. Refer instead to B.2.99 'How to Integrate Financial Analytics with Project Analytics'.
Note the following errors:
In Chapter 3 Setting Up Oracle BI Applications > Section 3.3.16 Performing System Setup Tasks > 3.3.16.2 Registering Source Systems Step 5 b: JDBC URL:
The format "jdbc:oraclebi://<sid>:<port>" is incorrect.
This should be:
jdbc:oraclebi://<BI Server host>:<BI Server port>/PrimaryCcs=<Cluster
Controller Host>;PrimaryCcsPort=<Cluster Controller Port>
For example: jdbc:oraclebi://biserverHost:9703/PrimaryCcs=CCSHost;PrimaryCcsPort=9706
Follow the instructions in this release note to configure user access in ODI Studio instead of the instructions documented in section 3.3.13.2, ”Configuring User Access for ODI Studio.”
The ODI Repository is configured for external authentication against the Fusion Applications LDAP server. ODI Studio must be configured to use the appropriate security files for authentication. The security files must be regenerated for login to ODI Studio to be successful.
To configure user access for ODI Studio:
Run the following command from the BI_ORACLE_HOME/common/bin folder in order to generate the ODI client security artifacts.
./wlst.sh <MW_HOME>/Oracle_BI1/bifoundation/install/createJPSArtifactsODI.py external -- ADMIN_USER_NAME <Administrator> --DOMAIN_HOSTNAME <Hostname> --DOMAIN_PORT <Domain Port> --DOMAIN_HOME_PATH <Domain Home Path> --OID_USER cn=orcladmin --LDAP_URL <ldap://host:port> --USERBASE_PREFIX <User base where users will be searched> --GROUPBASE_PREFIX <user group> Example: ./wlst.sh /scratch/mw6826/Oracle_BI1/bifoundation/install/createJPSArtifactsODI.py --ADMIN_USER_NAME Administrator --DOMAIN_HOSTNAME <hostname>.com --DOMAIN_PORT 7001 --DOMAIN_HOME_PATH /scratch/mw6826/user_projects/domains/bifoundation_domain --OID_USER cn=orcladmin -- LDAP_URL ldap://<hostname>.com:3060 --USERBASE_PREFIX cn=users,dc=us,dc=oracle,dc=com --GROUPBASE_PREFIX cn=groups,dc=us,dc=oracle,dc=com
Note:
Do not run wlst from any location other than BI_ORACLE_HOME/common/bin.
| Parameter | Description |
|---|---|
|
external |
Used to configure to the external LDAP system. |
|
ADMIN_USER_NAME |
The Weblogic Administrator user Name. |
|
DOMAIN_HOSTNAME |
The BI Domain host name. |
|
DOMAIN_PORT |
The BI Domain port. For example, |
|
DOMAIN_HOME_PATH |
The BI Domain home path. For example, |
|
OID_USER |
The OID user. For example, |
|
LDAP_URL |
The external ldap URL. Format: format: ldap://host:port |
|
USERBASE_PREFIX |
The user base prefix, where users will be searched. For example, |
|
GROUPBASE_PREFIX |
The user group prefix. For example, |
Copy the jps-config-jse.xml file and cwallet.sso files from DOMAIN_HOME_PATH/odi-client-config/external to ODI_Home/oracledi/client/odi/bin on all machines where ODI Studio clients are installed.
Open the ODI_Home/oracledi/client/odi/bin/odi.conf file for editing.
Edit the line starting with ”AddVMOption -Doracle.security.jps.config” to point to the jpsconfig-jse.xml file and location. In the example below, jps-config-jse.xml and cwallet.sso have been copied to the ODI_Home/oracledi/client/odi/bin directory.
AddVMOption -Doracle.security.jps.config=./jps-config-jse.xml
This section provides general issues and workarounds for Oracle BI Applications. It contains the following topics:
Section 1.3.1, "Source Systems Not Supported in this Release"
Section 1.3.3, "Limitations in Financials Analytics When Configuring Adjustment Periods"
Section 1.3.4, "NLS Regional Settings Not Save After Logout/Login"
Section 1.3.5, "Market Basket Analysis Facts and Dimensions Not Supported"
Section 1.3.6, "Error In Execution of EXECUTE RESET DATAWARESHOUSE SCENARIO (EXEC_TABLE_MAINT_PROC)"
Section 1.3.7, "Ignore PeopleSoft FSM Tasks in Non-PeopleSoft Implementation Projects"
Section 1.3.8, "Ignore Talent Management Subject Area in Load Plans"
Section 1.3.9, "FSM Tasks Displayed Erroneously for Product Information Management"
Section 1.3.10, "Product Information Management Incorrectly Listed For E-Business Suite"
Section 1.3.11, "Ignore FSM Task How to Integrate Project Analytics with Financial Analytics"
Section 1.3.12, "W_INDUSTRY_DH.INTEGRATION_ID Formatted Incorrectly"
Oracle Business Intelligence Applications Release 11.1.1.8.0 and the product documentation contain references to unsupported source systems such as E-Business Suite, Siebel, and JD Edwards. This release only supports Fusion Applications source systems.
For up-to-date information about supported source systems in Oracle Business Intelligence Applications, see the Oracle Business Intelligence Applications certification information available at:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
Not applicable.
While monitoring execution of long running load plans in Oracle Business Intelligence Applications Configuration Manager, to troubleshoot the status displayed at load plan level for long running tasks, you must review the status of individual steps of a load plan.
Not applicable.
Business Issue: GL Balance Amount at fiscal year level might show an incorrect balance amount when multiple adjustment periods are present for a given fiscal year and (at least one) non _999 suffix one has a transaction.Technical Issue: The GL balance amount logical column uses the LAST function. When querying at the year level, the ROW_WID at the day detail hierarchy level is used as the key in partition. As a result, the amount with a ROW_WID whose suffix is 999 is used to return the value. However, when there are multiple adjustment periods, the ROW_WID is not chronological, which means that the suffix 999 row is not the last period. Thus, if there is at least one transaction happening in another adjustment period (where the ROW_WID suffix is not 999), then this transaction will be missed and therefore the balance amount will be incorrect. To resolve the issue, a new key is created and used at the day detail hierarchy level. The new key is always chronological.
Potentially Affected Financial Report Areas:
Financials - Budgetary Control - Detail Transactions
Financials - Budgetary Control - Expense
Financials - Budgetary Control - Revenue
Financials - GL Balance Sheet
Financials - GL Budget and Expenses
Financials - GL Cash Flow
Financials - GL Detail Transactions
Financials - Profitability - Company
Financials - US Federal - GL Balance Sheet
Financials - US Federal - GL Detail Transactions
A new logical column called Fiscal Date Key has been added to the logical table Dim – Date Fiscal Calendar. It is mapped to the LTS:
"Oracle Data Warehouse"."Catalog"."dbo"."Dim_W_MCAL_DAY_D_Fiscal_Day"."FISCAL_DATE_WID"
where FISCAL_DATE_WID is a new physical column added to W_MCAL_DAY_D in Release 11.1.1.8.
This new logical column (Fiscal Date Key) should be used in the logical hierarchy level Day Detail Level of the logical dimension: Date – Fiscal Calendar.
To apply this workaround:
Using Oracle BI EE Administration Tool, edit the BI metadata repository (that is, the RPD file).
Navigate to Logical Dimension: Date – Fiscal Calendar and go to day detail level. The new column Fiscal Date Key should appear under it already.
Double click on logical hierarchy level Fiscal Day Detail to open it. In the Keys tab column, add a new key called Fiscal Date Key and map it to the new column Fiscal Date Key (Dim – Date Fiscal Calendar.Fiscal Date Key). Note at this time, the new key will be the third key in this level. The other two keys are Row Wid and Fiscal Date. Reorder the three keys and make sure the new key is the first key in the list, as follows:
Select the new Fiscal Date Key as the primary Key of the Logical Level – Fiscal Day Detail. After setting, then click on OK.
Click on Save and do a Global Consistency Check.
Host the RPD and generate Answers.
This issue applies to customers who want to use Oracle BI Applications Configuration Manager and FSM in non-English languages.
The changes in task Preferences -> Regional or Preferences -> Language are not saved properly after you log out the application and log in again.
After logging in, if the preference settings, (for example, UI language, number format, date format, time format, time-zone) are not set to the values as required, users can go to task Preferences > Regional or Preferences > Language, change the preferences as required and save, and then continue to use other tasks without logging out.
The market basket analysis related facts and dimensions are not supported in current release due to performance issues.
Due to performance issues, Market Basket analysis related facts and dimensions are not supported.
List of logical facts not supported:
- Fact - CRM - Next Order Same Account
- Fact - CRM - Next Order Same Contact
- Fact - CRM - Order Item Same
- Fact - CRM - Product Affinity
List of logical dimensions not supported:
- Dim - Market Basket Product
- Dim - Next Product Purchased
There is no workaround for this issue.
In Oracle Data Integrator, an error is reported in the scenario EXECUTE RESET DATAWARESHOUSE (EXEC_TABLE_MAINT_PROC), which is caused by a failure to truncate the table W_ETL_LOAD_DATES. The error message is similar to the following example:
java.lang.Exception: ODI-17546: Specified variable not found in the
Repository : DDL_RUN_MODE
at
com.sunopsis.dwg.dbobj.SnpSession.updateVarWithSessVar(SnpSession.java:3162)
at
com.sunopsis.dwg.dbobj.SnpSession.treatSessVariables(SnpSession.java:2713)
...
...
And so on.
In BI Applications Configuration Manager, on the Tasks bar select the Define Business Intelligence Applications Instance link to display the Define Business Intelligence Instance page.
Display the Environment Configuration tab.
In the Reset Data Warehouse Scenario Variables field, prefix the two variables with 'BIAPPS.'.
That is, change the value from:
DDL_TABLE_LIST=_ALL_,DDL_RUN_MODE=RESET_DW
To:
BIAPPS.DDL_TABLE_LIST=_ALL_,BIAPPS.DDL_RUN_MODE=RESET_DW
Click Save.
In FSM, the following tasks might be erroneously displayed in non-PeopleSoft (PFST) Implementation Projects, and should be ignored in that context:
- Configure Data Load Parameters for People Soft Trees
- Configure Data Load Parameters for People Soft Tree History Support
- Configure Data Load Parameters for PeopleSoft Department Tree
- Configure Data Load Parameters for People Soft Company - BU Tree
When you create a Load Plan in Oracle BI Applications Configuration Manager, you must not select the Subject Area named 'Talent Management'. This subject area is not supported in this release.
In Functional Setup Manager, the following FSM tasks that are not related to Product Information Management (PIM) are being displayed erroneously:
Table 1-2 FSM Tasks Displayed Erroneously for PIM
| Task Code | Task Name | Description |
|---|---|---|
|
HOWTO_MANAGER_HIER_SECURITY_PSFT |
How to Set Up Manager Hierarchy Base Security for Peoplesoft |
Setting up manager hierarchy base security for PeopleSoft |
|
HOWTO_SETUP_SECURITY_PIM_EBS |
How to Set Up Security for PIM in Oracle EBS |
List of steps to Set Up Security for PIM in Oracle EBS |
The Product Information Management (PIM) offering is available for Fusion Applications and Universal only in Release 11.1.1.8.1. However the Oracle BI Applications Configuration Manager metadata incorrectly indicates that PIM is also available for E-Business Suite Sources (EBS).
In Implementation Plans in FSM, ignore the Task 'How to Integrate Project Analytics with Financial Analytics' and instead use Task 'How to Integrate Financial Analytics with Project Analytics'.
The issue affects Industry, Organization Type, and auxiliary dimensions, and is caused by the format of the Integration_Id.
In Release 11.1.1.8.0, one new column INTEGRATION_ID is added to W_INDUSTRY_DH. The INTEGRATION_ID is in the format of:
W_INDUSTRY_CLASS ||'~'||ClassCategory||'~'||ClassCode
For example: IND~ONE_VOICE~01.
W_INDUSTRY_DH is a class dimension. CATEGORY is not a column to differentiate class dimensions. W_INDUSTRY_CLASS is used as the column to tell the class type. W_INDUSTRY_CLASS is part of the W_INDUSTRY_DH.INTEGRATION_ID. It contains the following hard-coded values:
Table 1-3 Classification Dimensions and Values
| Classification Dimension Name | W_INDUSTRY_CLASS |
|---|---|
|
Dim – Industry Hierarchy |
IND |
|
Dim - Customer Organization Type |
ORGTYPE |
|
Dim – Auxiliary Classification 1 |
AUX1 |
|
Dim – Auxiliary Classification 2 |
AUX2 |
|
Dim – Auxiliary Classification 3 |
AUX3 |
The IND_ID columns are changed to the same format as INTEGRATION_ID. Here is the list of impacted columns:
BASE_LVL_IND_ID
LVL1ANC_IND_ID
LVL2ANC_IND_ID
LVL3ANC_IND_ID
LVL4ANC_IND_ID
LVL5ANC_IND_ID
LVL6ANC_IND_ID
LVL7ANC_IND_ID
LVL8ANC_IND_ID
TOP_LVL_IND_ID
The W_INDUSTRY_D_TL.INTEGRATION_ID is changed to the same format accordingly.
There are no reported issues that are related to the use of Golden Gate.
|
 Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|