Anda di halaman 1dari 12

Group Account Configuration - OBIA 11.1.1.7.

1
This question is Not Answered.

VenkatGal Jan 8, 2014 3:10 AM


Hello,
I am setting up Financial Analytics OBIA 11.1.1.7.1, have following questions regarding
group account code setup

1. Should we always use Natural Account Segment for mapping to Group Acount Codes?
I could see a customer is using different segment (Sub Account) to classify their
accounts to various categories. Should we use combination of Natural Account and Sub
Account to classify them in to various Oracle supplied group account numbers?

2.If i have to go with multiple segments for group account configuration, i could n't see
a technical note from oracle support for OBIA 11.1.1.7.1 where ETL tool is ODI. Can we
customize ODI using the technote available for Informatica based OBIA 7964 tech note?
Are there any chnages to apply on top of it?

Thanks
Venkat G
I have the same question Show 0 Likes(0)
742 Views
Tags:
REPLY
Average User Rating: No ratings (0 ratings)
Average User Rating
No ratings
(0 ratings)
Your Rating:
Rate Poor(1 of 5)Rate Below Average(2 of 5)Rate Average(3 of 5)Rate Above Average(4 of 5)Rate
Exceptional(5 of 5)

1. Re: Group Account Configuration - OBIA 11.1.1.7.1

Ian Bristow-Oracle Jan 6, 2014 2:47 AM (in response to VenkatGal)


Venkat,
Firstly, welcome to the forums.

I will have to refer to my colleagues who know OBIA better than me to get an answer
for you. However, I would expect that the note to which you refer, would not be
suitable for ODI. What is the note number?

Many thanks. Regards,


Ian Bristow
o Like Show 0 Likes(0)
o Reply
o Actions
2. Re: Group Account Configuration - OBIA 11.1.1.7.1

User772439-Oracle Feb 15, 2014 12:19 PM (in response to VenkatGal)


Hi Venkat
I wanted to share more information on the group account configuration in BI Apps
11.1.1.7.1
The recommendation is to use the Configuration Manager :

1. Go to "Manage Warehouse Domains" in the Config. Manager.


2. Select Offering "Oracle Financial Analytics" and Dim Group "GL Account Dimension"
and click Search.
3. Select "Group Account".

Then you will see the seeded group account numbers.

The mapping between Group Account to Fin Statement has been moved to BIApps
Config Manager (BIACM) in 11.1.1.7.1.

It is not in a csv file anymore. It is a domain member mapping between the following
domains.

Source Domain: Group Account (W_GL_GROUP_ACCOUNT )


Target Domain: Financials Statement Item (W_FIN_STMT )

Refer to the following section in Configuration Guide for information on domains and
mappings:

--> 4.4 About Working With Domains and Domain Mappings


(http://docs.oracle.com/cd/E38317_01/doc.11117/e36171/setup_admin.htm#BABDFHA
B)

Additional information on this:


================================

How to Set Up Group Account Numbers for Oracle EBS

This section explains how to map Oracle General Ledger Accounts to Group
Account Numbers, and includes the following topics:
An overview of setting up Oracle General Ledger Accounts - see Section
B.2.20.1, "Overview of Mapping Oracle GL Accounts to Group Account Numbers".
A description of how to map Oracle General Ledger Accounts to Group Account
Numbers - see Section B.2.20.2, "How to Map Oracle GL Account Numbers to
Group Account Numbers".
An example that explains how to add Group Account Number metrics to the
Oracle BI Repository - see Section B.2.20.3, "Example of Adding Group Account
Number Metrics to the Oracle BI Repository".
.
Note
It is critical that the GL account numbers are mapped to the group account
numbers (or domain values) because the metrics in the GL reporting layer use
these values. For a list of domain values for GL account numbers, see Oracle
Business Analytics Warehouse Data Model Reference.
.
Overview of Mapping Oracle GL Accounts to Group Account Numbers
Group Account Number Configuration is an important step in the configuration
of Financial Analytics, because it determines the accuracy of the majority of
metrics in the General Ledger and Profitability module. Group Accounts in
combination with Financial Statement Codes are also leveraged in the GL
reconciliation process, to ensure that subledger data reconciles with GL
journal entries. This topic is discussed in more detail later in this
section.
You set up General Ledger accounts using the following configuration file
located in adaptor specific source files directory (e.g.

\SRC_FILES\EBS11510) of the physical data source that was defined as part of


Oracle BI Applications Configuration:
file_group_acct_codes_ora.csv - this file maps General Ledger accounts to
group account codes.
Before you load your data, you must ensure that the account values are mapped
consistently across these three configuration files.
You can categorize your Oracle General Ledger accounts into specific group
account numbers. The group account number is used during data extraction as
well as front-end reporting. The GROUP_ACCT_NUM field in the GL Account
dimension table W_GL_ACCOUNT_D denotes the nature of the General Ledger
accounts (for example, cash account, payroll account). For a list of the
Group Account Number domain values, see Oracle Business Analytics Warehouse
Data Model Reference. The mappings to General Ledger Accounts Numbers are
important for both Profitability analysis and General Ledger analysis (for
example, Balance Sheets, Profit and Loss, Cash Flow statements).
The logic for assigning the group accounts is located in the
file_group_acct_codes_ora.csv file. Table B??3 shows an example configuration
of the file_group_acct_codes_ora.csv file.
.
Example Configuration of file_group_acct_codes_ora.csv File
CHART OF ACCOUNTS ID FROM ACCT TO ACCT GROUP_ACCT_NUM
1 101010 101099 CA
1 131010 131939 FG INV
1 152121 152401 RM INV
1 171101 171901 WIP INV
1 173001 173001 PPE
1 240100 240120 ACC DEPCN
1 261000 261100 INT EXP
1 181011 181918 CASH
1 251100 251120 ST BORR
.
In Table B??3, in the first row, all accounts within the account number range
from 101010 to 101099 that have a Chart of Account (COA) ID equal to 1 are
assigned to Current Asset (that is, CA). Each row maps all accounts within
the specified account number range and within the given chart of account ID.
If you need to create a new group of account numbers, you can create new rows
in Oracle BI Applications Configuration Manager. You can then assign GL
accounts to the new group of account numbers in the
file_group_acct_codes_ora.csv file.
You must also add a new row in Oracle BI Applications Configuration Manager
to map Financial Statement Item codes to the respective Base Table Facts.
Table B??4 shows the Financial Statement Item codes to which Group Account
Numbers must map, and their associated base fact tables.
.
Financial Statement Item Codes and Associated Base Fact Tables
Financial Statement Item Codes Base Fact Tables
AP AP base fact (W_AP_XACT_F)
AR AR base fact (W_AR_XACT_F)
COGS Cost of Goods Sold base fact (W_GL_COGS_F)
REVENUE Revenue base fact (W_GL_REVN_F)
TAX Tax base fact (W_TAX_XACT_F)
OTHERS GL Journal base fact (W_GL_OTHER_F)
.
By mapping your GL accounts against the group account numbers and then
associating the group account number to a Financial Statement Item code, you
have indirectly associated the GL account numbers to Financial Statement Item
codes as well. This association is important to perform GL reconciliation and
to ensure the subledger data reconciles with GL journal entries. It is
possible that after an invoice has been transferred to GL, a GL user might
adjust that invoice in GL. In this scenario, it is important to ensure that
the adjustment amount is reflected in the subledger base fact as well as
balance tables. To determine such subledger transactions in GL, the
reconciliation process uses Financial Statement Item codes.
Financial Statement Item codes are internal codes used by the ETL process to
process the GL journal records during the GL reconciliation process against
the subledgers. When the ETL process reconciles a GL journal record, it looks
at the Financial Statement Item code associated with the GL account that the
journal is charging against, and then uses the value of the Financial
Statement item code to decide which base fact the GL journal should reconcile
against. For example, when processing a GL journal that charges to a GL
account which is associate to 'AP' Financial Statement Item code, then the
ETL process will try to go against AP base fact table (W_AP_XACT_F), and try
to locate the corresponding matching AP accounting entry. If that GL account
is associated with the 'REVENUE' Financial Statement Item code, then the ETL
program will try to go against the Revenue base fact table (W_GL_REVN_F), and
try to locate the corresponding matching Revenue accounting entry.
How to Map Oracle GL Account Numbers to Group Account Numbers
This section explains how to map Oracle General Ledger Account Numbers to
Group Account Numbers.
.
Note
If you add new Group Account Numbers to the file_group_acct_codes_ora.csv
file, you must also add metrics to the Oracle BI repository. See Section
B.2.20.3, "Example of Adding Group Account Number Metrics to the Oracle BI
Repository" for more information.
.
To map Oracle GL account numbers to group account numbers:
Open the file_group_acct_codes_ora.csv file with a text editor in the
$PMServer\SrcFiles directory (for example,
\SRC_FILES\EBS11510).
For each Oracle GL account number that you want to map, create a new row in
the file containing the following fields:
.
Field Name Description
CHART OF ACCOUNTS ID The ID of the GL chart of account.
FROM ACCT The lower limit of the natural account range. This is based on the
natural account segment of your GL accounts.
TO ACCT The higher limit of the natural account range. This is based on the
natural account segment of your GL accounts.
GROUP_ACCT_NUM This field denotes the group account number of the Oracle
General Ledger account, as specified in the file_group_acct_names.csv file.
For example, 'AP' for Accounts Payables, 'CASH' for cash account, 'GEN
PAYROLL' for payroll account, and so on.
.
For example:
101, 1110, 1110, CASH
101, 1210, 1210, AR
101, 1220, 1220, AR
.
Note
You can optionally remove the unused rows from the CSV file.
.
Ensure that the values that you specify in the file_group_acct_codes_ora.csv
file are consistent with the values that are specified in Oracle BI
Applications Configuration Manager for Group Accounts.
See Figure B??2, "Configuration Files for Configuring Group Accounts for
Oracle EBS" for an example.
Save and close the CSV file.
Example of Adding Group Account Number Metrics to the Oracle BI Repository
If you add new Group Account Numbers to the file_group_acct_codes_ora.csv
file (as described in Section B.2.20.2, "How to Map Oracle GL Account Numbers
to Group Account Numbers"), you must also add metrics to the Oracle BI
repository to expose the new Group Account Numbers. This example illustrates
how you can add Group Account Number metrics using the Oracle BI
Administration Tool.
This example assumes that you have a new Group Account Number called
'Payroll', and you want to add a new metric to the Presentation layer called
'Payroll Expense'.
To add a new metric in the logical table Fact ?? Fins ?? GL Other Posted
Transaction:
Using the Administration Tool, open OracleBIAnalyticsApps.rpd.
The OracleBIAnalyticsApps.rpd file is located at:
ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_
obisn\repository
.
In the Business Model and Mapping layer:
Create a logical column named 'Payroll Expense' in the logical table 'Fact ??
Fins ?? GL Other Posted Transaction'.
For example, right-click the Core\Fact - Fins - GL Other Posted Transaction\
object and choose New Object, then Logical Column, to display the Logical
Column dialog. Specify Payroll Expense in the Name field.
Display the Aggregation tab, and then choose 'Sum' in the Default aggregation
rule drop-down list.
Click OK to save the details and close the dialog.
Expand the Core\Fact - Fins - GL Other Posted Transaction\Sources\ folder and
double click the Fact_W_GL_OTHER_GRPACCT_FSCLYR_A source to display the
Logical Table Source dialog.
Display the Column Mapping tab.
Select Show unmapped columns.
Locate the Payroll Expense expression, and click the Expression Builder
button to open Expression Builder.
Use Expression Builder to specify the following SQL statement:
CASE WHEN "Oracle Data Warehouse"."Catalog"."dbo".
"Dim_W_GL_GROUP_ACCOUNT_D"."GROUP_ACCOUNT_NUM" = 'PAYROLL'
THEN "Oracle Data Warehouse"."Catalog"."dbo".
"Fact_Agg_W_GL_OTHER_GRPACCT_FSCLYR_A"."OTHER_GLOBAL1_AMT" ELSE NULL END
.
The case condition refers to the new Group Account Number 'Payroll' and uses
it as a filter.
Repeat steps d to h for each Logical Table Source. Modify the expression in
step h appropriately for each LTS by using the appropriate fact table that
corresponds to the Logical Table Source.
Steps d to h must be repeated for each Logical Table Source because in this
example, there are multiple Logical Table Sources for fact table and
aggregation tables in this logical table. Modify the expression in step h
appropriately for each Logical Table Source by using the appropriate fact
table to which it corresponds.
Save the details.
To expose the new repository objects in end users?? dashboards and reports,
drag the new objects from the Business Model and Mapping layer to an
appropriate folder in the Presentation layer.
To add a new metric in the logical table Fact ?? Fins ?? GL Balance:
Using the Administration Tool, open OracleBIAnalyticsApps.rpd.
The OracleBIAnalyticsApps.rpd file is located at:
ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_
obisn\repository
.
In the Business Model and Mapping layer:
Create a logical column named 'Payroll Expense' in logical table 'Fact ?? Fins
?? GL Balance'.
For example, right-click the Core\Fact ?? Fins ?? GL Balance object and choose
New Object, then Logical Column, to display the Logical Column dialog.
Specify Payroll Expense in the Name field.
In the Column Source tab, select Derived from existing columns using an
expression.
Click the Expression Builder button to display Expression Builder.
Use Express Builder to specify the following SQL statement:
FILTER("Core"."Fact - Fins - GL Balance"."Activity Amount" USING "Core"."Dim
- GL Account"."Group Account Number" = 'Payroll')
.
The case condition refers to the new Group Account Number 'Payroll'.
Save the details.
To expose the new repository objects in end users?? dashboards and reports,
drag the new objects from the Business Model and Mapping layer to an
appropriate folder in the Presentation layer.How to Set Up Group Account
Numbers for Oracle EBS
??? Status: Draft.
??? Bug: 15831940https://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?
rptno=15831940
??? ID=275 (Don??t forget to set OutputFileName and HelpTopicID atts to this
value).
??? Eng contacts:
??? Added by: PRB, 10 Jan, 2013
This section explains how to map Oracle General Ledger Accounts to Group
Account Numbers, and includes the following topics:
An overview of setting up Oracle General Ledger Accounts - see Section
B.2.20.1, "Overview of Mapping Oracle GL Accounts to Group Account Numbers".
A description of how to map Oracle General Ledger Accounts to Group Account
Numbers - see Section B.2.20.2, "How to Map Oracle GL Account Numbers to
Group Account Numbers".
An example that explains how to add Group Account Number metrics to the
Oracle BI Repository - see Section B.2.20.3, "Example of Adding Group Account
Number Metrics to the Oracle BI Repository".
.
Note
It is critical that the GL account numbers are mapped to the group account
numbers (or domain values) because the metrics in the GL reporting layer use
these values. For a list of domain values for GL account numbers, see Oracle
Business Analytics Warehouse Data Model Reference.
.
Overview of Mapping Oracle GL Accounts to Group Account Numbers
Group Account Number Configuration is an important step in the configuration
of Financial Analytics, because it determines the accuracy of the majority of
metrics in the General Ledger and Profitability module. Group Accounts in
combination with Financial Statement Codes are also leveraged in the GL
reconciliation process, to ensure that subledger data reconciles with GL
journal entries. This topic is discussed in more detail later in this
section.
You set up General Ledger accounts using the following configuration file
located in adaptor specific source files directory (e.g.

\SRC_FILES\EBS11510) of the physical data source that was defined as part of


Oracle BI Applications Configuration:
file_group_acct_codes_ora.csv - this file maps General Ledger accounts to
group account codes.
Before you load your data, you must ensure that the account values are mapped
consistently across these three configuration files.
You can categorize your Oracle General Ledger accounts into specific group
account numbers. The group account number is used during data extraction as
well as front-end reporting. The GROUP_ACCT_NUM field in the GL Account
dimension table W_GL_ACCOUNT_D denotes the nature of the General Ledger
accounts (for example, cash account, payroll account). For a list of the
Group Account Number domain values, see Oracle Business Analytics Warehouse
Data Model Reference. The mappings to General Ledger Accounts Numbers are
important for both Profitability analysis and General Ledger analysis (for
example, Balance Sheets, Profit and Loss, Cash Flow statements).
The logic for assigning the group accounts is located in the
file_group_acct_codes_ora.csv file. Table B??3 shows an example configuration
of the file_group_acct_codes_ora.csv file.
.
Example Configuration of file_group_acct_codes_ora.csv File
CHART OF ACCOUNTS ID FROM ACCT TO ACCT GROUP_ACCT_NUM
1 101010 101099 CA
1 131010 131939 FG INV
1 152121 152401 RM INV
1 171101 171901 WIP INV
1 173001 173001 PPE
1 240100 240120 ACC DEPCN
1 261000 261100 INT EXP
1 181011 181918 CASH
1 251100 251120 ST BORR
.
In Table B??3, in the first row, all accounts within the account number range
from 101010 to 101099 that have a Chart of Account (COA) ID equal to 1 are
assigned to Current Asset (that is, CA). Each row maps all accounts within
the specified account number range and within the given chart of account ID.
If you need to create a new group of account numbers, you can create new rows
in Oracle BI Applications Configuration Manager. You can then assign GL
accounts to the new group of account numbers in the
file_group_acct_codes_ora.csv file.
You must also add a new row in Oracle BI Applications Configuration Manager
to map Financial Statement Item codes to the respective Base Table Facts.
Table B??4 shows the Financial Statement Item codes to which Group Account
Numbers must map, and their associated base fact tables.
.
Financial Statement Item Codes and Associated Base Fact Tables
Financial Statement Item Codes Base Fact Tables
AP AP base fact (W_AP_XACT_F)
AR AR base fact (W_AR_XACT_F)
COGS Cost of Goods Sold base fact (W_GL_COGS_F)
REVENUE Revenue base fact (W_GL_REVN_F)
TAX Tax base fact (W_TAX_XACT_F)
OTHERS GL Journal base fact (W_GL_OTHER_F)
.
By mapping your GL accounts against the group account numbers and then
associating the group account number to a Financial Statement Item code, you
have indirectly associated the GL account numbers to Financial Statement Item
codes as well. This association is important to perform GL reconciliation and
to ensure the subledger data reconciles with GL journal entries. It is
possible that after an invoice has been transferred to GL, a GL user might
adjust that invoice in GL. In this scenario, it is important to ensure that
the adjustment amount is reflected in the subledger base fact as well as
balance tables. To determine such subledger transactions in GL, the
reconciliation process uses Financial Statement Item codes.
Financial Statement Item codes are internal codes used by the ETL process to
process the GL journal records during the GL reconciliation process against
the subledgers. When the ETL process reconciles a GL journal record, it looks
at the Financial Statement Item code associated with the GL account that the
journal is charging against, and then uses the value of the Financial
Statement item code to decide which base fact the GL journal should reconcile
against. For example, when processing a GL journal that charges to a GL
account which is associate to 'AP' Financial Statement Item code, then the
ETL process will try to go against AP base fact table (W_AP_XACT_F), and try
to locate the corresponding matching AP accounting entry. If that GL account
is associated with the 'REVENUE' Financial Statement Item code, then the ETL
program will try to go against the Revenue base fact table (W_GL_REVN_F), and
try to locate the corresponding matching Revenue accounting entry.
How to Map Oracle GL Account Numbers to Group Account Numbers
This section explains how to map Oracle General Ledger Account Numbers to
Group Account Numbers.
.
Note
If you add new Group Account Numbers to the file_group_acct_codes_ora.csv
file, you must also add metrics to the Oracle BI repository. See Section
B.2.20.3, "Example of Adding Group Account Number Metrics to the Oracle BI
Repository" for more information.
.
To map Oracle GL account numbers to group account numbers:
Open the file_group_acct_codes_ora.csv file with a text editor in the
$PMServer\SrcFiles directory (for example,
\SRC_FILES\EBS11510).
For each Oracle GL account number that you want to map, create a new row in
the file containing the following fields:
.
Field Name Description
CHART OF ACCOUNTS ID The ID of the GL chart of account.
FROM ACCT The lower limit of the natural account range. This is based on the
natural account segment of your GL accounts.
TO ACCT The higher limit of the natural account range. This is based on the
natural account segment of your GL accounts.
GROUP_ACCT_NUM This field denotes the group account number of the Oracle
General Ledger account, as specified in the file_group_acct_names.csv file.
For example, 'AP' for Accounts Payables, 'CASH' for cash account, 'GEN
PAYROLL' for payroll account, and so on.
.
For example:
101, 1110, 1110, CASH
101, 1210, 1210, AR
101, 1220, 1220, AR
.
Note
You can optionally remove the unused rows from the CSV file.
.
Ensure that the values that you specify in the file_group_acct_codes_ora.csv
file are consistent with the values that are specified in Oracle BI
Applications Configuration Manager for Group Accounts.
See Figure B??2, "Configuration Files for Configuring Group Accounts for
Oracle EBS" for an example.
Save and close the CSV file.
Example of Adding Group Account Number Metrics to the Oracle BI Repository
If you add new Group Account Numbers to the file_group_acct_codes_ora.csv
file (as described in Section B.2.20.2, "How to Map Oracle GL Account Numbers
to Group Account Numbers"), you must also add metrics to the Oracle BI
repository to expose the new Group Account Numbers. This example illustrates
how you can add Group Account Number metrics using the Oracle BI
Administration Tool.
This example assumes that you have a new Group Account Number called
'Payroll', and you want to add a new metric to the Presentation layer called
'Payroll Expense'.
To add a new metric in the logical table Fact ?? Fins ?? GL Other Posted
Transaction:
Using the Administration Tool, open OracleBIAnalyticsApps.rpd.
The OracleBIAnalyticsApps.rpd file is located at:
ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_
obisn\repository
.
In the Business Model and Mapping layer:
Create a logical column named 'Payroll Expense' in the logical table 'Fact ??
Fins ?? GL Other Posted Transaction'.
For example, right-click the Core\Fact - Fins - GL Other Posted Transaction\
object and choose New Object, then Logical Column, to display the Logical
Column dialog. Specify Payroll Expense in the Name field.
Display the Aggregation tab, and then choose 'Sum' in the Default aggregation
rule drop-down list.
Click OK to save the details and close the dialog.
Expand the Core\Fact - Fins - GL Other Posted Transaction\Sources\ folder and
double click the Fact_W_GL_OTHER_GRPACCT_FSCLYR_A source to display the
Logical Table Source dialog.
Display the Column Mapping tab.
Select Show unmapped columns.
Locate the Payroll Expense expression, and click the Expression Builder
button to open Expression Builder.
Use Expression Builder to specify the following SQL statement:
CASE WHEN "Oracle Data Warehouse"."Catalog"."dbo".
"Dim_W_GL_GROUP_ACCOUNT_D"."GROUP_ACCOUNT_NUM" = 'PAYROLL'
THEN "Oracle Data Warehouse"."Catalog"."dbo".
"Fact_Agg_W_GL_OTHER_GRPACCT_FSCLYR_A"."OTHER_GLOBAL1_AMT" ELSE NULL END
.
The case condition refers to the new Group Account Number 'Payroll' and uses
it as a filter.
Repeat steps d to h for each Logical Table Source. Modify the expression in
step h appropriately for each LTS by using the appropriate fact table that
corresponds to the Logical Table Source.
Steps d to h must be repeated for each Logical Table Source because in this
example, there are multiple Logical Table Sources for fact table and
aggregation tables in this logical table. Modify the expression in step h
appropriately for each Logical Table Source by using the appropriate fact
table to which it corresponds.
Save the details.
To expose the new repository objects in end users?? dashboards and reports,
drag the new objects from the Business Model and Mapping layer to an
appropriate folder in the Presentation layer.
To add a new metric in the logical table Fact ?? Fins ?? GL Balance:
Using the Administration Tool, open OracleBIAnalyticsApps.rpd.
The OracleBIAnalyticsApps.rpd file is located at:
ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_
obisn\repository
.
In the Business Model and Mapping layer:
Create a logical column named 'Payroll Expense' in logical table 'Fact ?? Fins
?? GL Balance'.
For example, right-click the Core\Fact ?? Fins ?? GL Balance object and choose
New Object, then Logical Column, to display the Logical Column dialog.
Specify Payroll Expense in the Name field.
In the Column Source tab, select Derived from existing columns using an
expression.
Click the Expression Builder button to display Expression Builder.
Use Express Builder to specify the following SQL statement:
FILTER("Core"."Fact - Fins - GL Balance"."Activity Amount" USING "Core"."Dim
- GL Account"."Group Account Number" = 'Payroll')
.
The case condition refers to the new Group Account Number 'Payroll'.
Save the details.
To expose the new repository objects in end users?? dashboards and reports,
drag the new objects from the Business Model and Mapping layer to an
appropriate folder in the Presentation layer.
Best Regards
Sruthi Jyesta
o Like Show 0 Likes(0)

o Reply
o Actions
3. Re: Group Account Configuration - OBIA 11.1.1.7.1

VenkatGal Jan 7, 2014 10:24 AM (in response to Ian Bristow-Oracle)


Hi Ian,
You should be able to search for that tech note on support portal using 'Related Bug
Number: 9202898'

Let me know if there exists one equivalent tech note for ODI based OBIA 11.1.1.7.1

Thanks
Venkat G
o Like Show 0 Likes(0)

o Reply
o Actions
4. Re: Group Account Configuration - OBIA 11.1.1.7.1

Ian Bristow-Oracle Jan 8, 2014 3:10 AM (in response to VenkatGal)


Venkat,
I presume you mean note 1409595.1 - OBIA: How to Create Group Accounts Based On
More Than One Segment? If so, I'm not aware of anything like this for ODI. Did
Sruthi's post help at all?

Regards,
Ian Bristow
o Like Show 0 Likes(0)

o Reply
o Actions
5. Re: Group Account Configuration - OBIA 11.1.1.7.1

megamalex1 Mar 28, 2014 3:17 PM (in response to Ian Bristow-Oracle)


Hi Venkat,

I made the following post which is similar to yours just now -

BIApps 11.1.1.7.1 Domain Mapping Group Accounts to Financial Statement Item

Did you query the domain mapping at all. As far as I see things at the moment in my
Financial Analytics environment I cannot see any mapping between Group Accounts to
Financial Statement Items I can however when I look in the database e.g. [PREFIX]_DW
schema

e.g.

SELECT COUNT(*) FROM W_DOMAIN_MEMBER_MAP_G WHERE TRG_DOMAIN_CODE LIKE


'W_FIN_STMT'

Returns 47 rows - I just cannot see them through Configuration Manger

Do you have the same problem?