ODI GroupAccounts ConfigureMultipleSegments

Background and Issue Description
Related Bug Number: 9202898 (ODI equivalent/adaptation for 11g)
Product: Oracle BI Applications, Financial Analytics
Issue: The current architecture of Group Account Numbers supports mapping only the Natural
Account segment values to a Group Account Number. It doesnt support mapping multiple charts
of accounts (COA) segments to Group Account Number.
Code Fix:
In order to achieve this, the following changes have to be made to the code. For a single chart of
accounts configuration, refer to the steps given below. In case you have a multiple chart of accounts
configuration, in addition to these refer to the extra steps given in section 2.
1. Single Chart of Accounts Configuration

Source File Changes:
a. Open the file file_group_account_codes_ora.csv file under the folder(s):
Source-Independent Files <Oracle Home for BI>\biapps\etl\data_files\src_files\
Source-specific Files <Oracle Home for BI>\biapps\etl\data_files\src_files\<source adaptor>
b. Add range columns for each additional segment used. You can name the columns like FROM
SEG<x> and TO SEG<x>. Suppose you have 2 segments (Cost Center and Balancing Segment)
in addition to Natural Account then you will have 3 pairs of range columns totally and you will
need to assign one range to one segment as shown below.
c.
For example FROM ACCT & TO ACCT will be for natural account, FROM SEG1 & TO SEG1 is
for cost center and FROM SEG2 & TO SEG2 is for Balancing Segment. Assign the Group
Account Numbers accordingly.
d. Save the file. The file after your changes should something like the one given below.
ODI Changes:
Source and target table changes:
1. Since we are adding new columns in the source file, the corresponding table definition in ODI
needs to be modified reflect these changes.
a.
b.
c.
d.
e.
f.
Open current ODI Repository by providing necessary credentials.

Go to Models section of the Designer tab.
Open Oracle E-Business Suite 11.5.10 section within Models.
Expand Oracle E-Business Suite 11.5.10 Source Files section
Search and find FILE_GROUP_ACCT_NUM and double click to open.
Go to columns section and add new columns (FROM_SEG1,TO_SEG1,
FROM_SEG2, TO_SEG2) as follows:
Note: Please ensure that the order of these columns matches
the physical data file, If necessary rearrange the columns.
2. Now modify the target table (W_ORA_GROUP_ACCOUNT_NUM_D_TMP) which is used to

populate data from the above source as follows:
a.
b.
c.
d.
e.
f.
Open current ODI Repository by providing necessary credentials.

Go to Models section of the Designer tab.
Open Oracle BI Applications section within Models.
Expand Oracle BI Applications section
Expand Dimension Temporary section
Search and find Group Account staging table with alias as
W_ORA_GROUP_ACCOUNT_NUM_D_TMP and double click to open.
g. Go to columns section and add new columns (FROM_SEG1,TO_SEG1,
FROM_SEG2, TO_SEG2) as follows:
3. Apply the same DDL change(s) manually to the underlying Data warehouse
database if necessary.
ALTER TABLE W_ORA_GROUP_ACCOUNT_NUM_D_TMP ADD(FROM_SEG1
VARCHAR2(30 CHAR), TO_SEG1 VARCHAR2(30), FROM_SEG2 VARCHAR2(30),
TO_SEG2 VARCHAR2(30));
ODI mapping changes:

Note: Before you begin please take a backup of the ODI repository prior to making code
changes.
4. Open Projects section of the ODI Repository under Designer Tab.
5. Expand Mappings section within BI Apps Project
6. Expand the Adaptor folder in which you want to make and apply changes (e.g.
SDE_ORA11510_Adaptor).
7. Open the interface SDE_ORA_Stage_GroupAccountNumberDimension to map the newly
added columns from the source to the target.
8. As the ranges can now repeat, the Integration ID has to be changed to include the starting range
of each segment. So change the Integration ID derivation to concatenate FROM_SEG<x>
columns in addition to the CHART_OF_ACCOUNTS_ID and FROM_ACCT_NUM_IN columns.
(e.g. FILE_GROUP_ACCT_NUM.CHART_OF_ACCOUNTS_ID||'~'||
FILE_GROUP_ACCT_NUM.FROM_ACCT_NUM||'~'||
FILE_GROUP_ACCT_NUM.FROM_SEG1||'~'||
FILE_GROUP_ACCT_NUM.FROM_SEG2).
9. As you have already added the new column(s) to W_ORA_GROUP_ACCOUNT_NUM_D_TMP

table, you should now see that the new unmapped columns are shown in the mappings section.
Map the source using the mapping expression for each additional segment used for mapping
Group Account Number. The modified mapping should look like
10. Modify the filter condition to include the new columns being mapped as follows:
11. Save the Interface and regenerate the scenario.

12. Now, that we have made necessary changes to bring data for mapping multiple chart of account
segment information to group accounts into a temporary table. We now have to modify the next
SDE mapping in the flow to bring this information into the GL Account Dimension table. For that,
open the interface SDE_ORA_GLAccountDimension.
13. Expand Interfaces, and open the main interface
(SDE_ORA_GLAccountDimension.W_GL_ACCOUNT_DS) for editing.
14. Click on Quick-Edit and expand Joins to view existing joins.
15. We need to modify an existing join to include the equalization (bringing all scattered segment
values into one place to facilitate storing in a single column in GL Account dimension). For this,
open the join expression between temp interface
(W_GL_ACCOUNT_DS_SQ_BCI_GL_ACCOUNTS) and the Group Account staging temporary
table Lookup (LKP_W_ORA_GROUP_ACNT_NUM_D_TMP as follows:
16. Modify the expression to include the additional joins (conditions) to account for the two new
account segment ranges that we are planning to include as follows:
Assumptions in the example:
In the below join expression(s), it is assumed that FROM_SEG1 & TO_SEG1 contains segment
values that are mapped to SEG1 in the file_glacct_segment_config_ora.csv file. Similarly
FROM_SEG2 & TO_SEG2 contains segment values that are mapped to SEG2 in the csv file.
Hence the 2 join conditions below use the columns LKP_HIER_CONFIG.SEG1 &
LKP_HIER_CONFIG.SEG2 respectively. You need to use appropriate column(s) for the join
condition depending on which segment column in the file_glacct_segment_config_ora.csv file
that the ranges you are providing fall into.
For example, if FROM_SEG1 & TO_SEG1 contains segment values that fall into SEG5 in the
file_glacct_segment_config_ora.csv file, use LKP_HIER_CONFIG.SEG5 instead of
LKP_HIER_CONFIG.SEG1 in the below example.
However, if you are providing ranges for "Cost Center" or "Balancing Segment" segments,
then instead of LKP_HIER_CONFIG.SEG1/LKP_HIER_CONFIG.SEG2, you need to use the
columns COST_CENTER_NUM & BALANCING_SEGMENT_NUM respectively.
OLD Join Expression:

TO_CHAR(SQ_BCI_GL_ACCOUNTS.CHART_OF_ACCOUNTS_ID) =
LKP_W_ORA_GROUP_ACNT_NUM_D_TMP.CHART_OF_ACCOUNTS_ID
AND #DATASOURCE_NUM_ID=LKP_W_ORA_GROUP_ACNT_NUM_D_TMP.DATASOURCE_NUM_ID
AND
SQ_BCI_GL_ACCOUNTS.NATURAL_ACCOUNT_NUM >=
LKP_W_ORA_GROUP_ACNT_NUM_D_TMP.FROM_ACCT_NUM
AND
SQ_BCI_GL_ACCOUNTS.NATURAL_ACCOUNT_NUM <=
LKP_W_ORA_GROUP_ACNT_NUM_D_TMP.TO_ACCT_NUM
NEW Join Expression:

TO_CHAR(SQ_BCI_GL_ACCOUNTS.CHART_OF_ACCOUNTS_ID) =
/* lookup for from_acct and to_acct range*/

AND
AND
/* end lookup for from_acct and to_acct range*/

/* lookup for from_seg1 and to_seg1 range*/
AND CASE
WHEN LKP_HIER_CONFIG.SEG1 = 'SEGMENT1' THEN SQ_BCI_GL_ACCOUNTS.SEGMENT1
ELSE NULL
END >= LKP_W_ORA_GROUP_ACNT_NUM_D_TMP.FROM_SEG1
AND
CASE

ELSE NULL
END <= LKP_W_ORA_GROUP_ACNT_NUM_D_TMP.TO_SEG1
/* end lookup for from_seg1 and to_seg1 range*/

/* lookup for from_seg2 and to_seg2 range */
AND CASE
ELSE NULL
AND
CASE

ELSE NULL
/* end lookup for from_seg2 and to_seg2 range */

17. Save the Interface and regenerate the scenario.
2. Additional Steps for Multiple Chart of Accounts Configuration.

This section specifies the additional steps that you may have to do in case you have a multiple
Chart of Accounts configuration. This would be required when there are different Group Account
Number mapping mechanisms for different COAs. For example, for COA1, your Group Account
Number is based on Natural Account + 2 segments, for COA2, it is Natural Account + 1 segment
and for COA3 it is just Natural Account. In such cases you would have to make the additional
changes mentioned below.
Source File Changes:
Lets take an example where you have 3 COAs. For COA 101, the group account number is
determined using natural account, cost center and balancing segment. For COA 102, its based
on natural account and cost center. For COA 103, its based on natural account only. That means,
you have 3 distinct segments (natural account, cost center, balancing segment) among all the 3
COAs that are used for group account number derivation. So, have 3 pairs of range columns in
the file, as shown below. Designate one pair of range to one segment - for example, FROM ACCT
& TO ACCT is for natural account, FROM SEG1 & TO SEG1 is for cost center, and FROM SEG2
& TO SEG2 is for balancing segment.
In step c, when you are defining the ranges, fill the ranges that are applicable for the COA and
use a default value (such as NA) for the range which is not relevant for a particular COA. In this
example, you will populate all 3 ranges for COA 101, FROM ACCT, TO ACCT & FROM SEG1, TO
SEG1 for COA 102 and just FROM ACCT, TO ACCT for COA 103 and populate the default value
for the remaining ranges, as illustrated in the screenshot below.
Note: Use a default value that wouldnt be a valid segment value. For example, if you happen to
have a segment which has NA as a valid value, then you cannot use NA but pick something else.
You will be using the same default value you pick here in one of the ODI mapping changes
explained in later sections.
ODI Changes:
All the steps (1-15) mentioned above for single chart of account configuration would remain the
same.
For Step 16 above the new join expression should now consider the above scenario where some
of the segment ranges are not applicable for various chart of accounts. So, the new join
expression for the above scenario is as follows:
NEW Join Expression:
TO_CHAR(SQ_BCI_GL_ACCOUNTS.CHART_OF_ACCOUNTS_ID)=
/* lookup for from_acct and to_acct range*/

AND
AND
/* end lookup for from_acct and to_acct range*/

AND (
/* set to 'NA' for COAs that dont use from_seg1 and to_seg1 range */
CASE WHEN TO_CHAR(SQ_BCI_GL_ACCOUNTS.CHART_OF_ACCOUNTS_ID) IN ('103') THEN 'NA' ELSE
CASE

ELSE NULL
AND
CASE
ELSE NULL
END)

AND (
/* set to 'NA' for COAs that dont use from_seg2 and to_seg2 range */
CASE WHEN TO_CHAR(SQ_BCI_GL_ACCOUNTS.CHART_OF_ACCOUNTS_ID) IN ('102','103') THEN 'NA' ELSE
CASE

ELSE NULL
AND
CASE
ELSE NULL
END)

ODI GroupAccounts ConfigureMultipleSegments

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ODI GroupAccounts ConfigureMultipleSegments

Transféré par

Droits d'auteur :

Formats disponibles

Background and Issue Description

Related Bug Number: 9202898 (ODI equivalent/adaptation for 11g)

Product: Oracle BI Applications, Financial Analytics

1. Single Chart of Accounts Configuration

Open current ODI Repository by providing necessary credentials.

2. Now modify the target table (W_ORA_GROUP_ACCOUNT_NUM_D_TMP) which is used to

Open current ODI Repository by providing necessary credentials.

ODI mapping changes:

9. As you have already added the new column(s) to W_ORA_GROUP_ACCOUNT_NUM_D_TMP

11. Save the Interface and regenerate the scenario.

OLD Join Expression:

NEW Join Expression:

/* lookup for from_acct and to_acct range*/

/* end lookup for from_acct and to_acct range*/

WHEN LKP_HIER_CONFIG.SEG1 = 'SEGMENT6' THEN SQ_BCI_GL_ACCOUNTS.SEGMENT6

/* end lookup for from_seg1 and to_seg1 range*/

WHEN LKP_HIER_CONFIG.SEG2 = 'SEGMENT5' THEN SQ_BCI_GL_ACCOUNTS.SEGMENT5

/* end lookup for from_seg2 and to_seg2 range */

2. Additional Steps for Multiple Chart of Accounts Configuration.

Source File Changes:

/* lookup for from_acct and to_acct range*/

/* end lookup for from_acct and to_acct range*/

WHEN LKP_HIER_CONFIG.SEG1 = 'SEGMENT14' THEN SQ_BCI_GL_ACCOUNTS.SEGMENT14

/* end lookup for from_seg1 and to_seg1 range */

WHEN LKP_HIER_CONFIG.SEG2 = 'SEGMENT9' THEN SQ_BCI_GL_ACCOUNTS.SEGMENT9

/* end lookup for from_seg1 and to_seg1 range */

Vous aimerez peut-être aussi