Drill-down reports Discoverer-style

Question

Hi,
I'm looking for a way to implement drill-down reports in HTMLDB. All the references I found are showing details in a 2nd page for a certain row in the 1st page (e.g. ordered items for an order ID).
I'm not looking for this, but for drill-down "a la Discoverer", such as this example
http://www.oracle.com/technology/obe/obe_bi/discoverer/discoverer_1012/viewer/lesson1.htm#t7
One can select there multiple criterias for drill down.
Perhaps the solution would be a combination of tree reports with standard reports
http://www.oracle.com/technology/products/database/htmldb/howtos/howto_tree.html
but I don't see clearly how to do it, especially with a lot of drill-down options.
Do you have any suggestions?
Many thanks,
Marius

Answer 1

I think there are two differen approaches:
- using the HTML report and doing some "dynamic" SQL at the block level
(That means you have to write the drill down - this is the logic that
is done by the tree - by yourself)
If you ever have done the work to do this in combination with a HTML DB report,
please post it here.
- using the a Tree Page with a special layout and view
Which one to use depends on how often you have to use this.
You can see an example under:
http://htmldb.oracle.com/pls/otn/f?p=41053:30
Here is a quick hack for the Tree Page variant, that may help you.
Using a Tree page uning a view and changing the tree template gives you some of
this functionality. If you have to do more of this kind use a stylesheet (.css) to
controll the layout.
1. Create a View that represents your Hierarchy (Structure)
For every level create a UNION secion.
Using UNION you can get the records from different sources also.
2. Create a Page with a Tree, SQL Query Based.
Use the View that you created before.
NAME .. are the levels of your dimensions
A1, A2 .. are your measures of your fact
ID, PID .. the hierarchy (structure) information
* Step 1 - creating a view:
create or replace view tree as
select id, pid, name, link, a1, a2
from (
-- Level 1 (Root Level)
select
to_char(ORDER_TIMESTAMP,'YYYY') id, null pid,
to_char(ORDER_TIMESTAMP,'YYYY') name, null link,
to_char(sum(ORDER_TOTAL),'999G9990D99') a1, to_char(count(*),'999G9990D99') a2
from DEMO_ORDERS
group by
to_char(ORDER_TIMESTAMP,'YYYY'),
to_char(ORDER_TIMESTAMP,'YYYY')
UNION
-- Level 2
select
to_char(ORDER_TIMESTAMP,'YYYYMM'), to_char(ORDER_TIMESTAMP,'YYYY'),
to_char(ORDER_TIMESTAMP,'Month'), null,
to_char(sum(ORDER_TOTAL),'999G9990D99'), to_char(count(*),'999G9990D99')
from DEMO_ORDERS
group by
to_char(ORDER_TIMESTAMP,'YYYYMM'), to_char(ORDER_TIMESTAMP,'YYYY'),
to_char(ORDER_TIMESTAMP,'Month')
UNION
-- Level 3 (Leaf Level)
select
to_char(ORDER_TIMESTAMP,'YYYYMMDD'), to_char(ORDER_TIMESTAMP,'YYYYMM'),
to_char(ORDER_TIMESTAMP,'DD. Day'), null,
to_char(sum(ORDER_TOTAL),'999G9990D99'), to_char(count(*),'999G9990D99')
from DEMO_ORDERS
group by
to_char(ORDER_TIMESTAMP,'YYYYMMDD'), to_char(ORDER_TIMESTAMP,'YYYYMM'),
to_char(ORDER_TIMESTAMP,'DD. Day')
)If you have a lot of this kind of reports you realy should think to
use discoverer. It does a lot of sql behind the szenes and also in the
presentation logic - this is what you have to do here by hand.
If you have more than two measures (A1,A2) you can do the
formatting in your view (realy ugly, but it is a workaround).
* Step 2: Create the tree page
Tree Query:
select
"ID" id, "PID" pid, "NAME" name,
null link, a1 a1, a2 a2
from TREEBefore Tree:
<table border="0" cellspacing="0" cellpadding="0">After Tree:
</table>Leaf Node:
<td style="background:#cece9c;
border-style:solid;
border-color:#f7f7e7 #cece9c #9c9b64 #cece9c;
border-width:1px 0px 1px 0px;" align="left">
</td>Leaf Node Last:
<td style="background:#cece9c;
border-style:solid;
border-color:#f7f7e7 #cece9c #9c9b64 #cece9c;
border-width:1px 0px 1px 0px;" align="left">
</td>Drill Up:
(up)Indent Vertical Line:
<td style="background:#cece9c;
border-style:solid;
border-color:#f7f7e7 #cece9c #9c9b64 #cece9c;
border-width:1px 0px 1px 0px;" > </td>Indent Vertical Line Last:
<td style="background:#cece9c;
border-style:solid;
border-color:#f7f7e7 #cece9c #9c9b64 #cece9c;
border-width:1px 0px 1px 0px;" > </td>Unexpanded Parent:
<td style="background:#cece9c;
border-style:solid;
border-color:#f7f7e7 #cece9c #9c9b64 #cece9c;
border-width:1px 0px 1px 0px;" >
< a href="#DRILL_DOWN#">
< img src="#IMAGE_PREFIX#rollup_plus_dgray.gif" width="16" height="22" border="0">
< /a>
</td>Unexpanded Parent Last:
<td style="background:#cece9c;
border-style:solid;
border-color:#f7f7e7 #cece9c #9c9b64 #cece9c;
border-width:1px 0px 1px 0px;" >
< a href="#DRILL_DOWN#">
< img src="#IMAGE_PREFIX#rollup_plus_dgray.gif" width="16" height="22" border="0">
< /a>
</td>Expanded Parent:
<td style="background:#cece9c;
border-style:solid;
border-color:#f7f7e7 #cece9c #9c9b64 #cece9c;
border-width:1px 0px 1px 0px;" >
< a href="#DRILL_DOWN#">
< img src="#IMAGE_PREFIX#rollup_minus_dgray.gif" width="16" height="22" border="0">
< /a>
</td>Expanded Parent Last:
<td style="background:#cece9c;
border-style:solid;
border-color:#f7f7e7 #cece9c #9c9b64 #cece9c;
border-width:1px 0px 1px 0px;" >
< a href="#DRILL_DOWN#">
< img src="#IMAGE_PREFIX#rollup_minus_dgray.gif" width="16" height="22" border="0">
< /a>
</td>Parent Node Template:
<tr>#INDENT#
<td style="color:#00319c; background:#cece9c;
border-style:solid;
border-color:#f7f7e7 #9c9b64 #9c9b64 #cece9c;
border-width:1px 1px 1px 0px;" colspan="#COLSPAN#"
  valign="CENTER" class="tiny">#NAME#</td>
<td align="right" style="background:#f7f7e7;">#A1#</td>
<td align="right" style="background:#f7f7e7;">#A2#</td>
#DRILL_UP#
</tr>Node Text Template:
<tr>#INDENT#
<td style="color:#00319c; background:#cece9c;
border-style:solid;
border-color:#f7f7e7 #9c9b64 #9c9b64 #cece9c;
border-width:1px 1px 1px 0px;" colspan="#COLSPAN#"
  valign="CENTER" class="tiny">#NAME#</td>
<td align="right" style="background:#f7f7e7;">#A1#</td>
<td align="right" style="background:#f7f7e7;">#A2#</td>
</tr>Name Link Anchor Tag:
< a href="#LINK#">#NAME#</a>Name Link Not Anchor Tag:
#NAME#* Extended Version of the View. Use this style of query if you have more than two measures:
create or replace view tree as
select id, pid, name, link,
'<table border="0" cellspacing="0" cellpadding="0" style="background:#f7f7e7;">'||
case when rownum = 1
then '<tr style="background:#cece9c;">'||
'<th style="border-style:solid; border-color:#cece9c #9c9b64 #9c9b64 #f7f7e7; border-width:0px 1px 1px 1px;">Amount</th>'||
  '<th style="border-style:solid; border-color:#cece9c #9c9b64 #9c9b64 #f7f7e7; border-width:0px 1px 1px 1px;">Orders</th>'||
  '<th style="border-style:solid; border-color:#cece9c #9c9b64 #9c9b64 #f7f7e7; border-width:0px 1px 1px 1px;">Measure</th>'||
  '<th style="border-style:solid; border-color:#cece9c #9c9b64 #9c9b64 #f7f7e7; border-width:0px 1px 1px 1px;">Measure</th>'||
'</tr>'
end||
case
when lvl = 2 then '<tr style="color:#000088;">'
when lvl = 3 then '<tr style="color:#888888;">'
else '<tr>'
end ||
'<td align="right" width="80px" height="24px" style="background:#f7f7e7; border-style:solid; border-color:#9c9b64 #9c9b64 #f7f7e7 #f7f7e7; border-width:1px 1px 0px 0px;">'||
to_char(a1,'999G9990D99')||'</td>'||
'<td align="right" width="80px" height="24px" style="background:#f7f7e7; border-style:solid; border-color:#9c9b64 #9c9b64 #f7f7e7 #f7f7e7; border-width:1px 1px 0px 0px;">'||
to_char(a2,'999G9990D99')||'</td>'||
'<td align="right" width="80px" height="24px" style="background:#f7f7e7; border-style:solid; border-color:#9c9b64 #9c9b64 #f7f7e7 #f7f7e7; border-width:1px 1px 0px 0px;">'||
to_char(a3,'999G9990D99')||'</td>'||
'<td align="right" width="80px" height="24px" style="background:#f7f7e7; border-style:solid; border-color:#9c9b64 #9c9b64 #f7f7e7 #f7f7e7; border-width:1px 1px 0px 0px;">'||
to_char(a4,'999G9990D99')||'</td>'||
'</tr>'||
'</table>' a1, null a2
from (
-- Level 1 (Root Level)
select
1 lvl, to_char(ORDER_TIMESTAMP,'YYYY') id, null pid,
to_char(ORDER_TIMESTAMP,'YYYY') name, null link,
sum(ORDER_TOTAL) a1, count(*) a2,
count(*)*10 a3, count(*)*100 a4
from DEMO_ORDERS
group by
to_char(ORDER_TIMESTAMP,'YYYY'),
to_char(ORDER_TIMESTAMP,'YYYY')
UNION
-- Level 2
select
2, to_char(ORDER_TIMESTAMP,'YYYYMM'), to_char(ORDER_TIMESTAMP,'YYYY'),
to_char(ORDER_TIMESTAMP,'Month'), null,
sum(ORDER_TOTAL), count(*),
count(*)*10, count(*)*100
from DEMO_ORDERS
group by
to_char(ORDER_TIMESTAMP,'YYYYMM'), to_char(ORDER_TIMESTAMP,'YYYY'),
to_char(ORDER_TIMESTAMP,'Month')
UNION
-- Level 3 (Leaf Level)
select
3, to_char(ORDER_TIMESTAMP,'YYYYMMDD'), to_char(ORDER_TIMESTAMP,'YYYYMM'),
to_char(ORDER_TIMESTAMP,'DD. Day'), null,
sum(ORDER_TOTAL), count(*),
count(*)*10, count(*)*100
from DEMO_ORDERS
group by
to_char(ORDER_TIMESTAMP,'YYYYMMDD'), to_char(ORDER_TIMESTAMP,'YYYYMM'),
to_char(ORDER_TIMESTAMP,'DD. Day')
)If you use stylesheets the above query will be more suitable.
See also:
Expand/Collpase Lists
Hope that helps, Willi