Oracle^® Business Intelligence Applications Installation and Configuration Guide > Checklist for Configuring Oracle Business Analytics Warehouse Applications >

Checklist for Configuring Oracle Financial Analytics

This section contains the mandatory and optional configuration points for the Financial applications for Oracle 11i and PeopleSoft 8.4. The Financial applications consist of Oracle General Ledger and Profitability Analytics, Oracle Payables Analytics, Oracle Receivables Analytics, and Oracle General Ledger and Profitability Analytics.

Checklist for Configuring Oracle Financial Analytics for Oracle 11i

This section contains the configuration points for Oracle Financial Analytics applications that are specific to Oracle 11i.

The following section contains mandatory configuration points for Oracle Financial Analytics:

• Extracting Data Posted at the Detail-Level. By default, the Oracle Business Analytics Warehouse assumes that the posting from your journal to your General Ledger is done at summary level and that references are maintained in the General Ledger for AP and AR subledgers. Configuration is required if import references are not maintained in the General Ledger and the posting from subledgers is at the detail level. For more information on extracting data posted at the detail-level, see Extracting Data Posted at the Detail-Level for Oracle 11i.
• Mapping General Ledger Analytics account numbers to group account numbers. You need to map General Ledger Analytics account numbers to group account numbers. For more information on mapping General Ledger accounts numbers to group account number, see Mapping Oracle General Ledger and Profitability Analytics Account Numbers to Group Account Numbers.

The following section contains optional configuration points for Oracle Financial Analytics:

• Configuring the Set of Books ID. By default, the Oracle Business Analytics Warehouse extracts data for all set of books. Configuration is required to extract data for a certain set of books only.
• Configuring posted or unposted transactions. By default, Oracle Business Analytics Warehouse extracts posted transactions. You can configure the Oracle Business Analytics Warehouse to extract unposted transactions as well as posted transactions.
• Configuring General Ledger account hierarchies. Additional configuration is required to make sure the General Ledger hierarchical information is correct and to load the W_HIERARCHIES table.
• Configuring the General Ledger Balance ID. By default, the General Ledger Balance ID is maintained at the Set of Books and GL Code Combination ID level. If you want to maintain your General Ledger Balance at a different grain, you can redefine the GL Balance ID.
• Configuring the AP Balance ID. If you want to maintain your AP balance at a different grain, you can redefine the Balance ID value in the applicable mapplets.
• Configuring the AR Balance ID. If you want to maintain your AR balance at a different grain, you can redefine the Balance ID value in the applicable mapplets.
• Configuring the AR Adjustments Extract. If you want to extract additional types of AR adjustment entries, you can remove the filter in the Business Component mapplet. For more information on configuring the AR adjustments extract, see Configuring the AR Adjustments Extract for Oracle Receivables Analytics.
• Configuring the AR Schedules Extract. If you want to extract additional types of AR schedule entries, you must remove the filter in the Business Component mapplet. For more information on configuring the AR schedules extract, see Configuring the AR Schedules Extract.
• Configuring the AR Cash Receipt Application Extract. If you want to extract additional types of cash-receipt application entries, you can remove the filter in the Business Component mapplet. For more information on configuring the AR receipt application extract, see Configuring the AR Cash Receipt Application Extract for Oracle Receivables Analytics.
• Configuring the AR Credit-Memo Application Extract. If you want to extract additional types of credit-memo application entries, you can remove the filter. For more information on configuring the AR receipt application extract, see Configuring the AR Credit-Memo Application Extract for Oracle's Siebel Receivables Analytics.
• Configuring the Customer Costs and Product Costs Fact Tables. In Oracle General Ledger and Profitability Analytics, the Customer Costs and Product Costs fact tables store the costing and expenses for the Profitability functional area. You need to use these tables with General Ledger Revenue and General Ledger COGS fact tables. For more information on configuring the Customer Costs and Product Costs Fact Tables, see Configuring the Customer Costs Lines and Product Costs Lines Tables for Oracle's Siebel Profitability Analytics.

Checklist for Configuring Oracle Financial Analytics for PeopleSoft 8.4

This section contains the configuration points for Oracle Financial Analytics that are specific to PeopleSoft 8.4.

The following section contains mandatory configuration points for Oracle Financial Analytics:

• Configuring PeopleSoft Trees. For PeopleSoft, the Financial Analytics application sources data from a data structure, called PeopleSoft Trees, to get information about the organization's General Ledger hierarchies, and so on. For a PeopleSoft environment with different tree names to the Financial Analytics application, you need to import these into the PowerCenter repository, and replace the old tree names with the new tree names. For more on PeopleSoft Trees, see About PeopleSoft Trees in Oracle Financial Analytics.