Oracle® Business Intelligence Applications

Release Notes

11g Release 1 (11.1.1.8.1)

E51482-06

January 2015

Provides late-breaking information about issues and work-arounds for Oracle BI Applications Release 11.1.1.8.1. The Release Notes are regularly updated.

Oracle Business Intelligence Applications Release Notes, 11g Release 1 (11.1.1.8.1)

E51482-06

Copyright © 2013, 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documentation

- Conventions

1 Release Notes

- 1.1 How to Use These Release Notes

- 1.1.1 Obtaining Patches from My Oracle Support

- 1.1.2 Oracle Business Intelligence Applications Issues and Workarounds Identified Since the Previous Revision

- 1.2 Issues and Workarounds for Installation, Upgrade, and Documentation

- 1.2.1 Installation

- 1.2.2 Upgrade

- 1.2.2.1 Upgrading from Oracle BI Applications V11.1.1.7.1 to V11.1.1.8.1

- 1.2.2.2 Scenario SIL_QASpecificationDimension Inserts Duplicate Records After Upgrade From 11.1.1.7.1 To 11.1.1.8.1

- 1.2.2.3 Domain Upgrade to Address Failure in DOMAINGENERAL_TRANSLATE and DOMAINGENERAL FAILS In JDE v9.1

- 1.2.2.4 Data Correction For BUDGET_TYPE_CODE

- 1.2.3 Documentation Corrections

- 1.2.3.1 Errors in Oracle Business Intelligence Applications Installation Guide

- 1.2.3.2 Errors in Oracle Business Intelligence Applications Configuration Guide

- 1.2.3.3 Additions to Oracle Business Intelligence Applications ETL Guide

- 1.3 General Issues and Workarounds

- 1.3.1 Load Plan Execution Status Does Not Show Error in Oracle BI Applications Configuration Manager

- 1.3.2 NLS: Repository and Catalog Strings Not Translated

- 1.3.3 NLS Regional Settings Not Save After Logout/Login

- 1.3.4 Market Basket Analysis Facts and Dimensions Not Supported

- 1.3.5 Partitioning Required for Oracle Student Analytics With SDS

- 1.3.6 Ignore Non-Fusion Applications FSM Tasks

- 1.3.7 FSM Tasks Displayed Erroneously for Product Information Management

- 1.3.8 Product Information Management Incorrectly Listed For E-Business Suite

- 1.3.9 Ex_Employee Count in PeopleSoft HCM only populated where Profile Management is Deployed

- 1.3.10 Memory Error with JD Edwards OM With DB2 Database

- 1.3.11 Discrete Quality Erroneously Displayed as Part of Enterprise Asset Management Analytics

- 1.3.12 ETL Failure in Fusion Applications Workforce Subject Area

- 1.3.13 RCU Cannot Drop the Business Applications Component Repository <prefix>_BIACOMP Schema

- 1.3.14 Human Resources E-Business Suite Payroll Patches for Payroll Analytics

- 1.3.15 Tech Switch ODI Repository

- 1.3.16 Agreement Status Warehouse Codes Not Set Correctly for E-Business Suite Sources

- 1.3.17 Agreement Status Warehouse Codes Not Set Correctly for JDE Suite Sources

- 1.3.18 LPG Trimming Out Scenarios in Load plans for Fusion Applications Sources

- 1.3.19 Deploying Oracle BI Applications Duty Roles for ETL

- 1.3.20 Standard UOM Conversion for Inventory Lot Monthly Balance Fact

- 1.3.21 Cloud Adaptor - Employee Expenses Is Supported in Patch Bundle 6 (PB6)

- 1.3.22 Database Error ORA-00907 Missing Right Parenthesis Error When Running Load Plan

- 1.3.23 Using a Third Party Driver For DB2 400 UDB

- 1.3.24 Load Plan Schedules Missing After Regeneration

- 1.3.25 Insufficient Memory During Load Plan Execution

- 1.3.26 Human Resources E-Business Suite Payroll patches for Payroll Analytics

- 1.3.27 Deploying Multiple Instances of the Same Source

- 1.3.28 Issue With Scenario SDE_ORA_PURCHASECOSTFACT for Financial Analytics with E-Business Suite R12.x Adapters

- 1.3.29 Missing Columns GL_JOURNAL_DT and JOURNAL_LINE_REFERENCE Causing Execution Error

- 1.3.30 Change to Table Definitions in Inventory Analysis

- 1.4 Issues and Workarounds for Golden Gate

Preface

Oracle Business Intelligence Applications is comprehensive suite of prebuilt solutions that deliver pervasive intelligence across an organization, empowering users at all levels — from front line operational users to senior management — with the key information they need to maximize effectiveness. Intuitive and role-based, these solutions transform and integrate data from a range of enterprise sources and corporate data warehouses into actionable insight that enables more effective actions, decisions, and processes.

Oracle BI Applications is built on Oracle Business Intelligence Suite Enterprise Edition (Oracle BI EE), a comprehensive set of enterprise business intelligence tools and infrastructure, including a scalable and efficient query and analysis server, an ad-hoc query and analysis tool, interactive dashboards, proactive intelligence and alerts, and an enterprise reporting engine.

Note:
Earlier Oracle BI Applications 11g releases were only for Oracle Fusion Applications source systems. For information about known issues and workarounds in these earlier Oracle BI Applications 11g releases, refer to the Oracle Business Intelligence Applications chapter in Oracle Fusion Middleware Release Notes, for the release of Oracle Fusion Middleware in use at your company. You can locate the appropriate Oracle Fusion Middleware documentation library from the Oracle Documentation page at this URL at: http://www.oracle.com/technetwork/indexes/documentation/index.html

Audience

This document is intended for administrators of Oracle BI Applications.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documentation

See the Oracle Business Intelligence Applications documentation library at http://docs.oracle.com/cd/E51479_01/index.htm for a list of related Oracle Business Intelligence Applications documents.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Release Notes

These release notes describe known issues and workarounds for Oracle Business Intelligence Applications Release 11.1.1.8.1, and contain the following sections:

- Section 1.1, "How to Use These Release Notes"

- Section 1.2, "Issues and Workarounds for Installation, Upgrade, and Documentation"

- Section 1.3, "General Issues and Workarounds"

- Section 1.4, "Issues and Workarounds for Golden Gate"

Note:
Earlier Oracle BI Applications 11g releases were only for Oracle Fusion Applications source systems. For information about known issues and workarounds in these earlier Oracle BI Applications 11g releases, refer to the Oracle Business Intelligence Applications chapter in Oracle Fusion Middleware Release Notes, for the release of Oracle Fusion Middleware in use at your company. You can locate the appropriate Oracle Fusion Middleware documentation library from the Oracle Documentation page at this URL:
http://www.oracle.com/technetwork/indexes/documentation/index.html

1.1 How to Use These Release Notes

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 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)

1.1.1 Obtaining Patches from My Oracle Support

Periodically, Oracle Business Intelligence Applications patches are released.

To see the patches that are available, go to My Oracle Support (formerly OracleMetaLink) using the following URL:

http://support.oracle.com

For additional information about obtaining patches, see 'Downloading and Applying Required Patches' in Oracle Fusion Middleware Infrastructure Release Notes.

1.1.2 Oracle Business Intelligence Applications Issues and Workarounds Identified Since the Previous Revision

The issues and workarounds related to Oracle Business Intelligence that have been identified since the previous revision of the Release Notes include:

- Section 1.3.28, "Issue With Scenario SDE_ORA_PURCHASECOSTFACT for Financial Analytics with E-Business Suite R12.x Adapters"

- Section 1.3.29, "Missing Columns GL_JOURNAL_DT and JOURNAL_LINE_REFERENCE Causing Execution Error"

- Section 1.3.30, "Change to Table Definitions in Inventory Analysis"

1.2 Issues and Workarounds for Installation, Upgrade, and Documentation

This section describes issues and workarounds for specific areas, such as installation, upgrade, security, and documentation.

1.2.1 Installation

This section provides release notes on installing Oracle Business Intelligence Applications. There are no known Installation issues at present.

1.2.2 Upgrade

This section provides release notes on upgrading Oracle Business Intelligence Applications.

1.2.2.1 Upgrading from Oracle BI Applications V11.1.1.7.1 to V11.1.1.8.1

For information about upgrading from Oracle BI Applications V11.1.1.7.1 to V11.1.1.8.1, refer to 'Oracle BI Applications 11.1.1.7.1 -> 11.1.1.8.1 Upgrade Guide' (Doc ID 1673221.1) on My Oracle Support (support.oracle.com).

1.2.2.2 Scenario SIL_QASpecificationDimension Inserts Duplicate Records After Upgrade From 11.1.1.7.1 To 11.1.1.8.1

After you upgrade from 11.1.1.7.1 to 11.1.1.8.1, the SIL_QASpecificationDimension scenario will load duplicate records unless you implement the Workaround below.

This issue is caused by a change to the name of the Scenario SILOS_SIL_QASPECIFICATIONSDIMENSION name in Release 11.1.1.8.1, which causes the SIL QA Specification Dimension mapping to run in full load mode again because the IS_INCREMENTAL variable value is set to No ('N').

Note: The Scenario name in 11.1.1.7.1 release is SILOS_SIL_QASPECIFICATIONSDIMENSION and the scenario name in 11.1.1.8.1 release is SILOS_SIL_QASPECIFICATIONDIMENSION (note the missing 'S' character after 'SPECIFICATION').

Workaround

1. Before you run the first Load Plan on the 11.1.1.8.1 environment, execute the following DML query on Oracle Business Analytics Warehouse:

update W_ETL_LOAD_DATES
set PACKAGE_NAME='SILOS_SIL_QASPECIFICATIONDIMENSION'
where target_table_name = 'W_QA_SPEC_D';
COMMIT;

1.2.2.3 Domain Upgrade to Address Failure in DOMAINGENERAL_TRANSLATE and DOMAINGENERAL FAILS In JDE v9.1

This issue applies to JD Edwards customers upgrading from version 11.1.1.7.1 of Oracle Business Intelligence Applications.

Due to a change in the format of the Integration ID for some Domains, it is necessary to remove certain Domain Member General records from the upgraded Oracle Business Analytics Warehouse prior to executing the Domain-only Load Plan, which will load new values. If these records are not removed, the Domain-only Load Plan can encounter duplicate key values and fail.

Use the following three SQL statements in the Workaround below to remove the necessary data from the Domain Member General tables and prepare the system to fully reload the affected Domains.

Workaround

You must execute these three statements in the upgraded Oracle Business Analytics Warehouse prior to running the Domain-only Load Plan.

Note: These statements use specific DATASOURCE_NUM_ID values (410 and 415) to target data that originated from a JDE source system. If you have configured your Oracle BI Applications environment to use different values to indicate your JDE sources, then you must substitute your values into the following commands.

Command 1

DELETE from w_domain_member_g where
DOMAIN_CODE IN ('UOM','COUNTRY','STATE_PROV','GENDER','ORGANIZATION_TYPE','AP_PAYMENT_METHOD','JDE_DOC_TYPES','COGS_XACT_TYPE','COGS_XACT_SUBTYPE','LEDGER_CATEGORY','SALES_ORDER_XACT_TYPE','SALES_INVOICE_XACT_TYPE','SALES_PICK_XACT_TYPE','BOM_TYPE','INV_TRANSACTION_TYPES','INV_TRANSACTION_SOURCE_TYPES','BOM_CATEGORY','FREIGHT_TERMS','ITEM_TYPE','DIVISION_TYPE','SIC_CODE','EXM_EXPENSE_PAYMENT_METHOD','HAZARD_MTL','CUSTOMER_CATEGORY','CUST_CLASS','CUST_TYPE','SALES_CHANNEL_TYPE','SALES_FREIGHT_TERMS','INV_TRANSACTION_ACTION','VENDOR TYPE')
AND DATASOURCE_NUM_ID IN (410, 415);

Command 2

DELETE from w_domain_member_g_tl where
DOMAIN_CODE IN ('UOM','COUNTRY','STATE_PROV','GENDER','ORGANIZATION_TYPE','AP_PAYMENT_METHOD','JDE_DOC_TYPES','COGS_XACT_TYPE','COGS_XACT_SUBTYPE','LEDGER_CATEGORY','SALES_ORDER_XACT_TYPE','SALES_INVOICE_XACT_TYPE','SALES_PICK_XACT_TYPE','BOM_TYPE','INV_TRANSACTION_TYPES','INV_TRANSACTION_SOURCE_TYPES','BOM_CATEGORY','FREIGHT_TERMS','ITEM_TYPE','DIVISION_TYPE','SIC_CODE','EXM_EXPENSE_PAYMENT_METHOD','HAZARD_MTL','CUSTOMER_CATEGORY','CUST_CLASS','CUST_TYPE','SALES_CHANNEL_TYPE','SALES_FREIGHT_TERMS','INV_TRANSACTION_ACTION','VENDOR TYPE')
AND DATASOURCE_NUM_ID IN (410, 415);

Command 3

DELETE from w_etl_load_dates where
PACKAGE_NAME LIKE '%SDE_JDE_DOMAINGENERAL_UDC';
commit;

1.2.2.4 Data Correction For BUDGET_TYPE_CODE

If you are upgrading from V11.1.1.7.1 to V11.1.1.8.1 and you have not installed all required patches, then the PA_FIN_PLAN_TYPES_TL.NAME column is not mapped to W_PROJ_BUDGET_DS. If so, then you must correct the data for BUDGET_TYPE_CODE by performing the Workaround below.

Workaround

1. Apply following update:

UPDATE W_ETL_LOAD_DATES
SET COMMITTED = '0'
WHERE PACKAGE_NAME LIKE '%SDE_ORA_DOMAINGENERAL_PROJECTBUDGETTYPE' OR PACKAGE_NAME LIKE '%SDE_ORA_PROJECTBUDGETDIMENSION';
COMMIT;

2. Run Incremental ETL.

3. Run following update:

UPDATE W_PROJ_BUDGET_D D
SET D.BUDGET_TYPE_CODE = (SELECT DS.BUDGET_TYPE_CODE FROM W_PROJ_BUDGET_DS DS
WHERE DS.INTEGRATION_ID = D.INTEGRATION_ID
AND DS.DATASOURCE_NUM_ID = D.DATASOURCE_NUM_ID);
COMMIT;

1.2.3 Documentation Corrections

This section provides corrections and additions for documentation and Help for Oracle Business Intelligence Applications.

1.2.3.1 Errors in Oracle Business Intelligence Applications Installation Guide

- Section 3.3.4 Applying Platform Patches
If you have applied the BI EE Bundle Patch 131017 as part of the procedure 3.3.4 Applying Platform Patches in the Oracle BI Applications Installation Guide for 11.1.1.8.1, or if you had applied Bundle Patch 13107 earlier but had not applied the patch to your BI Administration Tool instances, then you must patch BI Administration Tool as part of this procedure.

NOTE: If you have applied a Bundle Patch version higher than 131017 then ensure that BI Administration Tool has been appropriately patched.

The BI EE Client Installer executable is delivered in patch p17463403_111170_Generic. This patch is available in PATCH_ROOT_DIR\biappsshiphome\generic or PATCH_ROOT_DIR/biappsshiphome/generic. For the location of your PATCH_ROOT_DIR, see Section 3.3.4 Applying Platform Patches in the Oracle BI Applications Installation Guide for 11.1.1.8.1.

System administrators must provide the BI EE Client Installer executable to developers who have installed BI Administration Tool on Windows machines. On Windows machines where BI Administration Tool has been installed:

Run biee_client_install_x64.exe obtained on unzip of the patch zip file.

Select 'Modify an existing instance'.

Note: If BI Clients have not been installed then provide the biee_client_install_x64.exe executable file in the patch to developers to install the BI Clients. Run biee_client_install_x64.exe obtained on unzip of the patch zip file. Select 'Install a new instance'.

- Section 3.3.4 Applying Platform Patches
Step 8: Apply the Dynamic Monitoring Service patch 16569379 to your BI system. This patch is available on My Oracle Support > Patches & Updates.

Download the patch for your operating system and apply the patch following the instructions in the patch readme file.

This step does not have to be performed. The Dynamic Monitoring Service patch 16569379 is included the FMW Patches for BI Applications 11.1.1.8.1 under PATCH_HOME/patches/biappsshiphome/<OS folder>, and is applied when the Patch Application Script (APPLY_PATCHES.pl) is run.

- Section 3.3.6 Updating FSM
For parameter fsm.db.seed.url the document states that this is the URL used to connect to the BIACOMP schema. (The FSM user is the Business Analytics Warehouse schema owner.) (The FSM user is the Business Analytics Warehouse schema owner.) This is incorrect. The user is the BIACOMP user.

- Section 4.2 Performing Setup Steps for On-Premise Fusion Applications Sources > 4.2.1 Creating a User for ETL, in Chapter 4 Performing Post-Installation System Setup Tasks.
The section describes the creation of the ETL user named 'OBIA_ETL_USER' in the Fusion Applications LDAP System. Add the following information to this section on creating the ETL user:

When using the embedded LDAP for BI Applications, you must also create a user with exactly the same credentials as the ETL user created in Fusion Applications LDAP. Grant this OBIA_ETL_USER the BIAdministrator Duty Role.

- Section 4.3 Registering Source Systems and Propagating Connection Details to Oracle Data Integrator, in Chapter 4 Performing Post-Installation System Setup Tasks.
Step 5 b: JDBC URL incorrectly states: 'For Oracle Fusion sources, specify the JDBC URL for the Oracle BI Server. The format is jdbc:oraclebi://<sid>:<port>.'

This should read:

If your source is Oracle Fusion Applications on-premise, specify the JDBC URL for the Oracle BI Server. The format is:

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

- The guide is missing instructions for deploying Oracle BI Applications Duty Roles when the source is Fusion Applications. For more information, see Section 1.3.19, "Deploying Oracle BI Applications Duty Roles for ETL".

- When you follow the steps in Section 6.5.2 Running the Command Line Utility to Import Source Adapter Metadata Content, you might encounter the following error:

ORA-00907: missing right parenthesis error when running Load plan

If so, you must create a property file named 'sceregenparams.properties' in the \log file directory and execute a different command line command, as described in Section 1.3.22, "Database Error ORA-00907 Missing Right Parenthesis Error When Running Load Plan".

1.2.3.2 Errors in Oracle Business Intelligence Applications Configuration Guide

- In Section B.2.118 How to Configure Scorecard Target Before Running ETL, the file name 'file_purch_scorecard_target.csv' should be 'file_purch_target_fs.csv'.

1.2.3.3 Additions to Oracle Business Intelligence Applications ETL Guide

- Addition to Chapter 1 ETL Overview, Section 'About Multi-Source Environments'.
If you are implementing multiple instances of the same source, you can find additional information about how to do this in 'Multi-Instance Source Support in BI Applications 11.1.1.7.1, 11.1.1.8.1' (Support Note Doc ID 1633996.1) on My Oracle Support.

1.3 General Issues and Workarounds

This section provides general issues and workarounds for Oracle BI Applications, and contains the following topics:

- Section 1.3.1, "Load Plan Execution Status Does Not Show Error in Oracle BI Applications Configuration Manager"

- Section 1.3.2, "NLS: Repository and Catalog Strings Not Translated"

- Section 1.3.3, "NLS Regional Settings Not Save After Logout/Login"

- Section 1.3.4, "Market Basket Analysis Facts and Dimensions Not Supported"

- Section 1.3.5, "Partitioning Required for Oracle Student Analytics With SDS"

- Section 1.3.6, "Ignore Non-Fusion Applications FSM Tasks"

- Section 1.3.7, "FSM Tasks Displayed Erroneously for Product Information Management"

- Section 1.3.8, "Product Information Management Incorrectly Listed For E-Business Suite"

- Section 1.3.9, "Ex_Employee Count in PeopleSoft HCM only populated where Profile Management is Deployed"

- Section 1.3.10, "Memory Error with JD Edwards OM With DB2 Database"

- Section 1.3.11, "Discrete Quality Erroneously Displayed as Part of Enterprise Asset Management Analytics"

- Section 1.3.12, "ETL Failure in Fusion Applications Workforce Subject Area"

- Section 1.3.13, "RCU Cannot Drop the Business Applications Component Repository <prefix>_BIACOMP Schema"

- Section 1.3.14, "Human Resources E-Business Suite Payroll Patches for Payroll Analytics"

- Section 1.3.15, "Tech Switch ODI Repository"

- Section 1.3.16, "Agreement Status Warehouse Codes Not Set Correctly for E-Business Suite Sources"

- Section 1.3.17, "Agreement Status Warehouse Codes Not Set Correctly for JDE Suite Sources"

- Section 1.3.18, "LPG Trimming Out Scenarios in Load plans for Fusion Applications Sources"

- Section 1.3.19, "Deploying Oracle BI Applications Duty Roles for ETL"

- Section 1.3.20, "Standard UOM Conversion for Inventory Lot Monthly Balance Fact"

- Section 1.3.21, "Cloud Adaptor - Employee Expenses Is Supported in Patch Bundle 6 (PB6)"

- Section 1.3.22, "Database Error ORA-00907 Missing Right Parenthesis Error When Running Load Plan"

- Section 1.3.23, "Using a Third Party Driver For DB2 400 UDB"

- Section 1.3.24, "Load Plan Schedules Missing After Regeneration"

- Section 1.3.25, "Insufficient Memory During Load Plan Execution"

- Section 1.3.26, "Human Resources E-Business Suite Payroll patches for Payroll Analytics"

- Section 1.3.27, "Deploying Multiple Instances of the Same Source"

- Section 1.3.28, "Issue With Scenario SDE_ORA_PURCHASECOSTFACT for Financial Analytics with E-Business Suite R12.x Adapters"

- Section 1.3.29, "Missing Columns GL_JOURNAL_DT and JOURNAL_LINE_REFERENCE Causing Execution Error"

- Section 1.3.30, "Change to Table Definitions in Inventory Analysis"

1.3.1 Load Plan Execution Status Does Not Show Error in Oracle BI Applications Configuration Manager

While monitoring execution of long running load plans in Oracle BI Applications Configuration Manager, to troubleshoot the status displayed at load plan level, you must review the status of individual steps of a load plan.

Workaround

Not applicable.

1.3.2 NLS: Repository and Catalog Strings Not Translated

If you are using Oracle BI Applications reports and dashboards in non-English languages, then some repository and catalog strings are not translated.

Workaround

Use Oracle BI Administration Tool and Oracle BI Catalog Manager to translate repository and catalog strings.

1.3.3 NLS Regional Settings Not Save After Logout/Login

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.

Workaround

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, then 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.

1.3.4 Market Basket Analysis Facts and Dimensions Not Supported

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

Workaround

There is no workaround for this issue.

1.3.5 Partitioning Required for Oracle Student Analytics With SDS

This issue applies to Oracle Student Information Analytics.

By default, partitioning for Student Information Analytics is not deployed during installation. If you are using Source-Dependent Data-Store (SDS), then Oracle recommends that you deploy partitioning. If you are not using SDS, then partitioning is optional.

1.3.6 Ignore Non-Fusion Applications FSM Tasks

In FSM, the following task might be erroneously displayed in non-Fusion Applications Implementation Projects, and should be ignored in that context:

- Configure Enterprise List

1.3.7 FSM Tasks Displayed Erroneously for Product Information Management

In Functional Setup Manager, the following FSM tasks that are not related to Product Information Management (PIM) are displayed erroneously:

Table 1-1 Erroneously Displayed FSM Task Names

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

1.3.8 Product Information Management Incorrectly Listed For E-Business Suite

The Oracle BI Applications Configuration Manager metadata incorrectly indicates that Product Information Management (PIM) is available for E-Business Suite Sources. However, the PIM offering is available only for Fusion Applications and Universal.

1.3.9 Ex_Employee Count in PeopleSoft HCM only populated where Profile Management is Deployed

This issue applies to PeopleSoft Human Capital Management (HCM) source systems.

The Ex_Employee Count is only populated where Profile Management is deployed.

1.3.10 Memory Error with JD Edwards OM With DB2 Database

Some JD Edwards ODI mappings might cause an issue on a DB2 database where insufficient memory has been allocated by the database's STMTHEAP parameter.

Workaround

The workaround is to make sure that the parameter is using the AUTOMATIC feature.

For example:

db2 update db cfg for DATABASE_NAME using STMTHEAP 2048 AUTOMATIC

The STMTHEAP parameter can be set to AUTOMATIC with an underlying value or a fixed value. When it is set to AUTOMATIC, the underlying value enforces a limit on the amount of memory allocated for a single compilation using dynamic join enumeration. If a memory limit is encountered, the statement compilation restarts using greedy join enumeration and an unlimited statement heap. It is only limited by the amount of remaining application memory (APPL_MEMORY), instance memory (INSTANCE_MEMORY), or system memory.

1.3.11 Discrete Quality Erroneously Displayed as Part of Enterprise Asset Management Analytics

In Functional Setup Manager, the Configure Offerings dialog erroneously displays Discrete Quality as a Functional Area within the Enterprise Asset Management (EAM) Offering. Discrete Quality is not available as part of EAM, and should be ignored.

Workaround

There is no workaround for this issue.

1.3.12 ETL Failure in Fusion Applications Workforce Subject Area

During the incremental ETL run for the Fusion Applications Workforce Subject Area, the task SDE_FUSION_Persistedstage_TalentMgmt_ProfileItems.W_FSN_PRFL_ITEM_PS is failing with the error message 'ORA-00972: identifier is too long'.

Workaround

1. Open the ODI client.

2. Navigate to Load Plan and Scenarios --> BIAPPS Load Plan --> Load Plan Dev Components --> SDE --> Fusion_1_0.

3. Open the load plan component SDE PS WRKFRCEVT_GRP1_PS FUSION_1_0.

4. On the Steps tab, navigate to the step WRKFRCEVT_FG -> Persisted Staging -> Profile Item.

5. Disable the task SDE_FUSION_PERSISTEDSTAGE_TALENTMANAGEMENT by clearing the 'Enabled' check box.

6. Save the details.

7. Create and generate a new Load Plan.
Oracle recommends that you perform a full reload of the data warehouse. Reset the data warehouse from Oracle BI Applications Configuration Manager and all tasks will be executed in 'Full Load' mode when the next load plan is executed.

1.3.13 RCU Cannot Drop the Business Applications Component Repository <prefix>_BIACOMP Schema

The Oracle BI Applications 11.1.1.8.1 RCU cannot drop the Business Applications Component Repository <prefix>_BIACOMP schema. When launching RCU and selecting the 'Drop' schemas option, the Oracle BI Applications Component Repository (<prefix>_BIACOMP) is greyed out and cannot be selected.

Workaround

Work with your database administrator to drop the <prefix>_BIACOMP schema and related tablespaces. You must also delete the <prefix>_BIACM_IO schema and related tablespaces.

1.3.14 Human Resources E-Business Suite Payroll Patches for Payroll Analytics

If you are implementing Human Resources Analytics Payroll Subject Area for E-Business Suite, then it is mandatory to follow the E-Business Suite Payroll patching policy mentioned in My Oracle Support Note 295406.1 'Mandatory Family Pack / Rollup Patch (RUP) levels for Oracle Payroll'.

1.3.15 Tech Switch ODI Repository

If you are using an OLTP running on a non-Oracle database, then you must deploy a different repository to the repository deployed by the Oracle BI Applications installer. Follow the Workaround below to deploy a different repository by creating a blank repository and importing the tech switched content.

Workaround

Summary of steps:

1 Exporting Security Settings from Original ODI Repository

2 Create a blank ODI repository

3 Import content into blank ODI repository

4 Add ODI Administrator1 user

5 Enable External Authentication

6 Importing Security Settings Into the ODI Repository

7 Next Steps

8 Regenerate Scenarios

Detailed steps:

1. Exporting Security Settings from Original ODI Repository.

1. Log into ODI Studio.

2. Navigate to Topology, and select Export Security Settings.

3. Save the export file to a local directory.
You will use this export file to import the security settings in a later step.

2. Create a blank ODI repository.

1. In ODI, select File, then New.

2. Select 'Master Repository Creation Wizard' to start the Master Repository Creation wizard.

3. At the Repository Connection page (Step 1 of 3), enter details for the local database.
'User' is the schema where the ODI repository will be stored. 'DBA User' is a user on this database with DBA privileges such as 'SYSTEM' (do not use SYS which requires logging in as SYSDBA). Be sure to use an Id value greater than 500. Content with repository Id of 500 or less is considered to be associated with content originally shipped by Oracle.

4. At the Authentication page, (Step 2 of 3), configure to use External Authentication.
Supply the Supervisor User and Password specified when originally installing the BI Application.

5. At the Password Storage page, (Step 3 of 3), specify the Internal Password Storage parameters.
You will be notified that a Master repository already exists and prompted if you want to remove it. Select 'Yes'.

6. At the Repository Connection Information page, create a repository login connection.
Configure as Master Repository Only. For the ODI User and password, use the ODI Supervisor user specified during installation. For the database user, use the database schema for the ODI repository specified during installation.

7. Navigate to Topology - Repositories - Work Repositories, and right click and select the 'New Work Repository' option.

8. At the Create Work Repository page (Step 1 of 2), provide the same credentials as used to create the master repository.
The work repository needs to be in the same schema as the master repository.

You will be prompted that a Work Repository already exists. Select 'No' to overwrite it.

9. At the Specify ODI Work Repository properties page, (Step 2 of 2) use the same Id as specified when creating the master repository.
Specify any value for the password, this does not correspond to the Supervisor or database passwords. The password can even be left blank. Ensure the repository type is 'Development'.

10. At the Confirmation dialog 'Would you like to create a login for the work repository?', click No.
There is no need to create a login for the work repository.

11. Log off from the repository and edit the Repository connection details, checking the Work Repository radio button and selecting the work repository just created.

3. Import content into blank ODI repository.
On Windows:

<JAVA_HOME>\bin\java.exe -client -Xms32m -Xmx1024m -classpath <ODI_HOME>\oracledi.sdk\lib*;<ODI_HOME>\inventory\Scripts\ext\jlib*;<ODI_HOME>
\modules\oracle.idm_11.1.1*;<ODI_HOME>\modules\oracle.jps_11.1.1*;<BIAODIUTIL_HOME>\import\core\import*;<BIAODIUTIL_HOME>\import\core\lib\bia-odi-
util.jar oracle.apps.biaodiutil.Import MODE=IMPREGEN FILEDIR=<EXP_FILE_DIR> PLV=<PLV_CODE> JPSCONFIGFILE=<JPS_CONFIG_FILE> LOGDIR=<LOG_DIR>

For example:

C:\Java64\jdk1.6.0_35\bin\java.exe -client -Xms32m -Xmx1024m -classpath C:\oracle\product\odi11.1.1.7\oracledi.sdk\lib*;C:\oracle\product
\odi11.1.1.7\inventory\Scripts\ext\jlib*;C:\oracle\product\odi11.1.1.7\modules\oracle.idm_11.1.1*;C:\oracle\product\odi11.1.1.7\modules
\oracle.jps_11.1.1*;C:\temp\biaodiutil\import\core\import*;C:\temp\biaodiutil\import\core\lib\bia-odi-util.jar oracle.apps.biaodiutil.Import
MODE=IMPREGEN FILEDIR=c:/temp/export2/ PLV=BIA_11

On UNIX/Linux:

<JAVA_HOME>\bin\java.exe -client -Xms32m -Xmx1024m -classpath

"<ODI_HOME>/oracledi.sdk/lib/:<ODI_HOME>/inventory/Scripts/ext/jlib/:<ODI_HOME>/modules/oracle.idm_11.1.1/:<ODI_HOME>/modules/oracle.jps_11.1.1/:<B
IAODIUTIL_HOME>/import/core/import/*:<BIAODIUTIL_HOME>/import/core/lib/bia-odi-util.jar" oracle.apps.biaodiutil.Import MODE=IMPREGEN
FILEDIR=<EXP_FILE_DIR> PLV=<PLV_CODE> JPSCONFIGFILE=<JPS_CONFIG_FILE> LOGDIR=<LOG_DIR>

For example:

java -client -Xms32m -Xmx1024m -classpath
"/scratch/aime/oracle/product/11.1.1/Oracle_ODI_1/oracledi.sdk/lib/:/scratch/aime/oracle/product/11.1.1/Oracle_ODI_1/inventory/Scripts/ext/jlib/:/s
cratch/aime/oracle/product/11.1.1/Oracle_ODI_1/modules/oracle.idm_11.1.1/:/scratch/aime/oracle/product/11.1.1/Oracle_ODI_1/modules/oracle.jps_11.1.
1/:/scratch/aime/work/mw3463/Oracle_BI1/biapps/lib/*:/scratch/aime/work/mw3463/Oracle_BI1/biapps/biaodiutil/lib/bia-odi-util.jar"
oracle.apps.biaodiutil.Import MODE=IMPREGEN FILEDIR=c:/temp/export2/ PLV=BIA_11

4. Add an ODI Administrator1 user
When the repository is refreshed, log on as the SUPERVISOR user (password welcome) and add the following user:Name: Administrator1.Password: Admin12345.Check the 'Supervisor' property.

5. Enable External Authentication.
In ODI Studio when not logged-in, select ODI, then Switch Authentication Mode. You need to switch ODI to use external authentication. When switching it should map the user, Administrator1, to the user named Administrator1 already defined in the external authentication store (the WebLogic embedded LDAP in the BI domain).

6. Importing Security Settings Into the ODI Repository.
In this procedure you will import the security settings that you exported in Exporting Security Settings from Original ODI Repository step.

1. Log into ODI Studio.

2. Navigate to Security, and select Users section and delete the exiting user (Administrator1).

3. Select Import Security Settings.

4. In the Import Security Settings dialog, select Import From a Folder, and browse for the export file.

5. Click Yes in the Confirmation dialog.
You can now log into the ODI Repository with the security settings configured when the ODI Repository was created using the Oracle Business Analytics Suite RCU.

7. Next Steps.
In Oracle BI Applications Configuration Manager, register sources, configure parameters and generate load plans.

8. Regenerate Scenarios.
In Oracle BI Applications Configuration Manager, regenerate the scenarios.

1.3.16 Agreement Status Warehouse Codes Not Set Correctly for E-Business Suite Sources

Agreement status codes are not set correctly in Oracle Business Analytics Warehouse.

This issue applies to:

- Oracle E-Business Suite R11.5.10.0

- Oracle E-Business Suite R12.0.x

- Oracle E-Business Suite R12.1.1.x

- Oracle E-Business Suite R12.1.2.x

- Oracle E-Business Suite R12.1.3.x

- Oracle E-Business Suite R12.2.x

Workaround

1. Execute the Domain-only Load Plan again.

2. Execute SDE_ORA_PurchaseAgreementHeaderFact in FULL MODE.

3. Execute SDE_ORA_PurchaseAgreementLineFact in FULL MODE.

4. Execute SDE_ORA_StatusDimension_PurchaseAgreement in FULL MODE.

5. Execute SIL_StatusDimension.

6. Execute SIL_PurchaseAgreementHeaderFact.

7. Execute SIL_PurchaseAgreementLineFact.

8. Execute PLP_PurchaseAgreementHeaderFact_PurchaseScheduleLine.

9. Execute PLP_PurchaseAgreementLineFact_PurchaseScheduleLine.

10. To set up the FULL MODE, execute the following command:

UPDATE W_ETL_LOAD_DATES SET COMMITTED='0' WHERE PACKAGE_NAME in ('SDE_ORA_PurchaseAgreementHeaderFact','SDE_ORA_PurchaseAgreementLineFact','SDE_ORA_StatusDimension_PurchaseAgreement');
COMMIT;

1.3.17 Agreement Status Warehouse Codes Not Set Correctly for JDE Suite Sources

PO_DOCUMENT_SUBTYPES warehouse codes for Agreement are not set correctly in Oracle Business Analytics Warehouse.

This issue applies to:

- JD Edwards EnterpriseOne 9.0.x

- JD Edwards EnterpriseOne 9.1.x

Workaround

1. Execute the Domain-only Load Plan again.

2. Execute SDE_JDE_TransactionTypeDimension_PurchaseOrder in FULL MODE.

3. Execute SIL_TransactionTypeDimension.

4. To set up the FULL MODE, execute the following command:

UPDATE W_ETL_LOAD_DATES SET COMMITTED='0' WHERE PACKAGE_NAME in ('SDE_JDE_TransactionTypeDimension_PurchaseOrder');
COMMIT;

1.3.18 LPG Trimming Out Scenarios in Load plans for Fusion Applications Sources

If you are implementing V11.1.1.8.1 in-premise with Fusion Applications, then you might find that the LPG is trimming out some scenarios, because Oracle BI Applications Configuration Manager only sets the DSNs for the following four of the Fusion Applications logical schemas below:

- DS_FUSION10FSCM_SRCFILES

- DS_OBIEECRM

- DS_OBIEEFSCM

- DS_OBIEEHCM

This source registration must be completed before generating the load plans else the above issue will manifest.

The Workaround below follow Oracle's standard customization process, which is required for future ODI metadata patches to work in your repository.As part of the standard customization process, you 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 default installed scenario name. For general customization guideline, refer to section 'Customizing the Oracle Business Analytics Warehouse' in Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Applications.

Workaround

1. In your ODI repository, execute the below query to check the DSN value for the logical schemas.

SELECT LSCHEMA_NAME,FF_CODE,FVALUE FROM (SELECT I_LSCHEMA,LSCHEMA_NAME,FF.FF_CODE,FFV.NUM_VALUE,FFV.SHORT_TXT_VALUE
FVALUE,FFV.I_OBJECTS
FROM SNP_LSCHEMA LS LEFT OUTER JOIN
SNP_FF_VALUEM FFV ON  FFV.I_INSTANCE = LS.I_LSCHEMA AND FFV.I_OBJECTS=2100 AND FFV.FF_CODE IN ('LS_DATASOURCE_NUM_ID') LEFT OUTER JOIN SNP_FLEX_FIELD FF  ON FF.FF_CODE=FFV.FF_CODE AND FF.I_OBJECTS=FFV.I_OBJECTS
WHERE (LSCHEMA_NAME LIKE '%FUSION%' OR  LSCHEMA_NAME LIKE '%OBIEE%')
)
ORDER BY LSCHEMA_NAME,FF_CODE DESC;

DSN flexfields should have the value 200. If any DSN flexfields do not have the value 200, then you must update them, for example rows might have null or -1 values.

2. Open the ODI Studio client and login to the appropriate repository.

3. Navigate to Topology > Logical Architecture > Technologies > File, then under File ensure that the DSN Flexfield is set to the same value of 200 for all of the relevant Fusion Logical schemas.

4. Repeat the previous step for relevant Fusion Logical schemas under 'Oracle BI' and 'Oracle UCM' folders (UCM_FUSION_1_0).

5. Execute the SQL command mentioned in Step 1 to ensure that the Fusion logical schemas are set up correctly.
DSN flexfields should have the value 200, otherwise you must correct the configuration. You must do this before generating the Load Plan.

6. If any Fusion Applications Load Plans were generated before the above steps were performed, then delete them and regenerate the Load Plans.

1.3.19 Deploying Oracle BI Applications Duty Roles for ETL

This issue applies to new unmodified Oracle BI Applications installations with data that is sourced from Fusion Applications 11.1.8 (Release 8). This issue does not apply if the Fusion Applications Rel8 environment has been upgraded from a previous version of Fusion Applications.

In Fusion Applications 11.1.8, the Oracle BI Applications Duty Roles required for ETL are not deployed by default. If you are sourcing data into Oracle BI Applications V11.1.1.8.1 from a new installation of Fusion Applications Rel8 (not upgraded from a previous version of Fusion Applications), then you must deploy the Duty Roles required for ETL as described in the Workaround below.

If the Oracle BI Applications Duty Roles have not been deployed into the BI Policy Store of the Fusion Applications Rel8 environment, then the following error is received on ETL against the Fusion Applications Rel8 source:

[nQSError: 43119] Query Failed:

[nQSError: 13017] User or application role has not been granted the Direct Database Access privilege to access the database 'oracle.apps.fscm.model.analytics.applicationModule.FscmTopModelAM_FscmTopMode lAMLocal'. Please verify the User/Group Permissions in the Oracle BI Administration Tool.

Workaround

For instructions on how to deploy the required Duty Roles into the BI Policy Store of the Fusion Applications Rel8 environment, see 'Deploying BI Applications Duty Roles in Fusion Applications 11.1.8 (Rel8) Source for BI Applications 11.1.1.8.1 (Document Id 1927380.1)' on My Oracle Support (https://support.oracle.com).

1.3.20 Standard UOM Conversion for Inventory Lot Monthly Balance Fact

A number of calculations in the Inventory Balances subject area refer to an Oracle Business Analytics Warehouse column that does not exist. This causes reports containing the affected metrics to fail with an 'invalid identifier' message.

For Patch Bundle 5 and later, the issue is corrected by adding the missing columns to the Inventory Lot Monthly Balance Fact table and all associated mappings.

Prior to receiving this correction, the solution is to manually remove the references to the missing columns from the RPD.

Workaround

1. In Oracle BI Administration Tool, open the metadata repository file (RPD).

2. In the Business Model and Mapping pane, locate and expand Fact – Supply Chain – Inventory Balance.

3. Expand the Sources node.

4. Locate and double-click on the Fact_Agg_W_INV_LOT_MONTHLY_BAL_F source to open it.

5. Select the Column Mapping tab.

6. Select the Available Quantity line and then click the Edit Expression button.

7. Change the expression to:

("Oracle Data Warehouse"."Catalog"."dbo"."Fact_W_INV_LOT_MONTHLY_BAL_F"."ON_HAND_QTY" - "Oracle Data Warehouse"."Catalog"."dbo"."Fact_W_INV_LOT_MONTHLY_BAL_F"."RESERVED_QTY" )

8. Click OK to save the change.

9. Repeat these steps for the Fact_W_INV_LOT_MONTHLY_BAL_F_Quarter and Fact_W_INV_LOT_MONTHLY_BAL_F_Year sources.

10. Save and publish the updated RPD.

1.3.21 Cloud Adaptor - Employee Expenses Is Supported in Patch Bundle 6 (PB6)

If you are deploying a Fusion Applications Cloud source system, then Employee Expenses is supported only if you have applied Patch Bundle 6. When you create a load Plan, on the Define Load Plan\Select Fact Groups tab, you select Employee Expenses.

If you have not applied Patch Bundle 6, then Employee Expenses is not supported, and you should not select the Employee Expenses option on the Define Load Plan\Select Fact Groups tab.

1.3.22 Database Error ORA-00907 Missing Right Parenthesis Error When Running Load Plan

When you execute a Load Plan, you might encounter the following error:

ORA-00907: missing right parenthesis error when running Load plan

If so, you need to create a property file named 'sceregenparams.properties' in the \log file directory, as described in the Workaround below.

Workaround

1. Create a property file called 'sceregenparams.properties' under the log file directory and add the properties below:

LEVEL2_FOLDER_NAME = <Add the Adaptor folder names here separated by comma>
FOLDER_LIST = ANY
LOG_FILE_DIR = <Tech switch process Log file Folder>
MARKER_OWNERSHIP = <Not required>
MARKER_PROGRESS = DONE_OR_NONE
OLDER_THAN_DAYS = -1
GENERATION_MODE = REPLACE
MATERIALIZE = 0

2. Open a command line utility.

3. Navigate to the C:\<Middleware Home>\<BI_ORACLE_HOME>\biapps\biaodiutil\lib directory.

4. Run the following command to generate the scenarios.
On Windows:

<JAVA_HOME>\bin\java.exe \-client \-Xms32m \-Xmx1024m \-classpath <ODI_HOME>\oracledi.sdk\lib\*;<ODI_HOME>\inventory\Scripts\ext\jlib\*;<ODI_HOME>\modules\oracle.idm_11.1.1\*;<ODI_HOME>\modules\oracle.jps_11.1.1\*;<BIAODIUTIL_HOME>\import\core\import\*;<BIAODIUTIL_HOME>\import\core\lib\bia-odi-util.jar oracle.apps.biaodiutil.Import MODE=SCEREGEN FILEDIR=<EXP_FILE_DIR> PLV=<PLV_CODE> JPSCONFIGFILE=<JPS_CONFIG_FILE> LOGDIR=<LOG_DIR>

For example:

C:\Java64\jdk1.6.0_35\bin\java.exe \-client \-Xms32m \-Xmx1024m \-classpath C:\oracle\product\odi11.1.1.7\oracledi.sdk\lib\*;C:\oracle\product\odi11.1.1.7\inventory\Scripts\ext\jlib\*;C:\oracle\product\odi11.1.1.7\modules\oracle.idm_11.1.1\*;C:\oracle\product\odi11.1.1.7\modules\oracle.jps_11.1.1\*;C:\temp\biaodiutil\import\core\import\*;C:\temp\biaodiutil\import\core\lib\bia-odi-util.jar oracle.apps.biaodiutil.Import MODE=SCEREGEN FILEDIR=c:/temp/export2/ PLV=BIA_11

On UNIX/Linux:

<JAVA_HOME>\bin\java.exe \-client \-Xms32m \-Xmx1024m \-classpath "<ODI_HOME>/oracledi.sdk/lib/*:<ODI_HOME>/inventory/Scripts/ext/jlib/*:<ODI_HOME>/modules/oracle.idm_11.1.1/*:<ODI_HOME>/modules/oracle.jps_11.1.1/*:<BIAODIUTIL_HOME>/import/core/import/*:<BIAODIUTIL_HOME>/import/core/lib/bia-odi-util.jar" oracle.apps.biaodiutil.Import MODE=SCEREGEN FILEDIR=<EXP_FILE_DIR> PLV=<PLV_CODE> JPSCONFIGFILE=<JPS_CONFIG_FILE> LOGDIR=<LOG_DIR>

For example:

java \-client \-Xms32m \-Xmx1024m \-classpath "/scratch/aime/oracle/product/11.1.1/Oracle_ODI_1/oracledi.sdk/lib/*:/scratch/aime/oracle/product/11.1.1/Oracle_ODI_1/inventory/Scripts/ext/jlib/*:/scratch/aime/oracle/product/11.1.1/Oracle_ODI_1/modules/oracle.idm_11.1.1/*:/scratch/aime/oracle/product/11.1.1/Oracle_ODI_1/modules/oracle.jps_11.1.1/*:/scratch/aime/biaodiutil/import/core/import/*:/scratch/aime/biaodiutil/import/core/lib/bia-odi-util.jar" oracle.apps.biaodiutil.Import MODE=SCEREGEN FILEDIR=c:/temp/export2/ PLV=BIA_11

5. Enter the ODI Repository connection details when prompted.

6. Monitor the process by viewing the command line window or the log files being written to the logs directory.

1.3.23 Using a Third Party Driver For DB2 400 UDB

To deploy ODI with a DB2 400 UDB database (also known as 'Tech Switch'), Oracle BI Applications is installed by default with the IBM DB2 Datadirect Driver for Oracle Data Integrator. If you are not able to use the IBM DB2 Datadirect Driver, then follow the Workaround below to use a third-party driver.

Workaround

1. Download the IBM Toolbox JDBC driver, jt400.jar.
It is implemented by making direct socket connections to the database host server. The Toolbox runs on any JVM. The class name to register is com.ibm.as400.access.AS400JDBCDriver.

2. Save the driver file as follows:
On Windows, if using a standalone agent, then save the file in:

<ODI_HOME>\oracledi\agent\drivers

On Windows, if using a Studio agent (Local No Agent), then save the file in:

C:\Users\<username>\AppData\Roaming\odi\oracledi\userlib

On Linux, if using ODI Enterprise Edition Web agent (Local No Agent), then save the file in:

WL_HOME\server\lib

Edit the commEnv.cmd/sh script in WL_HOME/common/bin and prepend your JAR file to the weblogic_classpath environment variable.

3. Go to the Topology Navigator Editors > Data Server Editor > JDBC and use IBM Toolbox for Java (Type 4) driver.

4. Use driver JDBC URL as shown below:

jdbc:as400://hostname/LibraryName

1.3.24 Load Plan Schedules Missing After Regeneration

After Load Plan is regenerated in Oracle BI Applications Configuration Manager, the Load Plan schedule is missing.

Workaround

Before regenerating a Load Plan, remove all existing schedules and recreate them after regeneration is complete.

1.3.25 Insufficient Memory During Load Plan Execution

If you are generate a Load Plan with many fact groups and the Load Plan generation 'hangs' while reporting the status 'In Progress', then increase the memory as specified in the Workaround below.

Workaround

1. Restart BI Server and try to generate the Load Plan again.
If you get the same issue, performs Steps 2 and 3 below.

2. Increase BI Server memory settings to 3GB(-Xmx3072m) in <MWHome>/user_projects/domains/bifoundation_domain/bin/setBIAppsDomainEnv.sh.

3. Restart BI Server from Administration Console.
For example:

if [ "${SVR_GRP}" = "obi" ] ; then
#  BIA Managed Server : set max heap to 2GB
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
SERVER_MEM_ARGS="-Xms512m -Xmx3072m -XX:MaxPermSize=1024m"
export SERVER_MEM_ARGS
fi
if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
SERVER_MEM_ARGS="-Xms512m -Xmx3072m -XX:MaxPermSize=1024m"
export SERVER_MEM_ARGS
fi

4. Regenerate and re-execute the Load Plan.

1.3.26 Human Resources E-Business Suite Payroll patches for Payroll Analytics

If you are implementing Oracle Human Resources Analytics Payroll Subject Area for E-Business Suite, then it is mandatory to follow the E-Business Suite Payroll patching policy specified in My Oracle Support Note 295406.1.(Mandatory Family Pack / Rollup Patch (RUP) levels for Oracle Payroll').

1.3.27 Deploying Multiple Instances of the Same Source

If you are implementing multiple instances of the same source, you can find additional information about how to do this in 'Multi-Instance Source Support in BI Applications 11.1.1.7.1, 11.1.1.8.1' (Support Note Doc ID 1633996.1) on My Oracle Support.

1.3.28 Issue With Scenario SDE_ORA_PURCHASECOSTFACT for Financial Analytics with E-Business Suite R12.x Adapters

After applying the 11.1.1.8.1 PB6C8 patch, you might encounter a regeneration issue with scenario SDE_ORA_PurchaseCostFact in EBS R12.x adapters with Financial Analytics.

The following Workaround uses the Oracle recommended standard customization process. For more detailed information about this process, refer Section 'Customizing the Oracle Business Analytics Warehouse' in 'Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Applications'.

Workaround

1. In ODI Studio, navigate to 'BI Apps Project'.

2. Under the Mappings folder, create a new custom SDE adaptor folder based on the appropriate EBS release version in your environment, as follows:

1. Right-click the Mappings folder and select New Sub-Folder.

2. Specify the Name as CUSTOM_<Original Folder Name>.
For example, if this is for EBS 11i, create custom folder CUSTOM_SDE_ORA11510_Adaptor. This represents the custom SDE folder for the original SDE_ORA11510_Adaptor folder.

3. In the Designer tab, click the Connect Navigator button.

4. Select Edit Release Tags.

5. Select the release tag that corresponds to your source.
For example, EBS_11_5_10.

6. Select the custom SDE folder you created and add it to the release tag.

7. Click Next. then click Finish.

3. Enable versioning for the preconfigured Task Folder, SDE_ORA_PurchaseCostFact, to be customized.
The version comment should indicate that this is the base version of the task. Subsequent patches applied to this task in the future require increasing the version in the comment so that it can be compared to the original task to identify any changes.

1. Navigate to the appropriate EBS SDE folder (e.g. SDE_ORA11510_Adaptor), right-click the Task folder SDE_ORA_PurchaseCostFact and select Version > Create Version.

2. Accept the default version number, 1.0.0.0.

3. Add a description indicating that this is the original version of this task.

4. Duplicate the Task folder to be customized (i.e. SDE_ORA_PurchaseCostFact) by copying it.
Cut and paste the copied task folder to the Custom adaptor folder that you have created (e.g. CUSTOM_SDE_ORA11510_Adaptor), and rename it to remove the 'Copy of…' prefix.

5. 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 that all changes that have been introduced.

6. Create another version of the copied task SDE_ORA_PurchaseCostFact.
The version comment should indicate this is the customized version. Use the same steps as above.

7. Locate the data store W_PURCH_COST_FS_TMP under the 'Models' folder.

8. Open the task folder SDE_ORA_PurchaseCostFact in the custom adaptor folder.

9. Open the interface SDE_ORA_PurchaseCostFact.W_PURCH_COST_FS_TMP. Click on the 'Mapping' tab.

10. In the 'Mapping' tab, drag the data store from the Models folder directly on top of the target data store in the interface.

11. When prompted to auto-map the columns, select 'Yes'.

12. Click Apply, then click Save.

13. Before regenerating the scenario, go to the original task folder SDE_ORA_PurchaseCostFact in the default installed mapping folder (e.g. SDE_ORA11510_Adaptor), and delete the existing default installed scenario (e.g. SDE_ORA11510_ADAPTOR_ SDE_ORA_PurchaseCostFact).

14. Go back to the modified SDE_ORA_PurchaseCostFact in the custom folder, navigate 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 default installed scenario name. For example, SDE_ORA11510_ADAPTOR_SDE_ORA_PurchaseCostFact for EBS 11i, or SDE_ORAR1213_ADAPTOR_SDE_ORA_PurchaseCostFact for EBS R12.1.3.

1.3.29 Missing Columns GL_JOURNAL_DT and JOURNAL_LINE_REFERENCE Causing Execution Error

This issue applies to all instances of E-Business Suite, PSFT, JDE, and FUSION.

The columns 'GL_JOURNAL_DT' and 'JOURNAL_LINE_REFERENCE' are missing from the Mapping 'SIL_GLOtherFact'. During execution, the error 'scenario SILOS_SIL_GLOTHERFACT does not exist in work repository' is reported.

Workaround

Apply the following Workaround in both of the interfaces (that is, the temp and main interface) of the map 'SIL_GLOtherFact'.

1. In ODI Studio, navigate to 'BI Apps Project'.

2. Expand the BI Apps Project, and navigate to Mappings\SILOS.

3. Navigate to SIL_GLOtherFact\Interfaces\SIL_GLOtherFact.W_GL_OTHER_F.
Double click to open the Interface and then open Quick Edit tab and display the Mapping section. Click the edit cell icon to display the Target Datastore Select dialog.

Display the Target Datastore Select dialog and select the target datastore.

Browse the 'Oracle BI Applications' Model to find Fact, and then navigate to datastore 'General Ledger Journal Entries'. Click OK, and when prompted 'Do you want to perform an Automatic Mapping', click No.

4. Save changes and close interface.

5. Navigate to SIL_GLOtherFact\Interfaces\SIL_GLOtherFact.W_GL_OTHER_F_SQ_W_GL_OTHER_FS.

6. Double click the interface SIL_GLOtherFact.W_GL_OTHER_F_SQ_W_GL_OTHER_FS to display the Overview page on the right hand side, then display the Quick Edit tab.

7. On the Quick Edit tab, navigate to the Mappings area, then locate the columns 'GL_Journal_DT' and 'JOURNAL_LINE_REFERENCE'.

8. Delete the columns 'GL_Journal_DT' and 'JOURNAL_LINE_REFERENCE', using the red X icon highlighted in the right hand side mapping expression.
Save the changes, and close the interface.

9. Click File, the Save.

10. Regenerate the scenario for this map (if it is available).
If the scenario is not available, then first generate the scenario.

1.3.30 Change to Table Definitions in Inventory Analysis

If you are deploying Inventory Analysis, then you must update the table definition for the Inventory Lot Monthly Balance Fact table in Oracle Business Analytics Warehouse.

Workaround

Execute the Generate DW DDL procedure, set the Refresh Mode to INCREMENTAL, and set the Table Mask to specifically target W_INV_LOT_MONTHLY_BAL_F. This will add two new columns, STANDARD_UOM_CODE and STANDARD_UOM_CONV_RATE, to the table.

1.4 Issues and Workarounds for Golden Gate

There are no reported issues that are related to the use of Golden Gate.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.