Adding Planning Drill Through Definitions

In Calculation Manager, you can list, add, edit, and delete these cell drill through definitions for Planning plan types.

If you are working with a Planning plan type, and a Planning form that contains members whose data is loaded from a source such as Data Management, you can drill through to view more details for the cell data source.

To add a Planning drill through definition:

1. In System View, click (Database Properties).
2. In Enterprise View, right-click an application, and then select Drill Through Definitions.
   If asked to confirm the whether you want to start the database, click OK,
3. Click OK to confirm that you want to start the database, and then click OK in the Database Start Action Status dialog box.
4. In the Drill Through Definitions dialog box, click (Add).
5. In Create Drill Through Definition, create the drill through definition by entering the following information:

   • URL Name—Name to identify the drill through definition

   • XML Contents—XML to define the URL link

     Enter the URL without the server and port information. The URL must contain the parameter name and column name from the TDATASEG table enclosed in the symbol $. For example, enter: LEDGER_ID=$ATTR1$&GL_PERIOD=$ATTR2$. In this example the value of ATTR1 is passed as a value for the LEDGER_ID parameter, and ATTR2 is passed as the value for the GL_PERIOD parameter. Parameters are separated by the & character.

     To specify the request-response between a client and server for the drill URL format, enter either:

     • GET—Encodes form data into the URL

       For example, enter: GET@http://www.oracle.com/. If no method is entered, then GET is the assumed request response.

     • POST—Displays form data in the message body

       For example, enter: POST@http://www.oracle.com/

     As you enter XML contents, you can click to import a file into the XML Contents area, and you can click to export the XML content to Microsoft Excel.

   • Level 0 Flag—Whether the URL applies only to level 0 descendents of the region.

     For example, if the Level 0 Flag is enabled for the drillable region DESCENDANTS("Market"),@CHILDREN(Qtr1), then the URL is applicable for all states of "Market" during all months of "Qtr1," and for all level 0 members across the remaining dimensions.

   • Regions—Member specifications defining areas of the database that should allow drill-through using the specified URL

     You define drillable regions using a member specification of members from one or more dimensions. Define the member specification using the same Oracle Essbase member-set calculation language that you use for defining security filters. For example, the following is a valid member specification, indicating all eastern states, except "New York", for months of "Qtr1": @REMOVE(@DESCENDANTS("Eastern Region"), "New York"), @CHILDREN(Qtr1).

     To add a region, click Add Region.

6. Click Save, and then OK.