Background and Feature Description

Related Bug Number

: 18711839
Product:
Oracle Business Analytics Application : 11.1.1.8.1
OLTP Version
: All

Feature
:
This document gives steps to modify SIL_GLOtherFact, improving its
performance by replacing LEFT OUTER join with correlated query.

Tech Note instruction overview:

Please note customer must following the standard customization
process to make the change in custom folder instead of OOTB
folders. This is needed in order for our future ODI metadata patches to work
in your repository.
As part of the standard customization process, you will copy the existing
mapping folder to a custom folder, make changes in the custom folder, delete
the OOTB scenario from the original mapping folder, and then generate the
new scenarios in the custom folder using the original OOTB scenario name.
If you are not familiar with this procedure, please see the detail instruction in
Instructions_How_to_Make_Change_on_ODI_Mappings.doc.

Solution:
Steps: ODI Changes

1 Follow the step of 1 Create Custom Folder and Enable version

control in Instructions_How_to_Make_Change_on_ODI_Mappings.doc,
Create CUSTOM_SILOS folder, copy task folder SIL_GLOtherFact from
SILOS and enable version control.
2 In CUSTOMER_SILOS folder, open SIL_GLOtherFact, then its interface
SIL_GLOtherFact.W_GL_OTHER_F_SQ_W_GL_OTHER_FS. Go to QuickEdit.

From Sources, find source W_MCAL_PERIOD_D_BUDGET_PERIOD, then write

down the 3 attributes of it:
Source Name: Fiscal Period Dimension Table
Alias: W_MCAL_PERIOD_D_BUDGET_PERIOD
Join Expression: (can be found in Joins section)
W_GL_OTHER_FS.BUDGET_PERIOD_ID=W_MCAL_PERIOD_D_BUDGET_PERIOD.INTE
GRATION_ID
AND
W_GL_OTHER_FS.DATASOURCE_NUM_ID=W_MCAL_PERIOD_D_BUDGET_PERIOD.DA
TASOURCE_NUM_ID

Delete source W_MCAL_PERIOD_D_BUDGET_PERIOD by clicking the X icon

on the right. You will see a pop up window for you to confirm the delete. Click
Yes to finish the delete.

Go to Lookups, create a new lookup by clicking the + icon on the right.

a. In Lookup Wizard step 1 of 2, choosing the lookup table by
entering the Source Name in step 3
b. Rename Alias to the Alias in step 3
c. Click Next, in Lookup Wizard step 2 of 2, enter the lookup condition
by pasting Join Expression in step 3
d. Change the Lookup Type to SQL expression in the select clause
e. Click Finish, then save the change.

Repeat step 3 to step 5 to change the following sources to lookups, identified

by Alias:
BUDGT
U1
U2
W_BUDGET_D
W_LEDGER_D_BUDGET_LEDGER
W_LEDGER_D
W_MCAL_CONTEXT_G
W_MCAL_PERIOD_D
W_XACT_SOURCE_D_JOURNAL_SOURCE
W_XACT_TYPE_D_BALANCETYPE
X5
Note: Do NOT apply the change on ACCT

Create a new Lookup LKP_W_INT_ORG_D_BSV_LE with the following attributes:

a. In Lookup Wizard step 1 of 2, choose
W_GL_OTHER_FS(W_GL_OTHER _FS) as driving table, find lookup table
W_INT_ORG_D_BSV_LE and change the alias to
LKP_W_INT_ORG_D_BSV_LE
b. Click Next, in Lookup Wizard step 2 of 2, enter the lookup condition
as below:

W_GL_OTHER_FS.LEDGER_ID
=
LKP_W_INT_ORG_D_BSV_LE.LEGER_ID
c. Change the Lookup Type to SQL expression in the select clause
d. Click Finish.
e. Re-open the lookup condition, change it to
W_GL_OTHER_FS.LEDGER_ID = LKP_W_INT_ORG_D_BSV_LE.LEGER_ID
AND ACCT.BALANCING_SEGMENT_ATTRIB =
LKP_W_INT_ORG_D_BSV_LE.VALUE_SET_ID
AND ACCT.BALANCING_SEGMENT_NUM =
LKP_W_INT_ORG_D_BSV_LE.SEGMENT_VALUE
AND W_GL_OTHER_FS.DATASOURCE_NUM_ID =
LKP_W_INT_ORG_D_BSV_LE.DATASOURCE_NUM_ID
Note: step b. and e. is to overcome an ODI limitation. Sometimes you
have trouble creating a lookup which joins to two sources but you can
later modify the joins to two sources.

Create a new target column LEGAL_ENTITY_ID, as screenshot below. Map it to

LKP_W_INT_ORG_D_BSV_LE.LEGAL_ENTITY_ID

9 Save the change SIL_GLOtherFact.W_GL_OTHER_F_SQ_W_GL_OTHER_FS.

10 Open another interface SIL_GLOtherFact.W_GL_OTHER_F. Go to Quick-Edit

11 Repeat step 3 to step 5 to change the following sources to lookups, identified

by Alias:
LKP_W_GL_SEGMENT_D1
LKP_W_GL_SEGMENT_D2
LKP_W_GL_SEGMENT_D3
LKP_W_GL_SEGMENT_D4
LKP_W_GL_SEGMENT_D5
LKP_W_GL_SEGMENT_D6
LKP_W_GL_SEGMENT_D7
LKP_W_GL_SEGMENT_D8
LKP_W_GL_SEGMENT_D9
LKP_W_GL_SEGMENT_D10
LKP_W_GL_SEGMENT_D_PROJECT
LKP_W_GL_SEGMENT_D_PROGRAM
LKP_W_INT_ORG_D_BUSN_AREA_ORG
LKP_W_INT_ORG_D_CTRL_AREA_ORG
LKP_W_INT_ORG_D_FIN_AREA_ORG
LKP_W_INT_ORG_D_ISSUE_ORG
LKP_W_INT_ORG_D_SALES_ORG
LKP_W_INT_ORG_D_SALES_GROUP

LKP_W_INT_ORG_D_PURCH_ORG
LKP_W_XACT_TYPE_D_REF_DOC
LKP_W_XACT_TYPE_D_CLRNG_DOC
LKP_W_PAYMENT_METHOD_D
LKP_W_PAYMENT_TERMS_D
LKP_W_PRODUCT_D
LKP_W_INT_ORG_D_COMPANY_ORG
For LKP_W_INT_ORG_D_COMPANY_ORG, change the lookup condition to:
SQ_W_GL_OTHER_FS.DATASOURCE_NUM_ID =
LKP_W_INT_ORG_D_COMPANY_ORG.DATASOURCE_NUM_ID
AND
COALESCE(SQ_W_GL_OTHER_FS.COMPANY_ORG_ID,'COMPANY~'||
SQ_W_GL_OTHER_FS.LEGAL_ENTITY_ID) =
LKP_W_INT_ORG_D_COMPANY_ORG.INTEGRATION_ID
AND
SQ_W_GL_OTHER_FS.ACCT_PERIOD_END_DT >=
LKP_W_INT_ORG_D_COMPANY_ORG.EFFECTIVE_FROM_DT
AND
SQ_W_GL_OTHER_FS.ACCT_PERIOD_END_DT <
LKP_W_INT_ORG_D_COMPANY_ORG.EFFECTIVE_TO_DT
This new lookup condition use the new target column created in step 8
12 Delete source LKP_W_INT_ORG_D_BSV_LE. You should NOT see the pop up
window for you to confirm the delete.
13 For existing lookups, change the lookup type to SQL expression in the select
clause for all lookups except
LKP_W_GLOBAL_EXCH_RATE_G(LKP_W_GLOBAL_EXCH_RATE_G) and
LKP_W_EXCH_RATE_G_LOC(LKP_W_EXCH_RATE_G), which will still remain as
SQL left-outer join in the from clause.
You lookups should look like this after the fix:

14 Following the step of 3 Delete the old scenario and create new
scenario in
Instructions_How_to_Make_Change_on_ODI_Mappings.doc to create
new scenario SILOS_SIL_GLOTHERFACT in CUSTOM_SILOS folder.