Time characteristic hierarchy in drill down report

Hello Experts,
I try to modify the standard drilldown report in CJE2 - 001/12KST1C. It contains selection characteristic Period/year. Is it possible to add hierarchy to this characteristic? Ie. I want to be able to select year and drill down to period, simlilar like with WBS elements in the project. Currently it is possible to select one period but not the whole year.
Regards
Jiri

To bring the WBS elements drill down,include object type in the chracteristics of the report.
Regarding the year, I am not sure of bringing it in charaterisctics of report.But you can do awork around by including From period/year and To period/Year as characterictics in the form of that report and making it as entry in the initial screen.By this way you can get each year's report, only thing is you have to exit the report screen for different years.

Similar Messages

Reporting by org hierarchy with drill down by each level of reports to...

Hello,
I'm trying to determine how to aggregate reporting by org hierarchy. Utlimately to report on opportunities at the highest level (CEO; all opportunities below CEO) then a second drill down report that shows summary by Level 2 (all those who report to the CEO), then again by Level 3 drill down which would be those who report to somone in Level 2. In all instances I want the report to show all records that ultimately roll up to that level (thus include direct reports alll of their direct and indirect reports )
Level 1
CEO $10,000,000 200 Optys
Level 2
Sales Leader 1 $ 3,000,000
Sales Leader 2 $ 2,000,000
Sales Leader 3 $ 1,500,000
Sales Leader 4 $ 3,500,000
Level 3
<ul><li>- rollup of all that report to Sales Leader 1 (and so on) aggregated by first level of direct reports ($3,000,000)
     Sales Mgr 1.1 $ 1,000,000
     Sales Mgr 1.2 $ 500,000
     Sales Mgr 1.3 $ 750,000
     Sales Mgr 1.4 $ 250,000</li>
</ul>
I'd appreicate any help you can send my way.
Thanks, Aaron

Hi Aaron,
I have come across this and found that using the "Reports To" hierarchy and "Territory Team" hierarchy are not sufficient. I implemented this as a solution for one of our clients and it works very well:
I have modified the user entity and renamed 4 standard fields:
•     Business Unit renamed to "Primary Line of Business"
•     Business Unit Level 1 renamed to "BU Group"
•     Business Unit Level 2 renamed to "Business Unit"
•     Business Unit Level 3renamed to "Team"
Not all fields go through into analytics so I had to use these fields which are available in the Opportunity-Product History subject area. The downside is that they have to be text boxes so restrict access to who can populate these. From this you can get 4 hierarchy levels and drill from one to the next. The record owner then becomes the lowest level in your report and it can look something like this:
Level 1
Primary Line of Business
Level 2
BU Group
BU Group
Level 3
Business Unit
Business Unit
Business Unit
Level 4
Team
Team
Team
Team
Level 5
Sales Person 1
Sales Person 2
Sales Person 3
Sales Person 4
Sales Person 5
Obviously it would appear side by side in the report..
Thanks

How to add the required characterists and key figures to drill down report?

hi,
i am creating a drill down report using t.code FKI4. however i noticed that some of the characteristics and key figures required by me is not listed in the report catalog. how can i add the required characteristis and key figures to the report catalog?

Hi Inna,
Based on my research, a drilldown report is a layout design that at first hides complexity and enables the user to toggle conditionally hidden report items to control how much detail data they want to see. Drilldown reports are used to change the report
layout interactively. So it wouldn’t affect the rows displayed in the outmost group. Though some rows are hidden when the report is initially run, it will still count them. This is by design.
Furthermore, if I understand correctly, you also expect the outmost group is a dynamic group depends on the drilldown action, right? As per my understanding, this function still cannot be achieved at this moment.
Thanks for your understanding.
Regards,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Drill Down Report Performance issue?

Hi,
why drill down report is slower performance comparing with Action link/Navigation method? what could be the back end processing?
Thanks
MRD

Need to know/see your config to tell why it is slow, I would suggest to follow best practices for the same.
Drill down back end process something like:
Report fetch next level columns and the all aggregated measures are grouped by next level this may take some time unless you go with aggregate table (is part of best practices)
Appreciate if you mark as correct/helpful

Customized drill-down report cannot go to line item level (FGI4 and FGI1)

Hi Expert,
I created a customized drill-down report using New GL features, as follows:
FGI4 create form, with reference to form: 0SAPBLNCE-01
FGI1 create report for the form created.
After that I set some things like characteristic, variables, and output type.
When I execute the report, the data shown cannot be drill-down to line item level:
Goto > Line Item (this function is disabled).
Kindly advise why I cannot goto line item level, where I copy from standard form: 0SAPBLNCE-01, which ha sthe features of drill-down to line item level.
Thanks
sbmel

Hi sbmel,
For calling up a line item report in a drill down report you need to make the below settins:-
- You first have to generate the line item report with program RGRGENSI for your summary table.
- Then assign the generated line item report to the summary report.
Assiging the report is part of the 'Change drilldown report' function, which you reach by activating the characteristic selection field and then Extras -> Report assignment.
In the dialog box that appears, choose the 'Other report type' function and insert the line item report generated earlier, as an ABAP report
Regards,
Gaurav
Edited by: gka2707 on Jul 19, 2010 8:07 AM

FSI0 - Drill Down Reports for Account Balance Analysis

Any orientation on this issue will be greatly appreciated.
These are the steps I did to create a new Drill-Down Report for my customer.
1. Created and modified a new Form based on the Form for the Financial Statement Analysis 0SAPBLNCE-04 (Periodic Actual vs Actual) using Transaction FSI4 (Create) and FSI5 (Change)
2. Created and modified a new Report with reference to the Form I just created using transactions FSI1 (Create) and FSI2 (Change)
3. I select "Expand: Completely" to see all Account Balances
3. All the totals match between the Original Standard Report and the new report I just created.
4. On both reports, when I select a Balance and then select the GOTO \ Line Items to get the list of documents I get the following results:
==> Most of the cases (I would say probably 80% of the cases) the Account Balance I selected matches with the Total of Line Items that is displayed when I do the GOTO \ Line Items
==> In some cases (just a few) the Account Balance does not match at all with the totals of Line Items that is displayed when I do the GOTO \ Line Items
Can somebody explain why ? Shouldn't the totals match all the time since I am specifically selecting a balance to see all its line items? Where are the missing line items?
Since these are just a few cases my customer is okay with it but he would like to hear a logic explanation why the Account Balance and its line items do not match on this report.

Hello,
There is a possibility that you have activate line item display for some of the accounts at a later stage. Meaning that earlier postings were not be shown for the earlier postings but only totals will be made available. Therefore, obviously there is bound to be difference between line item report and totals report.
You need to identify which accounts are being changed with line item display at a later stage.
In case if you forget to keep GL Line item display for an account, but the posting are already made the following steps you would required to get the line item display retrospectively.
1. Note that you are NOT required to make the balance of that GL account to ZERO. Please do not confuse with Open Item Management.
2. Put the check box line item display for the account in FS00. Make sure you are entering right company code.
3. Block the account for posting in COA Segment and Company Code Segment in FS00
4. Go to SA38 and run program RFSEPA01 (Give correct GL Account and Company Code)
5. Now, remove the block you kept on the GL Account in FS00.
This will reset the line item display retrospectively.
Hope this will solve your problem.
Regards,
Ravi

Set headers for drill-down reports.

Hi!!!
The problem we have by now is when printing a report, selected characteristis are showed in header as "multiple values" instead of showing the real values that user have choose.
Does anybody knows how to set headers for drill-down reports in order to see selected characteristics?
Thanks in advance...
Adela Cambiasso.

Sorry, me again...
I have found yet they way to show in the header the report parameters, I mean, the selection criterias that user used when execute the report... I was able to show selected characteristics inside de report but not the selection criteria...
Do you know what I have lost? or what to use for this?
Thanks again.
Adela.

Query in EIS Drill-Down Reports

Hi all:
We want to build Drill-down reports in EIS. I know the basic of creating a drill-down report. Created a sample using SQL server database and Essbase 9.3.1 dummy(test) cube.
Just to give you a background we have planning application and no Essbase-only applications.
I wanted to know is it possible to use an already existing cube in essbase to create drill down reports. I do not want to go through a process of creating the hierarchy in EIS as we already have DRM and a process around metadata creation, which is not likely to change.
Is there some tool that can take a outline and create a Model/Metaoutline in EIS ?
Please let me know in case you have any suggestions or wild ideas on this :)

The short answer is no, you can't do it that way.
EIS development flows from the relational side to the Essbase side.
The Metadata Outline cannot be built until the OLAP Model has been created. Drill through reports are LROs defined in the Metadata Outline and linked through the OLAP model to the source tables.
I tried to do the same thing four years ago and learned that EIS has to build the Essbase Outline in order to enable drill-through. In Version 11.1.2 that has not changed.
I am curious, though. I was told by my Oracle Planning instructors that EIS doesn't work with Planning. Is that no longer true?
Good Luck.
Tim

Drill down reports using SVG component

I've created and dynamic report and an SVG chart following the examples of the tutorials. I was wondering if, and how, it was possible to create drill-down reports i.e report on colour, then clicking on that colour would reveal the types of car and so on. Does anyone have an example?
Thanks
Darren

Darren,
The query for an SVG chart requires 3 columns: Link, Label, and Value. You use the Link value to provide a link to another page. This link can also pass parameters to the next page.
If you set up a page for each "level" of your drill-down (e.g. color, type of car, etc), you can link from the higher-level page to the lower level page and pass the value that was clicked on in the chart.
Take a look in the HTML DB User's Guide for the section about "Using f?p Syntax to Link Pages": http://download-west.oracle.com/docs/cd/B14117_01/appdev.101/b10992/mvl_fund.htm#BEIJCIAG
You would use that syntax in the Link column of the query for your chart. Here is part of a query I used to drill down from one pie char to another (on page 3), passing the selected project to a variable called P3_PROJECT.
select 'f?p=&APP_ID.:3:&SESSION.::NO::P3_PROJECT:' || Project L,
Project, sum(Time)
from v_timesheet
where ...
Does that help?

Drill-down reports Discoverer-style

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

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

BW drill down report

Hi friends,
I have built a query which is analytical, now the business wants it to be a drill down. How can i make this drill down report? Can any please help me.
Thanks in advance.
Regards
Ananth

Hi Ananth,
Drill down in analytical reporting means being able to see further details for a given record.
So if you want the users to be able to drill down further and see more details of whatever is being reported in the initial screen you could add the required characteristic for drill down in the "Free characteristics" section of your queries. These are not displayed in the initial format of the report but the user has the facility to add/exclude them in the report format.
Moreover if you would like them to drill down from one report to another, you could setup Report to Report interfaces (transaction RSBBS).
Hope it helps.
Regards
Anurag

Drill down reporting - add new field

Hi experts,
                   we have created drill down reporting for vendor line item using FKI4. we need to add new characteristic (new field - assignment column- zuonr) for form and reports.
guide me.
Regards,
Ravi

Hi
For columns select 'key figure with characteristics' . There   give Key figure - balance c/f' and select the characteristic from the   left side list.
Then for rows select ' characteristic'    and   again select from left hand side list.
You define the total where required.   Save this form .
You can also   create report in GRR1 using the form created.
I   am sending   you a document in you contact details.
Thanks
kamala

Drill down report is showing popup even though it's disable in column properties

Hello,
I am facing an functionality issue where I have crated Summary to drill down report. Summary is chart and drill down is table view and I am using OBIEE Action link here.
Now I have disabled the Popup in column properties so when user click the bar on the graph they will directly navigate to detail report. But strangely after disabling the Popup, when i click on bar the drilldown report is coming as popup link.
does anyone has any idea how to handle this issue??

It would seem to be a issue with either the hardware of the printer or the replacement cartridge. If it is the cartridge, it should be covered under warranty (if it is HP genuine) since you just purchased it. At this time I think that your best move would be to contact HP's Technical Support to see about further options for you.
The only other option would be to try another new replacement cartridge to rule in or out the cartridge being at fault.
If you are calling within North America, the number is 1-800-474-6836 and for all other regions, click here.
JERENDS
I work on behalf of HP
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to the left of the reply button to say “Thanks” for helping!

Drill down report without using heirarchies in OBIEE11g

Hi,
Can we create multiple column drill down report without using hierarchies in OBIEE11g?
Kindly let me know the solution.
Thank you!
-Harshith

Yes, It can be done, but for each drill level you will require one seperate report. Drilling can be achieved using OBIEE Report Navigation.
For eg. If I have to create a drill report which starts from Year and goes to QTR and then to Month level. That means I have to create 3 reports.
1. A year report which will have report data at year level (Consider Year, Product, Order_QTY and Order_Amt are the columns)
2. A QTR report which will have report data at Qtr level. This report will have Year column in filter section as IS PROMPTED (Consider Qtr, Product, Order_QTY and Order_Amt are the columns).
3. A Monthly report which will have report data at Month level. This report will have Year, Qtr column in filter section as IS PROMPTED (Consider Month, Product, Order_QTY and Order_Amt are the columns).
Then we can go to Yearly report and put the OBIEE navigation on Year column and our target report will be QTR report. Similarly in Qtrly report put the OBIEE navigation on QTR column and our Target report will be Monthly report.
This way you can impliment drilling without hierarchy.
For step by step see below URL:
http://www.askjohnobiee.com/2012/07/how-to-drill-through-guided-navigation.html
Appriciate if you can mark Correct.
Thanks,
Kashi
Edited by: K N Yadav on 4 Jun, 2013 10:27 PM

Drill Down report in new window

Hi All,
i have report prompt ( Dashboard) and report . if i click on date column then it will display drill down report.
My issue is drill down report iis displaying in current window. if i click on return to previous screen button then prompt are refreshing. user was confusing which parameters he was selected.
I need solution like.
1) After coming back also prompts are should not refresh . it should display prompts which were user selected.
or
2) drill down report should display in other window. ( then user will close that window he can see his selected prompts)
how can achieve this one in OBIEE. please help me.
Thanks in advance for your time.

Couple things,
you can create primary interaction as Action Link and then in the action link menu you can select option for the new window (that I what I did)
Edit Action Links > More... > Edit Action > Options
For the values, you can use presentation variables and they will carry the values (your fields also have to be prompted, but I think you already have that).
Again this works for me just fine.
Hope this helps.

Time characteristic hierarchy in drill down report

Similar Messages

Maybe you are looking for