Set Up Drill Down in Oracle BI Answers from General Ledger to Subledger

Note:

The Drill Down feature is not supported on Oracle JD Edwards source systems.

Oracle BI Applications enables you to trace a GL Journal to the subledger transaction that created that journal. This ability (or drill down) is achieved through the 'Navigation' feature in Oracle BI Answers.
To set up drill down in Oracle BI Answers from General Ledger to subledger:

1. Create your subledger request from 'Financials - AP Transactions' or 'Financials - AR Transactions' catalog as applicable.
   
2. 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'.
   
3. Build your GL Journal request from the 'Financials - GL Detail Transactions' catalog.
   
4. To your request, add the column 'GL Journal ID' under the 'Document Details' folder.
   
5. Navigate to the Column Properties of this column, and set the Value Interaction property in the Column Format tab to 'Navigate'.
   
6. Add a navigation target and set the target location to the sub ledger request you created earlier.
   You might add multiple navigation targets if your GL report shows transactions from multiple subledgers and you want to drill from GL to the appropriate Subledger report. For example, if your GL report shows transactions from AP, AR and Revenue, and you have three subledger reports for each of these, you can add three navigation targets (by selecting the option 'Add Navigation Targets') and set the locations to each of these reports. Subsequently, when you run the GL report and when you click the "GL Journal ID" column Value, a popup appears, where you need to click the appropriate target based on the journal you selected. This will not happen automatically. For example, if you click a journal transaction originating from AP, you need to pick the appropriate subledger report (that is, the AP report in this case) to drill into the AP report and see the details. You can add the Group Account Number attribute from GL Account Dimension to your GL report to easily identify the subledger that the GL transaction belongs to.
   

Note:

For COGS, the 'GL Journal ID' column is not exposed in any Subjects Areas. It is available in the Business Model and Mapping layer of the Oracle BI repository under the logical tables 'Dim - GL COGS Details'. As a workaround, you can create Subjects Areas to report of detail level transactions for COGS and expose this column under the 'Document Details' folder in the Subjects Area and use similar steps as above to set up a drill-down from GL to COGS.
To create a Subjects Area for COGS:

1. Using the Administration Tool, open OracleBIAnalyticsApps.rpd.
   The OracleBIAnalyticsApps.rpd file is located at:
   

   ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\
   coreapplication_obisn\repository
   

2. Create an empty Subjects Area (for example, Financials – GL Cost of Goods Sold). Set properties by following other Subjects Areas.
   
3. Drag 'Dim – GL COGS Details' and 'Fact - Fins - GL Cost of Goods Sold Posted' to the Subjects Area.
   
4. Drag other dimensions.
   
5. Rename the presentation table 'Dim – GL COGS Details' to 'Document Details'.
   
6. Rename the presentation table 'Fact - Fins - GL Cost of Goods Sold Posted' to 'Facts - GL Cost of Goods Sold'. Rename other dimensions if necessary.
   

You might also follow this same process to create a presentation table for Revenue to be able to drill from GL to Revenue level detail transactions.