| Oracle® Fusion Middleware Release Notes for Oracle Business Intelligence Applications 11g Release 1 (11.1.1.7.1) E38332-06 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Release Notes for Oracle Business Intelligence Applications 11g Release 1 (11.1.1.7.1) E38332-06 |
|
|
PDF · Mobi · ePub |
These release notes describe known issues and workarounds for Oracle Business Intelligence Applications Release 11.1.1.7.1, and contain the following sections:
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
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:
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.
This issue affects customers who want to install Oracle BI Applications in Simplified Chinese, Traditional Chinese, Japanese, or Korean Windows platforms. When running %BIEE_HOME%\bin\configapps.bat (for example, in C:\Oracle\Middleware\Oracle_BI1\bin>\configapps.bat) to extend the BI EE domain, the configuration wizard fails at step "Executing: opmnctl start coreappliction_obicss1" and "Executing: opmnctl start coreappliction_obis1".
Open a Command window/prompt.
Stop the two OPMN processes manually.
For example:
C:\Oracle\Middleware\instances\instance1\bin\opmnctl stopproc ias-component=coreapplication_obiccs1 C:\Oracle\Middleware\instances\instance1\bin\opmnctl stopproc ias-component=coreapplication_obis1
Go back to the configuration wizard and click the "Retry" button to continue.
During the Oracle BI Applications Configuration step of the installation process (launched using configApps.bat or configApps.sh), Help does not open for the screen "Specify Installation Location".
The Help topic is as follows:
Specify Installation Location (When Running the configApps.bat/sh File).
The following table describes the fields on this screen.
| Field | Description |
|---|---|
|
Middleware Home |
The path to the directory for an existing Oracle Middleware Home where Oracle BI EE has been installed. The value in this field is read-only. |
|
Oracle Home |
The Oracle home for BI, which is the location where Oracle BI EE and Oracle BI Applications files are installed. The value in this field is read-only. |
|
WebLogic Server Home |
The directory name for the WebLogic Server. The installer automatically creates this directory inside the Oracle Middleware home. The default name for this directory is "wlserver_" followed by the version number. For example, wlserver_10.3. The value in this field is read-only and is the host name you specified in the Middleware Home field. |
|
Domain Home |
The home directory for the domain associated with the Oracle Business Intelligence system. The value in this field is read-only. |
|
Instance Home |
The path to the Oracle Instance directory. The installer installs component configuration files and runtime processes in the Oracle Instance directory. Runtime components write to this directory only. The directory that you identify for the Oracle Instance can be located anywhere on your system, and does not need to be inside the Oracle Middleware home. The value in this field is read-only. |
|
Instance Name |
The name of the Oracle Business Intelligence instance. By default, the location is based on the value in the Instance Home field. This directory is commonly referred to as ORACLE_INSTANCE. The value in this field is read-only. |
If you are installing on a Microsoft Windows operating system:
Ensure that the directory paths are valid and do not contain double back slashes (\\).
For more information about the Middleware home and the Oracle home requirements, see "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide.
This section provides release notes on upgrading Oracle Business Intelligence Applications. There are no known Upgrade issues at present.
This section provides corrections and additions for documentation and Help for Oracle Business Intelligence Applications. It contains the following topics:
List of errors:
The Help topic that is displayed when you select the Performing System Setups link on the Tasks bar includes an invalid cross-reference:
To get started with System Setup, see Chapter 3 in Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications.
This Help topic should read:
To get started with System Setup, see Section 3.4 in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence Applications.
List of errors:
In Section 1.5.2 'How to add an index to an existing fact or dimension table', Step 11 should be replaced with the following three steps:
11. Display the Control tab.
12. Check the 'Defined in the Database' and 'Active' properties.
13. Save the changes.
This section provides general issues and workarounds for Oracle BI Applications. It contains the following topics:
Section 1.3.1, "CREATION_DATE Issue In INTEGRATION_ID For AP Holds Fact"
Section 1.3.2, "Source Systems Not Supported in this Release"
Section 1.3.4, "Configuring Price Analytics for use with E-Business Suite"
Section 1.3.7, "Learning Calendar Facts Should Not Be Combined With Learning Dimensions In HR AN"
Section 1.3.8, "No Truncate Before Running SDE Tasks In Time And Labor Folder"
Section 1.3.9, "FSM Task Missing For $$TRAVEL_MIN in Service Analytics"
Section 1.3.10, "Ignore PeopleSoft FSM Tasks in Non-PeopleSoft Implementation Projects"
Section 1.3.12, "E-Business Suite Error Creating Index in Full Load With Flexfields Implemented"
Section 1.3.13, "NLS: Repository and Catalog Strings Not Translated"
Section 1.3.16, "W_PRODUCT_XACT_A Is Not Truncated In Full Load"
Section 1.3.17, "PeopleSoft Tree Node Update Issue In Incremental Run"
Section 1.3.18, "Issue In GL Segment Dimension Translate Mapping for Project Chartfield"
Section 1.3.19, "Configuration of HR Security Person ID List (EBS) SQL In RPD"
Section 1.3.21, "JD Edwards UDC Values Not Loaded Into Domains After Domain ETL Run"
Section 1.3.22, "NLS Regional Settings Not Save After Logout/Login"
Section 1.3.23, "PeopleSoft Departments and Company Org Have Incorrect Name in Reports"
Section 1.3.24, "Manufacturing Analytics: Deploying Inventory Content Areas As Part Of Load Plan"
Section 1.3.25, "Market Basket Analysis Facts and Dimensions Not Supported"
Section 1.3.27, "Connection Pool Errors in NQSSERVER.log File"
Section 1.3.28, "Security Filters for Procurement User and Spend Planning Users"
Section 1.3.30, "Unit of Measure (UOM) Data Not Populated in Oracle Business Analytics Warehouse"
Section 1.3.32, "Offerings (SIA, CDM AND PIM) Are Not Enabled For Selection For Universal Adaptor"
Section 1.3.33, "Load Failure in AR Billing Distribution Initialbalance for PeopleSoft Adaptors"
Section 1.3.34, "W_PROJ_CLASSIFICATOIN_D is Always Truncated and Reloaded"
Section 1.3.35, "Supplementary Information About Deploying Object Security for Project Analytics"
In 11i AP Hold, the integration_id is using last_update_date when it should be using creation_date. This issue will cause the following:
- Add unwanted records into hold fact.
- Leave holds open even when they are released in OLTP.
Log in to the ODI Designer.
Open the adaptor folder: SDE_ORA11510_Adaptor.
Open the folder: SDE_ORA_APHoldsFact.
Open the Interface: SDE_ORA_APHoldsFact_W_AP_HOLDS_FS.
Go to the Quick-Edit tab and navigate to INTEGRATION_ID expression under the Mappings section.
Paste the following expression:
TO_CHAR(SQ_AP_HOLDS_ALL.INVOICE_ID)||'~'|| TO_CHAR(SQ_AP_HOLDS_ALL.LINE_LOCATION_ID)||'~'|| SQ_AP_HOLDS_ALL.HOLD_LOOKUP_CODE||'~'|| TO_CHAR(SQ_AP_HOLDS_ALL.HOLD_DATE,'YYYYMMDDHHMISS')||'~'|| TO_CHAR(SQ_AP_HOLDS_ALL.CREATION_DATE,'YYYYMMDDHHMISS')
Save and close the Interface.
Re-generate the scenario.
Oracle Business Intelligence Applications Release 11.1.1.7.1 and the product documentation may contain references to Oracle Fusion Applications. Oracle Fusion Applications is not a supported source system in this release of Oracle Business Intelligence Applications. Ignore any references to Oracle Fusion Applications in the product and in the documentation. 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.
Order and Quote Header Facts are not supported for the E-Business Suite Adaptor. To ensure that Price Analytics logical queries follow the right query path, you must follow the Workaround below to disable Logical Table Sources that use W_QUOTE_F (or) W_ORDER_F as a source in the BI metadata repository (that is, in the RPD file).
Using Oracle BI EE Administration Tool, edit the BI metadata repository (that is, the RPD file), and display the Business Model and Mapping pane.
Disable W_QUOTE_F, as follows:
Navigate to logical table Dim – Quote and double click logical table source Fact_W_QUOTE_F to display the Logical Table Source dialog.
Display the General tab.
Select the Disabled check box for this LTS.
Repeat steps a. to c. for LTS Fact_W_QUOTE_F in logical table Fact – CRM – Quote Item.
Disable W_ORDER_F, as follows:
Repeat Step 2 for LTS Fact_W_ORDER_F in logical table Dim – Order.
Repeat Step 2 for LTS Fact_W_ORDER_F in logical table Fact – CRM – Order Item.
Applicable Source Systems: Oracle EBS, All versions.
Business Issue: GL Balance Amount at fiscal year level may show 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 (whose ROW_WID's suffix is not 999), 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
Define a new logical column (Fiscal Date Key) with the expression below in Dim – Date Fiscal Calendar:
Dim_W_MCAL_DAY_D_Fiscal_Day.MCAL_CAL_WID * 100000000000.0 + cast(Evaluate( to_char(%1,'YYYYMMDD'),Dim_W_MCAL_DAY_D_Fiscal_Day.MCAL_DAY_DT) as INTEGER ) * 1000 + Dim_W_MCAL_DAY_D_Fiscal_Day.MCAL_PERIOD
Use this new column in the logical hierarchy level Day Detail Level of the logical dimension: Date – Fiscal Calendar.
Using Oracle BI EE Administration Tool, edit the BI metadata repository (that is, the RPD file).
Navigate to the logical Dimension: Dim – Date Fiscal Calendar.
Expand Sources and double click on LTS Dim_W_MCAL_DAY_D_Fiscal_Day.
Navigate to Column Mapping tab and click on New Column.
Name the new column as "Fiscal Date Key" and click OK.
In Column Mapping tab, click on Show unmapped columns and highlight the new column Fiscal Date key.
Click the Edit Expression button (so the Expression Builder window is open) and add the following expression in the expression field:
"Oracle Data Warehouse"."Catalog"."dbo"."Dim_W_MCAL_DAY_D_Fiscal_Day"."MCAL_CAL_WID" * 100000000000.0 + CAST ( EVALUATE('to_char(%1,''YYYYMMDD'')', "Oracle Data Warehouse"."Catalog"."dbo"."Dim_W_MCAL_DAY_D_Fiscal_Day"."MCAL_DAY_DT") AS INTEGER ) * 1000 + "Oracle Data Warehouse"."Catalog"."dbo"."Dim_W_MCAL_DAY_D_Fiscal_Day"."MCAL_PERIOD"
Click on OK to close the Expression Builder, and then click on OK to close Logical Table Source.
Navigate to the logical table again and double click the newly created column to open it.
Navigate to Levels tab and choose 'Fiscal Day Detail' as its logical level.
Navigate to Logical Dimension: Date – Fiscal Calendar and go to day detail level. The newly defined column should appear under it already (because in the previous step you have set its logical level).
Double click on Fiscal Day Detail to open it. In the Keys tab column, add a new key called Fiscal Date Key and map it to the newly create 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, click on OK.
Click on Save and do a Global Consistency Check.
Host the RPD and generate Answers.
In Functional Setup Manager, the Task 'How to setup Accounts Receivable Security for E-Business suite' is displayed erroneously in non-E-Business Suite Implementation Projects.
When using an Implementation Project for a non-E-Business Suite project, ignore the Task 'How to setup Accounts Receivable Security for E-Business suite'.
Learning Calendar Facts include Training Hours and Training Days. These two metrics are intended to be combined with the Absence and Leave Accrual Subject Area to query employee training hours or days for absence reporting. These two metrics can not be combined with Learning dimensions. Otherwise they will return no data. To view training hours by learning dimensions (for example, course name), you must use Delivered Training Hours in Enrollment Facts.
On an existing data warehouse, if a full load is required again, Oracle BI Applications enables you to reset Oracle Business Analytics Warehouse and prepare it again for full load. To do this, execute the 'EXECUTE RESET DATAWARESHOUSE SCENARIO'. When this is done, and a full ETL is started, the following tasks fail because of PK violations.
SDE_PSFT_PERSISTEDSTAGE_TIME_AND_LABOR_CALENDAR
SDE_PSFT_PERSISTEDSTAGE_TIME_AND_LABOR_TASKGROUP
SDE_PSFT_PERSISTEDSTAGE_TIME_AND_LABOR_PAYABLETIME
SDE_PSFT_PERSISTEDSTAGE_TIME_AND_LABOR_REPORTEDTIME
This happens because the Table Maintenance is set to Manual (single $) for the Time and Labor Persisted stage components and did not include the BEFORE maintenance task, which truncates the table. And because the tables are not truncated, when a full load is run, it fails with PK violations since the records already exists there.
Do not use RESET DATAWAREHOUSE feature in Oracle BI Applications if you intend to re-run a full load against an existing/populated schema. Instead, you must re-deploy the tables (drop and create) and then attempt a full ETL re-run.
The variable $$TRAVEL_MIN is not exposed in FSM and there is no task available to edit it. This variable is used to calculate Actual_Travel_Duration in Minute in Oracle Business Analytics Warehouse based on the actual duration and actual duration UOM entered in the Dispatch center for any field service task.
The default expression for this variable is:
CASE WHEN ACTUAL_TRAVEL_DURATION_UOM='YR' THEN 365*24*60 WHEN ACTUAL_TRAVEL_DURATION_UOM='QRT' THEN 122*24*60 WHEN ACTUAL_TRAVEL_DURATION_UOM='MTH' THEN 30*24*60 WHEN ACTUAL_TRAVEL_DURATION_UOM='WK' THEN 7*24*60 WHEN ACTUAL_TRAVEL_DURATION_UOM='DAY' THEN 24*60 WHEN ACTUAL_TRAVEL_DURATION_UOM='HR' THEN 60 WHEN ACTUAL_TRAVEL_DURATION_UOM='MIN' THEN 1 ELSE NULL END
If JTF_TASK_ASSIGNMENTS.ACTUAL_TRAVEL_DURATION_UOM has any value different to those listed in the above expression, then you must edit this variable in the ODI repository. For example if the duration UOM is 'Minute', then change this variable to:
CASE WHEN ACTUAL_TRAVEL_DURATION_UOM='YR' THEN 365*24*60 WHEN ACTUAL_TRAVEL_DURATION_UOM='QRT' THEN 122*24*60 WHEN ACTUAL_TRAVEL_DURATION_UOM='MTH' THEN 30*24*60 WHEN ACTUAL_TRAVEL_DURATION_UOM='WK' THEN 7*24*60 WHEN ACTUAL_TRAVEL_DURATION_UOM='DAY' THEN 24*60 WHEN ACTUAL_TRAVEL_DURATION_UOM='HR' THEN 60 WHEN ACTUAL_TRAVEL_DURATION_UOM='MIN' THEN 1 WHEN ACTUAL_TRAVEL_DURATION_UOM='Minute' THEN 1 ELSE NULL END
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
Some groups in LDIF are named differently to the same logical groups in JAZN. For example, the group that is specified as 'Manufacturing Cost Analyst' in LDIF (that is, specified in WebLogic Server Administration Console) is specified as OBIA_MANUFACTURING_COST_ANALYST in JAZN (that is, specified in Oracle Enterprise Manager Fusion Middleware Control). Therefore, if a user (for example, named MFG1) is created in WebLogic Server Administration Console and associated with 'Manufacturing Cost Analyst', then this user will not have the correct privileges.
Before you start, you can verify the Group names in WebLogic Server Administration Console:
Open Oracle WebLogic Server Administration Console at <hostname>:7001/console.
Navigate to the security Realms > myrealm.
Navigate to Users and Groups > Groups, and verify the following groups:
- Manufacturing Executive- Manufacturing Execution Analyst- Manufacturing Cost Analyst
Apply the workaround:
Open Oracle Enterprise Manager Fusion Middleware Control, for example, <hostname>:7001/em.
Navigate to Weblogic Domain > bifoundation_domain > Weblogic Domain > Security > Application Roles to display the Application Roles dialog.
Search for Manufacturing Analytics roles.
The group associated in the membership for OBIA_MANUFACTURING_COST_ANALYSIS_DUTY says OBIA_MANUFACTURING_COST_ANALYSIS_DUTY.
Change the group 'Manufacturing Cost Analyst', as follows:
Click Edit button from the toolbar at the top.
Click Delete to delete OBIA_MANUFACTURING_COST_ANALYSIS_DUTY from the Members list.
Click Add to display the Add Principal dialog.
Search for Manufacturing Cost Analyst, select this item, and click OK.
Repeat Steps 3 and 4 for:
OBIA_MANUFACTURING_EXECUTION_ANALYST (change to Manufacturing Execution Analyst).
OBIA_MANUFACTURING_EXECUTIVE_ANALYST (change to Manufacturing Executive).
The issue affects Oracle E-Business Suite users implementing Flexfields with the bulk mode option enabled. The error occurs due to violation of constraint: W_FLEX_SQL_G_U1 on table W_FLEX_SQL_G, which is due to duplicate keys or W_FLEX_COLUMN_G_U1 on table W_FLEX_COLUMN_G due to duplicate keys.
Error step in load plan:
3 SDE General Flexfield ->Finalize Flexfield ->EXEC_TABLE_MAINT_PROC
Do one of the following:
Delete the duplicate and proceed with the load plan execution.
Script:
DELETE FROM W_FLEX_SQL_G A WHERE
a.rowid > ANY ( SELECT B.rowid FROM W_FLEX_SQL_G B WHERE
A.DOMAIN_CODE = B.DOMAIN_CODE AND
A.DOMAIN_MEMBER_CODE=B.DOMAIN_MEMBER_CODE AND
A.DATASOURCE_NUM_ID = B.DATASOURCE_NUM_ID
) ;
commit;
DELETE FROM W_FLEX_COLUMN_G A WHERE
a.rowid > ANY ( SELECT B.rowid FROM W_FLEX_COLUMN_G B WHERE
A.APPLICATION_ID =B.APPLICATION_ID AND
A.FLEXFIELD_TYPE=B.FLEXFIELD_TYPE AND
A.FLEXFIELD_CODE=B.FLEXFIELD_CODE AND
A.CONTEXT_CODE=B.CONTEXT_CODE AND
A.COLUMN_CODE=B.COLUMN_CODE AND
A.DATASOURCE_NUM_ID=B.DATASOURCE_NUM_ID
) ;
commit;
Before starting the load plan, disable bulk mode for steps 3 SDE General
Flexfield and PRE-SDE:
- Go to step 3 SDE General Flexfield in load plan and mark ETL_BULK_MODE to N.
- Go to step 3 PRE-SDE General -> PRE-SDE in load plan and mark
ETL_BULK_MODE to N.
If you are using Oracle BI Applications reports and dashboards in non-English languages, then some repository and catalog strings are not translated.
Use Administration Tool and Catalog Manager in Oracle BI EE to translate repository and catalog strings.
The 'Inventory - Inventory Turn' Subject Areas available in the Supply Chain and Order Management Analytics and Manufacturing Analytics modules of Oracle BI Applications 11.1.1.7.1 contains untranslated strings. This impacts queries generated using the 'Inventory - Inventory Turn' Subject Areas, where the dimension attributes and fact metrics will be hard coded and not translated to German, French and other languages, unlike the rest of the Subject Areas.
For the initialization blocks <Current Gregorian and Enterprise Values> and <Previous Gregorian and Enterprise Value> to work correctly, the following Workaround is required in the BI metadata repository (that is, the RPD file).
In Oracle BI EE Administration Tool, open repository initialization block <Current Gregorian and Enterprise Values>.
Click on Edit Data Source, and a window pops up. On Line 3 of the SQL, change CURRENT_QTR_OBIA to CURRENT_QUARTER_OBIA. (This is required because of a variable name change in RPD. CURRENT_QTR_OBIA no longer exists; instead we have CURRENT_QUARTER_OBIA.)
Keep the pop up window open.
The next change is needed because the number and order of variables populated by the SQL must match the number and order of variables defined in the Variable Target list of the initialization block.
Insert six new lines.
Between Lines 5 (the CASE WHEN statement for CURRENT_WEEK_OBIA) and 6 (the CASE WHEN statement for CURRENT_ENTERPRISE_YEAR_OBIA) of the existing SQL, using the same CASE WHEN structure as of Line 5, insert six new lines for the following six variables: CURRENT_JULIAN_YEAR_OBIA, CURRENT_JULIAN_QTR_OBIA, CURRENT_JULIAN_MONTH_OBIA, CURRENT_TRIMESTER_OBIA, CURRENT_CALENDAR_YEAR_OBIA, CURRENT_CALENDAR_QUARTER_OBIA.
Note that the order of these newly inserted variables is important. Once done, click on Ok to close the pop-up window, and click on Ok again to close the initialization block.
Open the repository initialization block <Previous Gregorian and Enterprise Values>.
Click on Edit Data Source, and a window pops up.
In the SQL, change all _OTBI suffixes to _OBIA.
For example, PREVIOUS_YEAR_OTBI should be PREVIOUS_YEAR_OBIA.
Click on Ok to close the pop-up window, and click on Ok again to close the initialization block.
Save the RPD.
Two PLP Load Plan steps INVTRX_FG and INVBAL_FG have $ instead of $$ in the name so no table maintenance steps are included to truncate the table W_PRODUCT_XACT_A.
Note: Load Plan Generator (LPG) uses the naming convention of the Step Property Name to determine whether table maintenance should be turned off or on. $means LPG will not add table maintenance steps into the corresponding step hierarchy section of the generated load plan, while $$ means LPG will add table maintenance steps.
In ODI, in the Designer tab, expand the Load Plans and Scenarios section.
Go to BIAPPS Load Plan->Load Plan System Components->PLP->2 PLP Fact Group.
Display the Steps tab.
Expand root_step >Parallel.
Highlight ${3 PLP Fact INVTRX_FG}.
In the properties, change the name to $${3 PLP Fact INVTRX_FG}.
Highlight ${3 PLP Fact INVBAL_FG}.
In the properties, change the name to $${3 PLP Fact INVBAL_FG}.
Regenerate Load Plans.
In Incremental run, Department and Customer Hierarchy in PeopleSoft are not able to update a node/leaf position change.
Note: Deletion or Addition of a node/leaf is properly updated in Oracle Business Analytics Warehouse.
In ODI Designer, navigate > Models > Oracle BI Applications > Oracle BI Applications > Dimension Hierarchy > W_INT_ORG_DH > Columns.
Open Following columns one by one:
RG_TOP_NUM, BASE_ORG_NUM, ORG_HIER1_NUM, ORG_HIER2_NUM, ORG_HIER3_NUM, ORG_HIER4_NUM, ORG_HIER5_NUM, ORG_HIER6_NUM, ORG_HIER7_NUM, ORG_HIER8_NUM, ORG_HIER9_NUM, ORG_HIER10_NUM, ORG_HIER11_NUM, ORG_HIER12_NUM, ORG_HIER13_NUM
For each of above columns, navigate to Flexfields, remove the default check for 'OBI Change Indicator' property, and set the value as Y.
Navigate to ODI Designer > Projects > BI Apps Project > Mappings > SILOS > SIL_InternalOrganizationHierarchy > Packages > SIL_InternalOrganizationHierarchy > Scenarios.
Right click on SILOS_SIL_INTERNALORGANIZATIONHIERARCHY.
Click Regenerate, then click OK.
At the 'Scenario Variables', click OK.
The GL segment dimension translate mapping for Project Chartfield and Activity Chartfield has issues with respect to the tables used.
In ODI Designer, open the appropriate PSFT Adaptor folder (SDE_PSFT_90_Adaptor or SDE_PSFT_91_Adaptor) under BIApps Project > Mappings > SDE_PSFT_90_ADAPTOR/SDE_PSFT_91_ADAPTOR.
Open the folder: SDE_PSFT_GLSegmentDimension_Translate_Project.
Open the interface:SDE_PSFT_GLSegmentDimension_Translate_Project.W_GL_SEGMENT_DS_TL_SQ_PROJECT_ID.
Navigate to the Quick-Edit tab and in the Select Dataset: select "Base".
In the sources section, select the existing Source (PROJ_LANG) and delete.
Click on the Add sources (The Green Plus Symbol) which will open the Source wizard editor. Navigate to the Peoplesoft 9.0> Peoplesoft 9.0 FNSCM > Peoplesoft 9.0 FNSCM > FPC-Projects / Peoplesoft 9.1> Peoplesoft 9.1 FNSCM > Peoplesoft 9.1 FNSCM > FPC-Projects and select the data store PROJECT.
Navigate to the "Mapping" section.
Use the expression for the target column names as given below by opening the expression editor for each target column.
BUSINESS_UNIT : PROJECT.BUSINESS_UNIT
DESCR : PROJECT.DESCR
PROJECT_ID : PROJECT.PROJECT_ID
CHANGED_ON_DT :
RUN_REPLICATED_TRANSACTIONAL('#IS_SDS_DEPLOYED',SESSSTARTTIME,PROJECT.CDC$_SRC
_LAST_UPDATE_DATE)
DELETE_FLG: RUN_REPLICATED_TRANSACTIONAL('#IS_SDS_DEPLOYED','N',CASE WHEN
PROJECT.CDC$_DML_CODE = 'D' THEN 'Y' ELSE 'N' END)
In the Filter Section , click on the add filter and paste the following expression:
RUN_REPLICATED_TRANSACTIONAL('#IS_SDS_DEPLOYED',
1 = 1,
PROJECT.CDC$_SRC_LAST_UPDATE_DATE > TO_DATE_VAR('#LAST_EXTRACT_DATE'))
Select the MLS data set from Select Dataset in the Quick Edit tab and select the MLS dataset from the drop down.
Delete the existing Sources ('GL_ACCOUNT_LANG' and the Alias 'SQ_LANG_MAX_EFFDT'). Click on Add sources.
Navigate to the Peoplesoft 9.0> Peoplesoft 9.0 FNSCM > Peoplesoft 9.0 FNSCM > FPC-Projects /Peoplesoft 9.1> Peoplesoft 9.1 FNSCM > Peoplesoft 9.1 FNSCM > FPC-Projects and select the data store PROJECT_LANG.
In the filter section click on the add filter and paste the following expression.
RUN_REPLICATED_TRANSACTIONAL('#IS_SDS_DEPLOYED',
1 = 1,
PROJECT_LANG.CDC$_SRC_LAST_UPDATE_DATE > TO_DATE_VAR('#LAST_EXTRACT_DATE'))
Navigate to the "Mapping" section. Use the expression for the target column names as given below by opening the expression editor for each target column.
BUSINESS_UNIT : PROJECT_LANG.BUSINESS_UNIT
DESCR : PROJECT_LANG.DESCR
PROJECT_ID : PROJECT_LANG.PROJECT_ID
LANGUAGE_CODE : PROJECT_LANG.LANGUAGE_CD
CHANGED_ON_DT :
RUN_REPLICATED_TRANSACTIONAL('#IS_SDS_DEPLOYED',SESSSTARTTIME,PROJECT_LANG.CDC
$_SRC_LAST_UPDATE_DATE)
DELETE_FLG :RUN_REPLICATED_TRANSACTIONAL('#IS_SDS_DEPLOYED','N',CASE WHEN
PROJECT_LANG.CDC$_DML_CODE = 'D' THEN 'Y' ELSE 'N' END)
Save and close the interface.
Re-generate the scenario.
Open the folder:SDE_PSFT_GLSegmentDimension_Translate_Activity_ID.
Open the Interface : SDE_PSFT_GLSegmentDimension_Translate_Activity ID.W_GL_SEGMENT_DS_TL_SQ_ACTIVITY_ID.
Go to Quick-Edit tab and in the Select Dataset drop down select 'Manage Datasets' which will open an Dataset Configuration Editor.
Click on the Add New Dataset. In the Dataset Name column, change the name to 'MLS' and the 'Default' name to 'Base'. Close the Dataset Configuration.
Select the MLS data set in Select Dataset dropdown. In the Sources Section click on the Add Sources, which will open the Source wizard editor.
Navigate to the Peoplesoft 9.0> Peoplesoft 9.0 FNSCM > Peoplesoft 9.0 FNSCM > FPC-Projects /Peoplesoft 9.1> Peoplesoft 9.1 FNSCM > Peoplesoft 9.1 FNSCM > FPC-Projects and select the data store PROJ_ACTIVTY_LG.
In the filters section , click on the add filter and paste the following expression:
RUN_REPLICATED_TRANSACTIONAL('#IS_SDS_DEPLOYED',1 = 1,
PROJ_ACTIVTY_LG.CDC$_SRC_LAST_UPDATE_DATE >
TO_DATE_VAR('#LAST_EXTRACT_DATE'))
Navigate to the "Mapping" section. Use the expression for the target column names as given below by opening the expression editor for each target column.
PROJECT_ID : PROJ_ACTIVTY_LG.PROJECT_ID
ACTIVITY_ID : PROJ_ACTIVTY_LG.ACTIVITY_ID
DESCR : PROJ_ACTIVTY_LG.DESCR
LANGUAGE_CODE : PROJ_ACTIVTY_LG.LANGUAGE_CD
CHANGED_ON_DT:RUN_REPLICATED_TRANSACTIONAL('#IS_SDS_DEPLOYED',SESSSTARTTIME,PR
OJ_ACTIVTY_LG.CDC$_SRC_LAST_UPDATE_DATE)
DELETE_FLG:RUN_REPLICATED_TRANSACTIONAL('#IS_SDS_DEPLOYED','N',CASE WHEN
PROJ_ACTIVTY_LG.CDC$_DML_CODE = 'D' THEN 'Y' ELSE 'N' END)
Save and close the interface.
Re-generate the scenario.
This issue applies to customers using Oracle HR Analytics with Oracle E-Business Suite. The initialization block HR Security Person ID List (EBS) as installed in this release does not function correctly. To correct this issue you must make two changes, one in ODI Designer, and one in the BI metadata repository (that is, the RPD file), as described in the Workaround below.
ODI change:
Connect to your ODI repository.
Under the Designer tab, navigate to the Mappings folder, locate the EBS adaptor folder that corresponds to the Oracle database version that you are using (such as SDE_ORA11510_Adaptor, SDE_ORAR1211_Adaptor, and so on) and then locate the task folder named SDE_ORA_PositionDimension.
In the SDE_ORA_PositionDimension task folder, open the Interface SDE_ORA_PositionDimension.W_POSITION_DS, click on the Mapping tab, and change the mapping expression of the column EMP_LOGIN to COALESCE(TO_CHAR(SQ_BC_POSITIONDIMENSION.EMP_ID),'#ETL_UNSPEC_STR').
Save the interface and close it.
Within the same task folder SDE_ORA_PositionDimension, navigate to Packages and then Scenarios, right-click on the existing scenario, and in the drill-down menu, choose Regenerate.
When the pop-up window is displayed, click OK without making any further changes.
As part of the regeneration process, another pop-up window will be displayed asking you to select the Startup Parameters.
Choose Use All from the drill-down list, and then click OK. The pop-up window will close and the regeneration process will conclude.
BI metadata repository change:
Using Oracle BI Administration tool, edit the BI metadata repository (that is, the RPD file), open the session initialization block named HR Security Person ID List (EBS), and then click Edit Data Source.
This action causes a pop-up window to open that shows the SQL for the initialization block.
Make the following changes in the pop-up window:
Change the SQL to:
SELECT 'HR_SEC_PERSON_ID____EBS', TO_CHAR(USR.EMPLOYEE_ID) AS PERSON_ID FROM FND_USER USR WHERE USR.USER_NAME = UPPER(':USER') AND USR.EMPLOYEE_ID IS NOT NULL
Change the Connection Pool to "Oracle EBS OLTP"."Oracle EBS OLTP InitBlocks Connection Pool".
Click OK to close the pop-up window, and then click OK again to close the initialization block.
Save the repository.
This issue applies to customers that use E-Business Suite with Bill of Material facts in the Supply Chain Analytics area, and need to populate Oracle Business Analytics Warehouse from multiple E-Business Suite instances (for example, 11i10 and R12.1.3).
During a data extraction from multiple sources, the BOM explosion process might create records with duplicate keys, for example:
Step SDE_ORA_BOMITEMFACT_HEADER in Multi-source returns error ORA-01427: single-row subquery returns more than one row
To prevent this issue, apply the Workaround below.
In ODI Designer, navigate to: BI Apps Project -> Mappings -> SDE_ORAxxx_Adaptor >SDE_ORA_BOMItemFact_Explosion > Interfaces.
Open the SDE_ORA_BOM_Explosion.OPI_OBIA_W_BOM_HEADER_DS_SQ_W_BOM_HEADER_DS interface.
Add a new filter, either from the Mapping or Quick-Edit tab.
Set the Implementation for the new filter to:
W_BOM_HEADER_DS.DATASOURCE_NUM_ID=#DATASOURCE_NUM_ID
Save and close the interface.
Regenerate the associated scenario.
This issue applies to customers with JDE Financial and Supply Chain and Order Management Analytics Adaptor before running domain ETL for the first time.
Within the JDE Adaptor, there are several Load Plan steps which load values from the User Defined Codes (F0005) table into corresponding Domains. Many of these steps override the values for two variables, JDE_UDC_RT and JDE_UDC_SY, to determine which UDC values will be retrieved. To retrieve the appropriate values, these variables must be defined correctly. The variables of the following Load Plan steps did not carry the proper values in the generally available version of PS1 ODI repository:
SDE_JDE_DomainGeneral_UDC GENDER SDE_JDE_DomainGeneral_UDC INV_TRANSACTION_TYPES SDE_JDE_DomainGeneral_UDC INV_TRANSACTION_SOURCE_TYPES SDE_JDE_DomainGeneral_UDC BOM_CATEGORY SDE_JDE_DomainGeneral_UDC DIVISION_TYPE SDE_JDE_DomainGeneral_UDC SIC_CODE SDE_JDE_DomainGeneral_UDC HAZARD_MTL
As a result, the corresponding domains are not populated from the JDE UDC table.
In Oracle Data Integrator (ODI), connect to your ODI repository and open the Designer Navigator.
Open the Load Plans and Scenarios area and navigate to BIAPPS Load Plan -> Load Plan Dev Components -> SDE -> JDE_9_x.
Open the "3 SDE General Domain JDE_9_x" Load Plan component and select the "Steps" tab.
Click the "Expand All" button to see all nested steps.
Open the Property Inspector panel and highlight a Load Plan step to view and change the associated variable values.
For each of the following steps, ensure that the JDE_UDC_SY and JDE_UDC_RT variables are overridden to the listed values:
SDE_JDE_DomainGeneral_UDC GENDER (JDE_UDC_S=01, JDE_UDC_RT=GD) SDE_JDE_DomainGeneral_UDC INV_TRANSACTION_TYPES (JDE_UDC_S=00, JDE_UDC_RT=DT) SDE_JDE_DomainGeneral_UDC INV_TRANSACTION_SOURCE_TYPES (JDE_UDC_S=00,JDE_UDC_RT=DT) SDE_JDE_DomainGeneral_UDC BOM_CATEGORY (JDE_UDC_S=41, JDE_UDC_RT=I) SDE_JDE_DomainGeneral_UDC DIVISION_TYPE (JDE_UDC_S=00, JDE_UDC_RT=MC) SDE_JDE_DomainGeneral_UDC SIC_CODE (JDE_UDC_S=00, JDE_UDC_RT=SC) SDE_JDE_DomainGeneral_UDC HAZARD_MTL (JDE_UDC_S=49, JDE_UDC_RT=BX)
Save your changes, and recreate/regenerate any Load Plans that load the Domains.
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.
This issue applies when a tree node for Department hierarchy or Company hierarchy has the same name as an existing department ID or Company Org ID.
To avoid this issue, you should not use same names for nodes of department and company org summer tree as an existing department ID or Company Org ID.
This issue affects customers who are not deploying Supply Chain and Order Management Analytics but only deploying Manufacturing Analytics and want to deploy the Inventory content areas as part of the load plan.
The Manufacturing Analytics license in 11.1.1.7.1 allows users to also deploy Inventory content areas. These content areas are not configured in Oracle BI Applications Configuration Manager for Manufacturing Analytics offering. These are only configured as part of Supply Chain and Order Management Analytics.
As a result, the Inventory content area is excluded when a Manufacturing load plan is generated.
To include the above Inventory related fact groups as part of the Manufacturing load plan, follow the steps outlined in the Tech Note "Oracle BI Applications Manufacturing Analytics – How to configure Inventory related fact groups?" [ID 1546632.1].
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.
The list below shows FSM Tasks that are missing a Help icon, and contains the Help topic where appropriate.
List of FSM Tasks with missing Help icons:
Configure Data Load Parameters for Master Organization
The missing Help icon should display the following information:
In Oracle 11i applications, products are defined in a Master Organization and then copied into the other Inventory Organizations for transactions. The Product dimension Extract mapping 'SDE_ORA_ProductDimension_Derive' has been enabled for configuration of this Master Organization based on the configuration in the OLTP. By default, the organization ID (that is set by the $$MASTER_ORG parameter) is set to 204. This organization ID 204 needs to be changed based on the individual implementation of OLTP in your deployment. This ETL implementation supports the best practice prescribed by Oracle for the creation of Single Master Organization for defining the Product master. This ETL implementation does not support the multiple master Organizations if the same product is defined in multiple master organizations. You can assign Multiple MASTER Organizations also under the same parameter by providing a comma-separated string of Organization codes (for example, '204','458').
How to configure C_State_prov
The missing Help icon should display the following information:
To configure conformed STATE_PROV, you use Externally Conformed Domains in Oracle BI Applications Configuration Manager. For more information about how to configure externally Conformed domains, see Section 4.4.8, "How to Configure Externally Conformed Domains".
Overview of Budgetary Control in Financial Analytics
To obtain this topic, see Appendix B in Oracle Fusion Middleware Configuration Guide for Oracle BI Applications.
The Help topics are also available in the Help system for Oracle BI Applications Configuration Manager/FSM (locatable using Search or Index facilities) and in Appendix B in Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications.
The Oracle BI Applications repository contains initialization blocks for source systems that are not supported in this release. In the NQSSERVER.log file for the Oracle BI Server, you might see entries such as the following:
Skipping execution of Initialization Block: '<Name of Initialization Block>'due to blacklisted Connection Pool:'"Oracle BI Application Configuration"."Oracle BI Application Configuration InitBlocks Connection Pool.
No workaround is required. Disregard these entries in the log file.
Due to a limitation in Procurement and Spend Analytics, dashboard users might experience security issues if the user accounts that they use have been granted both Procurement roles and Spend Planning roles.
Depending on how roles are granted, users might experience one or more of the following issues:
Users can access Procurement BU and Requisition BU dimension data without any filter applied.
Users are not allowed to access Spend Planning-related Subject Areas, such as:
- Spend Planning - Common
- Spend Planning - GL - HR Measures
- Spend Planning - GL Balances
- Spend Planning - Historical Spend
- Spend Planning - Planning
- Spend Planning - Purchasing
In this scenario, users have the following Procurement roles but do not have any Spend Planning roles:
- OBIA_PROCUREMENT_AGENT_ANALYSIS_ROLE,
- OBIA_PROCUREMENT_MANAGERIAL_ANALYSIS_ROLE,
- OBIA_CATEGORY_MANAGER_ANALYSIS_ROLE,
- OBIA_CONTRACT_ADMINISTRATOR_ANALYSIS_DUTY
- And OTBI analysis roles.
Users are able to access the filtered Procurement BU and Requisition BU business unit dimension data according to the security setup for Spend Planning. The Spend Planning related data are filtered by Procurement/Requisition Business Unit security filters.
Users are not allowed to access Procurement-related Subject Areas, such as:
- Employee Expenses - Credit Card
- Employee Expenses - Overview
- Employee Expenses - and so on.
- Procurement and Spend - Change Orders
- Procurement and Spend - Invoice Lines
- Procurement and Spend - Procure to Pay
- Procurement and Spend - and so on.
- Sourcing - Award
- Sourcing - Negotiation
- Sourcing - Overview
- Sourcing - and so on.
- Supplier Performance - Supplier AP Transactions
- Supplier Performance - Supplier Performance
In this scenario, users have the following Spend Planning roles but do not have Procurement Roles:
- OBIA_SPEND_PLANNING_LINE_OF_BUSINESS_ANALYSIS_DUTY,
- OBIA_SPEND_PLANNING_PROCUREMENT_ANALYSIS_DUTY
Users can access Subject Areas for both Procurement and Spend Planning. However, the Procurement BU and Requisition BU dimensions are filtered by the security setup for Spend Planning. The filters are not only applied to Spend Planning data, but also applied to Procurement Data. As a result, users might not have full access to some or all of the data in Procurement Subject Areas. For instance, if users are granted Procurement roles but no Planning roles, then they might be able to see the entire list of Procurement BU and Requisition BU in BU dimensions. However, if users are granted both Procurement roles and Spend Planning roles, then they will only be able to access BU assigned to them for Spend Planning. However, in both situations the facts are secured in the same way.
In this scenario, users have some/all Procurement Roles as well as Spend Planning roles.
To avoid these issues, Oracle recommends that you avoid granting Procurement roles and Spend Planning roles to the same users. You should create user accounts with Procurement roles to access Procurement Subject Areas, and create separate user accounts with Spend Planning roles to access Spend Planning Subject Areas.
This issue affects OLTP PeopleSoft 9.0 and 9.1 adapters. The scenario SDE_PSFT_DOMAINGENERAL_APINVOICEAPPROVALSTATUS fails due to index violation. The error refers to the W_DOMAIN_MEMBER_GS_U1 index being violated.
Note: The following workaround is for the PeopleSoft 90 implementation. If you are implementing PeopleSoft, then repeat the same steps in the SDE_PSFT91_Adaptor Folder.
In Oracle Data Integrator Designer, connect to the ODI repository.
Navigate to the SDE_PSFT90_Adaptor folder, and expand the SDE_PSFT_DOMAINGENERAL_APINVOICEAPPROVALSTATUS folder.
Expand the interface folder and open the temp interface 'SDE_PSFT_DomainGeneral_APInvoiceApprovalStatus_W_DOMAIN_MEMBER_GS_SQ_BC'.
Navigate to the 'Quick edit tab. Two datasets are displayed.
In the dataset DS1, add a column called as LANGUAGE (varchar2(80)).
Map it to B.LANGUAGE_CD, then select Execute On as Staging.
Select dataset DS2.
Map the LANGUAGE column to B.LANGUAGE_CD, then select Execute On as Staging.
Save your changes.
Open the Main interface 'SDE_PSFT_DomainGeneral_APInvoiceApprovalStatus_W_DOMAIN_MEMBER_GS'.
Navigate to the 'Quick edit tab.
Edit the expression for the target column LANGUAGE_CODE, and specify the following text:
DOMAIN_MEMBER_MAP( 'LANGUAGE', SQ_PSXLATITIM.LANGUAGE, #DATASOURCE_NUM_ID, 'W_LANGUAGE' )
Save the changes made to the Main interface.
Expand the scenarios and locate the scenario.
Right click on the scenario and choose regenerate.
Click 'OK' on the 'regenerate scenario as well as the pop-up Scenario variables dialog that is displayed.
Unit of Measure (UOM) data is not populated in Oracle Business Analytics Warehouse after running domains ETL and performing UOM mappings.
Run the Domain ETL.
Create the W_UOM domain members based on the UOM domain.
Set the Prune Days variable to a number that is large enough to extract all records from the OLTP.
Run the regular ETL (note that only the domain tasks will run in incremental mode, all other tasks will run in full mode so are not affected by Prune Days).
Re-set the Prune Days variable back to the actual number.
Some tasks for Oracle E-Business Suite fail if an earlier Load Plan was run but aborted before completion. If you have deployed the Human Resources Analytics module, the following steps need to be implemented.
In ODI Designer, navigate to the Design tab, and click on Load Plan and Scenarios.
Expand the 'BIAPPS Load Plan - Load Plan Dev Components - SDE' folder.
Choose your E-Business Suite release, and then find and edit the level 3 component for "3 SDE PS TLB_RPTD_TIME_PS EBS_{Release Number}".
Navigate to the 'Steps' subtab and select the root node W_ORA_TLB_RPTD_DTL_PS.
Click the '+' icon.
Choose "Run Scenario Step".
In the pop-up dialog enter the values:
Scenario Name: EXEC_TABLE_MAINT_PROC Version: -1
Step Name: EXEC_TABLE_MAINT_PROC
After the screen refreshes, select the newly added Scenario Step and using the Up arrow icon, move the new step to immediately above the existing step: SDE_ORA_PERSISTEDSTAGE_TIMECARDENGINE_REPORTEDTIME.
It should look like this:
W_ORA_TLB_RPTD_DTL_PS EXEC_TABLE_MAINT_PROC <--- newly added (Restart from failed step) SDE_ORA_PERSISTEDSTAGE_TIMECARDENGINE_REPORTEDTIME EXEC_TABLE_MAINT_PROC ...
Ensure you have selected the newly added step.
In the Property inspector, Scenario Variables, (Overwrite) the values:
BIAPPS.DDL_TABLE_LIST: W_ORA_TLB_RPTD_DTL_PS
BIAPPS.DDL_RUN_MDOE: BEFORE
Save and Close the load plan component.
In ODI Designer, navigate to the Design tab, and click on Load Plan and Scenarios.
Expand the 'BIAPPS Load Plan - Load Plan Dev Components - SDE' folder.
Choose your E-Business Suite release, and then find and edit the level 3 component for "3 SDE PS TLB_PRCSD_TIME_PS EBS_{Release Number}".
Navigate to the 'Steps' subtab and select the root node W_ORA_TLB_DEPSIT_TRNS_PS.
Click the '+' icon.
Choose "Run Scenario Step".
In the pop-up dialog enter the values:
Scenario Name: EXEC_TABLE_MAINT_PROC Version: -1
Step Name: EXEC_TABLE_MAINT_PROC
After the screen refreshes, select the newly added Scenario Step and using the Up arrow icon, move the new step to immediately above the existing step: SDE_ORA_PERSISTEDSTAGE_TIMECARDENGINE_DEPOSIT_TRANSACTIONS.
It should look like this:
W_ORA_TLB_DEPSIT_TRNS_PS EXEC_TABLE_MAINT_PROC <--- newly added (Restart from failed step) SDE_ORA_PERSISTEDSTAGE_TIMECARDENGINE_DEPOSIT_TRANSACTIONS EXEC_TABLE_MAINT_PROC ...
Ensure you have selected the newly added step.
In the Property inspector, Scenario Variables, (Overwrite) the values:
BIAPPS.DDL_TABLE_LIST: W_ORA_TLB_DEPSIT_TRNS_PS
BIAPPS.DDL_RUN_MDOE: BEFORE
Save the load plan component.
Navigate to the 'Steps' subtab and select the root node W_ORA_TLB_RETRVL_TRNS_PS.
Click the '+' icon.
Choose "Run Scenario Step".
In the pop-up dialog enter the values:
Scenario Name: EXEC_TABLE_MAINT_PROC Version: -1
Step Name: EXEC_TABLE_MAINT_PROC
After the screen refreshes, select the newly added Scenario Step and using the Up arrow icon, move the new step to immediately above the existing step: SDE_ORA_PERSISTEDSTAGE_TIMECARDENGINE_RETRIEVAL_TRANSACTIONS
It should look like this:
W_ORA_TLB_RETRVL_TRNS_PS EXEC_TABLE_MAINT_PROC <--- newly added (Restart from failed step) SDE_ORA_PERSISTEDSTAGE_TIMECARDENGINE_RETRIEVAL_TRANSACTIONS EXEC_TABLE_MAINT_PROC ...
Ensure you have selected the newly added step.
In the Property inspector, Scenario Variables, (Overwrite) the values:
BIAPPS.DDL_TABLE_LIST: W_ORA_TLB_RETRVL_TRNS_PS
BIAPPS.DDL_RUN_MDOE: BEFORE
Save the load plan component.
Generate (or if necessary, re-generate) the Load Plan.
In Oracle BI Applications Configuration Manager, users will not find the fact groups for selection for Offerings (Student Information Analytics, Customer Data Management Analytics and Product Information Management Analytics) listed under Universal adapter as a source.
Use the insert statements below to enable these offerings for Universal adaptor.
Insert Into C_Bia_Offering_Ds_Type_Rel (Offering_Key,Ds_Type_Key,Created_By,Creation_Date,Last_Updated_By,Last_Update
_Date) Values ('SI_AN_OFRNG','UNIVERSAL','USER_CUSTOMIZED',Systimestamp,'USER_CUSTOMIZED',Systimestamp);
Insert Into C_Bia_Offering_Ds_Type_Rel
(Offering_Key,Ds_Type_Key,Created_By,Creation_Date,Last_Updated_By,Last_Update
_Date) Values ('CDM_AN_OFRNG','UNIVERSAL','USER_CUSTOMIZED',Systimestamp,'USER_CUSTOMIZED',Systimestamp);
Insert Into C_Bia_Offering_Ds_Type_Rel
(Offering_Key,Ds_Type_Key,Created_By,Creation_Date,Last_Updated_By,Last_Update
_Date) Values ('PIM_AN_OFRNG','UNIVERSAL','USER_CUSTOMIZED',systimestamp,'USER_CUSTOMIZED',Systimestamp);
This applies to PeopleSoft adaptors SDE_PSFT_90_Adaptor and SDE_PSFT_91_Adaptor.
The interface SDE_PSFT_ARTransactionFact_BillingDistribution_InitialBalance.W_AR_XACT_FS has column PLANNING_DT populated with the SQ_LKP_RESOLUTION.NATURAL_SEGMENT_ID value, rather than the correct value 'Null'. This error causes the following issues:
During full load, it will fail the interface SDE_PSFT_ARTransactionFact_BillingDistribution_InitialBalance.W_AR_XACT_FS.
Initial Balance records will not be loaded.
In ODI Designer, open the adaptor folder: SDE_PSFT_<Version>_Adaptor.
For example, for PeopleSoft V9.0, open the folder SDE_PSFT_90_Adaptor.
In the SDE_PSFT_<Version>_Adaptor folder, open the sub-folder SDE_PSFT_ARTransactionFact_BillingDistribution_InitialBalance.
Open the Interface: SDE_PSFT_ARTransactionFact_BillingDistribution_InitialBalance.W_AR_XACT_FS.
Go to the Quick-Edit tab and navigate to PLANNING_DT target column.
Look for Mapping Expression for this target column. This target column will have the expression populated as SQ_LKP_RESOLUTION.NATURAL_SEGMENT_ID.
Open the Expression Editor for this expression.
Remove SQ_LKP_RESOLUTION.NATURAL_SEGMENT_ID from expression editor.
It should have nothing populated.
Click Apply and then click OK.
Save and close this Interface.
Re-generate the scenario under this folder: SDE_PSFT_ARTransactionFact_BillingDistribution_InitialBalance.
During ETL, the table W_PROJ_CLASSIFICATOIN_D is always truncated and reloaded.
In the table flexfield, set the value of 'OBI Table Maintenance Behaviour' to ALWAYS.
In all EBS LP components, set IS_SDS_DEPLOYED = N for this step.
For supplementary information about deploying object security for Project Analytics, refer to the following Technote on My Oracle Support:
Technote ID: 1607455.1 - OBIEE OBJECT SECURITY IMPLEMENTATION IN PROJECT ANALYTICS
This Technote explains how to apply object security to subject areas, tables, or columns by granting read access to the appropriate duty roles.
Oracle Business Intelligence Applications is available in the following languages:
| Language | Language Code |
|---|---|
|
Arabic |
l_ar |
|
Chinese (Simplified) |
l_zh-CN |
|
Chinese (Traditional) |
l_zh-TW |
|
Croatian |
l_hr |
|
Czech |
l_cs |
|
Danish |
l_da |
|
Dutch |
l_nl |
|
English |
l_en |
|
Finnish |
l_fi |
|
French |
l_fr |
|
French-Canadian |
l_fr-CA |
|
German |
l_de |
|
Greek |
l_el |
|
Hebrew |
l_he |
|
Hungarian |
l_hu |
|
Italian |
l_it |
|
Japanese |
l_ja |
|
Korean |
l_ko |
|
Norwegian |
l_no |
|
Polish |
l_pl |
|
Portuguese (Brazilian) |
l_pt-BR |
|
Portuguese |
l_pt |
|
Romanian |
l_ro |
|
Russian |
l_ru |
|
Slovak |
l_sk |
|
Spanish |
l_es |
|
Swedish |
l_sv |
|
Thai |
l_th |
|
Turkish |
l_tr |
This section describes issues and workarounds that are related to the use of Golden Gate, and contains the following notes:
Section 1.4.1, "SDS Support for PeopleSoft Learning Management"
Section 1.4.2, "SDS Support for Oracle E-Business Suite 11.5.10"
Section 1.4.3, "SDS Support for Oracle E-Business Suite Human Resources Analytics"
Section 1.4.4, "SDS Support for Oracle E-Business Suite With Service Analytics"
Section 1.4.6, "SDS Support For Oracle E-Business Suite With Procurement Analytics"
This release note applies only if you are using PeopleSoft Learning Management as a source for Oracle Business Analytics Warehouse and you want to enable SDS support for this source.
The PeopleSoft Learning Management (LM) pillar must be deployed with an associated Human Capital Management (HCM) pillar instance. However, PeopleSoft HCM does not require being deployed with an associated LM pillar. Due to this relationship, Oracle BI Applications treats HCM and LM as a single 'logical' application where LM is an optional component when HCM is deployed.
The SDS supports an application by providing a single schema where all tables associated with the logical application are stored. JD Edwards spreads data across multiple databases and eBusiness Suite spreads data across multiple schemas but in the SDS, all tables are stored in a single SDS schema. While it is possible (in the JDE case at least) for the same table to appear in more than one OLTP schema, the Oracle BI Applications ETL process only extracts from one of these tables and populates this table with data from that single OLTP schema.
In the case of PeopleSoft, tables appear in both OLTP schemas and have been instantiated in the ODI model. Several of these tables are not actually used and can be deleted to avoid conflict. However, there are cases where you extract from the same tables in both OLTP schemas, which can lead to conflict. The LM instance of these tables and the LM steps that extract from these tables must be configured to not leverage the SDS to avoid conflict.
Implement the following steps. First, delete the unused tables. Then, configure the remaining tables to not be deployed to the SDS. Then, configure the ETL steps that extract from these tables to not leverage the SDS. Finally, execute the steps to deploy the remaining tables to the SDS and populate them with data.
Navigate to 'Models - PeopleSoft 9.x - PeopleSoft 9.x LM - PeopleSoft 9.x LM'
Delete these data stores found under the following sub-models:
CEO-Enterprise Components:
• COUNTRY_TBL
• RT_DFLT_VW
NA:
• BUS_UNIT_HR_LNG
• BUS_UNIT_LANG
• BUS_UNIT_TBL_FS
• BUS_UNIT_TBL_GL
• DEPT_TBL_LANG
• NAMES
• STATE_TBL
PPT-PeopleTools:
• CURRENCY_CD_TBL
• PSASOFDATE
• PSPRCSRQST
• PSTREEDEFN
• PSTREELEAF
• PSTREENODE
• PSTREESTRCT
• RT_INDEX_TBL
• RT_RATE_TBL
• SET_CNTRL_REC
Configure the following data stores as 'View' rather than as 'Table' by editing the 'Datastore Type' property and changing it to 'View'. Though not actually views, this has no impact on the ETL process but does ensure these are not added to the SDS schema. The logic to generate the DDL for tables in the SDS only applies to tables and not to views. This avoids potential collision with the tables already created for the HCM pillar which would result in a 'name already used' error message. If this change is not made, then this error message will result but can be ignored.
PPT-PeopleTools:
• PSOPRDEFN
• PSXLATITEM
• PSXLATITEMLANG
Edit the following Load Plan Steps, selecting the Overwrite check box for the IS_SDS_DEPLOYED variable, and setting the 'Value' property to N. This causes these steps to extract data directly from the OLTP rather than the SDS instance of these tables. Since these tables in the SDS are only populated with data from the HCM pillar and not from the LM pillar, you must ensure these tasks only extract from the OLTP database.
Navigate to 'Load Plans and Scenarios - BIAPPS Load Plan - Load Plan Dev
Components - SDE - PSFT_X_X -
3 SDE Dims USER_DIM PSFT_X_X:
• SDE_PSFT_USERDIMENSION_JOBINFORMATION_LEARNING
• SDE_PSFT_USERDIMENSION_PERSONALINFORMATION_LEARNING
• SDE_PSFT_USERDIMENSION_LM_PRIMARY
3 SDE Dims STATUS_DIM PSFT_X_X:
• SDE_PSFT_STATUSDIMENSION_LEARNINGENROLLMENTSTATUS
3 SDE General Domain PSFT_X_X:
• SDE_PSFT_DOMAINGENERAL_PSXLATITEM_HCM ENROLLMENT_STATUS
Follow the steps to deploy the SDS as usual. At the steps where you generate the SDS DDL script and the script to initially load the SDS, execute the packages for the 'PeopleSoft X.X LM' model first, execute the scripts, then execute the packages for the 'PeopleSoft X.X HCM' model and execute the scripts. The script to initially load the SDS truncates the table and inserts data from the OLTP. As you have three tables used by both the HCM and LM pillars, you need to ensure the LM script is executed first and the HCM script is executed last - this will truncate the LM data from these tables and only populate them with HCM data.
This release note applies only if you are using Oracle E-Business Suite 11.5.10 as a source for Oracle Business Analytics Warehouse and you want to enable SDS support for this source. This release note does not apply to any other version of Oracle E-Business Suite.
When implementing the steps to create the SDS, one of the steps is to execute a script on the OLTP database that grants SELECT privileges to the OLTP tables. The IBY_PAYMENT_METHODS_TL table was erroneously included in the Oracle BI Applications Release 11.1.1.7.1 ODI repository as being associated with the Oracle E-Business Suite 11.5.10 database, but this table was introduced in the R12 version of Oracle E-Business Suite.
When executing the script against an Oracle E-Business Suite 11.5.10 database, the user will see the following:
GRANT SELECT ON APPS.IBY_PAYMENT_METHODS_TL TO GG_USER Error report: SQL Error: ORA-00942: table or view does not exist 00942. 00000 - "table or view does not exist" *Cause:
The user can ignore this error message; this table is not used in the Oracle E-Business Suite 11.5.10 adaptor.
Not applicable.
Some tasks for Oracle E-Business Suite fail in an Oracle GoldenGate SDS-enabled Load Plan Generation run. If you have deployed the Human Resources Analytics module, then you must implement the following Workaround.
In ODI Designer, navigate to the Design tab, and click on Load Plan and Scenarios.
Expand the 'BIAPPS Load Plan - Load Plan Dev Components - SDE' folder.
Choose your E-Business Suite release, and then find and edit the level 3 component for "3 SDE Dims TLCNSMR_DIM EBS_11_5_10".
Navigate to the 'Steps' subtab and select the root node TLCNSMR_DIM.
Navigate to the property Inspector and locate the variable IS_SDS_DEPLOYED. If the Property Inspector is not visible, then click on 'View - Property Inspector' in the menu. You should see the settings as Overwrite – Enabled, value – Null and Refresh Enabled.
Clear the Refresh check box, and assign the default value of 'N' for the IS_SDS_DEPLOYED parameter.
After this change, the option setting should be Overwrite – Enabled, value – 'N' and Refresh Disabled.
Save and Close the load plan component.
Generate (or if necessary, re-generate) the Load Plan.
Some tasks for Oracle E-Business Suite fail in an Oracle GoldenGate SDS-enabled Load Plan Generation run. If you have deployed the Service Analytics module, then you must implement the following Workaround.
In ODI Designer, navigate to the Design tab, and click on Load Plan and Scenarios.
Expand the 'BIAPPS Load Plan - Load Plan Dev Components - SDE' folder.
Choose your E-Business Suite release, and then find and edit the level 3 component for "SDE Fact ACTIVITY_FG EBS_<release number>."
Navigate to the 'Steps' subtab and select the root node ACTIVITY_FG.
Navigate to the property Inspector and locate the variable IS_SDS_DEPLOYED. If the Property Inspector is not visible, then click on 'View - Property Inspector' in the menu. You should see the settings as Overwrite – Enabled, value – Null and Refresh Enabled.
Clear the Refresh check box, and assign the default value of 'N' for the IS_SDS_DEPLOYED parameter.
After this change, the option setting should be Overwrite – Enabled, value – 'N' and Refresh Disabled.
Save and Close the load plan component.
Generate (or if necessary, re-generate) the Load Plan.
Some tasks for Oracle E-Business Suite fail in an Oracle GoldenGate SDS-enabled Load Plan Generation run. If you have deployed the Manufacturing and/or the Supply Chain Analytics modules, then you must implement the following Workaround.
In ODI Designer, navigate to the Design tab, and click on Load Plan and Scenarios.
Expand the 'BIAPPS Load Plan - Load Plan Dev Components - SDE' folder.
Choose your E-Business Suite release, and then find and edit the level 3 component for "3 SDE Fact MFGCOST_FG EBS_<release number>."
Navigate to the 'Steps' subtab and select the root node MFGCOST_FG.
Navigate to the property Inspector and locate the variable IS_SDS_DEPLOYED. If the Property Inspector is not visible, click on 'View - Property Inspector' in the menu. You should see the settings as Overwrite – Enabled, value – Null and Refresh Enabled.
Clear the Refresh check box, and assign the default value of 'N' for the IS_SDS_DEPLOYED parameter.
After this change, the option setting should be Overwrite – Enabled, value – 'N' and Refresh Disabled.
Save and Close the load plan component.
Follow steps 4 through 6 for the following additional components:
- 3 SDE Fact MFGMTLUSAGE_FG,- 3 SDE Fact MFGPERFORMANCE_FG,- 3 SDE Fact MFGPLAN_FG,- 3 SDE Fact MFGRESACTUAL_FG- 3 SDE Fact MFGRESCAP_FG,- 3 SDE Fact MFGRESCOST_FG,- 3 SDE Fact MFGRESPLAN_FG- 3 SDE Fact KANBANREPLENCYCLE_FG,- 3 SDE Fact QARESULTS_FG- 3 SDE Fact ITEMCOST_FG- 3 SDE Fact INVCYCNT_FG (EBS_11_5_10 only)
Generate (or if necessary, re-generate) the Load Plan.
The UOM Code and Potential Agreement Columns are not populated by some tasks when extracting from Oracle E-Business Suite in an Oracle GoldenGate SDS-enabled Load Plan Generation run.
Affected Release: Oracle BI Applications 11.1.1.7.1.
OLTP: All supported EBS adapter releases (11.5.10, R12, R12.1.1, R12.1.2, and R12.1.3).
In ODI Designer, navigate to the Design tab, and click on Load Plan and Scenarios.
Expand the 'BIAPPS Load Plan - Load Plan Dev Components - SDE' folder.
Choose your E-Business Suite release, and then find and edit the level 3 component for "3 SDE Fact PURAGG_FG EBS_<release number>."
Navigate to the 'Steps' sub-tab and select the root node PURAGG_FG.
Navigate to the property Inspector and locate the variable IS_SDS_DEPLOYED.
If the Property Inspector is not visible, then click on 'View - Property Inspector' in the menu.
You should see the settings as Overwrite – Enabled, value – Null and Refresh Enabled.
Clear the Refresh check box and assign the default value of 'N' for the IS_SDS_DEPLOYED parameter.
After this change, the option setting should be Overwrite – Enabled, value –'N' and Refresh Disabled.
Save and Close the Dev component.
Repeat steps 3 to 6 for the following Dev components:
"3 SDE Fact SPEND_FG EBS_<release number>" "3 SDE Fact PROCPO_FG EBS_<release number>" "3 SDE Fact PROCPURREQ_FG EBS_<release number>" "3 SDE Fact PROCPURRCPT_FG EBS_<release number>" "3 SDE Fact OP_FG EBS_<release number>"
Generate (or if necessary, re-generate) the Load Plan.
|
 Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|