Hi,
I have a report with the following structure:
District Store Sales
D1 S1 100
D1 S2 150
D1 S3 200
D2 S4 250
D2 S5 300
The requirement is to burst the report to District managers and Store managers where District manager should be able to see all stores assigned to them where as Store Manager should see just his store. I am able to burst to District managers, but could anyone help me to understand how do I burst reports to Store managers as well please? Or is this has to be two separate reports? My report query has above data along with one column for District manger emp no and another col for store manager emp no. And I have a another query for email addresses. Right now, I am creating a master detail with Report query and email query on District manager emp no, which works fine for DMs. How do I burst for Store managers as well.
Is your burst table set up with both levels? and more importantly, are both sets of keys absolutely unique?
| key | email |
| s1 | email |
| s2 | email |
| s3 | email |
| s4 | email |
| s5 | email |
| d1 | email |
| d2 | email |
Master Detail links can be set to feed parameters. What you can do is, instead of doing a link from the burst key to the district key, create a parameter in the target query [District Key]=?burstKey? or [Store Key]=?burstKey?
In the master detail, set the link to the parameter and when the report runs each row in the burst table will run either a district or a store.
Hi CognosPaul,
Thanks for looking into this. I tried to implement but no luck. I didn't quite understand how to set that master detail. I tried but got error: RSV-VAL-0016 The burst query Report cannot be a nested query.
I created a sample report out of 'GO Data Warehouse' package. Could you please take a look?
Appreciate your help on this.
Good day!
-Anu
Try setting the Burst Group query to your burst query.
The system I'm sitting at today doesn't have the samples installed, but take a look at the attached. I think it should work.
Thanks!. It worked.
Only thing I noticed is, the report got bursted for all the employees in the query (with no data). I created a local join to limit to only DM or SM employee IDs and used that query as BurstGroup query.
Thanks again for the quick response. You made my day !!