Background and Issue Description

Bug Number 20957491

Issue: RFA : RFA

Product: Oracle BI Applications, 11.1.1.8.1

Source System: EBS all versions

OBIA 11.1.1.8.1SDE_ORA_STAGE_COSTCENTERDIMENSIONHIERARCHY runs

slow

Code Fix:
In order to achieve this, the following changes have to be made to the ODI Code. The following section
explains in detail the changes that are needed for each interface which has to be modified. Before you
make any changes, ensure that you have taken a backup of all the interfaces modified.

ODI Changes:

I.

Create Patch Folder and Enable version control

If patching an out-of-the-box task that has been customized, use the task
in the Custom folder there is no need to create a Patch folder.
1) Login to ODI repository from ODI studio and go to BI Apps Project, Under
Mappings folder, create a new patch adaptor folder.
a. Right-click the Mappings folder and select New Sub-Folder
b. Set Name as PATCH_<Original Adaptor Name>. For example, if this is
for the PLP folder, create the patch folder PATCH_PLP. This represents
the patch PLP folder for the original PLP folder. If this is for an
SDE_ORAR1213_ADAPTOR task, create PATCH_ SDE_ORAR1213_ADAPTOR
c. Click the Connect Navigator button in the Designer tab.
d. Select Edit Release Tags.
e. Select the release tag that corresponds to your source. For example,
PATCH_PLP would use BIA_11 while PATCH_ SDE_ORAR1213_ADAPTOR
would use EBS_12_1_3.
f. Select the patch folder you created and add it to the release tag.
g. Click Next
h. Click Finish
2) Enable versioning for the out-of-the-box Task Folder, for example,
SDE_ORA_Stage_CostCenterDimensionHierarchy. The version comment should
indicate this is the original 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.
a. Go to the out of the box Task folder , right-click the Task folder and
select Version > Create Version.
b. Accept the default version number, 1.0.0.0.
c. Add a description indicating that this is the original version of this task.
3) Duplicate
the
Task
folder
to
be
patched
(i.e.
SDE_ORA_Stage_CostCenterDimensionHierarchy) by copying it. Cut and paste the
copied task folder to the Patch adaptor folder you have created, and rename
it to remove the 'Copy of' prefix.
4) Using the same method as in step 3, enable versioning of the copied Task
folder. The version comment should indicate this is the original version. This
versioning enables comparison of the patched task to a copy of the original
version to determine all changes that have been introduced.
5) Create another version of the copied task. The version comment should
indicate this is the patched version. Use the same steps as above.

II.

Make the following changes:

Please follow the below steps to add the below mentioned hint in the filter to
improve the performance.

Go to the SDE_ORA_Stage_CostCenterDimensionHierarchy folder and

open
the
SDE_ORA_Stage_CostCenterDimensionHierarchy_SQ_COST_CENTER_HI
ER_PS temporary(yellow) interface.

Click on mapping and select GET_TOPMOST_REC , go to the quick edit

-Filters and change the below filter condition by adding hint as
follows.

CURRENT FILTER CONDITION:

FND_FLEX_VALUE_NORM_HIERARCHY.PARENT_FLEX_VALUE NOT IN (SELECT
FLEX_VALUE
FROM QUALIFY(FND_FLEX_VALUE_CHILDREN_V) B WHERE
FND_FLEX_VALUE_NORM_HIERARCHY.FLEX_VALUE_SET_ID
B.FLEX_VALUE_SET_ID)
.

NEW FILTER CONDITION WOULD BE:

FND_FLEX_VALUE_NORM_HIERARCHY.PARENT_FLEX_VALUE NOT IN (SELECT
/*+ NO_MERGE
(B)
PUSH_PRED
(B)*/
QUALIFY(FND_FLEX_VALUE_CHILDREN_V) B

FLEX_VALUE

FROM

WHERE
FND_FLEX_VALUE_NORM_HIERARCHY.FLEX_VALUE_SET_ID
B.FLEX_VALUE_SET_ID)

After modifying the filter condition, save the interface.

Open the appropriate SDE_ORAR1213_ADAPTOR patch folder in your ODI repository using ODI studio
and make the following changes.

Goto SDE_ORA_Stage_CostCenterDimensionHierarchy folder

Open SDE_ORA_Stage_CostCenterDimensionHierarchy package and click on DIAGRAM tab.

Right-Click on IS_INCREMENTAL step and select FIRST STEP

III.

Save the changes to the package.

Generate scenario for patched task.

1) Generate a scenario for the patch task:
* Navigate to the patch Task folder - Packages - Right-click on the Package
SDE_ORA_STAGE_COSTCENTERDIMENSIONHIERARCHY*

* Right click the package and select 'Generate Scenario'

* Use the original, out-of-the-box scenario name (CTRL-V to paste the name if
you copied it previously). Ensure the scenario version number is larger than
the out-of-the-box scenario. All scenarios ship with version number 001 so
you can use 002 for example.
* Check the 'Generate scenario as if all underlying objects are materialized'
box
* Click 'OK'
* Select 'Use All' from the 'Startup Parameters' drop down box
* Click 'OK'
Load plans are configured to execute the scenario with the largest version
number. When you execute the load plan, it will now execute the patch task
rather than the original task since the patch task has a larger version number.
In the future if you make changes to any of the interfaces or the package, you
can either regenerate the existing scenario or generate a new scenario. Unless
you need separate scenarios, it is recommended that you regenerate the
existing scenario. To do this, right-click the scenario and select Regenerate.

Data Fix:

Ensure that you run a full load to correct the data already loaded in the DW.
Make
sure
to
update
W_ETL_LOAD_DATES.COMMITTED=0
for
SDE_ORA_STAGE_COSTCENTERDIMENSIONHIERARCHY.

the

package