| Oracle® Business Intelligence Applications Installation and Configuration Guide for Oracle Data Integrator Users Version 7.9.5.2 Part Number E13669-01 |
|
|
View PDF |
| Oracle® Business Intelligence Applications Installation and Configuration Guide for Oracle Data Integrator Users Version 7.9.5.2 Part Number E13669-01 |
|
|
View PDF |
This chapter describes how to configure Oracle Financial Analytics for particular sources to meet your business needs, and contains the following topics:
To find out about other possible tasks required to deploy Oracle Business Intelligence Applications, see Section 2.4, "Roadmap To Installing, Configuring, and Customizing Oracle Business Intelligence Applications With ODI".
Oracle Financial Analytics consists of the following:
Oracle General Ledger and Profitability Analytics. The General Ledger Analytics application provides information to support your enterprise's balance sheet and provides a detailed analysis on the overall health of your company. The default configuration for the General Ledger Analytics application is based on what is identified as the most-common level of detail or granularity. However, you can configure and modify the extracts to best meet your business requirements.
The Profitability Analytics application provides cost analysis, revenue trends, and sales performance to provide an accurate picture of profit and loss. The information found in the Profitability Analytics application pertains to data found in the revenue and expense account groupings of your financial statements and chart of accounts. The Profitability Analytics application is designed to provide insight into your enterprise's revenue and profitability information, which ties into your accounts receivable. The default configuration for the Profitability Analytics application is based on what is identified as the most-common level of detail, or granularity. However, the extracts are configurable and you can modify the extracts to meet your business requirements. The Profitability Analytics application provides cost analysis, revenue trends, and profitability analysis at the products and customer level, and the income statement at the company and business divisions level.
Oracle Payables Analytics. The Oracle Payables Analytics application provides information about your enterprise's accounts payable information and identifies the cash requirements to meet your obligations.
The information found in the Oracle Payables Analytics application pertains to data found exclusively under Accounts Payable (AP) in your financial statements and chart of accounts. Analysis of your payables allows you to evaluate the efficiency of your cash outflows. The need for analysis is increasingly important because suppliers are becoming strategic business partners with the focus on increased efficiency for just in time, and quality purchasing relationships.
The default configuration for the Oracle Payables Analytics application is based on what is identified as the most- common level of detail, or granularity. However, you can configure or modify the extracts to best meet your business requirements.
Oracle Receivables Analytics. The Oracle Receivables Analytics application provides information to support your credit and collection activities, and to monitor and identify potential, receivables problems.
The information found in the Oracle Receivables Analytics application pertains to data found exclusively in the Accounts Receivable (AR) account grouping of your financial statements and chart of accounts. Each day that your receivables are past the due date represents a significant, opportunity-cost to your company. Keeping a close eye on the trends, and clearing of AR is one way to assess the efficiency of your sales operations, the quality of your receivables, and the value of key customers.
The default configuration for the Oracle Receivables Analytics application is based on what is identified as the most-common level of detail or granularity. However, you may configure and modify the extracts to best meet your business requirements.
This section contains configuration steps that you need to perform on Oracle Financial Analytics before you do a full data load, and contains the following topics:
Section 7.2.3, "How to Specify the Ledger or Set of Books for which GL Data is Extracted"
Section 7.2.4, "Configuration Steps for Controlling Your Data Set"
If you modify or extend a seeded list of values, you must configure the CSV files for Oracle Financial Analytics by mapping values from your source systems to the domain values.
The following sections explain how to extract the lists of values from your source system, which you then compare with the seeded values. If the lists of values are different to the seeded values, you need to follow the instructions to configure the Domain Values and CSV Worksheet Files.
Typically, the number of rows returned by the source system will not match the number of rows provided in the domain valuesXXX.csv files. If so, you need to delete extra rows or insert additional rows in the CSV file to accommodate all the values returned by the source system in context.
The table below lists the CSV worksheet files and the domain values for Financial Analytics and Oracle EBS in the $ODI_HOME\biapps_odi\odifiles\odidatafiles\lkpfiles folder.
Table 7-1 Domain Values and CSV Worksheet Files for Oracle Financial Analytics and Oracle EBS
| Worksheet File Name | Description | Package/Interface |
|---|---|---|
|
domainValues_Xact_Types_DocTypes_ora11i.csv |
List the Transaction types and the corresponding domain values for the Oracle EBS 11i application. For more information about updating the values in this file, see Section 7.2.2, "How to configure domainValues_Xact_Types_DocTypes_ora11i.csv for Oracle General Ledger and Profitability Analytics"). |
SDE_ORA_TransactionTypeDimension_GLCOGSDerive |
This section explains how to configure domainValues_Xact_Types_DocTypes_ora11i.csv for Oracle General Ledger and Profitability Analytics, Release 11i.
To configure domainValues_Xact_Types_DocTypes_ora11i.csv for Oracle General Ledger and Profitability Analytics:
Identify the Entry Types in your Oracle Inventory Application by using the following SQL:
select mtt.transaction_type_id, mtt.description from mtl_transaction_types mtt;
This query gives the transaction type codes in your Oracle Inventory Application and their corresponding descriptions. Oracle Inventory Application is a data source from which Oracle General Ledger and Profitability Analytics extract data.
Open the domainValues_Xact_Types_DocTypes_ora11i.csv file in a text editor.
This file is located in the $ODI_HOME\biapps_odi\odifiles\odidatafiles\lkpfiles directory.
Look for only the rows in the file which has xact_cat_code = 'COGS'. From among these records, look for those with W_XACT_TYPE_CODE = 'DELIVERY' or 'RETURN'. The column XACT_TYPE_CODE will contain the entry type codes from Oracle Inventory application, and the column W_XACT_TYPE_CODE is the corresponding domain value to which this entry type code will be mapped to.
Map the entry type codes returned by the query above from your Oracle Inventory Application to the domain values.
Make sure the entry type codes go into the XACT_TYPE_CODE column in the file. Note that it is not necessarily a one-to-one mapping between the domain values and the entry types. For example, you can have multiple entry types mapped into the DELIVERY/RETURN domain value. Be careful not to map the same entry type to two different domain values.
Save and close the file.
If you have an Oracle EBS source system, you can specify from which set of books or ledgers you extract the GL data.
Oracle Business Intelligence Applications enables you to configure:
The list of ledgers or set of books from which to extract the GL data.
The types of ledgers or set of books for which to extract the GL data for.
You can use either of these configuration points separately and combine them. When installed out-of-the-box, Oracle Business Intelligence Applications extract all GL data for all ledgers or set of books.
For Oracle 11i customers, to configure the list of set of books to extract the GL data for, do the following:
Start Oracle BI Applications Configuration Manager (for more information, see Section 4.5.8.9, "How to Login to Oracle BI Applications Configuration Manager Using A Connection").
Select the Administer ELT Parameters link.
Display the Application Specific tab, and select Financial Analytics from the Select BI Application field.
Locate the following parameters and use the Parameter Value field to set the value:
FILTER_BY_SET_OF_BOOKS_TYPE
Set the value to 'Yes'.
SET_OF_BOOKS_ID_LIST
Enter the IDs of the set of books for which you want to extract GL data for.
Specify the list of set of book IDs separated by commas (do not specify single or double quotes).
For example, if you want to extract GL data for set of books with IDs: 101, 207, and 303, then set the value of this parameter to the following:
101, 207, 303
Save your changes.
For more information about specifying parameter values, see Section 4.6.3.3.1, "How to Set E-LT Parameters In Oracle BI Applications Configuration Manager".
You can also specify the Set of Books type you want to extract GL data for. In Oracle 11i, there are three set of books types (this is based on the column GL_SETS_OF_BOOKS.mrc_sob_type_code column):
P (Parent)
R (Reporting)
N (None)
For Oracle 11i customers, to configure the types of set of books to extract the GL data, do the following:
Start Oracle BI Applications Configuration Manager (for more information, see Section 4.5.8.9, "How to Login to Oracle BI Applications Configuration Manager Using A Connection").
Select the Administer ELT Parameters link.
Display the Application Specific tab, and select Financial Analytics from the Select BI Application field.
Locate the following parameters and use the Parameter Value field to set the value:
FILTER_BY_SET_OF_BOOKS_TYPE
Set the value to 'Yes'.
SET_OF_BOOKS_TYPE_LIST
Enter the types of set of books for which you want to extract GL data for.
Specify the list of set of book IDs in single quotes and separated by commas.
For example, if you want to extract GL data for all Parent set of books and all Reporting set of books, then set the value of this parameter as follows:
'P', 'R'
Save your changes.
For more information about specifying parameter values, see Section 4.6.3.3.1, "How to Set E-LT Parameters In Oracle BI Applications Configuration Manager".
This section contains additional configuration steps for Oracle Financial Analytics, and contains the following topics:
Section 7.2.4.1, "How to include UnApplied Payments in AR Aging Calculations"
Section 7.2.4.3, "How to Configure How GL Balances Is Populated in Oracle EBS"
Section 7.2.4.4, "How to Configure Oracle Profitability Analytics Transaction Extracts"
Section 7.2.4.5, "How to Configure Cost Of Goods Extract (Oracle EBS 11i-specific)"
Section 7.2.4.6, "How to Configure AP Balance ID for Oracle Payables Analytics"
Section 7.2.4.8, "How to Configure the AR Adjustments Extract for Oracle Receivables Analytics"
Section 7.2.4.9, "How to Configure the AR Schedules Extract"
Section 7.2.4.12, "How to Setup Drill Down in Oracle BI Answers from General Ledger to Sub-ledger"
To include UnApplied Payments in Aging Calculations for AR Aging tables
In ODI Designer, open the package PLP_ARSnapshotInvoiceAging in the PLP folder.
Open the Interface prep SQ_IA_AR_XACTS.
Display the Diagram tab and locate the table W_XACT_TYPE_D.
Selects the filter on the W_XACT_SUBTYPE_CODE column.
Change the SQL to the following:
W_XACT_TYPE_D.W_XACT_SUBTYPE_CODE IN ('INVOICE','CR MEMO','DR MEMO', 'PAYMENT')
Save the changes.
Regenerate the scenario of this package (expand the scenario folder under this package, right click the scenario and choose regenerate, keeping all the parameters as default).
The next E-LT will populate the Aging tables using UnApplied payments in the calculations.
This section explains how to control the lengths of the aging buckets in the AP and AR aging snapshot tables. These tables are:
W_AP_AGING_INVOICE_A
W_AR_AGING_INVOICE_A
W_AP_AGING_SUPPLIER_A
W_AR_AGING_CUSTOMER_A
In these four tables, outstanding AP/AR balance information is broken out into rows. Each row represents the outstanding balance information for a particular aging bucket. Four aging buckets are provided out-of-the-box, with the following durations:
Bucket 1: 0 – 30 days
Bucket 2: 31 – 60 days
Bucket 3: 61 – 90 days
Bucket 4: 90+ days
To configure the length of aging buckets:
Start Oracle BI Applications Configuration Manager (for more information, see Section 4.5.8.9, "How to Login to Oracle BI Applications Configuration Manager Using A Connection").
Select the Administer ELT Parameters link.
Display the Application Specific tab, and select Financial Analytics from the Select BI Application field.
Locate the following parameters and use the Parameter Value field to set the following values:
BUCKET1_START and BUCKET1_END
BUCKET2_START and BUCKET2_END
BUCKET3_START and BUCKET3_END
BUCKET4_START and BUCKET4_END
Save your changes.
For more information about specifying parameter values, see Section 4.6.3.3.1, "How to Set E-LT Parameters In Oracle BI Applications Configuration Manager".
These aging tables are snapshot tables. You can also control how many historic month end snapshots you want to keep in these tables (the default value is 24 months). You can increase or decrease the number by adjusting the $$HISTORY_MONTHS parameter.
To populate the GL balances (stored in the W_GL_BALANCE_F table), you can either extract them directly from Oracle General Ledger, or calculate them based on the records in the W_GL_OTHER_F table (which stores all journal lines).
To configure how GL balances is populated in Oracle EBS:
Start Oracle BI Applications Configuration Manager (for more information, see Section 4.5.8.9, "How to Login to Oracle BI Applications Configuration Manager Using A Connection").
Select the Administer ELT Parameters link.
Display the Global tab.
Locate the following parameters and use the Parameter Value field to set the values:
To extract the GL balances directly from Oracle General Ledger:
Set 'LOAD_EXTRACT_GL_BALANCE' to Y.
Set 'LOAD_CALCULATE_GL_BALANCE' to N.
To calculate GL balances based on the records in the W_GL_OTHER_F table:
Set 'LOAD_EXTRACT_GL_BALANCE' to N.
Set 'LOAD_CALCULATE_GL_BALANCE' to Y.
Save your changes.
For more information about specifying parameter values, see Section 4.6.3.3.1, "How to Set E-LT Parameters In Oracle BI Applications Configuration Manager".
There are two separate transaction extracts for Oracle General Ledger and Profitability Analytics—General Ledger Revenue and General Ledger COGS. By default, the Oracle General Ledger Analytics application extracts only Completed revenue and COGS that have been posted to the general ledger. Completed revenue transactions are those where the RA_CUSTOMER_TRX_ALL.COMPLETE_FLAG = Y. If you want to extract incomplete revenue transactions, you can remove the filter in the extraction Interface.
To modify the extract filter for Oracle General Ledger and Profitability Analytics Revenue:
In ODI Designer, open the appropriate Oracle Applications folder (for example, SDE_ORA11510_Adaptor).
Open the Package mplt_BC_ORA_GLRevenueFact.
Edit the Interface Prep SQ_GL_REVENUE_EXTRACT.
Display the Diagram tab.
Locate the source table 'RA_CUSTOMER_TRX_ALL' and delete its filter (with the value RA_CUSTOMER_TRX_ALL.COMPLETE_FLAG='Y').
Save your changes.
Repeat steps 3 to 6 for the Interface Prep SQ_GL_REVENUE_EXTRACT_FULL.
Re-generate the scenario of this package (expand the scenario folder under this package, right click the scenario and choose regenerate, keep all the parameters as default).
For customers of EBS 11i, 11.5.8, 11.5.9, and 11.5.10, the Oracle General Ledger Analytics application extracts only COGS transactions that have been posted to the General Ledger, by default. All COGS transactions that have been transferred satisfy the following condition— MTL_TRANSACTION_ACCOUNTS.GL_BATCH_ID <> -1. If you want to extract all transactions, you can remove the filter in the extraction Interfaces. You need to modify the extraction interfaces for both the regular extract package as well as the primary extract package. This does not apply to EBS R12, in which by default all transactions are extracted. The following section applies only to EBS 11i customers.
To modify the extract filter for General Ledger COGS:
In ODI Designer, open the appropriate Oracle Applications folder (for example, SDE_ORA11510_Adaptor).
Open the Package SDE_ORA_GLCOGSFact.
Edit the Interface Prep SQ_MTL_TRANSACTION_ACCOUNTS.
Display the Diagram tab.
Locate the source table Find source table 'RA_CUSTOMER_TRX_ALL' and delete its filter (with the value MTL_TRANSACTION_ACCOUNTS.GL_BATCH_ID<>-1).
Save your changes.
Repeat steps 3 to 6 for the Interface Prep SQ_MTL_TRANSACTION_ACCOUNTS_FU.
Re-generate the scenario of this package (expand the scenario folder under this package, right click the scenario and choose regenerate, keep all the parameters as default).
Open the Package SDE_ORA_GLCOGSFact_Primary.
Edit the Interface Prep SQ_MTL_TRANSACTION_ACCOUNTS_PR.
Display the Diagram tab.
Locate the source table 'RA_CUSTOMER_TRX_ALL' and delete its filter (with the value MTL_TRANSACTION_ACCOUNTS.GL_BATCH_ID<>-1).
Save your changes.
Re-generate the scenario of this package (expand the scenario folder under this package, right click the scenario and choose regenerate, keep all the parameters as default).
The AP Balance ID controls the level at which the balance in W_AP_BALANCE_F is maintained.
This section contains configuration information for Oracle Payables Analytics that is specific to Oracle.
By default, the Accounts Payable (AP) Balance ID is maintained at the following granularity:
SET_OF_BOOKS_ID||'~'||CODE_COMBINATION_ID||'~'||VENDOR_SITE_ID||'~'||INP_ORG_ID
However, if you want to maintain your AP balance at a different grain, you can redefine the Balance ID value in the applicable packages.
To modify the Accounts Payable Balance ID:
Note:
To modify the Accounts Payable Balance ID, you must modify the following packages:SDE_ORA_APTransactionFact_LiabilityDistribution
SDE_ORA_APTransactionFact_ExpenseDistribution
SDE_ORA_APTransactionFact_Payment
SDE_ORA_APTransactionFact_PaymentSchedule
SDE_ORA_Stage_APTransactionFact_DiffManDerive
In ODI Designer, open the appropriate Oracle Applications folder (for example, SDE_ORA11510_Adaptor).
Open the appropriate Package SDE_ORA_ARTransactionFact_Adjustments, and display the Diagram tab.
Edit the Interface at the end of the flow (for example, Run AR_XACT_FS).
Display the Diagram tab.
On the right of the pane, you will see the 'Target Datastore' panel with the column definition of the target table (e.g. W_AR_XACT_FS).
Select BALANCE_ID, and change the expression in the text editor in the lower pane.
Save your changes.
In the same package, make the same change for the full load interface.
For example, the full load interface for the Run AR_XACT_FS package is Run AR_XACT_FS_Full.
Re-generate the scenario of this package (expand the scenario folder under this package, right click the scenario and choose regenerate, keep all the parameters as default).
Repeat steps 1 to 8 for each of the packages listed above.
The AR Balance ID controls the level at which the balance in W_AR_BALANCE_F is maintained.
By default, the AR Balance ID is maintained at the following granularity:
set_of_books_id || '~' || code_combination_id || '~' || customer_id || '~' || customer_site_use_id || '~' ||transaction_currency_code || '~' || org_id
However, if you want to maintain your AR balance at a different grain, you can redefine the Balance ID value in the applicable packages.
To modify the AR Balance ID:
Note:
To modify the AR Balance ID, you must modify the following packages:SDE_ORA_ARTransactionFact_Adjust
SDE_ORA_ARTransactionFact_ARScheduleDerive
SDE_ORA_ARTransactionFact_CreditMemoApplication
SDE_ORA_ARTransactionFact_ReceivableApplication
SDE_ORA_Stage_ARTransactionFact_DiffManDerive
In ODI Designer, open the appropriate Oracle Applications folder (for example, SDE_ORA11510_Adaptor).
Open the appropriate Package SDE_ORA_APTransactionFact_LiabilityDistribution, and display the Diagram tab.
Edit the Interface at the end of the flow (for example, Run AP_XACT_FS).
Display the Diagram tab.
On the right of the pane, you will see the 'Target Datastore' panel with the column definition of the target table (e.g. W_AP_XACT_FS).
Select BALANCE_ID, and change the expression in the text editor in the lower pane.
Save your changes.
In the same package, make the same change for the full load interface.
For example, the full load interface for the Run AP_XACT_FS package is Run AP_XACT_FS_Full.
Re-generate the scenario of this package (expand the scenario folder under this package, right click the scenario and choose regenerate, keep all the parameters as default).
Repeat steps 1 to 8 for each of the packages listed above.
By default, Oracle Receivables Analytics extracts only approved adjustment entries against accounts receivable transactions. Approved adjustments are entries where the AR_ADJUSTMENTS_ALL.STATUS = A. If you want to extract additional types of AR adjustment entries, you can remove the filter in the extraction interface. By modifying or removing the filter, you can extract other entries, such as those that require more research, those that are rejected, or those that are not accrued charges.
To modify the extract filter for Accounts Receivable adjustments:
In ODI Designer, open the appropriate Oracle Applications folder (for example, SDE_ORA11510_Adaptor).
Open the Package SDE_ORA_ARTransactionFact_Adjustments.
Edit the Interface Prep SQ_AR_XACTS_ADJ.
Display the Diagram tab.
Locate the source table ADJUSTMENTS_ALL.
Select the filter on this source table with the value AR_ADJUSTMENTS_ALL.STATUS='A' to display the 'Filter on datastore <Name>' pane, and remove or modify the filter value in the Implementation box.
Save your changes.
Repeat steps 3 to 7 for the Interface Prep SQ_AR_XACTS_ADJ_Full.
Re-generate the scenario of this package (expand the scenario folder under this package, right click the scenario and choose regenerate, keep all the parameters as default).
Repeat steps 1 to 8 for the Package SDE_ORA_ARTransactionFact_Adjustments_Primary.
By default, Oracle Receivables Analytics extracts only completed schedules; that is, transactions where the RA_CUSTOMER_TRX_ALL.COMPLETE_FLAG(+) = Y. If you want to extract additional types of AR schedule entries, you must remove the filter in the extraction interface. By modifying or removing the filter, you can extract other entries, such as those that were marked as incomplete.
To modify the extract filter for Accounts Receivable schedules:
In ODI Designer, open the appropriate Oracle Applications folder (for example, SDE_ORA11510_Adaptor).
Open the Package SDE_ORA_Stage_ARTransactionFact_ARSchedules.
Edit the Interface Prep SQ_AR_XACTS_AR_SCH.
Display the Diagram tab.
Locate the source table RA_CUSTOMER_TRX_ALL.
Select the filter on this source table with the value RA_CUSTOMER_TRX_ALL.COMPLETE_FLAG(+)='Y' to display the 'Filter on datastore <Name>' pane, and remove or modify the filter value in the Implementation box.
Save your changes.
Repeat steps 3 to 7 for the Interface Prep SQ_AR_XACTS_AR_SCH_Full.
Re-generate the scenario of this package (expand the scenario folder under this package, right click the scenario and choose regenerate, keep all the parameters as default).
By default, Oracle Receivables Analytics extracts only confirmed, cash-receipt application entries against accounts receivable transactions. Confirmed receipts are entries where the AR_RECEIVABLE_APPLICATIONS_ALL.CONFIRMED_FLAG = Y OR NULL. If you want to extract additional types of cash-receipt application entries, you can remove the filter in the extraction interface. By modifying or removing the filter, you can extract other entries, such as unconfirmed applications.
You must modify both the regular package(SDE_ORA_ARTransactionFact_ReceivableApplication) as well as the primary extract package(SDE_ORA_ARTransactionFact_ReceivableApplication_Primary).
To modify the extract filter for AR cash receipt application:
In ODI Designer, open the appropriate Oracle Applications folder (for example, SDE_ORA11510_Adaptor).
Open the Package SDE_ORA_ARTransactionFact_ReceivableApplication.
Edit the Interface Prep SQ_AR_XACTS_APPREC.
Display the Diagram tab.
Locate the source table AR_RECEIVABLE_APPLICATIONS_ALL.
Select the filter on this source table with the value NVL(AR_RECEIVABLE_APPLICATIONS_ALL.CONFIRMED_FLAG,'Y')='Y' to display the 'Filter on datastore <Name>' pane, and remove or modify the filter value in the Implementation box.
Save your changes.
Repeat steps 3 to 7 for the Interface Prep SQ_AR_XACTS_APPREC_Full.
Re-generate the scenario of this package (expand the scenario folder under this package, right click the scenario and choose regenerate, keep all the parameters as default).
Repeat steps 1 to 8 for the Package SDE_ORA_ARTransactionFact_ReceivableApplication_Primary.
By default, Oracle Receivables Analytics extracts only confirmed, credit-memo application entries against accounts receivable transactions. Confirmed credit memos are entries where the AR_RECEIVABLE_APPLICATIONS_ALL.CONFIRMED_FLAG = Y OR NULL. If you want to extract additional types of AR credit-memo application entries, you can remove the filter. By modifying or removing the filter, you can extract other entries such as unconfirmed, credit memos.
You must modify both the regular package SDE_ORA_ARTransactionFact_CreditmemoApplication as well as the primary extract package SDE_ORA_ARTransactionFact_CreditmemoApplication.
To modify the extract filter for AR cash receipt application:
In ODI Designer, open the appropriate Oracle Applications folder (for example, SDE_ORA11510_Adaptor).
Open the Package SDE_ORA_ARTransactionFact_ CreditmemoApplication.
Edit the Interface Prep SQ_AR_XACTS_APPCM.
Display the Diagram tab.
Locate the source table AR_RECEIVABLE_APPLICATIONS_ALL.
Select the filter on this source table with the value NVL(AR_RECEIVABLE_APPLICATIONS_ALL.CONFIRMED_FLAG,'Y')='Y' to display the 'Filter on datastore <Name>' pane, and remove or modify the filter value in the Implementation box.
Save your changes.
Repeat steps 3 to 7 for the Interface Prep SQ_AR_XACTS_APPCM_Full.
Re-generate the scenario of this package (expand the scenario folder under this package, right click the scenario and choose regenerate, keep all the parameters as default).
Repeat steps 1 to 8 for the Package SDE_ORA_ARTransactionFact_ReceivableApplication_Primary.
Oracle Business Intelligence Applications enables you to trace a GL Journal to the Sub-ledger transaction that created that journal. This ability (using drill down) is achieved through the Navigation feature in Oracle BI Answers. This feature is available for AP if the source is Oracle EBS 11i.
To set up drill down in Oracle BI Answers from General Ledger to Sub-ledger:
Create your sub-ledger request from 'Financials - AP Transactions' or 'Financials - AR Transactions' catalog as applicable.
In your request, add a filter on the column 'GL Journal ID' under the 'Document Details' folder and the set the operator of the filter to 'Is Prompted'.
Build your GL Journal request from the 'Financials - GL Detail Transactions' catalog.
To your request, add the column 'GL Journal ID' under the 'Document Details' folder.
Navigate to the Column Properties of this column, and set the Value Interaction property in the Column Format tab to 'Navigate'.
Add a navigation target and set the target location to the sub-ledger request you created earlier.
|
 Copyright © 2009, Oracle. All rights reserved. Legal Notices |
|