These issues and workarounds are for specific areas, such as installation, upgrade, security, and documentation.
This issue involves installing Oracle Business Intelligence Applications.
This issue applies to operating system certification.
Workaround
Click Continue to resume the installation.
These issues involve upgrading Oracle Business Intelligence Applications.
Note:
For OBIA version 11.1.1.8.1, you can upgrade from OBIA version 11.1.1.8.1 PB6 only. When you upgrade from 11.1.1.8.1 PB6, you need to move directly to 11.1.1.9.2 and not 11.1.1.9.1. If you are on OBIA version 11.1.1.9.1, then you can upgrade to version 11.1.1.9.2.For information about upgrading from Oracle BI Applications V11.1.1.8.1 PB6, refer to Oracle BI Applications Upgrade Guide (Doc ID 2002382.1) on My Oracle Support (support.oracle.com).
OMBOOKING_ENABLED
A new parameter is introduced into BI Applications Configuration Manager in Release 9.1 called OMBOOKING_ENABLED. This parameter is related to the subject area of Sales Booking Lines Fact and is an advanced feature of Oracle Business Intelligence Applications. It can powerfully analyze the changing history of every sales order by any dimension. However, its ETL is complex and require significant experience to implement. Consequently, the ETL is disabled by default.
Note:
Make sure you clearly understand the benefit vs. involvement before you enable it. You can enable it by setting the value of this parameter to Y before running Upgrade Load Plan.OMCUSTSTATHIST_ENABLED
A new parameter is introduced into BI Applications Configuration Manager in Release 9.1 called OMCUSTSTATHIST_ENABLED. This parameter is related to the subject area of Customer Status History Fact & is an advanced feature of Oracle Business Intelligence Applications. It can powerfully analyze every customer's life cycle, that is, acquisition, activity, and attrition, across all sales orders. However, its ETL is complex and require significant experience to implement. Consequently, the ETL is disabled by default.
Note:
Make sure you clearly understand the benefit vs.involvement before you enable it. You can enable it by setting the value of this parameter to Y before running Upgrade Load Plan.Workaround
After upgrading from 11.1.1.8.1 PB6 to 11.1.1.9.2, the data warehouse schema has an issue because the precision value is set incorrectly during the schema upgrade.
Execute this statement in the data warehouse (DW schema) before running the Incremental Load Plan for Procurement and Spend Analytics.
ALTER TABLE w_purch_change_order_f_del MODIFY (DATASOURCE_NUM_ID NUMBER (10,0));
The ODI '11.1.1.9.1P' PeopleSoft Upgrade Load Plans contain steps that cause a partial refresh of W_TLB_ENTRY_STATUS_DS, which is not required.
Workaround
Before you execute any of the 11.1.1.9.1P PeopleSoft Upgrade Load Plans, perform the following workaround:
In ODI Designer, navigate to BI Apps Project > Load Plans and Scenarios > Predefined Load Plans > Upgrade, and open the load plan that is appropriate to your Peoplesoft version:
- Upgrade BIApps 111181 to 111191 PSFT 90 HCM
- Upgrade BIApps 111181 to 111191 PSFT 91 HCM
- Upgrade BIApps 111181 to 111191 PSFT 92 HCM
Navigate to the UPGRADE_FACTS > Is HCM Enabled > HCM > SDE > Time and Labor > TLSTATUS_DIM node, and clear the check box for this node.
Navigate to the UPGRADE_FACTS > Is HCM Enabled > HCM > SIL > Time and Labor > TLSTATUS_DIM node, and clear the check box for this node.
Save the load plan and start the ETL.
This issue applies to PeopleSoft V9.1 data sources.
When you execute the Upgrade Load Plan 'Upgrade BIApps 111181 to 111191 PSFT 91 HCM', the data for W_TLNT_PRFL_ACHVMNT_FS is not loaded due to a variable refresh issue.
Workaround
Before you execute the Upgrade Load Plan Upgrade BIApps 111181 to 111191 PSFT 91 HCM, perform the workaround.
In ODI Designer, navigate to BI Apps Project > Load Plans and Scenarios > Predefined Load Plans > Upgrade, and open the Upgrade BIApps 111181 to 111191 PSFT 91 HCM Load Plan.
Navigate to the PSFT_91_HCM > UPGRADE_FACTS > Is HCM Enabled > 'When Value = Y' > HCM > SDE > TLNTMGMT_FG Step.
In the Variables List for TLNTMGMT_FG Step, select the refresh checkbox for the variable named HR_PSFT_TLNT_CONTENT_TYPES_FILTER.
Save the Load plan and start the ETL.
The Upgrade Load Plans for Upgrade BIApps 111181 to 111191 PSFT 91 HCM are unable to upgrade data in column cost_center_wid column in the Absence and Accrual Fact.
Workaround
Before you execute the Upgrade Load Plan 'Upgrade BIApps 111181 to 111191 PSFT 91 HCM', perform this workaround.
In ODI Designer, navigate to BI Apps Project > Upgrade > PLP_111181_to_111191_Upgrade > PLP_AbsenceEventFact_UPG.
Navigate to the interface PLP_AbsenceEventFact_UPG.W_Absence_Event_F.
Display the Flow tab and change the value for OBI_SQL_OVERRIDE in IKM property to:
UPDATE QUALIFY(W_ABSENCE_EVENT_F) ABS_F SET ABS_F.cost_center_wid=(select WRKFC_F.cost_center_wid from QUALIFY(W_WRKFC_EVT_F) WRKFC_F WHERE WRKFC_F.ASSIGNMENT_ID=ABS_F.ASSIGNMENT_ID AND WRKFC_F.DATASOURCE_NUM_ID=ABS_F.DATASOURCE_NUM_ID And (WRKFC_F.MAX_SEQ_IND=1) And (ABS_F.ABSENCE_DT >=WRKFC_F.EFFECTIVE_FROM_DT AND ABS_F.ABSENCE_DT < WRKFC_F.EFFECTIVE_TO_DT)) WHERE (ABS_F.cost_center_wid =0) and ABS_F.ASSIGNMENT_ID in (select WRKFC_F.ASSIGNMENT_ID from QUALIFY(W_WRKFC_EVT_F) WRKFC_F WHERE WRKFC_F.ASSIGNMENT_ID=ABS_F.ASSIGNMENT_ID AND WRKFC_F.DATASOURCE_NUM_ID=ABS_F.DATASOURCE_NUM_ID And (WRKFC_F.MAX_SEQ_IND=1) And (ABS_F.ABSENCE_DT >=WRKFC_F.EFFECTIVE_FROM_DT AND ABS_F.ABSENCE_DT < WRKFC_F.EFFECTIVE_TO_DT))
Save the interface, then regenerate the scenario.
Navigate to BI Apps Project - Upgrade > PLP_111181_to_111191_Upgrade > PLP_AccrualTransactionFact_UPG.
Navigate to the interface PLP_AccrualTransactionFact_UPG.W_Accrual_Xact_F.
Display the Flow tab and change the value for OBI_SQL_OVERRIDE in IKM property to:
UPDATE QUALIFY(W_ACCRUAL_XACT_F) ACR SET ACR.cost_center_wid=(select WFC.cost_center_wid from QUALIFY(W_WRKFC_EVT_F) WFC WHERE WFC.ASSIGNMENT_ID = ACR.ASSIGNMENT_ID AND WFC.DATASOURCE_NUM_ID=ACR.DATASOURCE_NUM_ID And (ACR.TRANSACTION_DT >= WFC.EFFECTIVE_FROM_DT AND ACR.TRANSACTION_DT < WFC.EFFECTIVE_TO_DT) And (WFC.MAX_SEQ_IND=1)) WHERE (ACR.cost_center_wid =0) and ACR.ASSIGNMENT_ID in (select WFC.ASSIGNMENT_ID from QUALIFY(W_WRKFC_EVT_F) WFC WHERE WFC.ASSIGNMENT_ID = ACR.ASSIGNMENT_ID AND WFC.DATASOURCE_NUM_ID=ACR.DATASOURCE_NUM_ID And (ACR.TRANSACTION_DT >= WFC.EFFECTIVE_FROM_DT AND ACR.TRANSACTION_DT < WFC.EFFECTIVE_TO_DT) And (WFC.MAX_SEQ_IND=1))
Save the interface, then regenerate the scenario.
This issue applies to Oracle Business Analytics Warehouse tables.
The Upgrade Load Plan BIApps 111181 to 111191 for HCM PSFT and EBS is unable to refresh (truncate and reload) the following tables due missing step for Oracle Business Analytics Warehouse tables W_WRKFC_EVT_AGE_F, W_WRKFC_EVT_POW_F, W_WRKFC_EVT_MERGE_F, W_WRKFC_EVT_MONTH_F, and W_WRKFC_EVT_POW_F.
Workaround
Before you execute the Upgrade Load Plan, truncate the warehouse tables.
In ODI Designer, navigate to Load Plan Definition > Reset History Tracking Table.
Right click Add Step with the following information:
Step Type: Run Scenario Step Location: Add a Child Step to Selection Scenario name: RESET_W_ETL_LOAD_DATES Step Name: Reset - HCM Warehouse version: -1
Select the new step and navigate to Scenario Variables section under the Property Inspector, edit the following variables and set the Value column without any extra spaces:
BIAPPS.DDL_TABLE_LIST
For the following EBS upgrade Load plans:
- Upgrade BIApps 111181 to 111191 EBS 11510
- Upgrade BIApps 111181 to 111191 EBS 120
- Upgrade BIApps 111181 to 111191 EBS 1211
- Upgrade BIApps 111181 to 111191 EBS 1212
- Upgrade BIApps 111181 to 111191 EBS 1213
- Upgrade BIApps 111181 to 111191 EBS 122
Set BIAPPS.DDL_TABLE_LIST to:
W_WRKFC_EVT_AGE_F,W_WKFC_EVT_POW_F,W_WRKFC_EVT_MERGE_F,W_WRKFC_EVT_MONTH_F,W_R CRTMNT_APPL_A,W_RCRTMNT_HIRE_A,W_RCRTMNT_RQSTN_A_TMP2,W_RCRTMNT_RQSTN_A
For the following PSFT upgrade Load plans:
- Upgrade BIApps 111181 to 111191 PSFT 90 HCM
- Upgrade BIApps 111181 to 111191 PSFT 91 HCM
- Upgrade BIApps 111181 to 111191 PSFT 92 HCM
Set BIAPPS.DDL_TABLE_LIST to:
W_TLNT_PROFILE_TYPE_D_TL,W_WRKFC_EVT_AGE_F,W_WKFC_EVT_POW_F,W_WRKFC_EVT_MERGE_ F,W_WRKFC_EVT_MONTH_F,W_TLNT_PRFL_ACHVMNT_F,W_TLNT_PRFL_RQRMNT_F,W_RCRTMNT_APP L_A,W_RCRTMNT_HIRE_A,W_RCRTMNT_RQSTN_A_TMP2,W_RCRTMNT_RQSTN_A
BIAPPS.DATASOURCE_NUM_ID
Set to 999, or if the value of WH_DATASOURCE_NUM_ID is different to 999, then use the value of WH_DATASOURCE_NUM_ID.
Save the load plan, and run the ETL.
This issue applies to incorrect datastore name during upgrade.
In Oracle BI Applications Release 8.1, the override task PLP_RecruitmentRequisitionAggregate_Load.W_RCRTMNT_RQSTN_A_Update uses the incorrect datastore name W_WRKFC_EVT_AGE_F. The correct name is W_RCRTMNT_RQSTN_A. The load tracking step in W_ETL_LOAD_DATES use the incorrect datastore name. This affects upgrade for Oracle BI Applications 11.1.1.8.1 PB6 to 11.1.1.9.2. Before any Upgrade BIApps 111181 to 111191 load plan is executed, apply the workaround.
Workaround
Run the following command on the data warehouse schema:
UPDATE W_ETL_LOAD_DATES SET TARGET_TABLE_NAME = 'W_RCRTMNT_RQSTN_A' WHERE PACKAGE_NAME = 'PLP_PLP_RECRUITMENTREQUISITIONAGGREGATE_LOAD' AND TARGET_TABLE_NAME <> 'W_RCRTMNT_RQSTN_A'; COMMIT;
In Oracle BI Applications Release 11.1.1.9.2, the SDE_FUSION_RequisitionLinesCostFact_UPG mapping does not populate the CREATED_ON_DT column.
As a result, for Fusion Applications data sources, W_RQSTN_LINE_COST_F.BUYER_WID is set to 0 after executing SIL_RequisitionLinesCostFact_UPG, which affects the data upgrade for BUYER_WID. To populate BUYER_WID correctly, perform the workaround.
Workaround
In ODI Studio, display the Designer tab.
Navigate to Upgrade > 'SDE_FUSION_V1_11.1.1.8.1_to_11.1.1.9.1_Upgrade' > SDE_FUSION_RequisitionLinesCostFact_UPG > Interfaces, and open the following interface:
SDE_FUSION_RequisitionLinesCostFact_UPG.W_RQSTN_LINE_COST_FS_SQ_FSCMTOPMODELAM_PRCPORPUBLICDisplay the Quick Edit tab and expand Mappings section.
In 'Mappings' section at the bottom, add a column using+ green icon, as follows:
(1) Target Column Name: REQUISITIONDISTRIBUTIONCREATIONDATE (2) Data Type: TIMESTAMP (3) Length: 50 (4) Scale: 50 (5) Mapping Expression : A.RequisitionDistributionCreationDate (6) Execute On : Staging Area (7) Insert: keep it checked (8) Update: keep it checked
Save the Interface.
In the same Interfaces folder, open the following interface:
SDE_FUSION_RequisitionLinesCostFact_UPG.W_RQSTN_LINE_COST_FS
In 'Mappings' section at the bottom, locate CREATED_ON_DT(which will be grayed out, because it is not mapped), and update as follows:
- Change Mapping Expression value of CREATED_ON_DT to SQ_FSCMTOPMODELAM_PRCPORPUBLIC.RequisitionDistributionCreationDate <New mapping Expression of CREATED_ON_DT> SQ_FSCMTOPMODELAM_PRCPORPUBLIC.RequisitionDistributionCreationDate - Execute On: Staging Area - Insert : keep it checked - Update : keep it checked
Save the Interface.
Navigate to SDE_FUSION_V1_11.1.1.8.1_to_11.1.1.9.1_Upgrade > SDE_FUSION_RequisitionLinesCostFact_UPG > Packages > SDE_FUSION_RequisitionLinesCostFact_UPG > Scenarios, locate the following scenario, and regenerate the scenario using the right click menu to make the changes that you made take effect:
SDE_FUSION_V1_11_1_1_8_1_TO_11_1_1_9_1_UPGRADE_SDE_FUSION_REQUISITIONLINESCOSTFACT_UPG
If necessary, correct your data as follows:
If you upgraded your existing Release 8.1 Oracle Business Analytics Warehouse to Release 9.2 before applying the Workaround steps above, then you must correct the data in Oracle Business Analytics Warehouse. To do so:
Run the following UPDATE SQL in Oracle Business Analytics Warehouse:
update W_ETL_LOAD_DATES set committed=0
where TARGET_TABLE_NAME IN ('W_EXPENSE_CC_FS', ' W_RQSTN_LINE_COST_F');
COMMIT;
Run the next incremental load as usual.
This will populate only the W_RQSTN_LINE_COST_FS and W_RQSTN_LINE_COST_F tables in full load mode, while keeping other tables' records.
If you did not upgrade your existing Release 8.1 Oracle Business Analytics Warehouse to Release 9.2 before applying the Workaround steps above, then no further updates are required.
This issue applies to source versions Fusion 9 and 10.
When you upgrade form BI Apps 11.1.1.9.1 to 11.1.1.9.2, the incremental ETL fails with the following error:
ODI-1217: Session SDE_FUSION_V1_ADAPTOR_SDE_FUSION_EMPLOYEEDIMENSION (2489501) fails with return code 8000. ODI-1226: Step Run SDE_FUSION_EmployeeDimension.W_EMPLOYEE_DS fails after 1 attempt(s). ODI-1240: Flow Run SDE_FUSION_EmployeeDimension.W_EMPLOYEE_DS fails while performing a Loading operation. This flow loads target table W_EMPLOYEE_DS. ODI-1227: Task SrcSet0 (Loading) fails on the source ORACLE_BI connection fusion. Caused By: java.sql.SQLException: PreparedStatement execute failed java.io.IOException: execute query failed[nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 77031] Error occurs while calling remote service ADFService11G. Details: ADFException-3001: ViewObject "FscmTopModelAM.PrcPoPublicViewAM.PoAgentPVO" not found.
This issue arises because OBIA uses a new VO in 11.1.1.9.2 release called FscmTopModelAM.PrcPoPublicViewAM.PoAgentPVO. There is an existing AllBuyerPVO shared by OTBI and OBIA now. However, the changes made for OTBI cause a duplicates issue in the ETL run.
Workaround
In place of BUYER VO — FscmTopModelAM.PrcPoPublicViewAM.AllBuyerPVO a new VO - FscmTopModelAM.PrcPoPublicViewAM.PoAgentPVO is used in OBIA for SDE_FUSION_EmployeeDimension from 11.1.1.9.2 onward.
During ETL update, FscmTopModelAM.PrcPoPublicViewAM.AllBuyerPVO has been replaced with new VO - FscmTopModelAM.PrcPoPublicViewAM.PoAgentPVO in SDE_FUSION_EmployeeDimension.W_EMPLOYEE_DS_SQ_EMPLOYEES Of SDE_FUSION_EmployeeDimension.
As this is a new VO used from BI Apps 11.1.1.9.2, you need to apply the FA 9.2 PB1 Patch (having FUSIONAPPS_PT.INTERPNXT_LINUX.X64_141205.1123.S)
This information provides corrections and additions for documentation and Help for Oracle Business Intelligence Applications.
This applies to Oracle Business Intelligence Applications guides.
For Oracle BI Applications guides that are not included in the Release 11.1.1.9 documentation library, refer to the guides in the Release 11.1.1.8.1 documentation library at http://docs.oracle.com/cd/E51479_01/index.htm.
This issue applies to documentation errors in the Oracle Business Intelligence Applications Configuration guide.
In Section B.2.118 How to Configure Scorecard Target Before Running ETL, the file namefile_purch_scorecard_target.csv should be file_purch_target_fs.csv.
Ignore Chapter 6 Deploying the ODI Repository for Non-Oracle Source Databases. Deployment of the ODI Repository for Non-Oracle Databases is not supported.
Following has been added to the Oracle Business Intelligence Applications ETL guide:
Addition to Chapter 1 ETL Overview, Section 'About Multi-Source Environments'.
Note:
Applies to Business Intelligence Applications Consumer, version 11.1.1.7.1 and later.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.x.1' (Support Note Doc ID 1633996.1) on My Oracle Support.