Using Drilling Through to Source

Data Integration provides a framework that enables you to drill through from your target application to the source application. Use drill through when you want to understand the source of a data value, or you need a granular level of detail for a value.

Drill regions are defined to identify the cells that are drillable in the EPM data forms. The drill regions are identified by specifying a data slice that is drillable. The drill region can be created using two methods:

1. Auto create during data load—If you enable the Create Drill Region in Application Options, then drill regions are created based on the dimensions selected to participate in the Drill Region. For more information, see Defining Application Dimension Details.

2. Custom drill region—You can define a Custom drill region using Essbase member functions. This provides more control and easier maintenance of drill regions. For more information, see Defining Drill Details for an Application.

There are two flavors of drill flow supported:

1. Standard Drill—In this mode you drill from Oracle Enterprise Performance Management Cloud data form to a landing page and then drill to the source system data. In this method you must load data using Data Integration. You must use the Full Workflow mode, which is supported for all business service types. For this mode you can use the auto-created drill region or custom drill region.

2. Direct Drill—In this mode you drill from EPM Cloud data form directly to the source system data. In this case, you can load the data using Full Workflow mode, Quick mode or even load directly to the EPM Cloud business process. This mode is not supported for Account Reconciliation and Profitability and Cost Management business processes. For this mode you must define custom drill region.

When drilling through to the source from the target application, a separate landing page is displayed that shows all rows that comprise the amount from the selected cell.

Note:

If you map to an alias when loading data to Oracle Essbase, then the drill-through might fail because the filter on the landing page uses the member from Essbase. If this case, use the member name instead of the alias.

In the following example, drill through is available from a data form in Planning:

From this landing page, you can open the source document or continue to drill through to the defined source system landing page.

Note:

Drill through functionality is not supported for exchange rates data loaded to Planning applications.